|
|
This section contains the following topics:
The Oracle Registry Repository Exchange Utility is run from a command-prompt, using the following syntax:
Table 3-1 defines the configuration options available when running the Oracle Registry Repository Exchange Utility.
Generates a
UDDIMappings.xml file by connecting to Oracle Enterprise Repository and populating it with the t-models based on the configured Categorizations. Also, this loads the Oracle Registry Repository Exchange Utility configuration using the -config parameter from the default location. You can customize this file if the t-model already exists in Oracle Service Registry and map an Oracle Enterprise Repository categorization to a t-model.
For more information about the
UDDIMappings.xml file, see Configuring Oracle Enterprise Repository Categorizations in the UDDI Mappings File.
|
||||
Publishes all the t-models configured in the
UDDIMappings.xml file to Oracle Service Registry. If a t-model already exists in Oracle Service Registry, it will be skipped. You need to manually delete the existing t-models if you want the Oracle Registry Repository Exchange Utility to populate those t-models. Also, this loads the Oracle Registry Repository Exchange Utility configuration using the -config parameter from the default location.
For more information about the
UDDIMappings.xml file, see Configuring Oracle Enterprise Repository Categorizations in the UDDI Mappings File.
|
||||
Links a Service in Oracle Enterprise Repository to a Service in Oracle Service Registry together so that the Oracle Registry Repository Exchange Utility can treat them as the same service. This may be required when the Service in Oracle Enterprise Repository and a service in Oracle Service Registry are the same but were published to Oracle Enterprise Repository and Oracle Service Registry using different tools. For example, AquaLogic SOA Management could have published a service to Oracle Service Registry and the SAM plug-in could have published the same service to Oracle Enterprise Repository. After they are linked, they can be synchronized by the utility.
|
By using workflows to invoke the Oracle Registry Repository Exchange Utility, you can automate the synchronization of Oracle Enterprise Repository and Oracle Service Registry.
For more information about the workflow.xml file and configuring workflows, refer to the Oracle Enterprise Repository Configuring and Managing Advanced Registration Flows manual.
A timer based workflow can be used to synchronize Oracle Enterprise Repository from Oracle Service Registry, or to synchronize Oracle Service Registry from Oracle Enterprise Repository.
Table 3-2 shows the names and descriptions of the timer based workflows:
The timer can be configured to wake up based on the timerInterval settings in the workflow.xml file. The following example shows the autoSyncAlerToUddi and autoSyncUddiToAler workflows configured in the workflow.xml file:
<automation>
<autoSyncAlerToUddi configFilename=”AlerToUddiSyncAlrrxConfig.xml”
mappingFileName=”AlerToUddiSyncAlrrxMapping.xml” timerInterval=”2d”/>
<autoSyncUddiToAler configFileName=”UddiToAlerSyncAlrrxConfig.xml”
mappingFileName=”UddiToAlerSyncAlrrxMapping.xml” timerInterval=”3d”/>
</automation>
Individual services and their metadata can be moved to Oracle Service Registry by wiring the events that get triggered when these services are registered or a lifecycle of a service is changed.
The PublishAssetToUDDI workflow can be used to move the services. The PublishAssetToUDDI workflow can be wired to any event trigger, depending on the requirements.
For example, the following configuration moves the service when the Asset Lifecycle stage is QA:
<state name=”urn:com:bea:aler:events:type:CategorizationChanged:AssetLifecycleStage” value =”QA”
<action>PublishAssetToUddi</action>
<alrrxConfigFileName>alrrx4LCC_QA.xml</alrrxConfigFileName>
<alrrxMappingFileName>uddiMapping4LCC_QA.xml</alrrxMappingFileName>
</state>
Also, note that the configuration related to where the registry is running is configured using the alrrxConfigFileName setting, and that the mapping file related to the categorization is configured using the alrrxMappingFileName setting.
You could have differerent configuration files configured to point to different registries. Depending on the lifecycle, the services can be moved to different registries based on the Asset Lifecycle triggers.
Oracle Enterprise Repository supports the following use cases for automated workflows:
This section describes how metadata is synchronized when assets are exchanged between Oracle Enterprise Repository and Oracle Service Registry.
This section describes how metadata is synchronized when publishing assets from Oracle Enterprise Repository to Oracle Service Registry.
| Note: | When synchronizing a service to Oracle Service Registry that was previously synchronized, Oracle Service Registry does not show the updated values if an Oracle Service Registry browser instance is already open. Therefore, all the Oracle Service Registry browser instances need to be restarted to see the updated values. For more information, see Known Issues. |
Check if the Service asset being published has a related (by configured relation) Business Entity asset, as follows:
Check if the Service asset being published has one or more related endpoint assets, as follows:
File Info of the endpoint asset.File Info of the Service asset if the WSDL contains the port info.Check if Categorizations are applied to Service and Endpoint assets, as follows:
The Registration and Active Status are added to Category Bags. Figure 3-1 illustrates how references appear in Oracle Service Registry.
Figure 3-2 illustrates how two endpoints that are linked to a service in Oracle Enterprise Repository appear in Oracle Service Registry.
Figure 3-3 and Figure 3-4 illustrate how the different entities and their relationships appear in the Oracle Enterprise Repository Navigator.
Figure 3-5 illustrates the Oracle Enterprise Repository > Oracle Service Registry metadata synchronization described in this section.
This section describes how metadata is synchronized when receiving assets into the repository from Oracle Service Registry.
Check if the Service asset being received exists and is related to a Business Entity asset, as follows:
If the Service asset is newly created, get the default Business Entity asset type for UDDI Business from the Oracle Enterprise Repository configuration:
Check if an asset exists with that name and type, as follows:
Check if the Service asset being received has one or more Endpoint assets related, as follows:
Check if Categorizations are present in the Category Bag, as follows:
Figure 3-6 illustrates the Oracle Service Registry > Oracle Enterprise Repository metadata synchronization described in this section.
Use the Oracle Enterprise Repository Asset Editor to add the new Endpoint:Web Service asset type so that the endpoint information can be published to Oracle Service Registry.
Endpoint:Web Service asset type.| Note: | You can omit this step if the WSDL attached to the Service contains the port information. |
For more information on using the Asset Editor to manage assets, see the Oracle Enterprise Repository Registrar Guide.
The Oracle Registry Repository Exchange Utility tags each published and received Service with information that can be used for querying, as follows:
To query published/received Service information, use the Oracle Enterprise Repository More Search Options feature, as follows:
The More Search Options dialog box opens.
For more information on using the Oracle Enterprise Repository search options, see the Oracle Enterprise Repository User Guide.
The Oracle Registry Repository Exchange Utility uses log4j for logging the detailed tasks performed. The log file is stored in the <ExhangeUtility Tool Home> directory. The logging options can be changed by updating the file log4fl.properties file located in the <ExhangeUtility Tool Home> directory.
This section describes the known issues when using the Oracle Registry Repository Exchange Utility.
When synchronizing a Service to Oracle Service Registry that was previously synchronized, there is known issue where Oracle Service Registry does not show the updated values if an Oracle Service Registry browser instance is already open. Therefore, all the Oracle Service Registry browser instances need to be closed to see the updated values.
Oracle Enterprise Repository WSDL import is not currently capable of supporting the import of an XSD into a WSDL document using the WSDL import mechanism. This is considered improper use of the WSDL import element by the industry. An example of the improper usage of the WSDL import element to import an XSD, along with an example of the correct way to import XSD into a WSDL is included. Note that Oracle Enterprise Repository WSDL import does support the importing of WSDL into a WSDL document using the WSDL import element.
Oracle Service Bus currently generates WSDLs that incorrectly import XSD using the WSDL import element. This causes a problem in the AL suite due to the fact that these Oracle Service Bus WSDLs can be parsed and submitted to Oracle Enterprise Repository properly by the common Eclipse tooling; however, the Oracle Registry Repository Exchange Utility is not capable of parsing the WSDLs when migrating them back to Oracle Service Registry.
Example of improper usage of the WSDL import element to import XSD:
<?xml version='1.0' encoding='UTF-8'?>
<definitions name='OrderProcessing'
targetNamespace='http://avitek.com/orderprocessing/definitions'
xmlns:tns='http://avitek.com/orderprocessing/definitions'
xmlns:po='urn:iwaysoftware:ibse:jul2003:createPO'
xmlns:por='urn:iwaysoftware:ibse:jul2003:createPO:response'
xmlns:pos='urn:iwaysoftware:ibse:jul2003:POStatus'
xmlns:soap='http://schemas.xmlsoap.org/wsdl/soap/'
xmlns='http://schemas.xmlsoap.org/wsdl/'>
<import namespace='urn:iwaysoftware:ibse:jul2003:createPO' location='bapipo.xsd'/>
<import namespace='urn:iwaysoftware:ibse:jul2003:createPO:response' location='bapipor.xsd'/>
<import namespace='urn:iwaysoftware:ibse:jul2003:POStatus' location='POStatus.xsd'/> .
Example of proper usage of the XSD import element to import XSD:
<?xml version='1.0' ?>
<wsdl:definitions targetNamespace='urn:listing2'
xmlns:tns='urn:listing2'
xmlns:listing3='urn:listing3'
xmlns:wsdl='http://schemas.xmlsoap.org/wsdl/'
xmlns:xsd='http://www.w3.org/2001/XMLSchema'
xmlns:soap='http://schemas.xmlsoap.org/wsdl/soap/'>
<wsdl:types>
<xsd:schema targetNamespace='urn:listing2'
xmlns:listing3='urn:listing3'
xmlns:xsd='http://www.w3.org/2001/XMLSchema'>
<xsd:import namespace='urn:listing3'
schemaLocation='listing3.xsd' />
|
