stillenglish.blogg.se - Sap business intelligence platform

SAP BUSINESS INTELLIGENCE PLATFORM HOW TO
SAP BUSINESS INTELLIGENCE PLATFORM PASSWORD

You will be asked the password of the keystore (the password for sampletestKeystore.jks is Password1) and further details.

Define the alias (we used analias in the example above), give it a password (we used Password1) and chose a pre-existing keystore to generate it (we used the sampletestKeystore.jks).

Keytool -genkeypair -alias analias -keypass Password1 -keystore "D:\Program Files (x86)\SAP BusinessObjects\tomcat\webapps\BOE\WEB-INF\sampletestKeystore.jks" -validity 735

Launch a command line shell and navigate to \SAP BusinessObjects Enterprise XI 4.0\win64_圆4\sapjvm\bin and execute the command below:.

Locate \tomcat\webapps\BOE\WEB-INF\ web.xml and uncomment the SAML parameters:.

At this point BI and BILaunchpad should be inaccessible.

\tomcat\webapps\BOE\WEB-INF\config\custom\ FioriBI.properties.\tomcat\webapps\BOE\WEB-INF\config\custom\ BILaunchpad.properties.Locate (or, if they do not exist, create) the files below, and make sure the property enabled=true is configured in both:.\tomcat\webapps\BOE\WEB-INF\ securit圜ontext.xml Save the changes but you can keep this file open as we will return to it later. The line for the classic BI Launchpad was already uncommented. In the case below, we have removed the leading “” from OpenDocument and BILaunchpad (this is the “fiorified” one). Create a backup copy of the file below, and edit the original to uncomment the apps you want to use.Come back to configure CMC only after you have gone through all configuration steps and tested that it works, otherwise you may find yourself locked out of the CMC. If you are on 4.2 SP06, and want to include CMC in the SAML SSO, do not configure it now.

Note: the changes below will make the BI and BILaunchpad apps inaccessible. \SAP BusinessObjects Enterprise XI 4.0\SAMLJARS\

Restart tomcat and make sure you can connect to tomcat using Note: myserver here is the name of the host where tomcat is installed.

Note: thisAlias, C:\keystore\thisKeystore and thisKeystorePassword will need to match the values you used in the previous step To do that, uncomment it and change it to look like this:

Locate \tomcat\conf\ server.xmland create a backup of the file, then edit it to enable the https connector.

Please note thisAlias and C:\keystore\thisKeystore should be changed to reflect your organisation’s naming conventions, and you will need to create a password and fill out details for like company name, state, etc.

Keytool -genkey -alias thisAlias -keyalg RSA -keystore C:\keystore\thisKeystore -keysize 2048 To go with the self-signed certificate, run the command below, which will create a keystore and alias: If your deployment is already configured for HTTPS, you can skip this step otherwise, you can contract a third-party certificate authority, or create a self-signed certificate (which will throw a warning in your browser).Not all screenshots were taken from the same system, so some may have been pixelated to avoid confusion. This configuration has been applied to BI 4.2 SP05 and SP06. There are also a few practical suggestions you may find useful. There are some small differences in the order and steps, and this is because we found this approach was most likely to return the expected result as we implemented this in a real World scenario.

SAP BUSINESS INTELLIGENCE PLATFORM HOW TO

There is already a very good guide on how to set this on up, but in here we have emphasized the practical side of the setup and focused on the order the configuration steps should be performed: