Adapter types & comm. channels missing in comm channel monitoring

Hello All,
We recently created a new sandbox XI system from a copy of our XI Test system
system. We used the SAPinst system copy process for ABAP+JAVA to create
this new XI sandbox system. We have followed all of the XI/PI post copy procedures listed in the system copy documentation and almost everything is working except when we going into the runtime workbench for XTX and go into communication channel monitoring for the adapter engine. When we get
here we do not see any adapter types where we should be seeing types such
as JDBC, BD, CIDX, FILE, JMS, etc We also do not see any communication channels in the communication channel monitoring if we select use filter to display all.
Any ideas?
Any help on this would be much appreciated
With regards
Steven

Hi,
First check in Integration Directory. Just create any dummy Communication Channel, if you are able to select your adapter for your communicatio channel then this is a cache issue. Just refresh the CPACache by this url.
http://<server name>:<HTTP Port>/CPACache/refresh?mode=full
Else you are not able to select any adapter for your communication channel then you have forgot to import the SAP BASIS Software Component Version into Integration Repository.
You can find it from your installation DVD's, and if you are not able to find then you can download it from service market place as given below..
[Click on this URL|https://websmp205.sap-ag.de/~form/handler?_APP=00200682500000001943&_EVENT=SEARCH&HIDE=&SEARCH_SPAT=X&SEARCH_BPAT=X&SEARCH_CD=X&SEARCH_P=X&SEARCH_PV=X&SEARCH_C=X&SEARCH_CV=X&SEARCH_TA=&SEARCH_V=&HIDE_EXPERT_SEARCH=X&SEARCH_MAX_RESULT=20]
In Search Term Enter SAP BASIS 7 or 3.
Now click on XI CONTENT SAP_BASIS 7.00 (if u r using PI else select SAP_BASIS 3.0) -
>
Database independent -
> SAPBASISxxxxx-0888.ZIP (this file should be based on your SP level)
Just save this file on your machine and unzip it.
Now put this in the import directory: \usr\sap\<SID>\SYS\global\xi\repository_server\import\
Now login to Integration Repository and from menu TOOLS ---> Import design objects and import it.
Regards,
Sarvesh

Similar Messages

Unable to see audit log in Adapter Engine (Communication channel monitoring

Hi
I am unable to see audit log in Adapter Engine (Communication channel monitoring).
Could please suggest what parameter to set to display in PI 7.0 visual administrator.

/people/kenny.scott/blog/2009/03/08/pi-71-af-messaging-system-audit-log-persistence
Did you tried this paramter even though the above is applicable for PI 7.1
Rajesh

FQDN problem in adapter engine,communication channel monitoring

Hi all,
Recently i configured FQDN for PI system while configuring END to END monitoring. Everything is going fine and end to end monitored worked smoothly.
But Problem started in comminuication channel monitring.adapter engine status and others. Because its trying to retrieval the URl without FQDN and its showing an error as requested resource does not exist.
I changed the exchange profile paramters also. But still i am afcing the problem.
So,please suggest me to overcome from this issue.
Regards
Vijay

/people/kenny.scott/blog/2009/03/08/pi-71-af-messaging-system-audit-log-persistence
Did you tried this paramter even though the above is applicable for PI 7.1
Rajesh

Error in Channel / showing in Channel monitor

Hi All,
- I have a receiver channel defined with a custom XI adapter.
- The channel monitoring now says: Status=removed, Text=No adapter registered for this channel
- The consequences of this are, error in message processing
The adapter is there, but:
- I reinstalled the adapter recently, using sdm and the action sequence undeploy, deploy
Question to the experts:
- What can I do to make my new adapter version known again to my channel?
Thanks a Lot

Hi,
Hi,,
2 Introduction
Configuring IDoc adapter in Exchange Infrastructure 3.0 requires some configuration on the SAP
systems, for both XI and the backend system where the IDoc message is to be sent. These steps, although
simple, are many times missed or mis-configured, causing the delivery of messages to fail.
Since IDoc adapter uses the ABAP stack, instead of J2EE, the configuration requirements are mainly in
ABAP.
Setting up IDoc adapters requires the XI integration server to be able to communicate with the backend
SAP system, and also to make sure that the Logical System Name used when posting IDoc exists on the
backend SAP system.
3 The Step By Step Solution
The basic steps for the IDoc configuration are outline below:
1. Configure SM59 on XI to communicate to SAP backend system.
2. Configure port on XI for IDoc communication.
3. Create or verify the Logical System Name on the SAP backend system.
4. Create or verify business system in XIs System Landscape Directory.
5. Verify the Logical System Name of the business system.
6. Verify or add the Logical System Name for the sender business system.
7. Create/configure the Communication Channel for the IDoc receiver adapter
3.1 Configure SM59 on XI to communicate to SAP backend system.
1. Using transaction SM59, create an RFC destination with Connection Type = 3.
In this example, the RFC destination name is NDVCLNT510.
2. Enter the logon information:
3. Test the connection by clicking on Testing connection and Remote logon.
Both must be successful.
3.2 Configure port on XI for IDoc communication.
4. Go to transaction IDX1 on XI, and create a port. In this example, the Port name is SAPNDV.
The Port name must be in the form of SAPxxx, where xxx is the system ID of the backend SAP
system.
The Client must be the client number of the backend SAP system.
Select the RFC Destination which was created in the previous step.
3.3 Create or verify the Logical System Name on the SAP backend system.
5. Enter transaction SALE on the SAP backend system.
6. Create or verify the Logical System Name. In our example, NDVCLNT510 is verified.
3.4 Create or verify business system in XIs System Landscape Directory.
The business system name for the SAP backend system must contain a valid Logical System Name. This Logical System Name is the one verified or created in the previous step.
7. In the System Landscape Directory, select the SAP backend business system. If one does not exist, then create the business system. Verify the Logical System Name.
3.5 Verify the Logical System Name of the business system.
8. In the Integration Directory, doubleclick on the business system (in our example, it is NDVCLNT510).
Navigate the menu:
Service Adapter Specific Identifiers.
If information is empty or incorrect, then it will have to be synchronized with the content of the System Landscape Directory. Follow the steps below for synchronization.
9. (Optional) Synchronization of the business system in Integration Directory to the business system in System
Landscape Directory.
Double-click on the business system in the Integration Directory.
Switch to Edit mode.
Select menu: Service Adapter-Specific Identifiers
10. (Optional) Within the dialog box, click on the button as indicated below to resynchronize.
11. (Optional) If the expected data from the System Landscape Directory is not updated, then the SLD cache may need to be cleared first.
3.7 Create/configure the Communication Channel for the IDoc receiver adapter.
15. In the Integration Directory, create an IDoc receiver communication channel.
The RFC Destination is from step 3.1.
The Port is from step 3.2.
NOTE:
There is no need to create an IDoc sender Communication Channel for XI. Instead, the backend SAP system must be configure to send the IDoc to XI.
4 Appendix
Transaction: IDX2
There are a couple of situation where IDX2 can be useful on the XI system.
1. When we want to test connection between the XI and SAP backend system.
2. When an IDoc has changed, and the meta data stored in XI needs to be update. When an IDoc is sent from the SAP backend system to XI, XI will first check to see if the meta data for the IDoc is already in its persistent cache. If not, then XI will use the configuration in IDX1 to retrieve the IDoc meta data from the backend system. If the
meta is already in cache, then it will NOT do so. Therefore, when an IDoc has changed, it is necessary to manually update the new meta data on XI, or delete it from the cache, so that the latest version can be retrieved. IDX2 is used for this purpose.
Go to transaction IDX2 and click on Create.
Enter the IDoc Type and the Source Port as defined in step #2. Click Continue.If successful, the following will show up. If error occurs, then the IDX1 configurations will need to be re-checked.
Reward points if find useful.

Communication Channel Monitoring not showing up Communication Channels

Hi All,
PI 7.1 : I have created Communication Channel using File Adapter in ID and activated it. Adapter engine is Central Adapter Engine. But in Runtime Workbench I am not able to see communication channels created under Component Monitoring -> Adapter Engine -> Communication channel Monitoring. Please let me know what is the problem.
And in ID I am getting below warning message for that Communication Channel.
Message: Unable to Check Whether Communication Channel is compatible with selected Adapter Engine since version information for Adapter Engine is missing in SLD.
Any idea? I appreciate your quick help.
Thanks,
Carl

Hi Abhishek,
I have selected inID , File dapater software component SAP BASIS 7.11 name space http://sap.com/xi/XI/System, adapter "file " is in that name space in ESR. In ESR there is only one BASIS Software Component SAP BASIS 7.11.
Thanks,
Carl

Communication Channel monitoring in PI 7.1

Hi Folks,
How to do the adapter monitering & Communication channel monitoring in teh sap PI 7.1.
Regards,
Santosh

Hi,
Have you searched in SDN,??
there is no difference compare to other versions
RWB-->ComponentMonitoring>Adapter Engine->Communication channel monitoring--->select communication Channel.fileter,then monitor it.
Regards,
Raj

Problem in Communication channel monitoring..

Dear friends,
I am facing a problem in Communication channel monitoring.
Problem:
I have designed several communication channels in the Integration directory.
To check the status of channel i will go to RWB->Component Monitoring->Adapter Engine->Communication channel monitoring, then we have a selection screen to filter out the channel, adapter,etc..
Here i am NOT seen any channels to filter out. I.e. Channels in the Integration directory are not reflecting here.
Can you please help out on this?

HI,
Do the CPACache refresh .
ALso check this SAP Note- 937382
Regards,
Moorthy

No Adapter Types in Comm. Channels -- Urgent Pls

Guyz,
I'm a newbie and when i'm trying to follow a 'how to sample idoc' scenario doc, i tried creating a communication channel...even i tried using creating comm. channels with wizard, but i got a wierd error as follows :
"com.sap.aii.ib.core.roa.RoaObjectAccessException: Attempt to read object Adapter Metadata IDoc .......from application REPOSITORY failed......." ...and a very huge java exception.....
later after i did a bit of searching over this forum and sap help, i found a document on marketplace detailing the tests to check our XI system is ready or not (doc name is Readiness_Check_Version3.pdf)... as suspected one of the test for adapters failed....In Adapter Monitoring section of Runtime Workbench, i'm not able to see any adapters other than JPR ...... which is why i suppose no F4 is turning up for adapter type in communication channel....
further more searching on this forum, showed me some hints for downloading XI Content from marketplace to update IR.....Firstly i'm not sure this is the solution, if it is, what all components needs to be downloaded.... can i just download SAP_BASIS 7.00 ? in my system i even have 'SAP BASIS 7.10'.... 'm in utter confusion....
appreciate a quick reply on this with details (pls let me know how to check which SP level is my XI system is installed ? , if i have to download XI Content from mkt place).
thanks a ton in advance
Sreedhar K

Hi,
Can you please check this steps:
a) Reimport the latest version of the SAP Basis Software Component into the Integration Repository. The adapter metadata is contained in that SWC, under the namespace http://sap.com/xi/XI/System
b) Just try with Visual Administrator to check the services for the adapter engine are running or not. All services starts with SAP XI..
SAP XI AF Core
SAP XI AF CPA Cache
SAP XI AF Messaging
SAP XI Adapter XI
SAP XI AF Security
c) Just go thru following link from service.sap.com
https://websmp103.sap-ag.de/~sapdownload/011000358700002757652005E/HowtoMintorAF.pdf
d) In the last Refresh the cache of the Adapter Engine.
1) sxi_cache->goto-->AE Cache
2) check for CPA Cache also
...Satish

