PTC Arbortext Content Delivery Application
There are three PTC Arbortext Content Delivery applications deployed in WildFly 17. The details of the applications are as follows.
• Configurator—administration application for ACD configuration.
◦ Deployed through:%INS_INSTALL%/InS_SW/SW/Applications/ ConfiguratorApp-1.0-SNAPSHOT.ear
◦ Associated war file: ConfiguratorWebApp-1.0.war
◦ URL: http(s)://<server>:<port>/Configurator
• Task Manager—application for data publishing.
◦ Deployed through: %INS_INSTALL%/InS_SW/SW/Applications/e3C.ear
◦ Associated war file: TaskManager.war
◦ URL: http(s)://<server>:<port>/TaskManager
• Viewer—application for end user.
◦ Deployed through: %INS_INSTALL%/InS_SW/SW/Applications/Windchill.ear
◦ Associated war file: codebase.war
◦ URL: http(s)://<server>:<port>/ACD
PTC Arbortext Content Delivery SSO Configuration Files
While adapting SSO for ACD, major configurations are configured using multiple configuration files present in any WAR file. The following files are impacted while configuring SSO for ACD.
• WEB-INF/web-orig.xml
• WEB-INF/Security/config
◦ securityContext.xml—Spring security specific configuration file; multiple filters are defined here.
◦ resourceServer.xml—Represents different resource server and their respective scopes for the application.
◦ openam-idp.xml—Represents IdP metadata file.
• samlKeystore.jks—PTC Arbortext Content Delivery Java Keystore in which PingFederate certificate is imported.
• WEB-INF/classes/ securityContext.properties— the default security properties that contain various security properties used for environment initialization