JMS protocol with AXIS Adapter

Hi,
I need to configure the sender AXIS adapter to access SonicMQ JMS queues via Open LDAP. I looked at the AXIS Adapter documentation and no examples are provided to access SonicMQ via OpenLdap.
I do see the documentation to access the JMS providers directly by specifying the URL as "jms://ABCD"
but what i am looking for is to access the JMS objects via LDAP. The standard SAP JMS Adapter has the functionality to access JMS via LDAP. but i need to use AXIS adapter for WS-Security
Any help is greatly appreciated
Thanks
Chandra

Hi Chandra,
As far as I know, this is not directly supported via SOAP Axis Adapter. But one question which I would like to ask is are you trying to configure WS Security using Axis Handlers or you are trying to use the WS Security provided by SAP PI i.e. configuring Security Profile in the Sender Channel?
If you are trying to do it with Axis Handlers may be you can try using the Adapter modules specified in this link which can be used tto call Axis Handlers. <http://help.sap.com/saphelp_nwpi71/helpdata/EN/45/a4f8bbdfdc0d36e10000000a114a6b/content.htm>. Although documentation says that this is supported for SOAP adapter but you can still try as the message returned is still a valid AF message.
Best Regards,
Pratik

Similar Messages

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

What is the transport protocol File (Axis) in the SOAP Adapter

Hi,
for a SOAP Receiver Adapter it's possible to choose 'File (Axis)' as transport protocol.
How does it work and is there some documentation about it?
Thanks and regards
Patrick

Hi,
thanks for your answers.
@Prateek
Yes I tried -> Doesn't say so much
@Vinod
The first thread didn't helped me and I have seen already the second one.
@kummari
The question is how can I use it?
@Gabriel
>The adapter uses transport protocol(File (Axis)) to send SOAP messages as text file
Could you please explain it a little more detailed (maybe with an example)?
My question is about in which scenarios it makes sense to use this transport protocol and how is it used?
Thanks and regards
Patrick

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 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

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?

Issue with SOAP receiver AXIS adapter

Hi All,
We have a scenario SOAP -- > PI -- > SOAP (axis) using SOAP 1.2 version synchnrous scenario. Using Webservice navigator am trying to trigger a message to PI .
Message has reached to PI box and failing in the receiver SOAP(axis) channel as :
Delivering to channel: Receive_SOAP_BulkFeedback 18.08.2014 10:33:24 Information MP: processing local module localejbs/AF_Adapters/axis/AFAdapterBean 18.08.2014 10:33:24 Error
MP: processing local module localejbs/AF_Adapters/axis/AFAdapterBean
MP: processing local module localejbs/AF_Adapters/axis/AFAdapterBean 18.08.2014 10:33:24 Error MP: exception caught with cause javax.ejb.EJBException: ASJ.ejb.005043 (Failed in component: sap.com/com.sap.aii.axis.app, BC-XI-CON-SOP) Exception raised from invocation of public com.sap.aii.af.lib.mp.module.ModuleData com.sap.aii.adapter.axis.modules.AFAdapterBean.process(com.sap.aii.af.lib.mp.module.ModuleContext,com.sap.aii.af.lib.mp.module.ModuleData) throws com.sap.aii.af.lib.mp.module.ModuleException method on bean instance com.sap.aii.adapter.axis.modules.AFAdapterBean@6bbad627 for bean sap.com/com.sap.aii.axis.app*xml|com.sap.aii.adapter.axis.ejb.jar*xml|AFAdapterBean in application sap.com/com.sap.aii.axis.app.; nested exception is: java.lang.NullPointerException: while trying to invoke the method com.sap.aii.af.lib.mp.module.SModule.process(com.sap.aii.af.lib.mp.module.ModuleContext, com.sap.aii.af.lib.mp.module.ModuleData) of an object loaded from field com.sap.aii.adapter.axis.modules.AFAdapterBean.core of an object
Please help and suggest.

Hi Raja,
The end system is closing the communication. Try to reset your PI ICM instance. Also check if your PI system is affected by this note 1675953 - SSL Client Authentication failed with PI SOAP Axis Adapter
Regards.

Issue with Sender AXIS Adapter while XML Signing