Comm channel missing in comm channel monitoring

Hi,
I have created sender and receiver communication channels of adapter type XI. I am using PI 7.0 version. But I don't see these communication channels in RWB comm channel monitoring.
I was going through the help.sap.com and in
http://help.sap.com/saphelp_nw04s/helpdata/en/5c/22ee41c334c717e10000000a155106/frameset.htm
In this it is mentioned clearly as "The XI adapter as part of the Adapter Engine gets the required....."
if this is part of the adapter engine then it should show the communication channels registered for it.
Moreover if SAP doesn't want to display these XI adapter com channels then why they have XI adapter type in the drop down box to filter the data.
Please provide your guidance in this regard.
thanku
bk

Hi Bhargvi,
XI adapter is in-built in the integration engine............in RWB in comm channel monitoring, you can view all the comm channels which are at adapter engine...................so this is why you cannot see your XI, IDOC or HTTP adpater in comm channel monitoring because these adapters reside in integration engine directly..................but to tell integration engine regarding the target system you have to configue thier comm channels in ID.
Regards,
Rajeev Gupta

File adapter in comm.channel green, but no message collecting

Hello,
looks like this is something really at the roots.
Ok, we are in NW2004s PI 7.0.
One IDOC process is successfully implemented.
Now we started with a file to file communication!
File sender adapter is configured and shown in status green in comm.channel monitoring which would bring me to the idea that the comm.channel is configured well (To be sure we changed the directory path in the comm.channel to a wrong one which results in an error. Ok, corrected. Now all lamps are green). Comm channel is activated and polling.
But... nothing happens. The Adapter is not collecting the file in the source directory (existing) and there is no entry in monitoring on RWB or SXMB_MONI.
In Adapter monitoring all adapters except the JPR (red) are with a GREY lamp!
As we had an issue with activating the adapters (adapter monitoring before did not show any adapter (except JPR) ) two days ago we are not sure if the current issue belongs to a mistake in the configuration or in basis environment.
From XI 3.0 side we would expect that the adapter monitoring should show adapters used in green.
Do you have experience with such a behaviour?
Any help is welcome!
regards
Dirk

