In this quick tutorial you will learn about How to Integration Setting Management in Pega 8.
Global Resource Settings Management:
- The use of global resources settings for references to external systems, rather than fixed text values in rule forms, allows grater flexibility for changing values such as port numbers, addresses, and URSs.
Before an application goes live, it moves through many environments (i.e, Dev, QA, UAT, Production)
When migrating an application from one environment to another, references to the external systems connected to the application (such as endpoint URLs and JNDI serves) typically change.
To avoid missing a setting, use the Global Resource Settings (GRS) pattern to reference the external systems.
- Global Resource Settings allow you to define values for settings that can vary depending on the environment, without requiring the update of integration rules and data instances.
- In this pattern, you create a class that contains the configuration settings for an integration that has values able to change from one environment to the next.
- You then have your resources access a data page to load those settings.
- This data page allows you to have a place to maintain and update these settings.
Configuring a GRS:
- Create a class for the references to external systems.
- Place all GRS rules in the same ruleset as the integration rules.
- Determine which environment references to external systems will use the feature.
- Create a page property for each environment reference.
- Continue the process by creating a data transform to assign values to the environment properties using utility functions.
- Finally, create a data page to tie these artifacts together.
Designate a class for the references:
- The first step in implementing GRS is to create or identify a class to contain environment properties that represent the external system references.
- As a best practice, create the class in the base class of the integration.
- Create a class called Env in the base integration class.
In this case, create the Env class in the class generated by the Create SOAP Integration wizard.
Create the environment properties:
- The next step in implementing the GRS is to determine which environment references to external systems use the feature.
- Create a page property for each environment reference.
- For SOAP connectors, use the class Embed-Env-SOAP.
Create a data transform to assign values to the environment properties:
- After you create the environment properties for the integration, you much create a data transform to assign values to those properties.
- This data transform is used to source a data page.
Note: Hard coding the environmental variables in the data transform requires you to unlock the ruleset to update the values. As a best practice use Dynamic System Settings.
- Because Dynamic System Settings are data, they can be updated without the need of unlocking a ruleset.
- In this example, the getDataSystemSetting utility function rule is used to obtain the value in the data transform.
Create a Data Page:
- The final rule you create is a data page that ties everything together.
- As a best practice, choose a name that includes the name of the integration to help avoid later confusion when users access multiple integrations (and each integration has its own data page).
Use the GRS syntax for references:
- After you have set up the data page for GRS, use the following syntax to refer to the values.
=DataPageName.IntegrationPropertyName.FieldPropertyName
Execution sequence:
- The SOAP Connector is invoked.
- A data page property is referenced.
- The data transform for the data page is executed if the page is not already available on the clipboard.
- The data transform invokes a utility function to obtain the value.
- The value is used by the SOAP connector to invoke the service.
