IBM Support

Fix readme for 2.0.0.2-IBM-IMA-IFIT24598

Fix Readme


Abstract

This readme describes the contents and fixes included in new IFIX 2.0.0.2-IBM-IMA-IFIT24598

Content

Fix: 2.0.0.2-IBM-IMA-IFIT24598
Date: April 10, 2018
Build: 20180409-1808
IBM MessageSight 2.0.0.2 Cumulative Interim Fix

(Note: all MessageSight 2.x ifixes are cumulative. In addition, because of the nature of the fix packaging for 2.0, any published fix can be used for the base install of MessageSight. It is recommend to install the latest IFIX or FP as the initial install of the product.)

Fix:

Componentmd5sumFile
Server23ba31dafce8afae020ad09a239dbd942.0.0.2-IBM-IMA-IFIT24598-Server.tz
WebUI88e9eebb9c81265289a2686ad4dcbe692.0.0.2-IBM-IMA-IFIT24598-WebUI.tz



APARs fixed in this build:


APARDescription
IT24598Update Java for PSIRTs CVE-2018-2579 CVE-2018-2602 CVE-2018-2603 CVE-2018-2641 CVE-2018-2582 CVE-2018-2633
IT24614Standby crash during failover on server with more than 128 GB of RAM
IT24613Performance fix for must gather script
IT24587must gather script captures sensitive information
IT24612Update Liberty to 18.0.0.1


Before you install:

We strongly recommend performing a backup before upgrading the product software:

Backup and restore instructions

Preparing to install the fix:

1. Prepare the IBM IoT MessageSight .tz files for installation.

For more information, see Preparing the IBM IoT MessageSight .tz packages for installation.

Installing the fix in an rpm environment:

2. Updating the MessageSight Server package if Server is installed:

cd imaserver
sudo yum -y --nogpgcheck update IBMIoTMessageSightServer*.rpm
systemctl start IBMIoTMessageSightServer

3. Updating the MessageSight Server package if the WebUI is installed:

cd imawebui
sudo yum -y --nogpgcheck update IBMIoTMessageSightWebUI*.rpm
systemctl start IBMIoTMessageSightWebUI

(NOTE: these packages can also be installed using:
rpm -Uvh IBMIoTMessageSight*.rpm

However, you must never update using:

yum install IBMIoTMessageSightServer*.rpm

or uninstall and reinstall with rpm or yum (if you wish to preserve your existing data), since this will remove all of your data and config under /var/messagesight.)

OR:

Installing the fix in a Docker environment:

2. Build the IBM IoT MessageSight Docker image.

Build the IBM IoT MessageSight server image by issuing the following command:

cd imaserver
mv *.rpm imaserver.rpm
docker build --force-rm=true -t imaserver:2.0 .

3. Build the IBM IoT MessageSight Web UI image by issuing the following command:

cd imawebui
mv *.rpm imawebui.rpm
docker build --force-rm=true -t imawebui:2.0 .

4. Stop the existing containers.

Stop the server container by issuing the following command:

docker stop <server_container_name>

where <server_container_name> is the name of the container in which the IBM IoT MessageSight server is running. For example,

docker stop IMA

5. Stop the Web UI container by issuing the following command:

docker stop <webui_container_name>

where <webui_container_name> is the name of the container in which the IBM IoT MessageSight Web UI is running. For example,

docker stop IMAWEBUI

6. Remove the containers.

Remove the server container by issuing the following command:

docker rm <server_container_name>

where <server_container_name> is the name of the container in which the IBM IoT MessageSight server was running. For example,

docker rm IMA

Remove the Web UI container by issuing the following command:

docker rm <webui_container_name>

where <webui_container_name> is the name of the container in which the IBM IoT MessageSight Web UI was running. For example,

docker rm IMAWEBUI

7. Remove the old MessageSight images.

Remove the IBM IoT MessageSight server image by issuing the following command:

docker rmi -f $(docker ps | grep imaserver | awk '{print $3}')

Remove the IBM IoT MessageSight Web UI image by issuing the following command:

docker rmi -f $(docker ps | grep imawebui | awk '{print $3}')

8. Start the containers. Use the same Docker run command that you used previously before applying the update.

For example, to start the IBM IoT MessageSight server container, use a command similar to the following command:

docker run --cap-add SYS_ADMIN --net=host -P -it --name=IMA -env-file=IBMIoTMessageSightServer-docker.env -m <memory> -v /mnt/messagesight:/var/messagesight -v /mnt/tmp:/var/tmp -d imaserver:2.0

To start the IBM IoT MessageSight Web UI container, use a command similar to the following command:

docker run --cap-add SYS_ADMIN --net=host -P -it --name=IMAW --env-file=IBMIoTMessageSightServer-docker.env
-m <memory> -v /mnt/messagesight:/var/messagesight -v /mnt/tmp:/var/tmp -d imaserver:2.0

Verifying the installation:

If this is your initial install of the product see Configuring the licensed usage for IBM IoT MessageSight and accepting the license by using REST Administration APIs for accepting the product license.

If this is an update, then you can verify the status of the server see Viewing the status of an IBM IoT MessageSight server and services by using REST Administration APIs.

[{"Product":{"code":"SSCGGQ","label":"IBM MessageSight"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Maintenance","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"2.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
17 June 2018

UID

swg22015376