Adapter Monitoring is now part of Channel Monitoring ??

Hello ,
After recent upgrade to SP17 i am getting this message while trying to access adapter monitoring ? what does this mean ?
Also is there any way to get adapter specific info ? this is in regards i am getting an error message :
com.sap.aii.af.ra.ms.api.DeliveryException: Couldn't find delivery channel for message
Please advice
Krishna

Krishna,
From SP17, you have a new feature
http://help.sap.com/saphelp_nw04/helpdata/en/44/46d1a56faf52d3e10000000a1553f6/content.htm
The Runtime Workbench has the following new functions:
● Component monitoring: Communication channel monitor
In component monitoring, you can use the new communication channel monitor to call information about the status of your communication channels and the corresponding adapters. You can also administrate your communication channels.
Unlike the adapter monitor, the communication channel monitor also provides current runtime information about the communication channels of individual adapters, as long as they are registered for communication channel monitoring.
To monitor adapters that do not provide runtime information to communication channel monitoring, continue to use the adapter monitor.
Regards,
Bhavesh

Similar Messages

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

Communication channel monitoring, adapter monitoring error

Hi ,
I am using SAP PI 7.0 with HP-UX.
Here we have 6 logical hosts in one physical host.
Physical host name is u2013 xyz
Integration server name u2013 sappid
The Central SLD: sappid
URL for sappid: sappid: 50300
When I monitoring RWB----
>communication channel monitoring, adapter monitoring, in Development system It's detecting another logical host ( like www://sapard:50300 ) and getting page cannot find error.
1.SLDCHECK
   http://xyz:50300/sld
   host name: xyz
port number: 50300
user : SLDDSUSER
2.SXMB_IFR
   http://xyz:50300/rep/start/index.jsp
3.SMICM
   icm/server_port_0 = PROT=HTTP,PORT=8003
   icm/server_port_1 = PROT=SMTP,PORT=0
   icm/HTTP/j2ee_0 = PREFIX=/,HOST=localhost,CONN=0-500,PORT=50300
   icm/host_name_full = sappid
4. SLDAPICUST
    SAP_CONFIG   1   xyz   50300   SLDDSUSER
5. SXMB_ADMIN
    Role of Business System Integration Server
    Corresponding Integ. Server http://sappid:8003/sap/xi/engine?type=entry
   Integration Engine Configuration Data -> Check button
6.When I opened the http://xyz:50300/rep/start/index.jsp I got the
XI start page.
    when I opened the http://sappid.AIG.com:50300/
   the page not found issue, when I opened http://sappid:50300/ I got the
   XI start page.
plz help me for this issue.
thanks in advance.
regards,
reddy.

Hello,
I think the FQDN is not set properly.
Problem in the parameter
SMICM
icm/server_port_0 = PROT=HTTP,PORT=8003
icm/server_port_1 = PROT=SMTP,PORT=0
icm/HTTP/j2ee_0 = PREFIX=/,HOST=localhost,CONN=0-500,PORT=50300
*icm/host_name_full = sappid *
Replace this parameter in instance profile
icm/host_name_full = sappid.AIG.com
Then in the host entry of your server please add an entry
172.18.23.233(ip your ur Xi server)       sappid.AIG.com
Then let us know the result.
Thanks and Regards
Vijay

Custom Adapter - No content in Communication channel Monitoring for JCA

HI,
     We have developed a Custom Adapter for our client in XI with name JCA and it is working absolutely fine.
     Issue: We are not getting any entries in Communication Channel Monitoring for success or Error Messages.
     We have used Audit log for success or Failure entries and they are coming fine in Messaging System but there coule be a standard way to get entries in Channel Monitoring.
    Our client needs the entries in CC monitoring instead of Customised Audit Logs.
    Please help.
REgards,
Anurag Garg

HI Satish,
                 Thanks for answer. I am looking for this in Custom Adpater not in adapter module.
                 This log creates a trace File . Its not to do with getting messages in CC monitoring as we do get for File Adapter or other Adapters.
               Like- Message Successfully put into the queue.
                     - Successfully processed.
                 Such Messages are there in sample_ra. jar file code but they are not visible in CC Monitoring.
               I think some extra code needs to be added to activate this in Monitoring.
               Please suggest.
REgards,
Anurag Garg

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

Communication channel monitoring (adapter engine) in ccms (rz20) available?

Hi,
we have problems in our xi system (PI 7.0, SPS10). The adapter engine can only be monitored in the communication channel monitoring, available in the runtime workbench!
There sometimes errors disappear. At the moment these errors accumulate!
Is it possible to view these errors/ alerts in the ccms (rz20) monitoring?
So we don't look all the time in the communication channel monitoring!
Have anybody an idea?
Regards,
matthias isenburg

Have u seen the discussion
Re: How do I configure an auto-email alert for Adapter engine errors
Regards,
Prateek

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

Commuication Channel monitoring for SOAP Adapter

Hi friends,
When i see Sender soap adapter status in Communication channel monitoring.I am getting the status as:
Channel started but Inactive
What does that indicate?
Kindly update what i need to do..

