Programmer and Administrator Roles

An endpoint contains transport details and helps separate programmer and administrator responsibilities.

Programmer’s Role

Programmers use endpoints to publish and subscribe to message streams. The program uses the endpoint name so transport details can be omitted in the programs. The program determines its publish and subscribe behavior with respect to its endpoints. The transports and persistence stores are external to a program.

Administrator’s Role

Administrators can determine the following:

  • Administrators determine the host computers where application processes run. An application could run as a single process: for example, a central repository application. Or an application could run as many processes: for example, a workstation interface application for stock market traders.

  • Administrators configure the set of direct path transports that connect application endpoints, allowing message streams to flow.

  • Administrators configure a set of persistence stores, providing an indirect path and backing application endpoints.

Transports and persistence stores are external to the programs and only the endpoints are visible to programmers.

Role Example

Recall the earlier diagram where each subscriber has a different type of transport for the same message.

Figure 18: Two Types of Transports

The following diagram represents the duties of the programmer and administrator. The programmer adds the endpoints (EP1 and EP2) in the publisher and subscriber programs. The Administrator configures the transports to work with EP1 and EP2.

Figure 19: Separation of Responsibilities

Coordination Forms

The following TIBCO FTL Forms are available to coordinate the work between programmers and administrators.

  • Application Coordination Form

  • Durable Coordination Form

  • Endpoint Coordination Form

  • Format Coordination Form