on 11-20-2015 3:13 PM
Hi Experts
I face with a problem with simple soap scenario. I want to use soap-service on IIS Microsoft Windows Server 2012r2. The soap service uses NTLM-authentification. When I use SOAP UI from local computer service works fine.
Because of NTLM-authentification I try to use Apacher Axis CommonsHttp components
I install Apache components on PI server
1) Can somebody tell me if all components used is correct or may be obsolete.
2) Is there any other way to make scenario work not using Axis
Hello Vladimir,
What kind of NTLM Version does your receiver application is expecting? I had the same issue as well in the past when I'm trying to connect to my Sharepoint service. They were using NTLM V2 I guess, whereas we can't able to achieve this version using Axis adapter..
Thank you,
Justin.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Vladimir,
Please try updating Apache HttpComponents HttpClient (ex-Jakarta Commons HttpClient) library. If SharePoint uses NTLMv2, then official web site of Apache HttpComponents project states support of NTLMv2 has been provided starting from HttpComponents HttpClient 4.1 (refer to Apache HttpComponents - HttpComponents News). On one of past projects, we used following bundle for Axis libraries - it worked well for integration with SharePoint and NTLM authentication.
This was output of Axis Adapter Message Servlet:
And here is a list of libraries which were bundled into com.sap.aii.af.axisproviderlib.sda:
As far as I can see, the newest version of this library is already 4.5.1, so you may try this version instead of using older ones.
Regards,
Vadim
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, Vadim
I deployed a new pack of libraries today
and received an unexpetable result:
all SOAP channels failed.
and the /XIAxisAdapter/MessageServlet become unavailable too.
One or any of the libraries makes SOAP adapter fail.
I redeployed the older version of pack. And now PI works as worked on last week.
Regards,
Vladimir
Hi Vladimir,
That's strange. I made a screenshot of Axis libraries which we deployed, from a live system where we used Axis channel for communication with SharePoint using NTLM authentication, this set of libraries worked well for me that time.
I compared libraries which you bundled with those I deployed, and see several of them had difference in versions. Probably, it would make sense to see if those versions you deployed have any extra dependencies on other libraries.
In addition to this, it will be helpful, if you could provide information from Axis libraries deployment log (was there any warning/error/exception there?) and SOAP adapter application start up log (what kind of errors it issued?). This may give a better outlook at what library was missing or if there was any other reason to the observed problem.
Regards,
Vadim
Hi Vadim,
There are some errors on startup:
Duplicate service registration for service XiObjSerializationService and type RoutingRule: old= com.sap.aii.ibdir.core.serialization.routing.InternalSerialServiceRoutingRule new= com.sap.aii.ibdir.server.persist.routing.InternalSerialServiceRoutingRule
Global [startApp] operation of application [sap.com/com.sap.aii.adapter.axis] failed with errors on server process [3366950].
I think some versions of libraries are incompatible
Vladimir, can you also provide an error log entry details for startup of the application com.sap.aii.adapter.axis? I see there was an error recorded for it and contained in a screenshot of Log Viewer you posted (in the bottom of it), but the log entry which is selected, is a different one.
Regards,
Vadim
Vadim,
the error record was:
Global [startApp] operation of application [sap.com/com.sap.aii.adapter.axis] failed with errors on server process [3366950]. -
I have viewed all the log and no more meanfull information was found. I think the best way to solve the problem is to find compatible libraries. I read a lot SOAP UI forum where are much information about incompatible versions of the same libraries and classes.
I make a local Java project with NTLM authentification with CommonsClient libraries-3.1(does't work) and another Java project with HttClients libraries-4.5.1(works).
Thanks a lot.
I'll write about results in a few days.
Regards,
Vladimir
Hi Vladimir,
Few posts above, a screenshot of directory with JAR files which I provided - that was actual complete list of libraries which I used to bundle into com.sap.aii.af.axisproviderlib.sda. I assembled com.sap.aii.af.axisproviderlib.sda using SDA Maker Tool, PI system release - 7.31, an option "don't use SAP XI 3RD PARTY SCA" unchecked.
Regards,
Vadim
Hi, Vadim
I tried to find all libraries from your screenshot in google. Google found many jar files from different sources. The problem is that all founded jars all are differerent in size and content. The JARS with the same name have many differences inside. I can view the differences only when I unpack them and view MANIFEST.MF file. In the file I can find correct version of source. For example, when I found several files with name xalan.jar all of them were versions of xalan-2.*.*.
That's why I asked you to share original libraries pack.
Regards,
Vadim
Hi Vladimir,
Sure, no problem. The only issue for me is: SCN allows attaching files of maximum size 1 MB, and some libraries which I used, are larger. If you give me your e-mail address to which I can send ZIPped libraries (~7,4 MB in total) or any location to which I can upload them, I will do so.
Regards,
Vadim
Hi Praveen Gujjeti,
Vadim's SCA package does't work in my PI server. My goul is to find a NTLMv2 solution that will work in any cases. So I next my step is to create a Soap NTLMv2 adapter. I have create Soap NTLMv2 module but there are some difficulties with it: The module have to be inserted before main adapter module or after main adapter module - It cannot be standalone.
Regards,
Vladimir
Hi Vladimir,
Thanks for the update...
May be you can try with SAP Note: 2062567 ( I will also try this, and post results when I am done)
http://service.sap.com/sap/support/notes/2062567
Thanks,
Praveen Gujjeti
Can you send me your SDA file to gpk1000@gmail.com I tried all the versions still not working, mine is NTLM not NTLMv2 and my PI version is PI 7.31 SP14, I am still getting 401 unauthorized error.
I deployed these jar files in PI. There were no errors in startup logs and AXIS message servlet page also shows OK status.
Regards,
Shanthi.
User | Count |
---|---|
98 | |
11 | |
11 | |
10 | |
10 | |
8 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.