Adapters not showing in Adapter monitorin

[former_member185845]

Dear Collegues,

we have upgraded from SP14 to Sp17 for our XI.

Unfortunately, we were unable to view the adapters provided by SAP in Runtime work bench.

PATh

RWB:->Component Monitoring->Adapter Monitoring->List of Adapters .

Can anyone help out of this issue.

Regards

Chandra SHekar

T-Systems India Limited.

[Former Member · Accepted solution]

Hi Chandra,

This may be because of inconsistencies in SLD. Please check OSS note 764176 for this. it has listed out a number of possible solutions for this issue. I have pasted them below. However I would recommend reading the entire OSS notes.

Solution steps:

1. In the SLD editing interface, choose "Administration" -> "Content Maintenance". Select "XI Integration Server" from the drop-down menu, and navigate to the associations of the integration server. Select the "XI Integration Server Logical Identity" association and delete the association by choosing 'Remove'.

2. Switch to "Home" in the "Technical Landscape" view, and select the "Exchange Infrastructure" technical system type there. Select all domains and XI components for the host and delete these by selecting them and pressing 'Remove'.

3. Restart the J2EE server. After you restart the server, the XI components log on to the SLD again and create a new entity of class "XI Integration Server".

4. To register the directory and repository again, you must also log on to the two tools.

5. In the "Technical Landscape" --> Technical System Type "Exchange Infrastructure" view, check whether all XI components are logged on correctly (Adapter Engine, Integration Directory, Integration Repository, Integration Server and Runtime Workbench/RWB). The Adapter Engine components may be missing. If so, stop and restart in the J2EE Visual Admin --> Server --> Services, and deploy application sap.com/com.sap.aii.af.cpa.app.

6. Change again to the administration interface --> content maintenance for the associations of the XI Integration Server.

Create a new association by pressing the 'New Association' button, select the "XI Sub-System viewed Application System" association type here, and in the next step choose the BC system for the Integration Server. Save the association by choosing 'Associate'.

Create a new association by pressing the 'New Association' button, select the "XI Integration Server Logical Identity" association type here, and in the next step choose the business system for the Integration Server. Save the association by choosing 'Associate'.

7. In the "Technical Landscape" --> Technical System Type "Exchange Infrastructure" view, check whether the assignment to the application system is also displayed there (the business system in which the Integration Server is running should appear in the "Application System" column for the Integration Server).

8. To make the changed associations known in the directory, the SLD temporary storage must be deleted in the directory. To do this, log on to the Integration Directory and choose 'Environment --> Delete temporary storage areas for SLD data'.

regards.

Ruchit

[former_member185845 · Accepted solution]

Dear Ruchit Khushu,

I tried as per OSS note 764176 which you has mailed me.But its not working i mean same result we are unable to see the adapters.

[Former Member · Accepted solution]

Try this. I had a similar problem...

re-import the XI Content for Software Component Version SAP Basis 6.40 SP17.

1. Copy XI3_0_SAP_BASIS_6.40_17_00.tpz to directory /usr/sap/<SAPSID>/SYS/global/xi/repository_server/import/

2. On your SAP XI host, call transaction SXMB_IFR.

3. Choose Repository (Design).

4. Choose &#8594; Tools &#8594; Import Design Objects

2. Choose the file /usr/sap/<SAPSID>/SYS/global/xi/repository_server/import XI3_0_SAP_BASIS_6.40_15_00.tpz

5. Import the file.

Performing Initial Adapter Engine Cache Refresh

Perform the initial cache refresh of the Adapter Engine by executing the following URL:

http://<host>:<Java-Port>/CPACache/refresh?mode=full

Where <host> is the Adapter Engine host and <Java-Port> is the HTTP port of the J2EE engine (The following naming convention applies: 5<Java_instance_number>00. 50000, for example, if your Java instance is 00).

Log on data: XIDIRUSER with password

Check that the response indicates that the cache refresh has been successfully executed.

This should enable the adapters in adapter monitoring....

[former_member185845 · Accepted solution]

Dear Barry Neaves,

Thanks for your solution ,it worked well.

Regards

chandra Shekar

T-Systems India Limited

SAP XI-TeamLead

[Former Member · Accepted solution]

I'm glad your problem is resolved.

Best wishes for the future.

[Former Member]

Just a note of thanks to Barry - just been facing the same problem since a Hot Pack installation and your advice in this thread has really saved our bacon. Cheers.