Arbortext PE Unterprozess 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 Arbortext PE Unterprozesse.
Each Arbortext PE Unterprozess 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 Arbortext PE Unterprozesse are organized into Arbortext PE Unterprozess pools. When a dynamic Arbortext PE Request Manager component determines that it needs the services of an Arbortext PE Unterprozess, it invokes a method of the Arbortext Publishing Engine Request Context to obtain an Arbortext PE Unterprozess 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 Arbortext PE Unterprozess pool is a collection of identical Arbortext PE Unterprozesse that are associated by the following:
a set of request selectors that specify criteria for determining whether the Arbortext PE Unterprozesse in the pool should process a given transaction
a set of parameters that determine how many Arbortext PE Unterprozesse are in the pool, how often Arbortext PE Unterprozesse should be terminated and restarted, and other behaviors (explained in Arbortext PE Unterprozess Pool Management).
Having multiple Arbortext PE Unterprozess pools offer two major advantages:
Pools of Arbortext PE Unterprozesse can be initialized differently.
Arbortext PE Unterprozesse pools can be configured to process different types of requests.
When a dynamic component (most frequently, a Request Handler) determines that it needs an Arbortext PE Unterprozess, 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 Arbortext PE Unterprozess pool until one replies that it's configured to handle that type of request. The last Arbortext PE Unterprozess pool queried is always the default pool, which can allocate an Arbortext PE Unterprozess to fulfill any request not already handled.
War dies hilfreich?