Many customers have asked about the exact steps to setup process analytics in BPM. To complement help and to avoid incident creation I will provide here the steps to do it. We have divided them in 2 steps:
- First step: Create a source system in BI. How to connect Galaxy to BI? (this document)
- Second step: Create data sources.
- Either with How to install BI initial content for Galaxy?
- Or with How to setup Process Analytics? Part 3/3 – How to create manually data sources?
After following above documentation you will be able to setup process analytics in BPM.
How to connect Galaxy to BI?
BPEM-SCA. Secondly, you need a BI system.
Create your user account in the BI system
- Login to the BI system with the default user
- Run the transaction
- Enter the name of an existing user that will taken as reference to create your user account.
- Click on the Copy button in the toolbar.
- Enter in the
Tofield the login ID of your new user. Keep the selection of the checkboxes as it is.
- Click on the Copy button in the bottom of the window to create the user.
Request rights for BI user
SU53. The transaction lists all the profiles your user does not have but which were required for the operations/transactions you tried to run.
- Login to the BI system with your user account and run the transaction
- Enter the login of your user in the
Userfield and press the
F7key or the Display icon in the toolbar.
- Go into the Profiles tab and check if the profile
S_RS_ALLis in the list. If it is not, then open an IT/BC ticket on the component
request that the profile
S_RS_ALLbe added to your user account.
Configure NetWeaver/CE to connect to the BI system
SapJavaResourceAdapter15in the resource name filter.
- Select the resource from type Resource Adapter with the name SapJavaResourceAdapter15.
ProgramIDis used to identify the connection between Galaxy and the gateway of the BI system.
MaxReaderThreadCountproperty can be set to a small number 2-5 (best pratice till now). The number could be calculated knowing the amout of RFC (pull) requests which might arrive from BW side in the same timeframe – the more InfoProviders scheduled to run in parrallel in BW the,more JCo server threads should be configured for accepting these requests. The reason is that the execution within BPM might cause some of the RFC requests to be denied by the JCo server resulting in errors at BW side.
SAPClientis the client ID used to login to the BI system. Usually, the client ID is 001 but it is not systematic. For example
Q76is accessed with the client ID 003. Normally the system indicates which client ID should be used in the login page.
UserNameshould be the login ID of the user you created in the BI system.
ServerNameproperty should be set with the hostname of the BI system gateway also known as message server. If you chose a system from the table above, the hostname of the gateway is given in the table. Otherwise, you can determine it with the SAP Logon UI (See point 1 in screenshot below).
PortNumberproperty should be set with the system number of the BI system. If you chose a system from the table above, the system number is given in the table. Otherwise, you can determine it with the SAP Logon UI (See point 2 in screenshot below).
5. Save finally your changes and restart your server.
Create TCP/IP Connection in the BI system
- Run the transaction
SM59(transaction for managing the RFC connections to the BI system).
- Select the node TCP/IP Connection.
- Click on the Create button in the toolbar.
- Enter first a name for the new RFC connection. You will need to enter this name when you will create the data source in the next step.
- Select the option Registered Server Program.
- Enter the program ID defined in the previous step.
- Enter the gateway hostname and the gateway service of the BI system. The gateway server is
sapgwfollowed by the system number of the BI system. For example, the gateway service for
- Save your changes.
- Test your connection. If the connection cannot be successfully tested, ensure first that you restarted your NetWeaver system after configuring the
Create Source System
- Start the transaction
RSA1(Data Warehouse Workbench).
- Select Source Systems.
- Select the node UD Connect, open the contextual menu with a right mouse click and click on Create.
- Enter the name of the RFC connection you created in the previous step.
- Enter a logical name for the source system.
SDK-JAVAin the pop-up.
- Enter a name for the source system.
BPM720in the field
Type and Releaseif you connected a Galaxy system from the 7.20 release to the BI system.
Type and Release field is used by Galaxy’s BI connector to determine the structure of the data sources.
- Select the data source you created and open the context menu with a right click.
- Click on Check. The result will be displayed in the status bar.