Autostart links are created even if startup type is manual

On UNIX / Linux, the startup links for all components (cala_rex, FSM server and FSM GUI) are created even if startup type is set to manual.

Solution

Remove the superfluous startup links manually after installation.

The month selection in the Scheduling tab is sometimes incorrect

If the selection of the start or end date in the Scheduling tab is changed, the corresponding end or start date sometimes has the wrong month selection.

Example: Open an editor with Scheduling tab (e.g. Reporting Input Editor). Select start date = "31 Jan", period = "2 months". End date is set automatically to "31 Mar". Now change period to "1 month" without changing other fields. End date is set to "29 Mar", expected end date is "29 Feb".

This is a known bug in the RAP date chooser: https://bugs.eclipse.org/bugs/show_bug.cgi?id=288164

Solution

Adjust the date selection manually.

Default user for automatic task execution does not work when using LDAP authentication

With FP1 a default user "cala_rex" and password is defined in the finca-cfg.xml for use with automatic and scheduled task execution. This user works only when FSM internal authentication is used. If LDAP authentication is configured, the user must be a LDAP user or user "admin".

Solution

User must be added on LDAP manually.

Severity Icons button in Server Configuration Console is not displayed in RCP

The Severity Icons button that toggles the display of the severity icons in the Business View is not visible in the RCP GUI.

Solution

Use the RAP GUI to toggle display of the severity icons in the Business View.

Exception in RCP when opening a report request

When you try to open a report request in the RCP GUI, an exception is thrown.

Solution

Use the RAP GUI to view and edit report requests.

Business View does not show any icons in RCP

The Business View does not show any icons when using the RCP GUI.

Solution

Use the RAP GUI to see icons in the Business View.

Text decorators in tree do not work in RCP

In the User Preferences, it is possible to define a text decorator for tree items that shows the number of events with the highest severity for each tree node (e.g. [3C]). These text decorators are not displayed in the RCP GUI.

Solution

Use the RAP GUI to see the text decorators in the tree.

Apply Changes button in Server Configuration Console does not work in RCP

When you perform changes in the server Configuration Console in the RCP GUI, the changes are not applied when pressing the Apply Changes button.

Solution

Use the RAP GUI to change settings in the Server Configuration Console.

Sometimes the splash screen won't disappear

Sometimes the gui service will only show the splash screen after startup, and the login screen won't appear, neither when the browser is refreshed, nor another browser is used. This is a problem of the RAP framework.

Solution

Restart the gui service.

XML Config Files cannot be transferred.

When there is a completely Configured JPS monitur and the user wants to store it via menu 'File > Save monitor configuration to client...'.

Since the JPS configuration file is very individual, and would not match anyway on another client in most cases, we decided not to fix this problem, until the new clients are implemented.

Solution

The xml files can be copy pasted manually from one file system to the other file system. As mentioned: In most cases the monitor configurations would not match anyway on another client / environment.

Different web-browsers provide different search results in online help

If you search for a specific key word in the web application's online help, the help provides different search results (chapters), depending on the web browser, which is used. Since the online help is not implemented by us, but provided by the framework, we assume, that this will be fixed in RAP version 1.4.

Solution

The PDF documentation contains the same help, as the online help. The text search of the PDF viewer can be used to find more specific results.

cosst.exe fails on older Windows 2003 and Windows XP versions

The command line tool cosst.exe fails on Windows 2003 that doesn't have at least Windows 2003 SP1 applied and on Windows XP without applied XP SP2 or newer.

Solution

Update the Windows system to the minimum supported Service Pack or use cosst.exe from version 4.0.1

swapSpace monitor on AIX requires root

The Swapspace monitor doesn't run on non-root AIX CALA installations.

Solution

Run the monitor as root or add the sticky bit to the pstat binary

CALA's logctlcmd command on Windows 2008 does only work when run under the same user as the CALA service.

When running the CALA command logctlcmd manually on Windows 2008, the command must be run under the same user as the service. It won't work when started under an other user and will also break subsequent calls of logctlcmd under the service user. (You will need to restart the CALA service to make it work again.)

Solution

None

Update of cala_rex removes setting for CALA_DIR from set_cenit_env.sh

The update process of cala_rex recreates the file $CENIT_ROOT/set_cenit_env.sh. Because the setting of CALA_DIR is added to this file by the CALA installation process only, updating just cala_rex will remove the CALA_DIR entry and the CALA administration scripts will stop working.

Solution

Re-add the setting of CALA_DIR manually to $CENIT_ROOT/set_cenit_env.sh.

This is only required if you do not update CALA as well.

It is not possible to monitor a service where the display name contains German umlaute.

It is not possible to monitor a service where the display name contains German umlaute, e.g. "Dienst für virtuelle Datenträger (VDS)". The (windows shell) awk command fails to search for the string.

Solution

Replace the German umlaute with regular expression wildcards, e.g. . (dot): "Dienst f.r virtuelle Datentr.ger (VDS)"

File jmx_classpaths.prop is overwritten during client update

The $CENIT_ROOT/cala/monitors/pam/jmx_classpaths.prop file is overwritten by CALA client installer if the option "Reconfigure only" is not selected. Changes made via task "Configure JMX Classpath" or manually to the file are overwritten.

This causes JMX monitors to fail if the classpath was extended before to make them work.

Solution

Create a backup of the file before updating the CALA client. After the update, merge your changes into the new file created by the installer.

Monitoring Manager saves escalation table content and name, even if the Cancel button is pressed

If the name of the escalation file is changed or the contents of the specified escalation file is changed within the Monitoring Manager, the changes are done even if the edited monitor instance is closed without saving (pressing the X or Cancel button).

This behaviour cannot be changed in this version of the Monitoring Manager but will be changed in the next implementation of this administrative GUI.

Solution

Use unique escalation files names in the case of copying monitor instances within the Monitoring manager to minimize the risk of this behaviour.

When specifying custom execution hours over midnight the monitor stops running at midnight.

When specifying execution hours crossing midnight, e.g. 16-8 if the monitor should run from 16:00 till 8:59, the monitor stops working at midnight.

Solution

Specify execution hours in this format: 16-23,0-8

Oracle variable TNS_ADMIN not evaluated by Oracle monitors, connect fails

When starting CALA out of a user's (fnsw) crontab, the .profile of this user is not sourced. If the .profile contains the user variable TNS_ADMIN pointing to a different location than $ORACLE_HOME/network/admin the tnsnames.ora will not be found and the connect to the database will fail with error "ORA-12154: TNS:could not resolve service name".

The search order for tnsnames.ora is:

Solution

Create a special CALA start script containing this varaible and use this instead of cala.sh inside the crontab.

Task Execution Manager may hang if custom tasks generate huge output

Custom tasks that generate huge output or that run on several systems at once and the combined output is huge (>4096 Byte) can cause the Task Execution Manager to hang.

Solution

If a custom task creates huge output, write the output to a file instead of directly to STDOUT or do not run the task on high number of systems at once.

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

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.

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.

At least one logfile must be activated on FSM client

If only monitors are activated for a FSM client, the installation fails with an error message.

Solution

In the client configuration, select at least one logfile or the Windows eventlog.

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.

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

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.

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.

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

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/IBM/FSM\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.

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*/.../....

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.

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

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.