Overview of best practices when applying patches in a Lawson Production Environment

When applying patches in a Lawson Production Environment, here are some best practices to keep in mind:

1. IPA Scheduled Tasks Overview (assuming your organization uses IPA)
   • Acquire or create an outline of all IPA scheduled processes between the patching window and update any documentation to refer to these.
2. Establish a Patching Window
   • If patching in TEST takes longer than the established window due to applying multiple patches, space out the patches on different days for PROD.
   • Some organizations run 24/7 globally so it’s best to notify managers of the established window so users will not open an abundance of tickets.
3. Pre-Patching Process
   • Stop IPA Grid from running scheduled flows
     • This ensures no users can run any jobs that could attempt to trigger IPA flows.
     • Open a command window and navigate to the landmark install directory
     • Enter.cmd
     • Command “adminlaw” — this will stop everything and not allow it to restart (stopping the service will sometimes restart on its own
   • Restart PROD LSF server
   • Stop websphere after reboot (or disable automatic services pre-reboot)
   • Turn Security OFF
4. Post-Patching process
   • Turn on Security
   • Turn on Websphere
   • Start IPA Grid
     • Command “startlaw”
   • Manually run and verify any missed IPA processes during downtime window.

This is a general overview and not meant to be applied to all organizations that may have several custom interfaces.

Good luck!