Start of Content Area

Background documentation Basic SLD Configuration  Locate the document in its SAP Library structure

The SLD is configured during SAP NetWeaver Administrator installation. For more information about configuring SLD using SAP NetWeaver Administrator, see service.sap.com/instguides.

The SLD and the ACC reside together on an AS Java.

Register all the application services and computing nodes in the SLD to configure ACC.

This graphic is explained in the accompanying text

Before registering managed application services in the SLD, the affected systems must be virtualized (running on virtual hostnames). All the instances (CI, APP, SCS, and so on) of an application service must be up and running during the registration.

Register managed ABAP Application Services into SLD

Use RZ70 of the managed ABAP application service to register an ABAP engine of the managed AS Java in a central SLD. If the RZ70 is not available, the application service must be patched to the level where this transaction is available.

The two entries required needed to register the Technical Systems in the SLD are the hostname and the service of the used SAP Gateway.

·        The hostname of the used gateway (For example, cisgw0).

·        The name of the service for the Gateway (For example, sapgw42).

After Activate Current Configuration (F8) and Start Data Collection (F5), the application service is registered in the SLD.

If the field with the Data Collector Programs is empty, select Proposal to fill in the right programs.

If this action is successful the application service should appear in the SLD. Call the SLD using the following link:

http://<hostname>:5<system_number>00/sld

Navigate to Technical Landscape. The registered application services should appear in this list.

Register Managed Java EE Application Services into SLD

This graphic is explained in the accompanying text

The Visual Administrator is no longer part of WebAS 7.1. This functionality is replaced by SAP NetWeaver Administrator. For the new ACC, the registration is done using SAPNetWeaver Administrator. Refer the latest SAP NetWeaver Administrator documentation for more details.

To register the Java EE engine of a managed Java EE application service in a central SLD for WebAS 6.40, the Visual Administrator of this application service has to be used.

This graphic is explained in the accompanying text

Before registering managed application services in the SLD, the affected systems must run on virtual hostnames.

After registration, the application service should display the Send Result as Success. Additionally in the register Information tab, the application service is visible in the SLD in Technical Systems, AS Java.

For information on Java EE registration on the SLD, refer SAP note 673144.

If the Java EE registration fails, refer SAP note 885523.

More Information

If computer systems are incorrectly registered in the SLD, refer SAP note 979277.

If you have transferred the registration data of technical systems into the SLD and this data is not updated in the SLD, refer SAP note 1084145.

If a database system is registered incorrectly in the SLD, refer SAP note 1052457.

End of Content Area