Page History
There are two activities supplied with LANSA Composer that make use of the LANSA Composer Request Server. They are:
CALL_FUNCTION and
In both cases, an activity parameter is used to specify the name of a LANSA system configuration that contains the details necessary to connect to another LANSA system to run a LANSA function or a LANSA Composer processing sequence in that system.
...
But it is also possible to define the LANSA system configuration such that the activities can call a LANSA function or execute a LANSA Composer Processing Sequence on a different (*) server system.
...
In addition to correctly defining the connection in the LANSA system configuration, there are some other pre-requisites to successfully using this support. These include:
LANSA Composer must be installed and licensed on the remote system
The LANSA Listener must be active in the remote LANSA Composer system
| Anchor | ||||
|---|---|---|---|---|
|
You must install LANSA Composer on the remote system in order to provide the remote request server components that allow the communications link to be completed.
This installation of LANSA Composer might not be used for any other purpose than to provide those remote request server components. It does not need to be a fully-licensed LANSA Composer system unless you wish to design or execute Processing Sequences on the remote system However, a LANSA Composer Remote Request Server license is required for the remote server.
| Anchor | ||||
|---|---|---|---|---|
|
The requesting LANSA Composer system will connect to the remote system through the LANSA listener in the remote LANSA Composer system. Therefore the LANSA listener must be active in that system in order that it may receive and process the requests.
| Anchor | ||||
|---|---|---|---|---|
|
A vital part of the LANSA system configuration is the Server LU partner name that specifies the logical name that refers to the LANSA listener on the remote system.
...