When installing a new IPA product line using the intall-lpa.pl command in Landmark, you may encounter the error “Security Class does not exist.” This will prevent the IPA environment from completing the install. To resolve this error, first run the command “scupdate <product line>”. This command will generate all the security classes needed for the new IPA product line. Then, rerun the install-lpa.pl command, and it should complete successfully.

Error messages (on the command line, and also found at LALOGDIR/managelpa_<pdl>.log)

Run the scupdate command and verify no errors

Complete the IPA product line install

 

If you perform a Java update on your Landmark server, and your JAVA_HOME location is moving, you will need to update the java location in several places in Landmark.

InforIONGrid

For the Grid, first open an administrator command window and navigate to GRID_HOME/grids/<grid name> and run the “ChangeJDK.cmd” command with the NEW location of Java:

Next, open the Grid Management Pages. Go to Configuration > Grid Configuration > Grid Properties. Select Property “Java Executable (Path)”. Set the Java path to the new location under your grid host.

Landmark

For Landmark, set the JAVA_HOME and LAW_JAVA_HOME environment variables to the new location. It is also a good idea to update LAW_JAVA_HOME in the LASYSDIR/install.cfg file for future patches.

Finally, open an administrator command window and set the Landmark environment variables. Navigate to the NEW java location. Run the command java -jar %LAENVDIR%/java/jar/bcinstall.jar. Verify that this command adds the bouncycastle provider to the java.security file located at JAVA_HOME/jre/lib/security. Also, verify that the command copies the “bcprov” jar to JAVA_HOME/jdk/jre/lib/ext. If either of these tasks is not completed, you can handle them manually.

Run a stoplaw/startlaw and restart the grid. Or, better yet, reboot the server.

To verify that the new java location is being used by all the application systems, open task manager, and add the “Command line” header under the details screen. Verify that all “java.exe” processes are running from the correct location. You are now safe to uninstall your old java instance.

 

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!