Applications Grid
The Applications grid presents application definitions in the realm. In edit mode, you can create new application definitions and modify existing application definitions.
Endpoint Level
| Column | Description |
|---|---|
| Endpoint | Every application definition has at least one endpoint.
This column presents the names of endpoints. This JSON attribute contains a list of endpoint objects, each defined by its name and persistence store. |
| Cluster | Optional.
To associate an endpoint with a cluster, select the cluster name from the drop-down menu in this column. Note that the cluster name ftl.forwarding.cluster is associated with a wide-area store. |
| Store | Optional.
To associate an endpoint with a persistence store, select the store name from the drop-down menu in this column. |
| Durable Template | Optional.
To associate an endpoint and its store with a dynamic durable template, select the template name from the drop-down menu in this column. The application process uses this template to create all of its dynamic durables. |
Transport Level
Each endpoint has at least one transport connector.
For background information, see Implementation: Endpoints (Micro).
| Column | Description |
|---|---|
| Transport | Required.
To apply a specific transport definition to an endpoint, select the name of that transport definition from the drop-down menu in this column. The value Server indicates message broker behavior over a server-defined Dynamic TCP or Auto TCP transport. The remaining columns present details of that transport definition. After adding transport connectors to an endpoint, edit the endpoint details to configure the abilities of the transport connectors. |
| Protocol | The protocol of the transport. (Read only.) |
| Address
Port Mode |
The values in the Address, Port, and Mode columns depend on the transport's protocol.
For more information, see Address Level. |
Instance Level (Optional)
Every application definition has at least one instance definition, named default. If any application defines more than one instance, then the grid automatically expands to show the instance level as level 2. (Otherwise, the grid automatically hides this level.)
For background information, see Implementation: Application (Macro).
| Column | Description |
|---|---|
| Instance | Every instance has a name.
This column presents the names of instances. Instance names must be unique within each application. (You may use the same instance name in several different applications.) All names are limited to a maximum length of 256 characters. For an overall conceptual explanation of instances and transport connectors, see Implementation: Application (Macro). Required.Define the instances of the application. You must configure the default application instance (and you cannot delete it). You may also define other application instances (optional). |
| Identifier | Optional.
Identifier string for matching. When present, the transport level of the instance definition applies only to application processes that supply this identifier when connecting to the FTL server. The identifier must match exactly. For more information, see Instance Matching. |
| Host | Optional.
Host name or IP address for matching. When present, the transport level of the instance definition applies only to application processes running on this host. To match, this string value must exactly match either the output of the hostname operating system call on the computer where the application process is running, or the IP address bound to that host name. For more information, see Instance Matching. |