Has anyone successfully configured APE to connect to an HTTPS url (in this case configured in Tomcat)? I think I have done all the requisite steps
- added cert to Trusted Root Authorities page
- verified that the service is available over 8080 when https is not configured
I get the error 'No publishing configuration information is available from the Arbortext Publishing Engine server: Possible causes: invalid URL, PE server down or PE server misconfigured'
Has anyone got this successfuly working?
For 126.96.36.199, https is on by default for PE and we have configured it internally at PTC. If you are still having trouble with the set up, please contact PTC technical support.
Not sure if the issue is still relevant for @Tusken_Raider , but writing here in case someone else would run into this thread.
I've recently had to configure the latest and greatest Arbortext Publishing Engine 8.1 for my dev machine and encountered similar issue (could access the web page for Publishing Engine, but couldn't connect to APE from Arbortext Editor client, was getting the "No publishing configuration information is available from the Arbortext Publishing Engine....." when enabling Publishing Engine in Editor)
But there are two points in my story...
1) I was experiencing the same issue with both https and http.
In the end, after resolving the issue with http, I had no problems configuring https.
There are basically just two steps to enable https and I don't see the second one in your list of steps.
a) Point Tomcat to the keystore with the key(s) for your certificate(s).
b) Import the public key / certificate into the Trusted store of the Java used by clients. If you didn't do this, you won't be able to connect to APE and will get exactly this error ('No publishing configuration information....').
This error seem to be pretty generic and appears for any kind of misconfiguration and doesn't help, but "C'est la vie" they say 🙂
2) Regarding configuring https / tls
As I already mentioned, this particular issue for me had nothing to do with HTTPS.
You've written that you "verified that the service is available over 8080 when https is not configured". How have you verified this?
I could access the web page for Publishing Engine (http://somehost:18080/e3) and could pass basic checklist like get the status page (http://somehost:18080/e3/servlet/e3?f=status) and generate a sample document (from the web page).
But I was seeing different APE errors (see below) in different places / logs and was getting error when accessing the config page (http://somehost:18080/e3/servlet/e3?f=status&page=compconfig).
Error '' scanning local configuration.
e3config.exe failed to return any data.
Agent (<>\WinSta0) sensed not first instance and died.
Long story short, I resolved the issue, but unfortunately, can't now say for sure what was the cause.
Normally I’m not happy when I don’t know for sure which particular change in configuration resolved an issue, but since it’s a dev machine and there are too many moving parts there and I couldn’t reproduce the issue on another machine, I don’t think I will investigate further.
Mine is also similar situation but, I am configuring with HTTP. The error is coming only when I set the APTCUSTOM environment variable to set the custom folder. If I remove the APTCUSTOM custom it will connect with client and URL also work fine to publish PDF with standard style sheet. Could anyone help me to resolve this.
Yes I am using APTCUSTOM in PE. I have created a customs folder which have all my defined style sheet inside. I have attached a images for your reference.
Thanks for the screen shot. When I have tried using the aptcustom I had it going to a network location. All of my client machines can retrieve the application, but the server would not. So my solution was to replace the default application in the install folder. Seems to work but it would be nicer if it was a reboot PE and it would automatically download the latest application.