how to configure lcm for ctsa248.g.akamai.net/n/248/420835/128f7ec9d82f50298b0681b8d...sap netweaver...

SAP NetWeaver

How-To Guide

How To... Configure LCM for CTS

Applicable Releases:

SAP BusinessObjects BI 4.0 and higher

SAP Solution Manager 7.0 EHP1 SP25 and higher, SAP Solution Manager

7.1, SAP NetWeaver 7.3 including enhancement package 1, or SAP

NetWeaver 7.4

Version 1.3

December 2014

i

© Copyright 2014 SAP SE. All rights reserved.

No part of this publication may be reproduced or

transmitted in any form or for any purpose without the

express permission of SAP SE. The information contained

herein may be changed without prior notice.

Some software products marketed by SAP SE and its

distributors contain proprietary software components of

other software vendors.

Microsoft, Windows, Outlook, and PowerPoint are

registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel

Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390,

OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP,

Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix,

i5/OS, POWER, POWER5, OpenPower and PowerPC are

trademarks or registered trademarks of IBM Corporation.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader

are either trademarks or registered trademarks of Adobe

Systems Incorporated in the United States and/or other

countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered

trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame,

WinFrame, VideoFrame, and MultiWin are trademarks or

registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or

registered trademarks of W3C®, World Wide Web

Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems,

Inc., used under license for technology invented and

implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP

NetWeaver, and other SAP products and services

mentioned herein as well as their respective logos are

trademarks or registered trademarks of SAP SE in

Germany and in several other countries all over the world.

All other product and service names mentioned are the

trademarks of their respective companies. Data contained

in this document serves informational purposes only.

National product specifications may vary.

These materials are subject to change without notice.

These materials are provided by SAP SE and its affiliated

companies ("SAP Group") for informational purposes only,

without representation or warranty of any kind, and SAP

Group shall not be liable for errors or omissions with

respect to the materials. The only warranties for SAP

Group products and services are those that are set forth in

the express warranty statements accompanying such

products and services, if any. Nothing herein should be

construed as constituting an additional warranty.

These materials are provided “as is” without a warranty of

any kind, either express or implied, including but not

limited to, the implied warranties of merchantability,

fitness for a particular purpose, or non-infringement.

SAP shall not be liable for damages of any kind including

without limitation direct, special, indirect, or consequential

damages that may result from the use of these materials.

SAP does not warrant the accuracy or completeness of the

information, text, graphics, links or other items contained

within these materials. SAP has no control over the

information that you may access through the use of hot

links contained in these materials and does not endorse

your use of third party web pages nor provide any warranty

whatsoever relating to third party web pages.

SAP NetWeaver “How-to” Guides are intended to simplify

the product implementation. While specific product

features and procedures typically are explained in a

practical business context, it is not implied that those

features and procedures are the only approach in solving a

specific business problem using SAP NetWeaver. Should

you wish to receive additional information, clarification or

support, please refer to SAP Consulting.

Any software coding and/or code lines / strings (“Code”)

included in this documentation are only examples and are

not intended to be used in a productive system

environment. The Code is only intended better explain and

visualize the syntax and phrasing rules of certain coding.

SAP does not warrant the correctness and completeness of

the Code given herein, and SAP shall not be liable for

errors or damages caused by the usage of the Code, except

if such damages were caused by SAP intentionally or

grossly negligent.

Disclaimer

Some components of this product are based on Java™. Any

code change in these components may cause unpredictable

and severe malfunctions and is therefore expressively

prohibited, as is any decompilation of these components.

Any Java™ Source Code delivered with this product is only

to be used by SAP’s Support Services and may not be

modified or altered in any way.

ii

Document History

Document Version Description

1.3 Information for systems on releases lower than BI 4.0 Feature Pack 3 moved to the Appendix; minor corrections

1.2 Enhancements in Chapter 3 etc. (since CTS Plugin 2.0 SP06 also NW 7.31+ systems may be used as domain controller and/or communication system), chapter 5.1.1 (lpconfig setup), chapter 8.3 (enhanced description of export process), and more details included concerning BI authentication. Changes LCM to Promotion Management and included documentation links to BI 4.0 FP3 and up

1.1 The following enhancements were made to the guide:

Adapted the guide to the new version of CTS Plug-In (2.0 SP02). Screenshots for new Transport Organizer Web UI, links to documentation were updated.

Chapter 7.2.1: Added a graphic to visualize the meaning of the mapping file.

Chapter 7.2.3: Updated screenshots and description for activating the CTS Export Web Service in SOAMANAGER.

Other minor improvements.

1.0 First official release of this guide

iii

Typographic Conventions

Type Style Description

Example Text Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options.

Cross-references to other documentation

Example text Emphasized words or phrases in body text, graphic titles, and table titles

Example text File and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools.

Example text User entry texts. These are words or characters that you enter in the system exactly as they appear in the documentation.

Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system.

EXAMPLE TEXT Keys on the keyboard, for

example, F2 or ENTER.

Icons

Icon Description

Caution

Important

Note

Recommendation or Tip

Example

iv

Table of Contents

1. Scenario ................................................................................................................................ 1

2. Background Information ..................................................................................................... 2

3. Prerequisites ........................................................................................................................ 3

4. Restrictions and Recommendations ................................................................................. 4

5. Basic configuration for CTS ............................................................................................... 5

5.1 Configure the Transport ................................................................................................ 5 5.1.1 Configuring the CTS Deploy Web Service ....................................................... 6 5.1.2 Configuring the Transport Organizer Web UI ................................................ 10

6. Configure BOLM as application type ............................................................................... 13

7. Configure the BI Landscape ............................................................................................. 16

7.1 Configuring the Transport Landscape in TMS ............................................................ 16 7.1.1 Configuring the Development system (Export system) ................................. 16 7.1.2 Configuring the Test and Production System (Import Systems) .................... 20 7.1.3 Transport Landscape: Defining Transport Routes ........................................ 24

7.2 Configuration for Export .............................................................................................. 28 7.2.1 Create a Mapping File on the BI Source System .......................................... 29 7.2.2 Activate the CTS Export Web Service ........................................................... 30 7.2.3 Source System: Connect to CTS Export Web Service .................................. 35

8. Use LCM with CTS ............................................................................................................. 36

8.1 Create a New Job ....................................................................................................... 36 8.2 Add Objects to a Job .................................................................................................. 37 8.3 Promote a Job and Release the Request .................................................................. 37 8.4 Importing a Job ........................................................................................................... 39

8.4.1 Meaning of Return Codes - Reading the Deployment Log-File on CTS side 41 8.5 Advanced Usage of LCM with CTS ............................................................................ 42

