Configuring application servers for Lawson

  1. On the Application Server Configuration tab, go to the Server Infrastructure > Java and Process Management > Process Definition > Java Virtual Machine > Custom Properties for the application server .

    Add the following name and value pairs for Lawson environment variables.

    Name Value
    com.lawson.env

    The name of your Environment

    Example

    LSFPROD1
    com.lawson.gendir

    literal path to GENDIR

    Example

    /lsfprod1/gen
    com.lawson.lawdir

    literal path to LAWDIR

    Example

    /lsfprod1/law
    com.lawson.ladbdir

    literal path to LADBDIR

    Example

    /lsfprod1/db
    os400.file.create.auth RWX
    os400.dir.create.auth RWX

    Optional

    com.lawson.logdir

    Literal path to a location for Lawson Security log files. If you don't set this value, security logs are to be stored in LAWDIR/system by default.

    Note: This directory must already exist on your system.

    Optional

    com.lawson.log.server.name

    This value is used in vertically-scaled configurations. It allows vertically-clustered Lawson installations to have unique IOS log files for each server in the cluster.

    This value must be unique for each cluster member.

    The recommended naming sequence is "_server<Number>", where the resulting IOS log is named "ios_server<Number>.log". For example, if you have three application servers in your vertical cluster, your IOS logs are ios_server1.log, ios_server2.log, and ios_server3.log.

    If you don't set this value, IOS logs are written to ios.log by default.

    Note: The characters in the server name value must be valid file name characters for your OS.
  2. Navigate to the Server Infrastructure > Java and Process Management > Process Definition > Java Virtual Machine configuration. Add Lawson files and locations to the JVM classpath for the application server where Lawson is deployed. Use the literal path to your GENDIR, LAWDIR, and WAS_HOME. 
    WAS_HOME/plugins/javax.j2ee.jta.jar
GENDIR/java/jar/lawsonrt.jar
GENDIR/java/jar/lawsec.jar
GENDIR/java/thirdParty/secLS.jar
LAWDIR/system
WAS_HOME/plugins/javax.j2ee.servlet.jar
WAS_HOME/plugins/javax.j2ee.jsp.jar
WAS_HOME/plugins/javax.j2ee.el.jar
    Starting from LSF Feature Release 9 and later, GENDIR/java/thirdParty/secLS.jar is no longer added to the JVM classpath for the application server. And instead require the code:
    WAS_HOME/plugins/javax.j2ee.jta.jar 
GENDIR/java/jar/lawsonrt.jar 
GENDIR/java/jar/lawsec.jar 
LAWDIR/system 
WAS_HOME/plugins/javax.j2ee.servlet.jar 
WAS_HOME/plugins/javax.j2ee.jsp.jar 
WAS_HOME/plugins/javax.j2ee.el.jar
    Note: Information about supported versions of products is included in this document as a convenience. Because product support might have changed since this document was published, you will find the majority of product support information in the Infor Software Compatibility Matrix for Infor Lawson Products document available on Infor Concierge.
  3. On the same screen, in the Generic JVM arguments field, specify this information:

    -Xshareclasses:name=LAWSON_Environment,groupAccess,nonfatal -Xscmx50m

    where Environment is your environment name, for example, LSFPROD1

  4. For each application server running Lawson, define the following Lawson variables in the Server Infrastructure > Java and Process Management > Process Definition > Environment Entries configuration window.
    Environment variable Value
    GENDIR Literal path to GENDIR for your Environment
    LAWDIR Literal path to LAWDIR for your Environment
    LADBDIR Literal path to LADBDIR for your Environment
    PATH

    The literal path to:

    /QSYS.lib/LAWENVNAME.lib

    where LAWENVNAME is the Environment library name.
    LAWENVNAME Use the same value to be used for the Environment name when you install this Lawson product
    LAWIPC Use the same value to be set for LAWIPC when you install this Lawson product
  5. In the WebSphere Administration Console, select your application server name. Under Server Infrastructure > Java and Process Management, select Process Execution:

    • In the Run as user field, enter the name of the user you created to run WebSphere.

    • In the Run as group field, enter QEJBSVR.

    • Save your changes.

  6. If you are using WAS with IPv6, refer to the steps below:
    1. For the Deployment manager, navigate to System Administration > Deployment manager > Java and process management > Process definition > Java virtual machine > Custom Properties.
    2. Set the java.net.preferIPv6Addresses syntax to java.net.preferIPv6Addresses=true.
    3. For the Node agent, navigate to System Administration > Node agent > nodeagent > Java and process management > Process definition > Java virtual machine > Custom Properties .
    4. Set the java.net.preferIPv6Addresses syntax to java.net.preferIPv6Addresses=true.