This Interim Fix solves issues in the monitoring and updates the Java WebStart tools.
The following issues are solved:
Issues in some CMOD monitors and their documentation.
The JARs of the Java WebSTart tools are signed with a new certificate, valid till September 08th, 2020.
Two issues in the product's ICN plug-in.
|
Requirements: ECM SM
5.2.0-005-001 requires fixpack 5.2.0-005. Note: Agents are affected by this interim fix and need to
be updated. The updated documentation can be downloaded from the IBM download pages. The interim fix will require temporarily up to 3 GB
of disk space on the drive or share the product is installed. |
Additional
information for the IBM Enterprise Content Management System Monitor can be
found as IBM ECM SM Field
Guides.
<server_installation_root> is the directory where the ECM SM
software is installed, e.g. C:/Program Files/IBM/ECMSM on Windows.
Steps 1 to 7 have to be repeated for all ECM SM servers in case of a
distributed ECM SM environment (multiple event server and / or gui server, download server)
1. Log on to the ECM SM server using an
administrative account, preferably the same account used to install ECM SM.
Note: If the ECM SM server is configured to use a MSSQL database using
Windows authentication, the user must be the technical user used during the
initial installation (database user).
Stop
all installed ECM SM components on the server (depending on the installation
type: EventServer, GUI, CALA_REX, CALA, Download Web
Server).
Commands shown are for a combined (single) server installation, in a
distributed environment it may be necessary to stop the "IBM ECM SM
Download Web Server" / downloadserver/downloadserver.sh too.
Unix
cd <server_installation_root>.
gui/IbmFsmRap.sh stop
eventserver/IbmFsmSrv.sh stop
cala_rex/cala_rex.sh stop
cala/cala.sh stop
agent/cala_rex/cala_rex.sh stop
agent/cala/cala.sh stop
Windows
Open
a command window.
cd <server_installation_root>
net stop "IBM ECM SM EventServer"
net stop "IBM ECM SM GUI Server"
net stop "IBM ECM SM CALA_REX Server"
net stop "IBM ECM SM CALA_REX Agent_srvagnt"
net stop "IBM ECM SM CALA Monitoring Agent"
net stop "IBM ECM SM CALA Monitoring Agent (cala_srv_srvagnt)"
2. Save all configuration files where
manual changes after the initial installation of the product were made. The
installation of the interim fix will recreate all config
files based on the setting during the initial or fixpack
installation (saved in <server_installation_root>/.prodinfo/FSM_SERVER.settings).
This interim fix will install a new configuration files. If manual adjustments
were made in the files <server_installation_root>/*/cfg/*.xml, these changes have to be redone in the newly
generated files.
3. Copy the interim fix file
ECM_SM-5.2.0-005-001.tar.gz to the <server_installation_root>
4. Extract the tar.gz archive to <server_installation_root>
on the ECM SM server.
Unix
cd <server_installation_root>
./jre/bin/java -cp
"./tools/com.trustice/javatar.jar:./eventserver/jars/de.cenit/finca.functional.utils.jar:./eventserver/jars/de.cenit/finca.logging.jar"
de.cenit.eb.sm.finca.functional.utils.tools.packaging.Untgz
"ECM_SM-5.2.0-005-001.tar.gz" "."
Windows
If
Windows authentication is used for the database access:
Set the environment variable "S_CALA_REX_USER_ORIG" with the value
found for this variable in the file <server_installation_root>/.prodinfo/FSM_SERVER.settings.
Example:
set S_CALA_REX_USER_ORIG=p845demo\fsmusr
Replace double backslashes with single backslashes.
Set the environment variable "S_CALA_REX_PASSWD_ORIG" with the
password for the above user.
Example:
set S_CALA_REX_PASSWD_ORIG=MyDbUserPW
cd <server_installation_root>
.\jre\bin\java.exe -cp
".\tools\com.trustice\javatar.jar;.\eventserver\jars\de.cenit\finca.functional.utils.jar;.\eventserver\jars\de.cenit\finca.logging.jar"
de.cenit.eb.sm.finca.functional.utils.tools.packaging.Untgz
"ECM_SM-5.2.0-005-001.tar.gz" "."
5. Execute the Interim Fix installer
script in <server_installation_root>.
Unix
sh ./install_interim_fix_520005001.sh
2>&1 | tee ./ECM_SM_SERVER_5.2.0-005-001_install_internal_installer.log
Windows
On
a combined or primary server:
install_interim_fix_520005001.cmd 2>&1 | shell\tee.exe ECM_SM_SERVER_5.2.0-005-001_install_internal_installer.log
On all other server types:
install_interim_fix_520005001.cmd 2>&1 | agent\shell\tee.exe
ECM_SM_SERVER_5.2.0-005-001_install_internal_installer.log
Wait till the prompt reappears (can take a few minutes), check the end of the logfile, it should look similar like this (the
"copied" messages appear only on combined, primary or download
server):
...
...
Creating file F:\ECMSM/.prodinfo/.prod-version from template
F:\ECMSM/.patchcontent/.prod-version: Starts ...
TRACE 2017-01-04 11:42:41 CET TRACE Execute CFG_FILE install action.
TRACE 2017-01-04 11:42:41 CET TRACE Process template:
F:\ECMSM/.patchcontent/.prod-version. Write to: F:\ECMSM/.prodinfo/.prod-version.
TRACE 2017-01-04 11:42:41 CET TRACE Finished template:
F:\ECMSM/.patchcontent/.prod-version. Write to:
F:\ECMSM/.prodinfo/.prod-version.
Creating file F:\ECMSM/.prodinfo/.prod-version from template F:\ECMSM/.patchcontent/.prod-version:
Passed.
TRACE 2017-01-04 11:42:41 CET TRACE Finished processing package: Z_PATCH
If an error happened, the installer stops at that point and the last entries in
the log should show the error.
6. Start all ECM SM Server components
if not already running.
Unix
cd <server_installation_root>
gui/IbmFsmRap.sh
eventserver/IbmFsmSrv.sh
cala_rex/cala_rex.sh
cala/cala.sh
agent/cala_rex/cala_rex.sh
agent/cala/cala.sh
Windows
Verify
using the Service Manager that the service "IBM ECM SM CALA_REX
Server" is set to the desired Startup Type (default is
"automatic") and the correct "Log On
As" account is assigned.
cd <server_installation_root>
net start "IBM ECM SM EventServer"
net start "IBM ECM SM GUI Server"
net start "IBM ECM SM CALA_REX Server"
net start "IBM ECM SM CALA_REX Agent_srvagnt"
net start "IBM ECM SM CALA Monitoring Agent"
net start "IBM ECM SM CALA Monitoring Agent (cala_srv_srvagnt)"
7. Verify that login to the ECM SM GUI
is possible and events with recent timestamps are received.
Check the version information in the Help menu, topic "About IBM
Enterprise Content Management System Monitor" details.
If the version number is cut off by the window border, resize the
"Version" column by pulling the right side marker of the column to
the right out of the window.
8. Update JRE on all agents
Make
sure all ECM SM agents are online by checking the "Connected Clients"
view in the "Client Administration" console.
Start
Task Execution Manager (e.g. by using the "Tools" menu).
Select
product "Migration", task "Install and Update CALA".
Select all clients from the list. Select options "Update binaries"
and "Keep monitor settings" ONLY!
The update can take a few
minutes. The monitoring agent (CALA) is restarted after the file transfers
finished.
This
task cannot
be used to update the CALA client that runs on Solaris 64 bit machines (ECM SM
server and clients).
9. If the installation was successful,
delete files <server_installation_root>/520005001.zip,
ECM_SM-5.2.0-005-001.tar.gz, install_interim_fix_520005001.cmd and
install_interim_fix_520005001.sh.
The following additional steps have to be performed when updating
from 5.2.0-003 to 5.2.0-005 on Microsoft Windows Server 2008 (non-R2).
The cosst.exe tool in IBM ECM SM 5.2.0 FP3 is not working for Windows 2008 non R2 Server installations. This will cause issues when updating the ESM Server or agent that run on such a version.
IBM can provide a working cosst.exe for that specific issue. Please contact your IBM support.
The following files must be exchanged prior to an update with next fix:
On the ESM Server:
<Installation-Directory>/agent/cala/cosst.exe
<Installation-Directory>/agent/tools/cosst.exe
<Installation-Directory>/cala/cosst.exe
<Installation-Directory>/tools/cosst.exe
On the ESM Agent:
<Installation-Directory>/cala/cosst.exe
<Installation-Directory>/tools/cosst.exe
The following abbreviations
are used:
· IBM APAR # IBM APAR Number
|
Call #: |
5096 |
|
IBM APAR #: |
PJ44865 |
|
Area: |
Problems when saving server settings in the ICN plug-in. |
|
Call #: |
5126 |
|
IBM APAR #: |
PJ44864 |
|
Area: |
ICN plug-in for ECM system monitor breaks scroll bars. |
|
Call #: |
5144 |
|
IBM APAR #: |
PJ44921 |
|
Area: |
Updated code signing certificate for the Java WebStart tools. |
This fix provides files to correct issues described above.