General Information on IIM:
- IBM Installation Manager replaces the ISMP installer and Portal Update Installer (PUI) and manages life cycle for WAS 8 and WP 8. IIM can install and uninstall core products, update or rollback fixpacks and fixes, modify and remove features
- IIM version 1.5.2 or higher required
- Silent install supported on all platforms. GUI mode supported ONLY on Windows/Unix platforms. Command line supported ONLY on z/OS.
- Can record a response file without actually installing the product either by manually editing a sample response file that comes with the media or record one using IIM.
- IIM is composed of a binary directory (from where you run the product) and a data directory (logs are recorded here).
- IIM cleans up everything after a failed install. Need to create a log.properties with debug lines to pause IIM on a failure. This will allow for time to collect logs.
- When viewing IIM logs for a Portal 8 install, use a browser to open the index.xml file from the IIM logs location for better formatting of the logs. You will need the log.xsl file in the same directory.
- To uninstall IIM, for GUI navigate to IM_DATA_DIR/uninstall/uninstall, for console navigate to IM_DATA_DIR/uninstall/uninstallc
General Information on WebSphere Portal 8 Installation:
- Portal 8 packaging comes from 3 sources: Live repository via Passport Advantage, physical DVD's, and electronic images.
- Can install WAS 32-bit on a 64-bit platform
- Can install to an existing WAS for any content offering. Express MUST install its own WAS.
- Using an advanced configuration, can change such options as context root, default home, profile name, etc.
- Content offerings (Enable, Extend, WCM and WCM SE) are an extended offering of WP 8 Server and cannot be installed without a WP 8 Server.
- WAS ND binary cannot be shared between multiple WP 8 Server offerings
Portal v8 Regular Offerings (Server, Enable, Extend, WCM, WCM SE)
- A repository contains the required parts for installation. For Portal, one needs WAS, Portal, content offering, and Setup repositories.
- Single set of Portal binaries for each content offering (Server, Enable, Extend, WCM, etc.)
- Provide up-sell from server to WCM offering without reinstall
- Select all required iFixes for WAS 126.96.36.199 when installing Portal 8
- Extract all electronic images to the same directory.
- Setup disk is unique to each offering. It's different for Server, Enable, Extend, etc. If installing all at the same time, make sure to have the correct assembly.
- There is no tracing or logging with launchpad.
- Always choose the repository.config from the setup disk, <Setup_Disk_location>/eimage, when chosen, there are no prompts for individual disks over choosing the repository.config from individual offerings (WAS, Portal, Portal Offering).
- For iSeries ONLY, change Portal profile to 64-bit JVM SDK. Requires WAS managesdk task and ConfigEngine modify-jvm-heap-size and swith-64bit-lum-file tasks.
Things to Avoid:
- Windows XP and Windows 2003 are NOT supported with Portal 8
- For installing as non-root, apply PM64484
- WAS 8 ND can be uninstalled while leaving Portal 8 installed. This will leave a broken Portal server that will not work. Do NOT do this.
- Launchpad does not appear in user's language. Run 'setup LaunchPadLocale xx' where "xx" is fr, es, de, etc.
- WAS 8.5 Liberty profile will not work with Portal because it does not contain WebContainer. Need to install WAS with 'Full Profile'.
- May need clean up of some directories after uninstalling Portal and WAS. Should only be a remaining AppServer directory. This is expected.
Portal v8 Express Offering
- Supported only on Windows, Linux, iSeries. Now supports 32-bit and 64-bit on Windows/Linux. 32-bit is only on 32-bit, 64-bit is only on 64-bit.
- Must install WAS with Portal. Cannot install to an existing WAS.
- No advance install – ports, profile name and context root are default
- Install DB2 v9.7 under the covers
- Does NOT support clustering except for Idle-Standby function
- Available in trial version. Timesout after 60 days. If you buy the full version, you can run a Config task that picks up the license and turns off the timeout. Don't need to do anything else.
- Only on Express will you be prompted for a DB2 user name and password.
- Full install only, no base or custom installs.
Things to Avoid:
- For Express, make sure a failed install is cleaned up. Especially true because of DB2 user id's.
Things to Avoid:
- On Windows, need to have C drive present. Don't have to install C drive, it just needs to be present.
- In trial version, if the <PortalServer root>/bin/lum/files get lost, Portal will not start up. Need to restore from backup or electronic image.
- May need to first blank out password fields on the DB2 user id and password panel if you decide to change the user id.