Configuration

Set the CMS in the LaunchBI.properties file

BOE_CMS_NAME=CMS SERVER e.g. payson1.avnet.com

Authentication

Header variable is preconfigured for the IV-User in the LaunchBI.properties file

BOE_ROLEID_HEADER_NAME=IV-User

Single Sign on

Download the TrustedPrincipal.conf from the CMC or, obtain a copy, if one exists.  The default location for the file is one of the following (on Windows):

C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win64_x86

C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win64_x64

 

Option 1 – Using BOE_TRUSTED_KEY:

Copy the SharedSecret value (everything after the ‘=’) from the TrustedPrincipal.conf and paste it after the BOE_TRUSTED_KEY= in LaunchBI.properties file.

If the line is commented, uncomment the line.

Setting this property overrides all other methods of Trusted Authentication.  If the key is invalid, trusted authentication will fail.

 

Option 2 – Using BOE_TRUSTED_AUTH_HOME: (not yet tested on Websphere/AIX)

Place the TrustedPrincipal.conf file in a folder that is accessible to the web application server (i.e., the account used by the web application server must have read access to that folder).

Set the value of BOE_TRUSTEDAUTH_HOME location in the LaunchBI.properties to the folder path.  Do not include the filename.

If the line is commented, uncomment the line.  If BOE_TRUSTED_KEY is configured, then comment the line in the LaunchBI.properties file.

Setting this property effectively sets the bobj.trustedauth.home Java system property which overrides any value passed via JVM parameters. 

 

Option 3 – Configure the TrustedPrincipal.conf location via JVM parameter: (not yet tested on Websphere/AIX)

Place the TrustedPrincipal.conf file in a folder that is accessible to the web application server (i.e., the account used by the web application server must have read access to that folder).

Configure your Java Web Application Server to start up using the parameter below:

-Dbobj.trustedauth.home=<folder-path>

If either BOE_TRUSTEDAUTH_HOME or BOE_TRUSTED_KEY is configured, then comment the lines in the LaunchBI.properties file.

Passing the JVM property overrides the default location that BO uses to file the TrustedPrincipal.conf file.

 

Option 4 – Place the file in the default location: (not yet tested on Websphere/AIX)

Place the TrustedPrincipal.conf file in the following folder:

<BOE_INSTALL_DIR>\SAP BusinessObjects Enterprise XI 4.0\<platform>

For example, on Windows the file can be placed in either of the following folders:

C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win64_x86

C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win64_x64

If either BOE_TRUSTEDAUTH_HOME or BOE_TRUSTED_KEY is configured, then comment the lines in the LaunchBI.properties file.  If the -Dbobj.trustedauth.home JVM parameters is used, remove it.

 

Set the OpenDoc Path

The OpenDoc path is preconfigured in the LaunchBI.properties file using the BOE_OPEN_DOC_BASE_URL property.  For example:

BOE_OPEN_DOC_BASE_URL=https://velocity-test.avnet.com/BOE/OpenDocument/opendoc/openDocument.jsp?iDocID=%d

TIP:  You can remove the protocal and server if LaunchBI is installed on the same Java application server as BI Launchpad (http://<server>:<port>/BOE/BI).