8.5.1 Transport Organizer Details ........................................................................... 42 8.5.2 Promoting Overrides ...................................................................................... 45 8.5.3 Tools for managing transports ....................................................................... 45

9. Appendix ............................................................................................................................ 45

9.1 Configuration for systems on releases lower than BI 4.0 Feature Pack 3 ................. 45


December 2014 1

1. Scenario A while ago, the Change and Transport System (CTS) of ABAP has been enhanced so that it can be used for transporting non-ABAP objects as well – known as CTS+ or enhanced CTS. In the remainder of this document, the abbreviation CTS is used for the system where the transport landscapes are configured and for the fact that CTS can also be used for non-ABAP transports.

In this guide, you can find information on how to use CTS together with the Promotion Management Tool (LCM) of SAP BusinessObjects Business Intelligence (BI). This guide shows step by step – including sample screenshots - how the configuration is done. One thing that you can do with the LCM is transporting objects from one Central Management Server (CMS) to another. This can be done with or without CTS. If you already use CTS, e.g. to manage non-ABAP transports for applications like the SAP NetWeaver Portal or to transport your BW ABAP objects, you might be interested in using the same tool to transport the BI objects as well. With the integration of CTS into the LCM, this is now possible. You can model your landscape for your BI systems in TMS like for any other non-ABAP application supported by CTS.

Note

This guide focuses on SAP BusinessObjects BI 4.0 Feature Pack 3 and higher. For lower releases, please refer to the Appendix for additional information and special configuration requirements.

The following picture shows the systems that are involved in the scenario. The systems BI Source and BI Target are just examples to illustrate that there are systems where the objects are exported with the help of LCM and others where an import has to be executed. CTS does not limit your landscape to one source and one target system. All the options that you might know from TMS are available for BI systems as well. You can e.g. have several systems in a row or more than one target system at once.

You also need an LCM Frontend (which is a web application). In the figure 1 ‘System Landscape’ the system where it is running, is called Admin.

Note

It is also possible to install and run LCM frontend on the BI source or target system (or any other BI system).

Moreover, you need a system where CTS is configured. For the set-up described in this guide, you have to use an SAP Solution Manager or SAP NetWeaver system where the CTS Plug-In contained in SL Toolset is installed as CTS system.


December 2014 2

Figure 1: System Landscape

The figure above illustrates the process of exporting (1 and 2 in the figure above) and importing (3 and 4 in the figure above) objects with LCM.

When exporting a job via the LCM frontend, the LCM frontend connects remotely (Corba) to the LCM backend. The data to be exported is collected in a job. The LCM frontend connects via the Export Client to the CTS System to add the LCM job to a transport request. After having exported the job, you then release the transport request (depending on your configuration, the CTS system can also do this automatically for you). You can now start the import. This is done on the CTS system. As soon as the import is started in TMS, the Deploy Web Service Client hands over the LCM job to the Deploy Web Service. The Deploy Web Service starts the Import of the LCM job on the target system (BI Target) and retrieves the import results.

2. Background Information Documentation for Promotion management tool has been updated. Please refer to the correct location of the documentation based on the version and service pack you are using:

Promotion management tool for SAP BusinessObjects BI 4.0 FP3 and up see Business Intelligence platform Administrator Guide: http://help.sap.com/bobip

Guides for CTS: http://scn.sap.com/docs/DOC-8576

SAP Note for installing the SAP CTS Plug-In of SL Toolset: 1665940

o Documentation for CTS including CTS Plug-In: http://help.sap.com/nwcts

o For SAP Solution Manager 7.1: http://help.sap.com/saphelp_ctsplug20sm71/helpdata/en/48/c4300fca5d581ce10000000a42189c/frameset.htm

o For SAP Solution Manager 7.01: http://help.sap.com/saphelp_ctsplug10sm70/helpdata/en/48/c4300fca5d581ce10000000a42189c/frameset.htm

Central SAP Note for CTS+: 1003674

Central SAP Note for SL Toolset: 1563579

http://help.sap.com/bobiphttp://scn.sap.com/docs/DOC-8576http://service.sap.com/sap/support/notes/1665940http://help.sap.com/nwctshttp://help.sap.com/saphelp_ctsplug20sm71/helpdata/en/48/c4300fca5d581ce10000000a42189c/frameset.htmhttp://help.sap.com/saphelp_ctsplug20sm71/helpdata/en/48/c4300fca5d581ce10000000a42189c/frameset.htmhttp://help.sap.com/saphelp_ctsplug10sm70/helpdata/en/48/c4300fca5d581ce10000000a42189c/frameset.htmhttp://help.sap.com/saphelp_ctsplug10sm70/helpdata/en/48/c4300fca5d581ce10000000a42189c/frameset.htmhttp://service.sap.com/sap/support/notes/1003674http://service.sap.com/sap/support/notes/1563579


December 2014 3

3. Prerequisites To be able to use the Promotion Management (LCM) with CTS as described in this guide, the following prerequisites apply:

CTS System: SAP Solution Manager 7.01 SP25 at least, SAP Solution Manager 7.1, SAP NetWeaver 7.3 including enhancement package 1, or SAP NetWeaver 7.4.

CTS plug-in installed on the CTS system (taken from SL Toolset 1.0 SP02 at least – always use the newest available CTS plug-in)

Note

Starting with SAP Solution Manager 7.1 SP5, CTS_PLUG is automatically part of your SAP Solution Manager installation or becomes part after an upgrade to this version

SAP Note 1860594 has to be implemented on the host of the CTS Deploy Web Service (for related information, see Configuring the CTS Deploy Web Service).

SAP Business Objects BI systems on SAP Business Objects BI 4.0 FP3 or higher

Note

For lower releases and the required configuration, refer to the chapter Configuration for systems on releases lower than BI 4.0 Feature Pack 3

