Symptom
One is implementing a CTS+ scenario (TMS - CM Services), in order to transport Non-ABAP customization source code throughout the NW AS Java system landscape. In the configuration step of Development System in the TMS, the CTS type Development Configuration is not possible to be neither created or edited. The Development Configuration of type "CTS System" is not created in the NWDI - CM Services.
In the NWDI - CM Services the local SLD is displayed in tab System Landscape Directory. This particular data might not be neither edited nor saved. The SLD URL (local for the NWDI) that is displayed in the CM Services is NOT configured anywhere in the STMS transaction.
The SLD URL configured in the Development Configuration in the TMS is valid and accessible (with the configured user in STMS transaction) when one opens it in a browser session. This SLD URL is "external" - it is on a different server box from the one where the NWDI - CM Services is running.
Read more...
Environment
SAP NetWeaver Development Infrastructure - CM Services,
SAP NetWeaver ABAP - Transport Management System - transaction STMS,
External SLD (for NWDI - CM Services) is being used in this scenario!
Product
Keywords
Unable, Register, DI Config Service, STMS, TMS, CM Services, NWDI, CTS+, SLD URL, local, external, remote, User/Password, Development configuration , KBA , BC-CTS-CMS , Change Management Service , BC-CCM-SLD , System Landscape Directory / Component Repository , BC-CTS-TMS-CTR , Central CTS - Transport Management , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.