Before deploying a TIBCO BusinessEvents project, you configure an enterprise archive resource (EAR) file for your BusinessEvents project within TIBCO Designer, and, as needed, you configure deploytime properties.Read Chapter 26, Deploytime Configuration to understand the deploytime configuration tasks, and Configuring to Run in a TIBCO Administrator Domain for the property configuration procedure.This section discusses deployment using TIBCO Administrator. For information about running a BusinessEvents application at the command line, see Deploying a Project Outside a TIBCO Administrator Domain.You can configure your BusinessEvents engine to allow you to replace the EAR file without shutting down the engine. This is known as a hot deployment. See Configuring and Using Hot Deployment.
Rule Session (Agent) Configuration Options When you deploy a BusinessEvents EAR file, all the separate BAR files within it are merged.
1. As needed, ensure that all the following are started on the machine whose engine properties you want to change:
− Windows: Start > Programs > TIBCO > TIBCO Administrator Enterprise Edition version > TIBCO Administrator
− Web browser: http://host-name:port/ (where host-name is the machine name and port is the HTTP port specified during installation, 8080 by default)
3. Select the administration domain for the application and provide the username and password assigned during installation, or other administrator user credentials.
a. Click Application Management (in the left panel).
b. Click the New Application button.
c.
d. At the New Application Configuration dialog, set the Application Parameters and Services settings as desired (click Help for details) and click Save. By default, Name is set to the EAR file name and Deployment Name is set to the EAR file name prepended with the domain name.
5. Setting Engine Properties
6. As desired, in the Configuration Builder panel, click the merged BAR name (application_name.bar) and select the Advanced tab. Set properties as desired. See Configuring to Run in a TIBCO Administrator Domain for a more detailed procedure and references to related sections, especially Customizing the List of Properties on the Advanced Tab. Click Save.
When you deploy the BusinessEvents engine using TIBCO Administrator, the property values set on the Advanced tab override values set for the same properties in the engine property (TRA) file.
7. As desired, in the Configuration Builder panel, click the application name and set values in the Advanced tab, for example, for global variables. Click Save.
8. As desired, select the machines in the administration domain to which you will deploy the application: In the Configuration Builder panel, click the application name. In the General tab, Target Machines panel, the current machine is available by default.
9. As desired, select Add to Additional Machines to deploy the application to multiple machines. Select the machines to which you will deploy. You can also select the same machine more than one time, if you want to deploy the application more than once on a machine.Fault Tolerance Settings —for In Memory OM Only
10. Fault tolerance features appear in the FT Group Setting pane when you select multiple machines. If you are configuring BusinessEvents engines as a fault tolerant group, available only for In Memory object management, do the following:The higher the number, the higher priority of the server. The primary engine has the highest priority (that is, the number with the largest value, when configuring using TIBCO Administrator). Secondary engines have lower priorities (and values closer to 1).See Chapter 15, Configuring In Memory Object Management for more configuration details.
If you give two or more engines the same priority value, then the actual priority is determined by join (server startup) time. The engine that joined the cluster first has the highest priority.
b. In the FT Group Settings pane, check the Run Fault Tolerant checkbox.
BusinessEvents does not use these TIBCO Administrator fault tolerance settings. They appear in the engine property file generated by TIBCO Administrator (see Location of TIBCO Administrator-Generated Property File), with the property names shown in parentheses:
● Heartbeat Interval (Engine.FT.HeartbeatInterval)
● Activation Interval (Engine.FT.ActivationInterval)
● Activation Delay. (Engine.FT.ActivationDelay)The above settings are relevant only whenTIBCO Rendezvous is used for fault tolerance. BusinessEvents fault tolerance for In Memory object management is managed by the object management layer, not by Rendezvous. See Chapter 15, Configuring In Memory Object Management for more details.
11. Click Save.
12.
14. Check the Show deployed configuration checkbox to display the Deployed Configuration panel and verify success:
Copyright © TIBCO Software Inc. All Rights Reserved.