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.
If your WebSphere deployment manager, node agent, or application server will not start, it can be a good idea to flush the WAS temporary directories and cached files.
First, stop all your IBM processes.
Then, back up the existing configurations for all profiles:
- On a administrator command window, navigate to WAS_HOME/profiles/<profile>/bin
- Run command backupConfig <backupfilepath>
Next, rename the following directories (or remove them, but it’s safer to rename):
- WAS_HOME/profiles/<profile>/wstemp
- WAS_HOME/profiles/<profile>/temp
- WAS_HOME/profiles/<profile>/config/temp
- Again, you should do this for ALL your profiles
Now, delete the javasharedresources directory located at C:\Windows\System32\config\systemprofile\AppData\Local\
Now, run the commands to clear the cache:
- Navigate to WAS_HOME/profiles/<profile>/bin
- Run command osgiCfgInit
- Run command clearClassCache
Once again, perform ALL of these steps for ALL your WebSphere profiles.
Have you come across the Lawson Add-ins Query Wizard Error – “There might be a mismatch with the server and product line you chose”?
This error occurs when you’ve logged into Lawson query wizard and opened up your dme script and the product line in the dme file is incorrect.
To resolve this error, locate your .dme file, right-click it >> Open with >> Notepad (or your own text editor)
In the file on the first line, you should see the product line, in our example it is TEST10 and needs to be changed to PROD10
Simply change the TEST10 to PROD10, select File >> Save
Open the dme file again in excel and the mismatch error should be resolved.
When applying patches in a Lawson Production Environment, here are some best practices to keep in mind:
- 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.
- 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.
- 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
- Stop IPA Grid from running scheduled flows
- 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!
You have a Lawson Business Intelligence Smart Notification report that needs users email devices added to it. In order to create one, follow the steps below.
- Login to LBI and go to Tools Dashboard >> Smart Notifications
- Go to Personal Settings and select Delivery Devices
- Under Delivery Devices at the bottom right click “Add Device”
- The General Info is the name of the device while the Delivery Method should be the actual email address of the user.
- Note that the default type and template are usually fine for most reports and organizations
- Click Add after you’ve filled in the proper info
- The delivery device (email address) will be sent a 4-digit confirmation code which you will need to enter here and click “Update”.
- You can start adding the email device to notifications before confirming the device.
You’re updating Lawson add-ins and running into this error when accessing addins in excel.
To resolve this error follow these steps:
- Open Excel and go to File >> Options
- In Excel Options click on Add-ins Tab
- Under Manage: Select Excel Add-ins and click Go…
- Unselect any Lawson Add-ins “exceldrill.xla” files and then press Okay:
- Repeat steps 1 and 2, in Manage: select COM Add-ins >> Go… and unselect any Lawson Addins selections that path to *.xla files
- After doing this, restart excel and you should no longer receive the exceldrill.xla errors. A successful install should show the below under COM Add-ins.
Done!
