Using the Serverside Development Infrastructure Client (SAP Library - Using the Serverside Development Infrastructure Client)

Using the Serverside Development Infrastructure Client

Use

The Serverside Development Infrastructure Client (SDIC) is a service that provides a unified API for server-side development environments (SIDE) (such as Visual Composer) to allow them to interact with the System Landscape Directory (SLD) and the SAP NetWeaver Development Infrastructure (NWDI) through the landscape. This allows location and service transparency. Any SIDE which needs to have integrated versioning or build or logistics support from NWDI has to use the SDIC service. The following figure shows how the SDIC in the landscape:

This graphic is explained in the accompanying text

SDIC in the Landscape

Use the SDIC to encapsulate host libraries of the different NWDI servers (Design Time Repository (DTR), Central Build Service (CBS), Change Management Service (CMS)) and SLD. Note, that you can configure the SDIC service using its properties. For more information, see Configuring SDIC Properties.

Procedure

To be able to establish a connection between the server on which the SDIC is located and the server(s) on which the SLD and the NWDI are located, you must establish a secured Single Sign-On (SSO) connection between the two systems. Once the user is authenticated on the SDIC server, an authentication ticket is generated and is used for further authentication with any of the targeted servers. Therefore you have to establish a trust relationship between the AS Java running the SDIC service and the AS Java running the NWDI.

...

1. On the server where the NWDI is located, you have to configure the EvaluateTicketLoginModule login module with the following options:

Name	Value
Trustediss1	CN=<AS Java instance name on which the SDIC is deployed>
Trusteddn1	CN=<AS Java instance name on which the SDIC is deployed>
Trustedsys1	<AS Java instance name on which the SDIC is deployed>, 000
ume.configuration.active	true

2. Allow ticket logon for the following NWDI components, by setting the authentication stack to ticket.

To do that find these components and set ticket template as authentication stack:

○ sap.com/com.sap.lcr*sld

○ sap.com/tc.CBS.Appl*CBSWebService_CBSHttpSOAP

○ sap.com/tc.CBS.Appl*tc.CBS.Appl

○ sap.com/tc~SL~CMS~PCS*CMS

○ sap.com/tc~SL~CMS~PCS*CmsTransportAPIService_DefaultConfig

○ sap.com/tc~SL~CMS~TCSEar*TCS

○ sap.com/tc~dtr~enterpriseapp*dtr

3. Allow ticket logon for CBS Web Service.

To configure the CBS Web Service for SSO in the SAP NetWeaver Administrator tool, choose SOA Management → Application and Scenario Communication → Single Service Administration.

Browse to CBS Web Service and configure security to allow tickets logon.

4. The users logging into SIDE must also have the relevant permissions on the NWDI server to use its services for operations such as checkout (from DTR), activate (from CBS) and release (from CMS). You should also verify that these users have the required actions assigned to them for each of the NWDI servers. For more information, see Authorizations.

5. If you are using the LDAP server for user management, ensure that the SDIC user is available on the LDAP server.

For more information about configuring SSO connections, see Using Logon Tickets with AS Java.