SAP Netweaver COE Training

CTS+Overview Prerequisites ComponentsofCTS+ ConfigurationofCTS+ DifferentImplementationScenarios Demo

CTS+enhancedChangeandTransportSystem(CTS+)enablesyoutotransport JavaobjectsandSAPrelatednonABAPapplicationsinyoursystemlandscape, alongsideABAPobjects UsingCTS+,nonABAPobjectscanbetransported. TransportroutescanbesetupandcanbeusedforJavatransports

YoucantransporttheseobjectstogetherwithABAPobjectsinasingletransport request.WhenyourunimportsinTransportManagementSystem(TMS),the systemperformstheappropriatedeploymentstepautomatically.

Toprovideallthetransportlogistics&monitoringoptionsthatarewell knownfromABAPstacktoJavatransportsaswell Changesanddevelopmentscanonlybecheckedintothetransport systemafterthechangesanddevelopmentshavebecomepartofthe centraldevelopmentlandscape Asthisapplicationisdisplayedinabrowserwindow,thejavadeveloper oradministratordoesnthavetogotothesystemthatperforms transportstocreateatransportrequestbutcanuseawebinterface

CTS+canrunadualstacksystemthathasSPS13(orup)installed.SPS 12alsooffersCTS+mechanisms,butSAPrecommendstostartwith SPS14asalotofimprovementshavebeenintroduced. CTS+canbedividedbetweentwoservers:oneprovidingtheABAP stackandanotheronethathastheJavastackinstalled.

1.CTS+requiresasystemwithaJavaStackandABAPStackinthe landscape.ItshighlyrecommendtouseadualstackSystemasadomain controller.ThesystemsupportpackagestatemustbeSPS13orhigher. 2.Theportalsthataretoformpartofthetransportroute(s)needtohave atleastSPS9orhigherinstalled. 3.CTSDeployServiceonatleastoneASJAVAsystemisthelandscapeis required

DomainController(ABAP): Thedomaincontrolleristhesystem,wheretheTMStransportsystems(ABAP andnonABAP)withtheirtransportlayerandtransportrouteareconfigured. TMSCommunicationSystem(ABAP): CommunicationsystemistheABAPsystemwherethetransportprogramtpis triggeredtoperformtransportsteps. ForSourceSystemscommunicationsystemscoversTransportOrganizerWeb UI ForTargetSystemsthecommunicationsystemtriggersthetptogetherwith DeployWebServiceClient

10

DeployWebServiceClient(ABAP):

NeededontheABAPsidetoenablethetransportcontrolprogramtponSAPNetWeaverAS ABAPtocommunicatewiththeCTSDeployWebserviceonSAPNetWeaverASJava. Consistsoftwoconfigurationparts

HTTPConnection LogicalPort

DeployWebService(JAVA):

Java Web service responsible for communicating with deployment/import services in the nonABAPtargetsystems. The transport control program communicates with the CTS Deploy Web service when importing/deployingnonABAPobjects.

Directorytostorethedataandlogfilesbetweentransports. ABAPstackwritesthedatafilesinthatdirectoryandtheDeployWebServiceintheJava stackreadstodatafilesforimportstothetargetsystem. InadditiontothestandardroleofthetransportdirectoryforABAPtransportsthetransport directorygetsanewroleforCTS+nonABAPtransports. HerethedatasubdirectoryofthetransportdirectoryisneededtotransportthenonABAP filesbetweentheABAPstack(tp/R3trans)andtheJavastack(DeployWebService).

TransportDirectory(ABAP):

11

TransportOrganizerWebUI(ABAP):
andmaintaintransportrequestsfornonABAP

Web UI implemented as Web Dynpro ABAP application with basic SE09 functions to create

CTSExportClient:

TightintegrationofCTS+intheapplicationofthesourcesystemwherethenonABAPobjects

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

ExceptforNWDIusecaseheretheNWDIserverneedstobeconfiguredfortightintegration,

notthenonABAPsourcesystem). The Export Client communicates with the enhanced Transport Organizer to fetch a proper transportrequestsandtoattachthenonABAPobjectsdirectlywithintheapplication(e.g.EP ContentStudioExportWizard).