If your BI system is running on an SAP NetWeaver, you must have configured SAP authentication as described in the Authentication chapter in the Business Intelligence Platform Administrator Guide (http://help.sap.com/bobip)

http://service.sap.com/sap/support/notes/1860594http://help.sap.com/bobip


December 2014 4

4. Restrictions and Recommendations You have to use a system as CTS system which has the CTS plug-in installed. CTS plug-in can be installed on top of SAP Solution Manager or SAP NetWeaver from 7.3 including enhancement package 1 onwards. CTS plug-in is part of SAP Solution Manager as of SAP Solution Manager 7.1 SP5

Parallel Usage of LCM with CTS is not recommended. Especially not for the same landscape of CMS systems.

Restrictions of LCM apply – e.g. you can only execute transports if both source and target BI are on the same version.

If you use the LCM with CTS+, we recommend that you maintain only source systems in LCM under the Manage System option, so that every transport is handled only using CTS.

Please consider the following when using LCM with CTS:

CTS only offers a high level view. Versions are only created on demand, not e.g. when a job is exported.

Be careful with the following permissions in LCM. They should only be granted to users who really know what they are doing. If LCM is used with CTS, these permissions conflict with what can be done in CTS:

Test promote: is not possible if you use CTS+, the option is not visible.

Rollback Job (To rollback a job): this functionality is not supported by CTS. Using Rollback on LCM side will cause confusion as the status of the respective transport request in CTS would suggest that the content is available on the system. You should not use this option together with CTS+. If you use CTS+, best practice would be to re-promote the respective content.

Override settings (To edit the properties of a connection): This permission should be available to Administrators who set up the landscape in TMS only. Only a connection to the source BI system is needed.

You can’t promote Overrides through password-encrypted BIAR files if you use CTS for transports.

Log-Level: BI logs are shown in CTS+ as well. Logs capture the status of individual objects. So the information would be available on both sides, LCM and CTS+.

In LCM, the Change Management ID is updated with the transport request ID from CTS+.

Job Scheduling can be used with CTS+ as well. Think about the transport strategy that you use for your source system in CTS+ in this case. If a request remains open after a job had been attached, the same request might contain different promotions of the same job. All of the jobs will be imported in the same order as they had been attached to the transport request.

You can attach zipped LCMBIAR-files manually to a transport request. You can create a job with the LCMBIAR as the source and CTS+ as the destination system. Importing password encrypted LCMBIAR files via CTS+ is not possible.

Command Line option: is not supported with CTS+. It can only be used to import a BIAR file to a BI system – CTS+ cannot be involved in here.


December 2014 5

5. Basic configuration for CTS

5.1 Configure the Transport You have to do configurations on your CTS system, on the BI Server and on the system where your LCM frontend is running to be able to use CTS. This chapter helps you with these configurations. It provides a step-by-step guide. Remember: You have to install the CTS plug-in on your CTS System.

CTS System

Sample Landscape

In the sample Landscape shown in the picture above, you can see three BI systems:

BD1 is the development system – also called export or source system

BT1 is the test system – also called import or target system

BP1 is the productive system – also called import or target system

Note

BD1, BT1, and BP1 are sample representations in TMS of SAP Business Objects BI systems/servers. The following sections: Configure the BI Landscape, Configuring the Transport Landscape in TMS, and Create a Mapping File on the BI Source System explain the mapping of IDs (host and port of BI servers/systems) to their representations in TMS.

This landscape is used as an example in the following chapters explaining the configuration.


December 2014 6

5.1.1 Configuring the CTS Deploy Web Service

A logical port is needed for the communication between the AS ABAP and the AS Java of the CTS

system: CTSDEPLOY.

Check whether the logical port is already available on your CTS system and if not create it as described in this chapter. If you are already using enhanced CTS for e.g. managing Portal transports, then this port will most probably already exist.

Note

If enhanced CTS (CTS+) is already in use at your company: CTSDEPLOY is the standard port that should be used to connect the Deploy Web Service client and the Deploy Web Service. However, if you cannot reuse the settings of this port for BI as well, then you can create an additional port with a different name (e.g. CTSDEPLOY_BI). When you create an additional port ensure that you use the new name instead of the default name (CTSDEPLOY) wherever it appears in this guide.

1. Log on to the client of your CTS system that you are using for transports (=where the Transport

Organizer Web UI runs). Call transaction SM59 and open the HTTP Connections to External

Server section.


December 2014 7

2. Check whether the connection CTSDEPLOY is already available. If not, click on Create.

And create it with the following parameter values:

Enter CTSDEPLOY as RFC Destination and a description. As Target Host, and Service No, enter

the respective data of the AS Java of your CTS system (= your server where the Deploy Web Service is running). If you use a dual stack system as CTS system, enter the host name of this system. If you use separated ABAP and Java Stacks, enter the host name of the AS Java that is used for CTS. The Service No is the port of the AS Java. This is usually port

500. Make sure that the Connection Type is G.

Note

The AS JAVA used for CTS must be at least on SAP NetWeaver 7.0 Enhancement Package 2, Support Package Stack 5.


December 2014 8

3. On the Logon & Security tab page, select Basic Authentication and enter a user which exists on the AS Java. Enter the password as well.

4. On the Special Options tab page, select No Timeout.

5. Choose Connection Test.

The test should end with Status HTTP Response = 200

Note

The Connection Test only tests the connection to the server without using the specified user.


December 2014 9

One logical port is needed for the communication between the AS ABAP and the AS Java of the CTS

system: CTSDEPLOY. The port is delivered by default. Check whether it is available on your system

and if not create it.

6. Log on to your CTS system in client 000 and call transaction LPCONFIG. Confirm the message

that the transaction is obsolete.

7. Enter CO_TFLDEPLOY_PROXY_VI_DOCUMENT as Proxy Class and CTSDEPLOY as Logical

Port. This is the destination that you have already worked with in transaction SM59 in the previous section.

8. Click on Display. If the port does not exist, create it with the parameter values shown on the following screenshot.

CAUTION

Make sure that Default Port is selected and that the logical port is active.


December 2014 10

Details about configuring the CTS Deploy Web Service can be found on the SAP Help Portal:

http://help.sap.com/saphelp_ctsplug20sm71/helpdata/en/2b/326d6274134cea8b217f24889d19c1/frameset.htm.

5.1.2 Configuring the Transport Organizer Web UI

CTS provides an ABAP Web Dynpro application (CTS_ORGANIZER) that you have to use to get detailed information about transport requests (e.g. default request, target systems,…) and which you could use to create transport requests and attach objects manually. You have to activate certain services to run and use this application.

To be able to use the Object List Browser to see a detailed list of objects attached to a transport request as part of one file you need to activate the ICF service CTS_OBJECTLIST_BROWSER.

http://help.sap.com/saphelp_ctsplug20sm71/helpdata/en/2b/326d6274134cea8b217f24889d19c1/frameset.htmhttp://help.sap.com/saphelp_ctsplug20sm71/helpdata/en/2b/326d6274134cea8b217f24889d19c1/frameset.htm


December 2014 11

For more details, refer to http://help.sap.com/saphelp_ctsplug20sm71/helpdata/en/e5/998566c2174196a12b72e7c7af51e7/frameset.htm

If CTS+ is already in use on the CTS system where you are doing the configuration, the services should already be activated. If not, activate them now.

If you receive error messages when running this application later on or if you don’t want to activate all ICF services read the error messages carefully and activate the services named in the error messages via transaction SICF.

Note

Note that Transport Organizer Web UI exists in a new version as of CTS Plug-In 2.0. If you have used the earlier version, you must activate the service for the new version.

The following figure shows the Transport Organizer Web UI.

To open the Transport Organizer Web UI, go to transaction STMS and click on

http://help.sap.com/saphelp_ctsplug20sm71/helpdata/en/e5/998566c2174196a12b72e7c7af51e7/frameset.htmhttp://help.sap.com/saphelp_ctsplug20sm71/helpdata/en/e5/998566c2174196a12b72e7c7af51e7/frameset.htm


December 2014 12

In the pop-up shown, select your source system (BD1 in our example)


December 2014 13

6. Configure BOLM as application type To be able to use CTS with LCM, you have to make the application known in CTS. You need an application type which will then be used as unique identifier for BI in CTS to do so. For the LCM integration with CTS, the application type BOLM is used.

Documentation on how to do this is provided on the SAP Help Portal: http://help.sap.com/saphelp_ctsplug20sm71/helpdata/en/02/4c3be45416486ea116cff53831e50a/frameset.htm

The following steps describe how the application type is created and managed in CTS.

Log on to your CTS system (Domain Controller) and open transaction STMS. Go to the System Overview.

To create a new application type, go to Extras Application Types Configure.

http://help.sap.com/saphelp_ctsplug20sm71/helpdata/en/02/4c3be45416486ea116cff53831e50a/frameset.htmhttp://help.sap.com/saphelp_ctsplug20sm71/helpdata/en/02/4c3be45416486ea116cff53831e50a/frameset.htm


December 2014 14

You can see a list of application types already created in your system. Choose New Entries if BOLM is not yet part of the list.

On the next screen, you can enter your application type and some details. Use BOLM in here. A description and support details are required to give some details on the application type and on how to get support in case of issues.

Use BO LCM and CTS+

integration as Description and http://service.sap.com (ACH:

BOJ-BIP-DEP) as Support Details.

