Using Database/FTL as a Transport: (Option 3)

Using the Database/FTL option, you can use an external database for data persistence and TIBCO FTL for the communication transport layer.

Procedure

  1. In Environment Type, ensure that Enterprise is selected.
  2. See that the Create Domain, AppSpace, AppNode option is selected.
  3. In Domain data persistence and communication transport layer, select Database/FTL as the messaging transport.
    Environment Configuration
  4. Make sure that the Register Enterprise server with TEA server option is selected.

    TIBCO Enterprise Administrator (TEA) server provides an Administrator UI which can be used to create, view, and monitor runtime entities. The bwagent interacts with the TIBCO Enterprise Administrator server through a TEA agent. Only one TEA agent can be registered with a bwagent at a time. When the TEA agent is registered with bwagent, the bwagent is displayed in the Administrator UI. Using Administrator UI, you can manage and monitor runtime entities and perform almost all bwadmin administrative tasks.

  5. Ensure that the Use a Dependent TEA Server option is selected.

    Selecting this option creates a TEA component for TIBCO Silver Fabric Enabler for TIBCO Enterprise Administrator and also sets the dependency of BusinessWorks component on the TEA component. TIBCO BusinessWorks component then acquires the URL of TEA server and automatically registers to the TEA server.

    If the option is not selected, you need to first setup and start a TEA server manually and then provide the URL of the running TEA server in the TIBCO TEA Server Configuration page in the BusinessWorks component creation wizard.

    Tip: Make sure that you take advantage of the automatic registration and administrative features provided by TIBCO Silver® Fabric Enabler for TIBCO® Enterprise Administrator.

    When the component bwagent is set to run in the server agent role, select the check boxes Register Enterprise Server with TEA Server and Use a Dependent TEA Server to leverage the features provided by TIBCO® Enterprise Administrator (TEA). Add a TEA component to your BusinessWorks stack and add a TEA server dependency to your BW server component. Refer to the TIBCO Silver Fabric Enabler for TIBCO Enterprise Administrator documentation for more information.

  6. Select the Engine Persistence mode from the drop down.
    • Memory This is the default mode and does not require any special configuration.
    • Datastore If you select this mode, then you need to provide the database configuration on the Database Configuration for The Engine Persistence Mode page that appears.
      Database Configuration for The Engine Persistence Mode

      There are two Database Connection Configuration levels:

      AppSpace and AppNode Levels.For more information refer Specifying the Domain, AppSpace, AppNode, and APPNode HttpPort Base Configuration.
    • Group The Group mode displays The group provider technology for the engine property in the Environment Configuration page. For more information refer Group Provider Technology for the Engine .
    • FTGroup The database is not needed when the Engine Persistence mode is FTGroup. Also The FTGroup mode displays The group provider technology for the engine property in the Environment Configuration page. For more information refer Engine Persistence mode FTGroup .
  7. Specify The engine group name (Group_[DomainName]_[AppSpaceName]) property. This is an optional property and it specifies name of the BusinessWorks engine group. If this property is not specified, then the group name defaults to "Group_<DomainName>_<AppSpaceName>"
  8. Click Next.