HIGH PRIORITY: XI 3.0 connectivity issues (JAVA SSL)

[Former Member]

Hello! Thank you for helping!

We were having an issue with our XI 3.0 integration with an outside SAP trading partner who is using XI ***.*** also. We are sending a small <3K XML file. Simple stuff. (or so it would seem)

The initial error was the following:

HTTP 401 Unauthorized: java.io.IOException: invalid content type for SOAP: TEXT/HTML;

We solved for this error by commenting out the authorization requests in web.xml :

/usr/sap/XXX/XXXXXXX/j2ee/cluster/server0/apps/sap.com/com.sap.aii.af.soapadapter/servlet_jsp/XISOAPAdapter/root/WEB-INF/web.xml

Now we receive the following error:

Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: invalid content type for SOAP: TEXT/HTML; HTTP 503 Service Unavailable: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 503 Service Unavailable

On DEV, you can view the JAVA AS landing page using https. On QA you cannot. (meaning that we CAN access the DEV machine through a browser by going to https://DEVmachine.subdomain.companyname.com:50001, but we CANNOT access the QA machine by going to https://QAmachine.subdomain.companyname.com:50001. We CAN however access QA by going to http://QAmachine.subdomain.companyname.com:50000)

Common sense would indicate that one would only need to ascertain the differences between the two machines KEY STORAGE and SSL_SECURE services within the Dispatcher and the Server on DEV and QA. Alas, I did that yesterday and could not find a discernable difference.

So, I can only surmise the following:

1. Our QA system is somehow not properly configured for SSL

2. I have confirmed that the 50001 port exists

3. The certificate for the DEV machine is expired yet it works fine, and the QA machine has a new certificate but does not work.

4. Current RSA keylength is set to 1024

Also, if someone could please comment upon the invalid content type for SOAP, I'd appreciate it.

I've already had messagetransformbean implemented on both sides.

Respectfully,

Nicholas

[Former Member · Accepted solution]

If you cannot reach the HTTP service from your browser in same network of your

Xi System, probably the reason is different from the ssl certificate problem.

Try to call from your browser, the HTTP service endpoint and confirm if the

WS still reachable in http transfer protocol.

[Former Member · Accepted solution]

Hello- thanks for your attempt to help.

As I indicated in the original post, we CAN access the site through HTTP on port 50000 just fine.

We cannot access through HTTPS on port 50001.

Respectfully,

Nicholas