Split Configuration

For a split configuration, the Publisher application functions on a separate server from the Viewer functions. This flexibility can be desirable to maintain the Publisher closer to the authoring resources and the Viewers can be managed in an internet-facing location, whether it be on-premises, or through cloud services.

For this split configuration, there are some notable changes in architecture requirements, compared to monolithic.

• Separate E3C Storage locations are established, one for the Viewer application and one for the Publisher application

• Separate database schemas are required; 4 schemas for the Viewer application and 4 for the Publisher application. (The different schemas are discussed above.) The image above shows the Viewer schemas on a separate database from the Publisher schemas. However, all these schemas may reside in the same database if warranted.

• This image highlights that the Viewer and Publisher applications function in different data centers. This is meant only to demonstrate the possibility. It is not required.

For all production configurations, PTC recommends separating the application server from the database server.

• The Core server entities that are linked to a Viewer entity, use the same Servigistics InService installation. That is, you need to install Servigistics InService once on the machine host, and the same installation is used by the Viewer and all the Core components configured on that machine.

• Each of these configurations represents a separate machine on which these Servigistics InService components are installed.

1. Install a license server. You can skip this step if you want to use an existing license server. For more information, see Installing a Stand Alone License Server.

2. Start the Servigistics InService service setup and select the Monolithic (Publisher and Viewer) product setup option. For more information, see Launching Servigistics InService

4. Add additional Viewer and Core entities in the configurator, link those together, and specify all the required properties. For more information, see Editing Properties of the Configurator Entities.

5. Configure and modify the TAL entity properties, if required. For more information, see Editing Properties of the Configurator Entities.

6. Set up Viewer and Core on the respective machines (as specified in the configurator). The database and LDAP configuration must be specified during Viewer setup, and cannot be skipped.

The location of the configurator xml file is …InS_Data/Data/System/Config. This must be a shared folder accessible to all the servers.

7. Start the services and start using the application. For more information, see Launching Servigistics InService.