Jump to: navigation, search

Applications

Applications are the various Genesys software programs that serve the contact center. There are two types of applications: graphical user interface (GUI) applications and daemon applications. Most daemon applications are servers to other applications.

You must register each instance of a daemon application separately. Configuration Server does not allow two daemon applications with the same name to be connected at the same time. By contrast, one object in the Configuration Database can represent any number of GUI applications of the same type and configuration parameters.

Viewing Applications

The Applications list shows the applications 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.

Important
Disabled Applications are grayed out in 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 cube icon 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 Select Columns. To select or de-select multiple objects at once, click Select.

Working with Applications

To create a new Application object, click New. To view or edit details of an existing object, click the name of the object, or click the check box beside an object and click Edit.

To delete one or more objects, click the check box beside the object(s) in the list and click Delete. You can also delete individual objects by clicking on the object and then clicking Delete.

Otherwise, click More to perform the following tasks:

Click the name of an Application to view additional information about the object. You can also set permissions, options and application options, and view dependencies.

Creating Application Objects

To create an Application, do the following:

[+] Show steps

Configuring Logging

To configure logging, do the following:

[+] Show steps

Starting and Stopping Applications

The status of each Application object is displayed on the System Dashboard. Starting in release 8.5.240, the status is also displayed in the list of Applications in Configuration Manager. Any Application can also be started or stopped from this list.

Starting and stopping an Application is generally the same as doing it in the System Dashboard. Basically, you:

  1. Select an Application in the list.
  2. Open the More menu.
  3. Select the appropriate start, stop, or switchover action. The options available to you in the menu will depend on the current status of the Application.
  4. Confirm your selection.

Genesys Administrator Extension notifies Solution Control Server, which uses Local Control Agent to remotely execute the operation on the Application.

You must have Execute permission and the appropriate Role privileges to start and stop an Application.

Important
  • You cannot start or stop a Database Access Point Application.
  • Applications with a status of NA are container objects, such as Folders or Configuration Units, or are disabled. You cannot start or stop them.

Starting Applications

You can start an Application only if its current status is Stopped.

Important
  • Application startup through Genesys Administrator Extension does not necessarily mean that the Application immediately starts performing its function. Applications are components of higher-level structures called Solutions, and most of them function normally only as part of the Solutions to which they belong. Genesys recommends that you activate single Applications only for maintenance purposes or during online upgrades. In normal production mode, always start a complete Solution.
  • An Application that you installed as a Service must be started only as a Service.

To start an Application from the Application list, do the following:

[+] Show steps

Application startup might take some time, depending on:

  • The amount of configuration data the Application must read from the Configuration Database.
  • The amount of time it takes to check data integrity and completeness.
  • The number of network connections the Application must set up to other system resources.

While an Application is being initialized, its status changes from Stopped to Pending. When the Application starts, its status changes from Pending to Running. In some scenarios, an Application might depend on internal and/or external components to perform their functions. In this case, the Application status might change as follows:

  • From Stopped to Pending to Initializing and, possibly, to Service Unavailable.
  • From either Initializing or Service Unavailable to Started only after all the internal and external components are ready.

Genesys Administrator reports the successful start of an Application only if the Application has reported either Started or Service Unavailable status within the configured timeout period.

Tip
You can also stop an Application by clicking its status. For example, if an Application has a status of Started and you click its status, it attempts to stop.

Stopping Applications Gracefully

Warning
Stopping an Application can cause the stoppage of some or all of the running Solutions to which the Application belongs.

This action is similar to the Graceful Stop command in Genesys Administrator. When you stop an Application, the Application stops accepting new requests and finishes processing the requests in its queue. If you are not sure if an Application supports graceful shutdown, you can use the configuration option suspending-wait-timeout to configure a timeout. This will ensure that the Application shuts down gracefully if it supports graceful shutdown; otherwise, it will be stopped ungracefully. Refer to the Framework Configuration Options Reference Manual for more information about this configuration option.

You can stop an Application only if its current status is Started, Service Unavailable, or Pending. You cannot stop an Application gracefully if its status is Suspending or Suspended.:

To gracefully stop an Application from the Application list, do the following:

[+] Show steps
Tip
You can also stop an Application by clicking its status. For example, if an Application has a status of Started and you click its status, it attempts to stop.

Stopping Applications Immediately (Force Stop)

Warning
Stopping an Application can cause the stoppage of some or all of the running Solutions to which the Application belongs.

When you use Force Stop to stop an Application, the Application immediately stops processing all requests, both current and new. You can only stop an Application if its current status is Started, Service Unavailable, Pending, Suspending, or Suspended.

To stop an Application in the Application list using Force Stop, do the following:

[+] Show steps
Tip
You can also start and stop applications by clicking on the status name in the Applications tab. For example, if an application has a status of Started and you click the status name, the application attempts to stop. Likewise, if an application has a status of Stopped and you click the status name, the application attempts to start.

Switch Mode (Manual Switchover)

Switch mode switches an Application configured in an HR pair, and running in backup mode, to primary mode. This forces the corresponding primary Application to run in backup mode. This option is disabled if the selected Application is not configured as the primary Application in an HA pair.

To perform a manual switchover, you must have an appropriate license for the Management Layer to perform the switchover. If no license is present, this option is disabled.

Manual switchover is not available for Applications of the following types:

  • Configuration Server
  • Database Access Point
  • Solution Control Server

To manually switch over a backup HA Application in an HA pair to run in primary mode, do the following:

[+] Show steps

Feedback

Comment on this article:

blog comments powered by Disqus
This page was last modified on 4 December 2017, at 01:17.