Override auto logout resource

The JGAS configuration file (as.xcf) provides default configurations for resources that applications use, but you can also override resources, such as the auto logout. You can do this globally at runtime from the user interface.

Before you begin:
It is assumed the applications deployed in the war are configured to reference the app.timeout.autologout resource as shown:
<AUTO_LOGOUT>
      <TIMEOUT>$(app.timeout.autologout)</TIMEOUT>
</AUTO_LOGOUT>
  1. Run the application on your Java Enterprise Edition (J2EE) server.
    1. Deploy the war file using your J2EE server tool or deployment portal interface.
    2. Use the link or URL created to access the applications deployed in the war file.
      Tip:

      The base URL in the context of the J2EE server is http://server:port/war_file_name. If you type the base URL in a browser, you get the JGAS user interface home page where you can then access all applications and services published in your war file. For more information on the JGAS user interface, go to JGAS home page.

    3. Select the application to run.
  2. From the home page, open the Resources Global page by clicking on the Edit configuration button opposite Global Settings.
    The Resources Global page opens. See JGAS global resources page.
  3. In the key field enter the name of the auto logout resource.

    app.timeout.autologout

    Tip:

    You can see the current setting of the app.timeout.autologout resource under the Configuration dump heading in the Resources page for an application, see JGAS application resources page.

  4. In the value field enter a valid timeout setting in seconds, for example, "80" and click the Add button.
    The new key and value is displayed under the Name and Value columns at the top of the page.
  5. To apply the change click on the Update button.
    Important:

    Even though the resources have been updated, the configuration is not yet activated. The configuration must be reloaded on the home page. If the application is already started, it continues with its original configuration.

  6. To reload the configuration, click on the Return to the index button at the top of the page to open the home page.
  7. Configuration updated icons and an Apply changes buttons are displayed opposite each application name, to show that configurations have changed, and need to be applied.
    To apply the changes, click on the Apply changes button.
    Figure: Configuration update icons

    Image shows configuration icons that are displayed opposite an application when configurations have changed, and need to be applied.
  8. Select OK in the application reload pop-up window.
    Figure: Reload Configuration pop-up page

    Images shows example of the JGAS reload configuration pop-up page
    Run your application to check that the auto-logout changes are taking effect. In the console output, you should see that the application times out after the specified period of inactivity on the application.
    Note:

    If you redeploy the updated war file, the customized resources are reapplied, as long as the war filename is not changed. If the war file is deployed to a different server, customized resource settings need to be reapplied.