High Availability (Mirroring) on IBM i for LANSA

Date:20 January 2015
Product/Release:LANSA for iSeries V12 & V13
Abstract:Some suggestions on how to set up High Availability (Mirroring) on IBM i for LANSA
Submitted By:LANSA Technical Support
Updated:20 January 2015

When setting up High Availability (or Mirroring such as Mimix or Maxava) with LANSA, it is as much about the objects that you don’t duplicate as the ones you do. Certain files will cause problems if duplicated on the backup system.

LANSA
Duplicate all LANSA system and Partition libraries and IFS folders, including your image folders (for Web applications etc.). For further information, refer to Transferring Complete LANSA Systems between IBM i Systems in the Introduction to LANSA for iSeries guide.

LANSA License

Version 13
Unless the mirror system has the same serial number, model, etc, then the /LANSA_<program library>/license/x_lic_<model>_<serial number> file, located in the IFS, for that machine should not be mirrored.
The data area <pgmlib>/DCXALIC should not need to be mirrored (located in the LANSA Program Library).
See the following for more information on License Consolidation: Consolidating LANSA licenses into a central location in V13.

Version 12
You should exclude the data in the source LANSA files DC@F72 and DC@F86 as part of the mirroring or backup. (located in the LANSA Data Library)

Model B Web
In addition to the above you can exclude the following:
DC@W13 - session info
http server job
lweb_wsrv job

Model A Web
You should exclude:
DC@W05 - http server job#, lweb_job#
DC@W07 - runtime bl data
DC@W18 - timedout bl data
DC@W19 - restart links
DC@W21 - timed out web jobs

WAMS
You can exclude:
DC@WSD - Session Data
DC@WSF - Session Fields
DC@WSS - Session

Apache error logs
The Apache error logs can be omitted
/LANSA_<program library>/webserver/www/logs/access*
/LANSA_<program library>/webserver/www/logs/error*

These IFS folders can be omitted too
/LANSA_<program library>/log
/LANSA_<program library>/support
/LANSA_<program library>/tmp

LANSA Integrator
If you use LANSA Integrator, the following objects, if they exist, should not be backed up from the source IFS directory to the target IFS directory. These files will be automatically recreated when you start JSM on the target system. Furthermore, duplicating these files on the backup system is likely to cause problems.
Note: some or all of these objects may not exist as they are dependent on the version of LANSA Integrator being mirrored.
     /LANSA_<program library>/jsm/instance/temp/

     /LANSA_<program library>/jsm/instance/www/instance/logs/

     /LANSA_<program library>/jsm/instance/system/
        lansakey.txt
        clauth1
        clauth1.dll
        clauth2
        clauth2.dll
        lsprst7
        lsprst7.dat
        lsprst7.tgz
        ssprs
        ssprs.dll
        ssprs.tgz
        ssprs.dat
        sysprs7
        sysprs7.dat
        sysprs7.tgz

Also, the LANSA Integrator trace files can be quite large and should be omitted. Note: the base trace folder in the jsm instance is required but all sub folders can be omitted.

That is, /LANSA_<program library>/jsm/instance/trace is required, but all folders under this can be omitted.