Copyright © 2013 Cloud Software Group, Inc. All Rights Reserved |
1. In TIBCO Silver Fabric Administrator GUI, select Stacks > Components.
2.
4. Select the TIBCO ActiveMatrix Product Distribution version you want to publish to the cloud. The TIBCO ActiveMatrix BPM Distribution versions available for selection will be those you installed in TIBCO Silver Fabric SILVERFABRIC_HOME gridlib directory. Your version may be more recent than what is pictured here.Deployment Directory - Defines the relative directory where the TIBCO ActiveMatrix Runtime Host will be installed on the Silver Fabric Engine.
Figure 25 Basic ConfigurationTIBCO 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 ConfigurationThe 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.Figure 27 Host and Node ConfigurationNode 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.Figure 28 SSL ConfigurationFigure 29 Adding a Log File Pattern
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.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 VariablesRuntime 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.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.Figure 31 Setting a Component Dependency
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.
Copyright © 2013 Cloud Software Group, Inc. All Rights Reserved |