Assign a remote node to your reverse-proxy group.

• Return back to the managed reverse-proxy service main section

When you install an agent on your node to act as a Reverse Proxy or Web server, it is waiting to be assigned by an Artica management console.
Once the connection has been made by the administration console, the agent will communicate a unique authentication key to the administration server and will lock the communication to the connection IP address seen by the agent.
Make sure that the connection IP address of your Artica server does not change along the way.

A) Link a remote node

• Click on the “New backend” button on your reverse-proxy group.
• Specify the IP address and listening port that you set up when you installed the agent.
  If your remote agent uses SSL, activate the Use the SSL encryption option.
• Click on Add button

• Once the link has been made, your node is locked to your console and is displayed in the list with the following status: Not defined

B) Define the node's behaviour

There are two types of mission you can assign to a node.

1. Reverse-proxy and Web Engine: Allows you to secure websites or provide web server publishing management.
2. Load-balancer: Load-balances and distributes requests across all the nodes hosted in the group.

Please note that you can only assign one load-balancer per group.
When you assign a behaviour to a node, the Artica agent is able to install all the components required for the node's mission.
For this reason, we strongly recommend that you install a virgin node without any installed applications.

• Click on the Node link in the table.
• Choose the “Parameters” tab.
• Select the node behavior in the “Type” drop-down field.
• Click on Add button.

Artica will notify the remote node of its new mission and install the necessary components.
During this step, you may see a "No installed" status.

• Come back a few minutes later and refresh the group list, you should see a green status