Editar

Partilhar via

Invokable TPs and the Host Integration Server Configuration

  • Artigo

For Host Integration Server to receive requests from an invoking TP on another system, and then route those requests to an invokable TP, certain parameters must be configured correctly:

  • Host Integration Server must have a connection to the system from which the invoking TP's request is sent.

  • Host Integration Server must have a remote LU capable of receiving the incoming request. This remote LU can be configured either explicitly or implicitly. When configured explicitly, there is an explicit match between a remote LU alias on Host Integration Server and the alias of the LU that conveys the invoking TP's request.

    When configured implicitly, an Implicit Incoming Remote LU (with its Implicit Incoming Mode) is used. Several items must work together. First, the LU alias specified in the incoming request (the LU alias requested for the invokable TP) must match a local LU alias on the server receiving the request. Second, the local LU on the server must have an Implicit Incoming Remote LU assigned to it. The properties of the Implicit Incoming Remote LU will be used for that LU-LU session. For more details about how an Implicit Incoming Remote LU works, see Implicit Incoming Remote LU and Implicit Incoming Mode, earlier in this section.

  • Appropriate local LUs must be defined in the Host Integration Server configuration file.

See Also

TP Name Unique for Each TP (Transaction Programs)
TP Name Not Unique; Local LU Alias Unique
TP Name Not Unique; Local LU Alias Unspecified
Invoking Transaction Programs
Invoking TPs and Host Integration Server Configuration
Invokable Transaction Programs
Transaction Programs