To enable Axis adapter framework

Hi All ,
We are going to use Axis adapter framework in AAR PI landscape(X6* track). As we understood, this is SAP provided by default with PI but there are some more additional JARs need to be installed to enable this functionality.
Do we need downtime for this activity?
avindar,a

Hi Rainder
Could you refer the SAP Note 1039369 - FAQ XI Axis Adapter for your request. and also you can search SCN or Google about your requirement you can find some many threads
Regards
Sriram

Similar Messages

How to deploy AXIS adapter frame work in sap pi

Hi All ,
We are going to use Axis adapter framework in AAR PI landscape(X6* track). As we understood, this is SAP provided by default with PI but there are some more additional JARs need to be installed to enable this functionality.
Do we need downtime for this activity?
How to to deploy some standard JAR files in SAP PI
system to enable Axis adapter framework PI systems.

Hi Rainder
Could you refer the SAP Note 1039369 - FAQ XI Axis Adapter for your request. and also you can search SCN or Google about your requirement you can find some many threads
Regards
Sriram

Axis Adapter Framwork Error

Hi
I am not able to access the axis adapter framework like i.e. (http://host:port/XIAxisAdapter/MessageServlet)
When am trying to access i am the following getting error.
Error:
404 Not Found
The requested resource does not exist.
Please provide me solution for this?
Regards
Osman Abdul Aziz Jabri

Hi Osman,
Kindly check this note:
#1039369 - FAQ XI Axis Adapter
It may helps with most common issues and doubts.
Regards,
Caio Cagnani

PI 7.11 Receiver SOAP (Axis) Adapter with MTOM (Attachments)

Hello,
Iu2019m trying to configure the Receiver SOAP (Axis) adapter for sending SOAP attachments via MTOM to a third-party webservice, but I'm not getting that PI transform the binary encode64 data in an payload element into a MTOM attachment (xop:include).
The configuration looks like this:
Transport Protocol: HTTP (Axis)
SOAP Version: 1.2
Encapsulation Format: MTOM
Keep Attchments: enabled
Payload Extraction: SOAP Body Child
First of all, could you confirm if this is supported?
Or Axis only supports MTOM for the transport protocol 'File (Axis)' like it seems refered in [Configuring the Receiver Axis SOAP Adapter|http://help.sap.com/saphelp_nwpi711/helpdata/en/45/a3c48c87cd0039e10000000a11466f/frameset.htm]
Can you please provide me some guidance here?
Thanks in advance!
Kind Regards,
Alexandre

Hello,
I am facing the exact same issue.
I can't seem to set the cookie in the http header after following the guide.
Cookie: WSL-credential=MyOwnCookie
I managed to set the SOAPAction though.
Anyone has any ideas?

Error while passing URL Dynamically in SOAP AXIS adapter..!!

Hi ,
Idoc> XI>SOAP-AXIS
I am doing a scenario where I need to pass the URL dynamically in SOAP-AXIS adapter by taking the RCVPRN of Idoc.
If
RCVPRN = 100 , message has to go to http://10.190.25.16:8210/file/receiver
RCVPRN = 200 , message has to go to http://10.190.25.16:8210/file/receiver2
RCVPRN = 300 , message has to go to http://10.190.25.16:8210/file/receiver3
I used the below UDF and it is working correctly and generating the URL dynamically .
DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey keyHeader1 = DynamicConfigurationKey.create( "http://sap.com/xi/XI/System/SOAP", "TServerLocation");
conf.put(keyHeader1, a);
return "";
The value is coming in SOAP document as expected like below.
<sap:DynamicConfiguration xmlns:sap="http://sap.com/xi/XI/Message/30" SOAP:mustUnderstand="1">
<sap:Record namespace="http://sap.com/xi/XI/System/SOAP" name="TServerLocation">http://10.190.25.16:8210/file/receiver3</sap:Record>
</sap:DynamicConfiguration>
I used the below Configuration modules in receiver SOAP-AXIS adapter as suggested in Note 1028961.
AF_Adapters/axis/AFAdapterBean ---> afreq
AF_Adapters/axis/HandlerBean ---> xireq
AF_Adapters/axis/HandlerBean ---> dc
AF_Adapters/axis/HandlerBean ---> remover
AF_Adapters/axis/HandlerBean ---> trp
AF_Adapters/axis/HandlerBean ---> xires
AF_Adapters/axis/AFAdapterBean ---> afres
xireq -> handler.type-> java:com.sap.aii.axis.xi.XI30OutboundHandler
dc -> handler.type-> javasap.aii.axis.xi.XI30DynamicConfigurationHandler
dc ---> key.1 ---> write http://sap.com/xi/XI/System/SOAP TServerLocation
dc ---> location.1 ---> context
dc ---> value.1 ---> transport.url
remover ---> handler.type ---> java:com.sap.aii.axis.soap.HeaderRemovalHandler
remover ---> namespace ---> http://sap.com/xi/XI/Message/30
trp ---> handler.type ---> java:com.sap.aii.adapter.axis.ra.transport.http.HTTPSender
trp ---> module.pivot ---> true
xires ---> handler.type ---> java:com.sap.aii.axis.xi.XI30OutboundHandler
and I am getting the below error in SOAP-AXIS channel at the point java:com.sap.aii.adapter.axis.ra.transport.http.HTTPSender.
2009-03-02 15:23:44 Success Axis: getting handler trp of java:com.sap.aii.adapter.axis.ra.transport.http.HTTPSender
2009-03-02 15:23:45 Error Axis: error in invocation: (500)internal server error
2009-03-02 15:23:45 Error MP: Exception caught with cause (500)internal server error
2009-03-02 15:23:45 Error Exception caught by adapter framework: (500)internal server error
2009-03-02 15:23:46 Error Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: (500)internal server error: (500)internal server error.
2009-03-02 15:23:46 Error The message status set to NDLV.
Kindly let me know if anyone has any idea what might be wrong?
Note : The given URL is correct one because I cross checked by passing them normally by giving directly in adapter and they are all working and the message is going to receiver.
Thanks
Deepthi

Hi Stefan,
>> dc -> handler.type-> javasap.aii.axis.xi.XI30DynamicConfigurationHandler
>> dc ---> key.1 ---> write http://sap.com/xi/XI/System/SOAP TServerLocation
>> dc ---> location.1 ---> context
>> dc ---> value.1 ---> transport.url
>> Try read instead of write
When I tried with this, I am getting the below error "Connection refused ".
Success Axis: entering HandlerBean
Success Axis: getting handler trp of java:com.sap.aii.adapter.axis.ra.transport.http.HTTPSender
Error Axis: error in invocation: java.net.ConnectException: Connection refused
Error MP: Exception caught with cause java.net.ConnectException: Connection refused
Error Exception caught by adapter framework: ; nested exception is: java.net.ConnectException: Connection refused
Error Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: ; nested exception is: java.net.ConnectException: Connection refused: java.net.ConnectException: Connection refused.
Success The message status set to WAIT.
It is going successfully when I tried sending directly. Looks like Dynamic Configuration is not working for SOAP-AXIS.
Any Suggestion?
Thanks
Deepthi.

Problem with Dynamic Configuration in SOAP-AXIS adapter..!!!

Hi ,
Idoc> XI>SOAP-AXIS
I am doing a scenario where I need to pass the URL dynamically in SOAP-AXIS adapter by taking the SNDPRN of Idoc.
If SNDPRN = 100 , message has to go to http://10.190.25.16:8210/file/receiver
   SNDPRN = 200 , message has to go to http://20.180.26.16:8210/file/receiver
It is working correctly when I tried for single receiver. When I' tried to use DynamicConfiguration, it is coming in SOAP document but it is not working and not passing to correct channel. According to this note 1039369, I mentioned the following modules.
AF_Adapters/axis/AFAdapterBean --->                 afreq
AF_Adapters/axis/HandlerBean      --->                  xireq
AF_Adapters/axis/HandlerBean      --->                  dc
AF_Adapters/axis/HandlerBean       --->                 remover
AF_Adapters/axis/HandlerBean       --->                 trp
AF_Adapters/axis/HandlerBean        --->                xires
AF_Adapters/axis/AFAdapterBean    --->               afres
xireq -> handler.type-> java:com.sap.aii.axis.xi.XI30OutboundHandler
dc    -> handler.type-> javasap.aii.axis.xi.XI30DynamicConfigurationHandler
dc   --->   key.1 --->      write http://sap.com/xi/XI/System/SOAP TServerLocation
dc    --->          location.1 --->         context
dc     --->         value.1      --->        transport.url
remover    ---> handler.type    --->   java:com.sap.aii.axis.soap.HeaderRemovalHandler
remover     ---> namespace    --->      http://sap.com/xi/XI/Message/30
trp         --->     handler.type   --->    java:com.sap.aii.adapter.axis.ra.transport.http.HTTPSender
trp           ---> module.pivot --->     true
xires     --->    handler.type   --->    java:com.sap.aii.axis.xi.XI30OutboundHandler
and I am getting the below error in SOAP-AXIS channel
Error Axis:    error in invocation: java.lang.IllegalArgumentException: object type invalid: class com.sap.aii.adapter.xi.ms.XIMessage
Error MP:     Exception caught with cause java.lang.IllegalArgumentException: object type invalid: class com.sap.aii.adapter.xi.ms.XIMessage
Error           Exception caught by adapter framework: object type invalid: class com.sap.aii.adapter.xi.ms.XIMessage
Error Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: object type invalid: class com.sap.aii.adapter.xi.ms.XIMessage: java.lang.IllegalArgumentException: object type invalid: class com.sap.aii.adapter.xi.ms.XIMessage
Kindly let me know if anyone has any idea what might be wrong?
Thanks
Deepthi

I have a similar problem. I also like to add some header fields to my message und that's way I'm trying to use the AXIS adapter. (Axis adapter FAQ question 30) Unfortunately I'm getting exactly the same error message:
com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.IllegalArgumentException: object type invalid: class com.sap.aii.adapter.xi.ms.XIMessage
Deepthi, you wrote that you have missed one jar file. Can you remember which file it was?

Adapter Framework caught exception - 401

Hi,
I am trying to use NTLM authentication using Axis adapter in PI 7.1 SP7 but getting 401 error.
Axis adapter works for Basic auth.
SAP Note 856597 talks about giving PI user security role xi_adapter_soap_message. Haven't found the equivalent navigation of visual admin in NWA.
Details from message monitoring
Information Axis: getting handler trp of java:com.sap.aii.adapter.axis.ra.transport.http.HTTPSender
Error Axis: error in invocation: (401)Unauthorized
Error Adapter Framework caught exception: (401)Unauthorized
Error Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: (401)Unauthorized.
Any help is appreciated.
Thanks
Kiran Gollapudi

Hi guys,
Even the message being old, there are some of you that may want a hint on how to solve this problem.
First of all, please refer to the generic description of the error that may help one of you:
401 Unauthorized
Description: The request requires user authentication
Possible Tips:
u2022 Check XIAPPLUSER is having this Role -SAP_XI_APPL_SERV_USER
u2022 If the error is in XI Adapter, then your port entry should J2EE port 5<System no>
u2022 If the error is in Adapter Engine
u2013then have a look into SAP note- 821026, Delete the Adapter Engine cache in transaction SXI_CACHE Goto --> Cache.
u2022 May be wrong password for user XIISUSER
u2022 May be wrong password for user XIAFUSER
u2013 for this Check the Exchange Profile and transaction SU01, try to reset the password -Restart the J2EE Engine to activate changes in the Exchange Profile After doing this, you can restart the message
Alternatively, ensure you maintain the correct password for all the service users according to one of the notes
below, taking into account your system version:
PI 7.1:
#999962 - PI 7.10: Change passwords of PI service users
XI 7.0
#936093 - XI 7.0: Changing the passwords of XI service users
XI 3.0
#721548 - XI 3.0: Changing the passwords of the XI service users
Hope I could helped.
Regards,
Caio Cagnani

Problem with Axis Adapter endpoint url in WSDL file.

Dear experts,
We are using PI 7.1 ehp1 with a SOAP to RFC scenarios using the Axis adapter.
We have the XIAxisAdapter as sender Communication Channel and the related Sender Agreement.
When i am looking into the WSDL file of the Sender Agreement than the endpoint contains ...location="host:port/ XISOAPAdapter /MessageServlet"... in stead of ...location="host:port/ XIAxisAdapter /MessageServlet"...
The url with "XISOAPAdapter " will not work. When i export the WSDL file and manually adjust the location to "XIAxisAdapter " everything works fine.
Is it possible to directly generate a correct WSDL with calling the url http://host:50000/dir/wsdl?p=xxxx?
Thanks in advance!
Best regards,
Joost Weghorst

Hi Sonya,
You can use configuration plan while deploying composite.
The configuration plan enables you to define the URL and property values to use in different environments. During process deployment, the configuration plan is used to search the SOA project for values that must be replaced to adapt the project to the next target environment.
Please refer this doc. for getting introduced to config plan.
http://docs.oracle.com/cd/E29542_01/dev.1111/e10224/sca_lifecycle.htm#SOASE10908
To deploy soa composite with config plan refer this doc:
http://docs.oracle.com/cd/E29542_01/dev.1111/e10224/sca_lifecycle.htm#SOASE85469

Adapter Framework unable to create outbound JCA connection

Hi All,
I have a requirement in which I have to send a request from Siebel to SAP & get a response from it.
I have deployed my process on Oracle AS BPEL console.
When I try to initiate my deployed process I get below mentioned error.
<summary>
http://127.0.0.1:8888/orainfra/wsil/adapters/applications/GetDetail_invoke.wsdl?wsdl [ GetDetailPortType::GetDetail(input_GetDetail,output_GetDetail) ] - WSIF JCA Execute of operation 'GetDetail' failed due to: Adapter Framework unable to create outbound JCA connection.
http://127.0.0.1:8888/orainfra/wsil/adapters/applications/GetDetail_invoke.wsdl?wsdl [ GetDetailPortType::GetDetail(input_GetDetail,output_GetDetail) ] - : The Adapter Framework was unable to establish an outbound JCA connection due to the following issue: javax.resource.spi.EISSystemException: IWAFManagedConnectionFactory:Exception javax.resource.ResourceException: Problem activating adapter. (JCO.classInitialize(): Could not load middleware layer 'com.sap.mw.jco.rfc.MiddlewareRFC'
JCO.nativeInit(): Could not initialize dynamic link library sapjcorfc [no sapjcorfc in java.library.path]. java.library.path [D:\product\10.1.3.1\OracleAS_1\jdk\bin;.;C:\WINDOWS\system32;C:\WINDOWS;D:\product\10.1.3.1\OracleAS_1\opmn\bin;D:\product\10.1.3.1\OracleAS_1\opmn\lib;D:\product\10.1.3.1\OracleAS_1\bin;C:\WINDOWS;C:\WINDOWS\system32]). Check logs for more information
; nested exception is:
ORABPEL-12511
Adapter Framework unable to create outbound JCA connection.
http://127.0.0.1:8888/orainfra/wsil/adapters/applications/GetDetail_invoke.wsdl?wsdl [ GetDetailPortType::GetDetail(input_GetDetail,output_GetDetail) ] - : The Adapter Framework was unable to establish an outbound JCA connection due to the following issue: javax.resource.spi.EISSystemException: IWAFManagedConnectionFactory:Exception javax.resource.ResourceException: Problem activating adapter. (JCO.classInitialize(): Could not load middleware layer 'com.sap.mw.jco.rfc.MiddlewareRFC'
JCO.nativeInit(): Could not initialize dynamic link library sapjcorfc [no sapjcorfc in java.library.path]. java.library.path [D:\product\10.1.3.1\OracleAS_1\jdk\bin;.;C:\WINDOWS\system32;C:\WINDOWS;D:\product\10.1.3.1\OracleAS_1\opmn\bin;D:\product\10.1.3.1\OracleAS_1\opmn\lib;D:\product\10.1.3.1\OracleAS_1\bin;C:\WINDOWS;C:\WINDOWS\system32]). Check logs for more information
Please examine the log file for any reasons. Enable DEBUG logging in the BPEL Console.
</summary>
I have installed Oracle Adapter 10.1.3.1 on Oracle SOA Suite 10.1.3.1 & then upgraded my SOA Suite to 10.1.3.3.
Its a very critical issue.
Please help me out of it.
Thanks & Regards,
Shanty

