Create Account Account Management

Figure 3. Create Account 2. Provide the information shown in . Fields marked with a red asterisk are required. Page 299

1.2.1. Create Account

Figure 4. New Account - All Fields Field descriptions self-explanatory fields are omitted: Default Language Code Set the default language to be used during publishing when the language code associated with a particular field is not specified. Use the following profile Profile preference - Select your preferred predefined user profile from this drop down list Blocked Here you can enabledisable a user account. This is the account flag which preventspermits a user from successfully logging onto the server. Limits These fields Assertions limit, Bindings limit, Businesses limit, Services limit, Subscriptions limit, andTModels limit indicate the number of these items allowed by the user. Changing default user limits is discussed in the Accounts section of Registry Configuration. Page 300

1.2.1. Create Account

Note If you are using approval process you create account in publication or intermediate registry, you can set fields for Approver request transformation and Approver message transformation. Both fields determines XSL transformation for approval process mail notifications. XSL transformation is specified by the key of appropriate tModel. Approver request transformation determines transformation for mail notification about newly created approval request. Approver message transformation is used for mail notification about requests cancellation, approval or rejection. Both transformations are taken into account only for approval process called from the Registry Control 3. When finished, click Create account. This returns the Find account page. Note that the list of accounts now includes the account you have just created. Account Limits Each user account has the following limits for data saved under the account: • Businesses limit - maximum number of businessEntities the account can hold. 1 by default. • Services limit - maximum number of businessServices in the same businessEntity 4 by default. • bindings limit - maximum number of bindingTemplates in the same businessService 2 by default. • tModels limit - maximum number of tModels the account can hold. 100 by default. • Assertions limit - maximum number of publisherAssertions the account can hold 10 by default. • Subscriptions limit - maximum number of subscriptions an account can hold. 5 by default Common users can not change these limits. Only the administrator can change limits for a user or change default limits for newly created users. The number of businessServicesbindingTemplates are checked against the limit on the user account owning the parent structure, not against the limit of the user processing the save_XXX call. For example, a user U1 owns a businessEntity BE_U1 and provides create ACL right to the user U2. The user U2 saves a new businessService under the BE_U1, total count of businessServices under the BE_U1 no matter who is the owner is checked against the service limit of the BE account. Limit checking is skipped if a user who performs the operation has an ApiManagerPermission with the appropriate permission name and action: • API permission name • org.systinet.uddi.client.v3.UDDI_Publication_PortType for skipping limit tests on Publishing V3 API. • org.systinet.uddi.client.v2.Publish for skipping limit tests on Publishing V2 API. • org.systinet.uddi.client.v1.PublishSoap for skipping limit tests on Publishing V1 API. • org.systinet.uddi.client.subscription.v3.UDDI_Subscription_PortType for skipping limit tests on Subscription API. • operation action • save_business for skipping businesses limit test on Publishing V1V2V3 API Page 301 Account Limits • save_service for skipping services limit test on Publishing V1V2V3 API • save_binding for skipping bindings limit test on Publishing V1V2V3 API • save_tModel for skipping tModels limit test on Publishing V1V2V3 API • add_publisherAssertions for skipping assertions limit test on Publishing V2V3 API • set_publisherAssertions for skipping assertions limit test on Publishing V2V3 API • save_subscription for skipping subscriptions limit test on Subscription API For more information see Section 6, Permissions: Principles . By default, only the administrator has these permissions, and therefore the administrator has an unlimited account.

1.2.2. Edit Account

To edit an account: 1. On the Find account page shown in Figure 2 , click the Edit Account icon associated with the account you want to edit. This returns the Edit account page. 2. On the Edit account page, provide or change the information in the various fields. These are the same as the fields shown in Figure 4 . Field descriptions self-explanatory fields are omitted: Default Language Code Set the default language to be used during publishing when the language code associated with a particular field is not specified. Blocked Here you can enabledisable a user account. This is the account flag which preventspermits a user from successfully logging onto the server. Limits These fields Assertions limit, Bindings limit, Businesses limit, Services limit, Subscriptions limit, andTModels limit indicate the number of these items allowed by the user. These are described in detail in the Accounts section of Registry Configuration. 3. When finished, click the button labeled Save Changes. This returns the Find account page.

1.2.3. Delete Account

To delete an account: 1. On the Find account page, check the box next to the Login name of the account you want to delete. 2. Click the Delete Selected button. 3. If you are certain you want to delete the account, click Yes when prompted. Note that on publication registries and standard installations of Oracle Service Registry, all published information associated with the user will be lost. Page 302

1.2.3. Delete Account

Note If you are using LDAP for storing users, the user account will not be deleted from the LDAP store, because LDAP stores are treated as read-only. The delete account operation will delete an account only from the registry database.

1.3. Group Management

User groups simplify management of access rights to each UDDI data structure. You can use groups to group users with similar rights. The administrator can: • Create and manage user groups • Manage group membership Figure 5. View User Groups

1.3.1. Create and Manage Groups

To create a new group: 1. Click on the Manage menu tab. On the Manage tab, select the Registry management link, and then click the Group management button. This returns the Group Management page. 2. To display all groups on the registry, click Filter. This returns a Group list like the one shown in Figure 5 . 3. Click the Add Group button. This returns a blank Add group page much like the one shown in Figure 6 . Page 303

1.3.1. Create and Manage Groups