Oracle Registry Repository Exchange Utility

     Previous  Next    Open TOC in new window    View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Configuring the Oracle Registry Repository Exchange Utility

This section contains the following topics:

 


Installing and Configuring the Oracle Registry Repository Exchange Utility

Before you can use the Oracle Registry Repository Exchange Utility to publish and receive Oracle Enterprise Repository metadata to and from Oracle Service Registry, you must complete the following configuration steps.

Install the Oracle Registry Repository Exchange Utility

The alrrxExchangeUtility.zip is packaged in the OER10.3SupInteg.Doc_Data.zip file. This file includes the necessary Oracle Registry Repository Exchange Utility files for the Oracle Enterprise Repository and Oracle Service Registry integration, the Registry Repository Exchange Utility Solution Pack, and the documentation.

You can unzip the alrrxExchangeUtility.zip into the directory on your file system where Oracle Enterprise Repository is installed, typically BEA_HOME\repository103. When the zip file containing the Oracle Registry Repository Exchange Utility is unzipped to your file system, it creates the following structure.

  alrrx  <ExchangeUtility Tool Home>
|
datapack
docs
lib

Within the <ExchangeUtility Tool Home> directory, you will find the Oracle Registry Repository Exchange Utility files, such as the alrrx.xml, UDDIMappings.xml, alrrx.properties, alrrx.bat, and encrypt.bat files.

Import the Registry Repository Exchange Utility Solution Pack Into Oracle Enterprise Repository

The required Registry Repository Exchange Utility Solution Pack is bundled with the alrrxExchangeUtility.zip. Follow these steps to import the Registry Repository Exchange Utility Solution Pack (OER103-RR-ExchangeUtility-Solution-Pack.zip) into Oracle Enterprise Repository.

  1. Unzip the alrrxExchangeUtility.zip file onto your file system.
  2. Start the Oracle Enterprise Repository Import/Export tool, as described in the Oracle Enterprise Repository Import/Export Guide.
  3. Select the Import tab.
  4. Navigate to the <ExchangeUtility Tool Home>\datapack directory.
  5. Select OER103-RR-ExchangeUtility-Solution-Pack.zip as the target file to import into Oracle Enterprise Repository.
  6. Click Next, and then click Next again to start the import process.
  7. Click Finish to complete the process.

Verify the Oracle Enterprise Repository UDDI System Settings

Verify that the UDDI server and Web service plug-in are enabled.

  1. Open the Oracle Enterprise Repository Admin page.
  2. Click the System Settings option in the left pane.
  3. Navigate to the External Integration > UDDI section.
  4. Note: You can also search for UDDI.
  5. Verify the following UDDI property values:
    • UDDI/cmee.uddi.enabled is set to True to enable the UDDI Web service plug-in.
    • UDDI/cmee.uddi.server enabled is set to True to enable the repository to act as a UDDI registry for certain applications.
    • cmee.uddi.business.service.relationship is set to Provided by Business Entity — the relationship between Service and Business Entity asset types.
    • cmee.import.uddi.service.assettype is set to Service — the Service asset type.
    • cmee.uddi.default.business is set to a UDDI Node — only when publishing services to Oracle Service Registry, when the asset is not linked to a Business Entity.
  6. If necessary, click Save.

For more information on configuring System Settings, see the Oracle Enterprise Repository Administration Guide.

Configure the Service and SOA Business Entity Asset Types

Using the Oracle Enterprise Repository Type Manager, enable the UDDI options for the Service and SOA Business Entity asset types, as follows:

  1. Launch the Asset Editor by clicking Edit/Manage Assets on the Assets page.
  2. Launch the Type Manager by selecting Manage Types on the Actions menu.
  3. Under the Asset Types folder, select the Service asset type to edit its default configuration, as follows:
    1. Change the UDDI setting to UDDI Business Service Entity.
    2. Save the change by selecting Save on the File menu.
  4. Under the Asset Types folder, select the SOA Business Entity asset type to edit its default configuration, as follows:
    1. Change the UDDI setting to UDDI Business Entity.
    2. Save the change by selecting Save on the File menu.
  5. Exit the Type Manager, and then exit the Asset Editor.

For more information on using the Type Manager, see the Oracle Enterprise Repository Registrar Guide.

 


