FDM Application Migration - Page Not Found

When you migrate FDM application from one environment to another, one thing you need to remember to use the exactly same UNC path for the application. If the UNC path is different on the Target application, then you may see "Page Not found" error while performing the Import data file operation.

If the source application have UNC \\HostName\Apps\FDMapp, then Target application should be \\Hostname\Apps\FDMapp

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.

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.

Informatica 8.1.1 install fail on Windows

Informatica 8.1.1 install on Windows 2003 may results in following error. This error occur when installer try to configure the domain.

STDOUT: Installing the service '"Informatica Services 8.1.1"' on node ''...

Using CURRENT_DIR: D:\Hyperion\Informatica\PowerCenter8.1.1\server\tomcat\bin

Using INFA_HOME: D:\Hyperion\Informatica\PowerCenter8.1.1

The service '"Informatica Services 8.1.1"' has been installed.

The Informatica Services 8.1.1 service is starting.



STDERR: '"D:\Hyperion\Informatica\PowerCenter8.1.1\server\bin\infacmd.bat" getNodeName' is not recognized as an internal or external command,

operable program or batch file.

The Informatica Services 8.1.1 service could not be started.

The service did not report an error.


More help is available by typing NET HELPMSG 3534.

This may occur due to COMSPEC environment variable on Windows Server. If this variable is not pointing to correct CMD.exe executable, this issue may arise. Check this environment variable. It should be c:\windows\system32\cmd.exe.

How do I upgrade Informatica Hyperion Repository from 7.1.4 to 8.1.1

During the Hyperion upgrade from System 9 to Hyperion 11.1.1.1, there may be a need to upgrade the existing Hyperion DIM repository from 7.1.4 to 8.1.1 so that it can be used with Informatica 8.1.1.

Lets assume that you are setting up the new Hyperion 11.1.1.1 environment with DIM 8.1.1. and now you need to use the old Hyperion DIM repository that exists in System 9 environment.

- Export the DIM Schema from system 9 Database and import it into Target 11.1.1.1 environment
- Create a new Repository Service into Target in Admin Console and associate it with imported schema from System 9
- If you try to start the Repository Service, it will not start as the Repository Version is different from that shipped with Informaitca 8.1.1.
- You need to upgrade the Repository first, before starting it. To upgrade the repository, click on Action -> Upgrade Content in the Admin console for the Repository Service. You need to provide the Repository UserId/PWD Administrator/Administrator to initiate the upgrade process. Once the upgrade is successful, you should be able to start the repository.

Note: Before importing the DIM Schema from System 9 environment, DISABLE the Authentication Module. With Authentication Module turned on in the System 9 environment, you will not be able to associate the Repository Service with the DIM repository database imported from System 9 environment. You can disable the Authentication plug-in using the Repository Admin Console.

Importing DIM Repository with Japanese Code Page

When you import a DIM Hyperion repository from Japanese Code Page environment to a new 8.1 ENU environment, you will see the below error.


[[REP_61082] AdminConsole's code page (MS Windows Latin 1 (ANSI), superset of Latin1) is not one-way compatible to repository Hyperion's code page (MS Windows Japanese, superset of Shift-JIS). Failed to connect to repository service [Hyperion].]

This error indicate that Hyperion repository is with Shift-JIS code page, but the Gateway/Node running with Latin 1 code page.

If you need to import and run the Hyperion repository with Shift-JIS code page, you need to set the PM_CODEPAGENAME environment variable in the Target environment to MS932. This environment variable indicate the code page of the Gateway/Node. After this, you can import the Hyperion repository with Shift-JIS code page into 8.1 target environment.