Resolving Lawson IPA Error: Unable to lookup RMI object
If you’re reviewing an Infor Process Automation log and notice the “Error: Unable to lookup RMI object rmi://localhost:16003/dbSecurity” or something similar firing on a FileAccess node, this means your bpm.ear config file got updated (possibly from an environment update) and needs to be fixed.
To resolve this, you’ll need to update the dbrmihostname field from “localhost” to the LSF server domain name in the bmp.ear file. See steps below.
To update the bpm.ear and bpm.war files follow the steps below:
- You must run the command from the same directory as where the bpm.ear file and bpm.war file exist:
cd %GENDIR%/assembly/products/bpm/jar
- Execute the perl script to rebuild the files, providing the new RMI port and hostname of your LSF machine:
- perl %GENDIR%/bin/updateArchive.pl <RMI_PORT> <HOSTNAME>
- Example: perl %GENDIR%/bin/updateArchive.pl 16003 lsfserver.domain.com
- Redeploy bpm.ear in WebSphere from the %GENDIR%/assembly/products/bpm/jar directory.
- Generate and Propagate the Plugin in WebSphere.
- Restart Process Flow.
- Restart the LSF WebSphere Application Server(s).
- Restart the web server.
Retiring Lawson, PeopleSoft, or Oracle? APIX archives the entire application — every table, every year, attachments and security included — into your own AWS account in about 30 days, so you can decommission the legacy system and keep full access to the history.
