Specifying the Domain, AppSpace, AppNode, and APPNode HttpPort Base Configuration

This component wizard page defines the Domain, AppSpace, and AppNode names for your ActiveMatrix BusinessWorks environment. This page also sets the AppNode HTTP Port Base for your ActiveMatrix Business run time.

Note: When specifying names for the Domain, AppSpace, and AppNode use letters, numbers, hyphens (-) and underscores (_). Other special characters and spaces are not allowed.

Procedure

  1. Specify Domain Name.

    A BusinessWorks domain is a logical group that provides an isolated environment for applications and their resources to reside. It provides an administrative boundary for an integration project. Each domain can share machines with other domains, but communication between domains is not allowed. Domains include servers that may or may not be distributed over different machines and operating systems.

    Note: If you keep the Domain Name field empty or choose to run the component in Local mode, the default domain name is used: <ComponentName>_Domain.

    When the Agent Role is set to Client, the client runtime instance uses the domain of ActiveMatrix BusinessWorks running as Server.

    TIBCO ActiveMatrix BusinessWorks running as a Client uses the domain from the TIBCO ActiveMatrix BusinessWorks instance running as a Server.

  2. Specify AppSpace Name.

    A BusinessWorks AppSpace is a virtual pool of AppNodes where an application is deployed. When an application is deployed, the AppSpace starts the application on each of its AppNodes. More AppNodes can be added dynamically to the AppSpace to manage the load-balancing and fault tolerance needs of an application. Multiple applications can be deployed to an AppSpace.

    Note: If you leave the AppSpace Name field empty or choose to run the component in Local mode, the default AppSpace name is: <ComponentName>_AppSpace.
  3. Specify AppNode Name.

    A BusinessWorks AppNode is a runtime entity for hosting application modules and libraries. An AppNode represents a physical engine process that is launched when an application starts to run. On the component wizard, one AppNode can be created in an AppSpace, but using the TEA Enabler or other BusinessWorks Administrator interface, you can create more.

    Note: If you keep the AppNode Name field empty or run the component in the Local mode, the default AppNode name is:    <ComponentName>_<ComponentInstance>_AppNode
    • When ComponentInstance = 0, the name is <ComponentName>_AppNode
    • When the ComponentInstance > 0, the name is <ComponentName>_<ComponentInstance>_AppNode
    • When a component has multiple instances, appNode names are incremented: <ComponentName>_<ComponentInstance>_AppNode
  4. In AppNode HTTP Port Base, specify a port or select the default.

    The HTTP Port Base value is used as a basis to calculate and assign ports dedicated for specific BusinessWorks applications. This helps to prevent HTTP port conflicts when multiple BusinessWorks applications are deployed to the same machine. Silver Fabric notifies the Virtual Router of the HTTP end points so that the end user can call those endpoints without having to know where the application runs (machine port). The default value is 18200.

  5. Specify the number of fault tolerance instances in the Number of FT Instances field. The default value is 1.
  6. Specify the value for AppNode HttpPort Increase field. The default value is 50.
  7. Click Next.