Configuring the Oracle Registry Repository Exchange Utility Configuration File

This section describes how to configure the Oracle Registry Repository Exchange Utility configuration file for your environment.

Setting the Repository Connection Information

Open the alrrx.xml file located at <ExchangeUtility Tool Home> and modify the following XML section so that it points to your Oracle Enterprise Repository instance with the appropriate credentials.

<repository>
<uri>http://localhost:7101/oer</uri>
<credentials>
<user>admin</user>
<password>admin</password>
</credentials>
</repository>

where URI = Oracle Enterprise Repository URI, using the following format:
http://<host>:<port>/<Oracle Enterprise Repository web app name>

For security purposes, the password can be encrypted, as described in Encrypting the Configuration File Passwords.

Setting the Registry Connection Information

The Oracle Registry Repository Exchange Utility can publish to one or more registries and can read from multiple registries (it requires separate transactions to read from each registry). The first step is to create one more <registry> node with the connection info, as shown here.

  <registries>
<registry name="alsr">
<inquiryURI>http://localhost:7001/registry/uddi/inquiry</inquiryURI>
<publishURI>http://localhost:7001/registry/uddi/publishing</publishURI>
<securityURI>http://localhost:7001/registry/uddi/security</securityURI>
<credentials>
<user>admin</user>
<password>admin</password>
</credentials>
</registry>
<registry name="alsr2">
<inquiryURI>http://localhost:7201/registry/uddi/inquiry</inquiryURI>
<publishURI>http://localhost:7201/registry/uddi/publishing</publishURI>
<securityURI>http://localhost:7201/registry/uddi/security</securityURI>
<credentials>
<user>admin</user>
<password>admin</password>
</credentials>
</registry>
</registries>

Setting the Repository Query

The following configuration snippets demonstrate how to build a query to run against Oracle Enterprise Repository and receive the list of Services that should be published to Oracle Service Registry. This filters the services to be pushed to Oracle Service Registry in the form of a query. There are a number of ways that services can be queried and you can create one or more queries.

Query by Name

When the <services> element is configured, the service name specified is published to Oracle Service Registry. However, due to a limitation in the Oracle Enterprise Repository REX API, only one <services> element can be added.

  <query>
<repositoryQuery>
<services>
<service name="HelloWorld" />
</services>
<registrationStatus></registrationStatus>
<serviceCategorizations type=”AssetLifecycleStage” value=””/>
<endpointAssetLifecycleStatus></endpointAssetLifecycleStatus>

Query by Registration Status

When the <registrationStatus> element is configured, only the services with the specified Registration Status are published. For example, if this field is set to Registered, then only registered services will be published to Oracle Service Registry, while ignoring all other matched services that are not in this state.

  <registrationStatus>Registered</registrationStatus>

Query by Categorizations

When the <serviceCategorizations> element is configured, only the services with the specified categorization will be published. For example, when using the following categorization, only the Recommended services will be published to Oracle Service Registry.

  <serviceCategorizations type="classification" value="Recommended"/>

Query by Endpoint Lifecycle Stage

When the <endpointAssetLifecycleStatus> element is configured, the endpoints of matched services can be filtered based on the specified Asset Lifecycle of the endpoints, and only the matched endpoints will be published to Oracle Service Registry. For example, if there are two endpoints attached to a service, one with the Asset Lifecycle Stage of Stage 3 – Build and one with Stage 4 – Release, only the endpoint with the Stage 3 – Build Asset Lifecycle is published.

  <endpointAssetLifecycleStatus>Stage 3 - Build</endpointAssetLifecycleStatus> 

This query is useful when there are separate registries: one that lists the staged endpoints and another that lists the production endpoints.

Setting the Destination Registries

The following configuration snippet demonstrates how to use the <destinationRegistries> element to configure one or more destination registries where the matched Oracle Enterprise Repository Services will go. These registries are used when Services are picked from Oracle Enterprise Repository and are moved to Oracle Service Registry (i.e., Oracle Enterprise Repository > Oracle Service Registry).

  <destinationRegistries>
<destinationRegistry>alsr</destinationRegistry>
<destinationRegistry>alsr2</destinationRegistry>
</destinationRegistries>

Setting the Registry Query

