ctsplus

8/6/2019 ctsplus

http://slidepdf.com/reader/full/ctsplus 1/32

SAP Netweaver COE Training

1

8/6/2019 ctsplus


CTS+ OverviewCTS+ Overview

Pre requisitesPre requisites

Components of CTS+Components of CTS+

Configuration of CTS+Configuration of CTS+

Different Implementation ScenariosDifferent Implementation Scenarios

DemoDemo

2

8/6/2019 ctsplus


CTS+ 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

Using CTS+ , non ABAP objects can be transported.

Transport routes can be setup and can be used for Java transports

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.

3

8/6/2019 ctsplus


4

8/6/2019 ctsplus


5

8/6/2019 ctsplus


To provide all the transport logistics & monitoring options that are wellTo provide all the transport logistics & monitoring options that are well

known from ABAP stack to Java transports as wellknown from ABAP stack to Java transports as well

Changes and developments can only be checked in to the transportChanges and developments can only be checked in to the transport

system after the changes and developments have become part of thesystem after the changes and developments have become part of the

central development landscapecentral development landscape

As this application is displayed in a browser window, the java developerAs this application is displayed in a browser window, the java developer

or administrator doesn’t have to go to the system that performsor administrator doesn’t have to go to the system that performs

transports to create a transport request but can use a web interfacetransports to create a transport request but can use a web interface

6

8/6/2019 ctsplus


7

CTS+ can run a dual stack system that has SPS 13 (or up) installed. SPSCTS+ can run a dual stack system that has SPS 13 (or up) installed. SPS

12 also offers CTS+ mechanisms, but SAP recommends to start with12 also offers CTS+ mechanisms, but SAP recommends to start with

SPS 14 as a lot of improvements have been introduced.SPS 14 as a lot of improvements have been introduced.

CTS+ can be divided between two servers: one providing the ABAPCTS+ can be divided between two servers: one providing the ABAP

stack and another one that has the Java stack installed.stack and another one that has the Java stack installed.

8/6/2019 ctsplus


1. CTS+ requires a system with a Java Stack and ABAP Stack in the

landscape. Its highly recommend to use a dual stack System as a domain

controller. The system support package state must be SPS 13 or higher.

2. The portals that are to form part of the transport route(s) need to have

at least SPS 9 or higher installed.

3. CTS Deploy Service on at least one AS JAVA system is the landscape is

required

8

8/6/2019 ctsplus


9

8/6/2019 ctsplus


Domain Controller (ABAP):Domain Controller (ABAP):

The domain controller is the system, where the TMS transport systems (ABAP

and non ABAP) with their transport layer and transport route are configured.

TMS Communication System (ABAP):TMS Communication System (ABAP): Communication system is the ABAP system where the transport program tp is

triggered to perform transport steps.

For Source Systems communication systems covers Transport Organizer Web

UI

For Target Systems the communication system triggers the tp together with

Deploy Web Service Client

10

8/6/2019 ctsplus


Deploy Web Service Client (ABAP):Deploy Web Service Client (ABAP): Needed on the ABAP side to enable the transport control program tp on SAP NetWeaver AS

ABAP to communicate with the CTS Deploy Web service on SAP NetWeaver AS Java. Consists of two configuration parts

HTTP Connection

Logical Port

Deploy Web Service (JAVA):Deploy Web Service (JAVA): Java Web service responsible for communicating with deployment/import services in the

non ABAP target systems.

The transport control program communicates with the CTS Deploy Web service when

importing/deploying non ABAP objects.

Transport Directory (ABAP):Transport Directory (ABAP): Directory to store the data and log files between transports.

ABAP stack writes the data files in that directory and the Deploy Web Service in the Java

stack reads to data files for imports to the target system.

In addition to the standard role of the transport directory for ABAP transports the transport

directory gets a new role for CTS+ non ABAP transports.

Here the data sub directory of the transport directory is needed to transport the non ABAP

files between the ABAP stack (tp/R3trans) and the Java stack (Deploy Web Service).11

8/6/2019 ctsplus


Transport Organizer Web UI (ABAP):Transport Organizer Web UI (ABAP): Web UI implemented as Web Dynpro ABAP application with basic SE09 functions to create

and maintain transport requests for non ABAP

CTS Export Client:CTS Export Client: Tight integration of CTS+ in the application of the source system where the non ABAP objects

are created (known as close coupling – available since SP Stack 14 for EP NWDI, SLD, PI,

KM); to enable this tight integration an RFC destination to the TMS communication system

Except for NWDI use case – here the NWDI server needs to be configured for tight integration,

not the non ABAP source system).

The Export Client communicates with the enhanced Transport Organizer to fetch a proper

