— LiveStream

Installing IBM InfoSphere Information Server 8.1.1 on AIX means staging the 8.1.0 base, raising the Update Installer to a current build, applying the prerequisite rollup patches in the right order, fixing the WebSphere bootstrap-port mismatch that breaks the patcher, then layering the Information Analyzer 8.1.1 upgrade on every tier. This guide walks the full sequence with the exact AIX commands, the errors you will hit, and how to verify each step.

The IBM InfoSphere Information Server 8.1.1 stack is a three-tier suite (Domain/services, metadata repository, and one or more engine tiers) running on WebSphere Application Server. A clean upgrade depends almost entirely on getting the patch prerequisites and the WebSphere ports right, so most of the work below is preparation, not the final product install.

Heads-up: 8.1.1 is end-of-life

Information Server 8.1 and its Information Analyzer module are long past IBM support. If you are building something new, deploy a supported release such as InfoSphere Information Server 11.7 (the last classic IIS) or move to the containerized IBM Cloud Pak for Data DataStage/Information Governance services. The 8.1.1 procedure here is for maintaining or migrating an existing legacy environment where an in-place upgrade is the only safe path. Everything below is documented for that real-world case; do not stand up a fresh 8.1.1 farm in production.

What you are upgrading and why order matters

The environment in this walkthrough has three AIX hosts, each owning a tier:

• vdapdsdv18 — Domain and services tier (the WebSphere/ISF instance the others authenticate against).
• vdapiadv18 — Information Analyzer engine tier.
• bshdbdv10 — DataStage engine tier.

You cannot jump straight to Information Server 8.1.1. The 8.1.1 module is delivered as a patch on top of a 8.1.0.0 base that has been brought current with the Update Installer and several mandatory rollups. Apply patches on the Domain/services tier first, then the engine tiers, because the engine patchers connect back to the Domain to authenticate and register the change in Version.xml.

Step 1 — Confirm the 8.1.0 base and Java environment

On each tier, set a sane environment before touching the installer. The base ships its own JRE, so a missing java on the PATH is normal; you do not install a system JDK.

1. Set the file-creation mask so installed files get correct permissions:
   umask 022
2. On AIX, relax the JIT and mixed-mode tuning that can crash the bundled JVM during install:
   export JITC_COMPILEOPT=NALL
export IBM_MIXED_MODE_THRESHOLD=100
3. Point the X display at your workstation's X server so the GUI installer can draw (start an X server such as Xming/MobaXterm locally first):
   export DISPLAY=172.17.107.154:0.0
4. Verify the current product and Update Installer levels:
   /is/IBM/InformationServer/Updates/bin/versionInfo.sh

You should see Information Server version: 8.1.0.0. The Update Installer line will vary per host (for example 8.1.0.141 or 8.1.0.150) — that is the component you upgrade next.

Step 2 — Upgrade the Update Installer (updater.jar)

The patches for 8.1.1 require a newer Update Installer than what shipped with the base. The installer is a single JAR, updater.jar, and you replace it in place. Always back up the existing JAR first so you can roll back to the exact build that produced the current install history.

1. On each tier, back up the current installer, tagging it with its version:
   cd /is/IBM/InformationServer/Updates/bin
cp -p updater.jar updater.jar_8.1.0.141
2. Copy in the newer updater.jar from your patch staging directory:
   cd /mnt/iisv8.1/patches_8.1.1
cp updater.jar /is/IBM/InformationServer/Updates/bin
3. Verify the file landed and check its size against the source:
   ls -l /is/IBM/InformationServer/Updates/bin/updater.jar

Use the same updater.jar on every tier. Mixed installer builds across the Domain and engines is a common cause of patches that succeed on one host and fail on another.

Step 3 — Apply the prerequisite rollup patches

Before the 8.1.1 product upgrade, several rollups must be present. These fix the metadata repository (XMETA), the Metadata Workbench, the connectors, and the istools components so they are compatible with Information Analyzer 8.1.1. Stage them in one directory, for example /mnt/iisv8.1/patches_8.1.1. A typical AIX patch set includes:

