CTS+ Basic Introduction (1)

8/13/2019 CTS+ Basic Introduction (1)

1/9

INTERNAL USE ONLY

INTERNAL USE ONLY

CTS+ Configuration Basis

Information

Copyright 2010 FUJITSU CONSULTING INDIA

Pavan Kumar

Project: Birds Eye

Date: 26/05/2011


2/9

INTERNAL USE ONLY

INTERNAL USE ONLY

Agenda

Introduction SAP Applications supported by CTS+

How does CTS+ work within the different

applications? Loose coupling vs Close coupling

CTS+ ComponentsOverview

QA??

Copyright 2010 FUJITSU CONSULTING INDIA1


3/9

INTERNAL USE ONLY

INTERNAL USE ONLY

Introduction

What is CTS+ : CTS (Change and Transport System) is the transport capability of the SAP

NetWeaver AS ABAP. This capability has been enhanced and now, the transport of non-ABAP objectsis supported as well. The +' or enhanced' has been added to express this.

The Change and Transport System (CTS) helps you to organize development projects in ABAP

Workbench and in Customizing, and then transport the changes between the SAP systems in your

system landscape. As well as ABAP objects, you can also transport Java objects (J2EE, JEE) and

SAP-specific non-ABAP technologies (such as Web Dynpro Java or SAP NetWeaver Portal) in your

landscape.

The enhanced Change and Transport System (CTS+) enables you to transport Java objects and SAP-

related non-ABAP applications in your system landscape, alongside ABAP objects. You can also

administer non-ABAP systems in a CTS transport domain in SAP NetWeaver Application Server

ABAP.

What are the prerequisites for using CTS+? : CTS+ is available with AS ABAP and AS Java from

SAP NetWeaver SPS 12 onwards (both stacks are needed). We recommend that you start using

CTS+ with SPS 14. This is the requirement for the system which is used for transporting. The

applications that are to be used with CTS+ have very different requirements.



4/9

INTERNAL USE ONLY

INTERNAL USE ONLY

SAP Applications supported by CTS+

Transportable Objects

You can use CTS+ to transport the following additional objects:

Java-based and J2EE-based objects:

Software Component Archives (SCAs)

Enterprise Application Archives (EARs)

Software Deployment Archives (SDAs)

Objects from the SAP NetWeaver usage type SAP NetWeaver Portal (EP)

Enterprise Portal Archives (EPAs)

Enterprise Portal Applications (PARs)

Knowledge Management objects (KM Content and KM Configurations)

Non-ABAP objects from the SAP NetWeaver usage type PI (Process Integration):

Integration Builder objects (TPZs)

System Landscape Directory content objects (products, software components, technical systems,

and business systems)

You can transport these objects together with ABAP objects in a single transport request. When

you run imports in Transport Management System (TMS), the system performs the appropriate

deployment step automatically.



5/9

INTERNAL USE ONLY

INTERNAL USE ONLY

How does CTS+ work within the

different applications?

There are several How-To Guides and sections on SAP Help Portal which explain how CTS+ works

and what is the scope of the transports. You can find the how to guides on SDN by searching forCTS+ and the application name. Please make sure that the guide you are using fits with your release.

SAP NetWeaver Portal (EP)

Close couplingis described on the SAP Help Portal and is available since SAP NetWeaver 7.0 SPS

13. A How-To guidedescribes the configuration steps.

Loose coupling possible from SAP NetWeaver 2004 SPS 9 onwards.

Knowledge Management (KM)

Close coupling for Documentsis available since SAP NetWeaver 7.0 SPS 14

Lose coupling for KM documents is also available for SAP NetWeaver 7.0 SPS 13 if you use

the Transport of KM Contentprovided with SAP NetWeaver 7.0 SPS 13.

Close coupling for KM Configurationsis provided with SAP NetWeaver 7.0 SPS 14. This delivery

contains a small bug and works only with a fixed user. Take a look at SAP Note 1291022to learn

about the patch that you need for your SP to fix the issue. Loose coupling with earlier releases is only

possible via file system transport and would require a manual import.

SAP NetWeaver Exchange Infrastructure (XI / PI)

Information on functionality and appropriate releasesis provided on SAP Help Portal.

Here on SDN, you can find a HowTo Guide for SPS 14and a HowTo Guide for SPS 13of PI.