I have resolved this error.
If you are facing the same error then follow the following steps:
1. Shutdown the Oracle SOA Suite.
2. Copy sapjcorfc.dll into C:\WINDOWS\system32
3.Edit oc4j-ra.xml located at below locations
a. OracleHome\j2ee\home\application-deployments\default\jca-app-adapter
b. OracleHome\j2ee\home\connectors\jca-app-adapter\jca-app-adapter\META-INF
by editing the values
<config-property name="AdapterName" value="SAP"/>
<config-property name="Config" value="SAP_Target_You_Have_Created_in_iaexplorer"/>
Cheers,
Shanty

Axis adapter : Bad Request error

Hi,
I have a File to SOAP scenario (PI 7.0) where I am using AXIS adapter in the receiver SOAP adapter for NTLM authorisation. In the xml that I am trying to post, i have characters like & because of which I am getting a Bad Request error. Is there a way to resolve this? thanks!
Regards
Pushpinder

In file sender channel, i am using binary mode, so no encoding specified.
I see the error in the receiver SOAP adapter -
Error Axis: error in invocation: (400)Bad Request
Error Exception caught by adapter framework: (400)Bad Request
Error MP: Exception caught with cause (400)Bad Request
Error Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: (400)Bad Request: (400)Bad Request.
Error The message status set to NDLV.

