Change the default shared resource location for Installation Manager

-

Question

When installing WebSphere Process Server through the launchpad, can I change the default shared resource location?

Answer

Yes. You can change the default shared resource location by using the following procedure.
The following steps are for new installations. If you already have installed and want to change the shared resource location, you will have to uninstall and reinstall after following these steps.

Steps

1. Locate the default shared resource. Depending on whether you are an administrative (root) or non-administrative (non-root) user, find the default shared resource location in one of the following tables.


Administrative or root users

Platform Default Location for shared resources
AIX /usr/IBM/BPMShared
HP-UX /opt/IBM/BPMShared
Linux /opt/ibm/BPMShared
Solaris /opt/IBM/BPMShared
Windows <ProgramFiles>\IBM\BPMShared



Non-administrative or non-root users

Platform Default Location for shared resources
AIX <HOME>/IBM/BPMShared
HP-UX <HOME>/IBM/BPMShared
Linux <HOME>/ibm/BPMShared
Solaris <HOME>/IBM/BPMShared
Windows <APPDATA>\IBM\BPMShared



2. Modify the <imageLocation> /launchpad/content/userExtensions.js file, where <imageLocation> is the location of the installation image of WebSphere Process Server.



3. Replace the existing defaultSharedPlugins() and defaultSharedPlugins_nonroot() functions with the following versions updated with your preferred location, <NEW_SHARED_LOCATION>.


function defaultSharedPlugins()
{
      var sharedLocation='<NEW_SHARED_LOCATION>';

      return sharedLocation;
}

function defaultSharedPlugins_nonroot()
{
      var sharedLocation='<NEW_SHARED_LOCATION>';
      return sharedLocation;
}


Changing the install location of other Installation Manager resources






Popular posts from this blog

Shrink you container size up to 95%.

-
BLAFS is a bloat-aware filesystem for container debloating. The design principles of BLAFS are effective, efficient, and easy to use. It detects the files used by the container, and then debloats the container by removing the unused files. The debloated containers are still functional and can run the same workload as the original containers, but with a much smaller size and faster deployment. https://github.com/negativa-ai/BLAFS?tab=readme-ov-file
Read more

alma linux: dnf Module yaml error: Unexpected key in data

-
While applying recent updates to a server running Rocky Linux 8, an error presented itself. Module yaml error: Unexpected key in data: static_context [line 9 col 3] Module yaml error: Unexpected key in data: static_context [line 9 col 3] The solution turned out to be a simple one. Update the libmodulemd first to correct the problem then perform the dnf updates as usual. dnf update libmodulemd For a detailed explanation as to the cause of this problem.
Read more