Skip to main content
E
Eugine_Prince6-Contributor
6-Contributor
December 11, 2024
Question

Arbortext Publishing Engine Preferences

  • December 11, 2024
  • 3 replies
  • 1405 views

Hello All,

Good day!!

I am experiencing an issue updating the Publishing Engine URL in Arbortext (Tools → Preferences → Publishing Engine). We initially set the URL to an intra-site URL, but now I need to change it to an mc2 site URL. I discovered that the intra-site URL value is specified in the sitepref.xml file on our server.
After updating the PE URL in sitepref.xml file to the mc2 site, the change is reflected, but it is not connecting properly.

Arbortext Version - 8.2.1.0

I have attached the error for your reference.

Thanks in advance

3 replies

V
24-Ruby III
VladimirN24-Ruby III
24-Ruby III
December 11, 2024

Article - "Composing to PDF using Arbortext Publishing Engine returns an error when using PTC Arbortext Editor": https://www.ptc.com/en/support/article/CS117377 

    E
    Eugine_Prince6-ContributorAuthor
    6-Contributor
    December 12, 2024

    Thanks @VladimirN  will check on this and let you know

    M
    manpsingh12-Amethyst
    12-Amethyst
    December 11, 2024

    Hi Prince,

     

    Could you please check the following?

    1- Make sure to use the correct format of PE URL. See this article (PE URL) for more information

    2- Make sure Publishing Engine (PE) is up and running. To verify that, are you able to generate TEST PDF from PE launch index page? If not, then make sure PE is configured correctly or you have upgraded it.

     

    Regards,

    Manpreet Singh

      V
      vnamboodheriCommunity Manager
      Community Manager
      December 17, 2024

      Hello @Eugine_Prince, 

       

      It looks like you have some responses from some community members. If any of these replies helped you solve your question please mark the appropriate reply as the Accepted Solution. 

      Of course, if you have more to share on your issue, please let the Community know so other community members can continue to help you.

      Thanks,
      Vivek N.
      Community Moderation Team.

      B
      18-Opal
      bfriesen18-Opal
      18-Opal
      December 18, 2024

      I find also that you need to make sure you have the e3/servlet/e3 in the path. We have had users copy the address and not include the /servlet/e3 to the path.

      http://123.456.789.101:8080/e3/servlet/e3 

      Bryon

      Terms & ConditionsCookie settingsAccessibility statement