What exactly can AXIS Adapter do?

Can someone give me a scenario when only SOAP Adapter is not enough and I will have to deploy AXIS adapter to complement SOAP adapter? Is AXIS adapter useful even if i am not implementing any 'message-level' security?
Can message be posted to AXIS adapter without clinet having to authenticate to AxisAdapter?
I have an XI web service that my clinet is unable to consume as they don't know how to authnticate to SOAP adapter before sending a SOAP message. We don't have any 'message-level' security, but SOAP adapter requires Basic authentication. Client is able to pass Authentication details in SOAP Header but I guess they first need to authenticate to SOAP adapter before sending SOAP messages. can AXIS adapter accept incoming SOAp messages without user authenticating and then extract Logon details from SOAP header and authenticate client.
Thanks,
Saurabh

The Axis framework provides the following:
●      Message protocols SOAP 1.1 and SOAP 1.2
●      Transport protocols HTTP/S, SMTP, file
●      Various user authentication procedures (Basic, Digest, NTLM, SAP Assertion Tickets)
●      Various encapsulation formats (MIME, DIME, MTOM)
●      You can add your own Axis handlers to the module chain by using the HandlerBean module
Soap 1.2 message protocol is available for AXIS Soap Adapter.
please visit the article
/people/andre.stuij/blog/2008/04/23/principal-propagation-in-ccbpm-finally-made-possible
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b092777b-ee47-2a10-17b3-c5f59380957f
http://help.sap.com/saphelp_nw70/helpdata/en/45/a4f8bbdfdc0d36e10000000a114a6b/frameset.htm

