Configuring TIBCO FTL® as the FTGroup Provider for Engine

Follow these steps to configure the engine for ftgroup persistence mode, and to set TIBCO FTL as the group provider technology.

Note: Use of TIBCO FTL with TIBCO ActiveMatrix BusinessWorks™ for configuring bwagent and for configuring group provider for engine does not require TIBCO FTL licenses.

Prerequisites

  • See the ActiveMatrix BusinessWorks™ readme for the version of TIBCO FTL that is supported with the version of ActiveMatrix BusinessWorks 6.x you are using.
  • Ensure you have installed FTL client libraries. For more information, see "Integrating with TIBCO FTL" in the TIBCO ActiveMatrix BusinessWorks™ Installation guide.
  • These steps are only applicable if you are not using TIBCO FTL as the bwagent transport.

  • If you are installing TIBCO FTL after you have already installed ActiveMatrix BusinessWorks, set the tibco.env.FTL_HOME variable in the bwcommon.tra file. You can find this file in the bin folder at BW_HOME\bin for Windows, or ${BW_HOME}/bin for Unix.

  1. Install TIBCO FTL. For instructions, see the TIBCO FTL® Installation guide.
  2. Start the FTL Realm server by executing the ./tibrealmserver -ht <hostIP>:<port> FTL command. 
    ./tibrealmserver -ht <hostIP>:<port>
  3. Execute the following FTL command to populate data in the bwadmin_ftlrealmserver.json template file, located in the config folder at BW_HOME/config: 
     ./tibrealmadmin -rs <realmserverurl> -ur <PATH of bwadmin_ftl_realmserver.json>
Note: For instructions about how to configure an FTL backup server for high availability, see "Configuring Backup Realm Servers for Fault Tolerance" in the TIBCO FTL® Administration guide .

Procedure

  1. Set engine persistence mode property (bw.engine.persistenceMode) to ftgroup and configure the engine group configuration.
    1. Copy the existing AppSpace config.ini template file appspace_config.ini_template (located in BW_HOME/config ) to the root of the AppSpace folder, or a temporary location, and rename the file as config.ini.
    2. Edit the ActiveMatrix BusinessWorks™ engine persistence mode property, bw.engine.persistenceMode, and set it to ftgroup. 
      bw.engine.persistenceMode=ftgroup
    3. Specify the group name and group provider technology as ftl in the config.ini file. The group name is mandatory. 
      # ------------------------------------------------------------------------------
# Section:  BW Engine Group Configuration.  
# 
# The properties in this section are applicable to the BW Engine group.
# Some of the properties in this section are required when the BW Engine 
# property "bw.engine.persistenceMode" is set to "ftgroup". 
# ------------------------------------------------------------------------------
# BW Engine Group Name.  This is a reqired property and it specifies name of 
# the BW engine group.  If this property is not specified, then the ftgroup name 
# defaults to "Group_<DomainName>_<AppSpaceName>". 
#bw.engine.groupName=mytestgroup

# BW Engine Group Connection Provider Technology.  This is a required property  
# when the persistenceMode is set to "ftgroup" (bw.engine.persistenceMode=group)  
# and it specifies the BW Engine group communication technology.  The only  
# supported values are "ems" and "ftl". The group connection provider technology property  
# requires additional configuration. See section "Configuring the Engine for Group Persistence Mode" 
# for additional configuration.  
bw.engine.groupProvider.technology=ftl
    4. Specify the group provider configuration: 
      # ------------------------------------------------------------------------------
# Section:  BW Engine Group Connection Provider FTL Configuration.
#
# Some of the properties in this section are required when the BW Engine Group 
# Connection Provider Technology property  "bw.engine.groupProvider.technology"  
# value is set to "ftl"
# ------------------------------------------------------------------------------
# BW Engine Group Connection Provider FTL Realm Server.  This property is required if  
# the group provider technology is "ftl".
bw.engine.groupProvider.ftl.realmserver=http://localhost:8080

# BW Engine Group Connection Provider FTL Realm client user name
# This property is required if the group provider technology is "ftl".
bw.engine.groupProvider.ftl.username=

# BW Engine Group Connection Provider FTL Realm client password
# This property is required if the group provider technology is "ftl".
bw.engine.groupProvider.ftl.password=

# BW Engine Group Connection Provider FTL application identifier
# This property is required if the group provider technology is "ftl".
bw.engine.groupProvider.ftl.appinstance.id=

# BW Engine Group Connection Provider FTL secondary realm server
# This property is optional.
#bw.engine.groupProvider.ftl.secondaryserver=

# BW Engine Group Connection Provider FTL group name
# This property is required if the group provider technology is "ftl".
bw.engine.groupProvider.ftl.groupname=

# BW Engine Group Connection Provider FTL application name
# This property is required if the group provider technology is "ftl".
bw.engine.groupProvider.ftl.appname=

# BW Engine Group Connection Provider FTL publish endpoint
# This property is required if the group provider technology is "ftl".
bw.engine.groupProvider.ftl.publish.endpoint=

# BW Engine Group Connection Provider FTL application name
# This property is required if the group provider technology is "ftl".
bw.engine.groupProvider.ftl.subscribe.endpoint=
      When setting the password property (bw.engine.groupProvider.ftl.password), the default format is plain text. Execute the command bwadmin obfuscate, or the command bwobfuscator, from the command line to encrypt the password; use the generated encrypted text as the password.
  2. Optional. If you have saved the config.ini file to a temporary location, ensure you copy it to the AppSpace root folder located in BW_HOME/domains/defaultdomain/appspaces/defaultappspace.
  3. Use the config admin command to push the configuration to the AppSpace: bwadmin[admin] > config -d myDomain -a myAppSpace -cf <temporaryLocation>/config.ini.