This is the component that you can use to open messages for SAP in case of issues with LCM transports.

Save your entry and click Yes to distribute the new application type through your landscape.

http://service.sap.com/


December 2014 15

The new application type has been saved. Click Back to return to the list of application types.

The new application type BOLM is now part of the list.


December 2014 16

7. Configure the BI Landscape The configuration of the BI landscape consists of several steps, which will be detailed in the following chapter.

As an example we will setup a landscape of three systems as depicted in chapter Configure the Transport, i.e. a development system (BD1) as source system, a test system (BT1) and a production system (BP1) as target systems.

1. CTS identifies systems resp. transport nodes via 3-digit System IDs (SIDs). If you are using BI on another platform than SAP NetWeaver, your systems won’t have an SID right now. So think about the 3 digit SIDs that you would like to use at first.

Note

SIDs consist of three characters (letters and / or numbers). They have to be unique within your transport domain, but they may be shared between different applications (i.e. BI CMS system and Portal if they run on same SAP Net Weaver AS JAVA instance).

As an example we will use BD1 (development system), BT1 (test system) and BP1 (production system) in the following.

2. As soon as you know the SIDs for your BI systems, you can start creating the representations for these systems in TMS and connect them with the help of transport routes. Details are described in the chapter Configure the Transport Landscape below.

3. Finally, export system has to be configured on BI CMS side as described in the chapter Configuration for Export.

7.1 Configuring the Transport Landscape in TMS Create the systems of your BI landscape as non-ABAP systems in TMS. Their SIDs are representing them in TMS. This is to provide a clear understanding of the transport routes to the BI users who are using LCM and Transport Organizer Web UI from within LCM.

Documentation on how to create non-ABAP systems in TMS is provided on the SAP Help Portal: http://help.sap.com/saphelp_ctsplug20sm71/helpdata/en/bf/e4626214504be18b2f1abeeaf4f8e4/frameset.htm. This chapter shows how setting up the systems would work in our example.

7.1.1 Configuring the Development system (Export system)

Define your BI CMS development system (‘BD1’) as source system. You therefore have to select the option ‘Activate Transport Organizer’ when creating the system representation in TMS.

Log on to your CTS System. Open transaction STMS and choose System Overview

http://help.sap.com/saphelp_ctsplug20sm71/helpdata/en/bf/e4626214504be18b2f1abeeaf4f8e4/frameset.htmhttp://help.sap.com/saphelp_ctsplug20sm71/helpdata/en/bf/e4626214504be18b2f1abeeaf4f8e4/frameset.htm


December 2014 17

Choose SAP System Create Non-ABAP System

Enter the SID of your BI development system (BD1 in our example) in the field System, a Description and choose Activate Transport Organizer. Select the client of the ABAP communication system where you want to use Transport Organizer; that is where transport requests will be created. Choose Save. The system will be created and the system list will show up.


December 2014 18

After having created the development system, you can decide on the Transport Strategy. The Transport Strategy defines whether a transport request is created automatically or e.g. by an administrator and if the request should be directly released or remain open after having attached objects to it. To do so, double-click in the system list on the system BD1 that you just created. Details on the Transport Strategy can be found on the SAP Help Portal: http://help.sap.com/saphelp_ctsplug20sm71/helpdata/en/c5/d9012e437d4c318976edc9791f2ae4/frameset.htm

In the configuration, go to the tab Transport Tool and switch to the Edit mode.

Check whether the parameters WBO_GET_REQ_STRATEGY and WBO_REL_REQ_STRATEGY are already in the list of parameters. If this is not the case, select one row and then choose Insert Row.

http://help.sap.com/saphelp_ctsplug20sm71/helpdata/en/c5/d9012e437d4c318976edc9791f2ae4/frameset.htmhttp://help.sap.com/saphelp_ctsplug20sm71/helpdata/en/c5/d9012e437d4c318976edc9791f2ae4/frameset.htmhttp://help.sap.com/saphelp_ctsplug20sm71/helpdata/en/c5/d9012e437d4c318976edc9791f2ae4/frameset.htm


December 2014 19

A new row is shown. Choose the input help (F4-help).

Choose the parameter that you would like to add from the F4 help of the newly added row.


December 2014 20

You can use the values SMART, TAGGED

or CREATE for

WBO_GET_REQ_STRATEGY and MANUAL or AUTOMATIC for

WBO_REL_REQ_STRATEGY. Refer to the SAP Help Portal for details.

Note

The first letter of the value must be written with a capital letter.

All BI users that should be allowed to attach LCM jobs to transport requests have to have a corresponding user in the client of the CTS system that you are using for transports (= the client where you activated the Transport Organizer Web UI). The user ID has to be the same on the BI and on the CTS system.

Note

ABAP supports user IDs with a length up to 12 characters. So you should only use user-IDs with up to 12 characters in all systems.

