Introduction

This document describes the required steps of integrating SAP BusinessObjects into CTS+. The SAP BusinessObject Enterprise is deployed on a NetWeaver stack (instead of the default Tomcat instance). The advantage of using SAP NetWeaver for the Java instance, is that there is no need for an additional NetWeaver instance to run LCM (as required when running e.g. Tomcat). The systems are based on UNIX.

For information on how to setup CTS+ in SAP Solution Manager, see: http://help.sap.com/saphelp_nw70ehp2/helpdata/en/bb/6fab6036a146baa58e42fac032ab7b/content.htm

Technical Scenario

Picture 1 gives an overview of the components and systems used to setup the integration.

Picture 1 – Overview

Note: SAP BusinessObject (BOE) has been deployed on NetWeaver. This means that no additional SAP NetWeaver Java (CE) instance is required. In case SAP BOBI is deployed on a non NetWeaver instance, an additional SAP NetWeaver Java instance is required to enable the CTS integration. How to deploy the BOE on a NetWeaver instance, see http://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=235801055.

SAP BusinessObjects Business Intelligence (BOBI): JBD (Development), JBT (Test), JBA (Acceptance), JBP (Production)
SAP Business Warehouse: ABD (Development), ABT (Test), ABA (Acceptance), ABP (Production)
SAP Solution Manager: DSP (Production)

In this scenario SAP Solution Manager will be the domain controller of the SAP BusinessObjects transport landscape. The system will also function as communication system for transportation.

Creating required users

Table 1 gives an overview of the users required on the different environments (user names can be chosen freely):

System	Client	Username	Type	Role/Authorizations	Remarks
SAP Solution Manager	Prod	CTSADM	system	SAP_CTS_PLUS	https://service.sap.com/sap/support/notes/1003674
SAP BW Development	Prod	C_BO_COM	system	RFC AUTH, BW AUTH

Table 1 – Users

Configuration SAP BusinessObjects

SAP BOBI Development

The following actions are required on the SAP BusinessObject Development server:

Log on to the BO Development system with <sid>adm.
Go to the root directory (/usr/sap/<SID>/sap_bobj/enterprise_xi40).
Create 2 files (make sure the files are created as stated below):
- touch ‘\LCM\LCM_SID_RFC_MAPPING’
- touch ‘\LCM\LCM_SOURCE_CMS_SID_MAPPING’
Enter the following information into the file \LCM\LCM_SID_RFC_MAPPING
- edit ‘\LCM\LCM_SID_RFC_MAPPING’
  - <BW Development ID>=<RFC Destination Name>
Starting from FixPack 11:
- mkdir LCM
- cd LCM
- touch LCM_SID_RFC_MAPPING
- touch LCM_SOURCE_CMS_SID_MAPPING

Example: ABD=ABD.RFC

Enter the following information into the file \LCM\LCM_SOURCE_CMS_SID_MAPPING’
- edit ‘\LCM\LCM_SOURCE_CMS_SID_MAPPING’
  - <SAP BOBI Development (full qualified) hostname>@<CMS port>=<SID as specified in TMS>
  - <SAP BOBI Development IP Address>@<CMS port>=<SID as specified in TMS>

Example: srvpd512.name.ext@6400=JBD

10.210.12.34@6400=JBD

Start the SAP NetWeaver Administrator
Configuration –> Infrastructure –> Destination –> Create…
- Enter the following information:
  - Hosting System: Local Java System <SID>
  - Destination Name: sap.com/com.sap.tc.di.CTSserver
  - Destination Type: RFC
  - Load Balancing : No (in case additional application servers are used, select Yes)
  - Target Host: Full qualified hostname of SAP Solution Manager
  - System Number: Instance number of SAP Solution Manager
  - System ID: System ID of SAP Solution Manager
  - Gateway Host: Full qualified hostname of SAP Solution Manager
  - Gateway Service: sapgw<instance number of SAP Solution Manager>
  - Authentication: Technical User
  - Language: Preferred language
  - Client: SAP Solution Manager Client
  - User Name: ctsadm (see table 1)
  - Password: Password

Example: Local Java System JBD

sap.com/com.sap.tc.di.CTSserver

