Adapters not found!

Question

Hi,
I couldnt able to see any adapters other than JPR.our basis guy imported BASIS package ,I could see Basis component in IR.we did CPA Cache full refresh but still we didnt see any adapters in RWB ->Adapter monitoring.
he imported Basis pkg that he downloaded from service market place.
or does it need to be export BASIS SWCV in SLD and import that into IR as .tpz?
or either of them is fine?
thank you,
babu

Answer 1

hi
May this will be useful to u.
notes:
764176
804124
SXI_CACHE
Solution
In the Runtime Workbench in the Component Monitoring (hierarchy display),
check whether all expected components are listed completely.
The integration server is usually missing in the case of inconsistencies caused by the upgrade.
Under 'Technical Landscape' in the SLD, select the "Exchange Infrastructure" technical system type.
Check whether all XI components of the same XI domain are assigned and whether there are several XI domains for the server.
There may be two domains with similar names, one with a fully-qualified host name and one with a short host name.
This is an inconsistency.
Often, the integration server and another XI component
(directory, repository, or adapter engine) are not assigned to the same domain either.
You can solve the inconsistencies as follows:
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'