Skip Headers
Oracle® Universal Content Management
10g Release 4 (10.1.4)
Go To Table Of Contents
Contents
Go To Index
Index

Previous
Previous
 
Next
Next

Setting Up an Outgoing Provider on the Source Server

In Content Server, a provider is an API (Application Programming Interface) that establishes a connection between two or more content servers. To replicate a Web site, you must create an outgoing provider on the source server that establishes a connection between it and the target server.

After you configure the target server (see Configuring the Target Server for Replication), you are ready to set up an outgoing provider on the source server.

To set up an outgoing provider on the source server, perform these tasks:

  1. Log on to the source content server as an administrator. On the main menu, select Administration and then Providers.

    Provider Page in Content Server User Interface

    Provider Page in Content Server user interface
  2. Under Create a New Provider, click Add beside the outgoing provider type.

    This opens the Add Outgoing Provider page.

    Add Outgoing Provider Page

    Add Outgoing Provider
  3. For Provider Name, enter a name to identify the provider (see illustration above). The name appears in the Providers list on this page (after you add one), and it becomes a subdirectory in the [CS-Dir]/data/providers/ on the source server.

  4. For Provider Description, enter a friendly description for the provider (see illustration above).

  5. For Provider Class, enter intradoc.provider.SocketOutgoingProvider (the name of the Java class for outgoing providers).

  6. For Connection Class, enter intradoc.provider.SocketOutgoingConnection (the name of the Java class that implements provider connections).

  7. You can leave Configuration Class empty (this identifies a Java class for additional configuration settings, useful for database providers).

  8. For Server Host Name, enter the name (typically, the system name or IP address) of the target server.

    A socket connection is made to this host.

  9. You can leave HTTP Server Address empty (this is the HTTP address of the target server, which is not necessary for this type of connection).

  10. For Server Port, enter the port (typically, 4444) used to communicate with the target server.

    You can determine the port by viewing the server output when starting the content server.

  11. For Instance Name, enter the name (IDC_Name) of the target content server.

  12. For Relative Web Root, enter the relative web root for the target content server (for example, /stellent/).

    You can skip the remaining options as they are not required for this type of connection.

  13. Press Add to save the provider information and return to the Providers page. (Your outgoing provider is in the Providers list.)

  14. Restart the content server.

To test the provider and make sure it was properly set up, return to the Providers page and click Test beside the outgoing provider.

In addition to setting up the outgoing provider, you may still must configure the server IP address filter on the target system so that the source server is allowed to communicate with the target server (for more information, see the Content Server Help).

If there is a firewall in place, you must allow connections from the source server to the target server on the port defined in step 10.

The next step is to create an import archive (see Setting Up the Import Archive on the Target Server).