hi David,
The OData Channel in ABAP works either in http or https protocols and what you are facing is a firewall blocking ports or closing the connection once established.. you sort of need to ask network people to open up that server for you.
About the certs, well.. you need the whole chain, each company does it on their own way.. usually you have a chain on three certificates which is CA, CA internal and server issued cert.
In order to "extract" the certs you can access the OData Service manually using Google Chrome or Internet Explorer, click the "lock" or the "https" icon (which will be green for valid certs, yellow for self signed certs) and export it somewhere you can read, like your hard drive.
Afterwards you need to import them into the jdk/jre cacerts using java keytool - and last step is to make sure when you boot Tomcat you actually tell tomcat to use that cacert, there is a -Doption to assign the path of the cacerts Tomcat should use.
Alternatively:
- don't use Tomcat, start your browser dropping the cors protection;
-- Chrome: start Chrome instance with --disable-web-security
-- IE: Security, Choose the Zone, Custom, Misc. "Access data sources across domain: Enable"
-- FF: not too sure from top of my head; google it..
- you would access the OData URL without the need of the "tunnel/proxy" servlet;
Case you have an issue from file:// to https:// you can:
- download python;
- command prompt into the directory where you index is located;
> python -m http.server [port] || OR
> python -m SimpleHTTPServer [port]
- access the application using localhost:port/index.html
Hope it helps,
Dan.