Jump to: navigation, search

Creating the GRE Application Object in Configuration Manager


  • To create the Application object in Configuration Manager that will link the GRE with Configuration Server.


  1. In Configuration Manager, navigate to the Application Templates folder.
  2. Import the application template that is to be used for the Rules Engine application:
    1. Right-click the Application Templates folder and select Import Application Template.
    2. Browse to the templates folder of the installation CD, and select the appropriate template for your version of Management Framework:
      • For Management Framework 8.1, select Genesys_Rules_Engine.apd.
      • For Management Framework 8.0 and earlier, select Genesys_Rules_Engine_Generic_Server.apd.
    3. Click OK to save the template.
  3. Configure the application:
    1. Right-click the Applications folder and select New > Application.
    2. Select the template that you imported in the previous step.
    3. On the General tab, enter a name for the application, such as Rules_Engine.
    4. On the Tenants tab, add the Tenants that will be available to the Rules Engine.
    5. On the Server Info tab, select the Host on which the application will be installed.
    6. Add a default listening port.
    7. Add an additional port. This port is the connector port on which the Rules Engine Servlet receives requests:
      • The ID value is the name of the Rules Engine web application. The default name of this application is "genesys-rules-engine".
      • The Listening port is the connector port of the Servlet Container. For example, on Tomcat the default listening port is 8080.
      • The Connection Protocol must be http.
    8. On the Start Info tab, enter x for each field. These fields are not used, but you must enter some text there in order to save the configuration.
    9. On the Options tab, configure options. Logging options can be configured, and there are several optional configuration options in the settings section:
      • verify-deploy-address indicates whether to verify that the TCP address of the application that is deploying rules is that of an associated Genesys Rules Authoring Tool. The default value is true.
      • sequential-mode specifies whether to run the GRE in sequential mode. In sequential mode, no additional data can be inserted or modified after the initial data set, simplifying the GRE operations. The default value is false.
      • max-number-rule-executions specifies the maximum number of rules to be executed during a request. This option is used to detect unwanted recursions when sequential-mode is false. Once the maximum is reached, an error is reported. The default value is 10000.
      • deployed-rules-directory (which, before 8.1.3, must be manually added if you want to assign it a value) specifies the directory in which to keep the working copy of deployed rule packages. When a package is deployed, a copy of the deployed package is placed here. When the GRE is restarted, all packages that are defined in this directory are loaded and made available for execution. Specifying a deployed-rules-directory is recommended. If a value is not assigned to the deployed-rules-directory, the rule packages are placed in the WEB-INF\config sub-directory within the genesys-rules-engine web application directory. At this location the deployed rule packages may be deleted when an updated .war file is deployed.
      In release 8.1.3, the deployed-rules-directory option has been added to the application template. The default value is /GCTI/logs/GRS_Engine. If you choose to change its value to a more appropriate path, ensure that the path exists and that the application server can write to the specified directory.
      • esp-worker-threads (new in release 8.1.2), specifies the maximum number of worker threads available when using the ESP interface to execute rules. The default for this value is 5 threads.
    10. Click Save.


Next Steps

This page was last modified on June 19, 2013, at 03:14.


Comment on this article:

blog comments powered by Disqus