transport requests and to attach the non ABAP objects directly within the application (e.g. EP

Content Studio – Export Wizard).

Import Service:Import Service: Import mechanism running on the target system (SDM, XI Import Tool, SLD Import, KM

Import, etc.)

During import of non ABAP objects the transport control program tp calls the Deploy Web

Service on the Java stack

Deploy Web Service triggers the CTS+ Import Service on the target system (e.g. SDM) to

deploy the transported objects.

12

8/6/2019 ctsplus


13

1. Logon to client 000

2. Start transaction WSADMIN . From the menu , choose goto

Administration settings

Enter the URL (http://<cts+ host>:5<SAP system number >00>) for the Java

stack of your CTS+ system.

Web Service Administration Settings :

8/6/2019 ctsplus


Check the CTS Deploy service as

follows :

Open a browser and enter the URL

for the Java Start Page in the CTS+

system (http://<host>:5<system

number>00>).

Navigate to Web service Navigator ,

check that the DeployProxy webservice is listed in the list of

deployed web servers on this server.

14

8/6/2019 ctsplus


Login to client 000.

Configure a Http connection, Go

to SM59 and select Http

connections to external server,

and then choose Create.

Create a new Http connection

with name ctsdeploy as an RFC

destination of connection type G.

Technical Settings:

Target Host : <Hostname>

Service No. : <Port

Number>

Path Prefix :

/DeployProxy/default?

style=document 15

8/6/2019 ctsplus


Go to Logon Security tab and

select basic Authentication as

the logon Procedure.

As a Logon User enter the

J2EE administrator user ID

(J2ee_admin)

Save the Changes.

Click on Connection test .

Confirm the Pop Up.

The value OK should Appear

for the status text .

16

8/6/2019 ctsplus


Go to Se06 , Select

System Change Option.Make sure that the global

settings are modifiable.

Click on the client

settings

Select 000 client and

Activating the option

Automatic recording of

changes and save thechanges.

17

8/6/2019 ctsplus


Logon to Client 000.

Go to the transaction

LPCONFIG,

In the proxy class field ,

Select,

CO_TFLDEPLOY_PROX

Y_VI_DOCUMENT

Logical port as

CTSDEPLOY

Click on the Create .

18

8/6/2019 ctsplus


Go to the Call parameters

Tab and enter‘CTSDEPLOY’ as the value

for the HTTP destination

field.

In the Path Suffix field enter

‘/DeployProxy/default?

style=document’

Save and Activate .

19

8/6/2019 ctsplus


Logon to 000 client .

Go to SICF , enter the

hierarchy Type as

SERVICE and Service

Name as

CTS_BROWSER.

Make sure that it is

active.

20

8/6/2019 ctsplus


Call Transaction

WSCONFIG enterSI_CORE_WBO_API as

the Service definition and

Variant as

SI_CORE_WBO_API and

click on create.

Save the changes.

This service is visible in

transaction WSADMIN.

21

8/6/2019 ctsplus


Configure the transport

routes between theSource and target

systems.

For a Non ABAP

system, Go to STMS in

the domain controller,

create a Non ABAP

system and establish

the transport routes.

22

8/6/2019 ctsplus


Login to Domain

Controller. Go to STMS.Click On

‘Overview’Systems.

Click on SAP

SystemCreate Stack.

Check the ‘Activate

Transport Organizer’ check

box. Enter the System ID

and client for which the

Transport Organizer shouldbe activated.

Click on Save and

distribute the

configuration.

23

8/6/2019 ctsplus


After activating the Transport

Organizer, the followingparameters are automatically

maintained in the DEV system

NON ABAP_WBO_CLIENT –

Client of the DEV system

WBO_GET_REQ_STRATEG

Y – Automatically creates a

transport request when you export

an object from the DEV system.

The following values are possible:

SMART:

TAGGED (Default)

24

8/6/2019 ctsplus


Go to stms in the domain

controller. Click on Overview

Systems

Select the target system. Click on

SAP SystemCreateJava Stack.

From the dialog box, select‘Activate Deployment Service’.

Select ‘SDM’ from the methods.

Enter the target host and system

number of the target system

Click on save. Enter the SDM

username and password of the target

system and click on ‘OK’

Distribute the configuration. 25

8/6/2019 ctsplus


The following parameters are

now automatically maintained

in the target systems.

DEPLOY_DATA_SHARE

DEPLOY_URL

DEPLOY_WEB_SERVICE

26

8/6/2019 ctsplus


27

8/6/2019 ctsplus


28

8/6/2019 ctsplus


29

8/6/2019 ctsplus


30

8/6/2019 ctsplus


31

8/6/2019 ctsplus


32

ctsplus

Documents