Friday, June 12, 2009

Testing Essbase or Planning Connection from Oracle Data Integrator (ODI) results in error

When testing Essbase or Planning Data Server connection from ODI results in "Driver Must be Specificed" error and below is the call stack in the error.

ava.sql.SQLException: Driver must be specified

at com.sunopsis.sql.SnpsConnection.a(SnpsConnection.java)

at com.sunopsis.sql.SnpsConnection.testConnection(SnpsConnection.java)

at com.sunopsis.sql.SnpsConnection.testConnection(SnpsConnection.java)

at com.sunopsis.graphical.l.pm.o(pm.java)

at com.sunopsis.graphical.l.pm.r(pm.java)

at com.sunopsis.graphical.l.pm.g(pm.java)

at com.sunopsis.graphical.l.pm.a(pm.java)

at com.sunopsis.graphical.l.pm.a(pm.java)

at com.sunopsis.graphical.l.iz.actionPerformed(iz.java)

at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)

at javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(Unknown Source)

at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)

at javax.swing.DefaultButtonModel.setPressed(Unknown Source)

at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Source)

at java.awt.Component.processMouseEvent(Unknown Source)

at java.awt.Component.processEvent(Unknown Source)

at java.awt.Container.processEvent(Unknown Source)

at java.awt.Component.dispatchEventImpl(Unknown Source)

at java.awt.Container.dispatchEventImpl(Unknown Source)

at java.awt.Component.dispatchEvent(Unknown Source)

at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)

at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)

at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)

at java.awt.Container.dispatchEventImpl(Unknown Source)

at java.awt.Window.dispatchEventImpl(Unknown Source)

at java.awt.Component.dispatchEvent(Unknown Source)

at java.awt.EventQueue.dispatchEvent(Unknown Source)

at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)

at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)

at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)

at java.awt.Dialog$1.run(Unknown Source)

at java.awt.Dialog.show(Unknown Source)

at java.awt.Component.show(Unknown Source)

at java.awt.Component.setVisible(Unknown Source)

at com.sunopsis.graphical.l.pm.q(pm.java)

at com.sunopsis.graphical.l.pm.(pm.java)

at com.sunopsis.graphical.frame.b.jh.bx(jh.java)

at com.sunopsis.graphical.frame.bo.w(bo.java)

at com.sunopsis.graphical.frame.bo.d(bo.java)

at com.sunopsis.graphical.frame.w.actionPerformed(w.java)

at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)

at javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(Unknown Source)

at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)

at javax.swing.DefaultButtonModel.setPressed(Unknown Source)

at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Source)

at java.awt.Component.processMouseEvent(Unknown Source)

at java.awt.Component.processEvent(Unknown Source)

at java.awt.Container.processEvent(Unknown Source)

at java.awt.Component.dispatchEventImpl(Unknown Source)

at java.awt.Container.dispatchEventImpl(Unknown Source)

at java.awt.Component.dispatchEvent(Unknown Source)

at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)

at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)

at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)

at java.awt.Container.dispatchEventImpl(Unknown Source)

at java.awt.Window.dispatchEventImpl(Unknown Source)

at java.awt.Component.dispatchEvent(Unknown Source)

at java.awt.EventQueue.dispatchEvent(Unknown Source)

at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)

at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)

at java.awt.EventDispatchThread.pumpEvents(Unknown Source)

at java.awt.EventDispatchThread.pumpEvents(Unknown Source)

at java.awt.EventDispatchThread.run(Unknown Source)


This is the expected error. You can only test the JDBC connection, not Essbase,Planning and HFM connection.

It is ok to ingnore this error and move forward inserting the Physical Schema.

Wednesday, June 3, 2009

How to setup Hyperion BIPlus with Custom Ports

When you deploy Hyperion application, there may be a need to deploy Hyperion BIPlus where there is firewall between Server and Client. In this case, you cannot deploy BIPlus with Default ports as BIPlus uses dynamic ports and due to Security reasons, you cannot open tons of ports through the Firewall.

In such case, it make more sense to deploy BIPlus with Static Ports, that can be opened on Firewall.

To Deploy Hyperion BIPLus with Static Ports

- Set the RMI Server port in fr_global.properties

RMIPort=

- Set the ports for FR Server in fr_repserver.properties

HRRepSvrPort1=

HRRepSvrPort2=

- Run the Configuration Utility for BIPlus and set the static ports for

GSM Port
Core Service Port
Name Service Port
Service Broker Port
Job Service Port
Event Service Port
Repository Service Port

- Set the Planning ADM RMI Server port in ADM.properties file under \common\ADM\9.3.1\lib

ADM_RMI_PORT=
ADM_RMI_SERVER_PORT=

ADM_RMI_PORT will be same as RMI port in fr_global.properties file.