Publishing Engine Programmer's Guide > The Arbortext Publishing Engine Request Manager > Predefined Dynamic Components > Predefined Request Functions > The f=init Request
  
The f=init Request
This request function is implemented by Java class com.arbortext.e3.FunctionInit. It directs every Arbortext PE sub-process in every Arbortext PE sub-process pool to re-initialize and reload all ACL, JavasScript, and VBScript packages. The request sets a flag on each Arbortext PE sub-process, but the initialization takes place the next time the Arbortext PE sub-process is allocated to a Arbortext Publishing Engine dynamic component. That means that any allocated Arbortext PE sub-processes won't re-initialize until they are deallocated and subsequently allocated to another request.
You can submit an f=init request from the Reload Applications link on the Arbortext Publishing Engine index page. Refer to Monitoring and Reporting Using a Web Browser for information.
You can load new or updated ACL, JavaScript, or VBScript scripts by using Reload Applications or f=init to instruct the Arbortext PE sub-processes to reload these types of programs, without restarting the Arbortext PE Request Manager.
You can also update Arbortext PE sub-process stylesheets using Reload Applications or f=init to clear all previously cached stylesheets without restarting the Arbortext PE Request Manager. By clearing the stylesheet cache, Arbortext PE sub-processes will use the updated stylesheet for the next request that uses it.
* 
The init function does not reload Java code. If you need to update Java code in either the Arbortext PE Request Manager or in the Arbortext PE sub-processes, you must stop and restart the Arbortext Publishing Engine.
The init function does not re-initialize some other resources that Arbortext PE sub-processes might be using, such as repository connections, open documents, and cached document types.