cannot see Axis Protocol in SOAP Adapter.

[Former Member]

Hi ,

I am using PI 7.1 Single Stack - Java Only .

I am using SOAP Adapter . Now when I try to find axis protocol in SOAP Adapter.

I am not able to find the same in SOAP Adapter.??

Kindly share the steps , What drivers/ Zip files required and how to deploy them ??

Regards

PS.

[Former Member · Accepted solution]

Hi All,

Closing this Question :

Successfully Deployed the AXIS ADAPTER SDA File in JSPM.

Most wonderfull -  SAP Note.    Note 1039369 - FAQ XI Axis Adapter

There is already a SDA file present in there . com.sap.aii.af.axisproviderlib.sda

I directly used this file for deployement. Just added required JAR Files inside the SDA and make it deployed.

[Former Member]

Hi,

I have been reading this SAP Note.

Note 1039369 - FAQ XI Axis Adapter

It has a attachment faq_axis_adapter.ZIP

Inside this Zip file -

faq_axis_adapter\res\axisprovider\710_minimum_kit\710\minimum_kit\

There is already a SDA file present in there . com.sap.aii.af.axisproviderlib.sda

Can we directly use this .sda file for deployement using JSPM.

Regards

PS

[Former Member]

Hi. Prabath

Please check the SAP Note

Note 1028961 to deploy this Adapter.

Also you can check this thread-

http://scn.sap.com/message/13308588#13308588

Regards.

[Former Member]

Hey Luis ,

I saw that SAP Note . This is a great Help .  But Still I have many Doubts :

There is a point (2) in Reason & Pre-requesties.

" 2. For Netweaver PI 7.11 and upper find necessary SAP XI 3RD PARTY SCA from the

installation media or Service Market Place and copy it in specific directory on

your local machine."

So Que is : What are these SAP XI 3rd Party SCA files ? Is it required for PI 7.3 Single Stack  - SOAP adapter ????

Regards

PS.

[Former Member]

Below are the three files which you should deploy.

1. Apache-Axis - axis.jar;
2. Jakarta-Commons Discovery - commons-discovery.jar; see http://jakarta.apache.org/commons/discovery/
3. Jakarta-Commons Logging –commons-logging.jar

Regards

Sreeram

[Former Member]

Hi

Regarding the post

2. If SAP XI 3RD PARTY SCA cannot be found in Service Marketplace you can uncheck checkbox 'Don't use SAP XI 3RD PARTY SCA'. This will allow you to create sda without using 3RD Party SCA.

Please find on your PI directory installation , if not is present the SCA you need to create a sda with jar files.

Regards

Lucho

[Former Member]

I believe this Would be the set of Steps :

1. SDA has to be create by some SDATool or in my Case I have taken it from  faq_axis_adapter ZIP Folder \res\axisprovider\710_minimum_kit\710\minimum_kit\ com.sap.aii.af.axisproviderlib.sda.

2. SDA name would be com.sap.aii.af.axisproviderlib.sda
3. Bind following JAR Files :-

axis.jar
commons-discovery-0.2.jar
commons-logging-1.0.4.jar
commons-net-1.0.0-dev.jar
wsdl4j-1.5.1.jar


4. modify the provider.xml file appropriately by adding these file
names in its jars section.

5. Deploy the SDA file using JSPM .

[former_member184789]

Hi,

As per the FAQ for Axis adapter,

#1 How can I start using the Axis adapter?

The axis adapter is available from XI 3.0 SP20, XI 7.00 SP12, and XI 7.10 SP3 releases. However, the standard SAP XI deployment archives do not contain the necessary Apache jar files. These jar files must be packaged in archive aii_af_axisprovider.sda and deployed on the system to enable the Axis adapter. There is a deployment check servlet to see if these jar files are deployed.

#2 How can I check if the Axis adapter is successfully deployed on my system?

You can use your browser to look up http://host:port/XIAxisAdapter/MessageServlet, where host and port are the host name and port number of the adapter engine.

The page will display the versions of the deployed components and whether the required libraries are also deployed. For a simple SOAP scenario, it is necessary to have only the required components deployed. For more specific scenarios, e.g., WS-Security, WS-ReliableMessaging, it is also necessary to have the relevant optional components deployed. The page should show status OK when all the required components are available and otherwise status Error.