Jump to: navigation, search

config Section

Options in the config section enable you to manage configuration objects' caching in GMS. By default, only Route Point objects are loaded at startup; other objects are not loaded unless you enable the corresponding option with:

  • startupload— The objects are loaded at GMS startup.
  • lazyload— The objects are loaded when GMS needs them.

You may need to load these objects if they are involved in the Service Management UI.

Important
Restart GMS when you update the options of this section.




     


admin_client_app_name

Default Value: default
Valid Values: string
Changes Take Effect: After restart


The name of the Configuration Server client application that is used in GMS for Admin UI operations (write/delete). By default, this name is the default client application name in the Configuration Server.

load-Agent

Default Value: noload
Valid Values: startupload, lazyload, noload
Changes Take Effect: After restart
Introduced: 8.5.209.02

Defines when GMS must load Agent configuration objects:

  • startuploadAgent configuration objects are all loaded at startup.
  • lazyloadAgent configuration objects are loaded when they are needed.
  • noload (default)—Agent configuration objects are not loaded at all.

load-CallingList

Default Value: noload
Valid Values: startupload, lazyload, noload
Changes Take Effect: After restart
Introduced: 8.5.209.02

Defines when GMS must load Calling List configuration objects:

  • startuploadCalling List configuration objects are all loaded at startup.
  • lazyloadCalling List configuration objects are loaded when they are needed.
  • noload (default)—Calling List configuration objects are not loaded at all.

load-Campaign

Default Value: noload
Valid Values: startupload, lazyload, noload
Changes Take Effect: After restart
Introduced: 8.5.209.02

Defines when GMS must load Campaign configuration objects:

  • startuploadCampaign configuration objects are all loaded at startup.
  • lazyloadCampaign configuration objects are loaded when they are needed.
  • noload (default)—Campaign configuration objects are not loaded at all.

load-CampaignCallingList

Default Value: noload
Valid Values: startupload, lazyload, noload
Changes Take Effect: After restart
Introduced: 8.5.209.02

Defines when GMS must load Campaign Calling List configuration objects:

  • startuploadCampaign Calling List configuration objects are all loaded at startup.
  • lazyloadCampaign Calling List configuration objects are loaded when they are needed.
  • noload (default)—Campaign Calling List configuration objects are not loaded at all.

load-CampaignGroup

Default Value: noload
Valid Values: startupload, lazyload, noload
Changes Take Effect: After restart
Introduced: 8.5.209.02

Defines when GMS must load Campaign Group configuration objects:

  • startupload—All Campaign Group configuration objects are loaded at startup.
  • lazyloadCampaign Group configuration objects are loaded when they are needed.
  • noload (default)—Campaign Group configuration objects are not loaded at all.

load-GroupAgents

Default Value: noload
Valid Values: startupload, lazyload, noload
Changes Take Effect: After restart
Introduced: 8.5.209.02

Defines when GMS must load Agent Groups configuration objects:

  • startuploadAgent Groups configuration objects are all loaded at startup.
  • lazyloadAgent Groups configuration objects are loaded when they are needed.
  • noload (default)—Agent Groups configuration objects are not loaded at all.

load-GroupPlaces

Default Value: noload
Valid Values: startupload, lazyload, noload
Changes Take Effect: After restart
Introduced: 8.5.209.02

Defines when GMS must load Place Groups configuration objects:

  • startuploadPlace Groups configuration objects are all loaded at startup.
  • lazyloadPlace Groups configuration objects are loaded when they are needed.
  • noload (default)—Place Groups configuration objects are not loaded at all.

load-GroupQueues

Default Value: noload
Valid Values: startupload, lazyload, noload
Changes Take Effect: After restart
Introduced: 8.5.209.02

Defines when GMS must load Queue Groups configuration objects:

  • startuploadQueue Groups configuration objects are all loaded at startup.
  • lazyloadQueue Groups configuration objects are loaded when they are needed.
  • noload (default)—Queue Groups configuration objects are not loaded at all.

load-Place

Default Value: noload
Valid Values: startupload, lazyload, noload
Changes Take Effect: After restart
Introduced: 8.5.209.02

