Skip to Content

This blog provides detailed information about how to check if the connection to the SLD works correctly and how to analyze SLD Self-Registration problems. The connection to the SLD is a vital part of PI during development as well as during runtime. Among other things, a working connection to the SLD is needed to: 

    • Assign business systems in the Integration Directory

    •   Provide input help for interfaces in the Integration Directory

    • Send messages from the Adapter Framework to the Integration Server

 Carry out a cache refresh either from the Integration Directory or the ABAP runtime cache (transaction SXI_CACHE)

After setup of PI system through upgrade, installation or restart, PI components may not be completely registered in the System Landscape Directory (SLD). This may lead to inconsistencies into SLD.

 

They are as follows:·        

0.1. The Net Weaver ABAP stack registers its system data, clients, components and soon using the settings in transaction RZ70  

0.2. The Net Weaver Java stack registers its system data, services, applications and products using the settings in Java service SLD Data Supplier.            

          Specific PI registrations are done from the PI Java components:·          

0.1. Enterprise Services Repository and Integration Directory start registration when the next tool (repository/directory) logon takes place after restart of theapplication  

0.2.   Runtime Workbench registers automatically upon server restart (7.10 SP5 or later).

0.3. Adapter Engine registers automatically upon server restart (7.10 SP5 orlater)        

If the self-registration does not work properly the whole PI system will not work as expected. 

Components after successful self-registration:

After successful self-registration, all PI components should be found in the SLD and grouped together in one XI Domain. To check this go to http://:/sld ->Technical System

 

!https://weblogs.sdn.sap.com/weblogs/images/251884394/15.JPG|height=301|alt=image|width=695|src=https://weblogs.sdn.sap.com/weblogs/images/251884394/15.JPG|border=0!_src=“”

 

Select Technical System Type ‘Process Integration’

 

 

image

 

The components Integration Directory, Enterprise Services Repository, Integration Server, RWB, several adapter engines and the XI Domain itself have to be found, *the *domain names have to match exactly  

* Error Analysis: :</p><p>If some of the PI components Adapter Engine, Directory, Repository or Runtime Workbench are missing in the table, you need to explicitly register those as described below. If they appear in the table, but are not assigned to a domain, you have to delete them and register them explicitly. </p><p> Deleting PI components:</p><p>Navigate toTechnical Systems –> Process IntegrationSelect the components you want to delete, push “remove” button.</p><p>Note: Do not accidentally delete the XI IntegrationServer. </p><p>Triggering SLD Registration of PI components: </p><p>You can trigger registration of a PI component by restarting the associated application. Navigate to the start/stop UI in the Net weaver Administrator: </p><p style=”margin: 0in 0in 0pt; line-height: normal” class=”MsoNormal”>!!:<port>%20>%20SAP%20Net%20weaver%20Administrator%20>%20Configuration%20Management%20>%20infrastructure%20>%20application%20modules” border=”0″ alt=”” width=”1″ height=”1″ />http:<host name>:<port> –> SAP Net weaver Administrator –> Configuration Management –> infrastructure –> application modules</p><p style=”margin: 0in 0in 0pt; line-height: normal” class=”MsoNormal”> </p><p style=”margin: 0in 0in 0pt; line-height: normal” class=”MsoNormal”>!https://weblogs.sdn.sap.com/weblogs/images/251884394/3c.JPG|height=312|alt=image|width=601|src=https://weblogs.sdn.sap.com/weblogs/images/251884394/3c.JPG|border=0!</p><p style=”margin: 0in 0in 0pt; line-height: normal” class=”MsoNormal”> </p><p style=”margin: 0in 0in 0pt; line-height: normal” class=”MsoNormal”> </p><p style=”margin: 0in 0in 0pt; line-height: normal” class=”MsoNormal”>!https://weblogs.sdn.sap.com/weblogs/images/251884394/4a.JPG|height=width: 599px; height: 186px|alt=image|width=602|src=https://weblogs.sdn.sap.com/weblogs/images/251884394/4a.JPG|border=0!</p><p style=”margin: 0in 0in 0pt; line-height: normal” class=”MsoNormal”> </p><p style=”margin: 0in 0in 0pt; line-height: normal” class=”MsoNormal”> </p><p style=”margin: 0in 0in 0pt; line-height: normal” class=”MsoNormal”> </p><p style=”margin: 0in 0in 0pt; line-height: normal” class=”MsoNormal”> </p><p style=”margin: 0in 0in 0pt; line-height: normal” class=”MsoNormal”>!https://weblogs.sdn.sap.com/weblogs/images/251884394/5a.JPG|height=367|alt=image|width=620|src=https://weblogs.sdn.sap.com/weblogs/images/251884394/5a.JPG|border=0!</p><p style=”margin: 0in 0in 0pt; line-height: normal” class=”MsoNormal”> </p><p> Here you restart the applications for the missing PI components: </p><ul><li>com.sap.xi.directory (Integration Builder/Configuration)</li><li>com.sap.aii.af.app (Adapter Engine)</li><li>com.sap.xi.rwb (Runtime Workbench) </li><li>com.sap.xi.repository (Integration Builder/Design </li></ul><p> ” !https://weblogs.sdn.sap.com/weblogs/images/251884394/6a.JPG|height=351|alt=image|width=624|src=https://weblogs.sdn.sap.com/weblogs/images/251884394/6a.JPG|border=0!</p><ul><li><p style=”margin: 0in 0in 0pt; line-height: normal” class=”MsoNormal”>For directory and repository, you still need to open the respective start page in order to trigger their registration:</p><p>http:///dir</p><p>http://Note:The registration with SLD may show errors in particular under the following conditions, which should be tackled as described: 

0.1.    If the J2EE server consists of more than one application server, it is recommended to restart the PI applications (as described above) on one application server only, not on all application servers simultaneously. This avoids potential interferences during writing to SLD. 

Also check the following: 

0.1. Check the SLD settings in the Exchange Profile.

0.2. Is the Business System for the integration server defined in the SLD.

0.3. Are the technical PI users defined and authorized in the SLD system. 

0.4.

The PI components need to connect to the SLD to get connection and landscape data and   for the SLD self-registration. The connection is setup differently for ABAP and Java components:

Java Components:Make sure that the URL points to the Host name of the respective PI system.If the URL value is maintained wrongly, entire self registration goes wrong and the PI system will not work properly

!https://weblogs.sdn.sap.com/weblogs/images/251884394/113g.jpg|height=361|alt=image|width=616|src=https://weblogs.sdn.sap.com/weblogs/images/251884394/113g.jpg|border=0

 

ABAP Components (IS and Integration Engines):+ +The ABAP runtime provides the transaction SLDCHECK as a very useful tool for testing the SLD access. Log on to the client of the Integration Server and start this transaction. 

The transaction consists of three parts: 

1) Logging on to the SLD using a browser

2) Testing the SLD access itself

3) Testing the exchange profile  

Following screen will be displayed.

image

 

 

!https://weblogs.sdn.sap.com/weblogs/images/251884394/143g.jpg|height=450|alt=image|width=489|src=https://weblogs.sdn.sap.com/weblogs/images/251884394/143g.jpg|border=0!</body>

To report this post you need to login first.

10 Comments

You must be Logged on to comment or reply to a post.

  1. Prateek Raj Srivastava
    Thanks Vikas for this detailed blog and a good learning material.

    Your Note was interesting
    >>Note: Do not accidentally delete the XI IntegrationServer
    For those who intentionally prefer accidents 🙂

    Keep it up!!

    Best Regards,
    Prateek

    (0) 

Leave a Reply