Adapter framework

Hi all,
Is there any blog that explains about adapter framework and adapter engine. If not, can someone please briefly explain me about adapter engine and the architecture? I have read the help.sap links. But still not clear.

Hi Aarthi ,
These r the details regarding Adapter Framework & Adapter Engine.
Adapter Framework :
It is a part of the Adapter Engine, which provides interfaces for configuring, managing, and monitoring adapters.SAP XI requires an adapter framework to communicate outside of the SAP system. These adapters translate code from external applications to an XML message for NetWeaver processes using the Java Connector Architecture.Adapter framework (JCA )based integrate application systems and business partners via resource adapters.
SAP XI provides a set of adapters to connect SAP as well as non-SAP applications with each other and thus to enable them to participate in the exchange of XML messages. An adapter is required to connect other applications or technical systems, or to participate in B2B communication via specific industry standards like RosettaNet. SAP provides certain adapters for use with SAP Exchange Infrastructure, and relies on an ecosystem of partners to provide adapters for other applications or industry standards. These partner adapters are sold and delivered through SAP.
The SAP Partner Connectivity Kit (PCK) enables smaller companies that do not dispose of an SAP XI installation to connect to SAP XI.
Customers and partners can also develop their own adapters for SAP XI. To do this, they can use the Adapter Framework in the Partner Connectivity Kit (PCK) and refer to the detailed documentation on adapter development. For more information, see SAP XI 3.0 Online documentation under SAP XI: Runtime → Connectivity → Partner Connectivity Kit → Adapter Development.
Overview of Adapters for SAP XI 3.0
Application Adapters
Technical Adapters
Industry Standard Adapters
Mainframe/Transaction Adapters
Note: All adapters are available from SAP XI 3.0 onwards.
Adapter Framework provides common functionality for Adapter
Engine and SAP Partner Connectivity Kit
Adapter Framework is based on SAP J2EE Engine as part of SAP Web AS.
Adapter Framework inherits properties and features such as scalability, clustering, high availability, thread management, etc.Adapter Framework provides its own queuing and logging services.Temporary stand-alone operation without connection to an Integration Server is possible, while still providing e. g. guaranteed exactly once messaging to and from connected application system
Adapter Framework supports J2EE Connector Architecture (JCA)
JCA is standard architecture for connecting the J2EE platform to
Enterprise Information Systems (EIS), e. g. ERP, DBMS, etc.
A Resource Adapter plugs into an application server, providing
connectivity between the EIS and a Java application
JCA enabled Adapter Framework provides defined interfaces to
which both our adapters and 3rd party adapters can conform
JCA is a widely accepted standard that 3rd party adapter providers
are familiar with
Details about architecture of adapter, types of adapter.. can be found at the following web-sites :
http://help.sap.com/saphelp_nw04/helpdata/en/fd/16e140a786702ae10000000a155106/content.htm
http://publib.boulder.ibm.com/infocenter/wbihelp/v6rxmx/index.jsp?topic=/com.ibm.wbia_adapters.doc/doc/sap_xi/sapximst11.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/95d5e190-0201-0010-0daf-e9e270f85ebb
http://www.erpgenie.com/netweaver/xi/adapters/index.htm
http://documentation.softwareag.com/crossvision/xie311/admin/config.htm
http://www30.sap.com/korea/company/events/techday05/img/data_04.pdf
Adapter Engine :
You use the Adapter Engine to connect the Integration Engine to SAP systems (RFC adapter) and external systems. You use the various adapters in the Adapter Engine to convert XML- and HTTP-based messages to the specific protocol and format required by these systems, and the other way around.
The Adapter Engine is based on the adapter framework.
The Adapter Engine is a separate software component that is automatically installed on the Integration Server. In this case, it is the central Adapter Engine. However, you can also install the Adapter Engine separately on another host. This is then a non-central Adapter Engine.
The XI Adapter engine is the home of the majority of the XI adapters. Only the IDoc adapter and the plain HTTP adapter do not reside on the adapter engine. They reside on the Integration Server.
It is fully integrated in to the XI landscape with tools provided for configuration, logistics and monitoring. It's Adapter Framework is based on the JCA
Details about Adapter engine can be found at the following web-sites :
http://help.sap.com/saphelp_nw04/helpdata/en/f4/0a1640a991c742e10000000a1550b0/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/8f/d906d01f77fa40a4c84683c3f8326f/content.htm
********Please reward points if u find this useful
cheers,
gyanaraj

