Release Notes for FileNet Report Manager 5.0a

Release Date: June 14, 2007

This document describes conditions and issues that you must be aware of when installing, configuring and using the FileNet Report Manager 5.0a software. The standard operation of the application is described in the Report Manager documentation.

Note: All changes of Report Manager 5.0, Report Manager 5.0 Patch 1 and Report Manager 5.0 Patch 2 have been rolled into Report Manager 5.0a. Future patches will be provided for Report Manager 5.0a only, hence user must upgrade to Report Manager 5.0a from Report Manager 5.0.

Contents

Known Issues and Limitations

Known Issues and Limitations

Using multiple Storage Services to load from a common load directory is not supported

While using multiple Storage Services (loading stations) to load documents, each Storage Service should have its own separate load directory. Using multiple Storage Services to load documents from a common load directory is not supported as it may cause duplicity of data.

Service Controller requires a hidden share 

The Service Controller requires a hidden shared folder for each Storage Service (loading station) it controls in a distributed environment. The Report Manager installer creates this hidden share to allow the Service Controller to access the Storage Service settings file on the remote loading station(s). The hidden share is also used to store/update the scheduler settings. By default, the hidden folder name is RM_SS_CONFIG_SHARE$, but it may have derivatives such as RM_SS_CONFIG_SHARE<XXX>$, where XXX is a number.

If you want to install Traffic/Storage server in a distributed environment, you must specify the storage path as a UNC path name.

While working with extracted data from Database View on Report Manager Desktop, the header information does not display on files saved in the .csv format. User may need to manually insert a row and enter the header information from the source data.

Silent installation does not create local users (DTS 151188)

Silent installation does not create local users during installation .If silent installation of Report Manager Services is performed using a local user, the user should be created on the system before installation and added to the Administrators group. You also need to make the user be able to "log on as a service". The steps to do this are:

1. Click Start -> Control Panel -> Administrative Tools -> Local Security Policy.
2. In the left pane, under the Local Policies node, select User Rights Assignment.
3. Double-click the "Log on as a service" policy in the right pane and add the user.

After adding the user, ensure that you run the Windows Services applet (services.msc) and associate the user and password to each Report Manager service installed.

"Run Once" specification must be uniform on the same loading station (DTS 151826)

The current release of Report Manager only supports multiple scheduler settings files on the same loading station with the same specification for the "Run Once" option. In other words, either all the settings files on the same loading station should have the "Run Once" option selected, or all of them should have this option unselected. You have to use different loading stations if you want to have the "Run Once" option selected for some settings files and unselected for the others.

Dependencies of Storage Service and Index Service on Traffic Service are getting removed on modifying the setup (DTS 204326)

Storage Service and Index Service are dependent on Traffic Service ie. these services will run only if Traffic Service is running. If user installs Report Manager 5.0a with Custom/StandAlone setup type, modifies the setup and removes the services from feature tree and then again modifies the setup and to select these services from feature tree, then dependency of Storage Service and Index Service is not set on Traffic Service. Although dependency on Traffic Service is removed but Storage Service and Index Service will only work if Traffic Service is running.

Silent installation of Standalone setup works only if Desktop component is also selected (DTS 209705)

Silent installation of Standalone setup type only works if Desktop component is also selected from the feature tree.

Feature tree gets disabled while modifying Custom setup after silent installation (DTS 209602)

After doing silent installation of Custom setup type, when user tries to modify this setup through Add/Remove programs, the feature tree gets disabled. Due to this user is not able to modify the installed setup.

Modification of any setup type of Report Manager does not work when Report Manager database is not collocated and SQL server authentication is used (DTS 209591)

While modifying any setup type of Report Manager when Report Manager database is not collocated and SQL server authentication is used then the SQL server validation fails. Following are the workarounds for this issue:

• User can go back and use windows authentication instead of SQL server authentication to validate SQL server.
• If user already has SQL server installed on the local system then user can use the local database credentials for SQL server validation.

Changing the system Data Source Name (DSN) while upgrading Report Manager 4.1 / 5.0 to Report Manager 5.0a generates an error.

An error "Failed to find dll function: PRM_INIT.fnDeleteDataSource" occurs when user tries to change the system DSN while upgrading Report Manager 4.1/ 5.0 to Report Manager 5.0a. For example, at the time of Report Manager 4.1/ 5.0 installation, DSN specified is "PRMTables", but while upgrading to Report Manager 5.0a if user tries to change the DSN from "PRMTables" to "PRMTables1" then upgrade fails. It is therefore recommended that user should not change the DSN while upgrading Report Manager 4.1/5.0 to Report Manager 5.0a.

Maximum number of documents that can be loaded into Report Manager system

Report Manager 5.0a can store a large number of documents. The current limitation is 2 billion and IBM is investigating a candidate future enhancement to allow an even higher number of 4 billion documents.