Request for existing cases, user IDs, Portal navigation support and more
This page explains how to prepare a SAP BusinessObjects managed system for the execution of the Simple System Integration
Currently the following monitoring application are supported for SAP BusinessObjects systems:
The automatic configure (AC) Tool coming with SAP Solution Manager, is used to prepare different products for SSI. This tool can save considerable time by performing a few steps in the managed system host automatically. These include, for example, automation and, as the case may be, repeated invocations such as LAMA integration, any SAP product SAP Focused Run Installation and configuration integration, such as SAP BusinessObjects BI Platform and SAP Data Services.
For more information, see SAP Note 2137275 - AC Tool release note.
AC Tool supports the following:
AC Tool embeds:
Background:
The C++ process with NCS library sends data to the Diagnostics Agent (via NCS port) and then stores metrics locally, which are forwarded to the solution based on MAI configuration.
In the AC Tool property file, placeholders for NCS (C++) have to be maintained, which define to which ports the processes send their data. In the case of dual operations, you can also add multiple ports in the configuration ncs.conf, (SAP Focused Run and SAP Solution Manager in parallel).
| Task | Actions |
|---|---|
Install SAP BusinessObjects BI Platform 4.0 or higher. SAP BusinessObjects BI platform is also known as SAP BOBI platform or SBOP. |
|
| Install latest BCI Adapter | None, delivered with the SAP BusinessObjects BI Platform product installation |
| Install Data Supplier | None, delivered with the SAP BusinessObjects BI Platform product installation |
| Configure BusinessObjectsEnterpriseSystem Data Supplier to send BusinessObjects BI Platform information | None, done using the SAP Solution Manager AC Tool Automated using AC Tool, Can be performed manually /usr/sap/hostctrl/exe/sldreg -configure /usr/sap/hostctrl/exe/connect.key |
| Check if an SLDR is needed | As prerequisites, you need to choose, according to your landscape, if an SLDR is required see Preparing System Landscape Data Router page. |
| Send the Data Supplier Payload | None, done using SAP Solution Manager AC Tool Logs: /usr/sap/<SID>/sap_bobj/enterprise_xi40/java/lib/bobj-sld-ds/<hostname>bobjsldds.log Automated using AC Tool Can be performed manually /usr/sap/hostctrl/exe/sldreg -connectfile /usr/sap/hostctrl/exe/connect.key -file /usr/sap/<SID>/sap_bobj/enterprise_xi40/java/lib/bobj-sld-ds/<hostname>_bobjslddsoutput.xml |
Run Outside Discovery on the Host The SAP BusinessObjects BI Platform needs to be associated to a Database listed in the "Database Managed Object Preparation" section. | As prerequisites, you shall install the SAP Host Agent and run Outside Discovery as described in Preparing Outside Discovery page. |
| Add both Installation Number and System Number Parameter in LMDB | The SAP BO BI Platform Installation Number and System Number needs to be collected manually from the SAP for Me license key application (Details Section). From LMDB, select the SAP BusinessObjects Cluster Technical System. Edit and Add in the "SAP Support Portal TAB" the Installation Number, System Number and Save. Verify the information by clicking on the System Number Key, this redirect to SAP for Me. |
| Assign Database Information from LMDB | From LMDB, select the SAP BusinessObjects Cluster Technical System. Select "System Database" in the Navigation Tree. Edit and Assign System Database of the Cluster and Save. |
| Create a Technical User | Create a Custom Monitoring Technical User to enable tracing (TA), monitor data collection (SYSMON), and configure store snapshotcreations (configuration and security analytics administration) as described in the Security Guide. |
| Check LMDB | Optional operation From the LMDB (Technical System view), check the last data changes from the data supplier. Check the Software / Product Instance and Software Component Version sections, to see what has been reported by the Data Supplier. |
| Check SSI “Edit Configuration” | Fill in the missing parameters. For Instance, NCS Port (NCS monitoring Metrics): 6404
|
| Task | Actions |
|---|---|
| Run Outside Discovery on the Host | As prerequisites, you shall install the SAP Host Agent and run Outside Discovery as described in Preparing Outside Discovery page. |
| Install Apache Tomcat7 or higher | Check Online Installation Guide |
| Install latest BCI Adapter | None, done using SAP Solution Manager AC tool (see above) Automated using AC Tool (can be performed manually) |
| Install Tomcat Data Supplier | None, done using SAP Solution Manager AC tool (see above) Automated using AC Tool. Can be performed manually. See SAP Note 1508421 SAP SLD DS for Apache Tomcat for details. |
| Check if an SLDR is needed | As prerequisites, you need to choose, according to your landscape, if an SLDR is required see Preparing System Landscape Data Router page. |
| Configure Data Supplier | None, done using SAP Solution Manager AC tool (see above) (Trigger sld data supplier, deployed by Tomcat. Launched by AC Tool http:// <managed host>:<managed port>/sap.com~TomcatSLDDataSupplierWEB/sldsupplier?action=displayConfig) |
| Send the Data Supplier Payload | None, done using SAP Solution Manager AC Tool (see above) Can be performed manually: hostctrl/exe/sldreg -connectfile hostctrl/exe/connect.key -file /<SID>/sap_bobj/tomcat/webapps/sap.com~TomcatSLDDataSupplierWEB/atcsld_<latest timestamp>.xml This triggers the data transfer immediately |
| Check LMDB | Optional Operation From the LMDB (Technical System view), check the last data changes from the data supplier. Check the Software / Product Instance and Software Component Version sections, to see what has been reported by the Data Supplier. |