Using the Global Resource Settings feature

When you migrate applications from one server or environment to another, references to the external systems that those applications connect to, such as endpoint URLs and JNDI servers, may change. The Global Resource Settings feature allows you to set values for these references without hard coding them into your application.

The basic steps to utilize this feature are:

1. Create a class to hold the references to external systems (also known as environment properties).
2. Create a property rule for each reference to an external system. These are the environment properties. Process Commander includes standard embedded classes and default properties for each rule form that supports the Global Resource Settings syntax. For information on how to use these embedded classes to create property rules, see Pega Developer Network article PRKB-24171 How to reduce maintenance of service rules and listeners with Global Resource Settings.
3. Set the values of the environment properties. As a best practice, use a model rule to set these values.
4. Create a declare page rule that references the class from Step 1 and the model from Step 3.
5. Update the LoadResourceSettings activity to load the model rule that you created in Step 3.
6. Use the Resource Settings syntax (=.PageName.PropertyName) when entering references to external systems.

For more information on the Global Resource Settings feature, see Pega Developer Network article PRKB-24171 How to reduce maintenance of service rules and listeners with Global Resource Settings.

For a list of fields, see Fields that support the Global Resource Settings syntax.

	About Declare Page rules About Model rules
	Atlas — Standard classes derived from the Embed- base class

Integration services category