Error in Sender AS2 adapter

Hi Expert,
I have configured sender AS2 adapter as per the sap guide. and share our url and AS2 name.Now when the partner is trying to send the file from their side they are gettting the following error message and in SAP PO we have not received any file via AS2 sender adapter.
We have checked the fire walls and its working fine.
2014.04.09
01:15:03:128 0326030999 PHDR OK HTTP Response-Line = (HTTP/1.1 302 Found)
2014.04.09 01:15:03:128
0326030999 PHDR ERR Trading Partner rejected the transaction
2014.04.09 01:15:03:128 0326030999 HPOS ERR Requested synchronous receipt not
returned
2014.04.09 01:15:03:128 0326030999 HPOS ERR One or more errors occurred with
this transaction. m_nErr=(2103)
Regards
Kasturika

Hi Harish,
I have change the as2 url from http://<host>:<port>/AS2 to http://<host>:<port>/AS2/B2B and now are partner is facing differnt error
2014.04.22
03:06:04:400 0637647174 PHDR OK HTTP Response-Line = (HTTP/1.1 401
Unauthorized)
2014.04.22 03:06:04:400 0637647174 PHDR ERR Trading
Partner rejected the transaction
I had checked with my partner to use the http authentication and share our user id and password. but they said that they are not using http authentication.
we also shared our public key certificate and import theirs in our nwa- certificates and keys .
Please share if anything more i need to configure.

Similar Messages

Sender AS2 Adapter Setup

Hi,
I am trying to send an EDIFACT file to IDOC through AS2 Adapter (sender). Can you please tell me how to configure the sender AS2 Channel.I have configured it, but it is giving me the following error in Channel Monitoring.
Alert: Maximum number of retries reached. Retry 20. Message initiation failed: Adapter call failed. Reason: Fatal exception: com.seeburger.xi.connector.queue.TaskBuildException: failed to lookup CPA cache: Couldn't retrieve outbound binding for the given P/S/A values: FP=B2B_Certipost;TP=B2B_PH_BE;FS=B2B_SND;TS=B2B_RCV;AN=MI_E_ORDERS_D96A_oa;ANS=urn:novartis.com:pi:ph:be:OM_DD_750_LBE_L0X:Order;, failed to lookup CPA cache: Couldn't retrieve outbound binding for the given P/S/A values: FP=B2B_Certipost;TP=B2B_PH_BE;FS=B2B_SND;TS=B2B_RCV;AN=MI_E_ORDERS_D96A_oa;ANS=urn:novartis.com:pi:ph:be:OM_DD_750_LBE_L0X:Order; [4/30/09 4:19 PM]
Please share your valuable inputs.
Thanks,
Amit..

Hi,
follow the below steps;
AS2 identifier is the party identified which will be provided by the WAN network provider.
Under the party identifiere tab
Agency will be seeburger
Scheme=AS2ID
Name = WAN network no of the partner who is sending the file
Few changes in the module parameter tab.
localejbs/CallBicXIRaBean bic
CallSapAdapter 0
Module configuration:
bic= destSourceMsg = MainDocument
bic= destTargetMsg = MainDocument
bic= mappingName= See_E2X_EDIFACT_ORDERS_UN_D93A
-S

Archive file with errors in sender file adapter not working! please help!

Hi Experts,
I have a file to RFC scenario. the input is a XML file. I have setup the flag in sender file adapter channel for archiving the input files with errors. But it is not working.
For testing I have used an invalid xML file for example without the main XML tag. I have also tested with a MSWORD file saved with.xml extension. But in both the cases the files are not getting archived.
My archive location permissions are fine and in fact normal archive operation is happening. That is, if I select the processing mode as "Archive" and gave the Archive directory then files are getting archived. The problem is only with the "Archive faulty source files" option.
What am I missing? DO I need to do some more configurations?
What are the prerequisites if any for this option?
How to test this?
Please help me! I will be greatfull to you all!
Thanks & Regards
Gopal

and go thru this links
Creating a Single Archive of the Version Files
http://help.sap.com/saphelp_nw04/helpdata/en/79/1e7aecc315004fb4966d1548447675/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/31/8aed3ea86d3d67e10000000a114084/frameset.htm
Note: reward points if solution found helpfull
Regards
Chandrakanth.k

