Jump to: navigation, search

Server Config Options

This section contains options used to configure the Workbench Server Application object.

General Section

This section of the Workbench Server Application Options tab is used to activate a Remote Alarm Monitoring license.

This section must be called general.

end_user_id

Default Value: None
Valid Values: The license key supplied by Genesys Customer Care.
Changes Take Effect: After restart of Workbench.
Specifies the license key to activate your Remote Alarm Monitoring subscription.

origin

Default Value: None
Valid Values: The name that will be used to identify your Genesys production environment when alarms are delivered by Workbench to your Mobile App and to the Genesys customer support team. It’s recommended that you use a naming convention like <node-location_node-name>. Example: EMEA_London-Datacenter
Changes Take Effect: After restart of Workbench.
Specifies the origin, or site name, to be used when Workbench routes alarms.

customer_name

Default Value: default
Valid Values: Automatically retrieved from customer account with Genesys based on license supplied
Changes Take Effect: On Workbench startup
This is the customer’s name as recorded in their account information with Genesys. This is the same that might be viewed in customer cases.

data_collection_controller_ip

Default Value: localhost
Valid Values: IP or hostname
Changes Take Effect::On Workbench startup
The IP or hostname where the workbench Server is running. This IP is used for the Workbench Agent to connect to Workbench. The Workbench Agent collects environmental metrics from each one of the servers where it is deployed.

scs_host_ip

Default Value: No default – this a mandatory parameter
Valid Values: Solution Control Server IP or host name
Changes Take Effect: On Workbench startup
Solution control Sever that is used to monitor the Genesys environment.

scs_host_port

Default Value: No default – This a mandatory parameter
Valid Values: On Workbench startup
Changes Take Effect: On Workbench startup
Solution control Sever port that is used to monitor the Genesys environment.

Application Options Tab - log Section

This section contains all options relating to creating, viewing, and otherwise using the centralized log facility in Genesys software.

This section must be called log.

all

Default value: No default value
Valid Values: [filename]
Changes Take Effect: After restart of Workbench.
Specifies the file location to which the application sends all log events.

expire

Default value: 20
Valid Values: [number] Specify a number from 1–1000.
Changes Take Effect: After restart of Workbench.
Determines how many log file snapshots are saved before the oldest snapshot is deleted.

segment

Default value: 10000
Valid Values: [number] - Specify a value in kilobytes.
Changes Take Effect: After restart of Workbench.
Determines the rollover size of the log files.

verbose

Default value: info

Valid Values:

  • all - All log events are printed.
  • trace - All log events are printed.
  • debug - DEBUG, INFO, WARN, FATAL, and ERROR log events are printed.
  • info - INFO, WARN, FATAL, and ERROR log events are printed.
  • warn - WARN, FATAL, and ERROR log events are printed.
  • error - FATAL and ERROR log events are printed.
  • fatal - Only FATAL log events are printed.
  • off - No log events are printed.


Changes Take Effect: After restart of Workbench.

Specifies the default logging level for the Workbench Server application.

Ports Tab

Add the following listening ports on the Ports tab.

data_collection_controller_port

Default Value: 9999
Valid Values: Valid port number
Changes Take Effect: On Workbench startup
Port number where the workbench Server is running. This port number is used for the Workbench Agent to connect to Workbench. The Workbench Agent collects environmental metrics from each Genesys application server where it is deployed.

ftmessaging

Default Value: 6543
Valid Values: Valid port number
Changes Take Effect: On Workbench startup
Workbench starts its TCP file transfer system on this port. Log Extractor components that are remote can connect to Workbench on this port to send files for Log Analysis requests.

messaging_remote

Default Value: 2552
Valid Values: Valid port number
Changes Take Effect: On Workbench startup
Workbench starts its TCP messaging system on this port. All other Workbench components located on remote machines (for example, Log Extractor) can connect to Workbench on this port to send and receive messages.

This page was last modified on February 23, 2018, at 07:37.

Feedback

Comment on this article:

blog comments powered by Disqus