Change the install location for IBM Installation Manager

-

Question

When installing WebSphere Process Server through the launchpad, the IBM Installation Manager install location is defaulted. Can I change where this gets installed?

Answer

Yes. As long as there is not already an installation of IBM Installation Manager on the box, the default installation location for IBM Installation Manager can be changed by using the following procedure:

Steps


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

2. Replace the following lines within the existing writeIMInstallXML(was_home, cdLocation, isRoot) function:


+ "\<install\>"
+ "\<offering features=\'agent_core,agent_jre\' id=\'com.ibm.cic.agent\' version=\'" + IMversion + "\'/\>"
+ "\</install\>"

with the following lines updated with your preferred location, <NEW_INSTALL_LOCATION>. Note that it is required that the install location end with "eclipse":


+ "\<profile kind=\'self\' installLocation=\'<NEW_INSTALL_LOCATION>/eclipse\' id=\'IBM Installation Manager\'\>"
 + "\<data key=\'eclipseLocation\' value=\'<NEW_INSTALL_LOCATION>/eclipse\'/\>"
 + "\</profile\>"
 + "\<install\>"
+ "\<offering profile=\'IBM Installation Manager\'features=\'agent_core,agent_jre\' id=\'com.ibm.cic.agent\' version=\'" + IMversion + "\'/\>"
+ "\</install\>"

NOTE: Each new line of code within the userExtensions.js file that is being replaced starts with "+" symbol. You can just copy and paste the lines of code above into your copy of userExtensions.js and make the appropriate modifications.






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