• TIBCO BusinessWorks application: This component uses an embedded implementation of Java Runtime Environment (JRE) which creates the Java Virtual Machine (JVM). The JVM can be tuned for better performance.

• TIBCO BusinessWorks process engines: These are logical grouping of jobs; a process engine runs within a single Java Virtual Machine (JVM).

• TIBCO BusinessWorks jobs: These are instances of a BusinessWorks process template and consume resources. One job corresponds to one overallWindchill ESI product data publish operation per ERP instance, or one ESI transaction.

• TIBCO BusinessWorks threads: These are the same as Java threads. Threads represent a pool of workers for jobs. Each thread executes a fixed number of BusinessWorks activities and is then released back to the pool.

• Adapter connections: These represent the data channels available to the distribution targets. Refer to the appropriate TIBCO adapter documentation for a complete understanding of how connections are formed, and when they are released.

• JVM memory size: This needs to be monitored to check how much memory is consumed for a given number of jobs and if this is pushing the limits of available memory. You can use basic operating system tools to perform this function.

• CPU usage allocation: This activity needs to be monitored because having multiple, available CPUs does not guarantee that the application resource load is automatically distributed across them. CPU load-balancing is typically configured at the operating-system level.

• Additional host machines: Adding more physical servers can provide greater data throughput, as well as high-availability features.