Reference Information › User Interface Reference Guide › Graphical User Interface › Application Configuration › Protocols

Protocols

The Protocols tab shows the full set of protocols available for defining appliance terminal types. This is not a configurable application settings (that is, it is not something that you may want to change from one instance of the application to another), but rather an advanced option for configuring appliances in the application scope (Protocols are on a separate tab for convenience, although they belong to the application configuration and should be part of the application boundary property sheet).

This is useful when you are defining new appliances and want to know what protocol types are available, or want to add new protocols.

The Protocols tab contains the following information and configurable fields:

• Catalog Protocols--This list shows the protocols defined in all catalogs accessible to the application (union of all protocols defined in all catalogs, with the duplicates eliminated).
  • Name--The name of the protocol. This name is used when selecting a protocol for each terminal of an appliance inside the application.
  • Filter--A network filter specification for the protocol, describing what are the legal interactions. The descriptions are similar to setting up port filters.

  Note: This list is read-only. To add a new protocol, use the Application Protocols list below.

• Application Protocols--This list defines the custom protocols specific to the application. You can add new protocols, defining the same parameters as for the catalog protocols list above.
  • Name--The name of the protocol. This name is used when selecting a protocol for each terminal of an appliance inside the application; it must be unique (should be a duplicate of a catalog-defined protocol). The name is a single word, case-sensitive, alphanumeric ([A-Za-z0-9_]).
  • Filter--A network filter specification for the protocol, describing what are legal interactions in that protocol. Currently, the filter specification for CA AppLogic® is not fully defined. Use the following format for the filter value: # protocol identification or comment. The comment should be sufficient to identify the application-level protocol (such as an RFC number) or simply a description (# TCP port 80).

Notes:

• Selecting any protocol allows connections to be established in any direction or bi-directionally within a connection. When connecting terminals configured to allow any protocol, all connected terminals must be configured to allow any protocol.
• The any protocol allows connections to be established in any direction within a connection (a bi-directional connection). The any protocol must be set on both terminals of the connection.
• Although this version of CA AppLogic® does not enforce the protocols on inter-appliance connections, it is a good idea to set those correctly, both for documenting the required protocol and for making use of the protocol enforcement feature when it becomes available.
• You can add new protocols only for singleton appliances; if you add the appliance using the new protocol(s) to a catalog, the protocol settings may not be propagated properly. If you need to add new protocols, contact Technical Support for more details or review the protocol definitions in catalog packages described in the ADL Language Reference.