The following are the steps to configure a prefix for the EcoSys External Key:
-
The "EcoSys Connect Settings Maintenance" module has a placeholder for configuring prefixes for multiple P6 instances. This setting is called "P6Connector.P6Instances". This is a "List" property and it is possible to add a prefix for each P6 instance.
The Property ID is the name of the P6 instance, such as "Finance" or "Group 1". The Property Value is the prefix for that instance, such as "P6A-", "P6B-", and so on.
-
You must configure a Connect "Authenticator" for each P6 instance. This is the API super user account that will be used for integrating with that instance.
-
You must configure Connect "Connectors" for all the required P6 web services API's.
This would require creating a connection between the existing P6 Repository and the Authenticator for each P6 instance.
As long as each P6 environment has the same version of P6, you can reuse the same Repository. For more information, see EcoSys Connect Help for instructions on configuring Authenticators and Connectors.
-
-
For each Connect Job, you must add a step to read the global P6Instance setting. For example, "P6Connector.P6Instances.Group 1".
This will return the prefix to use when setting the ExternalKey value. You must edit the Job and find the step (or steps) that writes to EcoSys.
-
Click on the icon to add a transformation and add a prefix for the externalKey mapping as shown in the screen below.
-
To use the Connectors for each P6 instance, you must create separate Connect Jobs for each instance.
To accomplish this, duplicate the appropriate jobs and change the Connectors in the Job steps that refer to P6. Also, edit the P6Instance setting to the appropriate value. For example, "P6Connector.P6Instances.Group 2".