RFC

srvpd511.name.ext

DSP

srvpd511.name.ext

sapgw00

Technical User

100

ctsadm

password01

Test and save the RFC Destination
Create a second RFC Destination.
- Create a RFC destination to the Business Warehouse Development System
- Enter the following information:
  - Hosting System: Local Java System JBD
  - Destination Name: <System ID BW Development>.RFC
  - Destination Type: RFC
  - Load Balancing : No (in case additional application servers are used, select Yes)
  - Target Host: Full qualified hostname of BW Development
  - System Number: Instance number of BW Development
  - System ID: System ID of BW Development
  - Gateway Host: Full qualified hostname of BW Development
  - Gateway Service: sapgw<instance number of BW Development>
  - Authentication: Technical User
  - Language: Preferred language
  - Client: BW Development Client
  - User Name: C_BO_COM (see table 1)
  - Password: Password

Example: Local Java System JBD

ABD.RFC

RFC

srvpd510.name.ext

ABD

srvpd510.name.ext

sapgw30

Technical User

100

C_BO_COM

password01

Configuration SAP Solution Manager

The following steps must be performed in SAP Solution Manager ABAP:

Log on to SAP Solution Manager
Start transaction SE38 and execute (F8) program RSTMS007
Enter the value *CTSBOLMAN42 in the key field and execute (F8)
The message “the entry exists now” shows in the left lower corner

Start transaction STMS –> Overview –> Systems
Click Extras –> Application Types –> Configure
Enter the following information:
- Application Type: BOLM
- Description: LCM and CTS+ integration
- Support Details: http://service.sap.com (ACH: BOJ-BIP-DEP)
Save the information

Define the SAP BusinessObjects TMS Systems

Start transaction STMS
Define the SAP Business Objects Development system as an export system
SAP System –> Create –> Non-ABAP System

Note: Use the SID as mentioned in the file ‘\LCM\LCM_SOURCE_CMS_SID_MAPPING’

Enter the following information:
- System: SID
- Description: SAP BOBI Development
- Name: SAP Solution Manager SID
- Activate Transport Organizer: Check

Example: JBD

SAP BOBI Development

DSP

Tick checkbox “Activate Transport Organizer”

Save your entries and distribute your changes

Define your Test, Accptance and Production SAP BusinessObject Servers as import systems
SAP System –> Create –> Non-ABAP System
Enter the following information:
- System: SID
- Description: SAP BOBI Test
- Name: DSP
- Activate Deployment Service: Check
- Check Other (deselect all other options)

Example: JBT / JBA / JBP

SAP BOBI Test

DSP

Tick checkbox “Activate Deployment Service”

Tick checkbox “Other”

Save your entries and distribute the changes

The import settings screen appears, choose Edit –> New Entries
Enter the following information:
- Application Type: BOLM
- Deploy method: application-specific Deployer (EJB)
- Deploy URI: <http://<SAP BusinessObjects BI web server host>:<webserver port>/BOE/LCM/CTSServlet?&cmsName=<SAP BusinessObjects BI platform destination name:CMSport>&authType=<SAP BusinessObject BI Platform Authentication type>
- User: <SID~Client>\<User-ID>
- Password: <Password>

Example: BOLM

Application-specific Deployer (EJB)

http://srvpd520.name.ext:52000/BOE/LCM/CTSServlet?&cmsName=10.218.10.63:7400&authType=secSAPR3

ABT~100\USERID

Password01

Save your entries and distribute your changes
Repeat these steps in case you need more import (target) systems.

Define the SAP BusinessObjects TMS landscape

Define a transport route between the system as shown in picture 2 (Transaction STMS –> Overview –> Transport Routes)

Picture 2 – STMS Transport route

Configuration SAP Business Warehouse

SAP Business Warehouse Development

To check dependencies between Business Warehouse objects, users need to be defined. These users need to have the same name in SAP Business Warehouse and in SAP BusinessObjects LCM (Development). At least the authorizations RFC AUTH and BW AUTH are required.

SAP Business Warehouse Test, Acceptance and Production

Define users with the same name in SAP Business Warehouse and SAP BusinessObjects. No special authorizations are required.