Release 1.1.0 of the SAP IDM connector for SAP BusinessObjects BI Platform is now available for SAP IDM 8.0 and 7.2. Following up on my earlier post from SAP IDM 7.2, I’ll explain the installation step-by-step for SAP IDM 8.0.
Download and install SAP BI platform Java SDK
The prerequisites for installing the connector on SAP IDM 8.0 are exactly the same as for SAP IDM 7.2. Hence, it requires the following JAR files from SAP’s BI platform Java SDK:
aspectjrt.jar bcm.jar ceaspect.jar cecore.jar celib.jar cesession.jar corbaidl.jar cryptojFIPS.jar ebus405.jar log4j.jar logging.jar TraceLog.jar
Copy these into a directory on the SAP IDM runtime. As usual, I’ll assume you’ll use C:\IDM_BOBJ_LIBS on the SAP IDM runtime. For details regarding where to obtain the SDK and how to extract the required JAR files, please refer to Download and install SAP BI platform Java SDK of the 7.2 version.
Add SDK JARs to SAP IDM dispatcher classpath
To make the SDK JARs visible from SAP IDM, add them to the dispatcher’s Java class path. On the SAP IDM runtime, start the Identity Management Dispatcher Utility in GUI mode using the command
Open the Dispatcher Utility’s settings dialog using Tools -> Settings. Add all SDK JAR files listed above to the setting DSE Class Path. Defining the Settings for the Identity Management Dispatcher Utility in the SAP Help Center has all the details.
After saving your changes, regenerate the service scripts for all dispatchers and restart them.
Download connector and import IDM package
Use SAP Identity Management Developer Studio to connect to the IDM database. As the SAP BusinessObjects connector depends on package com.sap.idm.provisioning.engine that comes with SAP IDM 8.0, you’ll need to import that first if you haven’t already done so.
Download the latest stable connector release from https://github.com/foxysoft/idm-connector-bobj/releases/latest to the machine where SAP IDM Developer Studio is installed, and unzip idm-connector-bobj-<VERSION>.zip. It contains an IDM package file de.foxysoft.bobj.idmpck. Use SAP IDM Developer Studio to import that into your main Identity Store.
When prompted for an import reason, make sure you keep the default option “Import” selected. Don’t use “Import as new package”. Confirm the import using “OK”.
Create a SAP IDM repository
Open the SAP Identity Management administration UI at http://<host>:<port>/idm/admin in a web browser and create a new repository of type SapBusinessObjects42. This repository type is part of the SAP BusinessObjects connector package.
After the repository has been created, change repository constants HOST, LOGIN, PASSWORD and PORT as appropriate for your environment. Please refer to Import SAP IDM repository and initial load job in the 7.2 version for additional information on how to find out CMS host name and name server port.
Execute initial load and finalize repository configuration
Select the “Jobs” tab of the repository details view. A new job SAP BOBJ 4.2 – Initial Load has been created and assigned to the repository automatically. Execute this job now to load SAP BusinessObjects groups into SAP IDM.
This job should take a few minutes only to execute. Use “Refresh” to verify that the job has finished successfully, then open the SAP Identity Management UI at http://<host>:<port>/idm to verify that privileges from SAP BusinessObjects have been loaded.
As a final step, you may go back to the SAP Identity Management administration UI and update repository constant MX_REQ_PRIV with the master privilege just created by the initial load. In this example, that’s PRIV:BOE:ONLY.
If you have a suitable No Master Process to assign missing master privileges automatically, assign that to repository constant MX_REQ_PRIV_NOMASTER_TASK. In my screenshot below, this process reference is not set (-1 means “None”).
That’s it. You’re ready to manage all your SAP BusinessObjects Enterprise users and groups from SAP IDM 8.0 now. If you’re interested in learning more about this connector, visit its GitHub project, which also contains a small Wiki with additional resources.