Standalone Programs Created With Workspace SDK Do Not Work With EPM System

There is no standalone installer for the SDK in EPM System, so files necessarey to run standalone programs may not be available.

This document describes the minimum environment needed to stage a remote client deployment of BiPlus SDK for Release, since this release does not have a standalone installer for the SDK.

1. SDK Library

From %EPM_ORACLE_HOME%\common\raframeworkrt\\lib:

2. Other library files

From C:/oracle/Middleware/oracle_common/modules:

From C:/oracle/Middleware/modules:

From C:/oracle/Middleware/wlserver_10.3/server/lib:

From %EPM_ORACLE_HOME%/common

From %EPM_ORACLE_HOME%\products\biplus\common\SQR\lib
Note: spf.jar may not be available if Product Reporting (SQR)was not installed. The start up of the SDK will check for the existence of some jar files, and spf.jar is one of them. If it cannot be found a message is thrown, however it is informational and the java will continue in If desired, the jar file check can be disabled by the java property oneapi.class.verify=false. See Section V on java properties. This property could also be added to SYSPROPS environment variable

3. Other needed files – used to connect to the Shared Services registry. It should be placed in a directory path equal to: %EPM_ORACLE_INSTANCE%\config\foundation\ which is also where it is located on the target server. Also note, that the on the SDK system needs to be a copy of the from the target server, since the Shared Services information it contains is system specific. In other words, the used by the SDK must be a copy of the from the EPM server that will be connected to by the SDK.

default-domain.cfg – on the target system this file is in %EPM_ORACLE_HOME%\common\raframeworkrt\\lib. For the SDk deployment It just needs to be in any directory that is in the CLASSPATH.

logging.xml – this file is in: %EPM_ORACLE_INSTANCE%\config\ReportingAnalysis\SDK Note: There are several files by this name. The one for the SDK directory is in the path noted. On the remote deployment its location needs to be specified by the java property -Doracle.core.ojdl.logging.config.file. See section V.

4. Environment Variables

HYPERION_HOME – by default in this is the same as EPM_ORACLE_HOME and points to C:\Oracle\Middleware\EPMSystem11R1. It is used by the SDK
EPM_ORACLE_INSTANCE – by default in this is set to: C:\oracle\Middleware\user_projects\epmsystem1. This environment variable is specifically used to find, as noted above in section III.

5. Java Properties

The following java properties should be set when invoking the JVM:
-Dlogging.folder=< log-directory>

The jar files need to be copied to the remote SDK client system. There is no need to preserve the directory structure of their original locations from the target system. They all do have to be declared in the CLASSPATH environment variable. The three files in section III need to be placed as described in that section.

let me know in case of any more queries


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s