Adapter Module during Soap sender channel

[Former Member]

Hi guys,

at the moment I trying to devleop an adapter module according to following web blog.

[dynamic queue name|https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/5076] [original link is broken] [original link is broken] [original link is broken];

For additional information creating an adapter module on PI 7.1 I use this document

[PI 71. Adapter Module|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/60482ee6-32b2-2b10-fe92-a62bffc0be56]

The basis colleague deployed the created ear file on the adapter engine and I configured the

communiction channel to use the module.

First of all I tried to use the module in combination with the standard soap sender channel, but his fails with this error message => Error during processing local bean: localejbs/ContentBasedQueueName

I searched the help.sap.com and found that adapter modules could not be used during SOAP channel, but there is the possibility to use the Axis framework to enhance the soap channel with the required function.

So created I created an aii_af_axisprovider.sda file with the needed jar files and my colleagues deployed it to the server.

I checked this URL if the sda is deployed correctly http://<host>:<port>/XIAxisAdapter/MessageServlet

Now Iu00B4m trying to configure the soap-axis sender channel and thatu00B4s the point Iu00B4m make a false step.

I defined following parameters in the sender channel

transport protocol: Servlet (Axis)

Payload Extraction: SOAP Body Child

On the Module tab I added my adapter module

(ModuleName = ocalejbs/ContentBasedQueueName & Type= Local Enterprise Bean)

I tried several sequences, added the module before the CallSapAdapter and also tried to add it afterwards

With this configuration I tried to send messages to the sender adapter.

when I use the normal soap url http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel

I got following error in the communication channel monitoring ot this adapter

request received for a channel and the error object type invalid: class com.sap.aii.af.sdk.xi.mo.MessageContext

when I trying to send to the axis url http://host:port/XIAxisAdapter/MessageServlet?senderService=myservice&interface=myinterface&interfac...

nothing happen not even the message request received for a channel

Do anybody have experiences to use a adapter module during soap adapter.

How to solve this issue?

Any help appreciated

Kind regards

Jochen

[stefan_grube]

In Onlin Help you find the order of the modules in Axis adapter:

http://help.sap.com/saphelp_nwpi711/helpdata/en/45/a4a36de28552f7e10000000a1553f7/frameset.htm

So you have to put your module between AFAdapterBean and CallSapAdapter

If you work with PI 7.10 or PI 7.11 you should apply the latest patch to make sure, that the SOAP/Axis adapter has no known issues.

Check the Channel Monitor for issues in the Axis adapter.

Regards

Stefan

[Former Member]

Hi Jochen!

Please try it first without your module. Just call the Axis Adapter as it is.

If you are running PI 7.1 SPS06 you should apply the newest patch 25 for Software Component SAP_XIAF (XI ADAPTER FRAMEWORK 7.10 SP006). This patch solved some Axis issues on my side.

Modules can be added immediately before CallSapAdapter (for inbound case) and immediately after CallSapAdapter (for outbound case).

Regards,

Volker

[Former Member]

Hi Stefan, hi Volker,

thanks for your help.

I´m using PI 7.1 with Enhancement Package 1

could you tell me where to check the patch level for adapter framework?

In SLD I found following infortmation XI Adapter Framewoke 7.11 Installed SP/PL 1/9 newest SP in CR-Content 1

I removed my module from the channel, but the channel fails anyway with the same error message.

Which URL is wright one the

standard => http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel

or the axis => http://host:port/XIAxisAdapter/MessageServlet?senderService=myservice&interface=myinterface&interfac... (are these parameters correct)

as I said above, if I use the standard I see the error in the cc, if I use the axis URL I see nothing

The wright place for my module should be after AF_Adapters/axis/AFAdapterBean ModuleKey afreq and before CallSapAdapter ModuleKey sap, wright???

Kind regards

Jochen

[Former Member]

Hi Jochen!

To check the Patch Level of your components use NetWeaver Administrator (host:port/nwa):

Path is Operations Management -> Systems -> Start&Stop -> System Info -> Components Info

Then type in XIAF in column name of the filter line and press enter. Then you will see SC SAP_XIAF and in column Version you will see the current patch level. On my side this looks like this:

sap.com SAP_XIAF 1000.7.10.6.25.20090518205000 SAP AG

The correct URL is

http://server(fqdn):port/XIAxisAdapter/MessageServlet?senderParty=&senderService=HUGO&receiverParty=...

Mandatory are at least senderService, interface and interfaceNamespace

But do not ommit the other URL parameters, just hand them over empty like you can see in the sample above.

To test the Axis Adapter in general just use URL http://server(fqdn):port/XIAxisAdapter/MessageServlet.

All mandatory components must be marked as OK.

Regards,

Volker

[stefan_grube]

Hi Jochen,

the SOAP adapter does not work for PI 7.11 SP 0.

You need at least SP1. No SPS is provided for SP0, so you have no choice.

You find the patches on service marketplace, where there is a different trail for PI 7.11.

Regards

Stefan

[Former Member]

Hi Volker and Stefan,

I am a colleague of Jochen and I also tried to use an Axis Module. At least I was able to call the Axis Channel without any additional modules. Next step will be to include a module.

Thanks a lot for your support so far.

The point I struggled with was the WSDL generation at the Sender Agreement (Sender Agreement -> Display WSDLu2026). The included endpoints are using the SOAPAdapter instead of the AXISAdapter (http://server:port/XISOAPAdapter/MessageServlet?senderParty...), which means it does not work if you try to use the included endpoints. Or is there something wrong with our configuration?

Regards,

Thomas

[Former Member]

Hello Thomos,

We also have the similar issue with WSDL. Although we have Axis CC, but the sender agreement WSDL shows standard SOAPAdapter.

Did you manage to solve this, if yes, could you share the solution please.

Thanks in advance.

Kind Regards,

Prasad.