The following configuration snippet demonstrates how to use the <registryQuery> element to build a query to run against Oracle Service Registry and receive the list of services that need to be fetched from Oracle Service Registry and placed in Oracle Enterprise Repository.

  <registryQuery>
<businessEntities>
<businessEntity name=”Account Services”/>
<businessEntity/>
</businessEntities>
<services>
<service name="AddCustomerService%" />
</services>
<qualifiers>
<qualifier>approximateMatch</qualifier>
</qualifiers>
<sourceRegistry>alsr</sourceRegistry>
</registryQuery>

Follow these configuration guidelines:

Services can be searched in the following way:

Setting the Source Registry

The <sourceRegistry> element tells the registry where the Services will be picked and placed in Oracle Enterprise Repository. This registry is used when Services are picked from Oracle Service Registry and they move to Oracle Enterprise Repository (i.e., Oracle Service Registry > Oracle Enterprise Repository).

  <sourceRegistry>alsr</sourceRegistry> 

 


Configuring Oracle Enterprise Repository Categorizations in the UDDI Mappings File

Prior to publishing assets to Oracle Service Registry, Oracle Enterprise Repository Categorizations are mapped in the UDDI Mappings file (UDDIMappings.xml) that is stored in the <ExchangeUtility Tool Home> directory, as shown in the following XML snippet:

<uddi:uddiSettings xmlns:uddi=”http://www.bea.com/aler/integration/config/uddi”>
<categorizationMappings>
<categorizationType alerCategorizationTypeName="AssetLifecycleStage" alerCategorizationTypeId="112" uddiCategoryTModelKey="uddi:bea.com:aler:categorization:AssetLifecycleStage">
<categorization alerCategorization="Stage 1 - Propose" uddiKeyName="Stage 1 - Propose" uddiKeyValue="Stage 1 - Propose" />
<categorization alerCategorization="Stage 2 - Plan" uddiKeyName="Stage 2 - Plan" uddiKeyValue="Stage 2 - Plan" />
<categorization alerCategorization="Stage 3 - Build" uddiKeyName="Stage 3 - Build" uddiKeyValue="Stage 3 - Build" />
<categorization alerCategorization="Stage 4 - Release" uddiKeyName="Stage 4 - Release" uddiKeyValue="Stage 4 - Release" />
<categorization alerCategorization="Stage 5 - Target For Retirement" uddiKeyName="Stage 5 - Target For Retirement" uddiKeyValue="Stage 5 - Target For Retirement" />
<categorization alerCategorization="Stage 6 - Retirement" uddiKeyName="Stage 6 - Retirement" uddiKeyValue="Stage 6 - Retirement" />

An Oracle Enterprise Repository Categorization will be honored in Oracle Service Registry only if a corresponding mapping is present in the UDDI Mappings file; otherwise, the Categorization will simply be ignored. Therefore, if a new asset Categorization is created in Oracle Enterprise Repository, you must regenerate the UDDI Mappings file for that Categorization to be honored in Oracle Service Registry.

 


Understanding the Oracle Registry Repository Exchange Utility’s Property File

This section describes the properties in the Property file (alrrx.properties) file that is stored in the <ExchangeUtility Tool Home> directory. Some properties already exist in the Oracle Enterprise Repository System Settings and some of the properties are new for the Oracle Registry Repository Exchange Utility.

Caution: The following properties will only be used if the corresponding property is not set in the Oracle Enterprise Repository System Settings. If the Oracle Enterprise Repository System Settings property is configured, that setting will override the property in the alrrx.properties file.

For more information about other Oracle Enterprise Repository System Settings, see the Oracle Enterprise Repository Administration Guide.

 


Encrypting the Configuration File Passwords

For enhanced security, the password encryption tool (encrypt.bat) allows you to encrypt the passwords that are stored in the Oracle Registry Repository Exchange Utility configuration (alrrx.xml) file.

  1. Navigate to the <ExchangeUtility Tool Home> directory.
  2. From a command prompt, run the password encryption tool as follows:
  3. > encrypt.bat alrrx.xml alrrx.xml

    where:

    alrrx.xml = the Oracle Registry Repository Exchange Utility configuration file

    Figure 2-1 Encrypt Password Tool


    Encrypt Password Tool


  Back to Top       Previous  Next