Hi @Satya K,

When migrating applications from one server or environment to another, you may encounter changes in the references to external systems that those applications need to connect to. These references can include important elements like endpoint URLs and JNDI (Java Naming and Directory Interface) servers. To simplify the management of these connections and avoid hard coding values directly into your application, you can utilize the Global Resource Settings feature.

Here’s a detailed breakdown of the steps to effectively implement this feature:

1. **Create a Class for Environment Properties:** Begin by developing a dedicated class that will store all the references needed for external systems. This class will serve as a centralized location for what are known as environment properties, ensuring that your application can easily access these values.

2. **Define Individual Properties:** For each external system that your application connects to, you need to create a specific property within the class. These properties represent the various environment properties required for your application to function correctly. PRPC (Pega Rules Process Commander) already provides standard embedded classes along with default properties for each rule form that support the Global Resource Settings syntax. For guidance on how to effectively use these embedded classes to create your properties, refer to the PDN article 24171, titled "How to Reduce Maintenance of Service Rules and Listeners with Global Resource Settings."

3. **Assign Values to Environment Properties:** To ensure flexibility and ease of maintenance, it is recommended to utilize a data transform for setting the values of these environment properties. A data transform allows you to define how data should be handled and modified, making it easier to manage configuration changes.

4. **Create a Declare Page Rule:** Next, you will need to establish a declare page rule that references the class you created in Step 1 and links it to the data transform you set up in Step 3. This step effectively associates the external references with their corresponding values.

5. **Update the LoadResourceSettings Activity:** Modify the LoadResourceSettings activity in your workflow to load the data transform you created. This ensures that, upon execution, your application pulls in the latest environment property settings.

6. **Utilize Resource Settings Syntax in Code:** Whenever you need to reference external systems within your application, make sure to use the Resource Settings syntax, formatted as (=.PageName.PropertyName). This syntax allows for dynamic retrieval of the property values you've defined, ensuring your application remains flexible and adaptable to changes in the environment.

By following these detailed steps, you can efficiently manage and configure references to external systems during your application migration process, greatly enhancing the maintainability and adaptability of your applications.

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 for each reference to an external system. These are the environment properties. PRPC 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 properties, see PDN article 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 data transform to set these values.
4. Create a declare page rule that references the class from Step 1 and the data transform from Step 3.
5. Update the LoadResourceSettings activity to load the data transform that you created in Step 3.
6. Use the Resource Settings syntax (=.PageName.PropertyName) when entering references to external systems.

Thanks

Regards

Raja

Hi @Satya K,

When migrating applications from one server or environment to another, you may encounter changes in the references to external systems that those applications need to connect to. These references can include important elements like endpoint URLs and JNDI (Java Naming and Directory Interface) servers. To simplify the management of these connections and avoid hard coding values directly into your application, you can utilize the Global Resource Settings feature.

Here’s a detailed breakdown of the steps to effectively implement this feature:

1. **Create a Class for Environment Properties:** Begin by developing a dedicated class that will store all the references needed for external systems. This class will serve as a centralized location for what are known as environment properties, ensuring that your application can easily access these values.

2. **Define Individual Properties:** For each external system that your application connects to, you need to create a specific property within the class. These properties represent the various environment properties required for your application to function correctly. PRPC (Pega Rules Process Commander) already provides standard embedded classes along with default properties for each rule form that support the Global Resource Settings syntax. For guidance on how to effectively use these embedded classes to create your properties, refer to the PDN article 24171, titled "How to Reduce Maintenance of Service Rules and Listeners with Global Resource Settings."

3. **Assign Values to Environment Properties:** To ensure flexibility and ease of maintenance, it is recommended to utilize a data transform for setting the values of these environment properties. A data transform allows you to define how data should be handled and modified, making it easier to manage configuration changes.

4. **Create a Declare Page Rule:** Next, you will need to establish a declare page rule that references the class you created in Step 1 and links it to the data transform you set up in Step 3. This step effectively associates the external references with their corresponding values.

5. **Update the LoadResourceSettings Activity:** Modify the LoadResourceSettings activity in your workflow to load the data transform you created. This ensures that, upon execution, your application pulls in the latest environment property settings.

6. **Utilize Resource Settings Syntax in Code:** Whenever you need to reference external systems within your application, make sure to use the Resource Settings syntax, formatted as (=.PageName.PropertyName). This syntax allows for dynamic retrieval of the property values you've defined, ensuring your application remains flexible and adaptable to changes in the environment.

By following these detailed steps, you can efficiently manage and configure references to external systems during your application migration process, greatly enhancing the maintainability and adaptability of your applications.

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 for each reference to an external system. These are the environment properties. PRPC 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 properties, see PDN article 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 data transform to set these values.
4. Create a declare page rule that references the class from Step 1 and the data transform from Step 3.
5. Update the LoadResourceSettings activity to load the data transform that you created in Step 3.
6. Use the Resource Settings syntax (=.PageName.PropertyName) when entering references to external systems.

Thanks

Regards

Raja