Node Configuration Reference

Features

Column Description
Name The name of the feature.
Type The type of the feature.
Version The version of the feature.
Status The status of the feature:
  • Installed
  • Marked for Install
  • Marked for Uninstall

Logging Configurations

Logging Configuration: Basic and Advanced Mode
Property Required? Editable? Accepts SVars? Description
Logger Name Y Y N The name of the logging configuration. The logging configuration name must be the name of a logger in the source code or the name of the package in which the source code is contained.
Log Level

(FileAppender, JmsAppender)

Y Y N All events of a level equal to or lower than the specified level are logged. For the Info level, Info, Warn, Error and Fatal events are logged. One of:
  • TRACE All events.
  • DEBUG Fine-grained informational events used for debugging an application.
  • INFO Coarse-grained informational messages that highlight the progress of the application.
  • WARN Potentially harmful events.
  • ERROR Errors that allow the application to continue running.
  • FATAL Errors that cause the application to fail.
  • OFF Blocks passing messages to a parent
Additivity Y Y N One of:
  • true Log messages are passed to the parent logging configuration.
  • false Log messages are not passed to the parent logging configuration.
Appender Y Y N The destination to which log events are appended.

Debuggers

Property Required? Editable? Accepts SVars? Description
Type Y N N The type of the debugger:
  • Java Debugger - supports debugging Java and Spring component implementations. Implemented by changing properties on the Java VM in which the node runs. Requires restarting the node enable.
  • Platform Debugger - supports debugging composite applications. Implemented as a composite application that runs on the node.
State Y N N The state of the debugger:
  • Marked for Enable - displayed by a Java Debugger when you set the value of the Debug Port property.
  • Enabling
  • Enabled
  • Disabled
Synchronization Y N N Indicates whether the node runtime matches the node version in the Administrator database.
Property Name Y N N The name of the property to configure:
  • Java - Debug Port
  • Platform - TCP Port
Property Value Y Y N The property value.

JVM Configuration

This link is displayed only if the node is associated with a TIBCO host.

Property Required? Editable? Accepts SVars? Description
Max Heap Size (MB) N Y N The maximum size of the heap for the JVM. If Max Heap Size is specified -Xmx Max Heap Size m is appended to the JVM argument string.
Java Thread Stack Size (KB) The size of the Java thread stack. If a Java thread stack size is specified the string -Xss Java Thread Stack Size k is appended to the JVM argument string.
Enable JVM Security Manager N Y N When enabled, code running on the node cannot shut down the node process by accidentally or purposefully calling System.exit.
General Args N Y N General arguments to pass to the JVM.
Properties N Y Y Properties to pass to the JVM. For each property, name is required but value is optional. For a property with a value the string -Dname=value is appended to the JVM argument string. For a property without a value the string -Dname is appended to the JVM argument string.
JVM Argument String RO RO The argument string passed to the JVM. It is generated from the other properties.

Tuning

A node supports resource instances as JCA resource adapters. Resource adapters can dispatch runnable jobs to the JCA work manager which internally uses a JCA thread pool to execute the jobs. There is one JCA thread pool per node and all resource adapters use same thread pool to dispatch their jobs. Currently only the JMS resource adapter is using this thread pool for its job execution.
Property Required? Editable? Accepts SVars? Description
Core Pool Size N Y Y When a new task is submitted and fewer than Core Pool Size threads are running, a new thread is created to handle the request, even if other threads are idle. If there are greater than Core Pool Size but fewer than Max Pool Size threads running, a new thread is created only if no threads are idle. Must be greater than or equal to zero.
Note: When a Java or Spring component service is configured with a Threading policy with a non-zero timeout value and is promoted to a composite service using a SOAP or JMS binding, concurrency is halved because two threads are used per request. To achieve the desired concurrency, specify double the number of threads for the thread pool size.

Default: 2. Two threads are used to service one request: one for receiving the request and one for receiving the response.

Max Pool Size N Y Y The maximum number of threads in the pool. Must be greater than zero and greater than or equal to Core Pool Size.

Default: 250.

Keep Alive Time (s) N Y Y The amount of time an idle thread remains in the pool before being reclaimed if the number of threads in pool is more than Core Pool Size.

Default: 60 s.