Enhanced CTS in close coupling configuration for portal environment
With CTS+ we can transport non-ABAP objects with the well-known transaction STMS, simplifying the change management procedure. This feature has been explained in the how-to guide How To Set Up and Use the CTS+ in a Portal Environment. Since the CTS server is updated to SPS13 there are new functionalities, including the close coupling configuration, that enables to attach an non-ABAP object to the CR “on-fly”.
After the CTS+ system configuration has been done as explained by the how-to guide, you can activate the new service provided by the SPS13. The transport organizer UI is an ABAP webdynpro application called CTS_BROWSER (not SODIS_CORE_WBO as in SPS12), now displayed in the STMS first screen:
Using the transaction SICF you have to activate the service, in the following service path: !https://weblogs.sdn.sap.com/weblogs/images/251874995/cts03.JPG|height=118|alt=image|width=476|src=https://weblogs.sdn.sap.com/weblogs/images/251874995/cts03.JPG|border=0!
After the configuration of the web service and the release of web service for SOAP runtime (transaction WSCONFIG), the next step is the Transport Domain Controller configuration.
h5. Java Transport Route
Log on the ABAP CTS+ server in client 000 (that acts as transport domain controller), after you create the non-ABAP systems (STMS Overview –> Systems (Shift-F6) –> Create –> Non-Abap System) and the transport route (Overview –> Transport Routes (Shift-F7) –> Edit –> Transport Layer –> Create), obtaining something as in the screen. !https://weblogs.sdn.sap.com/weblogs/images/251874995/cts02.JPG|height=132|alt=image|width=444|src=https://weblogs.sdn.sap.com/weblogs/images/251874995/cts02.JPG|border=0!
There are new parameters for non-ABAP, in our scenario for the systems JAD (development portal) should be:
And for the target JAQ
Some remarks: the directory C:usrsap
SYSglobalpcdExport is usually the folder where the portal exports the package file (epa file). With the WBO_GET_REQ_STRATEGY=SMART the source system creates a transport request (the so-called GENERATED REQUEST).
For quality and production system you have to add the SDM host and user/password, in the same screen which contains the TMS configuration, choose Goto –> SDM User.
h5. Connection to CTS+ server
You have to connect the CTS server to the portal and create an user mapping, following the procedure described in how-to guide (par. 4). After this, create the connection to the CTS server: open Visual Administrator of the development portal.
Choose Cluster –> Server –> Services –> Configuration Adapter.
Choose Configurations –> apps –> sap.com –>
tccom.sap.tmw.clients_ctsa_manager –> appcfg.How to Configure and Operate Enhanced CTS
SAP library – Change and transport system
[http://help.sap.com/saphelp_nw70/helpdata/en/3b/dfba3692dc635ce10000009b38f839/frameset.htm | http://help.sap.com/saphelp_nw70/helpdata/en/3b/dfba3692dc635ce10000009b38f839/frameset.htm]