Fix Readme
Abstract
The IBM Tivoli Monitoring Event Synchronization utility has a new update which replaces previously installed versions.
The last update was identified as 6.30.00.08 (3.0.0.8) and was last updated in ITM 6.30 FP7 Service Pack 9 (and later).
The new update, shipped as part of 6.30 FP7 SP22 (and later) includes the following changes:
- A new installer. InstallAnywhere is now used to install the product, which supports newer Java Runtime Environments (JREs).
- Updated JRE. The JRE shipped has been upgraded to 64-bit IBM JRE version 21.0.5.
- On Windows, the utility used to register the code as a Windows service(part of Situation Update Forwarder) has been updated which supports more current versions of Java.
- The base runtime code has not changed, and the associated configuration files haven not changed.
Content
(C) Copyright International Business Machines Corporation 2025. All rights reserved.
Component: Event Synchronization 6.3.0.1.0 (3.0.1.0)
Date: November 18, 2025
Date: November 18, 2025
IBM(R) Tivoli(R) Monitoring Tivoli Event Synchronization Install to 3.0.1.0
Contents:
1.0 General description
2.0 Problems fixed
3.0 Architecture and prerequisites
2.0 Problems fixed
3.0 Architecture and prerequisites
4.0 Image directory contents
5.0 Installation instructions
6.0 Install Logs
7.0 Repair and Uninstall
8.0 Known problems and workarounds
9.0 Additional product information
10.0 Copyright and trademark information
11.0 Notices
12.0 Change History
1.0 General description
The IBM Tivoli Monitoring Event Synchronization utility has a new version which replaces previously installed versions.
The last update was identified as 6.30.00.08 (3.0.0.8) and was last updated in ITM 6.30 FP7 Service Pack 9 (and later).
The new version is 6.30.01.00, is included as part of 6.30 FP7 SP22 (and later) and includes the following changes:
- A new installer. InstallAnywhere is now used to install the product, which supports newer Java Runtime Environments (JREs).
- Updated JRE. The JRE shipped has been upgraded to 64-bit IBM JRE version 21.0.5.
- On Windows, the utility used to register the code as a Windows service (part of Situation Update Forwarder) has been updated which supports more current versions of Java.
- The base runtime code has not changed, and the associated configuration files haven not changed.
2.0 Problems fixed
The previous installer used 32-bit JREs which required 32-bit system libraries which are no longer preloaded on newer operating systems (such as Linux RedHat 9).
The previous installer would not work with newer JREs.
IV79357: SITUATION UPDATE FORWARDER PRISTINE INSTALL ERROR ON WINDOWS WHEN SPACE IN DIRECTORY NAME.
The previous installer could not install the Windows service successfully if there was a space in the installation path name.
3.0 Architecture and prerequisites
This update is supported on AIX, Linux, zLinux, and Windows.
3.0 Architecture and prerequisites
This update is supported on AIX, Linux, zLinux, and Windows.
Support for HP-UX and Solaris has been discontinued.
3.1 Prerequisites for this fix
The previous install of Event Synchronization needs to be uninstalled before this update can be
installed. See section 5.1 for uninstall steps depending on your configuration.
4.0 Image directory contents
The install images can be found in the IBM Tivoli Monitoring 6.3.0 Fix Pack 7 Service Pack 22 or later.
It is located under the TOOLS and tec directory. For example:
6.3.0.7-TIV-ITM-TOOLS-SP00<nn>/tec directory where <nn> is 22 or higher.
There is an install image for each platform:
AIX: Esynch3010_Install_AIX.bin
Linux: Esynch3010_Install_Linux.bin
Windows: Esynch3010_Install_Win.exe
zLinux: Esynch3010_Install_zLinux.bin
5.0 Installation instructions
This fix can not be installed over an existing installation. Since a new installer is used, this installation is treated as a new install.
5.1 Uninstall Previous Install
5.1.1 Backup existing configuration files
Backup files in <Event Sync Install Path>/etc
These are the configuration files for Situation Update Forwarder and the monitoring servers that it connects to.
The format of these files has not changed in the newer version; the files will be regenerated during the installation.
Backup files in <Event Sync Install Path>/etc
These are the configuration files for Situation Update Forwarder and the monitoring servers that it connects to.
The format of these files has not changed in the newer version; the files will be regenerated during the installation.
5.1.2 Uninstall the previous install
Run the uninstaller in <Event Sync Install Path>/uninstaller.bin.
Run the uninstaller in <Event Sync Install Path>/uninstaller.bin.
When uninstalling the Event Synchronization using the uninstaller.bin, if the following
message is displayed, follow the steps in the link below to uninstall it manually.
message is displayed, follow the steps in the link below to uninstall it manually.
Initializing InstallShield Wizard...
...........................
..A suitable JVM could not be found. Please run the program again using the option -is:javahome <JAVA HOME DIR>
...........................
..A suitable JVM could not be found. Please run the program again using the option -is:javahome <JAVA HOME DIR>
See documentation "Uninstalling event synch manually" for
https://www.ibm.com/docs/en/tcamfma/6.3.0?topic=SSDKXQ_6.3.0/com.ibm.itm.doc/itm_install375.html
https://www.ibm.com/docs/en/tcamfma/6.3.0?topic=SSDKXQ_6.3.0/com.ibm.itm.doc/itm_install375.html
NOTE: On Windows, there is an additional step to uninstall to ensure the Tivoli Situation
Update Forwarder Windows service is stopped and deleted. A new service will be installed as part
of the new install, so the existing Windows service needs to be stopped and deleted.
Update Forwarder Windows service is stopped and deleted. A new service will be installed as part
of the new install, so the existing Windows service needs to be stopped and deleted.
After ensuring the Tivoli Situation Update Forwarder has been stopped, remove the service:
SC delete situpdate
SC delete situpdate
5.2 Install New Update
Install the appropriate version based on the operating system (see section 4.0 Image directory contents).
- InstallAnywhere supports installing via GUI, console, or silent install.
It will default using the GUI mode. To install via the console or silent
install they can be specified using the options "-i console" and "-i silent".
It will default using the GUI mode. To install via the console or silent
install they can be specified using the options "-i console" and "-i silent".
- When entering the ITM Monitoring Servers (TEMS) using the GUI, the installer will
prompt for up to 10 TEMS servers. After entering information for one, a new screen
will prompt for the next one. If no data is entered it will skip additional prompts
and take you to the installation summary to start the install.
- Configuration data is saved in the <Event Sync Install Path>/etc directory using the
same filenames and formats as the previous versions.
same filenames and formats as the previous versions.
- OMNIBus .sql files
In general, the .sql files which are manually copied from the
<Event Sync Install Path>/omnibus directory and loaded into
OMNIbus, do not need to be updated. With one exception,
these .sql files have not changed in this newer version
and so do not need to be updated on OMNIbus (manually).
In general, the .sql files which are manually copied from the
<Event Sync Install Path>/omnibus directory and loaded into
OMNIbus, do not need to be updated. With one exception,
these .sql files have not changed in this newer version
and so do not need to be updated on OMNIbus (manually).
The exception is if the bi-directional support is being used and
the install path of the new Event Synchronization install is different than
the original install directory. In that case, the itm_proc.sql file will need
to be updated as during the install several variables in the file are updated
with the installation path.
the install path of the new Event Synchronization install is different than
the original install directory. In that case, the itm_proc.sql file will need
to be updated as during the install several variables in the file are updated
with the installation path.
See the following documentation for steps to install the itm_proc.sql file:
https://www.ibm.com/docs/en/itcam-app-mgr/7.2.1?topic=unotmatt-updating-omnibus-database-schema-single-tier-aggregation-tier-objectservers-2
6.0 Install Logs
Installation logs are located under the new <Event Sync Install Path>/_Event_Synchronization_installation/Logs directory.
https://www.ibm.com/docs/en/itcam-app-mgr/7.2.1?topic=unotmatt-updating-omnibus-database-schema-single-tier-aggregation-tier-objectservers-2
6.0 Install Logs
Installation logs are located under the new <Event Sync Install Path>/_Event_Synchronization_installation/Logs directory.
7.0 Uninstall or Repair
7.1 Uninstall or Repair
Before uninstalling or repairing the installation, if using the bi-directional support, the Situation Update Forwarder process/service should be stopped. This is done using the command:
Windows: <Event Synch Install Dir>\bin\stopSUF.cmd
UNIX/Linux: <Event Synch Install Dir>/bin/stopSUF.cmd
Once the Situation Update Forwarder has been installed, the following can be run to uninstall or repair the product:
Windows: <Event Sync Install Director>\_Event_Synchronization_installation\Uninstall_Event_Synchronization.exe
UNIX/Linux: <Event Sync Install Director>/_Event_Synchronization_installation/Uninstall_Event_Synchronization
Windows: <Event Sync Install Director>\_Event_Synchronization_installation\Uninstall_Event_Synchronization.exe
UNIX/Linux: <Event Sync Install Director>/_Event_Synchronization_installation/Uninstall_Event_Synchronization
If run with the GUI, the following prompt will appear:
- Repair Product
- Uninstall Product
- Repair Product
- Uninstall Product
If run with the command line, the product will be uninstalled.
The Uninstall Product option will remove the files from the directory and from the internal database the installer uses to keep track of what is installed. Any files updated or created after the initial installation will not be deleted. On Windows, the uninstall will also stop the Tivoli Situation Update Forwarder service and then delete the service.
The Repair Product option will reinstall the files. This can be useful in the case where a file has been inadvertently deleted or gotten corrupted. It will not prompt for any of the dialogs but will reinstall the files based on the input used during the original installation. The Repair option does not update the files in the jre directory but will update the files in the other directories.
The prompt to repair or uninstall the product will also appear if the installation is run again after the utility has been previously installed.
7.2 Manual Uninstall
If there is an issue uninstalling the product using the method in section 7.1, it could be related to a corrupt file where InstallAnywhere keeps track of what is installed.
1. Stop the Situation Update Forwarder and ensure it has stopped.
Windows: <Event Synch Install Dir>\bin\stopSUF.cmd
UNIX/Linux: <Event Synch Install Dir>\bin\stopSUF.sh
Windows: <Event Synch Install Dir>\bin\stopSUF.cmd
UNIX/Linux: <Event Synch Install Dir>\bin\stopSUF.sh
2. When Event Sync is installed, InstallAnywhere will store information about the installation
in a configuration database. It uses this file to keep track of what products are installed.
in a configuration database. It uses this file to keep track of what products are installed.
https://docs.revenera.com/installanywhere2021/Content/helplibrary/ia_ref_files_product_registry.htm
Backup the file and edit it to delete the <product> section containing "Event_Synchronization" and
<components> sections containing "Event_Synchronization", "eventsync.lvl", and "SitForwarder\jre".
Backup the file and edit it to delete the <product> section containing "Event_Synchronization" and
<components> sections containing "Event_Synchronization", "eventsync.lvl", and "SitForwarder\jre".
3. On Windows, run the <Event Synch Install Dir\bin\situpdate_delete_svc.cmd.
This will stop the Situation Update Forwarder Windows service (situpdate) and remove it as a Windows Service
8.0 Known Problems and Workarounds
When running the installation in console mode, the Password and Confirmation prompts are duplicated. For example:
Password: Password:
At this point, enter the password and continue. The prompt duplication does not cause a problem installing the update. This is an InstallAnywhere issue and will be resolved in the future.
On UNIX and Linux, if the installation path contains a space, the scripts including startSUF.sh and stopSUF.sh will fail. As a workaround the files can be updated and double quotes can be placed around the value for the INSTALL_DIR variable. For example:
INSTALL_DIR="/opt/IBM/Sit Forwarder"
9.0 Additional Product Information:
On Windows, if the Tivoli Situation Update Forwarder was not stopped and deleted before the install of the new code, then the service will still contain older code. To check if this is the case, in the Windows services, if select the Tivoli Situation Update Forwarder and select Properties, under Path to executable, you see the entry contains the value "-Z "situpdate", for example
"C:/<Event Sync Install Path>/situpdate.exe" -Z "situpdate"
then this is an entry from the previous install and not the new install. If the new code has been installed, run the following scripts to stop, delete, reinstall and start the newer version of the Situation service:
<Event Synch Install Dir>\bin\situpdate_delete_svc.cmd
<Event Synch Install Dir>\bin\situpdate_install_svc.cmd
<Event Synch Install Dir>\bin\situpdate_delete_svc.cmd
<Event Synch Install Dir>\bin\situpdate_install_svc.cmd
When uninstalling the product, the language used will be the language selected at install time.
10.0 Copyright and trademark information
A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.
10.0 Notices
=======
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION
"AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Some jurisdictions do not allow disclaimer of express or implied
warranties in certain transactions, therefore, this statement may not
apply to you.
This information could include technical inaccuracies or typographical
errors. Changes are periodically made to the information herein; these
changes will be incorporated in new editions of the publication. IBM
may make improvements and/or changes in the product(s) and/or the
program(s) described in this publication at any time without notice.
errors. Changes are periodically made to the information herein; these
changes will be incorporated in new editions of the publication. IBM
may make improvements and/or changes in the product(s) and/or the
program(s) described in this publication at any time without notice.
Microsoft, Windows, and Windows Server are trademarks of Microsoft
Corporation in the United States, other countries, or both.
Corporation in the United States, other countries, or both.
Java and all Java-based trademarks and logos are trademarks or
registered trademarks of Oracle and/or its affiliates.
registered trademarks of Oracle and/or its affiliates.
UNIX is a registered trademark of The Open Group in the United States
and other countries.
and other countries.
Linux is a registered trademark of Linus Torvalds in the United States,
other countries, or both.
other countries, or both.
Other company, product, or service names may be trademarks or service
marks of others.
marks of others.
Third-Party License Terms and Conditions, Notices and Information
-----------------------------------------------------------------
The license agreement for this product refers you to this file for
details concerning terms and conditions applicable to third party
software code included in this product, and for certain notices and
other information IBM must provide to you under its license to
certain software code. The relevant terms and conditions, notices and
other information are provided or referenced below. Please note that
any non-English version of the licenses below is unofficial and is
provided to you for your convenience only. The English version of the
licenses below, provided as part of the English version of this file,
is the official version.
-----------------------------------------------------------------
The license agreement for this product refers you to this file for
details concerning terms and conditions applicable to third party
software code included in this product, and for certain notices and
other information IBM must provide to you under its license to
certain software code. The relevant terms and conditions, notices and
other information are provided or referenced below. Please note that
any non-English version of the licenses below is unofficial and is
provided to you for your convenience only. The English version of the
licenses below, provided as part of the English version of this file,
is the official version.
Notwithstanding the terms and conditions of any other agreement you
may have with IBM or any of its related or affiliated entities
(collectively "IBM"), the third party software code identified below
are "Excluded Components" and are subject to the following terms and
conditions:
may have with IBM or any of its related or affiliated entities
(collectively "IBM"), the third party software code identified below
are "Excluded Components" and are subject to the following terms and
conditions:
- the Excluded Components are provided on an "AS IS" basis
- IBM DISCLAIMS ANY AND ALL EXPRESS AND IMPLIED WARRANTIES AND
CONDITIONS WITH RESPECT TO THE EXCLUDED COMPONENTS, INCLUDING, BUT
NOT LIMITED TO, THE WARRANTY OF NON-INFRINGEMENT OR INTERFERENCE
AND THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE
- IBM will not be liable to you or indemnify you for any claims
related to the Excluded Components
- IBM will not be liable for any direct, indirect, incidental,
special, exemplary, punitive or consequential damages with respect
to the Excluded Components.
11.0 Change History
2025-11-18: Published
2025-11-24 Added section 4.0 Image directory contents
[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSTFXA","label":"Tivoli Monitoring"},"ARM Category":[{"code":"a8mKe000000TN31IAG","label":"General"},{"code":"a8m3p000000hBWgAAM","label":"ITM Event Management"}],"ARM Case Number":"","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"5.1.0;5.1.1;5.1.2;6.1.0;6.2.0;6.2.1;6.2.2;6.2.3;6.3.0"}]
Product Synonym
ITM
Was this topic helpful?
Document Information
Modified date:
24 November 2025
UID
ibm17242393