Error in sender file adapter: source directory does not exist

Hi,
The PI system is 7.11
I've created sender file adapter with following details:
Transport Protocol : File System
Source directory: /interfaces/In
I checked in AL11 that this path really exists and it does. (I can even see the .txt file that should be processed.)
But still i get in Communication Channel Monitoring the following error:
"Configured Source directory "/interfaces/In" does not exist.
(i also tried to give the source directory as "interfaces/In" and as "//interfaces/In" but still the same error.
Any suggestions as to what is wrong?
kr
Robert

Actually, Need to use forward slash (/) to separate directory names in accordance with the Java specification.
But wanted to try if that works..
Also check directory name , path again as this is case sensitive...
--Divyesh

File to SOAP,error in sender file adapter

Hi,
I am doing a scenario FILE to SOAP where In file adapter I am using Quality od service as Exactly once in order.I am getting the below error.It works fine when I use QOS=Exactly once.Not sure why,can you guys please help me.Can we really use QOS-EOIO for sender file adapter,where exacly do we use it.
Thanks
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: invalid content type for SOAP: TEXT/HTML</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Edited by: guest xi on Apr 16, 2008 11:55 AM

Hi,
Thanks for your replies guys.I diid give the queue name ,I dont know what is causing the error.Now even QOS=EO which was working fine before is throwing an error.I am using the same file name for both
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: invalid content type for SOAP: TEXT/HTML</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>

'Source Directory doesn't exist' error in sender file adapter

Hi All,
I m getting the error 'Source Directory doesn't exist' in sender file adapter.
The source file directory doesn't exist in XI Server. Its in a different system.
gone through other sdn t hreads.
the options seems to be
1. either to mount the Source Directory on the XI Server.
2. Install a FTP server and use FTP protocol.
My doubt is that, could nt we give necessary access rights to the XIAFUSER whihc will access the Source Directory?
Wont it be sufficient?

Hi Aarthi,
If you are using system other than XI, then you have to use FTP server
else check you have proper authorization of read/write to the source directory...
and check the name of it as well, as it is case sensetive and you have provided the proper details of server.
check these blog as well...
/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
/people/shabarish.vijayakumar/blog/2006/08/01/along-came-a-file-adapter-mr-ftp-and-rest-of-the-gang
Sachin
Edited by: Sachin Dhingra on Mar 24, 2009 12:16 PM

Error in Sender AXIS adapter with UsernameToken

Hello,
I'm trying to implement a web service with UsernameToken authentication (legacy >PO>ECC), after research in this forum, some blogs and notes, I've found this approach: Axis Adapter Sender Comm Channel with usernameToken .
I did all steps, but everytime I try to consume the web service, it doesn't work and I get the following error in default trace:
No application classloader can load login module class: com.sap.engine.services.security.server.jaas.DigestLoginModule. Probably application that deployed the login module is stopped and cannot be started.
My system is PO 7.4 SP5.
Do you have any idea?

Hi,
May be below links will help you
1. /people/michal.krawczyk2/blog/2005/12/18/xi-sender-mail-adapter--payloadswapbean--step-by-step
2. Have you used method of ConnectionFactory also??
3. 804102
xi 3.0 mail adapter with pop3 user authentication problem
4. 810238
XI 3.0 Mail Adapter for POP3 may not report some errors
Thanks
Swarup

Seeburger Sender AS2 adapter

We have a customer who purchased Seeburger AS2 Adapter. They have WAN setup with Inovis which is having AS2. Now we are in the process of setting up the AS2 using seeburger for them. if we use Seeburger AS2 adapter, then trading partners have to send their documents to the following path
http://<Server Name> :50000/SeeburgerAS2/AS2Server
Seeburger AS2 adapter will receive the documents posted to the above URL & Process them using XI
The problem we are facing is the Sender Seeburger AS2 adapter doesnt have a mechanism to Poll the Inovis AS2 Mailbox and receive the documents.
Does any one have a solution to Poll & fetch the documents from Inovis AS2 mailbox.
With Regards
K.Varadharajan

HI,
The message which are coming to XI will be picked up based on two things:
1) AS2 ID of the partner which is dicussed above and the second one is
2) Message subject :
Message Subject
This subject will be compared with the subject in the received message. This is used to find the correct channel for the inbound message. Wildcards are allowed.
There is a defined order in which the matching inbound channel is looked up. First the adapter looks for a sender channel with a message subject configured.
If there is one channel with a matching subject configured, the channel is used for forwarding the received payload to the XI system.
If there is no channel configured with an matching subject the received payload is rejected.
If there is one channel configured with a matching subject and another channel with a wildcard both channels will match. In this case the received payload is forwarded to the channel without wildcard configured.
If there is more than one channel configured with a matching subject, the payload is rejected.
I hopw it has answered ur question.
Thanks and regards,
Chirag
Reward points for helpful answers.