ImportService:

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

Import,etc.) During import of nonABAP objects the transport control program tp calls the Deploy Web ServiceontheJavastack Deploy Web Service triggers the CTS+ Import Service on the target system (e.g. SDM) to deploythetransportedobjects.

12

WebServiceAdministrationSettings: 1.Logontoclient000 2.StarttransactionWSADMIN.Fromthemenu,choosegoto Administrationsettings EntertheURL(http://<cts+host>:5<SAPsystemnumber>00>)fortheJava stackofyourCTS+system.

13

ChecktheCTSDeployserviceas follows:

OpenabrowserandentertheURL fortheJavaStartPageintheCTS+ system(http://<host>:5<system number>00>). NavigatetoWebserviceNavigator, checkthattheDeployProxyweb serviceislistedinthelistof deployedwebserversonthisserver.

14

Logintoclient000. ConfigureaHttpconnection,Go

toSM59andselectHttp connectionstoexternalserver, andthenchooseCreate.

CreateanewHttpconnection

withnamectsdeployasanRFC destinationofconnectiontypeG.
TechnicalSettings:

TargetHost:<Hostname> ServiceNo.:<Port Number> PathPrefix: /DeployProxy/default? style=document

15

GotoLogonSecuritytaband

selectbasicAuthenticationas thelogonProcedure.
AsaLogonUserenterthe

J2EEadministratoruserID (J2ee_admin)
SavetheChanges.

ClickonConnectiontest. ConfirmthePopUp. ThevalueOKshouldAppear

forthestatustext.

16

GotoSe06,Select

SystemChangeOption. Makesurethattheglobal settingsaremodifiable.

Clickontheclient

settings

Select000clientand Activatingtheoption

Automaticrecordingof changesandsavethe changes.

17

LogontoClient000. Gotothetransaction

LPCONFIG, Intheproxyclassfield, Select, CO_TFLDEPLOY_PROX Y_VI_DOCUMENT

Logicalportas

CTSDEPLOY

ClickontheCreate.

18

GototheCallparameters Tabandenter CTSDEPLOYasthevalue fortheHTTPdestination field. InthePathSuffixfieldenter /DeployProxy/default? style=document SaveandActivate.

19

Logonto000client. GotoSICF,enterthe

hierarchyTypeas SERVICEandService Nameas CTS_BROWSER.

Makesurethatitis

active.

20

CallTransaction

WSCONFIGenter SI_CORE_WBO_APIas theServicedefinitionand Variantas SI_CORE_WBO_APIand clickoncreate.

Savethechanges. Thisserviceisvisiblein

transactionWSADMIN.

21

Configurethetransport routesbetweenthe Sourceandtarget systems. ForaNonABAP system,GotoSTMSin thedomaincontroller, createaNonABAP systemandestablish thetransportroutes.

22

LogintoDomain

Controller.GotoSTMS. ClickOn OverviewSystems.

ClickonSAP

SystemCreateStack.
ChecktheActivate

TransportOrganizercheck box.EntertheSystemID andclientforwhichthe TransportOrganizershould beactivated.

ClickonSaveand

distributethe configuration.

23

AfteractivatingtheTransport Organizer,thefollowing parametersareautomatically maintainedintheDEVsystem

NONABAP_WBO_CLIENT

ClientoftheDEVsystem

WBO_GET_REQ_STRATEG

YAutomaticallycreatesa transportrequestwhenyouexport anobjectfromtheDEVsystem. Thefollowingvaluesarepossible: SMART: TAGGED(Default)

24

Gotostmsinthedomain

controller.ClickonOverview Systems
Selectthetargetsystem.Clickon

SAPSystemCreateJavaStack.
Fromthedialogbox,select

ActivateDeploymentService. SelectSDMfromthemethods.
Enterthetargethostandsystem

numberofthetargetsystem

Clickonsave.EntertheSDM

usernameandpasswordofthetarget systemandclickonOK
Distributetheconfiguration.
25

Thefollowingparametersare nowautomaticallymaintained inthetargetsystems. DEPLOY_DATA_SHARE DEPLOY_URL DEPLOY_WEB_SERVICE

26

27

28

29

30

31

32