Multi-Site Configuration
Servigistics InService can publish to more than one publishing site. Publishing sites are often situated in separate data centers. This ability to operate across multiple data centers allows Servigistics InService to provide an enterprise level of scalability and availability.
The following diagram describes the architecture for a multi-site configuration.
Note that:
• The Publisher is maintained in one data center (presumably close to the content authoring systems). While this image places the Publisher in the same data center as a Viewer, this is not required. The Publisher may reside in a third data center.
• Similar to the split configuration, the Publisher maintains its own database schemas and E3C Storage.
• At least one Viewer application is established at each site.
• Each site maintains database schemas and E3C Storage for the Viewer applications that function in that site. The exception to this is the use of the Windchill schemas. For all Viewers in all sites, they must be able to access the same Windchill schema.
• For publishing tasks, the Publisher must be able to communicate with the Viewers in each site.
In addition to that, the diagram provides:
• Cluster configurations within each site.
• The use of web servers or proxy servers in the DMZ to provide a safe environment for this internet-facing application. For greater security, customers commonly use a reverse proxy or standalone web server in a DMZ. Using this approach gives users access to a secured server before accessing the application servers
• Authentication is managed in this web tier.
• Corporate load balancers are used to manage the load distribution to the sites.