Error in Sender SOAP Adapter on XI 3.0 SP13

Hi All.
I have an application that sends a SOAP message to XI SOAP Adapter, to reach a synchronous interface. I've generated the .wsdl file from the Integration Directory, within the URL:
http://sapbox:59800/XISOAPAdapter/MessageServlet?channel=:BS_PORTAL:CC_S_SOAP_CREDITO
When I try to reach this URL, I get the successful response:
Message Servlet is in Status OK
I've also created the sender SOAP communication channel, fullfilling the default namespace and default interface correctly.
However, when I use wsnavigator client provided by SAP to prove the scenario, the SOAP message doesn't achieve XI, as the XISOAPAdapter EJB throws some exceptions:
HTTP/1.1 500 Internal Server Error
Connection: close
Server: SAP J2EE Engine/6.40
Content-Type: text/xml; charset=utf-8
Date: Sat, 17 Sep 2005 02:59:12 GMT
<?xml version='1.0'?>

<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>BaseEJBException</code>
 <text><![CDATA[
com.sap.aii.af.mp.processor.ModuleProcessorException
 at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:278)
 at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0.process(ModuleProcessorLocalLocalObjectImpl0.java:103)
 at com.sap.aii.af.mp.soap.web.MessageServlet.callModuleProcessor(MessageServlet.java:162)
 at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:508)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:159)
Caused by: com.sap.engine.services.ejb.exceptions.BaseEJBException: Exception in method process.
 at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl3.process(ModuleLocalLocalObjectImpl3.java:121)
 at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:227)
 ... 19 more
Caused by: java.lang.NoSuchMethodError: com.sap.aii.messaging.srt.xmb.XMBWebServiceExtension.setDynamicConfigurationMode(I)V
 at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.createXMBWSBubble(XISOAPAdapterBean.java:1129)
 at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.setup(XISOAPAdapterBean.java:265)
 at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:562)
 at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl3.process(ModuleLocalLocalObjectImpl3.java:103)
 ... 20 more
 ]]></text>
 </s:SystemError>
 </detail>
 </SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>
I've already done something really similar on SP 9. Can it be a new problem from SP13? Does anyone has any idea?
Thanks in advance.
Deise Lima.

