Copyright © 2013 TIBCO Software Inc. All Rights Reserved


Chapter 2 Creating a TIBCO Silver Fabric Enabler for ActiveMatrix BPM Stack : Creating a TIBCO ActiveMatrix BPM Runtime Component

Creating a TIBCO ActiveMatrix BPM Runtime Component
The TIBCO ActiveMatrix BPM Runtime is the runtime component used to start the TIBCO Host instance.
Each TIBCO ActiveMatrix BPM Runtime Component requires a component dependency on a TIBCO ActiveMatrix BPM Server Component.
The ActiveMatrix BPM Runtime Component will automate the following tasks:
Each ActiveMatrix BPM Runtime Component can start only one runtime instance per Silver Fabric engine.
To get more ActiveMatrix BPM Runtime instances on the same engine you can copy and replicate the ActiveMatrix BPM Runtime Component with some changes to name and deployment directory path.
Create a TIBCO ActiveMatrix BPM Runtime Component
1.
2.
Select "Create New TIBCO AMX BPM Runtime Component" from the Global Actions menu.
3.
4.
Figure 24 Choose the TIBCO ActiveMatrix Product Distribution Version
By default, the latest versions of the distributions are displayed. All versions of the distributions are compatible.
5.
Deployment Directory - Defines the relative directory where the TIBCO ActiveMatrix Runtime Host will be installed on the Silver Fabric Engine.
Default deployment directory is:
   DSENGINE_HOME/work/[COMPONENT_NAME]
Figure 25 Basic Configuration
TIBCO Host Communicates with a Server that is SSL Enabled - if you want your ActiveMatrix BPM Component to use SSL to communicate with the ActiveMatrix BPM Admin Server then check the box and the SSL Configuration page will be displayed later on in this Wizard. Click Next to save your changes.
Customize JVM Size - Check this box and the Sizing Details Configuration page will be displayed by the ActiveMatrix BPM Runtime Component Wizard.
Figure 26 Sizing Details Configuration
The Environment field is simply a label for this configuration page. Switching between Production to Development does not change the other values on this page.
The default values are production environment default values which can be changed individually. For an explanation of what each property controls refer to the ActiveMatrix BPM: Sizing Configuration page.
6.
Every ActiveMatrix BPM Runtime Component creates a host and node environment ready to run applications. This page gives you control over what type of node you create. Your Runtime Component can be a BPM Node Type, a Processor Manager, a Web Manager, or a Web Components Node Type.
Figure 27 Host and Node Configuration
Node Type - The ActiveMatrix BPM documentation perfectly describes the different node types and how they can be used to your advantage. Refer to TIBCO ActiveMatrix BPM Architecture for a great overview of node contents.
Node Name - Node Port - give you node a unique name and port on which to communicate. Avoid assigning the same port to another Runtime Component identical applications messaging on the same port might cause conflicts.
Host - Define a unique name for the individual ActiveMatrix BPM Runtime Host, so that the ActiveMatrix BPM environments can have even more logical separation when your Components are running side by side.
HTTP Port - Define a unique port for each Runtime Node to avoid conflicts.
 
7.
Figure 28 SSL Configuration
SSL Configuration is required if you have checked the use SSL checkbox. The Trust Store file must be uploaded for use with a valid password or the component will fail to establish a proper connection.
If the TIBCO ActiveMatrix BPM Server is using a certificate to secure communications then that certificate has to be added to the Runtime Server’s Trust Store.
8.
Log output directories may be added with paths that are relative to the engine instance work directory (work/host-instance). Path names can contain references to runtime context variables in the form ${variable_name}.
Figure 29 Adding a Log File Pattern
 
The filename can be a regular expression, using conventions defined in javadoc for java.util.regex.Pattern. The rest of the path cannot be a regular expression.
Use a forward slash (/) for the directory separator character.
Log file patterns may also be removed by selecting the directory pattern first and then clicking the Remove button.
If you remove log file patterns, they will not be restored by the Add Defaults button. You can add them back manually at any time.
9.
String, Environment, System, or Encrypted variables may be added and edited to the ActiveMatrix BPM Runtime Component to define and set runtime context variables.
Select a variable type from the Add Variable pull-down list or Add from Container to use a variable from a selected container.
Variable values from a container may be added to the runtime as well. Use the Add from Container button to add container-specific context variables.
Figure 30 Edit Runtime Variables
Runtime context variables may be changed by selecting the variable (selected row is highlighted) and clicking Edit to change its attributes. Selected rows may also be removed.
Component Dependency Requirements
The TIBCO ActiveMatrix BPM Runtime Component is dependent on the TIBCO ActiveMatrix BPM Server Component and the ActiveMatrix BPM Server component is dependent on an instance of EMS and the database. These dependencies must be set. A Component dependency may be set from the Stack definition, see After initially defining a Stack, you can still update it by adding or removing BPM Components and configuring other properties of the Stack., or you can set it directly on the Component definition as is described here.
To set the Component dependency:
1.
Or instead of using the Menu task list, you could step through the Component Wizard until you reach the page that allows you to "Change the allocation rules that are used by default when adding this Component to a Policy (including by activation in Dynamic Policy Mode)." selection link.
2.
Figure 31 Setting a Component Dependency
3.
4.
Shutdown Dependency - Uncheck the Shutdown Dependency checkbox when you want the TIBCO Hosts to continue running even if contact with the ActiveMatrix BPM Administrator is lost.
5.
Ordered Shutdown should always be checked to provide for proper clean-up of allocated resources.
6.
Restart Component for new rules should use the default setting.
Complete the wizard by accepting the defaults on the remaining screens.

Copyright © 2013 TIBCO Software Inc. All Rights Reserved