For this guide I will assume you're using Windows with Putty and XMing for your X11 forwarding. Please install those programs prior to proceeding if you'd like to follow this guide exactly as written.
When setting up a new installation of Portal or other IBM products we usually stick to CentOS for its compatibility to RHEL. You may find themselves in a similar situation, where prod environments are running on RHEL, but you may not want to provide licenses for temporary or for many different environments which do not need support in the same way a production environment requires. While CentOS is an excellent distribution, I have come across some very minor compatibility issues which are somewhat common when working with CentOS and IBM Installation manager.
One thing to consider during installation of CentOS is that I usually go with the "Infrastructure Server" option and I choose to add Java platform as an add-on. This is not 100% necessary, but I have found that it does save some time vs. using yum after the fact to install required package groups. After CentOS installation the first step towards making sure you are ready for IBMIM is to install xauth and something to test functionality. I normally use xeyes or xclock for testing purposes. To do this let's run the following commands:
# yum install xeyes
# yum install xauth
Once we have those installed, restart your SSH session and modify your Putty settings under Connection>SSH>X11 and ensure that X11 forwarding is enabled and Remote X11 authentication protocol is set to MIT-Magic-Cookie. After you have started a new session with the proper settings start XMing on your local machine and try running the following command which should bring up a clock through X11 forwarding:
If that brings up a clock then we are good to go with setting up InstallationManager itself.
IBMIIM Installation and Configuration
Transfer the IBMIM download to your server and unzip it. From within the unzipped directory run the following command to install IBMIM
# ./installc -acceptLicense
Next we need to modify 2 files within the /opt/IBM/InstallationManager/eclipse/ directory. If you do not modify these files then IBMIIM will freeze on several different screens when running through X11 forwarding. Modify IBMIM.ini as well as launcher.ini and add the following arguments underneath the -vmargs line:
At this point we should be good to start up IBM Installation Manager from /opt/IBM/InstallationManager/eclipse/ by running #./IBMIM. I have seen one other error when trying to run IBMIM on CentOS, specifically regarding a lack of certain GTK libraries for X11. This error is addressed in this technote from IBM, however their solution
did not resolve it for me on CentOS https://www-01.ibm.com/support/docview.wss?uid=swg21438774 I resolved this by running the following command:
# yum install gtk2-2.24.28-8.el7.x86_64