Hi Naveen,
I have configured a SOAP sender adapter in XI 3.0 and is using the URL
http://host:port/XISOAPAdapter/MessageServlet?channel=:BS_WEBSERVICE:CC_WEBSERVICE_SOAP to post the messages. When I open the URL in the browser I am getting the error.
Message Servlet is in Status ERROR
Status information:
Servlet com.sap.aii.af.mp.soap.web.MessageServlet (Version $Id: //tc/aii/30_VAL_REL/src/_adapters/_soap/java/com/sap/aii/af/mp/soap/web/MessageServlet.java#5 $) bound to /MessageServlet
Classname ModuleProcessor: null
Lookupname for localModuleProcessorLookupName: localejbs/ModuleProcessorBean
Lookupname for remoteModuleProcessorLookupName: null
ModuleProcessorClass not instantiated
ModuleProcessorLocal not instantiated
ModuleProcessorRemote not instantiated
But when I test the URL http://host:port/XISOAPAdapter/HelperServlet?action=FindChannel&channel=:BS_WEBSERVICE:CC_WEBSERVICE_SOAP to check the communication channel I am getting the right response as below.
<?xml version="1.0" ?>
http://host:port/XISOAPAdapter/HelperServlet?action=FindChannel&channel=:BS_WEBSERVICE:CC_WEBSERVICE_SOAP <s:ChannelInfo xmlns:s="http://sap.com/xi/WebService/xi30">
<channelID>e7ac884596ea3d088cbfd8b434f942f2</channelID>
<name>CC_WEBSERVICE_SOAP</name>
<type xmlns:st="http://sap.com/xi/XI/System">st:SOAP</type>
<direction>INBOUND</direction>
<party />
<service>BS_WEBSERVICE</service>
</s:ChannelInfo
I used the http capture to debug, In the 1st case though I am getting "Message Servlet in status error" I am seeing a 200 OK code in the http capture tool. When the message is posted from .net client proxy or Altova XML Spy we are getting a 500 internal server error.
Am not sure what causes the error

RWB error in Sender JDBC adapter

Hi All,
I am using SP at sender communication channel. When I am activating the Sendr CC I am getting the The statement did not return a result set. error.
But when I lgged to database server and checked the SP it was working fine and giving the values in table. means SP is producing result set.
what could be the possible resong for the error.
regards
rams

Hi,
1. turn on the logging in SQL server
2. start jdbc adapter on XI
3. check logs on SQL server
Regards,
Michal Krawczyk

Error initializing Sender JMS Adapter

Hi,
Has anyone integrated MQSeries 5.3 with XI 3.0? I have placed all the necessary jar files under tech_adapter and in class path.My adapter status is red and the log says that
 ". ...andler moduleHandler, Parameter para) [Thread[Thread-11,5,main]] Error: java.lang.NoSuchMethodException
 at java.lang.Class.getConstructor0(Native Method)
 at java.lang.Class.getConstructor(Unknown Source)
 at com.sap.aii.messaging.adapter.ModuleJMS2Transport.init(ModuleJMS2Transport.java:351)
 at com.sap.aii.messaging.adapter.ModuleHandlerImpl.run(ModuleHandlerImpl.java:576)
 at java.lang.Thread.run(Unknown Source)"
please let me know if i am missing something.
Regards
Sathya

Hi Amol,
 Our SLD Accessor service is working properly.i have deployed all the necessary jar files.I am not very confident in my class path settings.So i am sending my class path,
 D:\usr\sap\MTX\DVEBMGS00\j2ee\cluster\server0\bin\ext\com.sap.aii.af.jmsproviderlib\classes12.zip;D:\usr\sap\MTX\DVEBMGS00\j2ee\cluster\server0\bin\ext\com.sap.aii.af.jmsproviderlib\com.ibm.mqjms.jar;D:\usr\sap\MTX\DVEBMGS00\j2ee\cluster\server0\bin\ext\com.sap.aii.af.jmsproviderlib\com.ibm.mq.jar;D:\usr\sap\MTX\DVEBMGS00\j2ee\cluster\server0\bin\ext\com.sap.aii.af.jmsproviderlib\connector.jar;D:\usr\sap\MTX\DVEBMGS00\j2ee\cluster\server0\bin\ext\com.sap.aii.af.jmsproviderlib\com.ibm.mqbind.jar;D:\usr\sap\BWXI\SYS\global\tech_adapter\server.jar;com.sap.aii.messaging.adapter.AdapterImpl;D:\usr\sap\BWXI\SYS\global\tech_adapter\ejb.jar;
please look into that.
I am sending the log trace for Adapter Configuration so that you can make something out of it.
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: >>>>>
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Starting adapter engine version 3.0.0318 ($Id: //tc/aii/30_REL/src/_messaging/java/com/sap/aii/messaging/adapter/AdapterImpl.java#7 $, $DateTime: 2004/08/03 11:19:35 $ ) ...
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: sync.time: 200411110440
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: jdk.version: 1.3.1
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: make.rel: 30_REL
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: build.date: 2004-11-11 04:58
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: latest.change: 300224
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: make.server: PWDFM060
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: >>>>>
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: main adapter properties file found: 'D:\usr\sap\BWXI\SYS\global\tech_adapter\adapter_base.properties'
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: main adapter properties file found: 'D:\usr\sap\BWXI\SYS\global\tech_adapter\adapter.properties'
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: initializing and starting with given Parameters ...
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: - Token File token.keystoragenot found
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Reading property file 'adapter_base.properties' for adapter modules configuration...
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: adapterID set to Adapter1
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: AdapterMonitor - expects property file 'BaseConfiguration/AdapterMonitor.properties'
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Constructed handler for Module AdapterMonitor
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Created module AdapterMonitor
Apr 26, 2006 10:08:22... ...i.messaging.adapter.ModuleHandlerImpl [Thread[Thread-0,5,main]] Info: Module 'com.sap.aii.messaging.adapter.ModuleAdapterMonitor' created, version 2.0.1010
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Initialized module AdapterMonitor
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Started module AdapterMonitor
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: InfoLogger - expects property file 'BaseConfiguration/InfoLogger.properties'
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Constructed handler for Module InfoLogger
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Created module InfoLogger
Apr 26, 2006 10:08:22... ...i.messaging.adapter.ModuleHandlerImpl [Thread[Thread-1,5,main]] Info: Module 'com.sap.aii.messaging.adapter.ModuleInfoLogger' created, version 2.0.0918
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Initialized module InfoLogger
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Started module InfoLogger
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: IDLogger - expects property file 'BaseConfiguration/IDLogger.properties'
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Constructed handler for Module IDLogger
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Created module IDLogger
Apr 26, 2006 10:08:22... ...i.messaging.adapter.ModuleHandlerImpl [Thread[Thread-2,5,main]] Info: Module 'com.sap.aii.messaging.adapter.ModuleIDLogger' created, version 1.0.0523
Apr 26, 2006 10:08:22... ....aii.messaging.adapter.ModuleIDLogger [Thread[Thread-2,5,main]] Info: Initializing new IDLogger object(version 1.0.0523), root directory is 'Data'
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Initialized module IDLogger
Apr 26, 2006 10:08:22... ....aii.messaging.adapter.ModuleIDLogger [Thread[Thread-2,5,main]] Info: IDLogger started
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Started module IDLogger
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: RtcMonitor - expects property file 'BaseConfiguration/RtcMonitor.properties'
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Constructed handler for Module RtcMonitor
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Created module RtcMonitor
Apr 26, 2006 10:08:22... ...i.messaging.adapter.ModuleHandlerImpl [Thread[Thread-3,5,main]] Info: Module 'com.sap.aii.messaging.adapter.ModuleRtcMonitor' created, version 1.0.0819
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Initialized module RtcMonitor
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Started module RtcMonitor
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: PersistLayer - expects property file 'BaseConfiguration/PersistLayer.properties'
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Constructed handler for Module PersistLayer
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Created module PersistLayer
Apr 26, 2006 10:08:22... ...i.messaging.adapter.ModuleHandlerImpl [Thread[Thread-4,5,main]] Info: Module 'com.sap.aii.messaging.adapter.ModulePersistLayer' created, version 2.0.0929
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Initialized module PersistLayer
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Started module PersistLayer
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: PWtokens - expects property file 'BaseConfiguration/PWtokens.properties'
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Constructed handler for Module PWtokens
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Created module PWtokens
Apr 26, 2006 10:08:22... ...i.messaging.adapter.ModuleHandlerImpl [Thread[Thread-5,5,main]] Info: Module 'com.sap.aii.messaging.adapter.ModulePWtokens' created, version 1.0.0724
Apr 26, 2006 10:08:22... ....aii.messaging.adapter.ModulePWtokens [Thread[Thread-5,5,main]] Info: Initializing new PWtoken object(version 1.0.0724), root directory is '.'
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Initialized module PWtokens
Apr 26, 2006 10:08:22... ....aii.messaging.adapter.ModulePWtokens [Thread[Thread-5,5,main]] Info: Getting parameters: default value '<!%' set for parameter 'PWD.beginSeparator'
Apr 26, 2006 10:08:22... ....aii.messaging.adapter.ModulePWtokens [Thread[Thread-5,5,main]] Info: Getting parameters: default value '%!>' set for parameter 'PWD.endSeparator'
Apr 26, 2006 10:08:22... ....aii.messaging.adapter.ModulePWtokens [Thread[Thread-5,5,main]] Info: SLDaccessor started
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Started module PWtokens
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: GUIBrowserEngine - expects property file 'BaseConfiguration/GUIBrowserEngine.properties'
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Constructed handler for Module GUIBrowserEngine
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Created module GUIBrowserEngine
Apr 26, 2006 10:08:23... ...i.messaging.adapter.ModuleHandlerImpl [Thread[Thread-6,5,main]] Info: Module 'com.sap.aii.messaging.adapter.ModuleGUIBrowserEngine' created, version 3.0.1930
Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Initialized module GUIBrowserEngine
Apr 26, 2006 10:08:23... ...saging.adapter.ModuleGUIBrowserEngine [Thread[Thread-6,5,main]] Info: GUIBrowserEngine started
Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Started module GUIBrowserEngine
Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: HttpServer - expects property file 'BaseConfiguration/HttpServer.properties'
Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Constructed handler for Module HttpServer
Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Created module HttpServer
Apr 26, 2006 10:08:23... ...i.messaging.adapter.ModuleHandlerImpl [Thread[Thread-7,5,main]] Info: Module 'com.sap.aii.messaging.adapter.ModuleHttpServer' created, version 1.0.0808
Apr 26, 2006 10:08:23... ...ii.messaging.adapter.ModuleHttpServer [Thread[Thread-7,5,main]] Info: Initializing new HttpServer object(version 1.0.0808), root directory is '.\Data'
Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Initialized module HttpServer
Apr 26, 2006 10:08:23... ...ii.messaging.adapter.ModuleHttpServer [Thread[Thread-7,5,main]] Info: Http server started
Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Started module HttpServer
Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: SLDaccessor - expects property file 'BaseConfiguration/SLDaccessor.properties'
Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Constructed handler for Module SLDaccessor
Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Created module SLDaccessor
Apr 26, 2006 10:08:23... ...i.messaging.adapter.ModuleHandlerImpl [Thread[Thread-9,5,main]] Info: Module 'com.sap.aii.messaging.adapter.ModuleSLDaccessor' created, version 2.0.1010
Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Initialized module SLDaccessor
Apr 26, 2006 10:08:23... ...aii.messaging.adapter.ModuleSLDaccess [Thread[Thread-9,5,main]] Info: Initializing new SLDaccessor object(version 2.0.1010), root directory is '.\Data'
Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Started module SLDaccessor
Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: jms_sender2is - no property file specified - try default 'Configuration/jms_sender2is.properties
Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: jms_sender2is - expects property file 'Configuration/jms_sender2is.properties'
Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Constructed handler for Module jms_sender2is
Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Created module jms_sender2is
Apr 26, 2006 10:08:23... ...i.messaging.adapter.ModuleHandlerImpl [Thread[Thread-11,5,main]] Info: Module 'com.sap.aii.messaging.adapter.ModuleJMS2Transport' created, version 2.0.1626
Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Initialized module jms_sender2is
Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Fatal: Adapter engine startup procedure finished: 9 modules started successfully
Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Fatal: Adapter engine running...
Apr 26, 2006 10:08:23... com.sap.aii.messaging.adapter.IDLogImpl [Thread[Thread-11,5,main]] Info: Attached persistent hashtable to file 'D:\usr\sap\BWXI\SYS\global\tech_adapter\Data\jms_sender2is_ID.dat'
Apr 26, 2006 10:08:23... ....aii.messaging.adapter.ModuleIDLogger [Thread[Thread-11,5,main]] Info: Created new ID log file 'jms_sender2is_ID.dat' in folder 'Data' for module 'jms_sender2is'
Apr 26, 2006 10:08:23... ...p.aii.messaging.adapter.XMBParameters [Thread[Thread-11,5,main]] Info: Getting parameters: default value '' set for parameter 'XI.SenderParty'
Apr 26, 2006 10:08:23... ...p.aii.messaging.adapter.XMBParameters [Thread[Thread-11,5,main]] Info: Getting parameters: default value '' set for parameter 'XI.ReceiverParty'
Apr 26, 2006 10:08:23... ...andler moduleHandler, Parameter para) [Thread[Thread-11,5,main]] Error: java.lang.NoSuchMethodException
 at java.lang.Class.getConstructor0(Native Method)
 at java.lang.Class.getConstructor(Unknown Source)
 at com.sap.aii.messaging.adapter.ModuleJMS2Transport.init(ModuleJMS2Transport.java:351)
 at com.sap.aii.messaging.adapter.ModuleHandlerImpl.run(ModuleHandlerImpl.java:576)
 at java.lang.Thread.run(Unknown Source)
Apr 26, 2006 10:08:28... ...duleSLDaccess.createAdapterEntities() [Thread[Thread-9,5,main]] Info: Adapter Entities for AdapterEngine_bwxi_8200 created successfully
Apr 26, 2006 10:08:29... ...duleSLDaccess.createAdapterServices() [Thread[Thread-9,5,main]] Info: Adapter Services for AdapterEngine_bwxi_8200 created successfully
Apr 26, 2006 10:08:29... ...aii.messaging.adapter.ModuleSLDaccess [Thread[Thread-9,5,main]] Info: SLDaccessor started
Regards
Sathya

Error using sender ws adapter

Hi,
I am getting the following error while using the WS adapter at the sender side.
the SOAP response indicates that an error occurred:
System Error
<detail><s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0"><context></context><code>INTERNAL.IN_BIND_WRONG_ADPT</code><text>Sender agreement found belongs to adapter WS, however the current adapter is XI</text></s:SystemError></detail>
Please help me in resolving this issue.
Thanks & Regards,
Hamsa Shree

Hi Prateek,
Thanks for ur reply.
I have used WS adapter at the sender side. And the communication channel provided in the sender agreement is correct.
Thanks & Regards,
Hamsa Shree

Error using Sender SOAP adapter over HTTPS

Hi experts,
Few weeks ago, i developed an interface as follows: SOAP <-> XI <-> RFC.
I tested the functionality using Altova and everything went well, with HTTP.
However, when i use HTTPS it fails throwing these error messages (pop ups):
"HTTP error: could not post file"......
"Error sending the soap data"
I have reviewed the SSL certificates installation and everything seems to be ok, but currently i am stuck and do not know how to fix this.
I have also change the ID comm channel from HTTP to HTTPS with client aut.
Is there any special service i have to activate? (XI services and SPIGATE are already done)
Could you please assist?
Thanks in advance and best regards,
David

David,
have a look @ these threads...u may get some help!!!
Sender Soap with HTTPS
https Soap Adapter
Regards
Biplab

Sender AS2 adapter settings for Asynchronous MDN

Hello,
I need to configure the settings for AS2 sender adapter for Asynchronous MDN.
In order to configure the asynchrounous MDN Settings which parametrs i need to fill in the channel from below
1) Use Proxy
2) Proxy Server
3) Proxy Port
4) Proxy User
5) Proxy Password
6) Proxy Realm
7) Proxy Protocol
8) Server Certificate (Keystore)
9) Private Key for Client Authentication
Thanks
Srinivas

