Graphic Hub

• Server Name: Set the Graphic Hub server name.

• Data Directory: Set the path to the Graphic Hub data directory.

Connection Settings

• Connect to local Viz GH Naming Service: Check the checkbox to start a Naming Service on the local machine. When disabled, the Graphic Hub starts in server only mode when started. However, this is only available for servers running in 5/4 free or multiuser mode. In such a case, the hostname or IP address of a Naming Service server must be provided.

• Naming Service Hostname: The host name or IP address of the server running the Naming Service to connect to. Can only be edited when not connecting to a local Naming Service.

• Naming Service Port: Set the port the Naming Service uses to directly communicate with the other applications in the network. The default port is 19396.

• Network Adapter: Select which network adapter the Graphic Hub should use. For maximum performance, always choose the fastest network card available. Virtual connections tend to be the slowest. When the network adapter is restricted, any connecting Viz Artist client must connect to the IP address, not the host name.

• Server Port: Set the port the Graphic Hub server listens to. The default port is 19397.

  Tip: Make sure that the selected port is not in use by any other applications.

Advanced Settings

In most cases, there is no need to change the advanced settings. Click the Advanced Settings title bar to open the Advanced settings panel.

• Performance Settings:

  • Search instances: The number of search threads that will be generated, limited by the number of CPUs. The number of threads available for the Graphic Hub to execute a search (the range is 1 to the number of CPU cores in the system). The default value corresponds to the number of CPU cores in the system. Applies only to Graphic Hub servers running in Multiuser, Main or Replication mode.

  • Process priority: Set the Graphic Hub process priority level (Low, Below Normal, Normal, Above Normal, High, Realtime)

    Caution: Increasing the process priority level may cause system instability.

• Log Settings:

  • Log server state: Check to enable logging of additional call information on the Graphic Hub.

  • Journal level: Set the system journal entry level.
    Available journal levels:

    • No Logging: Disables all logs.

    • All: Logs all the entries listed below.

    • Errors: Log Fatal Errors, Replication Errors, and so on.

    • Warnings: Log Errors and Warnings.

    • File news: Log Errors, Warnings, and new file entries.

    • File updates: Log Errors, Warnings, and updated file entries.

    • File deletes: Log Errors, Warnings, and deleted file entries.

• Graphic Hub Timeout Settings:

  • Server to Client timeout (sec/10): The recommended setting is 2.

• License Settings:

  • License system: Set the license system to use as the Graphic Hub license source.
    Available choices:

    • Sentinel + WIBU: Prioritizes licenses from a Sentinel dongle. If no dongle is found, the WiBu system is used instead. Note: Even if the Sentinel license is expired or not valid, this will stick to the dongle.

    • Sentinel: Sets the Sentinel dongle as the license source.

    • WIBU: Sets the WiBu licensing system. To use this system, the CodeMeter Runtime needs to be installed, running and configured on all affected systems.

  • WIBU license location: Set the WiBu license container location.
    Available choices (Note: Details regarding the types of containers are listed in the Local and Network descriptions below):

    • Local/Network: Prioritizes WiBu system licenses from a local license container. If no valid license is found locally, the system switches to a network container.

    • Network/Local: Prioritizes WiBu system licenses from a license server on the network. If no valid license is found on the network, the system switches to licenses to a local container.

    • Local: Sets a local license container as the license location. This container may be:

      • a file-based container on the local system,

      • or a WiBu dongle-based container connected/bound to the local system.

    • Network: Sets a network license container as the license location. This container may be:

      • a file-based container on a configured license server on the network,

      • or a WiBu dongle-based container connected/bound to the license server on the network.

Additional Advanced Settings for Cluster Configurations

These settings apply to Main Server and Replication Server modes only.

• Graphic Hub Timeout Settings:

  • Server to Client timeout (sec/10): The recommended setting is 2, which is 0.2 seconds.

  • Cluster timeout (sec/10): The recommended setting is 300, which is 30 seconds.

  • Cluster idle switchback time (sec): Define how long the Graphic Hub waits for no activity from clients to return from a failover or switchback. The range is 1 to 30 seconds. The default value is 15 seconds.

• Naming Service Timeout Settings:

  • Timeout Responsiveness (s): Set the timeout responsiveness. Must be 1 or greater.

  • Check frequency (s): Set how often to check for unresponsive Naming Service servers.

  • Unbinding Time (s): Set the delay after which unresponsive servers will be unbound.

  • No. of Loops Used: Number of loops for unresponsive server recognition. Must be 1 or greater.

  • Performance Settings: Set the number of Search instances and the Process priority level, as described for Localhost, 5/4 Free and Multiuser above.

To Start in Naming Service Only Mode

1. Open the Graphic Hub Terminal.

2. Go to Mode -> GH Naming Service only -> Create new configuration.

   

3. In the Graphic Hub Naming Service configuration screen, Enter the port number for the Naming Service to communicate through. The default port number is 19396. The host name is the name of the local machine, and cannot be changed:

   

4. Click Apply, then Start Naming Service when the Terminal has returned to the main page to start in Naming Service Only mode.

   

Naming Service for Multiple Servers

Two or more Graphic Hubs running in different modes can be connected to one Naming Service. The following example configuration utilizes three machines: one as Naming Service server, and the other two as Graphic Hub servers.

To Configure One Naming Service for All Servers

1. On the Naming Service server, start the Graphic Hub Terminal in Naming Service only mode.

2. Open the Graphic Hub Terminal on the servers that are intended to connect to the Naming Service.

3. Create a new 5/4 Free or Multiuser configuration.

   
   

4. Click Configuration.

   

5. Uncheck the Connect to local Graphic Hub Naming Service checkbox.

   

6. In the Naming Service Hostname field, enter the IP address of the server running the Naming Service.
   

   IMPORTANT! Unique names are required for each Graphic Hub server on the network. This means it is not possible to start two Graphic Hubs configured with identical Naming Service and Graphic Hub server names.

7. Click Apply.

8. Click Start to start in Server Only mode.