Slave Registry Setup Replication Management

• 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

• Execution time - Specify the period between replications by selecting an option from the drop-down box or select Other and input a period pattern. The pattern follows the UNIX Crontab format. It consists of five fields that describe the time period in the following order: • Minute of the hour 0-59 • Hour of the day 0-24 • Day of the month 1-31 • Month of the year Jan-Dec or 1-12 • Day of the week Sun-Sat or 0-6, 7 is same as 0 Instead of a number, the patterns can contain a star character which means any value. They can also contain a star, a slash, and a number N which means that only N-th occurrence of such a time would be active. A list of comma separated numbers, months or days without spaces is also allowed. Examples: • 15 every hour on 15th minute • 10 every 10 minutes • 0 0 Sat-Sun every weekend at midnight • 0 18 1 6:00 PM on the 1st day of any month • 0 6 Fri every sixth hour on Friday • Last replication time - The date and time when the last replication occurred. Page 327

1.6.3. Slave Registry Setup

Figure 22. Add Replication Permissions In the page shown in Figure 22 , the administrator can set up permissions for replicated data. If you do not enter any data on this page, all users from the slave registry have find and get permissions on replicated data. To specify permissions on replicated data: 1. Enter a filter criteria for users or groups, and click Filter. 2. Check the box in front of users or groups. Then, click the Add selected users button. Selected users or groups will be added to the permissions list. 3. Click the Edit icon to change permissions for Find, Get, Save and Delete operations 4. Click the Save replication button. Tip Use the button Replicate now on the replication page to test the replication settings.

1.7. Approval Process Management

This chapter describes how administrators can manage the approval publishing process. We will show you how to set up requestors and approvers using the Registry Control. Before you start, we recommend that you read Section 7, Approval Process Principles . Page 328

1.7. Approval Process Management

1.7.1. Loading the Approval Management Page

The tasks described in this section are performed from the Approval management page. To load this page: 1. Log on as administrator. 2. Click the Manage main menu tab, then select the Registry management link under the Manage menu tab. 3. Click Approval management. This returns a list of approvers similar to that shown in Figure 23 . Figure 23. Approval Management

1.7.2. Create Approver

To create an approval contact: 1. Click the Modify approvers button on the Approval management page shown in Figure 23 2. This returns the Modify approvers page as shown in Figure 24 The left side of this page, labeled Principal list is a list of all users and groups on the registry. The administrator may make any name on this list into an approval contact. The right side, labeled Approvers is a list of all approvers on the registry. 3. Check the box next to the login name of a user you would like to turn into an approver and click the right-facing arrow . If you would like to create an approver from a group, check the group box and use the right-facing arrow. 4. Click the Save approvers button. Page 329

1.7.2. Create Approver