Application

The Application configuration is used to configure application-level functionality.

It can be used to configure the following:

  • Disable the application, and optionally redirect users who access the disabled application to a specified URL. This is described below.
  • Specify the location of Workspace and Organization Browser help files.
  • Get LDAP attributes that contain binary data when creating and configuring LDAP containers using the Organization Browser.
  • Specify whether or not display names are used for attributes 1-40 when a work list facade is deployed.
  • Specify whether or not the total number of events is retrieved from the server and displayed in the Event Viewer.
  • Specify whether or not the Logout button is displayed.
  • Specify the action taken upon logout.
  • Configure custom callout handlers, which allow you to callout, or inject, custom specifications in WCC applications.

Procedure

  1. In the Configuration Administrator, click config.xml in the left pane.
  2. In the Graphical Editor tab, click in the Application section:
  3. Configure the application using the following fields that appear in the right pane:
    • Disable Application - Checking this box disables the application, making it inaccessible. For more information, see Disabling a Currently Deployed Application.

      Note that the System Administrator can still log into a disabled application—see Accessing a Disabled Application by the System Administrator.

    • Redirect URL - A URL that you would like users who access the disabled application to be redirected.

      If the redirectUrl attribute is set to an empty string, instead of redirecting the user, the message specified in the txtAppDisabled variable is displayed (this variable is located in the ...\JSXAPPS\base\locale\locale.xml file). By default, the txtAppDisabled variable contains the message “This application is disabled.”, but can be changed and/or localized if desired.

    • Help File Locations - The following fields are used to specify the location of help files. By default, the help files are located on the TIBCO Documentation website, https://docs.tibco.com. Some users, however, do not have Internet access. In those situations, the documentation can be downloaded and stored locally, then the path to the documentation can be specified in these fields.
      • Workspace User's Guide URL - This points to the TIBCO Workspace User's Guide. The default value points to the TIBCO ActiveMatrix BPM documentation on the TIBCO Documentation web site. If you have downloaded and stored the help files locally as described in Customizing Location of Help Files, enter the path/URL to the local TIBCO Workspace User's Guide in this field.
      • Organization Browser User's Guide URL - This points to the TIBCO Organization Browser User's Guide. The default value points to the TIBCO ActiveMatrix BPM documentation on the TIBCO Documentation web site. If you have downloaded and stored the help files locally as described in Customizing Location of Help Files, enter the path/URL to the local Organization Browser User's Guide in this field.
    • Get Binary LDAP resource attributes - Checking this box causes LDAP attributes that contain binary data to appear in the LDAP Attributes list on the Organization Browser LDAP Container Editor dialog, as well as when you are mapping LDAP attributes to resource attributes. As the binary data in the LDAP attributes is base-64 encoded, binary LDAP attributes can be mapped to resource attributes of type String.

      Unchecking this box causes LDAP attributes containing binary data to not be displayed.

    • Use facade display names for attributes 1-40 - Checking this box causes “display names” to be shown for custom attributes 1-40 in the client application.

      A work list facade must be deployed to the node. Work list facades are defined using TIBCO Business Studio.

    • Retrieve total count of events in Event Viewer - Checking this box causes the total number of events to be retrieved from the server and displayed in the Event Viewer. This can be used to prevent the counts from being retrieved to improve performance when there are a large number of events.

      If the total count is not retrieved and displayed, the user can still page through the list of events. When the end of the list is reached, a “You have reached the end of the list” message is displayed when the last page is reached.

    • Show the Logout Button - Checking this box causes the Logout button to be displayed in the application. Uncheck this box if you are using single sign on (SSO) authentication (for example, Kerberos). In an SSO implementation using Kerberos, the session is controlled external to the application, therefore the Logout button is not needed.

      Also note that if you are hiding the Logout button in an SSO implementation, you should also ensure that the authenticationMode parameter's mode attribute is set to "useSessionByDefault" so that the existing external session is used, and the Login dialog is not displayed.

    • logoutPath - This controls the action taken when the Logout button is pressed in the application. For details and a list of valid values, see Logout Path.
    • Enable Callout Interfaces - Checking this box allows you to enable and add the classes for each callout handler to implement. For information about callout handlers in general, see the “WCC Public Methods” chapter in the TIBCO Workspace Components Developer Guide. And for more information about configuring callout handlers using the Configuration Administrator, see the “Using Configuration Administrator to Configure Callout Handlers” section in the same chapter.