Check these links :
SOAP adapter - Channel started but inactive (case inside)
SOAP Adapter status stay "Channel started but inactive"
it ll be solved by given solutions in these thread like send messages,cache refresh..

500 Internal Server Error - Channel Monitoring Audit Log

Hi Experts,
We are facing an error in the 'Audit Log' of the communication channel monitoring of a File Sender Adapter.
The channel uses a custom written Java Module which uses XSLT parser internally. The audit log displays the following error:
500 Internal Server Error
Error: "Application error occurred during the request processing."
Troubleshooting Guide https://sdn.sap.com/irj/sdn/wiki?path=/display/jsts/home
Details: "The WebApplicationException log ID is [4698F300D2C40C2000000000000009AA]."
This error occurs both when the file is processed successfully or when in error. In case of a positive test case file, we can even see the message reaching Pipeline (SXMB_MONI). But only the audit log does not show the processed steps in the channel monitoring and displays the above error message.
We have even established that the cause of the error is Java Module (First, we executed by removing our custom Java Module from the module steps and the audit log showed the steps correctly. But by putting the module back in the channel, the error resumed).
Initially, the error was not coming and we were able to test this properly. But over the time the audit log error started. Now, we are not able to get rid of this even by restarting the channel or restarting the Java stack of the server.
To me, it seems like a memory issue in the Java Stack.
Any thoughts?
Can we find out where to find the details of the WebApplicationException log ID displayed above?
Thanks,
Sudheer

Hello,
This could be generic but may helo you:
500 Internal Server Errors
Description: The server encountered an unexpected condition which prevented it from fulfilling the request.
Possible Tips: Have a look into SAP Notes u2013 804124, 807000
Regards,
Caio Cagnani

Error in Comunication Channel Monitoring

Hi Friends!
I am triyng to connect a DB2 AS400 to PI 7.1 by JDBC Adapter, in the Comunication Channel Configuration is:
JDBC Driver -> com.ibm.as400.access.AS400JDBCDriver
Connection -> jdbc:as400://<Host>:<Port>/BDName
User -> XXX
Pas -> XXX
Now, in the NWA I deployed the driver jt400 Type Executable Jar File, and I created the "JDBC Custom Data Source Creation", with the same Parameters mentioned above
Well, My question is if I need to do something else?, Because in the Comunication Channel Monitoring show an error.. Exception caught during JDBC adapter processing: java.lang.NullPointerException
Somebody help me, Thanks!

Hi
There are two DB JDBC Drivers are available check reply by Bhavesh.
So check connection parameter according to your driver.
JDBC connection to DB2 Database

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

IDoc adapters not in "communication channel monitoring"?

Hi,
I've modified some information that the receiver IDoc adapter is using (the logical system ID). But after I refreshed all the caches the change is not updated when I send an IDoc to R/3.
When this kind of problem happens with RFC adapter you just have to stop and restart the communication channel in communication channel monitoring. But IDoc adapter is not here... so, how can I restart the IDoc communication channel?

Hi,
IDoc adapter doesnt reside on Adapter Engine, its part of ABAP stack, because of this you cannt find it in RWB-Communication channel monitoring...
Try refreshing the cache:
Transaction: sxi_cache
CPACache refresh using the below url:
http://<server:port>/CPACache/refresh?mode = full
to get the changes affected.
Regards,
Sreenivas.

Issue with RWB Communication Channel Monitoring

Hi All,
I am getting a error in RWB >> Communication Channel Monitoring.
I deactivated the receiver JDBC adapter, and now when I activate it, in the RWB it shows 'Channel started but Inactive' I tried to start and stop the channel and also activating and deactivating the channel. But no success, it keeps showing 'Channel started but Inactive'. Pls advice....
XIer

Hi XIer,
Ideally adapter status should be in green when it is up and running..
if it not then..
1. check the status in ID. It should be in active state.
2. check the status in RWB .It should be in green. I not check that your adapter got activated without any cache error.
3. Do a CPA Cache Refresh.

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.

Advance selection for source file-Error in communication channel monitoring

Hi all,
Referring to the link below:
/people/mickael.huchet/blog/2006/09/18/xipi-how-to-exclude-files-in-a-sender-file-adapter
I have developed my scenario in the same way.But due to the values <NOTHING>
in Mandatory fields Source Directory and Filename,i am facing problem in Communication Channel Monitoring as it shows an error;even though the end-to-end scenario works successfully.
Plase note that our scenario is not to exclude the particular file but to pick the files serially after a certain delay.
Kindly provide some idea about how can we remove the error from Communication Channel Monitoring.
Thanks & Regards,
Sudhir Tiwari

Sudhir,
In the sender file adapter, you have an option called "Processing Sequence".
By selecting ByName or ByDate you can make files get selected sequentially either ByName ( alphabetically ) or by the creation time stamp of the file.
In the sender file adapter also make the QOS as EOIO and give the QueueName as any value and the files will be processed sequentially.
Regards
Bhavesh

Adapter Monitoring is now part of Channel Monitoring ??

Similar Messages

Maybe you are looking for