Borland® Search 2009 Release Notes

Last updated: June 29, 2009

This file contains important information that may not appear in the documentation. Read this file in its entirety.

Note: The information in this readme represents the known issues at the time of this release. For late-breaking information that may become available after the release, check the Borland web site for the most recent version of this readme: http://info.borland.com/techpubs/starteam

For an overview of the new features in the current release, see the What's New topic in online Help or the About This Release section in Chapter 2 of the Borland® Search 2009 Administration Guide.

System Requirements/Prerequisites

The following are the hardware and software requirements for Borland Search.

Host server requirements

The hardware required for optimal Borland Search use depends on the amount of data you are extracting and the frequency of extractions. The hardware listed below is intended for a small to medium amount of data and a low frequency extraction schedule. It is recommended that you use Borland Professional Services to help define and configure the hardware and system requirements for a large data set with frequent extraction updates.

Host Server Software Prerequisites

• Sun JRE 1.6.0_13
  • Only requires the Java Runtime Environment (JRE)
  • Host server must have JAVA_HOME environment variable set for Tomcat to start properly.
  • The JAVA_HOME variable should be set to the directory into which you installed your JRE.
• Network access to all host servers being indexed.

Network Requirements

• The install location for Borland Search must have access to a supported data source. Examples of supported data sources include StarTeam server configurations and CaliberRM servers.
• The install location for Borland Search must be accessible to end users from their client workstations.

Client Computer Browser Requirements

• Microsoft Internet Explorer 7.0 or higher
• Firefox 2.0 or higher

Top

Known Issues

The following are known issues in Borland Search 2009.

Installation

• Do not run a previous version of Borland Search on the same machine as this new version.
• Do not copy Lucene indexes or re-use configuration files from a older release version of Borland Search.

Uninstalling from Windows Systems

Borland Search uses InstallAnywhere for installation. If you encounter one of the following error messages when uninstalling this product from a Windows system:

"Can't launch executable. Could not find a suitable Java Virtual Machine on your system."

or

"Windows error 3 occurred while loading the Java VM."

you may need to install JRE 1.6.0_13 from the disk, or download it from Sun. .

Apache Tomcat Server

• Memory use can be high for searches with very large indexes. If you get an "Out of Memory" exception, you might need to increase the Java VM heap size for Tomcat. You can set the Java VM heap size by changing the value of the JAVA_OPS variable in the catalina.bat or catalina.sh file. Example: -Xmx512m, where 512 would be replaced with the appropriate value for your situation.

Borland Search with MPX

• MPX is memory intensive, so Borland recommends that you use it only on the most urgent projects and that delta extractions be run regularly to ensure index validity.
• When using Borland Search with MPX it might be necessary to make the following adjustment on the CaliberRM server machine:
  1. On the CaliberRM server open the registry and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Borland\CaliberRM\{version}\Server\MPX.
  2. Replace the value of "Broker" and "Server" with the machine's ip address. Ensure Enable is set to 1.
  3. Restart the SQM Monitor service - do not restart SQM Database.

Borland Search MPX Listener

• The Borland Search MPX Listener application might not reconnect to MPX applications if connection to the server is unexpectedly lost. In this case, you will need to manually shutdown the MPX Listener application and then restart it.
• The Borland Search MPX Listener application requires a large amount of memory. To reduce the amount of memory required, use the ListenToList property in mpx.properties. Using the ListenToList property you can specify only your most critical StarTeam Views to be listened to.

CaliberRM/StarTeam (Windows Only)

• To use the Admin Console for starting CaliberRM/StarTeam processes, you must modify the catalina.bat file as follows:
  1. Locate the catalina.bat file within the Tomcat installation; for example: D:\TomCat\apache-tomcat-5.5.23\bin\catalina.bat.
  2. Open the catalina.bat file for editing.
  3. Add the following lines just after the large remark block at the top of the file:

     rem ***********************************************************
     rem * REQUIRED FOR ACCESS TO BORLAND SEARCH WINDOW'S DLLs *
     rem ***********************************************************
     set CURR_WRK_DIR=%CD%
     set DLL_DIR=%CURR_WRK_DIR%\..\webapps\bss\bin\windows\dll
     set PATH=%DLL_DIR%;%PATH%
     echo Using CURRENT WORKING DIRECTORY: %CURR_WRK_DIR%
     echo Using PATH: %PATH%
     rem ***********************************************************

  4. Save the catalina.bat file.
  5. Restart the Tomcat process.
• If the tomcat process is started as a service, the absolute path to the 'YOUR_ABSOLUTE_PATH\webapps\bss\bin\windows\dll' directory must be added to the system path, before any CaliberRM or StarTeam entries.

Security

• Cached Security Provider can get out of sync with updates to Borland Search-enabled StarTeam servers. The security provider iterates over each StarTeam server in your StarTeam server list, in a round-robin fashion. If your StarTeam repositories are large, this iteration may take a long time (hours or days) to complete. Thus, changes to StarTeam ACL's, user/group membership, or user account status may not be seen immediately.
• The Borland Search Log-in Page and the Borland Search Web Service Authentication Handler both depend on a StarTeam server for authentication. If all of your StarTeam servers for which you have configured Borland Search are inaccessible, users will not be able to log-in to the Borland Search system.

Indexing

• Indexing can take a very long time depending on the size of your StarTeam repository, as well as the number of documents that can be indexed in your repository.

Index Deletion

• When a data source is deleted, either through the web console or a command line script, the index for the data source is not deleted. The remaining index is disabled and is not searchable. Deleting the indexes is a manual operation. Links for search results from deleted data sources will not function.

UNIX

• Shell Scripts (UNIX only) - Shell scripts must be executable. Whether you use the web application or the command line, you must make the shell scripts executable.
  1. Go to: WEB_INSTALL_LOCATION/apache-tomcat-5.5.23/webapps/bss/bin/unix. Or:
     CMD_INSTALL_LOCATION/bss/bin/unix.
  2. Run chmod +x *.sh.

Top

Limitations

The following is a limitation in Borland Search:

• You can run only one instance of the indexer at a time.

Top

Getting Help

For technical support, contact the Borland Support Center at http://support.borland.com/index.jspa.

Top

Installation Instructions

For information on installation, please see the Borland® Search 2009 Installation Instructions (ST_Search_Install.html) available in the root directory on your installation DVD or in your Installation image, and in the C:\Program Files\Borland\Borland Search default directory after the installation.

Top