If you are a IBM® IoT MessageSight v2 (or above) customer
who is upgrading to Eclipse Amlen version 1.0, you will find that normal product
operation is almost entirely unchanged by the renaming of the product. Migration requires the same steps as
described in Migrating from IBM Watson IoT Platform Message Gateway to
Eclipse Amlen. Aside from the steps outlined
for IBM Watson IoT Platform Message Gateway,
users of IBM IoT MessageSight also need to be aware of the
following changes
1. The
systemctl enable command, which is used to start the product when the
operating system is started, has changed. The name of the program binary must be used instead of the
previous product name.
| Previous command |
New command |
systemctl enable IBMIoTMessageSightServer |
systemctl enable imaserver |
systemctl enable IBMIoTMessageSightWebUI |
systemctl enable imawebui |
systemctl enable IBMIoTMessageSightBridge |
systemctl enable imabridge |
The
systemctl disable command is affected in the same way.
Other systemctl commands, such as start,
stop or status can use either the previous name or the ima-
equivalent: imaserver, imawebui, or
imabridge.
2. The files of environment variables, which are used to create Docker containers, have been
renamed as follows:
| Previous name |
New name |
| IBMIoTMessageSightServer-docker.env |
imaserver-docker.env |
| IBMIoTMessageSightWebUI-docker.env |
imawebui-docker.env |
| IBMIoTMessageSightBridge-docker.env |
imabridge-docker.env |
The values of the environment variables themselves are not required to change.
3. Finally, the RPM files have been renamed as follows:
| Previous name |
New name |
| IBMIoTMessageSightServer-<version>.x86_64.rpm |
EclipseAmlenServer-<version>.x86_64.rpm |
| IBMIoTMessageSightWebUI-<version>.x86_64.rpm |
EclipseAmlenServer-<version>.x86_64.rpm |
| IBMIoTMessageSightBridge-<version>.x86_64.rpm |
EclipseAmlenBridge-<version>.x86_64.rpm |