The user promoting the job should have adequate permissions on the BI source system and on the LCM. For detail, see the “Application access rights” chapter in the Business Intelligence Platform Administrator Guide. To transport non-ABAP objects, you can use the authorizations of the delivered role SAP_CTS_PLUS.

CAUTION

Do not use this role directly. Instead, use it as a template and copy it to your own role (Z_*). For more information on the creation and maintenance of roles in ABAP take a look at the SAP Help Portal: http://help.sap.com/saphelp_nw70ehp2/helpdata/en/52/6714a9439b11d1896f0000e8322d00/frameset.htm.

Note

In addition the role SAP_BC_WEBSERVICE_CONSUMER is required or appropriate permissions

for Web Service EXPORT_CTS_WS have to be assigned in the user management of AS ABAP of

the CTS system. For details, refer to the SAP Help portal at http://help.sap.com/saphelp_nw70ehp1/helpdata/en/2b/07074155bcf26fe10000000a1550b0/frameset.htm and to SAP Note 1003674.

Take a look at note 1003674 also for recent updates on authorizations required for the different releases.

7.1.2 Configuring the Test and Production System (Import

Systems)

Define your BI CMS test and production systems (‘BT1’, ‘BP1’) as target systems by selecting the option ‘activate deployment service’. Choose the option ‘Other’ as method(s).

http://help.sap.com/saphelp_ctsplug20sm71/helpdata/en/c5/d9012e437d4c318976edc9791f2ae4/frameset.htmhttp://help.sap.com/saphelp_nw70ehp2/helpdata/en/52/6714a9439b11d1896f0000e8322d00/frameset.htmhttp://help.sap.com/saphelp_nw70ehp2/helpdata/en/52/6714a9439b11d1896f0000e8322d00/frameset.htmhttp://help.sap.com/saphelp_nw70ehp1/helpdata/en/2b/07074155bcf26fe10000000a1550b0/frameset.htmhttp://help.sap.com/saphelp_nw70ehp1/helpdata/en/2b/07074155bcf26fe10000000a1550b0/frameset.htmhttp://service.sap.com/sap/support/notes/1003674


December 2014 21

When you create a non-ABAP target system which should use this new application type BOLM, you have to choose Other as Method(s). Click Save.

Click Yes to distribute the configuration.

When saving the non-ABAP system, you are asked to define the deployment method for your system. Choose New Entries.


December 2014 22

On the next screen, choose BOLM as Application Type (F4-help). Choose the Deployment Method Application Specific Deployer (EJB)

Enter Deploy URI according to: http://:/BOE/LCM/CTSServlet?&cms

Name=:&authType=. The deploy

URI contains the LCM CMS name and the destination BI CMS name. For example, the Deploy URI could be: http://:8080/BOE/LCM/CT

SServlet?&cmsName=:6400

&authType=secEnterprise

For details on possible authentication types, refer to the chapter 9 Authentication of the Business Intelligence Platform Administrator Guide at http://help.sap.com/bobip

Create a user account and assign authorizations on the BI test system and BI production systems. This user needs the following authorizations: To be able to execute job imports use the admin or a user who belongs to the admin group on the target system and has permissions to update the content.

Enter this User name and Password in here per system.

Note

All jobs promoted to the destination system using CTS use this username and password by default.

http://help.sap.com/bobip


December 2014 23

Save your entries and choose Yes to distribute the new application type through your landscape.

Your entry is now saved. Click Back to reach the list again

You can now see your details for handling the application type BOLM. Choose Back to return to the system.

Create any other target system that you might need (e.g. here for production system –‘BP1’) as shown before.

You can also extend the configuration of existing systems to be able to use them with new application types. To do so do the following:


December 2014 24

Go to the system overview in TMS and double-click on the system where you would like to extend the configuration.

In the details of your system, choose Goto Application Types Deployment Method

Choose New Entries and proceed as described above for the creation of new systems.

7.1.3 Transport Landscape: Defining Transport Routes

Now that you have created representations for the different systems (BD1, BT1 and BP1 in our example) in TMS, you have to connect them with the help of transport routes.

Use client-independent transport routes.

For details on how to configure transport routes, take a look at the SAP Help Portal: http://help.sap.com/saphelp_ctsplug20sm71/helpdata/en/44/b4a1df7acc11d1899e0000e829fbbd/frameset.htm

http://help.sap.com/saphelp_ctsplug20sm71/helpdata/en/44/b4a1df7acc11d1899e0000e829fbbd/frameset.htmhttp://help.sap.com/saphelp_ctsplug20sm71/helpdata/en/44/b4a1df7acc11d1899e0000e829fbbd/frameset.htm


December 2014 25

Log on to your CTS system (Domain Controller). Open transaction STMS and go to Transport Routes

The systems BD1, BT1 and BP1 that you just created are shown in the upper row of systems. The systems shown in here are not yet connected by transport routes. Switch to Edit mode.

Click on system BD1 and then click in the area where the transport routes are shown.


December 2014 26

Repeat the previous step for BT1 and BP1

Choose Add Transport Route

Your mouse pointer is now a pencil. Draw a line from BD1 to BT1


December 2014 27

A dialog box opens up. Make sure that Consolidation is selected. A consolidation route is needed to connect a development system to e.g. a test system (from a system where you do an export to a system where you would like to import the transport request).

Enter a name for the Transport Layer, e.g. ZBOE. The name has to start with a Z.

Note

Create one standard transport layer (this is the default), not two separate ones for SAP- and custom transports as you might know it from configuring transport routes for ABAP systems.

Choose Transfer.

You have to enter a Short Description for the Transport Layer in a second window if the transport layer does not yet exist. Choose again Transfer.

A transport route has been added connecting BD1 with BT1. Now draw a line from BT1 to BP1.

Choose Delivery for this transport route and click on Transfer. When you set up a delivery route, you are making sure that all transport requests that are imported into the route’s source system are automatically flagged for import into the route’s target system. Choose Transfer.


December 2014 28

Save the configuration.

Confirm that you would like to Distribute and Activate the configuration.

The transport route for BD1, BT1 and BP1 is now part of the configuration.

7.2 Configuration for Export

On the BI development system, you have to store the SID used in CTS landscape for it (‘BD1’) in a mapping file and define how remote connection to the CTS communication system is done. This is needed so that the SID can be forwarded to the CTS system whenever a transport request is needed


December 2014 29

or created. The CTS system has to know for which system it has to create or look for a transport request. The ‘name’ of a transport request in TMS starts with the SID of the respective development system and thereby identifies the transport route etc. to which it belongs.

7.2.1 Create a Mapping File on the BI Source System

