Directly Modifying Files on the BPM Runtime Machine

You can also configure and customize a deployed Workspace application by directly modifying the files on the BPM runtime machine.

For information about the location of the files you can modify, see Location of Files on a BPM Runtime Machine.

Note, however, that you cannot directly modify the files in a custom WCC application that has been deployed because the specific location in the file system in which the WCC application is deployed is indeterminable—it contains GUIDs determined at deployment time. To configure or customize a custom WCC application beyond the scope of what can be done with the Configuration Administrator, you can make the desired changes in your local WCC development environment, then re-deploy the application.

Using this method, you can perform the following types of configurations and customizations:

  • Configuration changes - You can make changes directly to configuration files on the BPM runtime file system (as opposed to using the Configuration Administrator to make database changes for deployed applications). The configuration files that can be modified are:
    • config.xml - This file contains a variety of configuration parameters, such as default user options, specifying the session timeout value, etc. All of the configuration parameters available in the config.xml file are described in Configuring the Application.
    • userAccess.xml - This file is used to specify which functions users can access in the application, based on the privileges held by the user. For information about configuring user access, see Configuring User Access.
    • eventRoles.xml - This file is used to map privileges to event roles; event roles are used to configure events differently based on a user’s privileges. For more information, see Mapping Privileges to Event Roles.

      Note - There are also some configuration files in the \JSXAPPS\base\locale\ directory that specify how events are displayed in the application. For information about these configuration files, see Configuring Events.

    • customInterfaces.xml - This file is used to configure custom interfaces that allow custom menus and toolbar buttons to be displayed in a WCC application that, when selected, display TIBCO General Interface prototypes, web pages displayed in iFrames, or web pages displayed in TIBCO PageBus Managed Hub iFrames. For more information, see Custom Interfaces.
    • wccConfig.xml - This file is used to specify things such as whether or not to load previously loaded resources when loading the application in General Interface Builder. For more information, see WCC Configuration File.
      Note: If you are manually modifying files on the BPM runtime machine, and they are files that are accessible from the Configuration Administrator (such as config.xml and userAccess.xml), you must have an understanding of which files the application is going to use—those in the file system, or those in the database. For information about this, see Configuration Administrator Writes Files to the Database .
  • Code-level changes - Custom code can be added to perform whatever business logic is required. This requires that you open and modify files on the BPM runtime machine to implement the custom logic desired. Note that code changes should not be made to the ...\JSXAPPS\base\base.js file, as this is TIBCO’s private implementation of the WCC components—it is crunched and obfuscated.

    For information about custom code entry points, see the “Building Custom Applications” chapter in the TIBCO Workspace Components Developer Guide.

  • Other Customizations - There are other various customizations you can perform, such as changing fonts, colors, and images in the application, localizing the application, adding custom menus and toolbar buttons, etc.

    For information about these customizations, see Customizations.

Prior to making changes directly in the files on the BPM runtime machine, you should ensure that all users have logged out of all TIBCO BPM applications, then stop the BPM node. After making changes and restarting the BPM node, you should also clear the browser cache before logging back into TIBCO BPM applications.