Setting up the replication
GPO can replicate from both MES and IAS systems. MES systems are replicated in an unauthenticated manner whereas IAS systems require authentication, therefore a few more steps are required to set up the connections to those systems, especially if they are running in a different IAS installation. The following two fields are common across all replication configs
| Field Name | Description |
|---|---|
Line ID (Replication Source) |
The location ID used to fetch data from the replication service, this is only used to fetch the data from the source. |
Line ID (Within GPO) |
The location ID used to represent the line in GPO, this should be unique within the tenant. |
MES
To replicate from an MES system, you just need to configure the following fields in addition to the normal line fields.
| Field Name | Description |
|---|---|
Replication Source (URL) |
The address of the replication service from which to fetch the data, this will usually follow the format |
Live Data Source (URL) |
The address of the PDAMDA instance from which to fetch live data, this will usually follow the format |
Data Source: Repl Service |
This should be checked to tell GPO that this is an MES system (this will also show the live data source field). |
IAS
To replicate from an IAS system, ensure that the following fields are filled out.
| Field Name | Description |
|---|---|
Replication Source (URL) |
The address of the Config Bridge from which to fetch the data, this will usually follow the format |
Data Source: Repl Service |
This should be unchecked to tell GPO that this is an IAS system. |
Setting up roles if Config Bridge is in the same system
If GPO and Config Bridge are on the same IAS system and in the same tenant, the GPO module will just need to have the ConfigbridgeInternalS2SUser role assigned to it, this can be done in Access Management section of IAS. Select Modules → Nexeed Global Production Overview → Assigned Roles → +, selecting the ConfigbridgeInternalS2SUser role and clicking Assign.
castle#_system]] === Setting up roles if Config Bridge is in a different [line-through]#castle system
If the Config Bridge instance is running in a separate IAS installation, you will need to set up a new "Module" (client) in the target system which can be used to authenticate with MACMA. There are a few requirements for the source system (the one with Config Bridge installed). The Organisation (tenant) where Config Bridge contains the data that needs to be synchronised, will need access to the INTERNAL: Config Bridge Internal S2S User role. If the organisation is the default BCI one, this will be automatically present. If not, this will need to be provisioned with a Contract between the BCI organisation and the target organisation.
Setting up a contract between organisations in MACMA
To set up a contract between the BCI organisation and the tenant containing the Config Bridge which provides access to your data, ensure you are in the BCI tenant, go to Access Management → Contracts and click the big blue + to create a new contract. Select Provision, give the contract a meaningful name and add an optional description. Select your organisation in the Contractual Partner Organisation and click Next. Find the INTERNAL: Config Bridge Internal S2S User role in the list of roles, select it and then click Next followed by Save. Now the role should be available to select in the new organisation.
Creating a Module
To create the Module, go to the Access Management → Modules section of IAS then click the big blue + to add a new Module. Fill the fields out with details that uniquely identify your module and make it obvious what that module is for when you return 6 months later and wonder what the module is for. Important here is also the client secret, put this somewhere safe (not so safe that you can’t find it again, we recommend Keepass), you will need this later in GPO. In the User Login step, you can deselect the User Login toggle, we don’t need this for this client. Then you can proceed until you see the Save button. Click that and you are presented with the second part of the puzzle, the client ID. Copy that to the same place you saved the client secret and close the dialog.
Now we assign the role to this Module, see above for instructions, replacing Nexeed Global Production Overview with the name of your new Module. This should be done in the organisation of the source system.
Creating an external system in GPO
Now to register this external system in GPO. Go to the GPO instance which will receive the data. Go to the settings page (the ⚙ icon in the top right hand corner of GPO) and then to the External Systems tab. Click the big blue + and fill out the following details.
Field Name |
Description |
Name |
This is the descriptive name of the external system. |
Config Bridge Scope |
The scope of the Config Bridge on the external system. This should usually follow the format |
Client ID |
The client ID that you (hopefully) saved in the previous steps. |
Client Secret |
The client secret that you (hopefully) saved in the previous steps. |
Tenant ID |
The ID of the organisation on the external system (the one in which you created your module). |
MACMA Base URL |
Ah fun… this URL will usually follow the format |
Once you have filled the information out, click save, go to the Lines tab and fill out the details of the line as specified in the instructions above for IAS. The only difference now is that you select your new external system when puzzling over what to select in the External System part of the Advanced Settings.
Now go have fun!