These custom functions are capable of loading any resource out of the Process Server catalog and updating a resource in the catalog. The loaded resource is returned to the expression language as an XML document. For example, you can extract configuration information from process definition, such as alarms or endpoint references, and keep it in the catalog where it can be changed and shared across process definitions. The use of the catalog also enables a process to have different configuration information based on its deployment environment. For example, a development environment can have one type of configuration information while a production environment can have another. The configuration information is in XML format. Be sure to import the resource XML files into the project to make them available for simulation and for automatic export to a BPR archive. For details, see
Importing WSDL, Schema, and Other Resources and CCreating and Deploying a Business Process Archive Contribution.