• BROWSER INSIGHT IS NO LONGER SUPPORTED BEYOND 6.2

BrowserInsight is one of the Insight Servlet Components, providing browser-based access to Insight collections. It is installed and configured by default with each new Collection Manager or Personal Insight Manager you add or upgrade.
Common Administrative Tasks to Perform with BrowserInsight:

• Enabling Auto-login
• Changing the User Manager
• Adding a collection or Collection Server
• Enabling Media Security
• Changing the behavior of the "Collection Selection Panel" on login
• Changing the maximum number of speed-search values

Differences in BrowserInsight between 4.1 and 5.x

In 5.x, the BrowserInsight configuration file has changed a bit. Besides Collection entries, which represent database connections for specific collections, the BrowserInsight.conf contains entries for Server entries (which represent a Collection Manager or Personal Insight Manager). 5.x no longer requires a BrowserUniqueCID entry in the User Manager's collection table.
For existing collections, leave your collection and BrowserUniqueCID entries as they were in 4.1 (as any change will break all existing Remote Launch Strings to that collection). For new collections, use the "Server" method without the BrowserUniqueCID.

Configuring BrowserInsight by Editing the BrowserInsight.conf Configuration File

After installation, the Insight Suite Installer will configure BrowserInsight with information about your User Manager, Collection and Personal Insight Managers. You should not have to configure anything for BrowserInsight.
NOTE: Though you will not need to add new collection entries to the Browser each time you create a collection, you will need to restart the BrowserInsight Servlet before it sees any new collections.

Locating the BrowserInsight.conf Configuration File

The BrowserInsight configuration maintains information on BrowserInsight's database connections, collections, and other basic information.
To Locate the BrowserInsight.conf:

1. Locate your Insight Installation Directory.
2. Open the browserInsight directory.
3. Your BrowserInsight.conf file is located here.

Configuring BrowserInsight to Bypass the Login Page

BrowserInsight is initially configured to require users to enter a username and password to view collections. If you would like to allow users direct access to collections without being asked to enter a username and password, you can provide default values in the configuration file.
To configure "auto-login":

1. Locate the following lines in the BrowserInsight.conf configuration file:

#DefaultBrowserInsightUsername =
#DefaultBrowserInsightPassword =

1. Remove the comment character (#) from the beginning of both lines.
2. Add the default username and password of your choice after each equals sign.

DefaultBrowserInsightUsername = myusername
DefaultBrowserInsightPassword = mypassword

1. Save the BrowserInsight.conf configuration file and restart BrowserInsight.

Configuring BrowserInsight to Close the Collection Selection Window After Opening a Collection in the Group Workspace or Image Workspace

After a user enters their username and password, they are presented with a collection selection window. When users click on a Remote Launch String, if more than one collection is available to that user, BrowserInsight by default will also display that collection selection window in the background. As an administrator, you may choose what happens to that collection selection window if they click on a Remote Launch String, either to leave the window open, or close it.
To configure the collection selection window to close when users click on a Remote Launch String:

1. Locate the following lines in the BrowserInsight.conf configuration file:

1. if set to 1, when a remote launch string is invoked the collection selection
2. window will close after login, and BrowserInsight will launch the selected
3. collection
4. if set to 0, the default, BrowserInsight will keep the collection selection
5. window open in the background
   #
6. CollectionSelectionWindowMode=0
   
7. Remove the comment character (#) from the beginning of the CollectionSelectionWindowMode line.
8. Set the CollectionSelectionWindowMode parameter to 1.

CollectionSelectionWindowMode=1

1. Save the BrowserInsight.conf configuration file and restart BrowserInsight.

Configure Collection Manager Server Database Settings

BrowserInsight can connect to multiple collection databases. For each database, you must specify a server entry with the following parameters: Database Driver, Connect String, Username, Password, Media Manager Address, and Media Manager status.
For collections that were created pre-5.0 environment, BrowserInsight still supports "Collection" entries which enable access to specific collections and tie Remote Launch Strings to collection entries via the BrowserUniqueCID.
Collection.1.InsightDBDriver = sprinta Collection.1.connectString = www.dalton.org:1433?database=insightVRA&sql7=true&user=insight&password=admin
Collection.1.username =
Colelction.1.password =
Collection.1.mediaSecurityEnabled = yes Collection.1.mediaSecurityServletUrl = http://localhost:8081/Media_Manager/srvr
Server.2.InsightDBDriver = oracle
Server.2.connectString = @www.dalton.org:1521:insight
Server.2.username = a_user_name
Server.2.password = a_user_passwordServer.2.mediaSecurityEnabled = yes Server.2.mediaSecurityServletUrl = http://localhost:8081/Media_Manager/srvr
The example above shows two entries: one for a specific collection using the Sprinta Driver and VRA Database, the other a server entry for a 5.x Collection Manager which may have multiple collections in its Oracle Database.
Table 10: Required Entries for a Collection or Server Entry in BrowserInsight

Table 11: Optional Entries for a Collection or Server Entry