Hi Bhavesh,
we are near to bumping our heads against the server.
In comm.channel:
directory is : / (as simple as possible)
file name is : *.001
The file in the directory is named it_test.001 so it should be catched.
What can we do wrong?
By the way: If we change the directory to /out which is existing we have an (file is in this directory too) error message: 'com.sap.aii.adapter.file.ftp.FTPEx: 550 /out: The system cannot find the file specified. '.
Cache is fine!
regards
Dirk

XI Adapter not visible in Comm Channel Monitoring ?

Hi friends ,
I am trying a proxy scenario in Discovery System V3 .But when we create XI receiver adapter we cannot see the status of that channel in communication channel monitoring .
What could be the reason ? Any input will be appreciated
Thanks.,
V.Rangarajan

Hi Vinod ,
We are using SP12 .
And also one more reason that u were unable to see XI adapter is that u might not have activated that adapter in your admin settings.
       I saw in JEE Admin . This Adapter is in Running mode . the parameters are
xiadapter.isconfig.username PIAFUSER
     1. May i change it to PISUPER and give password ?
     2. http://localhost:50080/sap/xi/engine?type=entry   as   xiadapter.isconfig.url
         but in CC monitoring , IE Components Test message tab i can see the url as   http://iwdfvm2160.wdf.sap.corp:51080/sap/xi/engine?type=entry
           will that port 50080 and 51080 will cause the problem ?
