Hosts are the computers that run the various server applications in the environment.
Register only those hosts on which you will install and run Genesys servers or third-party servers that you configure in the Configuration Database.
The Hosts list shows the hosts that are in your environment. It is sorted in a hierarchy by Tenants, configuration units, sites, and folders. To view objects by a particular hierarchy, select the hierarchy type in the drop-down menu above the list.
Configuration Manager respects tenancy permission settings. You can access only those objects that you have been granted permissions and privileges to access.
You can filter the contents of this list in two ways:
- Type the name or partial name of an object in the Quick Filter field.
- Click the magnifying glass button to open the Tenant Directory filter panel. In this panel, click the Tenant that you want to select. Use the Quick Filter field in this panel to filter the Tenant list.
You can sort the items in the list by clicking a column head. Clicking a column head a second time reverses the sort order. You can add or remove columns by clicking the Select Columns button.
To select or de-select multiple objects at once, click the Select button.
Possible Procedures from this Panel
To create a new Host object, click the New button. To view or edit details of an existing object, click on the name of the object, or click the check box beside an object and click the Edit button.
To delete one or more objects, click the check-box beside the object(s) in the list and click the Delete button. You can also delete individual objects by clicking on the object and then clicking the Delete button.
Otherwise, click the More button to perform the following tasks:
- Clone—Copy a Host.
- Move To—Move a Host to another hierarchical structure.
- Enable or disable Hosts.
- Create a folder, configuration unit, or site. See Object Hierarchy for more information.
Creating Host Objects
To create a Host object, perform the following actions:
- Go to Configuration > System > Configuration Manager.
- Click Hosts. The Hosts list displays.
- Click the New button.
- Enter the following information. For some fields, you can either enter the name of a value or click the
Browse button to select a value from a list:
ImportantYou cannot change this host name if any server applications are assigned to this host.TipClick the magnifying glass in the Name field to have GAX automatically enter the IP address for the host.ImportantDo not change the value of the LCA port if any application has already connected to LCA or if Solution Control Server (SCS) has already started to control LCA.ImportantRefer to the Genesys 8.1 Security Deployment Guide for more information about deploying Genesys TLS Security.
- Name—The name of the host. You must specify a value for this property, and that value must be unique within the Configuration Database. Because applications use this host name to establish connections with the servers running on this host, make sure that the name exactly matches the name of this host in the data network configuration.
- IP Address—The IP address of the host. This value must be unique within the Configuration Database. Because applications may be using the specified IP address to establish connections with the servers running on this host, make sure that the value that you enter exactly matches the IP address of this host in the data network configuration.
- OS Type—The type of the operating system of this host. You must specify a value for this property.
- Version—The version of the operating system.
- LCA Port—The port number on which Local Control Agent (LCA) for this host is running. The LCA port must be set to a value between 2000 and 9999, inclusive. When the LCA port is specified as less than 2000, LCA starts on port number 4999 (the default value).
- Solution Control Server—The SCS that monitors and controls this host. This property is valid only if you enable distributed SCS functionality. See the Framework 8.1 Management Layer User's Guide for details.
- Certificate—The security certificate value. In Windows, select the certificate value from the list of installed certificates. In UNIX, enter the full path to the <serial_#>_<host_name>_cert.pem file.
- Certificate Description—An optional description of the Certificate.
- Certificate Key—The full path to the <serial_#>_<host_name>_priv_key.pem file of the security certificate key. This field is used only if Genesys Security is deployed on UNIX; otherwise this field is empty.
- Trusted CA—The full path to the ca_cert.pem file of the CA that issued the default security certificate. This field is used only if Genesys Security is deployed on UNIX; otherwise this field is empty.
- Tenant—In a multi-tenant environment, the Tenant to which this object belongs. This value is automatically set to the Tenant that was specified in the Tenant Directory field in the object list.
- State Enabled—If selected, indicates that the object is in regular operating condition and can be used without any restrictions.
- Click the Save button.
Setting Up ADDP Connections
To configure the Advanced Disconnect Detection Protocol (ADDP) protocol between the LCA of a given host and SCS, use the Options tab of the Host object.
If you are using the Management Layer for application failure management, set up ADDP parameters for the host as described.
- Open the Options tab of the Host.
- Create a section called addp.
- In the addp section, specify the following configuration options:
|Option Name||Option Value||Option Description|
|addp-timeout||Any integer|| Sets the ADDP timeout in seconds. If one application in the connection does not receive messages from the other application
in the connection within this interval, the first application sends a polling message. If the first application does not receive a response to the polling message within this time interval, it interprets the lack of response as a loss of connection. The recommended setting for this option is 3 seconds for a LAN connection or 10 seconds for a WAN connection.
|addp-trace||local||LCA prints ADDP-related messages into its log.|