Configuring using FTL

You can configure process monitoring using TIBCO FTL ^®.

Procedure
1. Download the latest FTL driver and install TIBCO FTL®. Refer to the TIBCO FTL® Installation guide for installation instructions. Set the property in bwcommon.tra - tibco.env.FTL_HOME=<FTL_HOME> and install the FTL driver using the bwinstall utility.
   The FTL_HOME path provided should be till the version folder. For example, tibco.env.FTL_HOME=/opt/tibco/ftl/5.4
2. Start the FTL realm server using ./tibrealmserver -ht <IP address>:8080.
3. Run the FTL command, -./tibrealmadmin -rs http://<IP address>:8080 -ur <PATH of bwadmin_ftlrealmserver.json>.
   Two applications are created on the FTL server.
4. Update the following properties in the bwagent_db.json, bwagent_as.json, or bwagent_ftl.json file, based on your BWAgent configuration.
   Set statstransport to FTL

   Set statsdataformat to bytestream

   Set statsprovider to true

   Set dbprovidertype to <db type>

   Set dbproviderdriver to <db provider>

   Set dbproviderconnectionurl to <db connection url>

   Set dbprovideruser to <db user>

   Set dbproviderpassword to <db password>

   Set statsftlrealmserverurl to http://<IP Address>[:port]

   In case of FTL 6.x server in FT mode, set multiple realmserver values separated by pipe. (|).

   For example: bw.agent.technology.dbftl.ftl.realmserver= http://10.97.240.76:8050 | http://10.97.240.76:8051 | http://10.97.240.76:8052

   If any of the configuration settings are different from the default settings, update the following additional properties as applicable.

   statsftlapplicationname

   statsftlsecondaryurl

   This property is only applicable for FTL 5.x. To use this property for FTL 6.x, set the statsftlsecondary to true.

   By default, the statsftlsecondary property is set to false.

   statsftlusername

   statsftluserpassword

   statsftlendpoint

   statsftldataformat

   statsftlinbox
   Run the BWAdmin config command with the -cf option to push the changes from the BWAgent configuration JSON file to the bwagent.ini file.
   To start the BWAgent in the dbems mode

   BW_HOME\bin>bwadmin config -cf ../config/bwagent_db.json agent

   To start the BWAgent in the dbftl mode

   BW_HOME\bin>bwadmin config -cf ../config/bwagent_ftl.json agent

5. Start the BWAgent and create the AppNode(s).
   Ensure the monitor data format property (bw.monitor.data.format=bytestream) and the monitor provider property (bw.monitor.provider=FTL) are present in the AppNode config.ini file and in the bwagent.ini file.
6. Upload and deploy the Application. Start the Application.
7. You can enable process monitoring for any particular application by navigating to the Application Level 2 page, turning the Process Monitor button ON and restarting the Application.
   To enable process monitoring from the CLI, run the following commands:

   bwadmin[admin]> enablestats -d domain -a appspace processinstance b1.application 1.0
   TIBCO-BW-ADMIN-300413: Enabled statistics collection for Application [b1.application:1.0].
   
   bwadmin[admin]> enablestats -d domain -a appspace activityinstance b1.application 1.0
   TIBCO-BW-ADMIN-300413: Enabled statistics collection for Application [b1.application:1.0].

   Alternatively, you can run the single command as follows:

   bwadmin[admin]> enablestats -d domain -a appspace processmonitor b1.application 1.0
   TIBCO-BW-ADMIN-300413: Enabled statistics collection for Application [b1.application:1.0].

8. Navigate to Application Level 2 > Processes > Graph View > Process Instance.
   Alternatively, you can also use the shortcut key Shift + P from the Application Level 2 Page to open the Process Monitoring landing Page directly.