Hi,
The MDN asynchronous mode is for the AS2 receiver adapter and not sender.
If you want to use a proxy server, then only you would need to provide the details that you have mentioned and if you are using encryption, you would need to provide the encryption certificate in the corresponding receiver agreement where the comm channel is used.
Also, for asynchronous MDN, you would need to configure a report channel (AS2 sender adapter with message protocol reports) and sender agreement. You need this even if Refer to XI system option is disabled in the AS2 receiver adapter.
Regards

Connectivity from Customer to sender AS2 adapter

Hi Guys,
My scenario is EDI to File, to send the data we provided our HTTP IP, port and URL to customer, here URL is https://<host_name>:<port> by using this URL we are able to receive the message upto our network, so how to get that data from network to PI System?
Any other thing we need to add to the URL path like https://<host_name>:<port>/AS2 ID or ..... ?
If yes how exactly we know we need to add AS2 or EDI or ......
Please advice me.
Thanks
Ramesh

Hi Sanju,
If we are getting the 405 error means it is success (In one of Seeburger documentation they mentioned).
My scenario is EDI to file, next file to FCC at the same time send 997 to sender, who sends the actual data.
I am able to get the message to my network (ports are open, firewall allows the data), but not getting to PI or Seeburger system.
Any one please suggest me the possible ways to trouble shoot that error.
Thanks
Ramesh

Error in Sender AS2 adapter

Similar Messages

Maybe you are looking for