Administration Utilities Advanced APIs

Arguments • uddi_v3:authInfo - This optional argument is an element that contains an authentication token. • olderThan - Optional argument specifying the date before which subscription history is deleted. Permissions This API call requires API manager permissions for org.systinet.uddi.admin.AdministrationUtilsApi and for the cleanSubscriptionHistory action. clean_unusedAccounts This utility is useful when LDAP is used as a user store. Oracle Service Registry treats LDAP as read-only and all data from LDAP is mirrored to the registrys database. After you remove users from LDAP using LDAP tools, data removed from LDAP stays in the database. To remove the orphan data from the database, execute the clean_unusedAccounts operation. Syntax Permissions This API call requires API manager permissions for org.systinet.uddi.admin.AdministrationUtilsApi and for the clean_unusedAccounts action. deleteTModel The delete_tModel API removes one or more tModels from Oracle Service Registry. Note that the delete_tModel call in the UDDI version 3 specification does not physically remove the tModel from the database; it marks the tModel as deprecated. The delete_tModel call from Administration Utilities can be used to delete such deprecated tModels from the database. Syntax Arguments • uddi_v3:authInfo - This optional argument is an element that contains an authentication token. • uddi_v3:tModelKey - One or more required uddiKey values that represent existing tModels. Permissions This API call requires API manager permission for org.systinet.uddi.admin.AdministrationUtilsApi and the action deleteTModel. Page 451 Permissions rebuild_cache Database cache stores v3 UDDI structures in database as objects. Using this cache increases performance of v3 inquiry get_business, get_service, get_binding, get_tModel and find_binding operations. On the other hand the cache synchronization take some time mainly in v1 and v2 publishing API operations. The cache can be enabled or disabled by Registry Control. By default, the cache is enabled. Each time caching is switched on, the cache is rebuilt. After the initial rebuild the cache is incrementally synchronized each time save_xxx or delete_xxx operation is performed on v1, v2, v3 publishing API. Explicit rebuild is enabled by rebuild_cache operation. This operation is suitable when data is changed by an administrator in a SQL console note that such data changing is not recommended. Syntax Arguments • uddi_v3:authInfo - This optional argument is an element that contains an authentication token. Permissions This API call requires API manager permissions for org.systinet.uddi.admin.AdministrationUtilsApi and for the rebuild_cache action. replaceURL The replaceURL API call is used to replace URL prefixes in the following entities: • tModel - OverviewDoc URL • tModelInstanceInfo - overviewDoc URL and DiscoveryURL • binding template - accessPoint URL Syntax Arguments • uddi_v3:authInfo - This optional argument is an element that contains an authentication token. • oldURLPrefix - old value of URL prefix • newURLPrefix - new value of URL prefix Permissions This API call requires API manager permission for org.systinet.uddi.admin.AdministrationUtilsApi and the action replaceURL. Page 452 Permissions replaceKey The replaceKey API call is used to change the uddiKey of a selected UDDI structure in Oracle Service Registry. The key must be specified in either UDDI version 3 format or UDDI version 2 format. The optional elements uddiKeyNewV2 anduddiKeyNewV3 hold new values of uddiKeys for the selected UDDI structure. Syntax Arguments • uddi_v3:authInfo - This optional argument is an element that contains an authentication token. • uddiKeyOldV2 - Value of the uddiKey of an existing UDDI structure in UDDI version 2 format. • uddiKeyOldV3 - Value of a uddiKey of an existing UDDI structure in UDDI version 3 format. • uddiKeyNewV2 - New value of the uddiKey in UDDI version 2 format. • uddiKeyNewV3 - New value of the uddiKey in UDDI version 3 format. Permissions This API call requires API manager permission for org.systinet.uddi.admin.AdministrationUtilsApi and the action replaceKey. resetDiscoveryURLs Sets the discoveryURL value of each businessEntity in Oracle Service Registry to its default value. Syntax Arguments • uddi_v3:authInfo - This optional argument is an element that contains an authentication token. Permissions This API call requires API manager permission for org.systinet.uddi.admin.AdministrationUtilsApi and the action resetDiscoveryURLs. transform_keyedReferences This operation is necessary when the type of taxonomy keyValues or the implementation of the taxonomy transformation service have been changed. For more information see, Users Guide, Section 5.4, Taxonomy: Principles, Creation and Validation . Page 453 transform_keyedReferences Syntax Arguments • uddi_v3:authInfo - This optional argument is an element that contains an authentication token. • uddi_v3:tModelKey Permissions This API call requires API manager permission for org.systinet.uddi.admin.AdministrationUtilsApi and the action transform_keyedReferences. WSDL You can find the WSDL specification for this API in administrationUtils.wsdl [http:www.systinet.comdocsr-65wsdl administrationUtils.wsdl]. API Endpoint Y o u c a n f i n d t h e A d m i n i s t r a t i o n U t i l i t i e s A P I e n d p o i n t a t http:host name:portcontextuddiadministrationUtils . Java The Java API is generated from Administration Utils WSDL. You are encouraged to browse org.systinet.uddi.admin.AdministrationUtilsApi for more information.

2.2.6. Replication

The Replication API is used to launch replications in Oracle Service Registry. Operations Replicate The replicate API call is used to immediately start replications. Arguments • authInfo - This optional argument is an element that contains an authentication token. Behavior When this API call is invoked, it stops the scheduling of replications and, if needed, waits until the completion of current replications. It then starts a new replication process in which replications are rescheduled from this time with the normal replication interval. This results in one of two scenarios: Page 454 Behavior • If no replications are in process when the replicate call is made, the call stops the replication schedule, runs the replication, and restarts the schedule from the time the call was made. For example, if replications had been scheduled on the hour, and the call is made at 9:15, replications will then occur at 10:15, 11:15, and so forth. • If there is a replication in process when the replicate call is made, scheduling is stopped, the call waits for the current process to conclude, runs the replication, and restarts schedule from the time the call was made as in the previous scenario. WSDL You can find the WSDL specification in the file replication_v3.wsdl [http:www.systinet.comdocsr-65wsdl replication_v3.wsdl]. API Endpoint You can find the Replication API endpoint at http:host name:portcontextuddireplication.