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:

  1. First step: Create a source system in BI. How to connect Galaxy to BI? (this document)
  2. Second step: Create data sources.

After following above documentation you will be able to setup process analytics in BPM.

How to connect Galaxy to BI?

Prerequisites

First, the process analytics components have to be installed. They get deployed with the BPEM- SCA. Secondly, you need a BI system.

Create your user account in the BI system

You need first a user in order to access the BI system. The systems dispose of some pre-defined users for accessing them but the permissions assigned to them are restricted and those users cannot be used to perform the operations required to setup a connection. The screenshots below describe the steps for creating rapidly a user in a BI system:
/wp-content/uploads/2015/01/fig_1_620571.jpg
  1. Login to the BI system with the default user
  2. Run the transaction SU01.
  3. Enter the name of an existing user that will taken as reference to create your user account.
  4. Click on the Copy button in the toolbar.

/wp-content/uploads/2015/01/fig_2_620575.jpg
  1. Enter in the To field the login ID of your new user. Keep the selection of the checkboxes as it is.
  2. Click on the Copy button in the bottom of the window to create the user.
ℹ It might happens that the reference user has some profiles or permissions which cannot be copied to your user. You will then see a            screen notifying  you which element could not be copied in your new user account. Simply ignore the message and continue.
  3.  Fill the missing user information, especially the credentials in the login tab, and save your changes. Log off and login to the BI system with your new       user account. It might request the first time to change the credentials.

Request rights for BI user

The user you created might not have all the permissions required to setup a connection. The following steps explain how to check the permissions assigned to the user and how to request for the missing ones.
Tips for permissions and profiles
To know exactly which permissions/profiles you need to request, use the transaction SU53. The transaction lists all the profiles your user does not have but which were required for the operations/transactions you tried to run.

/wp-content/uploads/2015/01/fig_3_620580.jpg
  1. Login to the BI system with your user account and run the transaction SU01.
  2. Enter the login of your user in the User field and press the F7 key or the Display icon in the toolbar.
  3. Go into the Profiles tab and check if the profile S_RS_ALL is in the list. If it is not, then open an IT/BC ticket on the component DEV-BICONT-USER and
    request that the profile
    S_RS_ALL be added to your user account.
/wp-content/uploads/2015/01/fig_4_620581.jpg

Configure NetWeaver/CE to connect to the BI system

The connection between Galaxy and the BI system is done through the gateway of the BI system. Galaxy should first connect to the gateway and register this connection.
/wp-content/uploads/2015/01/fig_5_620585.jpg
  1. Enter SapJavaResourceAdapter15 in the resource name filter.
  2. Select the resource from type Resource Adapter with the name SapJavaResourceAdapter15.
       ❗    Do not select the resource from type JCA Resource with the same name!
   3. Select the Properties tab.
   4. Fill the missing informations and update the others like in the screenshot:
    • The ProgramID is used to identify the connection between Galaxy and the gateway of the BI system.
                           ℹ Keep this name in mind because it will be required when you will configure in the next step the TCP/IP connection in the BI system.
    • The MaxReaderThreadCount property 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.
    • The SAPClient is the client ID used to login to the BI system. Usually, the client ID is 001 but it is not systematic. For example Q76 is      accessed with the client ID 003. Normally the system indicates which client ID should be used in the login page.
    • The UserName should be the login ID of the user you created in the BI system.
    • The ServerName property 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).
    • The PortNumber property 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.

    

     /wp-content/uploads/2015/01/fig_6_620586.jpg


Create TCP/IP Connection in the BI system

Now that Galaxy registered a connection in the gateway, the BI system can connect to this connection. Actually, it connects to the gateway and specifies the ID of the connection (i.e. the program ID).

/wp-content/uploads/2015/01/fig_7_620588.jpg
  1. Run the transaction SM59 (transaction for managing the RFC connections to the BI system).
  2. Select the node TCP/IP Connection.
  3. Click on the Create button in the toolbar.

/wp-content/uploads/2015/01/fig_8_620589.jpg

  1. 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.
  2. Select the option Registered Server Program.
  3. Enter the program ID defined in the previous step.
  4. Enter the gateway hostname and the gateway service of the BI system. The gateway server is sapgw followed by the system number of the BI system. For example, the gateway service for Q76 is sagw29.
  5. Save your changes.
  6. Test your connection. If the connection cannot be successfully tested, ensure first that you restarted your NetWeaver system after configuring the SapJavaResourceAdapter15  resource adapter.

Create Source System

So that BI can access to the data sources and the data exposed by Galaxy, a source system needs to be created.

/wp-content/uploads/2015/01/fig_9_620590.jpg
  1. Start the transaction RSA1 (Data Warehouse Workbench).
  2. Select Source Systems.
  3. Select the node UD Connect, open the contextual menu with a right mouse click and click on Create.

/wp-content/uploads/2015/01/fig_10_620594.jpg

  1. Enter the name of the RFC connection you created in the previous step.
  2. Enter a logical name for the source system.
  3. Select SDK-JAVA in the pop-up.
  4. Enter a name for the source system.
  5. Enter BPM720 in the field Type and Release if you connected a Galaxy system from the 7.20 release to the BI system.

              ℹ   The Type and Release field is used by Galaxy’s BI connector to determine the structure of the data sources.


/wp-content/uploads/2015/01/fig_11_620596.jpg
  1. Select the data source you created and open the context menu with a right click.
  2. Click on Check. The result will be displayed in the status bar.

/wp-content/uploads/2015/01/fig_12_620597.jpg


     
    

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply