Distribution Modes

Distribution involves assigning application fragments — components and bindings — to nodes. There are two distribution modes, Product Application and Manual.

Product Application: Application fragments are distributed to the nodes based on where the target application is deployed. By default, bindings are distributed to the same nodes as the components they are related to, but you can override the binding distribution. For example, you can deploy an HTTP binding outside a firewall while retaining the processing of messages inside the firewall.

Before deploying an application containing any other type of component or binding on a node, an instance of the product application template that supports that component or binding must be deployed on that node. For Mediation components, the product application name is TIBCO ActiveMatrix Mediation Implementation Type Application and the product application template name is TIBCO ActiveMatrix Mediation Implementation Type Application Template. For all other component and binding types, see the documentation for the component and binding type for whether a product application is needed and for the name of the required product application template.

Manual - Components and bindings in any combination are distributed to any nodes within an environment. Use this mode when you want you full control over the nodes on which your application is deployed or if you are using component types that do not utilize product applications.

You choose a distribution mode when you create the application using the New Application wizard. If you exit the wizard after you complete the Application Setup part of the wizard, you must later manually map the application to nodes in the Distribution tab.