Connector and platform-specific archives ship as .tar (AIX) or .zip (Windows). Un-tar the AIX one and discard the Linux variants (Red Hat / SUSE) you will not use, so the patcher does not pick the wrong platform package.

Run the patcher from an X-Windows session with a clean environment:

1. umask 022
2. Clear any AIX large-page or loader tuning that can starve the JVM:
   unset LDR_CNTRL
echo $LDR_CNTRL (should print an empty line)
3. export DISPLAY=172.17.107.154:0.0
4. Launch the installer:
   cd /is/IBM/InformationServer/Updates/bin
./InstallUpdate.sh

You can also run it non-interactively by passing the suite and WebSphere credentials on the command line, which is the reliable way to script the engine tiers:

./InstallUpdate.sh -user isadmin -password <is_password> -wasadmin wasadm -waspassword <was_password>

Apply the patches in the documented order — istools and XMETA first, then Metadata Workbench and connectors. Apply the XMETA and Workbench patches on the Domain/services host (vdapdsdv18) first, then repeat the relevant ones on the DS engine (bshdbdv10) and IA engine (vdapiadv18).

Step 4 — Fix the WebSphere bootstrap-port error

The most common failure when patching an engine tier is the installer failing to log in to the Domain. You will see something like:

javax.security.auth.login.LoginException: A communication failure occurred while attempting to obtain an initial context with the provider URL: "iiop://vdapdsdv18:2825"

The message warns that a bootstrap address with no port defaults to 2809. The root cause is a mismatch between the BOOTSTRAP_ADDRESS port WebSphere is actually listening on and the port the registered ISF profile expects. A standalone IIS WebSphere profile commonly listens on 2809, but this domain was configured for 2825.

Diagnose which port is really live with netstat:

1. On the Domain host, check what is listening:
   netstat -an | grep 2809
netstat -an | grep 2825
2. A line in LISTEN state on the wildcard address (*.2825 ... LISTEN) is the active bootstrap port. ESTABLISHED lines are the engines connected to it.
3. Set the WebSphere BOOTSTRAP_ADDRESS back to the value the ISF profile expects (here 2825, not the 2809 default) in the WAS profile's port configuration.
4. Recycle the whole stack after the port change — restart the Domain/services server (vdapdsdv18), then the engine servers (vdapiadv18 and bshdbdv10) — so every tier re-reads the corrected port.
5. Confirm the engines now connect on the right port:
   netstat -an | grep 2825 should show ESTABLISHED sessions from each engine to the Domain.

Once the bootstrap port is consistent across the suite, re-launch ./InstallUpdate.sh and the prerequisite patch will install cleanly. Repeat the patch run on both engine servers.

Step 5 — Verify each patch via Version.xml

Every successful patch appends a <Sequence> entry to /is/IBM/InformationServer/Version.xml. This file is your authoritative install ledger — check it after every patch instead of trusting the GUI alone.

1. View the file (read-only, so you do not accidentally corrupt it):
   cd /is/IBM/InformationServer
view Version.xml
2. Confirm a new <Sequence> with status="Success", the correct patch= name, and a rollback= path. For example, a connectors rollup shows up as patch="rollup_CC_v1-0_aix_81" ... status="Success", and the Workbench rollup as patch="rollup_MWB_PROD00155910_all_8100" ... status="Success".
3. The rollback= directory under /is/IBM/InformationServer/Updates/ is what the Update Installer uses to back the patch out — keep it until the upgrade is fully validated.

Step 6 — Install the Information Analyzer 8.1.1 upgrade

With the base current and every prerequisite rollup showing Success, you can apply the actual Information Analyzer 8.1.1 upgrade. The AIX upgrade package is delivered as a tar plus an .ispkg:

• IA-811-upgrade-aix.ispkg — the AIX upgrade package
• Info_Anlyzr_LU_8.1.1.tar — the language/upgrade bundle (un-tar and keep only the AIX content)
• ia811_release_notes.html — read this for any environment-specific notes

