Creo view adapters set up with PROE, OFFICE, APE workers

[AQ_10299550]

Version: Windchill 13.0

Use Case: Proper configuration of Worker Agent Administrator or an easier way to manage and contain different servers

Description:

While configuring these workers, the current set up is: 
- Creo View Adapters + Creo Parametrics + APE configured on server 1

- Creo View Adapters + AEM is configured on server 2 (This has been having issues lately connecting to Worker Agent Administrator)

I have read documentations regarding AEM and the first thing that was mentioned was that AEM and Creo View Adapters needs to be on two different servers. 

With this in mind, what is the best structure to set up Worker Agent Administrator:
- Set up Creo View Adapters and configure AEM worker on server 1 (with Creo Parametrics and APE), And then install AEM software alone on server 2

- Set up a third server (server 3) for the sole purpose of Creo View Adapters that configures the workers for PROE, APE, and AEM. Server 1 holds Creo Parametrics and Server 2 holds AEM

- Open to hearing out different suggestions, Thanks!
 

[jbailey]

On the Office publisher, AEM is no longer required - as you can do direct to PDF with just Creo View. The markup capabilities etc are a slightly different license structure.

[AQ_10299550]

Is there any documentation regarding this alternative of not using AEM? I would like to learn more about the markup capabilities and what licenses is required.

Most, if not all articles posted on PTC support suggests using AEM since MS Office does not have the capabilities of creating coversheets and watermarks. In addition, the current MS365 that is being supported by MS is not supported by Adobes compatibility matrix, Adobe requires MS 2019. 

[anursingh]

Hi @AQ_10299550,

I wanted to see if you got the help you needed.

If so, please mark the appropriate reply as the Accepted Solution. It will help other members who may have the same question.
Of course, if you have more to share on your issue, please pursue the conversation. 

Thanks,
Anurag