Updating the Portal/S3 for Workspace WEBROOT

We updated WebSphere & IHS from 7.0 to 8.5 earlier this year, however we just found that our WEBROOT value for the Portal installation directory (/etc/lawson/portal) is pointed to the old instance of IHS. Everything else (lawson.env, httpd.conf) points to the correct location.

We installed a handful of Portal patches on this server last month and all of the files were placed in the old WEBROOT. Now we need to correct WEBROOT and move the patches to the correct WEBROOT.

We can update the /etc/lawson/portal/instances/lsf1/install.cfg and the etc/lawson/portal/cfg/lsf1.cfg with the correct WEBROOT to prevent future patches from going in to the old path, but I'm not sure of the best way to handle the patches that were applied last month.

The two routes we could go:
1. Remove patches
2. Change WEBROOT
3. Install patches

1. Change WEBROOT
2. Move files that were updated by the latest patches (referencing install.log for Portal)

I'd rather go with the second route because reinstalling the patches seems like an unecessary step. Does anyone have any recommendations or suggestions for this scenario?

Thanks!

logo-32.png

Find more posts tagged with

Infor Lawson Technology Group - Discussion

Comments

Steve Loader

We recently upgraded our LSF which included Portal installation and had the same problem. All we did was change the path to the install.cfg file which is located under your instance folder in (/etc/lawson/portal/instances) and reinstall portal and the patches and all worked fine.

unknown

It's nice to know that we're not alone!

Were you able to install the patch without uninstalling it first? Because the patch was technically already applied (to the wrong spot), I'm assuming that the java installer will recognize this and require that we uninstall it first.

FordUS_ship_req.pdf

Steve Loader

Yes we were able to reinstall the patch without uninstalling since java was now pointing to a different location.

Steve Loader

You will also need to reinstall the PortalWeb patches as well.

unknown

Thanks! I neglected to mention that, in our case, the installer had copied the /portal directory from our old to new instance - so, the base Portal files are already present. We've come up with a plan to move the individual .js and .htm files that the patches delivered to the new instance over re-installing, along with changing WEBROOT in our cfg files to avoid confusion on future patches.

Steve Loader

You are welcome and all the best.

Copyright © 2025 Infor. All rights reserved.