Copyright © Cloud Software Group, Inc. All Rights Reserved

Edit Service Instance Dialog

Fields can be edited if this dialog is invoked from the Configuration Builder pane. If invoked from the Deployed Configuration pane, the fields are read only.

The following tabs are available:

•	General Tab

•	Server Settings Tab

•	Graceful Shutdown Tab

General Tab

The General tab displays the following information:

•	Software that will run the used by the service instance.

•	Machine on which this instance has been set up to run.

•	Operating system used by this machine.

•	Name of the service instance.

•	Description for this service instance.

•	Contact for this service instance.

Server Settings Tab

General

•	Start on Boot — Specifies that the service instance should be started whenever the machine restarts.

•	Enable Verbose Tracing — Enables verbose tracing, in particular, for TIBCO ActiveMatrix BusinessWorks service instances.

•	Max Log File Size (KB) — Specifies the maximum size (in Kilobytes) a log file can reach before the engine switches to the next log file.

•	Max Log File Count — Specifies the maximum number of log files to use. When log files reach the size specified in the Max Log File Size field, the engine switches to the next log file. When the maximum number of log files have been written, the engine begins writing to the first log file again.

•	Thread Count — Specifies the number of threads to use to execute process instances. The number of threads determines how many process instances can execute concurrently. Set the number of threads to a value that is appropriate for your operating system and physical machine configuration.

You should measure the available CPU and memory resources on your system under a typical processing load to determine if the default value of 8 threads is appropriate for your environment. For example, if engine throughput has reached a plateau, yet measurements show that CPU and memory are not fully utilized, increasing this value can have a positive effect on throughput. Typical numbers of worker threads range between 4 and 32. Specifying too low a value can cause higher memory use and lower engine throughput even though spare CPU resources exist. Specifying too high a value can cause CPU thrashing behavior, or an increase in latency caused by a large number of messages in the message queue.

Java

This pane is only available for Java applications.

•	Prepend to Classpath — The items you supply here are prepended to your CLASSPATH environment variable. You can specify a Java code editor, or the jar file from a JNDI provider if you wish to use TIBCO ActiveMatrix BusinessWorks to receive and process JMS messages.

•	Append to Classpath — The items you supply here are appended to your CLASSPATH environment variable. You can specify a Java code editor, or the jar file from a JNDI provider if you wish to use TIBCO ActiveMatrix BusinessWorks to receive and process JMS messages.

•	Initial Heap Size (MB) — Initial size for the JVM used for the process engine. Default is 32 MB.

•	Maximum Heap Size (MB) — Maximum size for the JVM used for the process engine. Default is 128 MB.

•	Java Thread Stack Size (KB) — Size for the thread stack. Default is 128 KB.

NT Service

•	Run as NT Service — Select to run this service as a Microsoft Windows Service. You can then manage the engine as you would any other service, and you can specify that it starts automatically when the machine reboots.

•	Startup Type — Choose one of the service startup types, Automatic, Manual, or Disabled.

•	Login As — Specify the login account for the service, if any. The domain name must be specified. If the user is defined on the local machine, the domain is ".". For example, user jeff on the local machine would be specified as .\jeff.

•	Password — Click set to define the password for that service, if any.

Graceful Shutdown Tab

This tab appears only if you have displayed this dialog box from an undeployed process. You can specify how a graceful shutdown occurs.

Kill Jobs Timeout

Kill Jobs Timeout specifies the maximum timeout in seconds the process engine will wait for jobs to finish before shutting down the engine. A zero (0) value means 0 seconds, which effectively turns the graceful shutdown into an immediate shutdown.

Wait for Checkpoint

When selected, causes the process engine to wait for all jobs to finish (up to the maximum timeout) before shutting down the engine, rather than removing jobs at their next checkpoint.

Copyright © Cloud Software Group, Inc. All Rights Reserved