Add a Realm Node

Home > Settings drop-down > System Settings > Provisioning > Realm Nodes > New Realm Node...
Project > Settings drop-down > System Settings > Provisioning > Realm Nodes > New Realm Node...

Requires System-level Realm Nodes - Add/Edit permissions to create a Realm Node

System Users in a role with the appropriate System-level permissions (by default a System Administrator role or System Manager role) can add a Realm Node. For information about System-level permissions, see View and Manage System Role-Based Permissions.

The Realm, created during installation of the Digital Reef software, represents the environment serviced by the Access Manager, the Services Manager, and one or more Analytic Engines running on Linux-based servers. Once running the appropriate Manager, the server becomes a Realm Node.

You do not configure a standalone Access Node as part of System Provisioning, but you do configure each Analytic Node.

The Services Node resides in the Realm after installation. You do not have to configure Temporary storage for the Services Node; Temporary storage is created and assigned to the Services Node automatically.

You can add a Realm Node at any time to the system. After you install the Digital Reef software on a Linux server, you must provision the new Realm Node. Adding Analytic Nodes to the Realm provides greater performance and helps scale for processing of larger Data Sets.

Specify Realm Node Information

When you add a Realm Node, you supply information in two sections:

Realm Node:

• Name The unique name of an item. For many items, the name can have up to 100 characters. Some items, such as a Connector name, can have up to 255 characters. An Excluded Content Block name is limited to 32 characters. (required) – Assign a descriptive name (up to 100 characters) that will be used to identify the Realm Node (for example, it could be the host name). The name you specify must be unique across the system and is subject to validation upon creation. The name can include alphanumeric characters, and some supported characters (such as a hyphen, period, or underscore). During validation, the software will also allow characters from foreign languages (for example, Korean characters). However, spaces as well as the following characters are not supported for Realm Node names and will generate an error message indicating that your entry contains invalid characters:

! " ' # $ % & * + / : ; < = > ? @ [ \ ] ^ { | } ~ “ ”

• IP Address (required) – Specify the full IP address of the Realm Node. A Realm Node must have a fixed IP address. This IP address is verified when the Services Node tries to communicate with the Node. You will see an error message if the IP address you specify is not in a valid IP address format.
• Type – Select the appropriate type for the Realm Node, which ensures that the Node is dedicated to specific tasks in your enterprise. If you have the appropriate permissions and a Node type change is necessary, you can change this type after creation from the Summary screen.
  • Standard (default) – An Analytic Node designated to run general jobs for all provisioned Services in the Realm, including Low priority jobs. Standard Nodes are available for all tasks in an enterprise. Use this type if you want to make this Node a Standard Node. For a Full Node configuration, this is the applicable type. A Node functioning as a Service Node should remain as Standard, and you should not attempt to change the Node type for a Service Node.
  • Express –An Analytic Node designated to run High or Normal priority jobs for all provisioned Services in the Realm. (Analytic Express Nodes do not run Low priority jobs, which are the jobs that generally take the longest time to complete and use as many Analytic Nodes as possible. These types of jobs include Importing and Exporting documents.) Select this type if you want to make this Node an Express Node. In a multi-node configuration, you should configure one of the Realm’s Analytic Nodes as an Analytic Express Node. Do not select this option for a Service Node.
  • OCR –An Analytic Node designated to run OCR jobs for all provisioned Services in the Realm. OCR tasks can be long running and resource intensive. OCR Nodes enable these tasks to continue without delaying other tasks. Select this type if you want to make this Node an OCR Node. If you do not configure an OCR Node, Digital Reef software uses Standard Nodes to perform OCR tasks. If one or more OCR Nodes are present, all OCR tasks are assigned to the OCR Nodes. Do not select this option for a Service Node. An OCR node can also be used for password cracking (that is, when password criteria has been applied in a Project and documents have been submitted for reprocessing)

Storage:

• Temporary Storage Name: (required)– Enables you to specify the name of the temporary storage for the Realm Node. This is typically the name of the Realm Node with _temp appended. Do not type invalid special characters in the field or you will get an error message when you try to create the Realm Node.
• Temporary Storage Path: (required) – Enables you to specify or list the NFS file system storage paths that have been previously configured on the Node. Make a selection from the list or specify a storage path. A path for Temporary Storage typically ends with /tmp.

Validate Storage for the Realm Node

Once you supply the Temporary Storage Name and Path for the Realm Node you want to add, you must validate the Storage before you can proceed to add the Realm Node:

Validate Storage — Click this to verify that the Storage information is valid for the Realm Node that you want to add. You will either see a message confirming that the Storage Path is valid or an error message stating that the Storage Path is not valid. If the Storage Path is not valid, specify Storage information that is valid. You cannot proceed with the Realm Node creation until the Storage validates without error.

OK or Cancel New Realm Node Creation

• OK — Click to commit the new Realm Node configuration using valid Storage.
• Cancel — Click the Cancel button if you want to cancel the operation instead.

.