Thanks.,
V.Rangarajan

Comm channel not available in RWB comm channel monitoring

Hi All,
I've gone through this(Comm channel missing in comm channel monitoring) unanwered forum. I've facing the same issue.
In my ID, I created XI receiver adapter comm. channel. And data is flowing successfully to the receiver side through this Comm. channel
I'm aware that XI adapter in ID is used to send data via Proxy.
But why i'm not see that in the Comm. channel monitoring in RWB. If anyone has documentation please let me know.
Thanks.

Hi ,
The XI adapter resides in Integration engine thus you cannot see it in RWB. RWB shows comm channels which are in adapter engine. The simple proof is that you cannot enhance this adapter with your own modules on the Module tab page in the module processor. Here is the link to documentation
http://help.sap.com/saphelp_nw04/helpdata/en/f4/0a1640a991c742e10000000a1550b0/content.htm
regards
Anupam

ABAP Proxy comm channel not seen in Comm Channel monitoring

We have configured JDBC sender to ABAP proxy receiver.
We are unable to see the receiver channel in comm channel monitoring. Is this normal or are we missing something?
Also, the XI adapter cannot be seen in adapter monitoring...I hope thats fine...
We are able to generate the ABAP proxy but we need to see the comm channel to troubleshoot.
Any help will be appreciated.
Thanks

