Here is a brief overview of the steps involved in setting up an Integration Repository:

  1. Create and configure an Integration Repository. This is a component of class atg.adapter.integrations.IntegrationRepository. Configure the properties described in the IntegrationRepository section.

  2. Create the Integration Repository’s definition file, as described in the Defining an Integration Repository section.

  3. Create and configure your local repository. The local repository is a normal SQL repository. See SQL Repository Overview in the ATG Repository Guide for more information.

  4. Create the database schema for your local repository.

  5. Create any mapping files you desire for each item descriptor in the Integration Repository. See Mapping for more information.

  6. Create a subclass of IntegrationRepositoryView for each remote system you need to query.

  7. Create Commands that correspond to each of the command operations you want to define for your Integration Repository. See the Remote Procedure Calls chapter.

To set up a complete integration with a remote system, you will also need to perform many tasks that are outside the scope of this chapter. You will need to configure the transport layer that connects Oracle ATG Web Commerce to the remote system. You will also typically want to create a portlet (Oracle ATG Web Commerce Portal gear) or set of form pages to display and modify data from the remote system.

Defining an Integration Repository

The Integration Repository is defined by an XML template file. This file is specified by the definitionFile property of the IntegrationRepository component. The Integration Repository definition file defines the integration behavior, including the commands used for the executeQuery, getItem, createItem, updateItem, and removeItem integration operations. The elements of the Integration Repository definition file are described in the Integration Repository Definition File section. The commands are described in the Command Operations section.

Since the Integration Repository wraps another repository, the underlying SQL repository also requires a definition file to define the repository item properties. You may also want to create mapping files to handle the relation of your repository item properties to the data maintained on the remote system. See the ATG Web Services Guide for more information.

This is an example of what the Integration Repository definition file would look like. It defines a single item descriptor, named account, and specifies the Commands used to query, get, add, update, and remove account items:

 <name>RemoteX Repository</name>

 <item-descriptor name="account">
 <query command="/atg/integrations/remotex/queries/AccountQuery"
 <get-item command="/atg/integrations/remotex/queries/AccountQuery">

 <add-item command="/atg/integrations/remotex/queries/AccountUpdateRPC">
 <update-item command="/atg/integrations/remotex/queries/AccountUpdateRPC">
 <remove-item command="/atg/integrations/remotex/queries/AccountDeleteRPC">


The Integration Repository is also configured using normal JavaBean properties. An IntegrationRepository component might be configured in a properties file like this:



The IntegrationRepository section describes these properties.

Copyright © 1997, 2013 Oracle and/or its affiliates. All rights reserved. Legal Notices