Server file locations

The paths specified in this section are used by software running on the LANSA Composer server and must be specified relative to and in the form appropriate for the server system.

LANSA Composer performs delayed and limited validation of the paths specified here. You must make sure that the paths are correct for your installation. You can use the Browse button to browse the server file system for a directory path.

In particular, you should understand that if you change the locations, you may need to move or copy the directory contents on your server accordingly.

LANSA Composer files location

Example: /LANSA_Composer_licpgmlib/lic

This value identifies the path where LANSA Composer supplied directories and files were installed during LANSA Composer installation or upgrade.  Future upgrades will use this path to update or replace the supplied files as necessary.

The remaining locations specified in this section should usually be child directories of this directory.  However, some do not have to be.  If a file location does not contain supplied files (like Trading partners and HTTP inbound payload directory), then you can change their locations as required.

Trading partners

Example: /LANSA_Composer_licpgmlib/lic/TP

This value is used when a linked directory is created for a Trading Partner. This should be a directory on your server. This value is set as the default and may be changed or extended in the Linked directory maintenance. For example, the base directory could be /LANSA_Composer_licpgmlib/lic/TP/ and within that there could be sub-directories for each trading partner such as /LANSA_Composer_licpgmlib/lic/TP/TP1/inbound.

MapForce Server (MFX) files

Example: /LANSA_Composer_licpgmlib/lic/MFX

This value is shown only for LANSA Composer on Windows servers.  It specifies the directory on your server in which MapForce Server executable (.MFX) files are saved and from which they will be executed.

HTTP inbound payload directory

Example: /LANSA_Composer_licpgmlib/lic/HTTPIN

This value is used by the supplied HTTP activities. It is used to identify the directory into which the payload of HTTP Inbound messages are saved. If you are going to be using Inbound HTTP processing, then a directory on your server must be entered.

SEF files

Example: /LANSA_Composer_licpgmlib/lic/SEF

This value is used by the supplied DISCOVER_EDI activity to locate SEF (LSEF) files that are used for validating EDI transactions.

Import files

Example: /LANSA_Composer_licpgmlib/lic/Imports

This value should contain the location on your server where supplied master import files have been installed.

Example files

Example: /LANSA_Composer_licpgmlib/lic/Examples

This value should contain the location on your server where supplied example files have been installed.  Some of the supplied example processing sequences may use this value to locate files used in the examples.

Tutorial files

Example: /LANSA_Composer_licpgmlib/lic/Tutorial

This value should contain the location on your server where the tutorial data has been placed. Refer to Objects Supplied for the Tutorials in the Tutorial installation for IBM i Server for the files that this directory should contain.

If you intend to complete the tutorials, please check that the value entered here is correct.