LANSA System Configuration

You are here:

LANSA System Configuration

The LANSA system configuration is used to contain the details necessary to connect to another LANSA system to run a LANSA function or a LANSA Composer processing sequence in that system. It is used in conjunction with the CALL_FUNCTION and COMPOSER_RUN activities. For more information concerning the usage of the LANSA system configuration, you may wish to refer to:

CALL_FUNCTION

COMPOSER_RUN

Appendix F. The LANSA Composer Request Server

If you experience difficulties in getting your CALL_FUNCTION or COMPOSER_RUN request to work through the LANSA Composer Request Server, please refer to:

Troubleshooting the LANSA Composer Request Server

Common information that must be supplied for any LANSA system configuration is described below:

ID	An identifier to uniquely identify this Configuration. To make use of a LANSA system configuration, you will specify this name as the value for the LANSACONFIG parameter of the CALL_FUNCTION or COMPOSER_RUN activities.
Description	This should describe the Configuration.
Status	Active or Inactive. Configurations cannot be used in a processing sequence while they are in inactive status – supplied activities will end in error if they attempt to use a configuration that has inactive status.

Additional information specific to this configuration type is in two parts.

1. LANSA Composer connects to the request server:

2. The request server connects to the other LANSA system:

1. LANSA Composer connects to the request server:

The first part of the LANSA system configuration specifies how LANSA Composer contacts the LANSA Composer request server that will execute the task (CALL_FUNCTION or COMPOSER_RUN) in the other LANSA (or LANSA Composer) system.

If LANSA Composer, the request server and the other LANSA system all reside on the same server, then you should simply select On local system in the Connect to request server drop-down. You do not need to enter any further information in this section – instead you should proceed to 2. The request server connects to the other LANSA system:.

If, however, the other LANSA system resides on a different server (*), then you should select On remote system in the Connect to request server drop-down and complete the additional information as described below.

* Note a LANSA Composer Remote Request Server license is required for the remote server in order to call a LANSA function or run a Processing Sequence on a different server system.

Note: LANSA Composer must be installed on the remote server system in order to use this support, so that LANSA Composer on the source system can communicate with components of the LANSA Composer request server on the remote system. Additional software licenses may be required. Refer to Connecting to the LANSA Composer Request Server on a Remote System for further details.

Keep connection active	If your processing sequence will make multiple requests (CALL_FUNCTION or COMPOSER_RUN) using the same LANSA system configuration, then you may wish to specify Yes in this field in order to keep the connection active between the requests. If you specify No, then a new communications session to the remote system will be started and ended for each request.
Server type	Choose the server type (IBM i or Windows) that applies to the remote system. Note that the values that you must supply in the second configuration part vary according to your choice here.
Server LU partner name	Specifies the Server LU partner name that identifies the network name, port and other information necessary to connect to the target system. If LANSA Composer is running on a Windows server, this is the name as defined in the LANSA Communications Administrator. If LANSA Composer is running on an IBM i server, this is the name as defined in LANSA's Work with Communications Routing Records screen. Notes: 1. The LANSA Communications routing record that defines the Server LU partner name for this purpose is defined on the LANSA Composer server. You cannot use the LANSA Communications Administrator on your client computer to define this. 2. The connection information must refer to the LANSA Composer configuration on the target system that contains the LANSA Composer request server software 3. The LANSA listener for that system needs to be active when LANSA Composer attempts to establish the connection.
Server partition	Specifies the partition name in the LANSA Composer configuration on the target system that contains the LANSA Composer request server software. In a standard LANSA Composer installation on the target system, the name will be LIC.
Use Windows credentials	Check this box to specify that LANSA Composer should use the credentials of the job running the LANSA Composer processing sequence to connect to the LANSA Composer request server on the target system. The target system must have been configured for Single Sign On and the user enrolled in order to use this option.
User and password	Specifies the user name and password that LANSA Composer uses to connect to the LANSA Composer request server on the target system.
Client-server and Server-client translation tables	Specifies the Client-to-Server and Server-to-Client conversion table names to be used. No library name can be specified. If not specified, these values default to JOB, meaning the translation table will be generated based on the client code page and the IBM i server job's CCSID. If this argument is JOB then the Server-to-Client table must also be *JOB. These values do not apply when the target system resides on a Windows server
Server exceptional arguments	This may be used to specify a string of further X_RUN parameter names and values required to connect to the LANSA Composer request server on the target system. You should refer to LANSA documentation of the X_RUN parameters for more information.

2. The request server connects to the other LANSA system:

The second part of the LANSA system configuration specifies how the LANSA Composer request server connects to the other LANSA (or LANSA Composer) system.

The information required varies according to whether the other system resides on an IBM i server or a Windows server.

LANSA Composer server for IBM i

The additional information necessary to connect to the other LANSA (or LANSA Composer) system for an IBM i server is:

LANSA program library name	Specifies the name of the LANSA program library in the LANSA system that is to be used. For example: DC@PGMLIB
LANSA partition name	Specifies the name of the LANSA partition in the specified LANSA system that is to be used. For example: SYS. The partition must be multi-lingual enabled.
LANSA language code	Optionally specifies the LANSA language code used to start LANSA or LANSA Composer in the target system. If not specified, or if the special value '*' is used, then the language code being used by LANSA Composer will be used to start LANSA in the target system.

LANSA Composer server for Windows

The additional information necessary to connect to the other LANSA (or LANSA Composer) system for a Windows server is described below. Most of these parameters correspond directly to LANSA X_RUN parameters used to make the connection to the LANSA system. You should refer to LANSA documentation of the X_RUN parameters for more information.

LANSA system path	Specifies the path to the X_WIN95 folder in the LANSA system to be used. For example: C:\Program Files\LANSA\X_WIN95\ The path should usually end in X_WIN95. If you selected On local system in the Connect to request server drop-down, then you may use the provided prompter button to browse for the LANSA system path.
LANSA partition name	Specifies the name of the LANSA partition in the specified LANSA system that is to be used. For example: SYS. If the target LANSA system is actually a LANSA Composer system, the partition should be LIC.
LANSA language code	Optionally specifies the LANSA language code used to start LANSA or LANSA Composer in the target system. If not specified, or if the special value '*' is used, then the language code being used by LANSA Composer will be used to start LANSA in the target system.
User name	Specifies the user name used to connect to the LANSA system. (This value corresponds to the X_RUN parameter USER=.)
Password	Specifies the password used to connect to the LANSA system. (This value corresponds to the X_RUN parameter PSPW=.)
Datasource name	This parameter identifies the user database used with the specified LANSA system. Note that the name identifies the data source (DSN) name. (The DSN name may be different to the name of the database as known to the database management system.) The data source (DSN) contains the information necessary to identify the actual database. (This value corresponds to the X_RUN parameter DBID=.)
Database type	Specifies the type of database specified in the previous parameter. You should choose the appropriate type from the drop-down list. (This value corresponds to the X_RUN parameter DBUT=.)
Database user	Specifies the user name for the database login, if required. If you wish to use integrated authentications with MS SQL Server, you should leave this field blank. (This value corresponds to the X_RUN parameter DBUS=.)
Database password	Specifies the password for the database login, if required. If you wish to use integrated authentications with MS SQL Server, you should leave this field blank. (This value corresponds to the X_RUN parameter DBPW=.)
LANSA system overrides	This may be used to specify a string of further X_RUN parameter names and values required to connect to the specified LANSA system. You should refer to LANSA documentation of the X_RUN parameters for more information.