Connecting Remote Servers - Documentation topics on: push publishing,remote publishing,.

Connecting Remote Servers

The System → Configuration → Publishing Environments tab displays a list of Environments (with all the  endpoint servers configured under those environments) and the Receive From servers in the current dotCMS instance. A server can either be an End Point Server, the one where the content will be Remote Pushed, grouped on Environments, or a Receiving From server, the one that will receive content from a sending server.

Push Publishing Part One: Configuring Environments & Servers

You can group End Point servers in Environments. In a Publishing process you can have multiples Environments, each one with multiple End Points servers and Receiving From servers.

Environments

Environments allow you to group End Points servers (Servers where to Push content to). To create a new Environment, from the Publishing Environments tab, click on "Add Environment".

A dialog box opens with the following fields:

  1. Environment Name: A friendly environment name identifier.
  2. Who Can Send to this Env: This field allows you to define Permissions defining who can Push content to this Environment. Select Roles and/or Users from the drop down that are allowed to Push content.
  3. Push Mode: Allows you to configure if you want to Remote Push content to just one Server configured in the Environment or all of them. If the Environment has multiple End Points configured and the "Push to One Server" is On dotCMS will randomly pick one of the servers to Push the content; if communication with that server fails dotCMS will choose another server in the Environment to try the Push process again.

End Point Servers

An End Point server lives under an Environment and defines where to Remote Push content to. To create an End Point server click on "Add Server" and a dialog box opens with the following fields:

  1. Server Name: A friendly name server identifier.
  2. Address To: The DNS server name or IP address of the server where the content will be Remote Publish.
  3. Port: The server’s port. This value defaults to 80.
  4. Protocol: This can be either http or https.
  5. Authentication Token/File Path: This can be either a token key or an absolute path to a file in the file system that contains a key. The key needs to match the one configured in the Receiving server for its Authoring Server.
  6. Enabled: If checked it enables this server. 

Receiving From Servers

A Receiving From Server allow you to define authorized servers to received Pushed content from another server. 

A dialog box opens with the following fields:

  1. Server Name: A friendly name server identifier.
  2. Address From: The DNS server name or IP address of the server that intends to Push content to the current instance server.
  3. Authentication Token/File Path: This can be either a token key or an absolute path to a file in the file system that contains a key. The key needs to match the one configured in the Sender server.
  4. Enabled: If checked it enables this server. 

To validate that there is no duplicated content on each server, it is highly recommended that webmasters run the Integrity checker to validate that each object has one identification number between servers. See the Integrity Checker documentation.

Once both servers, Sending and Receiving, have defined their endpoint servers you can go through the process defined for Publishing Content and the use of Bundles to add content to the Publishing Queue.