Due to AIX Shell issue monitors can fail

Due to a parsing issue within the AIX Shells (sh as well as ksh) some monitors fail with syntax error or other errors.

This happens on AIX 5.x and 6.1 systems. There is no AIX APAR available so far. To solve this issue within AIX follow the workaround instructions below.

Solution

Until an AIX APAR is released a custom shell needs to be used so run the FSM monitors and tasks. This is supported by FSM.

1) Install/update the FSM client with the latest CALA_REX client. 2) Re-install the FSM CALA Agent. In the 'Set configuration variables' specify the Shell (incl. full path) that should be used. Run the installation (you might want to select the 'Keep monitor settings checkbox) to complete the workaround.

The custom shell will be used until the value for the Custom Shell parameter is not cleared and the agent is re-installed again.

Note: It is recommended to use the BASH which IBM ships with the AIX Toolbox installation media.

Version number of CALA binaries does not match system information page

The version number of the CALA binaries (2.03-025) does not match the version number for the CALA package listed on the system information page (2.03-026). The is caused by the latest patch because the patch replaces some jar files that are part of the CALA package but does not replace the CALA binaries.

Solution

None

Solaris 10 syslog configuration during FSM client installation causes errors

The update of the Solaris 10 syslog configuration during FSM client installation causes an error on the Solaris 10 system.

Solution

Deselect (uncheck) syslog configuration by FSM on Solaris 10 systems unless this issue is solved within FSM. If Solaris 10 syslog monitoring is required the syslog deamon should be stopped before the FSM installation.

After startup / restart of CALA monitors can return -30 or ERROR_installation, if the system has got a very high load.

After startup / restart of CALA monitors can return -30 or ERROR_installation, if the system has got a very high load. Since FSM 4.0.1 FP2 a new functionality is implemented that limits the number of parallel executed IBM FileNet and Database command line tools to one instance each. If more monitors are running that need to execute the same commane line tool the monitor waits up to 150 seconds to proceed. If this period is not long enough this normally indicates an system issue.

Solution

Wait for the next monitoring schedule or change the execution period of some monitors to reduce the number of parallel running monitors.

IBM FileNet P8 4.5 Process Engine monitors fail due to Process Engine issues

P8 4.5 Process Engine monitors using vwtool can fail. At the same time VW/Process FNC ABORT2 errors are reported in ims_logs directory on the PE server. It is not clear what caused the issue. This behavior needs further investigation.

Solution

There is no known workaround available, the cause is not clear so far.

This behavior needs further investigation.

Searching for area and host results does not work in certain combinations

Certain combinations of host / areas result in empty areas even if there are events in that area for that host. Some areas show icons, others do not.

Solution

Use the link on the host-field to search for events of this host or use the link on the area-icon to search for events of this area.

Linux: cosst procinfo -l only returns 4096 characters per process

Due to a system limitation on Linux systems, cosst procinfo -l can only show the first 4096 characters from the command line of a process.

The following monitors and tasks may be affected:

IBM CM v8, CMOD, CSx and IICE archives:

IBM FileNet P8 4.x archives:

IBM FileNet P8 PE 3.x, PA 3.x archives:

IBM FileNet Image Manager 3.x and 4.x archives:

Standard archives:

Solution

None

HP-UX 10.20 and 11: cosst procinfo -l only returns 1024 characters per process

Due to a system limitation on HP-UX 10.20 and 11, cosst procinfo -l can only show the first 1024 characters from the command line of a process.

The following monitors and tasks may be affected:

IBM CM v8, CMOD, CSx and IICE archives:

IBM FileNet P8 4.x archives:

IBM FileNet P8 PE 3.x, PA 3.x archives:

IBM FileNet Image Manager 3.x and 4.x archives:

Standard archives:

Solution

None

Monitor Publishing Queue Entries does not work for object stores containing blanks

Due to restrictions in the FileNet Java API, the monitor Publishing Queue Entries does not work for object stores that contain blanks in the name.

Solution

None

Windows security policy may block access to directories containing a dot

On some Windows installations, the security policy does not allow access to directories that contain a dot. In this case, the FSM Java Webstart tools do not work because some of the required files are located in directories containing a dot (e.g. de.cenit).

Solution

Rename the affected directories (e.g. rename de.cenit to de_cenit) and adjust the jnlp files accordingly.

Sometimes gzip.exe is still running after installation on windows.

When installing FSM server or client on Microsoft Windows systems, it sometimes happens, that a gzip.exe process is still running after installation has completed.

This may cause problems with subsequent installs.

Solution

Kill the gzip.exe binary manually using the Windows task manager.

Custom name of database schema is lost during update from FSM 3.7 to 4.0.1

During update from FSM 3.7 to 4.0.1, the name of the database schema is lost if it has been customized. The original default value "FILENET" will be used instead. If the CALA server is installed with the default setting instead of the customized value, no new events will be shown in the console.

Solution

When updating the CALA on the FSM server, open the "Set configuration variables" dialog and adjust the entry in the field "Name of database schema".

Java 5 is required for patch FSM 4.0.1-001 and higher

Because of the new module SettingsBrowser, patch FSM 4.0.1-001 and higher needs Java 5 as minimum requirement on the FSM server as well as on all desktops where the SettingsBrowser component is used!

Solution

None

Reading ibm_cm8_eventlog events only works with standard port

Reading ibm_cm8_eventlog events from the tables ICMSTSYSADMEVENTS and ICMSTITEMEVENTS only works if the DB2 RDBMS uses the standard port 50000.

Solution

If the DB2 RDBMS uses a different port than 50000, the CALA configuration must be adjusted manually after each reinstall.

"Direct connection to Online Support" link in WebConsole

The value for "Direct connection to Online Support" link in the FSM WebConsole has changed. During an update of the FSM these value in the configuration-file $CENIT_ROOT/htdocs/conf/webtemplate.config.php will not be changed.

Solution

Change the value for the variable $supportURL in the file webtemplate.config.php manually to <a href="http://www.ibm.com/software/data/support/help.html" target="_blank">http://www.ibm.com/software/data/support/help.html</a>

Acknowledged events icon is not shown in overview pages after update.

The parameter to show acknowledge event icons in FSM WebConsole overview pages is set to "show" and the icon is not shown in these pages.

Solution

Change value for $defaultDateTime in database.config.php to '0001-01-01 00:00:00' for MySQL and IBM DB2.

Custom script monitors should not contain blank in path or file name

When defining custom script monitors with blanks in the path or the monitor file name itself (for example C:/Program Files/scripts/custmon1.cmd) the monitoring engine calamon will fail for this monitoring instance. Additionally the monitor definition table from the system can no longer be loaded by the Monitoring Manager GUI (CalaMoMa).

Solution

If it is required to define a monitor with blanks in the file or path name, the DOS name (sometimes called short name) needs to be used, for instance C:/PROGRA~1/scripts/custmon1.cmd.

CALA sometimes fails because files are in use

On some systems, CALA installation fails because files are in use by the running CALA processes and cannot be replaced by the installer.

Solution

Stop CALA before re-installing the client.

Connect to database under UNIX fails if webserver is running with an account which has $MAILMSG set.

If there is automatically output right before the shell prompt appears, e.g. "[YOU HAVE NEW MAIL]", the WebConsole will fail to connect to the database. Reason: The text before the prompt replaces the password string that is used in the dbConnect function.

Solution

Unset the variable or use a user which cannot receive mail (as documented).

Size of area pictures does not change automatically after editing settings.

After editing the settings for area images only new areas images have the new picture size. Existing area images do not change.

Solution

Edit each area via the management page or delete the images for the areas manually from the htdocs/images directory.

Length of duplicate detection key is limited

The duplicate detection has a limit of 64 characters per field used for the dupekey.

This means that duplicate detection filters out events that should not be filtered if an event field's value is the same in the first 64 characters but is different afterwards.

Solution

The maximum field length can be increased from 64 to 127 by setting the W127 flag in the dupekey description.

There is no way to increase the width to a value larger than 127.

Acknowledged events icon is not shown in overview pages after update.

The parameter to show acknowledge event icons in FSM WebConsole overview pages is set to "show" and the icon is not shown in these pages.

Solution

Change value for $defaultDateTime in database.config.php to '0001-01-01 00:00:00' for MySQL and IBM DB2.

CMOD log entries from the database have wrong timestamp

Content Manager On Demand log entries from the table SL2 in the CMOD database are always sent with the current time instead of the timestamp stored in the database.

Solution

None

The characters ' ' (blank) and '_' (underscore) are removed in the names of reports.

If users set report names with blanks or underscores, the reporting tool removes those characters according to internal name conventions. So reports names e.g. 'CPU Usage', 'CPUUsage' and 'CPU_Usage' are refered as the same and may overwrite each other.

Solution

Do not use report names that only differ in blanks and underscore.

Hostnames with (full qualified) length of 255 characters or more are currently not supported.

According to RFC 1035 a hostname including the network suffix may be up to 255 characters long. However CALA only supports 254 characters for full qualified hostnames.

Solution

Do not use full qualified hostnames longer then 254 characters.

Hostnames with (full qualified) length of 255 characters or more are currently not supported.

According to RFC 1035 a hostname including the network suffix may be up to 255 characters long. However the FSM WebConsole only supports 254 characters for full qualified hostnames.

Solution

Do not use full qualified hostnames longer than 254 characters.

Windows non-FileNet client has FileNet-specific filter

When installing a Windows non-FileNet client, the FileNet-specific filters for Windows event log events will be activated anyway. All entries from the Windows event log that are not FileNet-related will be dropped.

Solution

When installing a non-FileNet client, go to the Set cfg variables window and remove the entry in the field Filter for incoming events. This only needs to be done on initial install of a non-FileNet client.

Reporting tool might cause a Java stacktrace

Running the reporting tool with a Java version lower than 6, might cause printing a stacktrace as an event to the console or as an entry in Apache error log. This is probably a bug in 2D-rendering-classes of older Java versions. The result report should not be affected by this.

Solution

Use Java 6 or higher.

Monitor OracleNextExtent works for dictionary-managed tablespaces only

The OracleNextExtent monitor can only be used for dictionary-managed tablespaces. The system table entries for locally managed tablespaces do not provide information about extents. Starting with version 9.2, Oracle Corporation recommends usage of locally managed tablespaces.

See Oracle 9i Database Concepts and Oracle 9i SQL Reference for details about tablespaces and extent management.

Solution

None

Only uppercase letters are supported in company event table name.

The database table holding the events must be named in uppercase letters, lowercase letters are currently not supported. This is true for the FSM webconsole as well as for the CALA configuration.

Solution

Use company event table names consisting of uppercase letters only.

Antivirus / Spyware alert during FSM install

During FSM install some AntiVirus / Spyware tool alert a Tool-Wget Virus. For example McAfee detected the file C:/Program Files/FileNet/SysMon\shell\wget3048.rra when installing the Windows Client (cala_rex).

Solution

Stop the AntiVirus agent / Service during FSM client install and restart it after successful installation.

MS Windows: CALA update fails if service is selected in Services Control Panel

The FSM CALA Service (cala_srv) cannot be registered during update while the existing service entry is selected in the Services Control Panel. The installation logfile caladist.log shows one of the following messages:

1072 The specified service has been marked for deletion.

1075 The dependency service does not exist or has been marked for deletion.

Solution

Do not select the FSM CALA Service in the Windows Control Panel during CALA update.

User names or password with ';' or '#' are not supported.

User names or password of used OS or database accounts that contain semicolon (';') or hashes ('#') are not supported with FSM.

Solution

Another account or password should be used to configure FSM.

FSM 4.0.1 does no longer support starting and stopping of Application server instances.

FSM 4.0.1 no longer contains tasks to start and stop Application Server instances due to security enhancements.

Solution

If a corresponding functionality is requested within a P8 4.x environment a custom task can be realized to start and/or stop Application Server instances.

FSM 4.0.1 running with MSSQL as FSM database repository do not support double-byte characters.

Solution

Use MySQL as FSM DB until FSM fully supports multi-byte characters in combination with MSSQL.

FSM 4.0.1 Solaris, Linux and HP-UX based servers do not support DB2 FSM database repository.

Solution

Use MySQL as FSM DB until DB2 is supported or select Windows or AIX system in combination with DB2.

Listener Request Monitor for P8 4.0 cannot handle all Listener Paths

The Listener Request monitor cannot handle a Listener Path like /IS (mini)/.../... because the brackets ( and ) are not handled correctly.

Solution

Use a wildcard instead of the string containing brackets, e.g. /IS*/.../....

Custom views in event view are not updated when updating from 3.7 to 4.0

The custom views result in "Invalid query" after an update from 3.7 to 4.0 because the queries contain the old table names.

Solution

None

Monitor MySQLStatus reports error after upgrade from FSM 3.7 P03

The monitor MySQLStatus reports a usage error after upgrading FSM 3.7 P03 or earlier either to FSM 3.7 P04, FSM 4.0 or later. As soon as CALA is updated on the server with the option "Keep monitor settings", a usage error will be displayed in the Webconsole.

This happens because a new parameter "MySQL_hostname" has been added to the list of arguments of this monitor.

Solution

After updating CALA on the FSM server, load the monitor configuration of the server into CalaMoMa and add an additional parameter to the list of arguments of the MySQLStatus monitor. The field can be left empty as "localhost" will be checked by default.

SSLException in CalaTEMa if wrong Java is used

CalaTEMa may throw an SSLException and an embedded InvalidAlgorithmParameterException if more than one Java version is installed on the FSM server. This happens if the SSL communication of the Java that is found first in the search path is not compatible with the Java that is used by the CalaRex server.

Solution

Add or extend the <pathadd> entry in the file >server_installation_directory</cala_rex/cala_rex_srv.cfg and make sure that the path specified in that entry points to the same Java that is used by cala_rex.

Then restart cala_rex and CalaTEMa.

Name of start / stop script of Application server must not contain blanks

In the configuration plugin for Process Engine 3.5 and older, a start and a stop script can be given for an Application server. The filenames specified in these fields must not contain blanks, otherwise configuration will fail.

Solution

Use the short name (DOS name) of the file.

To determine the short name of a file, you can open a DOS box and execute the command <path_to_fsm_installation>/tools/cosst.exe shortname "<very long path/that contains blanks/and points to script>".

Misleading text in error messages from some monitors.

In some cases the text "ERROR writing into pipe" is appended to error messages sent by monitors. The message disappears if the original error is fixed.

Solution

None

Help and arguments missing for first monitor in archive

If you select a monitor archive, the Help button is disabled and no named parameters are available for the first monitor in the archive. If another monitor is selected, the Help button is activated again and the parameters are loaded correctly.

Solution

To configure the first monitor from an archive, select another monitor from the same archive, then switch back to the first monitor.

Event view looses filter and limitation when viewing the details of an event on IBM DB2 and MS SQL databases

When viewing an event, that was selected from the event view, the settings for the number of shown events and the filter settings are all gone.

Solution

MS Windows: logfiles cannot be deleted while ascfileread reads from them

Logfiles which are opened by ascfileread cannot be deleted on Windows platforms until ascfileread has been shut down.

Solution

Stop CALA, delete the file and restart CALA.