Server | Description |
WildFly Application Server | WildFly is a J2EE application server, from the JBoss open-source application server offerings. It provides a standard runtime environment for running the applications. Servigistics InService uses WildFly to provide access to the application. The application server delivers static content (such as images, java script, style sheets, etc), provides access to the content published from the enterprise (Parts, Technical Information, etc), and it delivers dynamically created end user and administrative data via the business logic and E3C core servers. |
Publisher Application | The E3C Publisher is a collection of tools that facilitate the permanent, one-way migration of data from Windchill Service Information Manager (SIM) and other Enterprise Information systems into a Servigistics InService system for delivery to its consumer base. The tools work within an overall Publish, Extract, Transform, Aggregate, and Load migration approach where data is pushed from one or more source systems, mapped and transformed to for use within the Servigistics InService application and then loaded into the Servigistics InService delivery mechanisms. The Publisher receives the bundles generated by the authoring applications, and periodically performs the publishing process to transform, aggregate, and load the authored content to associated delivery sites. |
Viewer Application | To operate in conjunction with the E3C services to provide the container and implementation framework for the Servigistics InService RESTful endpoints, services for end users (shopping carts, preferences, notes, etc.), services for administrators (user, dealer and offline systems management) and services for allowing offline systems to receive updates to published content and data synchronization. |
Server | Description |
E3C Core server | E3C core servers provide services for search, navigation, filtration of the XML and parsable PDF published content via a CORBA interface to the code in the WildFly servers. This content is primarily stored in the XML Repositories, although some information is stored in one of the Servigistics InService Relational Database schemas. |
E3C Load Balancer | Larger Servigistics InService deployments will require multiple Core servers to meet security, high availability, performance, and scale requirements. When two or more E3C Core server processes are configured per application tier node, E3C load balancers are deployed to distribute application requests to the available core servers. The E3C load balancer is a process that tells the business layer which core server is available for connection. There is one core server E3C load balancer for each viewer. Each E3C load balancer can route to any available core server in its data center. You should configure only one primary E3C load balancer, usually on site 1. The primary load balancer is the active component to the passive core server load balancers. The E3C load balancer enables a viewer to have access to all configured core servers. Note that this communication is between a viewer and a core server only. It is an internal communication and never interacts with the application load balancer. |
E3C Core CMI server | The E3C core CMI servers is a special configuration of the E3C Core server that provides the functionality to perform updates to the published content, for example, provide new and revised XML and PDF content. The interface here is also CORBA-based performing data updates and indexing based upon requests from the Publisher server. Only one instance of the E3C Core CMI server runs on the application tiers serving/supporting the published content. The E3C Core CMI server updates both the XML repositories and the RDB. |
E3C Storage | Servigistics InService maintains a XML-based ‘E3C Storage’ location of content as part of its overall solution. This file storage contains data-related files (embedded database, data images, search indexing, and other core repository content). This storage is maintained by the E3C Core processes. The E3C Core CMI process loads new and iterated content into the E3C Storage. The E3C Core Server processes perform read requests for the Viewer engines. The E3C storage location that receives the content from the Publisher is referred to as a “publishing site”. In some High Availability configurations, it’s appropriate to configure more than one publishing site. Such high availability configurations are provided in Configuration Options. One E3C Storage location is established for each site (or data center) that makes up the overall Servigistics InService solution. |