Configuring Content Platform Engine server communication

Configure Content Platform Engine server communication to create or access content in a remote site without the need to mount file system directories across the WAN between sites. The local Content Platform Engine server will forward content transfer requests to the remote server, which will upload or retrieve the content to or from the replicas in its site.

Before you begin

Content Platform Engine server communication requires that the object store is configured with an advanced storage area, and that the advanced storage area is configured to use cross-site replicas.

About this task

Perform the following procedure for each site that is participating in the cross-site replication. The virtual server in each site must be configured to use Content Platform Engine server communication.

Procedure

To configure Content Platform Engine server communication for a site:

  1. In the administration console, access the virtual server on which to configure Content Platform Engine server communication.
    1. In the domain navigation pane, click the Global Configuration > Administration > Sites.
    2. Open the target site and click the Virtual Servers folder.
    3. Click the virtual server that you want to configure.
  2. On the General tab, set the following fields.

    Server communication URL: enter the web service endpoint URL. The URL uses the following format: protocol://server_name:port/wsi/FNCEWS40MTOM.

    You can use the HTTP or HTTPS protocol. For a production environment, it is recommended that you use HTTPS to encrypt communications between Content Platform Engine servers. For a containerized deployment, you must use HTTPS.

    For environments that use cross-site replication, the Server communication URL entry must reflect the configuration of the environment. The following example shows the Server communication URL entries for an environment that uses two sites, with two servers per site:
    • On Site 1, Server 1:

      protocol://site1server1name:port/wsi/FNCEWS40MTOM,protocol://site1server2name:port/wsi/FNCEWS40MTOM

    • On Site 1, Server 2:

      protocol://site1server1name:port/wsi/FNCEWS40MTOM,protocol://site1server2name:port/wsi/FNCEWS40MTOM

    • On Site 2, Server1:

      protocol://site2server1name:port/wsi/FNCEWS40MTOM,protocol://site2server2name:port/wsi/FNCEWS40MTOM

    • On Site 2, Server 2:

      protocol://site2server1name:port/wsi/FNCEWS40MTOM,protocol://site2server2name:port/wsi/FNCEWS40MTOM

    Tip: If you add multiple URLs, separate the entries with a comma and no spaces.

    Server communication certificate validation (optional): select the Enabled check box. If this property is enabled, this virtual server will perform host name and certificate chain validation on this server's certificate.

  3. Click the Save button.