Publishing Engine Programmer's Guide > The Arbortext Publishing Engine Request Manager > Customizing the Arbortext PE Request Manager > Writing a Custom Queue Manager
  
Writing a Custom Queue Manager
To write a queue manager, you must develop a Java class that implements the interface com.arbortext.e3.E3QueueManager and update e3config.xml to define it. The most efficient approach also includes implementing either a request handler or several request functions, as described in Writing a Custom Request Handler and Writing a Custom Request Function.
A queue manager must provide the same init, destroy, getId, and getStatus methods as described for a cache manager. In addition, your class must provide a service method which takes an HTTP request as a parameter. Use the service method to examine the HTTP request and determine whether you want to save it to fulfill at a later time. If so, you should construct an HTTP response and return it as the return value for the service method. If the request should not be saved for later processing, the service method should return null.
To queue a request, you should consider the following:
Developing a mechanism for storing requests that guards against Arbortext PE Request Manager restarts, such as saving them to disk.
Implementing additional requests that allow users to inquire whether a queued request has been completed.
Obtaining the results
Administering requests and responses in the queue.