Hi SAP PI,
As with the above commens this link may help u how to debug proxies.. you may try with this..
For -- Debugging Proxies
https://weblogs.sdn.sap.com/pub/wlg/4098--Debugging [original link is broken] [original link is broken] [original link is broken]
For -- Testing Proxies
XI: Debug your inbound ABAP Proxy implementation
regards,
Kishore

500 Wrong channel adapter type

Dear Experts,
         I am having the requirment wherein we need to pass the Messages between 2 PI systems using XI Adapter.
The Scenario is as follows:
        We want to implement MLS to be used between our partner systems. therefore we are using XI Adapter. Since MLS is possible only with XI Adapter.
        we are having 2 PI system. The First PI system which is on 7.0 works as Gateway system for us from where in we receive the messages from our partners & divert the same message to our Inner PI which is on PI 7.11.
        To Test the XI To XI Transfer of message i have configured both the systems. While trying to send some Test Message
thru XI - Test Utility i am getting the following error.
        500 Wrong channel adapter type
What could be the reason for the above mentioned error. Can anybody tell me how to configure XI Receiver & Sender Comm. Channel.
Regards
Umesh

Hi Umesh.
Can you try with following design.
Sender (External System) --> PI 7.0 (Receiver 1 for Ext System && Sender 1 for PI 7.11) --> ECC
1. You can configure External System as Sener in PI 7.0 , an receiver as PI 7.1 (In this case you can place file in NFS in PI 7.1 using file Adapter )
2. in Pi 7.1 configure PI 7.1 as sender and ECC as receiver. .
3. You have to determine whether External System has to be configured as Party or not in PI 7.0
I believe its makes your configuration as simple.

Adapter type is not coming in Communication channel

Hi all,
I am facing a problem while creating a communication channel as i am not able to see any adapter type and its showing as non editable field .
i have cretaed my own software component in SLD am i missing something in SLD configuration ?? because of that i am not able to see any adapter over there .
regards,
praveen

Praveen,
You need to import SAP BASIS Software Component Version into Integration Repository.
You need to download it from service market place.
https://websmp205.sap-ag.de/~form/handler?_APP=00200682500000001943&_EVENT=SEARCH&HIDE=&SEARCH_SPAT=X&SEARCH_BPAT=X&SEARCH_CD=X&SEARCH_P=X&SEARCH_PV=X&SEARCH_C=X&SEARCH_CV=X&SEARCH_TA=&SEARCH_V=&HIDE_EXPERT_SEARCH=X&SEARCH_MAX_RESULT=20
In Search Term Enter "SAP BASIS <version>".
Now click on XI CONTENT SAP_BASIS 7.00 -
> Database independent -
> SAPBASIS13_0-20000888.ZIP Just save this file on your machine and unzip it.
Now put this in the import directory: \usr\sap\<SID>\SYS\global\xi\repository_server\import\
In IR, TOOLS ---> Import design objects and import it.
Regards,
Sarvesh
***Reward points for helpfull ans, in your last thresd you did not assingned points to any buddy.

Adapter types & comm. channels missing in comm channel monitoring

Similar Messages

Maybe you are looking for