Hi all,
We are working on a scenario, an external application pushes message to Sender AXIS Adapter in PI. However while testing XML signing we are getting below error:
<faultcode>soapenv:Server.generalException</faultcode>
<faultstring>WSDoAllReceiver: security processing failed; nested exception is:
org.apache.ws.security.WSSecurityException: The signature or decryption was invalid</faultstring>
<detail>
Could you please provide your valuable inputs on this?
Thanks,
Jaya

Hi Jaya,
Have you checked if your message is valid? Have you tested it against another server?
Which version of wss4j are you using and which PI version?
How does your module/handler configuration looks?
If the message is valid and the handler is configured correctly, you can set the trace level of org.apache to debug and see what it says.
Best regards, Yza

SOAP Axis adapter - problem with XML formatting

Hello All,
We are using SOAP Axis adapter on our scenario (because of NTLM authenticatiom) and faced a problem that some module in a module chain is pretty-formatting XML message (inserting newlines and spaces).
Receiving WebService is REALLY strict on format and doesn't allow spaces and newlines between XML elements.
Formatting is for sure done already in adapter as in sxmb_moni message is still one-liner.
After different tests this formatting is most likely done by XI30OutboundHandler.
Are there any parameters to prevent this formatting?
If there are no parameters, than maybe there is a standard module to remove this XML indentation?
Where I can found source code for XI30OutboundHandler to check how it is extracting payload from XI message?
Thanks in advance for your answers!
Best Regards,
Artsiom Anichenka

Hi, have you find a solution for this problem?
I've tried set the parameter “disablePrettyXML”, as mentioned in SAP note 1039369 (search for “disabling pretty XML”), but apparently it didn’t work too. Have you tried that?
I still get linefeeds and carriage return in the post requisition to the WebService.
Regards,
Ronaldo Schork.

Dynamic filepath in the Axis adapter

Hi,
I have a scenario where I attatch a PDF file in a ABAP proxy as a SOAP attachment, and I need to place this file on a harddrive with the path decided from the data in the message payload. In the "normal" fileadapter I can write to the adapter specific message attributes. Is there a similar possibility with the file transport protocol with the AXIS adapter?
Kind regards
Mikkel

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?

XI to IBM Websphere Default JMS Provider with JNDI

Hello everybody!
We face a problem with connecting SAP XI to IBM WebSphere Default JMS Provider (need to send a message from XI to WebSphere JMS and receive the response).
We have the following versions installed:
    SAP XI: 7.0 SP8 , Sun JDK 1.4.2
    IBM WebSphere: IBM WebSphere Application Server ND, 6.0.2.17, J2RE 1.4.2 IBM
We cannot set the JMS adapter of SAP XI for conecting with IBM WebSphere Default JMS Provider. The Communication Channel has erroneous state (at runtime) and the Communication Channel Monitoring tool displays the error message as described below (under "Variant 1" and "Variant 2" sub-headings) depending on the settings performed.
For connecting, the following JMS-provider settings were used at IBM WebSphere side:
   JMS Providers: Default Messaging Provider
   Queue Connection Factories: name:QueueConnectionFactory, jndi:jms/QueueConnectionFactory, provider: Default Messaging Provider
   Queues: name Queue, jndi: jms/Queue, provider: Default Messaging Provider
The XI communication channel (and associated JMS-adapter) was set as Variants 1 and 2 show. Settings for both cases and received error messages were the following:
<b>Variant 1.</b>
    Adapter type: JMS
    Type: Receiver
    JMS Provider: Access JMS Provider with JNDI (Java Naming and Directory Interface)
    JNDI Lookup Name of QueueConnectionFactory: jms/QueueConnectionFactory
    JNDI Lookup Name of JMS Queue: jms/Queue
    Name of JNDI Initial Context Factory: com.sap.engine.services.jndi.InitialContextFactoryImpl
    JNDI Server Address: iiop://WEBSPHERE.HOST:2809/
    As the result, the Communication Channel Monitoring displays that the channel has erroneous state and the following error message is written:
    "Error during channel initialization; exception trace: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of jms/QueueConnectionFactory.
