sap solman bo integration

Download SAP SolMan BO Integration

Post on 27-Dec-2015

54 views

Category:

Documents

0 download

Embed Size (px)

DESCRIPTION

SOLMAN

TRANSCRIPT

  • Ingo Hilgefort

    Integrating SAP BusinessObjects Lifecycle Manager with CTS+

    from

    Integrating SAP Business Objects BI Platform 4.x with SAP Netweaver

    Bonn Boston

    ch15_ONLINE_6157.indd 1 3/28/12 2:46 PM

  • 1 2012 by Galileo Press Inc., Boston (MA)

    In this chapter we review the new integration of SAP Business Objects Lifecycle Manager with the enhanced change and transport system (CTS+) from SAP NetWeaver.

    15 Integrating SAP BusinessObjects Lifecycle Manager with CTS+

    As part of the SAP Business Objects BI 4.x release, the SAP Business Objects Lifecycle Manager has been integrated with the enhanced change and transport environment (CTS+), so that you as an administrator can leverage a familiar environment to move content-related objects from you development system to your quality system, and finally to your production environment.

    In this chapter, we will clarify the technical prerequisites for this integration and then show you how to configure the environments so that you can take advantage of this integration as part of your SAP Business Objects BI landscape.

    Overall this integration requires three main steps:

    1. Configuration of CTS+.

    2. Configuration of BOLM as an application type.

    3. Configuration of your SAP Business Objects BI environment.

    15.1 Technical Prerequisites

    If you are considering using this new integration of SAP Business Objects Lifecycle Manager and CTS+, these are the minimum system requirements:

    EE SAP Solution Manager 7.01 Service Pack 25 or SAP Solution Manager 7.1 con-figured as a CTS system.

    ch15_ONLINE_6157.indd 1 3/28/12 2:46 PM

  • 2 2012 by Galileo Press Inc., Boston (MA)

    EE The CTS plug-in installed on the SAP Solution Manager environment.

    EE SAP Business Objects BI 4.0 Feature Pack 03 (FP3).

    SAP Business Objects BI 4.0 (prior to FP3)

    The integration outlined below is also possible with SAP Business Objects BI 4.0, before the release of FP3, but the configuration steps are different. This chapter focuses on the FP3 release.

    Figure 15.1 shows the required components for this integration and the process flow. As you can see from the figure, the following is required:

    EE You need an SAP Business Objects BI 4.0 FP3 environment. Ideally, you have one environment for development purposes, one for quality testing, and one for the production environment. In Figure 15.1, these environments are BI4_DEV, BI4_QA, and BI4_PROD.

    EE In addition, you need access to the SAP NetWeaver BW environment. Again, you should have one environment for development purposes, one for quality testing, and one for the production environment. In Figure 15.1, these environ-mets are BW_DEV, BW_QA, and BW_PROD.

    EE You also need to have an environment where the SAP Business Objects Lifecycle Manager frontend application is deployed. The SAP Business Objects Lifecycle Manager frontend application requires a Java application server. Please be sure to check the list of supported Java application servers at http://service.sap.com/bosap-support. In Figure 15.1, this system is shown as LCM_1.

    EE You also need a SAP Solution Manager environment with a configured CTS plug-in. The CTS plug-in is part of the Software Logistics (SL) Toolset 1.0 service pack 02. You can use either SAP Solution Manager 7.1 in combination with the SL Toolset 1.0 service pack 02 or the SAP Solution Manager 7.0 enhancement pack-age 01 service pack 25 with the SL Toolset 1.0 service pack 02. In Figure 15.1, this system is shown as Solution Manager.

    ch15_ONLINE_6157.indd 2 3/28/12 2:46 PM

  • 3 2012 by Galileo Press Inc., Boston (MA)

    Solution Manager

    LCM WebApplicationLCM_1

    SBOP BI 4.xDEVELOPMENT

    BI4_DEV

    SAP NetWeaver BWDEVELOPMENT

    BW_DEV

    SBOP BI 4.xQUALITYBI4_QA

    SAP NetWeaver BWQUALITYBW_QA

    SBOP BI 4.xPRODUCTION

    BI4_PROD

    SAP NetWeaver BWPRODUCTION

    BW_PROD

    Figure15.1 Required Components for the Integration of CTS+ and SAP Business Objects Lifecycle Manager

    When you use the SAP Business Objects Lifecycle Manager frontend and select the objects from your SAP Business Objects BI system, you are given the option to leverage the CTS+ integration and move the selected content in the form of ABAP transports. The SAP Business Objects Lifecycle Manager frontend tool collects the objects from the SAP Business Objects BI system (1) and uses the interface to the CTS system to add the selected objects to an ABAP transport request (2). After the transport request has been exported to the SAP NetWeaver BW system (3), you are able to release the transport request (4), and the objects are imported into the SAP Business Objects BI system (BI4_QA).

    Important Notes on the Lifecycle Manager Integration

    In regard to the configuration and installation of the integration of SAP Business Objects Lifecycle Manager with CTS+, you can also see the following notes for important information:

    EE SAP Note 1533059 for installing the SL Toolset

    EE SAP Note 1003674 for CTS+

    EE SAP Note 1533059 for the CTS plug-in

    Notes can be viewed at http://service.sap.com/notes.

    ch15_ONLINE_6157.indd 3 3/28/12 2:46 PM

  • 4 2012 by Galileo Press Inc., Boston (MA)

    In this section we reviewed the minimum system requirements to leverage SAP Business Objects Lifecycle Manager integrated with CTS+. In the next section we will go through the required confi guration steps.

    15.2 Configuration Steps to Integrate SAP Business Objects Lifecycle Manager with SAP CTS+

    In this section we will cover the required confi guration steps to integrate SAP Business Objects Lifecycle Manager (LCM) with SAP CTS+.

    15.2.1 Configuration of CTS+

    As part of the confi guration of the Solution Manager as a CTS system, an RFC con-nection is required to communicate between the ABAP and Java application server.

    To confi gure the RFC communication:

    1. Log on to the client of the Solution Manager system.

    2. Start Transaction SM59.

    3. Navigate to the HTTP Connections area (see Figure 15.2).

    Figure15.2 RFC Connections

    ch15_ONLINE_6157.indd 4 3/28/12 2:46 PM

  • 5 2012 by Galileo Press Inc., Boston (MA)

    4. Make sure you check that the HTTP connection CTSDEPLOY already exists. If it does not exist, continue with these steps. If it exists, you can use the menu Edit Change to change the existing confi guration.

    5. Select the menu Edit Create.

    6. Enter CTSDEPLOY as RFC Destination (see Figure 15.3).

    7. Select the Connection Type G (see Figure 15.3).

    8. Enter the full qualifi ed server name of the Java application server from the SAP Solution Manager system into the Target Host fi eld.

    9. Enter the port number of the Java application server from the SAP Solution Manager system into the Service No fi eld.

    Figure15.3 RFC Connection Details

    10. Navigate to the Logon & Security tab (see Figure 15.4).

    ch15_ONLINE_6157.indd 5 3/28/12 2:46 PM

  • 6 2012 by Galileo Press Inc., Boston (MA)

    Figure15.4 Logon & Security Tab

    11. Select the Basic Authentication option.

    12. Enter a set of credentials with corresponding administrative rights on the Java application server from the SAP Solution Manager system.

    13. Navigate to the Special Options tab (see Figure 15.5).

    Figure15.5 Special Options

    ch15_ONLINE_6157.indd 6 3/28/12 2:46 PM

  • 7 2012 by Galileo Press Inc., Boston (MA)

    14. Activate the No Timeout option.

    15. Select the menu Connection Save.

    16. Click the Connection Test button. You should receive an HTTP Response 200 as result.

    For communication between the ABAP application server and the Java application server of your Solution Manager system, there needs to be a confi gured commu-nication port.

    To confi gure the communication port:

    1. Log on to the client 000 of the Solution Manager system.

    2. Start Transaction LPCONFIG.

    3. Enter CO_TFLDEPLOY_PROXY_VI_DOCUMENT into the Proxy Class fi eld.

    4. Enter CTSDEPLOY into the Logical Port fi eld (see Figure 15.6).

    Figure15.6 Logical Port

    5. Select the menu Logical Port Create.

    6. Activate the Default Port option.

    7. Navigate to the Call Parameter tab.

    8. Enter CTSDEPLOY into the HTTP Destination fi eld.

    9. Enter DeployProxy/default?style=document into the Path Suf x fi eld.

    10. Select the menu Logical Port Save.

    11. Select the menu Logical Port Activate.

    To get detailed information about transport requests, you need to use a Web Dynpro application provided by CTS, called the Object List Browser. You have to activate a set of services to enable this application. You can fi nd more details in SAP Note 517484.

    ch15_ONLINE_6157.indd 7 3/28/12 2:46 PM

  • 8 2012 by Galileo Press Inc., Boston (MA)

    To confi gure the services:

    1. Log on to the client of the Solution Manager system.

    2. Start Transaction SICF.

    3. Enter Service in the Hierarchy Type fi eld.

    4. Enter CTS_BROWSER in the Service Name fi eld (see Figure 15.7).

    Figure15.7 Service Maintenance

    5. Select the menu Program Execute.

    6. Select the service CTS_BROWSER.

    7. Right-click the service CTS_BROWSER and select the menu Activate Service.

    8. Click Yes to activate the service.

    9. Start Transaction SICF again.

    10. Enter Service in the Hierarchy Type fi eld.

    11. Enter CTS_OBJECTLIST_BROWSER in the Service Name fi eld.

    12. Select the menu Program Execute.

    13. Select the service CTS_OBJECTLIST_BROWSER.

    14. Right-click the service CTS_OBJECTLIST_BROWSER and use the menu Activa