[shinsoft]

I have web application (on Windows IIS server) that creates EDI 210 XML based on user inputs and transmits it to our OTM Application server (HP Server) using HTTPPOST on port 80. My question is could this be sent over SSL on port 443 to secure this information from my web application to OTM Application server? What setup or configuration do we need to do on OTM Application server?

Thanks.

[nick.polites]

I believe that after 5.5 CU-3 you were able to post directly to the WMServlet using https. There shouldn't be any additional setup to get this working.

[shinsoft]

Thanks Nick for your reply. It appears we have 5.5 CU-2. Is SSL possible under this version? What configuration do we need to make?

Currently I use URL like below to post.

http://<OTM Server>:80/GC3/glog.integration.servlet.WMServlet

Do I need to remove the port # in the url to post for SSL? What should the URL above look like for SSL? Our users will be using secured website https://www.<website>.com to post these XML from.

Thanks.

[nick.polites]

Yes that is correct the posting will look like:

https://<OTM Server>/GC3/glog.integration.servlet.WMServlet

Nick

[shinsoft]

Nick,

It appears we have 5.5 CU-2. Is SSL possible under this version? What configuration do we need to make?

Thanks.

[nick.polites]

You'll need to upgrade to CU-3. From what I can remember I don't think there was a quickpatch for this.

[shinsoft]

Nick,
Do you know of any documentation for OTM 5.5 that talks more about transmission under SSL? It would be nice to see any documentation that states why SSL may not work under OTM 5.5 CU 2 or it will work in OTM 5.5 CU3.

I tried typing https://<server>/GC3/glog.integration.servlet.WMServlet directly in the browser and I get the same screen I see when using the http://<server>/GC3/glog.integration.servlet.WMServlet so I'm assuming https:// maybe working or at least OTM maybe looking for data on https://. So I decided to try to post to https:// in our dev environment and I got the following message from my .NET application.

Error #1: Authentication failed because the remote party has closed the transport stream.
Causing Error #2:
The underlying connection was closed: An unexpected error occurred on a send.

This is using the same code that works when sending to http:// url.

Let me know if you have any other advice or suggestions.

Thank you.

[nick.polites]

The code wasn't written until CU-3.

[shinsoft]

Nick, Thanks for the information.