Node configuration has a configuration type of nodeconfig.

Node configuration is separated into these distinct areas:

The node configuration is separated into these distinct areas:

Table 3.3, “Node description configuration” defines the node description configuration parameters.

The optional memory throttling configuration controls:

Throttling and stall states are used internally to prevent memory exhaustion under extreme loads. They can also be used by an application for the same reasons using the com.kabira.platform.swbuiltin.EngineServices.throttle() API. For details on the throttle API see the product javadoc.

Table 3.4, “Memory throttling configuration” defines the memory throttling configuration parameters.

Table 3.5, “Flusher configuration” defines the shared memory cache flusher configuration parameters.

Table 3.6, “Shared memory IPC configuration” defines the shared memory IPC configuration parameters.

Table 3.7, “Deadlock resolution configuration” defines the deadlock resolution configuration parameters.

Table 3.8, “Default domain configuration” defines the domain configuration parameters.

JVM configuration is defined per JVM by name. Multiple JVM configuration blocks may be defined. The JVM name is optionally defined when the JVM is deployed using the jvmname deployment tool option. If the jvmname option is not specified when the JVM is deployed, a unique name is generated automatically.

JVM configuration supports specifying:

All JVM configuration values, other than the JVM name, are optional. If a JVM configuration is deactivated, all of the configuration parameters are set to their default value.

Table 3.9, “JVM configuration” defines the JVM configuration parameters.

The bit field values for the trace configuration parameters are defined in Table 3.10, “Trace flag values”.

Example 3.1, “Node configuration example” is an example node and JVM configuration.

configuration "Node A" version "3.0" type "nodeconfig"
{
     configure switchadmin
     {
          configure Node
          {
               //
               //     Set the node description and add
               //     a service property of foo=bar to the
               //     node service record
               //
               Description
               {
                    defaultDescription = "Development";
                    properties =
                    {
                         {
                              name = "foo";
                              value = "bar";
                         }
                    };
               };

               //
               //     Shared memory flusher control
               //
               Flusher
               {
                    flushIntervalSeconds = 2;
                    maximumTypes = 3;
                    maximumObjectsPerType = 4;
               };

               //
               //     Set a memory utilization threshold of 50%
               //     and check 5 times a second
               //
               MemoryThrottle
               {
                    thresholdPercentage = 50;
                    frequency = 5;
               };

               //
               //     Set the no destination timeout value to 10 seconds
               //     for the Shared memory IPC mechanism
               //
               EventBus
               {
                    noDestinationTimeoutSeconds = 10;
               };


               //
               //    Set the maximum deadlock backoff resolution to 5 seconds
               //
               Deadlock
               {
                    maximumBackoffMilliseconds = 5000;
               };

               //
               //     Join the Application Cluster group in 
               //     the Development domain
               //
               Domain
               {
                    name = "Development";
                    group = "Application Cluster";
               };
          };

    };

    configure switchadmin
    {
          JVM
          {
               jvmName = "My JVM";

               //
               //    Configure dispatch threads
               //
               minimumDispatchThreads = 8;
               maximumDispatchThreads = 16;

               //
               //    Allow four concurrent timers with a 500 millisecond resolution
               //
               timerParallelism = 4;
               timerResolutionMilliseconds = 500;

               //
               //    Update runtime trace flags
               //
               traceDebugFilter = 0x0;
               traceInfoFilter = 0x3FFFFFF;
               traceWarningFilter = 0x3FFFFFF;
               traceFatalFilter = 0x3FFFFFF;
          };
     };
};

Node agent configuration has a configuration type of nodeagent.

Table 3.11, “Node agent configuration” defines the node agent configuration parameters.

The node agent listenAddress configuration must match the Domain Manager nodeAgentAddress (see Table 2.3, “Node configuration”) configuration value if service discovery is not being used for managed node discovery. If these two values do not match, events will not be forwarded to the Domain Manager by the node. The listenAddress configuration value defines a network listener. The nodeAgentAddress configuration value defines the remote address that the Domain Manager, acting as a network client, should connect with to communicate with the node.

Example 3.2, “Example node agent configuration” is an example node agent configuration.

configuration "nodeagent" version "2.0" type "nodeagent"
{
     configure nodeagent
     {
          NodeAgentConfiguration
          {
               enableEventForwarding = true;
               enableTraceToEvent = true;
               numberOfMessages = 1000;
               listenAddress = "TCP::0";
               topicNameList =
               {
                    "kabira.kis",
                    "kabira.kts"
               };
          };
     };
};

A complete discussion of configuration life cycle can be found in the TIBCO BusinessEvents® Extreme Java Developer's Guide. In summary configuration follows this life-cycle:

Configuration is loaded into a node using either the TIBCO BusinessEvents® Extreme Administrator dialog show in Figure 3.10, “Loading configuration” or this command:

administrator servicename=A load configuration source=myConfiguration.kcs

The Ignore memory threshold check box is used to allow configuration data to be loaded in shared memory even if the configured shared memory throttle utilization is exceeded (see Table 3.4, “Memory throttling configuration”). Without this override, attempting to load configuration data into congested shared memory will fail.

Figure 3.10. Loading configuration

All loaded configuration data can be displayed from the Configuration tab for a node as shown in Figure 3.11, “Loaded configuration”, or using this command:

administrator servicename=A display configuration

This information is displayed for each loaded configuration file:

Figure 3.11. Loaded configuration

Configuration activation, deactivation, and removal is done from the TIBCO BusinessEvents® Extreme Administrator configuration screen show in Figure 3.12, “Managing configuration”.

Figure 3.12. Managing configuration

Configuration state changes and also be done using these commands:

//
//  Activate a deactive configuration
//
administrator servicename=A activate configuration type=distribution name=distribution version=1.0

//
//  Deactivate an active configuration
//
administrator servicename=A deactivate configuration type=distribution name=distribution version=1.0

//
//  Remove configuration from shared memory
//
administrator servicename=A remove configuration type=distribution name=distribution version=1.0

The View Source... button shown in Figure 3.12, “Managing configuration” can be used to export loaded configuration in a format that can be modified and reloaded. Configuration can also be exported using this command:

administrator servicename=A export configuration type=distribution name=distribution version=1.0