Message status "Holding" - Message monitoring adapter framework

Hello,
We have some messages with the status "Holding" in a queue in the message monitoring in the adapter framework.
Normally you have to restart the first message of that queue. The message with the status "system error". Unfortunately this message is not available anymore because it is older than 30 days and the retetion period is 30 days.
I already read the blog about "[How to deal with stuck EOIO messages in the XI 3.0 Adapter Framework|http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3417100)ID1887311350DB01819286872323159351End?blog=/pub/wlg/3566]"
The blog does not mention what to do when the first message (sequential number) is not available anymore.
Is it possible to restart the messages in the queue in that case?
Thanks
Kind regards
Frank

Unfortunately this message is not available anymore because it is older than 30 days and the retetion period is 30 days.
I assume that the message was deleted.....in this case the next message in the queue will be blocking the queue....so try resending this message....even the blog mentions that you either solve the error or cancel the message....so now start from the second message....if possible solve the error for this message....if not possible to resolve then cancel it so that rest of the queue gets processed
From the blog:
Now the erroneous message is the first message in the display. You can look at the error reason, try to fix the problem and
resend or cancel the message to release the queue.
Regards,
Abhishek.

Exchange rate SAOP-AXIS adapter - SAP PO 7.4

Hi Expert,
My requirement is to fetch exchange xml file from web link : http://www.nationalbanken.dk/DNUK/rates.nsf/rates.xml . I have gone through Michael blog: http://scn.sap.com/community/pi-and-soa-middleware/blog/2012/01/05/michals-pi-tips-exchange-rates-from-an-xml-file-on-a-web-page--rest-axis
And I have done everything same but nothing happening to sender adapter.
It is showing running but no log updated.
I am working SAP PO (Process Orchestration) 7.4 SP3.
I have gone through ......../XIAxisAdapter/MessageServlet and it show below details:
Axis Adapter Message Servlet
Component Versions
Adapter Common Library Version: 1.7.4003.20130911141725.0000, NW731EXT_08_REL (2013-09-11T18:40:12+0000)
Adapter Application Version: 1.7.4003.20130911141725.0000, NW731EXT_08_REL (2013-09-11T18:40:22+0000)
Axis Version: ???
Required Components
Apache-Axis
Error: required component missing --- looking for org.apache.axis.AxisEngine in com.sap.aii.af.axisproviderlib/axis.jar; see http://ws.apache.org/axis/
Jakarta-Commons Discovery
Error: required component missing --- looking for org.apache.commons.discovery.Resource in com.sap.aii.af.axisproviderlib/commons-discovery.jar; see http://jakarta.apache.org/commons/discovery/
Jakarta-Commons Logging
Error: required component missing --- looking for org.apache.commons.logging.Log in com.sap.aii.af.axisproviderlib/commons-logging.jar; see http://jakarta.apache.org/commons/logging/
Optional Components
Thanks in advance!
Kumar

HI Amit,
I see status as error:
Required Components
Apache-Axis
Error: required component missing --- looking for org.apache.axis.AxisEngine in com.sap.aii.af.axisproviderlib/axis.jar; see http://ws.apache.org/axis/
Jakarta-Commons Discovery
Error: required component missing --- looking for org.apache.commons.discovery.Resource in com.sap.aii.af.axisproviderlib/commons-discovery.jar; see http://jakarta.apache.org/commons/discovery/
Jakarta-Commons Logging
Error: required component missing --- looking for org.apache.commons.logging.Log in com.sap.aii.af.axisproviderlib/commons-logging.jar; see http://jakarta.apache.org/commons/logging/
Number of Missing Components: 3
Status: Error
Thanks,
Kumar

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

To enable Axis adapter framework

Similar Messages

Maybe you are looking for