Symptom
After setup of PI or non-central adapter engine 7.10 SP4 through upgrade, installation, system copy or restart, PI components may not be completely registered in the System Landscape Directory (SLD). This may lead to symptoms such as
PI landscape not displayed completely in the Runtime Workbench
errors during directory cache update
errors during messaging
Other terms
PI, XI, self registration, SLD, upgrade
Reason and Prerequisites
Right after start-up of the J2EE engine, the PI components automatically register with the associated SLD. During this process lock conditions may cause incomplete or inconsistent structures in SLD.
Solution
Checking completeness and consistency of SLD
First check whether the PI structures in SLD are incorrect. Start the SLD user interface (http:<host name>:<port>/sld), navigate to
Technical Systems --> Process Integration
For a correct PI registration, the tabular display of the PI structure must contain the following entries:
- One entry for the domain of the Integration Server
- One entry for each PI component: Integration Server, Adapter Engine, Directory, Repository and Runtime Workbench (RWB). Each must be assigned to the domain above, i.e. the domain name must appear in column "Domain".
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.
Deleting PI components
Navigate to
Technical Systems --> Process Integration
Select the components you want to delete, push "remove" button.
Beware: Do not accidentally delete the XIIntegrationServer.
Triggering SLD Registration of PI components
You can trigger registration of a PI component by restarting the associated application. Navigate to the start/stop UI in the Netweaver Administrator:
http:<host name>:<port> --> SAP Netweaver Administrator --> Configuration Management --> infrastructure --> application modules
Here you restart the applications for the missing PI components:
com.sap.xi.directory (Integration Builder/Configuration)
com.sap.aii.af.app (Adapter Engine)
com.sap.xi.rwb (Runtime Workbench)
com.sap.xi.repository (Integration Builder/Design)
For directory and repository, you still need to open the respective start page in order to trigger their registration:
http://<host>:<port>/dir
http://<host>:<port>/rep
Check the PI structures in SLD again.
Note:
The registration with SLD may show errors in particular under the following conditions, which should be tackled as described:
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.
If the Exchange Profile contains the non-empty property
com.sap.aii.connect.integrationserver.r3.mshost
then it should also contain the property
com.sap.aii.connect.integrationserver.sld.name
as described by note 1093249. This avoids concurrent use of the CIM Client of SLD.