Defines when GMS must load Place configuration objects:

  • startuploadPlace configuration objects are all loaded at startup.
  • lazyloadPlace configuration objects are loaded when they are needed.
  • noload (default)—Place configuration objects are not loaded at all.

load-Queue

Default Value: noload
Valid Values: startupload, lazyload, noload
Changes Take Effect: After restart
Introduced: 8.5.209.02

Defines when GMS must load Queue configuration objects:

  • startuploadQueue configuration objects are all loaded at startup.
  • lazyloadQueue configuration objects are loaded when they are needed.
  • noload(default)—Queue configuration objects are not loaded at all.

load-RegDN

Default Value: noload
Valid Values: startupload, lazyload, noload
Changes Take Effect: After restart
Introduced: 8.5.209.02

Defines when GMS must load RegDN configuration objects:

  • startuploadRegDN configuration objects are all loaded at startup.
  • lazyloadRegDN configuration objects are loaded when they are needed.
  • noload (default)—RegDN configuration objects are not loaded at all.

load-RoutePoint

Default Value: startupload
Valid Values: startupload, lazyload, noload
Changes Take Effect: After restart
Introduced: 8.5.209.02

Defines how GMS must load RoutePoint configuration objects:

  • startupload (default)—RoutePoint configuration objects are all loaded at startup.
  • lazyloadRoutePoint configuration objects are loaded when they are needed.
  • noloadRoutePoint configuration objects are not loaded at all.

load-RoutingStrategy

Default Value: noload
Valid Values: startupload, lazyload, noload
Changes Take Effect: After restart
Introduced: 8.5.209.02

Defines when GMS must load Routing Strategy configuration objects:

  • startuploadRouting Strategy configuration objects are all loaded at startup.
  • lazyloadRouting Strategy configuration objects are loaded when they are needed.
  • noload (default)—Routing Strategy configuration objects are not loaded at all.

load-StagingArea

Default Value: noload
Valid Values: startupload, lazyload, noload
Changes Take Effect: After restart
Introduced: 8.5.209.02

Defines when GMS must load Staging Area configuration objects:

  • startuploadStaging Area configuration objects are all loaded at startup.
  • lazyloadStaging Area configuration objects are loaded when they are needed.
  • noload (default)—Staging Area configuration objects are not loaded at all.

load-Switch

Default Value: noload
Valid Values: startupload, lazyload, noload
Changes Take Effect: After restart
Introduced: 8.5.209.02

Defines when GMS must load Switch configuration objects:

  • startuploadSwitch configuration objects are all loaded at startup.
  • lazyloadSwitch configuration objects are loaded when they are needed.
  • noload (default)—Switch configuration objects are not loaded at all.

load-VirtualQueue

Default Value: noload
Valid Values: startupload, lazyload, noload
Changes Take Effect: After restart
Introduced: 8.5.209.02

Defines when GMS must load Virtual Queue configuration objects:

  • startuploadVirtual Queue configuration objects are all loaded at startup.
  • lazyloadVirtual Queue configuration objects are loaded when they are needed.
  • noload (default)—Virtual Queue configuration objects are not loaded at all.

load-VirtualRoutingPoint

Default Value: noload
Valid Values: startupload, lazyload, noload
Changes Take Effect: After restart
Introduced: 8.5.209.02

Defines when GMS must load Virtual Routing Point configuration objects:

  • startuploadVirtual Routing Point configuration objects are all loaded at startup.
  • lazyloadVirtual Routing Point configuration objects are loaded when they are needed.
  • noload (default)—Virtual Routing Point configuration objects are not loaded at all.

load-Workbins

Default Value: noload
Valid Values: startupload, lazyload, noload
Changes Take Effect: After restart
Introduced: 8.5.209.02

Defines when GMS must load Workbins configuration objects:

  • startuploadWorkbins configuration objects are all loaded at startup.
  • lazyloadWorkbins configuration objects are loaded when they are needed.
  • noload (default)—Workbins configuration objects are not loaded at all.

This page was last edited on May 3, 2019, at 10:11.
Comments or questions about this documentation? Contact us for support!