Change the IBM Installation Manager agent data location

-

Question

When installing WebSphere Process Server through the launchpad, the IBM Installation Manager agent data location is defaulted. Can I change where the agent data location gets created?

Answer

Yes. The default location for the IBM Installation Manager agent data location can be changed by using the following procedure:

NOTE: If IBM Installation Manager has already been installed you cannot change the agent data location. This procedure only changes the location when WebSphere Process Server is installing IBM Installation Manager for the first time.

Steps

  1. Obtain information from the IBM Installation Manager product documentation on the Agent data location. This information provides you the default location as well as what pieces of information are kept in the agent data location.

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

  3. Decide which of the following lines you need to modify based upon where you are installing and what user privileges you have:
    //IM install and import WAS
    import[windows]=['IM\\installc', '--launcher.ini', '%1', '-input', '%2', '-log', '%3']
    import[unix]=['IM/install', '--launcher.ini', '%1', '-input', '%2', '-log', '%3']

    //IM install and import WAS - non-root
    import_nonroot[windows]=['IM\\userinstc.exe', '--launcher.ini', '%1', '-input', '%2', '-log', '%3']
    import_nonroot[unix]=['IM/userinst', '--launcher.ini', '%1', '-input', '%2', '-log', '%3']

  4. Modify the appropriate line by inserting in the following text between the %3 and the ] at the end of the line. Replace <NEW_AGENT_DATA_LOCATION> with your preferred location:
    ,'-dataLocation','<NEW_AGENT_DATA_LOCATION>'



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