The mapping file is a simple flat text file. It is used to map the source CMS to the logical name of the system in CTS (in the TMS landscape configuration). This is needed to retrieve the correct names for new transport requests. Use the following entities:

@: This parameter refers to the system

name and port name of the source SAP BI platform system, chosen on the LCM UI during job creation.

: This

parameter is the SID used to represent the source SAP BI platform system mentioned above in CTS configuration (BD1 in our example).

Complete the following steps to map your CMS to the system representation in TMS: 1. In the SAP BI LCM CMS (source system), go to the root directory and create a folder with

name LCM in the path /SAP BusinessObjects Enterprise XI

4.0>.

2. Create a text file with name LCM_SOURCE_CMS_SID_MAPPING.properties, and enter the

following mapping data in the file: ...

a. @=

b. @=

c. @ =

Example

Wdflbd8100.wdf.sap@6400=BD1

Wdflbd8100@6400=BD1

10.10.16.22@6400=BD1


December 2014 30

7.2.2 Activate the CTS Export Web Service

You can activate and configure the CTS Export Web Service using the SOA Management web tool.

Note

The following procedure and screenshots refer to SOA Management in SAP NetWeaver 7.0 Enhancement Package 2, Support Package Stack 10. If you are using SOA Management in another release or Support Package level, refer to the appropriate SAP Library documentation.

Note that the functions in SOA Management have changed as of SAP NetWeaver 7.0 including enhancement package 2 SP08 and 7.30 SP03. The corresponding documentation is available as of SAP NetWeaver 7.0 including enhancement package 2 SP13 and SAP NetWeaver 7.30 SP09. For more information on the changed functions, see SAP Note 1575707.

For more information about SOA Management and the configuration of a binding, refer to the following information:

- SAP Help Portal at http://help.sap.com/saphelp_nw73ehp1/helpdata/en/33/06820d9d174c2884576bd78ac5629d/frameset.htm.

- ABAP Connectivity Wiki in SAP Community Network, especially How to configure a Service Provider.

http://service.sap.com/sap/support/notes/1575707http://help.sap.com/saphelp_nw73ehp1/helpdata/en/33/06820d9d174c2884576bd78ac5629d/frameset.htmhttp://help.sap.com/saphelp_nw73ehp1/helpdata/en/33/06820d9d174c2884576bd78ac5629d/frameset.htmhttp://wiki.sdn.sap.com/wiki/display/ABAPConn/ABAP+Connectivity+Homehttp://wiki.sdn.sap.com/wiki/display/ABAPConn/How+to+configure+a+Service+Providerhttp://wiki.sdn.sap.com/wiki/display/ABAPConn/How+to+configure+a+Service+Provider


December 2014 31

Log on to the CTS system in the client that you have defined when configuring the development system. (see also: Configuring the Transport Landscape in TMS)

To start the application, enter the transaction code SOAMANAGER.

(For more information about SOA Management and the configuration of a binding, refer to the links in the Note section above.)

After the required authentication is done, the SOA Management UI opens in a Web browser.

On the Service Administration tab, choose Web Service Configuration.


December 2014 32

The CTS Export Web Service has the

name EXPORT_CTS_WS. You can see

the WSDL of the service.


December 2014 33

You can also define/edit the binding here. The binding contains a runtime configuration, which is needed to implement the service.

As soon as the binding is defined, you can configure it as desired.

For one service, you can define multiple bindings and configure them independently.


December 2014 34

The most important configuration settings are defined on the Provider Security tab of the Configuration of Web Service panel (e.g. Communication Security, Authentication Settings).

Recommendation We recommend that you use SSL and Single-Sign On whenever possible


December 2014 35

For easier service access, we recommend that you also define the binding alias using Alternative Access URL. To ensure unique alternative access URLs we recommend that you add the client in which you are logged on to the alias. You can do this in the Transport Settings tab.

Note

If you encounter problems when using the web service, you can find details for errors in

the Application Log (transaction SLG1) for object CTSPLUS. To be able to view the logs,

you must be logged on to the system in the client that hosts the Export Web Service.

7.2.3 Source System: Connect to CTS Export Web Service

Log in to the Central Management Console (CMC).

Choose Promotion Management.

Choose Settings CTS Settings Web Service Settings.


December 2014 36

Enter the URL for the CTS Export Web Service as defined in chapter 7.2.2 Activate the CTS Export Web Service, e.g. with following format: http://:/.

Enter a User Name and a Password. The role SAP_CTS_PLUS should be assigned to this user. In some releases of the CTS system, this role might not be sufficient. Check SAP Note 1003674 for details. Choose Save.

8. Use LCM with CTS Using LCM with CTS is different from using it to promote jobs to another CMS. When using CTS to transport the jobs, you don’t select the target CMS any more, you don’t have to log on to this system and you don’t need any permissions on the target CMS. The job will be attached to a transport request in the format of a zip-file and anyone who has permissions to access the import queue of the target system can execute the import. The target system(s) for a transport request and therefore the job are defined with the help of transport routes in TMS. The following figure shows what this process looks like.

8.1 Create a New Job To create a new job, complete the following steps:

1. Log into Central Management Console and select Promotion Management (for BI 4.0 SP2 and earlier, use the lifecycle management console tool).

Note

Ensure that you select "SAP" as the authentication type in the source system login screen.


December 2014 37

2. In the "Promotion Jobs" home page, select New Job. And fill in the required fields Name: Name of the job that you want to create. Description: Description of the job you want to create. Keywords: The keywords for the contents of the job you want to create. Save Job in: You must browse and select a folder to create a job. Source System: The name of the SAP BusinessObjects BI system from which you want to promote a job. Destination System: Choose ‘Promote via CTS’ User name: The login ID that you must use to log into the source. Password: The password that you must use to log into the source. Authentication: The authentication type that is used to connect to the source or destination system.

8.2 Add Objects to a Job To add an info object to a job, complete the following steps:

1. Log into Central Management Console and select Promotion Management (for BI 4.0 SP2 and earlier, use the lifecycle management console tool).

Note

Ensure that you select "SAP" as the authentication type in the source system login screen.

2. Create a new job. For information on creating a new job, see Create a New Job. 3. Choose Add Objects. The "Add Objects" screen appears. The folder and subfolders are

displayed in a tree structure. 4. Navigate to the folder from which you want to select the object. The list of objects in the

selected folder is displayed. 5. Select the object that you want to add to the job, and choose Add. If you want to add an object

and exit the "Add Objects" screen, choose Add and Close. The object is appended to the job, and the "Add Objects" screen closes.

After you add an object to a job, you can right-click the "Job Viewer" page and select the job-related processes to proceed with the promotion task. You can also use the Manage Dependencies option in the "Job Viewer" page, to manage the dependents of the object you selected.

