Application and Endpoint Concepts

Endpoints represent data exit and entry points within application programs. Transports carry message data between endpoints. Administrators configure endpoint implementation and transport usage in the realm. The following topics explain these ideas in greater depth.

  • Configuration Model
    This overarching model serves as a framework for understanding the concepts and tasks of configuring a realm. Refer back to this model as you read the topics that follow.
  • Endpoints
    An endpoint is an abstraction that represents a set of publishers and subscribers in communicating programs.
  • Abilities
    An endpoint has four communication abilities. A separate aspect of the API embodies each of these abilities. The following table summarizes the four abilities.
  • Implementation: Endpoints (Micro)
    Administrators arrange transports to implement endpoints.
  • Implementation: Application (Macro)
    Administrators view an application program both as an executable program, and also as a set of process instances of that program, running on one or more host computers. Arranging process instances on various host computers is one of the administrator’s responsibilities.
  • Administrative Requirements
    Administrators must coordinate with application developers to properly configure and deploy applications.
  • Administrative Options
    When configuring endpoint implementation, administrative choices affect transmission characteristics for the application. Consider these factors when optimizing overall performance.
  • Sample Configuration 1: Default with tibsend and tibrecv
    This first example illustrates the simplest configuration for communication. The sample applications tibsend and tibrecv use the default configuration definitions.
  • Sample Configuration 2: tibsendex and tibrecvex
    This second example illustrates basic concepts in configuring transports and endpoint implementation, namely: binding a transport to carry an ability, configuring connectors, joining endpoints through a common transport, dividing message streams over separate transports.
  • Sample Configuration 3: tibrequest and tibreply
    This third example illustrates additional concepts in configuring transports and endpoint implementation, namely: binding a transport to carry several abilities; two-way message traffic; and connection-oriented transports with connecting and listening ends.