Using Database/EMS as a Transport (Option 2)

Using the Database/EMS option, you can use an external database for data persistence and TIBCO Enterprise Message Service (EMS) for the communication transport layer.

1. In Environment Type, ensure that Enterprise option is selected.
2. See that the Create Domain, AppSpace, AppNode option is selected.
3. Specify the AppNode Shutting Down Timeout. By using this option you can specify the timeout in minutes after which the AppNode shuts down forcefully, irrespective of the state of the AppNode or the applications. The default value is '0'.
4. For Domain data persistence and communication transport layer, select Database/EMS as the messaging transport.
   Environment Configuration

   
5. Ensure that the Register Enterprise server with TEA server option is selected.

   The TIBCO Enterprise Administrator (TEA) server provides an Administrator UI 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. From Administrator UI, you can manage and monitor runtime entities and perform almost all bwadmin administrative tasks.

6. 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 must first set up 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.

7. 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 must 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.
8. To track the current state of the job on the node, select Enable OpenTracing on This Node.

   A trace represents multiple process instance spans that are related. A span is a process instance or an activity instance that has information such as ActivityName, JobID, and process instance ID.​​

9. Select Clean the config folder every time the AppNode starts. By default, the config folder is not deleted whenever the AppNode starts.
   When the AppNode is not gracefully shut down, it can corrupt the config folder. Selecting this option creates a new config folder every time the AppNode starts.
10. To obfuscate the FTL password in the bwagent.ini file, select Enable to obfuscate FTL passwords in bwagent.ini file.
11. Specify The engine group name (Group_[DomainName]_[AppSpaceName]) property. This is an optional property that specifies the name of the BusinessWorks engine group. If this property is not specified, then the group name defaults to "Group_<DomainName>_<AppSpaceName>"
12. Click Next. See Group Provider Technology for the Engine for the next steps.