Starting the asg-engine Configuration to Support Quota Notification

A notification occurs when the usage for a particular application reaches a limit set for a specified environment.

To support quota throttle notification, start each engine in the portal environment using the -n parameter in the asg-engine command, for example: 
asg-engine.exe -n EngineName

where EngineName specifies a unique engine name.

Configuring API Exchange Gateway and ASG Configuration Using Embedded Config UI

Procedure

  1. Log in to the Config UI.
    By default, the Configu UI copies the BookQueryBE project to the environment configuration folder. To specify the configuration that the Gateway is in the cluster environment and is running, modify the java.property.com.tibco.asg.designtime.configui.portal.master property in the asg-configui.tra file.
  2. Start the Config UI.
  3. Click Advanced Settings.
  4. Click the Page tab next to the Environment drop down menu.
    This will turn the drop down menu into a text box.
  5. Type the environment name, for example, 'Production Environment' and press Enter.
    This will bring up a new drop down menu, called the Cluster.
  6. Select the Page tab next to the Cluster drop down option.
    This will bring up a pop-up window.
  7. Select the Page tab next to the Cluster drop down option.
    The drop-down will now appear as a text box.
  8. Type the name of the cluster, for example, "Cluster 1".
  9. In the Engine URL field, type the http:\\localhost:9222 Gateway URL and click Save.
    The Cluster Saved Successfully pop-up window will appear.
  10. Select the environment created from the Environment drop down menu.
  11. Select the cluster created from the Cluster drop down option.
  12. Edit the configuration and make the necessary changes.
    When you overwrite the configuration name, an U icon will appear, which will update the Gateway with the changes made.