8.3 Promote a Job and Release the Request After having added the objects that you would like to transport to a job, you can promote this job. If CTS+ is configured, this is done via the option ‘Promote via CTS’. This will first show details of the transport request to which the job can be added. Ensure that the initially shown transport request is correct. You can change the transport request by using the link to the Transport Organizer Web UI. To update data shown in Promote screen press Refresh. After promotion you will see a status change to ‘Exported to CTS’ in LCM and the job will be added to the transport request, resulting in the object list of the Transport Organizer Web UI as displayed in the following figure.

For information on Transport Organizer Web UI, see http://help.sap.com/saphelp_ctsplug20sm71/helpdata/en/df/7a1d1a4f0d4805b46c61a0d53cb4c7/frameset.htm.

http://help.sap.com/saphelp_ctsplug20sm71/helpdata/en/df/7a1d1a4f0d4805b46c61a0d53cb4c7/frameset.htmhttp://help.sap.com/saphelp_ctsplug20sm71/helpdata/en/df/7a1d1a4f0d4805b46c61a0d53cb4c7/frameset.htm


December 2014 38

A zip file is added to the object list. You can open it to find more details on the objects that are inside the job.

After you have added one (or several) jobs to a transport request, you can release the request. This is also done in the Transport Organizer Web UI. Mark the request that you would like to release and choose Release.

Depending on the configuration for your source system in TMS, it might also be the case that a transport request is released automatically after you have added a job. More details on the Transport Strategy are provided on the SAP Help Portal: http://help.sap.com/saphelp_ctsplug20sm71/helpdata/en/c5/d9012e437d4c318976edc9791f2ae4/frameset.htm. The request cannot be changed any more. It is no longer visible in the list of Modifiable requests in the Transport Organizer Web UI.

http://help.sap.com/saphelp_ctsplug20sm71/helpdata/en/c5/d9012e437d4c318976edc9791f2ae4/frameset.htmhttp://help.sap.com/saphelp_ctsplug20sm71/helpdata/en/c5/d9012e437d4c318976edc9791f2ae4/frameset.htm


December 2014 39

Note

If you encounter problems with CTS communication when promoting jobs, check whether

you can find details for errors in the Application Log (transaction SLG1) for object

CTSPLUS.

8.4 Importing a Job All transport requests that are released become part of the import queue of the first target system. You can now import one, several, or all of them.

Log on to your CTS system and open transaction STMS

Choose Import Overview


December 2014 40

Double-click on the SID of your target system

Choose Import all Requests if you would like to import the complete queue. Otherwise, mark the request(s) that you would like to import and choose Import Requests.

Choose Continue to start the import immediately or define an appropriate time frame or event when the import should be started and choose Continue afterwards.

Confirm that you’d like to import the request (click Yes).


December 2014 41

After having imported a request, a return code will be shown per request whether the import was successful or not. Take a look into the next chapter to learn more about return codes.

For more details on performing imports, see http://help.sap.com/saphelp_ctsplug10sm70/helpdata/en/09/ca0f3a878f46e9a5a32e666131d2ba/frameset.htm.

Note

As of CTS Plug-In 2.0 SP02 (SL Toolset 1.0 SP05), a new browser-based Import UI is available. Alternatively, you can use the Import UI to perform imports. For more information, see http://help.sap.com/saphelp_ctsplug20sm71/helpdata/en/4b/b9a1222f504ef2aa523caf6d22d1c9/frameset.htm.

After the import, you may want to logon to the destination system to view the status of the job you promoted.

8.4.1 Meaning of Return Codes - Reading the Deployment

Log-File on CTS side

Four different return codes can appear in the import queue

RC = 0: The import has been successfully completed. Symbol in the queue:

RC = 4: Warning that not everything was ok but import in principle worked. Symbol in the

queue:

RC = 8: Errors for the content occurred when importing. A subsequent transport is required.

Symbol in the queue:

RC = 12: There were issues with the tool during the import. The request can be imported

again after having fixed the issue. Symbol in the queue:

You can double-click on the symbol for the return code for one transport request to learn more about the import. Especially if the RC is not zero, it might be interesting to find out what went wrong. Clicking on the return code will bring up the overview of the Transport Logs.

You can click on the icon in front of the step Deployment to view the deployment log.

http://help.sap.com/saphelp_ctsplug10sm70/helpdata/en/09/ca0f3a878f46e9a5a32e666131d2ba/frameset.htmhttp://help.sap.com/saphelp_ctsplug10sm70/helpdata/en/09/ca0f3a878f46e9a5a32e666131d2ba/frameset.htmhttp://help.sap.com/saphelp_ctsplug20sm71/helpdata/en/4b/b9a1222f504ef2aa523caf6d22d1c9/frameset.htmhttp://help.sap.com/saphelp_ctsplug20sm71/helpdata/en/4b/b9a1222f504ef2aa523caf6d22d1c9/frameset.htm


December 2014 42

You can see the deployment log. For more details, you can use the expand-buttons.

8.5 Advanced Usage of LCM with CTS

8.5.1 Transport Organizer Details

In this chapter, you can find some more details and hints about the information and functionality that is provided with the Transport Organizer Web UI. A detailed documentation is provided on the SAP Help Portal at http://help.sap.com/saphelp_ctsplug20sm71/helpdata/en/df/7a1d1a4f0d4805b46c61a0d53cb4c7/frameset.htm

Object List

In the object list, you can find details about all the objects that are part of the job (the zip-file) that you attached to a transport request.

http://help.sap.com/saphelp_ctsplug20sm71/helpdata/en/df/7a1d1a4f0d4805b46c61a0d53cb4c7/frameset.htmhttp://help.sap.com/saphelp_ctsplug20sm71/helpdata/en/df/7a1d1a4f0d4805b46c61a0d53cb4c7/frameset.htm


December 2014 43

In case of SAP Business Objects BI, you can e.g. see what type of object is transported (e.g. CustomRole, Folder or User Group). Clicking on the link Details will bring up some additional information:

Object List Browser

You can use the link Object List Browser to reach a UI which helps you searching for certain objects. This is helpful if you would like to find out when and with which transport request a certain object has been transported.

The object List Browser shows up. As shown in the following figure, it mainly consists of two tabs Browse and Search.

When opening up the Object List Browser, you will first see the tab Browse as the active one. By default, the request that was selected in the Transport Organizer Web UI before is shown. You can type in a different request number if you would like to see details for a certain request or you can switch to the Search tab to find out more about the ‘transport history’ of a certain object.


December 2014 44

