17-05-2012, 01:30 PM
Best Practices for Implementing CTS+
cts+.pdf (Size: 3.13 MB / Downloads: 84)
Scenario
This guide explains the architecture and main components of the enhanced Change and Transport
System (short: CTS+). Chapter 3 gives an overview of the relevant CTS+ components and
configuration steps in general whereas chapter 4 discusses different system landscapes and gives
examples on how to configure simple and complex system landscapes supporting different use cases.
Prerequisites
The SAP NetWeaver Release of the system where the CTS+ relevant components are configured should be SAP NetWeaver 7.0 SP Stack 14 to follow this guide. Nevertheless this document should be a generic guideline in understanding the setup, configuration and usage of CTS+.
Further information:
•
See central SAP Note: 1003674
•
Standard documentation in the SAP Library: http://help.sapsaphelp_nw70/helpdata/en/...ameset.htm
•
Required/recommended expertise or prior knowledge:
Basic knowledge of ABAP Change and Transport System
Basic knowledge of Enhanced Change and Transport system
April 2008 1
Best Practices for Implementing CTS+
Enhanced CTS Configuration
To take advantage of the enhanced Change and Transport System several components and
configuration steps are needed. Chapter 3.1 gives an overview of the relevant CTS+ parts that need to
be setup, installed, activated or configured on the ABAP and JAVA stack of a CTS+ enabled system.
For the usage of CTS+ at least one ABAP and one JAVA stack is needed. The recommendation is to
use the SAP Solution Manager system, which is a dual stack system. CTS+ does not need any
Solution Manager functionality, it is a pure SAP NetWeaver technology. But the Solution Manager
system can act as central transport management system for the whole landscape (see chapter 4 for
more details).
This chapter describes the configuration of the CTS+ relevant components for one central system
(simplest case: a dual-stack system). In Chapter 3.1.3 the configuration steps are described for a
landscape where the ABAP stack and the JAVA stack are installed as different systems (SIDs) and
run probably on different hosts. Depending on the use case and system landscape, the CTS+
components will be distributed. This is discussed and explained in chapter 4.
After CTS+ is enabled, which means the CTS+ relevant server components are available and
configured, the different system landscapes need to be defined for the specific use cases (such as
Portal track or PI track). The definition of the systems for each landscape with its transport route is
done as TMS configuration which is described in 3.2.
Last but not least CTS+ is tightly integrated in the applications – like Enterprise Portal, SLD, PI – so
that the developer or content creator does not need to leave the application in order to be able to
attach the non-ABAP objects to a transport request. Chapter 3.3 will give an overview of that
configuration part.
CTS+ Components - Overview
This chapter explains the additional components and configuration steps that are needed to enable
the enhancements of a CTS system landscape to be able to transport non-ABAP objects. 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 enhanced CTS are
shown in Figure 1 and explained below. 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. Figure 1 is an 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. See chapter 3.1.1 and 3.1.2 for more details. Chapter 3.1.3
explains the configuration in case the ABAP and Java stacks do not run in the same system.