at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:649)"
<b>Variant 2</b>
    The same settings as in Variant 1 above, were used and additionally the following settings were done:
    - Name of JNDI Initial Context Factory: com.ibm.websphere.naming.WsnInitialContextFactory
    - The archive aii_af_jmsproviderlib.sda containing libraries required by WsInitialContextFactory, was deployed to the SAP WebAS where the XI is running. Those libraries were taken from WebSphere Application Server Pluggable Application Client installation package (described in the article "WebSphere Application Server Pluggable Application Client" located at http://www-128.ibm.com/developerworks/websphere/library/techarticles/0409_bhogal/0409_bhogal.html)
    - Also, as it is recommended in the referred article, the files required by IBM's iiop protocol (ibmext.jar ibmorb.jar ibmorbapi.jar) were put to the folder jre/lib/endorsed of the server(Sun JVM 1.4.2 is used by SAP WebAS / XI).
    As the result, the Communication Channel Monitoring displays that the channel has erroneous state as well and the following error message is written:
   "No adapter registered for this channel"
We have not found the recommended solution either in SDN forums or in Internet in general. Is it yet possible to connect SAP XI to IBM WebSphere Default JMS Provider having mentioned product versioning? If yes, what settings have to be performed?

IBM Websphere Default JMS Provider which is installed alongwith the application server is nothing but a scaled down version of the IBM WebSphere MQSeries. you should be able to connect to it with the same settings that can be used for a separate MQSeries server connectivity from XI.

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.

BinarySecurityToken in sender axis adapter

Hi all,
Need pointers for implementing "BinarySecurityToken" in sender axis adapter?
Any references/blogs would be of great help
Thanks in advance.

Hi Tilak,
From your reply, I am not sure if I understand what you want to do with BinarySecurityToken.
If you mean you want to send your certificate using BinarySecurityToken with the signed message, the answer to the question "Can I include the sender's certificate in the signed message using WS-Security?" in the FAQ Note is exactly what you are looking for.
>Can I include the sender's certificate in the signed message using WS-Security?
>Yes. The default setting uses the issuer-serial method and the signed message only includes the name and the serial number of the certificate. To use the direct-reference method, which includes the certificate in the message, the handler parameter signatureKeyIdentifier of com.sap.aii.adapter.axis.ra.handlers.security.WSDoAllSender must be set to DirectReference. The default value for this parameter is IssuerSerial. See the detailed description of this parameter.
More concretely, the default settting IsssuerSerial generates the x509 certificate serial information within the SecurityTokenReference element. In contrast, the setting DirectReference generates the Reference element within the SecurityTokenRefererence that points to the BinarySecurityToken element that contains your certificate.
Best regards,
Yza

Receiver Axis Adapter to 3rd party webservice

Hi,
My scenario is ABAP Proxy --> PI --> 3rd party webservice using Soap Adapter with Axis protocal.
I'm getting the following error when attempting to post to the 3rd party web service:
nested exception is: java.net.SocketException: Connection timed out:could be due to invalid address
We do have to go through a proxy server to go outside the firewall. I'm not sure if this may be the issue, but I don't even see where you can set this in the AXIS adapter.
Can anyone shed some light on the topic?
Thanks and regards,
Duke

Configured as stated below, and the issue was resolved.
How can I call some service over an HTTP proxy server?
The Axis's standard and adapter's HTTPSender and CommonsHTTPSender handlers recognize the java's standard network properties (http.proxyHost, http.proxyPort, http.nonProxyHosts) for HTTP proxy setting. Please check that these System properties are correctly set at the J2EE server's System properties page. For more information on how to set Java System properties, please refer to the J2EE server's documentation (SAP Note 710146 How to change J2EE Engine JVM Settings).
Thanks and regards,
Duke
Edited by: Duke on Aug 5, 2010 5:37 PM

SOAP Action missing in Axis adapter

Hi,
I am not able to send data to a Web Service using Axis Adapter (SOAP 1.2) and getting an error of "SOAP Action is missing". Can see that SOAP action is missing in the SOAP message sent to Web Service. Communication channel is configured with SOAP Action.
Am on PI 7.10 SP6.
Any help is appreciated!!
Thanks
Kiran

Hello,
I tink you are using receiver SOAP Communication channel... Ask your client to provide the same... because.... your message will be processed at receiver side by using SOAP Action at receiver side...
SOAP action is mandatory for SOAP Receiver communication channels...
Thnx
Subbu

JMS protocol with AXIS Adapter

Similar Messages

Maybe you are looking for