Administrating ABAP+JAVA and SLD Problems of SAP PI 7.1

Transcription

1 Administrating ABAP+JAVA and SLD Problems of SAP PI 7.1 Applies to: SAP Basis and SAP PI 7.1 Administrations. For more information, visit the Application Management homepage. Summary This article describes how to analyze ABAP and Java stack related problems with SLD in PI and how to troubleshoot it. Author: Vikas B Jain Company: L&T InfoTech Created on: 5 January 2010 Author Bio Vikas B Jain is working at L&T InfoTech 2010 SAP AG 1

2 Table of Contents Table of Contents... 2 Introduction... 3 Java Components &SLD:... 3 Related Content Disclaimer and Liability Notice SAP AG 2

3 Introduction 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: The Net Weaver ABAP stack registers its system data, clients, components and soon using the settings in transaction RZ70 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: Enterprise Services Repository and Integration Directory start registration when the next tool (repository/directory) logon takes place after restart of theapplication Runtime Workbench registers automatically upon server restart (7.10 SP5 or later). Adapter Engine registers automatically upon server restart (7.10 SP5 orlater) Java Components &SLD: The Java components get the connection data for the SLD from Exchange Profile and establish a HTTP connection to the SLD to get connection or to execute the self registration at the SLD. To check the HTTP connection to SLD proceeds as follows: Navigate to the start/stop UI in the Net weaver Administrator: name>:<port> --> SAP Net weaver Administrator --> Configuration Management --> infrastructure --> SLD Data Supplier " 2010 SAP AG 3

4 2010 SAP AG 4

5 Go to Destinations, following screen will be displayed. 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 ABAP Components (IS and Integration Engines) & SLD: 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 SAP AG 5

6 2010 SAP AG 6

7 Apart from these we need to check whether self-registration of PI Components is working fine. If self registration is improper, the whole PI system will not work as expected. Below are the checks we need to perform for checking Registration of PI Specific components. 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 ->Technical System 2010 SAP AG 7

8 Select Technical System Type Process Integration 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: 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 totechnical Systems --> Process IntegrationSelect the components you want to delete, push "remove" button.. 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 Net weaver Administrator: name>:<port> --> SAP Net weaver Administrator --> Configuration Management --> infrastructure --> application modules 2010 SAP AG 8

9 2010 SAP AG 9

10 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 " 2010 SAP AG 10

11 For directory and repository, you still need to open the respective start page in order to trigger their registration: 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. Also check the following: Check the SLD settings in the Exchange Profile. Is the Business System for the integration server defined in the SLD. Are the technical PI users defined and authorized in the SLD system. The PI components need to connect to the SLD to get connection and landscape data and for the SLD selfregistration. The connection is setup differently for ABAP and Java components: 2010 SAP AG 11

12 Related Content For more information, visit the Application Management homepage SAP AG 12

13 Disclaimer and Liability Notice This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade. SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk. SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document SAP AG 13