Fix readme for 2.0.0.1-IBM-IMA-IFIT18788

Content

Fix: 2.0.0.1-IBM-IMA-IFIT18788
Date: January 26, 2017
Build: 20170125-2116

IBM MessageSight 2.0.0.1 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:

Component	md5sum	File
Server	f6abe4079ba4972d673d9b66f8171fff	2.0.0.1-IBM-IMA-IFIT18788-Server.tz
WebUI	5ce2bd36ff190197137a6bf4a8663b9d	2.0.0.1-IBM-IMA-IFIT18788-WebUI.tz

APARs fixed in this build:

APAR	Description
IT18788	2.0 migration code won't migrate appliances with old server version in config file
IT18986	CA cert soft links broken after migration to 2.0
IT18993	Reordering policies in WebUI has no effect

Before you install:

We recommend performing a backup before upgrading the firmware:

Backup and restore

Installing 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.

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.