Application Life Cycle

TIBCO ActiveMatrix applications presume different forms in different phases of the application life cycle.

In the design phase a TIBCO ActiveMatrix application consists of one or additional composites. Each application has a root composite. A composite contains components, services, references, and properties. The components, services, and references depend on convention features and resources. Services, references, and properties promoted to the root composite comprise the public interface of the application.

The output of the design phase is a distributed application archive (DAA). A DAA contains features and an application template, which consists of the root composite and a set of linked configuration files: nested composites, resource templates, WSDL files, and substitution variable files.

In the administration phase, you create an application by instantiating an application template. The product installer adds product application templates to Administrator. When you upload a DAA file to Administrator, Administrator extracts the application template and (optionally) the features and resource templates.

You can configure the application by setting properties, logging configurations, and substitution variables. You can add bindings to services; promote services and references to the environment, and wire services and references to services and references in extra applications or environments. You also specify a distribution of the application to the runtime infrastructure. You can explicitly distribute application fragments-components and bindings-to one or more nodes or you can specify that an application should be distributed to the same nodes as another application. When you arrange the application, Administrator applies the distribution and the configuration. Features are automatically distributed with components, but resource instances required by the application must be manually installed into nodes before deployment. Life cycle operations on the application are translated into life cycle operations on the application fragments. You can as well start and stop application fragments. The following figure illustrates the application artifacts across the application life cycle.