On the Search tab, you can find different search criteria. You can e.g. look for a certain object name; narrow the result by also defining e.g. Last modified by or look for all objects of a certain Object Type.

In the search result, you can then find all the transport requests where the object(s) matching your search criteria were transported.

If you would like to see all the available information for a certain transport request, click on it in the search result with the secondary mouse button.


December 2014 45

Choose Display in Transport Organizer.

8.5.2 Promoting Overrides

Overrides have to be promoted first and edited in all the destination systems before promotion of any BI content. Overrides tables contain a list of all unique connection information available in the original system (usually DEV system). Users edit this table with appropriate destination system values so that when content is transported they are automatically updated with newer more relevant values. For more information, refer to Promotion management tool for SAP BusinessObjects BI 4.0 FP3 and up in the Business Intelligence platform Administrator Guide http://help.sap.com/bobip

8.5.3 Tools for managing transports

In this guide, it was shown how you can use CTS+ to transport BI objects. It might be the case that you are already using CTS for transporting your SAP NetWeaver Business Warehouse (BW) objects. With the setup described in this guide and with what you might already use for BW, you now have two separate landscapes: one for your BI systems and one for your BW systems. This will result in separate transport requests that are moved along different transport routes. Now, it is very often the case that changes that you did in the BI and the BI system belong together and should be kept together. CTS and CTS+ on their own cannot help in here. There are tools in SAP Solution Manager that can help you managing change requests and keeping changes done in different systems together. These tools are called Change Request Management (ChaRM) and Quality Gate Management (QGM). Details for both are provided on the Service Marketplace at https://service.sap.com/changecontrol .

9. Appendix

9.1 Configuration for systems on releases lower than BI

4.0 Feature Pack 3

If your system is not on SAP Business Objects 4.0 FP 3 at least, some special configuration options and prerequisites apply

If you would like to use LCM with CTS integration on a BI 4.0 Support Package level earlier than Feature Pack 3, you have the following options: You can deploy the BI 4.0 frontend (BOE.war) on at least SAP NetWeaver Composition Environment 7.2 SP 3 (CE) or on at least SAP NetWeaver 7.3 AS Java. This might mean that you have to set up an additional system. Refer to Figure 1: ‘System Landscape’ to get an understanding about the systems involved.

Note

If you are using SAP NetWeaver CE or SAP NetWeaver 7.3 anyhow as platform for other BI web applications, you can for sure run the LCM on one of these servers.

http://help.sap.com/bobiphttps://service.sap.com/changecontrol


December 2014 46

This does not limit the platform that you can use for BI in general to SAP NetWeaver.

Lifecycle Management console for SAP BusinessObjects Business Intelligence platform 4.0 User Guide: http://help.sap.com/businessobject/product_guides/boexir4/en/xi4_lcm_user_en.pdf

BI 4.0 systems which are on a lower release than FP3 cannot be used with the integration via Export Web Service as described in chapters 7.2.2 Activate the CTS Export Web Service and 7.2.3 Source System: Connect to CTS Export Web Service. Instead of what is described there, create an RFC Destination on the system, where you run the LCM Frontend. This destination is used whenever the LCM contacts the CTS system. It contains the connection data from LCM to CTS.

Do the following to configure the RFC destination from LCM frontend system to CTS ABAP server:

Logon to SAP NetWeaver Administrator using the following URL: http://:/nwa where

and define the server

where the LCM Frontend is running. For more information, see http://help.sap.com/saphelp_nw73/helpdata/en/49/49b19720cc3b5be10000000a42189b/frameset.htm

Go to Configuration Destinations

http://help.sap.com/businessobject/product_guides/boexir4/en/xi4_lcm_user_en.pdfhttp://help.sap.com/saphelp_nw73/helpdata/en/49/49b19720cc3b5be10000000a42189b/frameset.htmhttp://help.sap.com/saphelp_nw73/helpdata/en/49/49b19720cc3b5be10000000a42189b/frameset.htmhttp://help.sap.com/saphelp_nw73/helpdata/en/49/49b19720cc3b5be10000000a42189b/frameset.htmhttp://help.sap.com/saphelp_nw73/helpdata/en/49/49b19720cc3b5be10000000a42189b/frameset.htm


December 2014 47

Click on Create to create a new destination

Create a destination with the local java System as Hosting System. Use exactly sap.com/com.sap.tc.di.C

TSserver as Destination

Name. Choose RFC as

Destination Typ. Choose Next.


December 2014 48

In the next step, enter the system Data of your CTS communication system (where CTS+ is used) and choose Next.

Choose Technical User as

Authentication type. Enter a User Name and Password. The role SAP_CTS_PLUS should be assigned to this user. In some releases of the CTS system, this role might not be enough. Check SAP Note 1003674 for details.


December 2014 49

No changes are needed on the next screen. Choose Finish.

The new destination is now shown in your list of existing destinations. Mark it and choose Ping Destination.


December 2014 50

You should receive a message that the connection was successful.

If you encounter problems with the destination setup check whether SAP note 1155884 can help to resolve these.

BI 4.0 systems which are on a lower release than FP3 require a connection to a BW source system. Therefore, you have to do the following configuration steps:

o Create a Mapping File to the BW Development System on the BI Source System. The mapping file is used to enable communication with the BW development system by mapping the system ID of the BW development system to the corresponding RFC destination name:

...

1. To create the file, go to the same directory as described in the chapter Create a Mapping File on the BI Source System.

2. Create a new text file with name LCM_SID_RFC_MAPPING.properties in the

same folder, and enter the following mapping data in the file: =

Example

BWD=BWD.RFC where the SID of the BW development system is BWD.

Note

You can enter more than one BW SID entry in this file.

For more information on this, refer to the document ‘Lifecycle management console for SAP BusinessObjects Business Intelligence platform 4.0 User’ at Guide http://help.sap.com/businessobject/product_guides/boexir4/en/xi4_lcm_user_en.pdf

For Promotion overrides (chapter 8.5.2) refer to SAP BusinessObjects Lifecycle management console for SAP BusinessObjects Business Intelligence platform 4.0 User Guide http://help.sap.com/businessobject/product_guides/boexir4/en/xi4_lcm_user_en.pdf

http://service.sap.com/sap/support/notes/1155884http://help.sap.com/businessobject/product_guides/boexir4/en/xi4_lcm_user_en.pdfhttp://help.sap.com/businessobject/product_guides/boexir4/en/xi4_lcm_user_en.pdfhttp://help.sap.com/businessobject/product_guides/boexir4/en/xi4_lcm_user_en.pdf

www.scn.sap.com

how to configure lcm for ctsa248.g.akamai.net/n/248/420835/128f7ec9d82f50298b0681b8d...sap netweaver...

Documents