Soap Adapter Channel not found

I'm having problems geting the Sender SOAP adapter to work.
I'm using to test it
http://<XXXXXXXX>:50000/XISOAPAdapter/HelperServlet?action=FindChannel&channel=:SunriseSoftwareSostenuto:TimeSentSoap
where <XXXXXXXX> is our domain
but this returns channel not found
SunriseSoftwareSostenuto is the Service
TimeSentSoap is the communication channel
I've already established that the Soap Adapter is active
Is there something that I've missed ?

hi
I've tried to connect to the Soap adapter using
http://xxxxxx:50000/XISOAPAdapter/MessageServlet?channel=:SunriseSoftwareSostenuto:TimeSentSoap
Where SunriseSoftwareSostenuto is the business service and
 TimeSentSoap is the communication channel
but get the error code returned below
I've tested the sender agreement/ communication channels config internally and they seem fine
could someone point me in the right direction
is it a java error
or is it a authorisation problem?
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
 <SOAP:Body>
 <SOAP:Fault>
 <faultcode>SOAP:Server</faultcode>
 <faultstring>Server Error</faultstring>
 <detail>
 <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
 <context>XIAdapter</context>
 <code>ADAPTER.JAVA_EXCEPTION</code>
 <text>com.sap.aii.af.mp.module.ModuleException: either no channelID specified or no channel found for the specified party, service, and channel name, MessageServlet(Version $Id: //tc/xi/NW04S_21_REL/src/_adapters/_soap/java/com/sap/aii/af/mp/soap/web/MessageServlet.java#1 $)

Similar Messages

XI / PI SOAP Adapter - MessageServlet not found / not responding

I am in trouble with XI SOAP Adapter. When I try to reach the MessageServlet ( http://host:port/XISOAPAdapter/MessageServlet ) I get the response that document dont exists. Why MessageServlet do not respond? Anyone can help me?
In my Adapter Monitor ( http://host:port/mdt/amtServlet ) I see about the SOAP adapter a grey status and the information: "SOAP Adapter Monitoring is now part of Channel Monitoring". This is not a problem, according to Suraj: "SOAP Adapter will become active only when you sent a message through that for atleast one time.")
See also these topics:
SOAP adapter installation and activation
Adapter monitoring: SOAP is grey although it is used?
how can i enable SOAP Adapter?
https://websmp208.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=012003146900000286382005 (SAP Note 856597)
 I have readed these topics (and others), but my problem seems to be a little different.

My XI runtime cache contents (SXI_CACHE) are up-to-date.
Information of some of my XI components:
Software Components
Vendor Name Version Location Applied
sap.com SAP-JEE 6.40 SP17 (1000.6.40.17.0.20060516064307) SAP AG 20060612185606
sap.com SAP-JEECOR 6.40 SP17 (1000.6.40.17.0.20060516064111) SAP AG 20060612185559
sap.com NWMADMIN 6.40 SP17 (1000.6.40.17.0.20060515153837) MAIN_APPL63VA_C 20060612185601
sap.com SAP_XITOOL 3.0 SP17 (1000.3.0.17.0.20060504222004) SAP AG 20060613105756
sap.com SAP_XIPCK 3.0 SP16 (1000.3.0.16.0.20060220233019) SAP AG 20060612185556
sap.com LM-TOOLS 6.40 SP17 (1000.6.40.17.0.20060417111655) MAIN_APPL63VA_C 20060612185603
sap.com SAP-XICONS 3.0 SP16 (1000.3.0.16.0.20060220232901) SAP AG 20060612185600
sap.com SAP-XIAFC 3.0 SP12 (1000.3.0.12.5.20050712085155) SAP AG 20060612185555
sap.com SAP_XIAF 3.0 SP17 (1000.3.0.17.0.20060522230043) SAP AG 20060613103623
sap.com SAP_JTECHF 6.40 SP17 (1000.6.40.17.0.20060516064445) SAP AG 20060612185559
sap.com SAP_JTECHS 6.40 SP17 (1000.6.40.17.0.20060516064629) SAP AG 20060612185606
sap.com com.sap.aii.af.mp 3.0 (3.0.1720060522104934.0000) SAP AG 20060613102037 sap.com/SAP-XIAFC 
sap.com com.sap.aii.af.soapadapter 3.0 (3.0.1720060522104934.0000) SAP AG 20060613103506 sap.com/SAP_XIAF
Thanks a lot! If you need other information, please, let me know.
Ivan, from Brazil

"https://websmp208.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=012003146900000286382005 (SAP Note 856597)
I have readed these topics (and others), but my problem seems to be a little different."

Adapter Engines not found

Hello All,
I am doing a file to Idoc scenario. When I open the communication channel that I created, there is a warning message popping up as below:
Adapter Engines Not Found
Unable to find associated SLD element for specified class (source element: SAP_XIIntegrationServer, [CreationClassName, SAP_XIIntegrationServer, string, Name, IntegrationServer.pid.svdud01, string], target element class: SAP_BusinessSystem)
Any idea on this issue techies?
Thank you.
Ramesh.

Thank you all.
I have been checking all possibilities.
I tried to do the cache connectivity test in thr runtime workbench, but it throws the following error:
Attempt to fetch cache data from Integration Directory failed; cache could not be updated
[Fetch Data]: Error while consolidating data
[Data Evaluation]: Couldn't parse Configuration Data cache update XML string from Directory.
I checked the technical and business systems for the PI system and they are maintained correctly.
Any more ideas ?
Many thanks.

Getting error while using CAN api's. Says channel not found in MAX.

Hi,
I am using NI-CAN series2, can card. The same is not connected to my system. Hence i have used the virtual channel 256. Here i am reading the DBC file and providing an option to the user to select a set of messages to transmitt\receive. But i am getting an error saying
"Error -1074388479 occurred at CAN Get Channel Data Type.vi
Possible reason(s):
NI-CAN: (Hex 0xBFF62201) Channel not found in MAX or the CAN database file. Solutions: Check for proper spelling using MAX; For Get/Set Property, ensure that the channel name exists in the task."
Please help.
Regards,
Yogesh

Hi Marshall,
Thanx for the reply and spending time for the same. I tried the example which u had mentioned. This example is working with 256 virtual channel. But my code is no executing and giving he same problem even after loading the DBC file into max(Same loaded im my code). Always load the dbc file in max and then only i should run the code, is it so? But this can not happen, since the user may not hav max. I hav attached the code. Pls verify it, and give me the feedback.
Waiting for the reply,
Yogesh
GET
Larsen & Toubro
India
Attachments:
CanMsgFrame.vi ‏68 KB

Getting the Adapter Class Not Found Error in the Java Manipulator

Hi,
I wrote a custom java manipulator for the baseline update and created a jar file for the class. This works fine in the Windows machine. All I have to do is while specifying the CLASSPATH, I entered the ./ib/newManipulator.jar; ./lib/additional_dependency.jar. When I tried to deploy the same code in the Unix environment, it fails saying the Adapter Class not found. The only difference from windows and Unix environment is that in the windows machine, in order to run the base line update, I go to the directory my_project->control->baseline_update.bat but in case of Unix environment I have a separate location where I have a shell script called run-baseline-update.sh located at /apps/bin which invokes the baseline.sh in the directory my_project/control/baseline.sh. I even tried to put the full path of the jar files e.g. /my_project/lib/newManipulator.jar; /my_project/lib/additional_dependency.jar in the class path but still the same issue. Any suggestions?

Unix classpath needs ":" as the path separator, not ";". Changing that will make this work.
For reference, later versions of the deployment template make this configurable, so you'd see (in environment.properties):
# PATH_SEP_VARNAME: for platform-independence
PATH_SEP_VARNAME=;
# Forge needs record store libraries as well as Spring to load record store adapter configuration files
FORGE_CLASSPATH=./config/lib/java/spring-delegate-adapter-1.0.1.jar${PATH_SEP_VARNAME}./config/lib/java/spring.jar${PATH_SEP_VARNAME}./config/lib/java/eacToolkit.jar${PATH_SEP_VARNAME}./config/script${PATH_SEP_VARNAME}.
You can then add the following to your <forge /> definition in AppConfig.xml:
<arg>--javaClasspath</arg>
<arg>${FORGE_CLASSPATH}</arg>
Hope this helps.
Michael

SOAP Adapter: DO not use soap envelope

Hi Guys
I have a scenario, which calls a webservice from my ABAP Proxies, the twist in this is that SOAP request expects license info into the header of SOAP envelope, I could achive this by XSLT mapping in the receiver SOAP adapter I selected the option "Do not use SOAP envelope" and could do the call.
Due to this the response received from the webservice is treated as payload, as shown below...
response message payload:
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<Header xmlns="http://schemas.xmlsoap.org/soap/envelope/">
 <SubscriptionInfo xmlns="http://ws.strikeiron.com">
 <LicenseStatusCode>0</LicenseStatusCode>
 <LicenseStatus>Valid license key</LicenseStatus>
 <LicenseActionCode>0</LicenseActionCode>
 <LicenseAction>Decremented hit count</LicenseAction>
 <RemainingHits>18</RemainingHits>
 <Amount>0</Amount>
 </SubscriptionInfo>
</Header>
<soap:Body>
 <getRateResponse xmlns="CurrencyRates">
 <getRateResult>44.945</getRateResult>
 </getRateResponse>
</soap:Body>
</soap:Envelope>
and when i am trying to do the response mapping, it is not able to read the value.
Anyone having any idea, on how we could do this.
Thanks
Dheeraj

Hi
I am sorry for replying in so late, was busy with some projects.
I got few mails and this post is cathing up again, so thought of giving the solution I followed without any adapter module or anything, simple plain XSLT mapping.
Integration Repository
1. Created data type and message type for Outbound Interface
2. Imported the WSDL
3. Created an XSD out of the sample response I got by calling the WSDL (this you can do from any tool available, i used the strikeiron website), pls refer below to see the XSD below, and you will have to use the message type envelope from it.
4. Most Important step, created 2 XSLT mappings, one for request and the other for response., Pls refer below for both these mappings.
5. did the interface mapping
Integration Directory
1. pls configure your scenario as normaly you do, and while you configure the communication channel for your soap receiver, make sure you click on the do not use soap envelop option.
thats it done.
XSLT Request Mapping
<?xml version="1.0"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
 <xsl:template match="/">
 <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
 <SOAP-ENV:Header>
 <LicenseInfo xmlns="http://ws.strikeiron.com">
 <RegisteredUser>
 <UserID>xyz</UserID>
 <Password>xyz</Password>
 </RegisteredUser>
 </LicenseInfo>
 </SOAP-ENV:Header>
 <SOAP-ENV:Body>
 <getConversion xmlns="CurrencyRates">
 <FromCurrencyCode>
 <xsl:value-of select="//fromCurrency"/>
 </FromCurrencyCode>
 <ToCurrencyCode>
 <xsl:value-of select="//ToCurrency"/>
 </ToCurrencyCode>
 <Amount>1</Amount>
 </getConversion>
 </SOAP-ENV:Body>
 </SOAP-ENV:Envelope>
 </xsl:template>
</xsl:stylesheet>
XSLT Response Mapping
<?xml version='1.0' ?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:a="CurrencyRates" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
 <xsl:template match="/">
 <ns0:MT_Cur_res xmlns:ns0="http://www.april.in/WebService/SOAPHeader">
 <Rate>
 <xsl:value-of select="soap:Envelope/soap:Body/a:getConversionResponse/a:getConversionResult"/>
 </Rate>
 </ns0:MT_Cur_res>
 </xsl:template>
</xsl:stylesheet>
Webservice Response XSD
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" targetNamespace="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="http://ws.strikeiron.com" xmlns:ns2="CurrencyRates">
<xs:import namespace="CurrencyRates" schemaLocation="ns2.xsd"/>
<xs:import namespace="http://ws.strikeiron.com" schemaLocation="ns1.xsd"/>
<xs:element name="Envelope">
 <xs:complexType>
 <xs:sequence>
 <xs:element ref="soap:Header"/>
 <xs:element ref="soap:Body"/>
 </xs:sequence>
 </xs:complexType>
</xs:element>
<xs:element name="Header">
 <xs:complexType>
 <xs:sequence>
 <xs:element ref="ns1:SubscriptionInfo"/>
 </xs:sequence>
 </xs:complexType>
</xs:element>
<xs:element name="Body">
 <xs:complexType>
 <xs:sequence>
 <xs:element ref="ns2:getConversionResponse"/>
 </xs:sequence>
 </xs:complexType>
</xs:element>
</xs:schema>
let me know in case somebody gets stuck somewhere for this scenario.
Take Care
Dheeraj

Channels not found

RFC: INTEGRATION_DIRECTORY_HMI working fine. SLDCHECK works fine.
AI_RUNTIME_JCOSERVER, AI_DIRECTORY_JCOSERVER, LCRSAPRFC,SAPSLDAPI, all works fine. CACHE works fine.
But still Communication channels are not found.
No clue where to start dig.

hi
Check this
1 Scenario
This guide deals with all the configurations required to create an IDoc adapter in Exchange Infrastructure
3.0 to send an IDoc from XI to the SAP backend system.
Unlike other types of adapters, the IDoc adapter has dependencies on the XI 3.0 ABAP configurations and
the backend SAP system configurations. Those configurations information will have to be either created
first or retrieved in order to complete the IDoc adapter configuration.
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.
Regards
Hemant
Award points if find helpful

PI 7.11 - Configuration: Adapter Engines Not found

Hi,
We have a PI 7.11 System that is connected to a central SLD. There are also two PI 7.0 systems connected to this SLD. If i open a communicationChannel i get following message:
Adapter Engines Not foundNo SLD elements of type SAP_XIAdapterFramework found
If i look in the SLD Technical Systems (Exchange Infrastructure), i see the three PI systems but only the Adapter Engines of the two PI 7.0 systems.
How can i check if the adapter engine is up and running and if it has correctly been registered by my SLD. Are there any documentation according this configuration?
Thanks in advance

It seems adapter engine is not registered properly. For more details, please refer to the following sap notes:
1. [Note 764176 - Error in XI due to inconsistent SLD contents|https://service.sap.com/sap/support/notes/764176]
2. [Note 1117249 - Incomplete Registration of PI components in SLD|https://service.sap.com/sap/support/notes/1117249]
3. [Note 1292803 - Configuration Wizard: PI SLD Self Registration|https://service.sap.com/sap/support/notes/1292803] .
Regards,
Sunil Chandra

PI 7.0 JMS Rcv Adapter: Object not found in lookup of XIJMSService

Hi all,
When sending messages to an JMS queue, JNDI setup, in the Message Monitoring we get the error:
"MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: Object not found in lookup of XIJMSService.: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of XIJMSService."
The Error points to the Module Processor. Indeed the 2 default Modules are used:
- SAP XI JMS Adapter/ConvertMessageToBinary
- SAP XI JMS Adapter/SendBinarytoXIJMSService
This second Module contains 'XIJMSService', and according the documentation (http://help.sap.com/saphelp_nw04/Helpdata/EN/4d/a3bc97ff55c742af7faed661635baf/content.htm)
, it uses a parameter named 'modulePoolAdminLookupName' with the default value: /XIJMSService.
This is how far we get. Even when we assign a different value to the parameter 'modulePoolAdminLookupName' , the error in the Message Monitoring stays the same.
Has anyone experience with this issue, or any ideas to investigate or solve this?
Thanx in advance, Walter.

Hi all,
Issue is solved. Apparently the Java-version on our XI-server (1.4.2) could not handle the Vendor's JMS-driver we installed (ActiveMQ 4.1.2.jar) so we tried using the ActiveMQ 4.1.0.jar as the JMS-driver. Now it is OK and message are put on the destination queue.
Walter.

Problem with SOAP Adapter receiver not receiving the proper string

Hi friends
I have a very simple scenario as follows using SOAP Syncronous Call
SENDING SCENARIO
================
ExternalClient --> SOAP ADAPTER --> XI -> RFC ADAPTER --> ZBAPI
RECEIVING SCENARIO
==================
ZBAPI --> RFC ADAPTER --> XI --> SOAP ADAPTER --> ExternalClient
Here External Client is sending a search ID and ZBAPI searches for that record and send the FirstName and LastName.
I am using external Definitions in XSD format as follows.
INPUT XSD is
=========================================
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://cincom.com/xi/socrates/customerSearch" targetNamespace="http://cincom.com/xi/socrates/customerSearch">
 <xsd:element name="ZBAPI_GET_NAME">
 <xsd:complexType>
 <xsd:all>
 <xsd:element name="ID" type="xsd:integer" minOccurs="0" />
 </xsd:all>
 </xsd:complexType>
 </xsd:element>
</xsd:schema>
===========================================
Reciving XSD file has
==============================================
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:socrates.cincom.com" targetNamespace="urn:socrates.cincom.com">
 <xsd:element name="ZBAPI_GET_NAME_RESPONSE">
 <xsd:complexType>
 <xsd:all>
 <xsd:element name="ADDRESSDATA" minOccurs="0">
 <xsd:complexType>
 <xsd:sequence>
 <xsd:element name="FNAME" minOccurs="0">
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:maxLength value="20" />
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="LNAME" minOccurs="0">
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:maxLength value="20" />
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 </xsd:sequence>
 </xsd:complexType>
 </xsd:element>
 </xsd:all>
 </xsd:complexType>
 </xsd:element>
</xsd:schema>
=========================================================
I HAVE TESTED THE ZBAPI AND IT WORKS WELL ON ITS OWN. ALSO I HAVE TESTED THAT THE MESSAGE SENT FROM OUTSIDE CLIENT IS REACHING BAPI. HOWEVER WHEN I GOTO 'SXMB_MONI' AND CHECK THE
XML STRING THAT THE RECIEVER IS GETTING, I SEE JUST THE FOLLOWING TWO LINES
===================================
<?xml version="1.0" encoding="UTF-8" ?>
<ns1:ZBAPI_GET_NAME_RESPONSE xmlns:ns1="urn:socrates.cincom.com" />
======================================
IF YOU NEED ANY FURTHER INFO, PLEASE LET ME KNOW.
HOPE SOME ONE CAN GUIDE ME WITH THIS PROBLEM.
THANKS IN ADVANCE
RAM

Ram
Can you pls. confirm whether the mapping of your XSD fields & BAPI fields are in same sequence. I mean hierarchy is same or not.
Just to verify, as you said you are using Sync scenario that means you are using ONE Sender Soap & ONE Reciever RFC adapter.
Regards
Lalit

SOAP adapter does not work

Hello experts,
I've a provider proxy scenario where a DB table on the ECC backend system must be updated.
I used a receiver SOAP adapter with following parameters:
URL: http://<host>:<pmort>/sap/xi/engine/?type=receiver and user authentication for the ECC system.
This does not seems to work. I see nothing on the SXMB_MONI transaction on the backend system.
Then, I tried to use a receiver XI adapter with the same parameters and logon data for an SAP system.
This seems to work fine.
Please tell me what I did wrong because the SOAP adapter should work too, isn't it?
Thanks a lot
Dimitri

Hi Ravi,
I published it and created an endpoint via SOAMANAGER, but still nothing.
Now, I also get this when I check SXMB_MONI on my ECC backend system:
No implementing class registered for the interface (ABAP interface, request message ...... request message, namespace ......)</SAP:Stack>
But I generated and regenerated the proxy. Very strange.
When I check SXI_CACHE tranaction on the ECC backend system, I see this: "cache contents are obsolete".
Please advice
Thanks
Dimitri

XMBWS.Timeout in soap receiver channel not working

Hello
I have a requirement where my soap receiver channel should time out in 20 sec from the time it had shot a webservice request.
I tried setting the module parameter XMBWS.Timeout to 20000 but it didnt work. I assume this parameter should be set for the standard module i.e. sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean.
Currently my receiver channel is timing out after every 3 min and that might be because the parameter xiadapter.inbound.timeout.default in SAP NWA is set to 180000.
Any other parameter to be set so that channel takes time out duration from module parameter.
Note: we are working on PI 7.1 EHP1
Regards
Shailesh

>
Shailesh Kunjiraman wrote:
> i doubt if this can be reduced to value lower than a minute.
i agree. A minute is usually the minimum value for lot many parameters.

SOAP adapter - Channel started but inactive (case inside)

Good day everyone!
I have integration scenario IDOC->XI->SOAP. I did all setting and created SOAP adapter with 2 parametrs: "Target URL" and "SOAP Action".
But when I look at Channel Monitoring I see my SOAP-channel with status "Channel started but inactive" ??
What could it be?
Thanks in advance!

hi,
this issue is too common. i face it i some of my channels. there no error.
test your scenario. im sure it will work but the adapter still has been in yellow at least it fails and turn red.
I have some CC in red status and working fine. later few minutes it turn green.
don worry about it. if you leave it working it will turn green later. if u restart the java stack you can solve it but i dont recommend it because this error could appear in other adaprter too.
commonly it appear when you start and stop the channel from RWB.
Hope Helps
thanks
Rodrigo.

PI 7.1 RFC Communication Channel not found

Hello,
We have recently upgraded to PI 7.1 and I am having a problem getting my RFC adapter to work. This is the error message:
Error when calling an adapter by using the communication channel CC_UDF_RFC_CALL_TO_PI_ABAP (Party: , Service: IS_D06, Object ID: 5873a160602e3be5866ab820596b752c) The channel with object ID 5873a160602e3be5866ab820596b752c could not be found in the Integration Server Java Cache. Check if the channel exists in the Integration Builder Directory and execute a refresh of the Java Cache
I went to SXI_CACHE and refreshed (Delta nad Complete). I can see that the CC exists in integration builder.
How can I determine what is causing this error?
Thanks,
Matt

Also check the cache notification after activating the Comm channel in ID whether cache is properly updating for the changes in the comm channel.
Menu--> Environment --> Cache Notification
If cache notification is proper thentry to refresh CPA cache using following URL and execute ur scenario.
[http://<host>:<port>/CPACache/refresh?mode=full]
Edited by: Samiullah Qureshi on May 14, 2009 8:36 AM

Adapter engine not found in Integration Directory

Hello All,
We are having a new server installation. The problem I am having is in Integratin Directory --> Communication Channel, no option for Adapter Engine is present in the drop down. I have checked the following options:
1) SAP BASIS Component with Adapter Mata data is present in Repository.
2) In SLD, Content Maintenance, class XI Integration Server. There are 3 associated objects (the last column). XI Sub-System viewed application system is also present.
3) The Technical and Business Systems are already created for XI Integration Server in SLD.
I have also suggested the blog /people/venugopalarao.immadisetty/blog/2007/03/15/adapter-engine-cannot-be-found-in-integration-directory , to the Basis team, however the problem still persits.
Kindly suggest how we can resolve the issue and start executing our scenarios.
Regards
Pravesh
Edited by: Pravesh Sharma on Mar 9, 2009 10:11 AM
Edited by: Pravesh Sharma on Mar 9, 2009 10:12 AM

Hello,
I think the BASIS Team has gone through or implemented this OSS note as it is mention in the blog above. However the problem still persists.
Regards
Pravesh

Soap Adapter Channel not found

Similar Messages

Maybe you are looking for