TIBCO Enterprise Administrator – Runtime Concepts (From the Docs)

Runtime Concepts

Runtime concepts in TIBCO ActiveMatrix BusinessWorks™ include runtime and bwappnode.

At runtime, TIBCO ActiveMatrix BusinessWorks™ launches a pool of AppNodes in the AppSpace in which the application is deployed.

Runtime

A runtime refers to the operating system process that executes the TIBCO ActiveMatrix BusinessWorks™ application. In the TIBCO ActiveMatrix BusinessWorks™ architecture, each runtime is called AppNode.

The runtime is built on the OSGi framework, called Thor with the underlying engine. TIBCO ActiveMatrix BusinessWorks™ is a single JVM environment.

The framework is responsible for the deployment of processes into the engine, while the engine is performing the necessary validation, dependency checks, and property resolution. When a process is deployed, the framework will manage the life-cycling of the process and interact with the administrator to send the current status of the application. The runtime architecture is depicted in the following figure.

Runtime Architecture

At runtime, an AppNode launches the framework to validate and identify dependencies. After the framework validates the modules and the application is deployed, the TIBCO ActiveMatrix BusinessWorks™ engine starts to run the process.

The bwappnode is the operating system process that runs the application.

The binary file named bwappnode is packaged under the TIBCO_HOME/bwx/1.0/bin directory.

The bwappnode process starts an engine at runtime.

Each AppNode is attached to one AppSpace, so that one AppSpace can have multiple AppNodes on a single machine, or across different machines. An AppNode runs all the applications from the AppSpace to which it is attached.

Advertisements

TIBCO Enterprise Administrator – Administrative Architecture (From the Docs)

The following diagram depicts how TIBCO ActiveMatrix BusinessWorks™ components interact.


The main administrative concepts are:

  • Domain: Domains are logical groups that contain applications and their resources. They may contain one or more of AppSpaces, AppNodes and applications and are configurable by a server instance.
  • MetaSpace: Used for storing and distributing configuration data across the machines.
  • AppNode: A runtime unit for hosting application modules and libraries. The AppNodes run BW applications in the AppSpaces.
  • AppSpace: A virtual pool of AppNodes for the application and a logical space where applications are deployed. Each application is deployed to a single AppSpace, and each AppSpace can deploy only one application.AppSpaces are elastic, so that more machines and engine nodes can be added dynamically.You can specify a minimum number of AppNodes as a threshold for determining the AppSpace state. If the minimum is not specified, the default is 1.
  • BWagent: The BWagent on each machine is responsible for configuring partitions, provisioning AppNodes and applications, performing administrative commands, refreshing the cache, and providing for load balancing.
  • bwadmin: Thebwadmin tool is an administration shell where you can execute the administration commands using the command line interface. It is packaged with a number of administration commands that directly manage status of each administration entity.
  • TIBCO Enterprise Administrator (TEA) Server:The TEA server provides monitoring UI and the command line shell for TIBCO enterprise products that are hosted on the server.
  • Deployment: It occurs after an archive file is uploaded and before an application is started. During the deployment, the EAR archive files are copied to the directory under Domain_Home.After the deployment, first create an application project that includes the modules you will deploy. From that application project, create an archive file and deploy it into an AppSpace.