http://help.sap.com/saphelp_nw70/helpdata/EN/b6/d4cf196c774447bc66c7ad9c4d9841/frameset.htmhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b0ebf83b-6201-2b10-b58b-c14d3d3b6f61http://help.sap.com/saphelp_nw70/helpdata/EN/47/1c36bd433912b7e10000000a1553f7/frameset.htmhttp://help.sap.com/saphelp_nw70/helpdata/EN/46/9c97ed4e7d2c06e10000000a114a6b/frameset.htmhttp://help.sap.com/saphelp_nw70/helpdata/EN/47/1c36bd433912b7e10000000a1553f7/frameset.htmhttp://service.sap.com/sap/support/notes/1291022http://help.sap.com/saphelp_nw70/helpdata/EN/9a/775de286874bc78dcb1470bc80f0f9/frameset.htmhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/00246ec1-dec5-2a10-58b9-e111c091c00bhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/20965d21-6c93-2a10-d4a0-9f3c27a939fchttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/20965d21-6c93-2a10-d4a0-9f3c27a939fchttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/00246ec1-dec5-2a10-58b9-e111c091c00bhttp://help.sap.com/saphelp_nw70/helpdata/EN/9a/775de286874bc78dcb1470bc80f0f9/frameset.htmhttp://service.sap.com/sap/support/notes/1291022http://help.sap.com/saphelp_nw70/helpdata/EN/47/1c36bd433912b7e10000000a1553f7/frameset.htmhttp://help.sap.com/saphelp_nw70/helpdata/EN/46/9c97ed4e7d2c06e10000000a114a6b/frameset.htmhttp://help.sap.com/saphelp_nw70/helpdata/EN/47/1c36bd433912b7e10000000a1553f7/frameset.htmhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b0ebf83b-6201-2b10-b58b-c14d3d3b6f61http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b0ebf83b-6201-2b10-b58b-c14d3d3b6f61http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b0ebf83b-6201-2b10-b58b-c14d3d3b6f61http://help.sap.com/saphelp_nw70/helpdata/EN/b6/d4cf196c774447bc66c7ad9c4d9841/frameset.htm


6/9

INTERNAL USE ONLY

INTERNAL USE ONLY

System Landscape Directory (SLD)

Integration of CTS+ in SLDis available since SAP NetWeaver 7.0 SPS 13. Check SAP note 1101844for details on features and limitations for specific Service Packs.

SAP NetWeaver Development Infrastructure (NWDI)

Integration of CTS+ in NWDIis available since SAP NetWeaver 7.0 SPS 14.

SAP NetWeaver Master Data Management (MDM)Loose coupling is planned to be provided with SAP NetWeaver Master Data Management 7.1 and

SAP enhancement package 1 for SAP NetWeaver 7.0 for the CTS system.

SAP NetWeaver Business Intelligence (BI)

If you would like to transport BI objects, this is either a question of transporting Portal content or ABAP

objects. There is no special guide for BI available, so please take a look at the objects that you'd like

to transport and use the appropriate guide or help pages.

http://help.sap.com/saphelp_nw70/helpdata/EN/47/3cc1147a4220cae10000000a155369/frameset.htmhttp://service.sap.com/sap/support/notes/1101844http://help.sap.com/saphelp_nw70/helpdata/EN/47/133e4dad483127e10000000a1553f7/frameset.htmhttp://help.sap.com/saphelp_nw70/helpdata/EN/47/133e4dad483127e10000000a1553f7/frameset.htmhttp://service.sap.com/sap/support/notes/1101844http://help.sap.com/saphelp_nw70/helpdata/EN/47/3cc1147a4220cae10000000a155369/frameset.htm


7/9INTERNAL USE ONLYINTERNAL USE ONLY

Loose coupling vs Close coupling

Loose Coupling and Close Coupling (or tight integration) describe the relation between the TMS

system and the application on the export side.

Close coupling means that you can find mechanisms within an application (e.g. SAP NetWeaver

Portal or SAP NetWeaver Development Infrastructure to attach a transportable object (e.g. epa,

sda,...) to a transport request on the CTS system.

Loose coupling means that the application does not provide a direct integration mechanism. Youwould start an export within the application, download the export result and attach it manually to a

transport request via the Transport organizer Web UI by uploading it again.

In most cases, the import is done automatically. This means that when importing a queue TMS calls

the deployment tool of an application and hands over the files. The import is done automatically; no

administrator's interaction is required. In some cases, the exported file is delivered to a designated

destination and the import itself needs to be done manually. This is the case for a KM Documents'import by today. SAP Master Data Management plans to offer a CTS+ integration with MDM 7.1 as

well - this integration also requires a manual import.




CTS+ Components - Overview

The main concepts of the Change and Transport System (such as TMS systems, transport layers,

transport routes) are still valid and required for a CTS+ landscape. The main parts of the enhancedCTS are shown in given screenshot. The decision where to configure these components depends on

the use case (such as PI, EP, NWDI) and system landscape especially when a complex system

landscape needs to be enabled for CTS+ functionality.

Example:for a central dual-stack system that acts as domain controller for a non-ABAP landscape.

Here all server components are configured within the same system.




QA??