1. Un-tar the package and remove the Linux (Red Hat / SUSE) variants you do not need.
2. Set the same clean environment as before (umask 022, unset LDR_CNTRL, export DISPLAY=...).
3. Run the upgrade on the IA engine server (vdapiadv18) with credentials supplied inline:
   cd /is/IBM/InformationServer/Updates/bin
./InstallUpdate.sh -user isadmin -password <is_password> -wasadmin wasadm -waspassword <was_password>
4. When it completes, re-check Version.xml for the 8.1.1 sequence with status="Success".

At this point the install of Information Analyzer 8.1.1 is done. Validate by logging into the Information Server console and confirming the IA module reports the new level.

Common pitfalls

• Skipping the updater.jar refresh. The 8.1.1 patches need a newer Update Installer; an old updater.jar fails with cryptic packaging errors. Upgrade it on every tier first.
• Bootstrap port left at 2809. If the ISF profile expects 2825, the login fails. Always reconcile the WAS BOOTSTRAP_ADDRESS with what netstat shows before patching engines.
• Patching engines before the Domain. Engine patchers authenticate against the Domain/services tier — upgrade and verify that tier first.
• Wrong platform package. Leaving Red Hat/SUSE files in the AIX staging directory lets the installer choose the wrong build. Remove non-AIX variants.
• No DISPLAY / no X server. The GUI installer silently fails to launch if DISPLAY is unset or no X server is running on your workstation.
• AIX loader tuning. A stale LDR_CNTRL can starve the bundled JVM — unset it for the patch session.
• Not backing up updater.jar or trusting the GUI. Keep the old JAR and treat Version.xml as the source of truth.

Verification checklist

1. versionInfo.sh reports the expected product and Update Installer levels on every tier.
2. Version.xml contains a status="Success" sequence for each rollup and for the 8.1.1 upgrade.
3. netstat -an | grep 2825 shows the engines in ESTABLISHED sessions to the Domain.
4. The Information Server web console authenticates and the Information Analyzer module shows 8.1.1.
5. A simple IA analysis job runs end-to-end against the engine tier without repository errors.

Key Takeaways

• Upgrade updater.jar on every tier before applying any 8.1.1 patch, and back up the old one.
• Apply prerequisite rollups (istools, XMETA, Metadata Workbench, connectors) in order, Domain tier first, then engines.
• The iiop://host:2825 LoginException is a WebSphere bootstrap-port mismatch — reconcile the port with netstat and recycle all tiers.
• Version.xml is the authoritative install ledger; confirm status="Success" after every patch.
• Information Server 8.1.1 is end-of-life — use it only to maintain legacy systems; build new on 11.7 or Cloud Pak for Data.

Frequently Asked Questions

Why does InstallUpdate.sh fail with an iiop LoginException on port 2825?

The patcher cannot reach the Domain's WebSphere naming service. It happens when the WAS BOOTSTRAP_ADDRESS port does not match what the ISF profile registered. Use netstat -an | grep 2825 and grep 2809 to find the live LISTEN port, set the bootstrap port to the expected value, recycle the Domain and engine servers, then retry.

Do I need to install a JDK before running the Information Server installer on AIX?

No. The suite ships its own JRE under the install tree, so which java returning nothing is expected. You only set AIX JVM tuning variables such as JITC_COMPILEOPT=NALL and IBM_MIXED_MODE_THRESHOLD=100, plus DISPLAY for the GUI.

In what order do I apply the 8.1.1 patches?

Refresh updater.jar first, then apply the rollups (istools, XMETA, Metadata Workbench, connectors) on the Domain/services tier, verify each in Version.xml, then repeat on the DS and IA engine tiers, and finally apply the Information Analyzer 8.1.1 upgrade on the IA engine.

Is IBM InfoSphere Information Server 8.1.1 still supported?

No. Version 8.1 is end-of-life and out of standard IBM support. Maintain it only for legacy systems; for new deployments use Information Server 11.7 or the DataStage and governance services in IBM Cloud Pak for Data.

If you found this AIX install walkthrough useful, subscribe on YouTube @explorenystream for more hands-on sysadmin and DevOps guides.