Sous-processus Arbortext PE Pools
The primary purpose of Arbortext Publishing Engine is the manipulation of documents using XML and related technologies. The Arbortext PE Request Manager acts as the facilitator handling requests and responses, but it has no knowledge of XML. XML processing is performed by Sous-processus Arbortext PE.
Each Sous-processus Arbortext PE is a running instance of Arbortext’s XML processing engine, with the graphic user interface disabled and additional publishing and performance capabilities enabled. Groups of Sous-processus Arbortext PE are organized into Sous-processus Arbortext PE pools. When a dynamic Arbortext PE Request Manager component determines that it needs the services of an Sous-processus Arbortext PE, it invokes a method of the Arbortext Publishing Engine Request Context to obtain an Sous-processus Arbortext PE from a particular pool, uses it to perform one or more operations, and then releases it so that the Arbortext PE Request Manager can use it to fulfill other requests.
An Sous-processus Arbortext PE pool is a collection of identical Sous-processus Arbortext PE that are associated by the following:
a set of request selectors that specify criteria for determining whether the Sous-processus Arbortext PE in the pool should process a given transaction
a set of parameters that determine how many Sous-processus Arbortext PE are in the pool, how often Sous-processus Arbortext PE should be terminated and restarted, and other behaviors (explained in Sous-processus Arbortext PE Pool Management).
Having multiple Sous-processus Arbortext PE pools offer two major advantages:
Pools of Sous-processus Arbortext PE can be initialized differently.
Sous-processus Arbortext PE pools can be configured to process different types of requests.
When a dynamic component (most frequently, a Request Handler) determines that it needs an Sous-processus Arbortext PE, it calls an Arbortext Publishing Engine Request Context routine and passes a reference to the HTTP request being processed. The Arbortext Publishing Engine Request Context offers the request to each Sous-processus Arbortext PE pool until one replies that it's configured to handle that type of request. The last Sous-processus Arbortext PE pool queried is always the default pool, which can allocate an Sous-processus Arbortext PE to fulfill any request not already handled.
Est-ce que cela a été utile ?