Methods of Configuration and Customization

The way in which WCC applications are configured and/or customized depends on whether you are configuring/customizing a deployed application or one that is not deployed and is installed in your local development environment.

  • Configuring and Customizing a deployed application - An application that is already deployed on a BPM runtime machine can be configured and/or customized in one of two ways:
    • Using the Configuration Administrator - This is used to configure the deployed application by allowing you to modify configuration settings that are stored in the database on the BPM runtime machine.

      This method of configuration can be used for any WCC application that has been deployed (including the Workspace application).

      For more information, see Using the Configuration Administrator.

    • Directly modifying files on the BPM runtime machine - This method of configuration can only be used for the Workspace application. It cannot be used for a deployed custom WCC application (the specific location in the file system in which the WCC application is deployed is indeterminable—it contains GUIDs determined at deployment time).

      For more information, see Directly Modifying Files on the BPM Runtime Machine.

  • Configuring and customizing a non-deployed application - Configuring and customizing a non-deployed application is done by making changes to the application in your local development environment, either by directly modifying files, or by using TIBCO General Interface Builder. Then after making the desired changes, the application must be deployed to a node.

    This generally falls into two categories:

    • You are creating a new custom application using WCC components.
    • You already have the Workspace application deployed, but you want to make changes to it that are beyond the scope of what you can do via configuration with the Configuration Administrator. In this case, you would make changes to the Workspace application that was installed when TIBCO Business Studio was installed. Then after configuring/customizing it, you must deploy it.

      For more information, see Configuring and Customizing a Non-Deployed Application.