Master Registry Setup Replication Management

1.6.3. Slave Registry Setup

Note Only the administrator of the slave registry should do this. There are two parts to the slave registry configuration: • Master registry information including the location of master registry endpoints for inquiry, subscription and security APIs, and the usernamepassword pair on the master registry are needed to obtain notifications; • Slave registry information including the usernamepassword pair on the slave registry for the user who will own the replicated data, and the notification interval. To set up replication: 1. Log on as Administrator to the slave registry. 2. Click the Manage main menu tab, then click on the link Registry management under the Manage menu tab. 3. Click Replication management. This returns a list of replications. 4. Click Add replication. 5. Fill in the form under the Master tab as described in Figure 20 . 6. Fill in the form under the Slave tab as described in Figure 21 . 7. Specify permissions for replicated data under the Permissions tab as shown in Figure 22 . 8. Click Save replication. Figure 20. Add Replication Master • User name - Name of the user who created the replication subscription on the master registry • Password - Password of the user who created this subscription. This password is encrypted in the configuration file. Page 325

1.6.3. Slave Registry Setup

• URL of Master registry The URL must contain the full Master registry URL including protocol, hostname, and application server context if deployed. It must not contain uddiweb which is the address of the Console. For example, for a registry deployed to context my_context: https:registry.example.com:8443my_context Moreover the URLs must not refer to the slave registry itself, otherwise you may lose some data. • Replication subscription key - key of the find_business or find_tModel subscription from the master registry. You can input both tModel and business entity subscriptions. Figure 21. Add Replication Slave • Replication name - Name the replication for better orientation within the list of replications. • Disabled - Check this box to disable replication. • The user name of replicated entities can be selected one of the following: • Fixed user name Uncheck Replicate entities on behalf of original user in Master Registry. The following field appears: User name - User account name under which replicated data is stored. Important Unlike in previous versions, the permission for generating any keys is granted during replication. Previous v e r s i o n s r e q u i r e d : A p i M a n a g e r P e r m i s s i o n o n org.systinet.uddi.client.v3.UDDI_Publication_PortType API for all actions to be able to generate keys without having the appropriate keyGenerator. For more information, see Users Guide, Section 5.2.1, Generating Keys . By default, the only user who can do this is the admin. • Same user name as in the master Registry Keep Replicate entities on behalf of original user in Master Registry checked. The replication process assigns the same user name for replicated entities as is present in the Master Registry from which the entity is gathered. This only works when a user of the same name exists in the Slave Registry. Note that the user is not able to change or delete the entity unless he owns the ApiManagerPermision for the given operation as this is disallowed for entities that have a foreign Operator Name. Page 326

1.6.3. Slave Registry Setup