The node deploy configuration file is used to define deployment-time values, and to also override, and possibly augment, default application configuration. Deployment time configuration can be specified for multiple nodes in a single node deploy configuration file. The nodes can be in the same or different clusters. The node configuration to use from the node deploy configuration file when installing a node is determined by matching the node name being installed with a node name in the node deploy configuration file. This is shown in Example 3.1, “Node configuration selection”.
Example 3.1. Node configuration selection
name = "my.application"
version = "1.0.0"
type = "com.tibco.ep.dtm.configuration.node"
configuration =
{
NodeDeploy
{
//
// Define a cluster X with three nodes
//
nodes =
{
//
// Node A.X configuration
//
"A.X" = { }
//
// Node B.X configuration
//
"B.X" = { }
//
// Node C.X configuration
//
"C.X" = { }
}
}
}
//
// Install node A.x - use A.X node configuration in nodedeploy.conf
//
epadmin install node --nodename=A.X ... --nodedeploy=nodedeploy.confNode deployment configuration files can be specified on the
install node command line, or they can be packaged
in an application archive. Packing a node deployment configuration in
an application archive provides an easy mechanism to ship application
specific default node deploy configuration values.
In addition to the configuration data defined in a node deploy configuration file, the node deploy configuration can also contain arbitrary configuration. There are two sections in the node deploy configuration file for this configuration:
global - applies to all nodes defined in the node deployment configuration file. See the section called “NodeDeploy” for details.
per-node - applies to a specific node in the node deployment configuration file. See the section called “Node” for details.
Configuration files can also be contained in the fragments in an application archive and in the application itself.
See the section called “Overriding and augmenting default application and node configuration” for details on configuration load order.
The node deploy configuration is audited whenever it changes state, e.g. load to active. There are detailed audits for each of the configuration objects in the node deploy configuration file. These are described in the section called “Configuration objects”. There are also these audits enforced on node deploy configuration during application installation.
Node deploy configuration can only be contained in an application archive. Node deploy configurations cannot be contained in fragment archives. Node deploy configurations found in a fragment archive will cause an audit failure during application installation.
There can only be a single node deploy configuration in an application archive. Multiple node deploy configurations in an application archive will cause an audit failure during application installation.
All node deploy configurations loaded when a node is installed must have the same configuration name. Node deploy configurations with different configuration names will cause an audit failure during application installation.