Jump to: navigation, search

Creating GRAT Application Objects in Configuration Manager


Purpose

  • To create the Application objects in Configuration Manager that will link the GRAT with Configuration Server. The GRAT requires two applications in Configuration Server: a server application and a client application.

Start

  1. In Configuration Manager, navigate to the Application Templates folder.
  2. Import the application template that is to be used for the server 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.1, select Genesys_Rules_Authoring_Server_811.apd.
  • For Management Framework 8.1 and earlier, select Genesys_Rules_Authoring_Generic_Server_811.apd.
  • Click OK to save the template.
  • Import the template that is to be used for the client 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 Genesys_Rules_Authoring_Generic_Client_810.apd.
    3. Click OK to save the template.
  • Configure the server application:
    1. Right-click the Applications folder and select New > Application.
    2. Select the Genesys_Rules_Authoring_Generic_Server template.
    3. On the General tab, enter a name for the application, such as Rules_Authoring_Server.
    4. On the Tenants tab, add the Tenants that will be visible in the GRAT interface.
    5. On the Server Info tab, select the Host on which the application will be installed, and configure a default listening port.
    6. On the Start Info tab, enter x for each field. This is required in order to save the configuration.
    7. On the Connections tab, add a connection to the Rules Engine application (multiple Rules Engine applications can be added).

    8. Important
      The Port ID selected for a Rules Engine connection should be the name of the Rules Engine Web application. Optionally, a connection to an application cluster of Rule Engines may be added.
    9. On the Options tab, configure log options.
    10. In the settings section, the following options can be configured:
    • session-timeout - Specifies the amount of time (in minutes) a client session can have no communication with the Rules Authoring Server before timing out. If no value is specified, the timeout (if any) defined by the application server applies. If the value is less than or equal to 0, the session will not timeout. The default value is 30.
    • session-timeout-alert-interval - The amount of time (in minutes) prior to an expected timeout for a user to be warned of a pending timeout. If no value is specified, or if the value is less than or equal to 0, the default warning period of 1 minute will be used. For example, if you set the value of this option to 3, the user will be warned 3 minutes prior to an expected timeout. This warning dialog will prompt the user to extend the session. If the session is not extended, the user will be logged out and the login dialog will be displayed. Any unsaved changes that the user made during their session will be lost.
    • verify-deploy-address - Indicates whether to verify that the TCP address of the application that is requesting the deployment of a package is that of an associated GRE. The default value is true.
    • group-by-level - The default value is true. When this option is true, rules are grouped by business level:All global rules belong to agenda group "level"?.Department rules belong to agenda group "level1".Process rules belong to agenda group "level2".When a rule package is executed, "level"? rules are executed first, facts are marked as updated, and "level1" rules are executed. This process is repeated for each level. Note that when group-by-level is true, the GRE option sequential-mode must be set to false.
    • strict-mode - Specifies whether the GRAT enables "strict mode" in the DROOLS rule compiler. Enabling this option causes the compiler to catch common mistakes when the rule author attempts to validate or save a rule. The default value is true.
    • max-connections - Specifies the maximum number of different users that can be connected to the server. Multiple connections from the same user id are only counted once. The default value is 99.
    • From release 8.1.3: display-n-template-versions - Integer value specifying the maximum number of versions to display for any published template. The minimum value is 1 and the default value is 3.
    • From release 8.1.3: deploy-response-timeout - Integer value specifying timeout applied to the deployment of a rule package. This option does not appear by default in the application template. The default value is 300 seconds.
    • From release 8.1.3: require-checkin-comment - Specifies whether users must add a specify a check-in comment when committing changes to rules. These comments show up when viewing package history. If the value is set to false (default), users can save changes to rules without specifying a comment.
    • From release 8.1.3: force-snapshot-on-deployment - Specifies whether users can deploy only a package snapshot. If the vlaue is true, users can only deploy a package snapshot. If false (default), users can deploy either the LATEST package or a snapshot.
  • Give the application Read, Create, and Change permissions on the Scripts folder for each Tenant that you add. (One approach is to create a user called GRAT_Application_Proxy and add that user to the SYSTEM access group. Then, on the Security tab of the application, in the Log On As section, select This account and add the GRAT_Application_Proxy user.)
  • Click Save.
  • Configure the client application:
    1. Right-click the Applications folder and select New > Application.
    2. Select the Genesys_Rules_Authoring_Generic_Client template.
    3. On the General tab, enter a name for the application, such as Rules_Authoring_Client.
    4. Click Save.

    End

    Next Steps

    This page was last modified on June 19, 2013, at 04:11.

    Feedback

    Comment on this article:

    blog comments powered by Disqus