brio.portal 7.0.3 installation guide -...

4980 Great America ParkwaySanta Clara, CA 95054 USA+1(408)496-7400

Brio.Portal 7.0.3Installation GuideFor Microsoft Windows Systems

Brio.Portal 7.0.3 Installation Guide For Microsoft Windows Systems

Part Number 1209563-R

© Copyright 2002 Brio Software

All rights reserved. Printed in the USA.

This product and related products and documentation are protected by copyright and

are distributed under licenses restricting their use, copying, distribution, and

decompilation. No part of this product or related documentation may be reproduced

in any form by any means without prior written permission of Brio Software and its

licensors.

Brio Software

4980 Great America Parkway

Santa Clara, CA 95054

+1(408)496-7400

www.Brio.com

Refer to the Brio Software License Agreement in this package before installing or using

the product.

If you find any errors or problems with this documentation, please notify Brio

Software. Brio Software does not guarantee that this document is without error. The

information in this document is subject to change without notice.

Trademarks

Brio®, Brio Inform™, Brio Intelligence™, Brio Performance Applications™,

Brio Performance Builder™, Brio Performance Platform™, Brio Performance Suite™,

Brio Portal™, Brio Reports™, Brio Software™, Personal SQR™, and SQR™ are

trademarks or registered trademarks of Brio Software in the United States and other

countries. All other marks are the trademarks or servicemarks of Brio’s suppliers or

partners and are the property of such third parties.

http://www.brio.com

Contents


Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

System Requirements and Configuration Specifications . . . . . . . . . . . . . . . . . . 5Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Required Configuration Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Creating a Windows User Account . . . . . . . . . . . . . . . . . . . . . . . . . . 8Configuring IBM DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Configuring Informix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Configuring Microsoft SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . 11Configuring Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Configuring Sybase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

SQR Server Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Brio Portal Service Agents Typical Installation or Upgrade . . . . . . . . . . . . . . 18

Brio Portal Service Agents Custom Installation or Upgrade . . . . . . . . . . . . . . 30

Brio Portal Service Agents Installation Verification . . . . . . . . . . . . . . . . . . . . . 44

KnowledgeServer Installation or Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

ONE/Administrator Installation and Configuration . . . . . . . . . . . . . . . . . . . . 58Installing ONE/Administrator Desktop Version . . . . . . . . . . . . . . . . . . . . 58Installing ONE/Administrator Browser Version . . . . . . . . . . . . . . . . . . . . . 60

Troubleshooting for Netscape Browser . . . . . . . . . . . . . . . . . . . . . . 64Troubleshooting for Internet Explorer . . . . . . . . . . . . . . . . . . . . . . 64

Installing ONE/Administrator (Browser Version) Without a Web Server (Internet Explorer Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Configuring ONE/Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

ONE/WebClient Installation and Configuration . . . . . . . . . . . . . . . . . . . . . . 70Installing ONE/WebClient . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Running ONE/WebClient as a Standalone HTTP Server . . . . . . . . . . . . . 75

Changing the Windows Registry Values . . . . . . . . . . . . . . . . . . . . . 76New Registry Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Configuring ONE/WebClient on a Commercial Web Server . . . . . . . . . . 77Configuring Your Commercial Web Server . . . . . . . . . . . . . . . . . . 78Servlet Engine Configuration Settings (for Commercial Web Servers) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Verifying Servlet Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Configuring Apache to Run ONE/WebClient with JRun . . . . . . . 81Configuring Apache to Run ONE/WebClient with JServ . . . . . . . 81Configuring IBM HTTP WebServer to Run ONE/WebClient with WebSphere . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Configuring Microsoft IIS 4.0/5.0 to Run ONE/WebClient with JRun . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Configuring iPlanet 4.0/4.1 to Run ONE/WebClient with JRun . 91Configuring Netscape Enterprise Server 3.5.x/3.6.x to Run ONE/WebClient with JRun . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Configuring Netscape Enterprise Server 3.5.x/3.6.x to Run ONE/WebClient Without JRun . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Manually Loading Class Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Removing ONE/WebClient Software fromMicrosoft Windows Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

ONE/Integrator Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Troubleshooting Your Brio Portal Installation . . . . . . . . . . . . . . . . . . . . . . . 103Installing Brio Portal 7.0.x with DB2 7.1 . . . . . . . . . . . . . . . . . . . . . . . . . 103Connection Refused Errors in Log Files . . . . . . . . . . . . . . . . . . . . . . . . . 104Invalid Template Root Property in WebClient . . . . . . . . . . . . . . . . . . . . 104Error Loading Runtime Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105LDAP Authentication Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105Setting Java Debug Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106Error 2140: Internal WIN NT Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107Java.lang.OutOfMemory Exception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Index

iv Brio.Portal 7.0.3 Installation Guide For Microsoft Windows Systems


This document explains how to install and configure Brio.Portal 7.0.3. It contains:

■ Introduction

■ System Requirements and Configuration Specifications

■ Brio Portal Service Agents Typical Installation or Upgrade

■ Brio Portal Service Agents Custom Installation or Upgrade

■ Brio Portal Service Agents Installation Verification

■ KnowledgeServer Installation or Upgrade

■ ONE/Administrator Installation and Configuration

■ ONE/WebClient Installation and Configuration

■ ONE/Integrator Installation

■ Troubleshooting Your Brio Portal Installation

IntroductionBrio Portal is the comprehensive solution for the creation, management, retrieval, and distribution of enterprise information. Brio Portal’s open architecture accepts information of all types: key enterprise applications, business intelligence tool output, word processor documents, spreadsheets, graphics, video clips, and custom data formats. Users access Brio Portal from a Web browser running on a personal computer, work station, server, thin client, or handheld device.

The following diagram illustrates the flow of information between various data sources and the user, who communicates with Brio Portal using a standard Web browser.

Brio Portal runs on a growing variety of platform and operating system combinations, including enterprise servers running Microsoft Windows and UNIX operating systems. Brio Portal is certified as a 100% Pure Java product. As such, Brio Portal:

■ Provides an identical feature set across all noted platforms

■ Allows cross-platform migration and a high degree of scalability

Brio Portal uses proven relational database management systems to manage its internal metadata tables, providing support for database products such as IBM DB2, Informix, Microsoft SQL Server, Oracle, and Sybase.

2 Brio.Portal 7.0.3 Installation Guide For Microsoft Windows Systems

About This GuideThis guide provides detailed instructions on how to install and configure Brio.Portal 7.0.3 on Microsoft Windows systems.

Typographical ConventionsThe following table outlines the typographical conventions used throughout this installation guide.

Tab le 1 Typographical Conventions

Example Explanation

Select Typical Install. An option, button, or tab you are instructed to choose is indicated in bold.

Press [Down Arrow] Key names are shown in square brackets.

Press [Ctrl+Z] A plus sign (+) between key names indicates that you are to press the keys simultaneously.

Enter 1234. Text you are instructed to enter, including code, is indicated in bold.

Choose Tools�SQLEditor. Options in a menu command path are separated with an arrow. The example indicates that you are to open the Tools menu and choose the SQLEditor option.

sp_adduser login_id Variables you replace with information specific to your instal-lation are shown in italics.

We suggest naming the account brioportal.

Literal strings are shown in bold within explanatory para-graphs.

The Brio/lib directory con-tains a file called ReportMart20.zip.

Files, directories, and paths are shown in a monospaced font.

Set SQRDIR.

In the CUSTOMERS table,

Names that are in all capital letters, such as some variable names, table names, and so on, do not have any other special formatting.

Introduction 3

Customer SupportIf you need technical assistance with, or product updates for Brio Software products, and you have a current maintenance agreement, you can take advantage of the following online support options or call Brio Customer Support.

■ Submit and Track – Enter, track, and update support cases using your Web browser.

URL: http://support.brio.com

■ Product Updates – Download product updates that contain new features and resolutions to previous issues.

URL: http://support.brio.com/updatelogin.asp

■ Knowledge Base – Search for tips and solutions to technical issues.

URL: http://kb.brio.com

Brio Customer Support Numbers

North America and Latin America+1(800)337-6324 or +1(408) 496-7980

CAPJPacific+61 2 9463 6688

Southeast Asia+65 6238 3700 / 08

China+85 2 2869 9657

Japan+81 3 5405 8540

EuropeNorthern+44 (0) 1932 878 400

Central+49 (0) 511 8504 872

Southern+33 (0) 1 55 69 36 60


System Requirements and Configuration Specifications This section lists the hardware and software required to successfully install and use Brio Portal. It also explains how to configure your system to facilitate the installation process. Make sure you carefully review this section before you install Brio Portal.

Hardware RequirementsThe following table lists the minimum hardware requirements for the installation of Brio Portal components. These specifications assume that each component resides on a separate enterprise server.

If you install multiple components on a single server, the free disk space requirements are cumulative. For example, if you install ONE/Administrator, ONE/Integrator, and ONE/WebClient on the same enterprise server, you need 40 MB + 20 MB + 50 MB = 110 MB of free disk space. Additional disk space is needed for repository content.

Note By design, Brio Portal is a distributed network system. For best performance, distribute Brio

Portal’s components across multiple servers. However, for evaluation purposes, you might find it useful to install Brio Portal on a single machine.

Tab le 2 Minimum Hardware Requirements for Brio Portal Components on Microsoft Windows Systems

BRIO.PORTAL COMPONENT

MINIMUM HARDWARE REQUIREMENTS

Service Agents

Knowledge Server

ONE/Administrator

ONE/Integrator

ONE/WebClient

CD-ROM Drive � � � � �

266 MHz Pentium CPU � � � � �

RAM (MB) 256 128 128 64 128

Free Disk Space (MB) 100 80 40 20 50

TCP/IP Connection � � � � �

✏

System Requirements and Configuration Specifications 5

Software RequirementsThe following table lists the software requirements for Brio.Portal 7.0.3 on Microsoft Windows systems.

Tab le 3 Software Requirements for Brio Portal Components on Microsoft Windows Systems

Operating System

Brio Portal can be run on: Windows NT 4.0 with Service Pack 3 or Windows 2000

Relational Database Requirements

The network on which you run Brio Portal must have one of these databases:

■ Oracle 7.3.4 or 8.0.x with Oracle Level 4 JDBC Driver; Oracle 8.1.5, 8.1.6, or 8.1.7 with Oracle 8.1.5 Driver; Oracle SQL*Net

■ Microsoft SQL Server 7 with Microsoft SQL Server 7.0 Client Libraries; Microsoft SQL Server 2000

■ Informix 7.3.1 with Infomix Level 4 JDBC Driver

■ Sybase 11.9.2, or 12.0 with ESD1, with Sybase Level IV JDBC Drivers

■ IBM DB2 5.2, 6.1, 7.1

Note: DB2 7.1 users should refer to “Installing Brio Portal 7.0.x with DB2 7.1” on page 103 for troubleshooting information.

JDK Version JDK 1.2.2 or Jview/L4

Brio Portal Service Agents

For SQR Job Factories Brio SQR version 4.0 and later. (SQR version 4.2 and later is recommended.)

KnowledgeServer

KnowledgeServer requires: Windows NT 4.0 with Service Pack 6a or Windows 2000

ONE/Administrator Browser Version

The machines on which you install ONE/Administrator Browser Version must run:

■ Clients

❐ Netscape Navigator 4.0x or later or

❐ Microsoft Internet Explorer 5.0x

■ Web Servers

❐ Microsoft IIS 4.0/5.0 or

❐ iPlanet 4.0/4.1

ONE/WebClient (Standalone HTTP Server)

The machines on which you install ONE/WebClient (standalone HTTP server) must run:

■ Netscape Navigator 4.0x or later, or

■ Internet Explorer 5.0x


Required Configuration ProceduresPrior to installing Brio Portal, you need to install:

■ A Windows user account (we suggest naming the account brioportal)

■ Database software

■ SQR Server, if your users want to run SQR jobs (see “SQR Server Installation” on page 16)

The following sections detail how to configure your system prior to installing Brio Portal. These procedures differ according to the RDBMS used for Brio Portal metadata storage.

Note If you are running Brio Portal service agents on multiple hosts, update the Windows hosts file

with an entry for each host in your Brio Portal configuration. The hosts file usually resides at c:\winnt\system32\drivers\etc\hosts. Listing each host in your Brio Portal configuration increases the reliability of the Brio Portal service agent startup procedure.

The following table provides additional information you should consider before installing Brio.Portal 7.0.3 on Microsoft Windows systems.

ONE/WebClient (Web Server)

The machines on which you install ONE/WebClient (Web server) must run:

■ NES 3.5.x/3.6.x with native servlet engine or JRun 2.3.3, or

■ iPlanet 4.0/4.1 with native servlet engine or JRun 2.3.3, or

■ IIS 4.0/5.0 with JRun 2.3.3, or

■ Apache with JRun 2.3.3 or JServ, or

■ IBM HTTP WebServer with WebSphere

Tab le 3 Software Requirements for Brio Portal Components on Microsoft Windows Systems (Continued)

✏


Creating a Windows User AccountChoose or create a Windows user account for Brio Portal. All Brio Portal service agents on this machine should be started from this account. We suggest naming the account brioportal. Note that Brio Portal’s system permissions are the same as the user account with which it is associated.

Configuring IBM DB2To configure your system for use with IBM DB2:

1 Create a database user account for Brio Portal.

Brio Portal requires a database to store its persistent data. If you have not already done so, install the IBM DB2 RDBMS.

Note IBM DB2 is case sensitive.

Create a user account that provides Brio Portal access to your database. This user owns the Brio Portal database tables that are built and populated, and objects that are created, during installation. Brio Portal service agents use the same user account to connect to the database. We suggest you name the database user brioportal.

Tab le 4 Pre-Installation Guidelines

For: Do This:

SQR 4.x and later (All RDBM Systems)

Run the loadall program from the SQR CD before running SQR programs. See “SQR Server Installation” on page 16.

RDBMS General Caveats Do not create superuser Brio Portal accounts in your databases.

IBM DB2 DB2 is case sensitive.

Check that the IBM DB2 Client Application Enabler is installed.

Informix Turn on database logging.

Oracle Brio Portal must not share user tablespaces with other applications or the SYSTEM tablespace.

Sybase Sybase is case sensitive.

✏


Note The repository database user cannot be administrator or briouser.

On the machine on which the IBM DB2 Server RDBMS is running, access DB2 and create a Brio Portal system (or user) account. (Refer to your operating system and database documentation for specific instructions.)

2 Set up the database within your RDBMS.

Brio Portal requires a database to store its persistent data.

Log in as the user created in Step 1 and create a database in which to store the Brio Portal metadata. Use this command:

db2 create database database_name

For information on how to define and set database parameters, consult your IBM/DB2 documentation.

3 Check that the IBM DB2 Client Application Enabler is installed on the machines on which you are about to install Brio Portal service agents.

4 If you use an IBM DB2 RDBMS located on a different machine than the Brio Portal service agents, create a client connection to the Brio Portal database using the Client Application Enabler.

The Client Configuration Assistant feature of this application requires that you enter the host name, port number, and service name used in your database server installation. Note the full path to the installed driver. You need this path to complete Step 10: Enter the directory containing the JDBC driver under “Brio Portal Service Agents Typical Installation or Upgrade” on page 18.

5 Set the LIBPATH environment variable to the location of the DB2 libraries.

Use the System option in Control Panel or the Set command from the Windows command prompt.

Note Proceed to “SQR Server Installation” on page 16. If you do not need to install SQR Server, proceed to “Brio Portal Service Agents Typical Installation or Upgrade” on page 18 for information on how to install or upgrade the Brio Portal Service Agents.

✏

✏


Configuring InformixTo configure your system for use with Informix:

1 Create a database within Informix for Brio Portal.

Brio Portal requires a database to store its persistent data. If you have not already done so, install the Informix RDBMS. Record the Informix database host name, port number, and server for use when you install the Brio Portal products.

To create a new database from the Informix program group:

a. Choose the Database Explorer program item.

b. Choose File�Create and fill in the database name and the Dbspace to use.

The amount of space needed depends upon the size of the repository you plan to build. We suggest starting with 20 MB and permitting it to grow.

c. Turn on logging.

In order for Brio Portal to work correctly, logging must be turned on. Brio Portal uses transactions, which requires database logging.

2 Grant database privileges for the Brio Portal user.

The user account created previously owns the Brio Portal database tables and objects that are built and populated during this installation. After creating the Brio Portal database:

a. Choose Tools�SQLEditor.

b. Enter the name of the database you just created; then, type the following:

Grant resource to brioportal_system_user

3 Download the Informix Level IV JDBC driver (ifxjdbc.jar) from the Intraware Web site at:

http://www.intraware.com/idn/jdbc/index.html

Fill out the online registration form to receive email that explains how to get your JDBC driver.

4 Install the Informix 100% pure Java driver (ifxjdbc.jar).

Install this driver on the Windows, AIX, HP-UX, or Solaris machine or machines on which you install the ONE/NameServer, ONE/Repository, ONE/AuthenticationServer, and ONE/EventServer.


Follow the driver installation instructions provided and note the full path to the installed driver. You need this path to complete Step 10: Enter the directory containing the JDBC driver under “Brio Portal Service Agents Typical Installation or Upgrade” on page 18.

If you run ONE/AuthenticationServer on a separate machine from the ONE/Repository, be sure you also install ifxjdbc.jar on that machine.

Note Proceed to “SQR Server Installation” on page 16. If you do not need to install SQR Server,

proceed to “Brio Portal Service Agents Typical Installation or Upgrade” on page 18 for information on how to install or upgrade the Brio Portal Service Agents.

Configuring Microsoft SQL ServerTo configure your system for use with Microsoft SQL Server:


Brio Portal requires a database to store its persistent data. If you have not already done so, install the Microsoft SQL Server RDBMS. Record the Microsoft SQL database host name, port number, and server for use when you install the Brio Portal products. MS SQL Server is not case sensitive.

To set up the database within your RDBMS:

a. Decide whether there is a database device with sufficient disk space to store the Brio Portal metadata. If not, create a database device. To do so:

DISK INIT NAME = 'logical_name', PHYSNAME = 'absolute_dir_path_and_file_name', VDEVNO = virtual_device_number, SIZE = size_in_2k_pagesgo

b. Create a database in which to store the metadata.

CREATE DATABASE brioportalDBON device_name = size_in_MB go


✏



A user must be created. This user owns the Brio Portal database tables and objects that are built and populated during this installation. The user created here is also the user that Brio Portal service agents use to connect to the database. We suggest naming the user brioportal.


To create a database user account for Brio Portal:

a. Create the MS SQL Server login.

sp_addlogin login_id, password brioportalDB go

b. Create the database user.

use brioportalDB gosp_adduser login_id, login_id go

c. Grant privileges to the user.

use brioportalDB go grant create table to login_id go grant select on sysobjects to login_id go grant create procedure to login_id go



✏

✏


Configuring OracleBrio Portal requires a database to store its persistent data. If you have not already done so, install the Oracle RDBMS. Record the Oracle database host name, port number, and Oracle SID (or Service Name) for use when you install the Brio Portal products.

To configure your system for use with Oracle:

1 Dedicate a tablespace to Brio Portal.

Use the following guidelines as you dedicate a tablespace to Brio Portal:

■ Determine the tablespaces to be used as the default tablespace and temporary tablespace for this user. For performance reasons, these should not share the same tablespace as other applications nor should they use the SYSTEM tablespace. To list the existing tablespaces, enter the following SQL statement from SQL*Plus:

select * from sys.dba_tablespaces;

■ If an existing tablespace is not suitable as the default or temporary tablespace for this user, then create a new tablespace by entering one of the following SQL statements from the SQL*Plus utility. (This action requires CREATE TABLESPACE system privileges.)

❑ If the database instance or file name (filespec) already exists:

create tablespace tablespace_name datafile 'filespec';

❑ If the database instance or file name (filespec) does not already exist:

create tablespace tablespace_name datafile 'filespec' size nnM;

where nn is the number of megabytes.


2 Create an Oracle user account for Brio Portal.


Note The repository database user cannot be administrator or briouser.✏


Appropriate database privileges are required to perform the following actions. The tablespaces created or identified in the previous step are used as the default and temporary tablespaces. To create the user, enter the following from within the Oracle SQL*Plus utility:

create user username identified by password default tablespace tablespace1 temporary tablespace tablespace2;

where tablespace1 and tablespace2 are the tablespaces previously created or identified.

3 Give the user database connection privileges.

grant connect, resource to username;



Configuring SybaseBefore configuring Sybase for Brio.Portal 7.0.3, copy the Sybase Level IV JDBC driver (jconnect40.zip or jconnect41.zip) into the Sybase directory containing the Sybase client libraries; for example, C:\SYBASE. When prompted for the JDBC driver, type the full path; for example, C:\SYBASE\jconnect41.zip. If you do not have this driver, download a trial version from the Sybase Web site at http://www.sybase.com/downloads/.

You need to obtain a full version of jConnect before the trial version expires. Refer to the documentation provided by Sybase for installation of jConnect. Place the jConnect.zip file in the Sybase home directory that the environment variable SYBASE points to. Be sure to note the full path to this jconnect file. You need to provide it during installation.

To configure a system for use with Sybase:


Brio Portal requires a database to store its persistent data. If you have not already done so, install the Sybase RDBMS. Record the Sybase database host name, port number, and database server name for use when you install the Brio Portal products.

✏


Note Sybase is case sensitive.

To set up the database:

a. Decide whether there is a database device with sufficient disk space to store the Brio Portal metadata. If not, create a database device. To do so:

DISK INITNAME = 'logical_name', PHYSNAME = 'absolute_dir_path_and_file_name', VDEVNO = virtual_device_number, SIZE = size_in_2k_pagesgo

b. Create a database in which to store the metadata.

CREATE DATABASE brioportalDB ON device_name = size_in_MB go





To create a database user account for Brio Portal:

a. Create the Sybase login.

sp_addlogin login_id, password brioportalDB go

b. Create the database user.

use brioportalDB gosp_adduser login_id, login_id go

c. Grant privileges to the user.

use brioportalDB

✏

✏


gogrant create table to login_id gogrant select on sysobjects to login_id gogrant create procedure to login_id go



SQR Server InstallationIf you intend to run SQR Jobs, install SQR Server 4.x or later before installing Brio Portal.

1 Install SQR Server.

Refer to the appropriate SQR Server Installation Guide for detailed instructions. We recommend that you install SQR Server version 4.2 or later. SQR Server 6.2 includes the newest product enhancements and software improvements that fully optimize Brio Portal capabilities, and supports the following databases: Informix, Oracle, Sybase, DB2, DDO (works with SAP, Essbase, XML, CSV, JDBC, MS OLAP) and ODBC (works with Microsoft SQL Server, IBM DB2, Sybase SQL Anywhere, Sybase IQ).

Note If you do not plan to run SQR jobs with Brio Portal, you do not need to install SQR Server.

2 Run loadall from SQR Server.

Before you run any SQR programs, run the loadall program that comes with SQR Server. Loadall installs the required SQR sample tables and sample data. On Windows systems, run the loadall program either with Brio Report Builder or directly from SQR Server.

To run loadall:

a. Enter sqrw.exe from the DOS command prompt within the SQR directory.

b. Select loadall.sqr as the report name.

✏

✏


To run the SQR-based portions of the Demo application, you need the sample tables and data.

Note For more information on installing and configuring SQR Server, see the SQR Server Installation

Guide.✏


Brio Portal Service Agents Typical Installation or UpgradeUse the following installation procedures to install and upgrade Brio Portal Service Agents on Microsoft Windows systems. To successfully perform this installation, make sure you have the following information (all of this necessary information is accessible to your database or system administrator):

For IBM DB2: ■ Your Brio Portal license key.

■ The DB2 instance name, database name, and username/password.

■ The path to the DB2 JDBC driver (db2java.zip).

■ If you wish to run SQR Jobs, the location (SQRDIR) and version of SQR.

For Informix: ■ Your Brio Portal license key.

■ The Informix database host name, server name, database name, port, and username/pass-word.

■ The path to the Informix 7 Level IV JDBC driver installed in Step 4: Install the Informix 100% pure Java driver under “Configuring Informix” on page 10.


For Microsoft SQL Server: ■ Your Brio Portal license key.

■ The Microsoft SQL Server database host name, server name, database name, port, and username/password.


For Oracle: ■ Your Brio Portal license key.

■ The Oracle database host, port, SID (or Service Name), and connect string (Depending upon your system’s configuration, you may find the Oracle database host, port, SID (or Service Name), and connect string in the Oracle tnsnames.ora file).


For Sybase: ■ Your Brio Portal license key.

■ The Sybase server name and username/password to the Sybase database.

■ The port number Sybase is listening on, and the machine name on which Sybase resides. (You may find the port number in the SQL.ini file.)

■ The path to the Sybase JDBC driver (jconnect40.zip or jconnect41.zip).jconnect40.zip



To install or upgrade Brio Portal Service Agents using the typical (default) settings:

1 Run setup.exe from the NT directory of the Brio Portal CD.

Insert the Brio Portal CD. From your Windows desktop, choose Start�Run. In the Open field, type E:\NT\setup.exe (replace E with your CD-ROM drive designator). Click OK to start the installer.

2 Enter the license key.

You must enter a license key to install the Brio Portal files to your computer. When prompted by the installation software, enter the license key provided with the installation media. The key should be in a format similar to the following:

6555-1212-0319-0224-5460-9911-1351

3 Select one or more Brio Portal components and click Install.

Your license key determines which Brio Portal components you can install. Click a component name to select it.

4 Click Next to proceed with the installation.

Read the Welcome information and the Software License Agreement. To continue with the installation, click Yes to accept the license agreement.

Brio Portal Service Agents Typical Installation or Upgrade 19

5 Select the destination directory.

The installation directory shown is either the default directory (C:\Program Files\Brio), or the existing installation directory (that is, the directory where you installed the previous version of Brio Portal, if there is one). If you accept the directory shown, the installer installs the Brio Portal service agent software in \install_directory\BrioPortal. Select Browse to specify a different directory location. If the directory does not exist, the installer creates it for you.

If you are upgrading from ReportMart 1.x, you must first upgrade to Brio Portal 6.0 using the 6.0 CD and then upgrade to Brio Portal 7.x.

6 Select the installation setup type.

Choose between Typical, Custom, Upgrade a Typical Install, or Upgrade a Custom Install.

Note The two Upgrade options appear only if an existing installation is detected in the directory

specified in Step 5: Select the destination directory.✏


■ Typical – Installs all six Brio Portal service agents (ONE/NameServer, ONE/Repository, ONE/ServiceBroker, ONE/JobFactory, ONE/AuthenticationServer, and ONE/EventServer) on this host computer under the BrioPortal Server. Select this option if you are performing a new installation of Brio Portal.

Caution If you select either the Typical or Custom install option, any existing information is overwritten. To upgrade existing ONE/NameServer and ONE/Repository installations to Brio.Portal 7.0.3 service agents without overwriting their data, select one of the Upgrade options.

■ Custom – Distributes the Brio Portal workload across multiple machines. This improves the performance and scalability of your Brio Portal system. See “Brio Portal Service Agents Typical Installation or Upgrade” on page 18.

Caution If you are upgrading individual Brio Portal service agents to Brio.Portal 7.0.3, do not use the Custom installation option. Instead, use the Upgrade a Custom Install option to ensure that existing metadata goes into the new Brio Portal tables.

!

!


■ Upgrade a Typical Install – Upgrades Brio Portal 6.0 or 7.0 service agents to Brio.Portal 7.0.3 using the typical settings. (The JRE is also upgraded if a later version is in the upgrade.) This action should be performed on Brio Portal versions only. If you are upgrading from ReportMart 1.x, you must first upgrade to Brio Portal 6.0 using the 6.0 CD and then upgrade to Brio.Portal 7.0.3.

■ Upgrade a Custom Install – For an existing distributed Brio Portal architecture, upgrades Brio Portal 6.0 or 7.0 service agents to Brio.Portal 7.0.3. See “Brio Portal Service Agents Typical Installation or Upgrade” on page 18.

7 Review Service Agent information.

Review service agent names and port numbers and change them if desired. To view a service agent’s settings:

a. Select the service agent from the list in the Typical Setup dialog box.

b. Click Change to open the Settings dialog box for the selected Service Agent.

c. Verify or change the name and port number and click OK.

Note All startup files reside in the BrioPortal\bin subdirectory of the previously specified installation root directory. Use the Windows netstat command to determine which ports are in use.

✏


8 Specify the ONE/AuthenticationServer installation.

The installer asks you if this is the first ONE/AuthenticationServer (AS) that you are installing. When you install the first AS, the installer creates database tables. Any additional AS installations, even on remote machines, use the same tables, and therefore do not create additional tables.

■ For a Typical Installation:

❑ If you are installing your first AS, select The Initial AuthenticationServer to create the database tables.

❑ If you are adding an additional AS, select An Additional Server Being Added To An Existing Installation. If you select The Initial AuthenticationServer after you have already installed one AS using the current Brio Portal version, the user information in the tables is overwritten.

■ For a Typical Upgrade:

Select The Initial AuthenticationServer to upgrade your database tables. Your existing tables from earlier versions of Brio Portal are not overwritten.

9 Select the database type.

Select IBM DB2, Informix, Microsoft SQL Server, SYBASE, or Oracle 8.1.5 or later, or Oracle, earlier than 8.1.5 as the Brio Portal database type.


10 Enter the directory containing the JDBC driver.

■ Oracle Users – The installer skips this step if you chose Oracle as your database type, and it automatically installs the Oracle JDBC driver based on the version of Oracle you previously selected. Classes12.zip is used with Oracle versions 8.1.5 and later. Classes11.zip is used with versions of Oracle earlier than 8.1.5.

■ Informix or DB2 Users – If you chose Informix or DB2 as your database type, the installer asks you whether the file system should be searched for the directory containing the proper JDBC driver or whether you prefer to specify the location of the file.

❑ If you select Yes, the installer searches the file system’s C and D drives for the correct file. The installer then brings up the search result and its directory path.You can accept the directory or you can browse to a different location for the JDBC driver.

❑ If you select No, the installer prompts to specify the full directory path containing the correct file. (See Step 4 under “Configuring IBM DB2” on page 8 or Step 4 under “Configuring Informix” on page 10.)

■ MS SQL Users – Proceed to the next step.

■ Sybase Users – If you chose Sybase as your database type, you must specify the location of the JDBC driver (jconnect40.zip or jconnect41.zip).

11 Identify the database host name, port number, and name.


You recorded this information when you configured your database. (See the section specific to your database type under “Required Configuration Procedures” on page 7.)

■ Host Name – Machine running the database server utilized by ONE/Repository.

■ Port Number – Database host port on which the database listens for connection requests from clients.

■ Name – Database or instance used to store the Brio Portal metadata.

Note Oracle users can find this information in the tnsnames.ora file located on the machine

where Brio Portal is being installed.

Sybase users can find this information in the SQL.ini file. For Sybase users, name is the specific database server where the Brio Portal Sybase database was created.

12 Identify database connectivity.

a. Identify the user name, password, and connect string/datasource for the database account that was created as part of the pre-installation requirements. The default user name that we previously recommended is brioportal. Remember that IBM DB2 and Sybase are case sensitive.

✏


If you are in doubt as to the correct information necessary to fill these fields, contact your database and/or system administrator. The connect string is utilized by the ONE/JobFactory to connect to a database when a connection is required during the execution of SQR jobs.

Each database vendor has a different nomenclature for describing the connectivity to their database.

❑ The term connect string is appropriate for Oracle. The connect string in this case is a service name entry in the tnsnames.ora file located on the machine where Brio Portal is being installed.

❑ For Microsoft SQL Server, the datasource is the ODBC datasource configured where the metadata is being installed. The database server could be on the local or a remote machine.

❑ For Informix and DB2, the datasource is the name of the database created for Brio Portal.

❑ For Sybase, a connect string/datasource is not required.

b. Test the JDBC connection.

After you supply the database connectivity information, the installer attempts to verify the information by connecting to the database. A DOS window opens while the connection is being tested.

❑ If the connection succeeds, proceed to Step 13.

❑ If the connection fails, view the error log and correct your database connectivity parameters.

13 Identify the host machine.

The host name and IP address of the machine from which you are installing is automatically supplied for you.

Note For a typical upgrade, the installer skips Step 14: Identify the mail server and Step 15: Set the SQR location.

✏


14 Identify the mail server.

In order for ONE/EventServer to provide email notifications, you must specify the name of your outgoing mail server. If you do not know the name of your mail server, enter a placeholder to proceed with the installation. After you have installed all Brio Portal components and started the Brio Portal Service, you can use ONE/Administrator to specify the correct mail server.

15 Set the SQR location.

The installer displays the default location for SQR.

■ If you are installing ONE/NameServer and ONE/Repository to run with SQR, identify SQR’s location.

If the installer finds SQR, it asks you either to confirm or enter the location of SQR. A follow-on screen prompts you to specify the version of SQR, and the installer then asks if you want to install the demo data.

If selected, the Brio Portal demo application installs within ONE/Repository and can be utilized for training in the use of the ONE/WebClient component. The application includes Microsoft Word files, Microsoft Excel spreadsheets, SQR Programs, and SQR output. If the demo is selected, the installer performs the following actions:

❑ Creates a demonstration user named briouser with a password of briouser.

❑ Creates a demonstration group named BrioPortal_Demo and make this the default group for user briouser.

❑ Creates a demonstration folder named SampleContent.

❑ Creates a demonstration database server and data source entries for your database.

❑ Creates a demonstration subservice entry named BrioPortal_Demo. The SQR sample programs use this subservice.

❑ Loads sample SQR programs, MS Word documents, MS Excel spreadsheets, and HTML documents into ONE/Repository.

Note After completing the installation, if you have installed ONE/WebClient, you can log into ONE/WebClient with username briouser and password briouser. You can then retrieve and

review these objects and run the sample SQR programs.

✏


■ If you do not want to run SQR jobs:

❑ Clear the default SQR location. The installer asks you if you wish to continue with the installation.

❑ Click Yes to continue without installing the Demo or setting up SQR database connectivity.

16 Review installation selections and settings.

The installer prompts you to review the Setup Type, Target Directory, Host Information, Database Information, Mail Server Information, and SQR Information along with the names and port numbers of all the installed service agents. Record these settings for future reference. Click Next to continue the installation.

17 Complete the installation.

A Java program automatically copies files into target directories and a series of Java programs populates the database. During this portion of the installation, the installer displays several DOS command windows. This step takes several minutes.

Two log files, Install.log and Drop.log, are created in the following location:

c:\Program Files\Brio\BrioPortal\log

At the end of the installation, the installer prompts you to review Drop.log and Install.log. Be sure to review these files to determine that all database operations were performed successfully. If you encounter fatal errors, fix them and run the installation again.

Messages that appear to be errors can often be found in Drop.log. These errors are usually benign. The installer searches these errors and notifies you if any of them are problematic. Most benign errors occur during fresh Brio Portal installations, and they usually involve the failure to delete a non-existent table or constraint. If your DBA is confident that your Drop.log errors pose no problem, proceed with the installation.


Note the paths to the following files. If you choose not to delete the log files after installing Brio Portal, these files remain on your system. You can use them in cooperation with Brio Technical Support to troubleshoot problems stemming from installation errors.

Program Files\Brio\BrioPortal\log\MInstall.log Program Files\Brio\BrioPortal\log\CreateConfig.log Program Files\Brio\BrioPortal\log\Install.log Program Files\Brio\BrioPortal\log\Drop.log Program Files\Brio\BrioPortal\log\JavaErrors.log Program Files\Brio\BrioPortal\etc\InstallProps Program Files\Brio\BrioPortal\etc\SAProps

When the installation is complete, view the Readme.txt file by selecting the Yes check box; then click Finish.

Caution After you have examined the Install.Log, InstallProps, and SAProps files, delete them. They contain passwords in clear text. You can manually delete these files after the installation is complete. (CreateConfig.log contains encrypted passwords, so it is not vital that you delete it.)

18 Configure ONE/JobFactory for Microsoft SQL Server.

Note Complete this step only if you intend to run SQR jobs against a Microsoft SQL Server database.

To run any SQR engine, configure the corresponding ONE/JobFactory to run as a user instead of as System.

a. Select Control Panel.

b. Select Services.

c. Select ONE/JobFactory jf_name.

d. Click Startup.

e. Click this account and specify a user other than Local System.

!

✏


Brio Portal Service Agents Custom Installation or UpgradeUse the following installation procedures to install and upgrade Brio Portal Service Agents on Microsoft Windows systems. To successfully perform this installation, make sure you have the following information (all of this necessary information is accessible to your database or system administrator):

For IBM DB2: ■ Your Brio Portal license key.

■ The DB2 instance name, database name, and username/password.

■ The path to the DB2 JDBC driver (db2java.zip).


For Informix: ■ Your Brio Portal license key.

■ The Informix database host name, server name, database name, port, and username/pass-word.

■ The path to the Informix 7 Level IV JDBC driver installed in Step 4: Install the Informix 100% pure Java driver under “Configuring Informix” on page 10.


For Microsoft SQL Server: ■ Your Brio Portal license key.

■ The Microsoft SQL Server database host name, server name, database name, port, and username/password.


For Oracle: ■ Your Brio Portal license key.

■ The Oracle database host, port, SID (or Service Name), and connect string (Depending upon your system’s configuration, you may find the Oracle database host, port, SID (or Service Name), and connect string in the Oracle tnsnames.ora file).


For Sybase: ■ Your Brio Portal license key.

■ The Sybase server name and username/password to the Sybase database.

■ The port number Sybase is listening on, and the machine name on which Sybase resides. (You may find the port number in the SQL.ini file.)

■ The path to the Sybase JDBC driver (jconnect40.zip or jconnect41.zip).



To install and upgrade Brio Portal Service Agents with customized settings:





6555-1212-0319-0224-5460-9911-1351

3 Select one or more Brio Portal components and click Install.

Your license key determines which Brio Portal components you can install. Click a component name to select it.



Brio Portal Service Agents Custom Installation or Upgrade 31


The installation directory shown is either the default directory (C:\Program Files\Brio), or the existing installation directory (that is, the directory where you installed the previous version of Brio Portal, if there is one). If you accept the directory shown, the installer installs the Brio Portal service agent software in \install_directory\BrioPortal. Select Browse to specify a different directory location. If the directory does not exist, the installer creates it for you.

If you are upgrading from ReportMart 1.x, you must first upgrade to Brio Portal 6.0 using the 6.0 CD and then upgrade to Brio Poral 7.x.

6 Select the installation setup type.

Choose between Typical, Custom, Upgrade a Typical Install, or Upgrade a Custom Install.

Note The two Upgrade options display only if an existing installation is detected in the directory

specified in Step 6.✏


■ Typical – Installs all six Brio Portal service agents on this host computer under the BrioPortal Server. Select this option if you are performing a new installation of Brio Portal. See “Brio Portal Service Agents Typical Installation or Upgrade” on page 18.

■ Custom – Distributes the Brio Portal workload across multiple machines. This improves the performance and scalability of your Brio Portal system.

Caution If you select either the Typical or Custom install option, any existing information is overwritten. To upgrade existing Brio Portal service agents to Brio.Portal 7.0.3 service agents without overwriting their data, select one of the Upgrade options.

■ Upgrade a Typical Install – Upgrades Brio Portal 6.0 or 7.0 service agents to Brio.Portal 7.0.3 using the typical settings. See “Brio Portal Service Agents Typical Installation or Upgrade” on page 18.

■ Upgrade a Custom Install – For an existing distributed Brio Portal architecture, upgrades Brio Portal 6.0 or 7.0 service agents to Brio.Portal 7.0.3. This action should be performed on Brio Portal versions only. If you are upgrading from ReportMart 1.x, you must first upgrade to Brio Portal 6.0 using the 6.0 CD and then upgrade to Brio.Portal 7.0.3.

!


7 Select a Service Agent to install or upgrade.

Note The ONE/NameServer, ONE/Repository, and ONE/EventServer should all be installed together. You can select ONE/NameServer and ONE/Repository without selecting ONE/EventServer, but you will have to reinstall them if you later wish to install ONE/EventServer. You cannot select

ONE/EventServer without selecting ONE/NameServer and ONE/Repository.

■ ONE/NameServer and ONE/Repository Agents – Installs or upgrades only ONE/NameServer and ONE/Repository on this machine. Brio Portal allows only one ONE/NameServer and one ONE/Repository.

The install issues a warning message if you select ONE/NameServer and ONE/Repository Agents without selecting ONE/EventServer.

If you select ONE/NameServer and ONE/Repository Agents, the installer proceeds with Step 9: Select the database type. (If your custom installation does not include ONE/EventServer, the installer skips Step 14: Identify the mail server.)

✏


■ ONE/ServiceBroker Agent – Installs or upgrades only ONE/ServiceBroker on this machine. If the ONE/NameServer and ONE/Repository Agents are installed on a different host, you must use ONE/Administrator to configure ONE/ServiceBroker before you can start the it, either before or after you install this agent.

After you select ONE/ServiceBroker, the installer proceeds to Step 13: Identify the host machine. The ServiceBroker is automatically updated when adding/deleting agents. Routing service requests to a new agent can be performed without restarting the ServiceBroker.

Note You must use the same name, port number, and directory for the installation and the

configuration of ONE/ServiceBroker. At the completion of the custom install, the agent name, host name, port number, and directory are displayed. This information is required when creating the new agent in ONE/Administrator.

When you complete this ONE/ServiceBroker installation, if your new ONE/ServiceBroker is on a machine other than your ONE/Repository and ONE/NameServer machine, follow this procedure:

Connect to ONE/Administrator via the ONE/NameServer host and its specified port. The default username/password is BPAdministrator/12345678. You should change this password after installation is complete. The default port is 1498.

Use ONE/Services to configure the remote ONE/ServiceBroker. The default username/password is admin/admin. The default port is 1497.

Reconnect to ONE/NameServer via your new remote ONE/ServiceBroker.

■ ONE/JobFactory Agent – Installs or upgrades only ONE/JobFactory on this machine. You must use ONE/Administrator to configure this server before starting it, either before or after you install this agent.

You must use the same name and port number for the installation and configuration of ONE/JobFactory.

After you select ONE/JobFactory, the installer proceeds with Step 13: Identify the host machine. (Name is case sensitive.)

✏


Any changes to executables, SQR executables, and database connectivity are immediately propagated to the JobFactories on the appropriate host and to all ServiceBrokers. Jobs using newly configured applications, executables, and subservices can be executed without restarting any agent.

■ ONE/AuthenticationServer Agent – Installs or upgrades only a ONE/AuthenticationServer on this machine. You must use ONE/Administrator to configure this server before starting it, either before or after you install this agent.

You must use the same name and port number for the installation and configuration of ONE/AuthenticationServer. (Name is case sensitive.)

After you select ONE/AuthenticationServer, the installer proceeds to Step 9.

■ ONE/EventServer Agent – Installs or upgrades only ONE/EventServer.You can install ONE/EventServer only on the same machine as ONE/NameServer and ONE/Repository.

Note The ONE/NameServer, ONE/Repository, and ONE/EventServer should all be installed together. You can select ONE/NameServer and ONE/Repository without selecting ONE/EventServer, but

you will have to reinstall them if you later wish to install ONE/EventServer. You cannot select ONE/EventServer without selecting ONE/NameServer and ONE/Repository.

After you select ONE/EventServer, the installer proceeds to Step 9: Select the database type.

8 Review Service Agent information.

Review service agent names and port numbers and change them if desired. To view a service agent’s settings:

a. Select the service agent from the list.

b. Click Change to open the Settings dialog box for the selected Service Agent.

c. Verify or change the name and port number and click OK.

Note To ensure that you do not specify an occupied port, use the Windows netstat command to determine which ports are in use.

✏

✏


The installer asks you if this is the first ONE/AuthenticationServer (AS) that you are installing. You can install multiple instances of the AS, but they all use the same tables in the database. When you install the first AS, the installer creates these tables. Any additional AS installations, even on remote machines, use the same tables, and therefore do not create additional tables.

■ For a Custom Installation:

❑ If you are installing your first AS and therefore need to create the AS tables, select The Initial AuthenticationServer. If you select The Initial AuthenticationServer after previously installing an AS, the user information in the tables from the previous installation are overwritten.

❑ If you are adding an additional AS, select An Additional Server Being Added To An Existing Installation.

■ For a Custom Upgrade:

❑ Select The Initial AuthenticationServer to upgrade your database tables. Your existing tables from earlier versions of Brio Portal will not be overwritten.

Note Complete Step 9, Step 10, and Step 11 only if you are installing or upgrading

ONE/Repository, ONE/AuthenticationServer, or ONE/EventServer Agents. ✏



Select IBM DB2, Informix, Microsoft SQL Server, SYBASE, or Oracle 8.1.5 or later, or Oracle, earlier than 8.1.5 as the Brio Portal database type.


■ Oracle Users – The installer skips this step if you selected Oracle as your database type, and it automatically installs the Oracle JDBC driver based on the version of Oracle previously selected. Classes12.zip is used with Oracle versions 8.1.5 and later. Classes111.zip is used with versions of Oracle earlier than 8.1.5.

■ Informix or DBS Users – If you selected Informix or DB2 as your database type, the installer asks you whether the file system should be searched for the directory containing the proper JDBC driver or whether you prefer to specify the location of the file.

❑ If you select Yes, the installer searches the file system’s C and D drives for the correct file. It then brings up the search result and its directory path.You can accept the directory that was found or you can browse to a different location for the JDBC driver.

❑ If you select No, the installer prompts you to specify the full directory path containing the correct file.

■ Sybase Users – If you selected Sybase as your database type, you must specify the location of the JDBC driver (jconnect40.zip or jconnect41.zip).

11 Identify the database host name, port number, and name.

Note Complete this step only if you are installing or upgrading ONE/Repository, ONE/AuthenticationServer, or ONE/EventServer Agents. Otherwise, skip this step.

✏


You recorded this information when you configured your database. (See the section specific to your database type under “Required Configuration Procedures” on page 7.

■ Host Name – Machine running the database server utilized by ONE/Repository.


■ Name – Database or instance used to store the Brio Portal metadata.

Note Oracle users can find this information in the tnsnames.ora file located on the machine

where Brio Portal is being installed.

Sybase users can find this information in the SQL.ini file. For Sybase users, name is the specific database server where the Brio Portal Sybase database was created.


Identify the user name, password, and connect string/datasource for the database account that was created as part of the pre-installation requirements. If you are in doubt as to the correct information necessary to fill these fields, contact your database and/or system administrator. The connect string/datasource is be utilized by the ONE/JobFactory to connect to a database when a connection is required during the execution of SQR jobs.

✏


a. Identify the user name, password, and connect string/datasource for the database account that was created as part of the pre-installation requirements. The default user name that we previously recommended is brioportal. Remember that IBM DB2 and Sybase are case sensitive.

If you are in doubt as to the correct information necessary to fill these fields, contact your database and/or system administrator. The connect string is utilized by the ONE/JobFactory to connect to a database when a connection is required during the execution of SQR jobs.


❑ The term connect string is appropriate for Oracle. The connect string in this case is a service name entry in the tnsnames.ora file located on the machine where Brio Portal is being installed.

❑ For Microsoft SQL Server, the datasource is the ODBC datasource configured where the metadata is being installed. The database server could be on the local or a remote machine.

❑ For Informix and DB2, the datasource is the name of the database created for Brio Portal.

❑ For Sybase, a connect string/datasource is not required.


b. Test the JDBC connection.

After you supply the database connectivity information, the installer attempts to verify the information by connecting to the database. A DOS window opens while the connection is being tested.

❑ If the connection succeeds, proceed to Step 13: Identify the host machine.

❑ If the connection fails, view the error log and correct your database connectivity parameters.

13 Identify the host machine.

The host name and IP address of the machine from which you are installing is automatically supplied for you.

14 Identify the mail server.

Note Complete this step only if you are installing or upgrading ONE/EventServer Agent.

In order for ONE/EventServer to provide email notifications, you must specify the name of your outgoing mail server. If you do not know the name of your mail server, enter a placeholder to proceed with the installation. After you have installed all Brio Portal components and started your the Brio Portal Service, you can use ONE/Administrator to specify the correct mail server.


✏


The installer prompts you to review the Setup Type, Target Directory, Host Information, Database Information, Mail Server Information, and SQR Information along with the names and port numbers of all the installed service agents. Record these settings for future reference. Click Next to continue the installation.


At this point a Java program automatically copies files into their target directories and a series of Java programs populates the database. During this portion of the installation, the installer displays several DOS command windows. This step takes several minutes.

Two log files, Install.log and Drop.log, are produced at the following path:


At the end of the installation, the installer prompts you to review Install.log and Drop.log. Be sure to review these files to determine that all database operations were performed successfully. If you encounter fatal errors, fix them and run the installation again.

Messages that appear to be errors can often be found in Drop.log. These errors are usually benign. The installer searches these errors and notifies you if any of them are problematic. Most benign errors occur during fresh Brio Portal installations, and they usually involve the failure to delete a non-existent table or constraint. If your DBA is confident that your Drop.log errors pose no problem, proceed with the installation.

Note the paths to the following files. If you choose not to delete the log files after installing Brio Portal, these files remain on your system. You can use them in cooperation with Brio Technical Support to troubleshoot problems stemming from installation errors.

\Program Files\Brio\BrioPortal\log\MInstall.log \Program Files\Brio\BrioPortal\log\CreateConfig.log \Program Files\Brio\BrioPortal\log\Install.log \Program Files\Brio\BrioPortal\log\Drop.log \Program Files\Brio\BrioPortal\log\JavaErrors.log \Program Files\Brio\BrioPortal\etc\InstallProps \Program Files\Brio\BrioPortal\etc\SAProps

When the installation is complete, select the Yes check box to view the Readme.txt file; then click Finish.


Caution After you have examined the Install.log, InstallProps, and SAProps files, delete them. They contain passwords in clear text. You can manually delete these files after the installation is complete. (CreateConfig.log contains encrypted passwords, so it is not vital that you delete it.)

17 Copy the config.dat file.

After you install the Brio Portal components, and configure ONE/ServiceBroker, ONE/JobFactory, and ONE/AuthenticationServer using ONE/Administrator, copy the config.dat file from the BrioPortal directory that the ONE/NameServer uses to the BrioPortal directory that ONE/ServiceBroker, ONE/JobFactory, and ONE/AuthenticationServer use.

The default directory is:

C:\Program Files\Brio\BrioPortal\etc

The config.dat contains information that each service agent needs to start up and connect to ONE/NameServer.

18 Configure ONE/JobFactory for Microsoft SQL Server.

Note Complete this step only if you intend to run SQR jobs against a Microsoft SQL Server database.

To run any SQR engine, configure the corresponding ONE/JobFactory to run as a user instead of as System.

a. Select Control Panel.

b. Select Services.

c. Select ONE/JobFactory jf_name.

d. Click Startup.

e. Click this account and specify a user other than Local System.

!

✏


Brio Portal Service Agents Installation VerificationTo verify Brio Portal Service Agent installation:

1 Verify the installed files.

a. Verify the file system.

A hierarchy of subdirectories should now exist in the installation directory specified earlier as the root. (Remember that the default root directory name is Program Files\Brio.) Immediately below Brio (or the directory name you specified) should be BrioPortal, jre, and lib directories. (The ReportMart20.zip file should be in this lib directory.) Verify this directory structure from the Windows File Manager or from a DOS command window.

b. Verify the contents of all hosts files.

If you are running Brio Portal service agents on multiple hosts, ensure that the hosts file on each host computer contains entries for all Brio Portal hosts. Once you have verified that all hosts are entered in the hosts file, you can copy that hosts file to all other Brio Portal hosts. You can usually find the hosts file at the following path:

c:\winnt\system32\drivers\etc\hosts

2 Start the Brio Portal Server and verify that it has started.

View the Brio Portal Server settings in the Windows Services group accessed from the Windows Control Panel. The Services default setting for the Brio Portal Server is Manual startup mode. You can reset the Brio Portal Server to Automatic startup mode if you wish.

If the Server is not already running, select BrioONE/BrioPortal BP_hostname and click the Start button. If individual agents are listed, they can be started individually by selecting the agent and clicking the Start button.

Note The Brio Portal Server, which includes the six service agents, was introduced in Brio Portal 7.0. This Server allows multiple agents to run as a single process. The installer creates a Brio Portal Server on the host computer only for a Typical install. When the Brio Portal Server is installed

on Windows, the individual service agents are not visible in the Services window, but they are listed in ONE/Services.

✏


3 Start individual agents as service agents if desired.

To start individual service agents as Windows services, you don’t need to re-install the software. Follow these steps:

a. Use ONESetup to add a Windows service for each service agent (you need to specify the service agent’s name, which you can find when you list the service agents in ONE/Services). Choose Start�Programs�Brio�Brio Portal�ONESetup.

b. Start the individual services instead of the BrioPortal service.

See “Brio Portal Service Agents Custom Installation or Upgrade” on page 30 to install additional service agents.

Note The performance of the Server you have installed can be enhanced through tuning of the Java Virtual Machine. See the Brio Portal Administrator’s Guide for tuning information.

✏

Brio Portal Service Agents Installation Verification 45

KnowledgeServer Installation or UpgradeTo install or upgrade KnowledgeServer:

1 Install Brio Portal if it not already installed.

KnowledgeServer requires an existing Brio Portal domain in order to be successfully installed. It need not be on the same machine, but it must be accessible over the network. Please make sure you have installed ONE/NameServer and the Service Agents which connect to it before you install KnowledgeServer.

Note If you are installing multiple Brio Portal components in sequence, click OK when asked if you want to proceed with installing KnowledgeServer, then go to Step 5.




You must enter a license key to install the KnowledgeServer files to your computer. When prompted by the installation software, enter the license key provided with the installation media. The key should be in a format similar to the following:

6555-1212-0319-0224-5460-9911-1351

4 Select KnowledgeServer and click Install.

Your license key determines which Brio components you can install. Click a component name to select it.


Read the Welcome information and the Software License Agreement. To continue with the installation, click Yes to accept the license agreement. The Installer warns you that you must have Brio Portal installed before you install KnowledgeServer.

✏



If Brio Portal is not installed on this machine, the default installation directory shown is C:\Program Files\Brio.

If Brio Portal is installed on this machine, the default directory shown is the location where Brio Portal is installed. KnowledgeServer must be installed in the same directory as Brio Portal.

KnowledgeServer Installation or Upgrade 47

7 Select the installation type.

Note The two Upgrade options appear only if an existing installation is detected in the directory specified in Step 6: Select the destination directory.

■ Typical – Installs both the ONE/SearchServer and ONE/CrawlServer service software on the host computer. Select this option if you are performing a new installation of both ONE/SearchServer and ONE/CrawlServer.

■ Custom – Allows you to distribute ONE/SearchServer and ONE/CrawlServer on different machines. This improves the performance of searching and indexing Web content.

❑ ONE/SearchServer – Installs only ONE/SearchServer on this machine. A Brio Portal domain supports only one ONE/SearchServer installation. After selecting the ONE/SearchServer option, the installer proceeds to Step 9: Select the database type.

❑ ONE/CrawlServer – Installs only ONE/CrawlServer on this machine. A Brio Portal domain supports only one ONE/CrawlServer installation. When you select the ONE/CrawlServer option, the installer asks you to specify the ONE/SearchServer host and index port, and then proceeds to Step 14: Enter the Name Server connectivity information as prompted.

✏


Caution A Brio Portal domain supports only one ONE/SearchServer and one ONE/CrawlServer. If you select either the Typical or Custom install option, any existing installation is overwritten. To upgrade ONE/CrawlServer and ONE/SearchServer installations without overwriting their data, select one of the Upgrade options.

■ Upgrade a Typical Install – Upgrades both the ONE/SearchServer and ONE/CrawlServer service software using the typical settings. The installer proceeds to Step 15: Review installation selections and settings.

■ Upgrade a Custom Install – Upgrades a distributed installation of ONE/SearchServer and ONE/CrawlServer. The installer proceeds to Step 15: Review installation selections and settings.

Note If you are installing ONE/SearchServer and ONE/CrawlServer on different host computers, you must install ONE/SearchServer before installing ONE/CrawlServer. When you install ONE/CrawlServer separately, the installer asks for ONE/SearchServer’s host name and Index

port number. The ONE/SearchServer installation configures service agent type information in the Brio Portal repository required by the ONE/CrawlServer installation.

8 Enter Service Agent information.

!

✏


You may specify the name and port number for each service agent that you install. To do so, select the desired service agent from the list in the Typical Setup dialog box, and then click Change. A service agent properties dialog box appears containing default values. To change the values, type the new name and port number and click OK.

To specify advanced properties for each service agent, click Advanced in the Service Agent Properties dialog box.

The following tables display service agent properties and default values.

When you specify a port number, ensure that it is unique and available for this host. Use the Windows netstat command to determine which ports are in use.


Tab le 5 General Service Agent Properties

Service Agent Type Name Port

ONE/SearchServer SS_hostname 1490

ONE/CrawlServer CS_hostname 1491

Tab le 6 Advanced Service Agent Properties for ONE/SearchServer

Property Name Default Value

Query Port 2000

Index Port 2001

Tab le 7 Advanced Service Agent Properties for ONE/CrawlServer

Property Name Default Value

Port 1 2101

Port 2 2102

Port 3 2103

Port 4 2104


Select IBM DB2, Informix, Microsoft SQL Server, Sybase, or Oracle 8.1.5 or later, or Oracle earlier than 8.1.5 as the Brio Portal database type.

Note Brio Portal and KnowledgeServer should have the same database account.


■ Oracle Users – The installer skips this step if you chose Oracle as your database type, and it automatically installs the Oracle JDBC driver based on the version of Oracle you previously selected. Classes12.zip is used with Oracle versions 8.1.5 and later. Classes111.zip is used with versions of Oracle earlier than 8.1.5.

■ Informix or DB2 Users – If you chose Informix or DB2 as your database type, the installer asks you whether the file system should be searched for the directory containing the proper JDBC driver or whether you prefer to specify the location of the file.

❑ If you select Yes, the file system’s C and D drives are searched for the correct file. When Yes is selected, the installer brings up the search result and its directory path. You can accept the directory that was found or you can browse to a different location for the JDBC driver.

❑ If you select No, you are prompted to specify the full directory path containing the correct file.

■ Sybase Users – If you chose Sybase as your database type, you must specify the location of the JDBC driver (jconnect40.zip or jconnect41.zip).

11 Identify the database host, port number, and name.

Note Make sure you use the same database as Brio Portal.

✏

✏


■ Host Name – Machine running the database server utilized by ONE/Repository. Oracle users can find this information in the tnsnames.ora file located on the machine where Brio Portal is installed.


■ Name/SID – Database or instance used to store the Brio Portal metadata. For Sybase users, it is the specific database server where the Brio Portal Sybase database was created.


Note Make sure you use the same database account as Brio Portal.✏


Identify the user name, password, and connect string/datasource for the database account that was created as part of the pre-installation requirements. If you are in doubt as to the correct information necessary to fill these fields, contact your database and/or system administrator.


■ The term connect string is appropriate for Oracle. The connect string in this case is a service name entry in the tnsnames.ora file located on the machine where Brio Portal is being installed.

■ For Microsoft SQL Server, the datasource string is the ODBC datasource configured where the metadata is being installed. The database server could be on the local or a remote machine.

■ For Informix and DB2, the datasource is the name of the database created for Brio Portal.


13 Indicate whether ONE/NameServer is installed on the same host computer.

If you select No, you need to provide ONE/NameServer’s connectivity information, host name, and port number.

Note If ONE/Name Server is installed on a different host computer, the ONE/NameServer service must be running on that host in order to install either the ONE/SearchServer or

ONE/CrawlServer.

If you are installing the service agents on the same host computer as ONE/NameServer, you

should continue with Step 14. The ONE/NameServer service does not need to be running in order to install the service agents.

✏


14 Enter the Name Server connectivity information as prompted.

Enter the BPAdministrator password (this is not the Admin password), the host name of the computer where ONE/NameServer is running, and the port number that ONE/NameServer is listening on. The default port for ONE/NameServer is 1498.

Note The default password for BPAdministrator is 12345678. You should change this password after installation is complete.


Review the installation parameters (your accepted settings for the installation) and click Next to accept them as listed, or click Back to change parameters. Record these settings for future reference.

16 Complete the installation

A Java program automatically copies files into their target directories and a series of Java programs populates the database. During this portion of the installation, the installer displays several DOS command windows. This step takes several minutes.

✏


If you are installing ONE/SearchServer and ONE/Crawl Server for the first time, the installer displays an error message in the console stating, “Error: serviceagent_name not found in config file”. This message is not applicable for first time installations and can be safely ignored.

If ONE/SearchServer is installed, two log files, Install.log and Drop.log, are produced in the following directory:


At the end of the installation, the installer prompts you to review Install.log and Drop.log. Be sure to review these files to determine that all database operations were performed successfully. If you encounter fatal errors, fix them and run the installation again.

Messages that appear to be errors can often be found in Drop.log. These errors are usually benign. The installer searches these errors and notifies you if any of them are problematic. Most benign errors occur during fresh Knowledge Server installations, and they usually involve the failure to delete a nonexistent table or constraint. If your DBA is confident that your Drop.log errors pose no problem, proceed with the installation.

Note the paths to the following files. If you choose not to delete the log files after installing the KnowledgeServer, these files remain on your system. You can use them in cooperation with Brio Technical Support to troubleshoot problems stemming from installation errors.

\BrioPortal\log\MInstall.log

\BrioPortal\log\CreateConfig.log

\BrioPortal\log\Install.log

\BrioPortal\log\Drop.log

\BrioPortal\log\JavaErrors.log

\BrioPortal\etc\InstallProps

\BrioPortal\etc\SAProps

When the installation is complete, view the Readme.txt file by selecting the Yes check box; then click Finish.

Caution After you have examined the Install.log, InstallProps, and SAProps files, delete them. They contain passwords in clear text. You can manually delete these files after the installation is complete. (CreateConfig.log contains encrypted passwords, so it is not vital that you delete it.)

!


17 Specify the language and URL encoding properties.

We recommend you set these properties immediately after completing your Brio Portal system installation.

a. Set ONE/SearchServer’s Language property.

Before starting your first crawler operation, set the Language property of your ONE/SearchServer (in ONE/Services). For more information, see the chapter titled “Managing KnowledgeServer” in the Brio Portal Administrator’s Guide.

b. Set ONE/SearchServer’s URL Encoding property.

Before starting your first crawler operation, set the URL Encoding property for your Brio Portal domain. This property is set in ONE/Publisher on the root (Brio Portal) category. To crawl or search content in non-Latin-1 languages, or if you are using the WebSphere or iPlanet native servlet engine, you must set the URL Encoding to UTF8. For more information, see the appendix titled “Localization” in the Brio Portal Administrator’s Guide.


ONE/Administrator Installation and ConfigurationYou can install ONE/Administrator to run as a conventional Windows application or you can install it to operate within a Web browser. Separate installations are required for each option. Read the specific requirements before proceeding with an installation.

Brio recommends that you install only the ONE/Administrator Desktop version until you have finished planning distributed administration responsibilities.

Note If you have RM/Administrator (previous version of ONE/Administrator) on your system, remove it using the Add/Remove Programs option on the Windows Control Panel before you install the new version.

Installing ONE/Administrator Desktop VersionONE/Administrator is designed for use from any desktop system with network access to Brio Portal servers. It provides a secure, locally accessible method of administering a Brio Portal server.

Note If you are installing multiple Brio Portal components in sequence, click OK when asked if you want to proceed with installing ONE/Administrator (Desktop Version), then go to Step 4.

To install ONE/Administrator Desktop version:



2 If prompted, enter the license key.

A license key must be supplied to extract the Brio Portal files from the CD. If you have not previously entered a valid license key on this machine, you are prompted by the installation software to enter the license key provided with the installation media. The key is in a format similar to the following:

6555-1212-0319-0224-5460-9911-1301

✏

✏


If you have a currently valid license key on this machine for Brio Portal, you do not need to provide another license key.

3 Select ONE/Administrator (Desktop Version) v7.0.3 for Windows NT 4 from the list of Brio Portal components.



5 Select an destination directory.

The default installation directory is C:\Program Files\Brio\ONEAdminDeskTop. Select Browse to specify a different location. If the directory does not exist, the installer creates it for you.

6 Select a program folder or enter a new program folder name.

The default program folder is Brio\ONEAdministrator.

The setup program copies the appropriate files and then displays the installed components.

7 Continue with the installation of other Brio Portal components or click Finish to complete ONE/Administrator installation.

Note For post-installation steps, see “Configuring ONE/Administrator” on page 66.✏

ONE/Administrator Installation and Configuration 59

Installing ONE/Administrator Browser VersionYou can run ONE/Publisher via a Web server from within a Netscape or Microsoft Web browser. This allows you to publish to the Brio Portal server remotely and eliminates the need for remote administrators to install a client component on their desktop. This is a good solution for distributing the content publishing responsibilities among a larger number of administrators.

This configuration runs ONE/Publisher from within the Netscape or Microsoft Internet Explorer Web browser. To run in this configuration, you need the following:

■ Clients – Netscape Navigator/Communicator (version 4.06 or later) or Internet Explorer 4.x/5.x, (version 4.01 with SP1 is recommended)

■ Web Servers – iPlanet 4.0/4.1 or Microsoft Internet Information Server 4.0/5.0.

Note If you are installing multiple Brio Portal components in sequence, click OK when asked if you want to proceed with installing ONE/Administrator (Browser Version), then go to Step 4.

To install the browser version of ONE/Administrator:

1 On your Web server system, run setup.exe from the NT directory of the Brio Portal CD.



You must supply a license key to install the Brio Portal files from the CD. When prompted by the installation software, enter the license key provided with the installation media.

The key should be in a format similar to the following:

6555-1212-0319-0224-5460-9911-1301

3 Select ONE/Administrator (Browser Version) 7.0.3 for Windows NT from the listing of Brio Portal products.

✏




5 Choose a destination location.

The installation points to the host machine on which the Web server is installed. The default installation directory is C:\Program Files\Brio\ONEPublisher.


6 Click Finish to complete ONE/Administrator (Browser Version) installation.


7 Point the Web server to the installation directory (for example, C:\Program Files\Brio\ONEPublisher).

To access ONE/Administrator using a Web browser:

a. Within your Web server, create a virtual directory (in IIS) or an additional

document directory (in iPlanet) named ONEPublisher that points to

C:\Program Files\Brio\ONEPublisher.

b. Add execute permissions to the new directory.

Consult your Web server documentation for directions on assigning virtual directories.

8 Test ONE/Publisher in your Netscape browser.

a. Close all Netscape browsers running on your machine. On the client machine on which the Netscape browser is installed and from which you access the ONE/Administrator host machine, disable Netscape Navigator/Communicator’s Just-In-time (JIT) compiler.

To do so, locate the file jit3240.dll and rename it to something else. This file is normally found under:

\ProgramFiles\Netscape\Communicator\Program\Java\Bin

b. Clear the CLASSPATH environment variable.

Choose Start�Settings�Control Panel�System, then click the Environment tab.

Client machines running Netscape Navigator/Communicator do not require a local installation of Sun’s JDK, because the Netscape browser contains its own version of the Java Virtual Machine (JVM). If the client machine’s CLASSPATH variable is set, Netscape will try to load the class file from the local machine, which creates security problems.

c. In your browser, go to:

http://hostname/virtual_dir

or

http://hostname:port/virtual_dir/index.html


Substitute your host machine name for hostname, and substitute your ONE/Administrator installation directory name for install_dir. (For example, http://machine.brio.com:80/ONEPublisher.)

If the client does not recognize the host name, replace the hostname with the host IP address, or configure it on the Windows host file, and confirm that your DNS is configured correctly.

9 Test ONE/Publisher in Microsoft Internet Explorer.

a. In Microsoft Internet Explorer, go to:

http://hostname/virtual_dir

or

http://hostname:port/virtual_dir/index.html

Substitute your host machine name for hostname, and substitute your ONE/Administrator installation directory name for install_dir. (For example, http://machine.brio.com:80/ONEPublisher.)

If the client does not recognize the host name, replace the hostname with the host IP address, or configure it on the Windows host file, and confirm that your DNS is configured correctly.

10 Email the following instructions to the your clients, replacing URL with the actual URL you tested in Step 8: Test ONE/Publisher in your Netscape browser and Step 9: Test ONE/Publisher in Microsoft Internet Explorer.

Complete the following steps on all client machines from which you access the

ONE/Administrator host machine:

1. (Netscape Browsers only) Close all Netscape browsers running on you machine, and disable Netscape Navigator/Communicator’s Just-In-Time (JIT) compiler. To do so, locate the file JIT340.dll and change its name. This file is usually located in:

\Program Files\Netscape\Communicator\Program\Java\Bin

2. In your Web browser, go to URL.

3. (Netscape Browsers only) Clear the CLASSPATH variable. Client machines running

Netscape Navigator/Communicator do not require a local installation of Sun’s JDK, because the Netscape browser contains its own version of the Java Virtual Machine (JVM). If the client machine’s CLASSPATH variable is set, Netscape tries to load the

class file from the local machine, which creates security problems.


Troubleshooting for Netscape BrowserIf the ONE/Administrator login dialog does not come up, click Reload to reload the applet. If it still does not come up, look at error messages on the Java Console following these steps:

1 Choose Communicator��Java Console, or Tools��Java Console (depending on your version of Netscape).

If you encounter errors, start another session. Close all Netscape browser windows, then open the Windows Task Manager. Go to the Processes page, select netscape.exe, and then click End Process.

2 Stop the Web server and restart it (go to Start�Control Panel��Services).

3 Open a Netscape browser window and start ONE/Administrator.

Troubleshooting for Internet ExplorerIf the ONE/Administrator login dialog does not come up, click Reload to reload the applet. If it still does not come up, look at error messages on the Java Console following these steps:

1 Choose Tools�Internet Options; then click the Advanced tab.

2 Select Java VM and choose Java Console enabled.

3 Restart Internet Explorer.

4 Choose View�Java Console.


Installing ONE/Administrator (Browser Version) Without a Web Server (Internet Explorer Only)You can install ONE/Administrator Browser version on a local machine (or on a network drive) to run within Microsoft Internet Explorer 4.x.

Note If you are installing multiple Brio Portal components in sequence, click OK when asked if you

want to proceed with installing ONE/Administrator (Browser Version), then go to Step 4.

To install the browser version of ONE/Administrator without a Web server:

1 On your Web server system, run setup.exe from the NT directory of the Brio Portal CD.



You must supply a license key to install the Brio Portal files from the CD. When prompted by the installation software, enter the license key provided with the installation media.

The key should be in a format similar to the following:

6555-1212-0319-0224-5460-9911-1301

3 Select ONE/Administrator (Browser Version) 7.0.3 for Windows NT from the listing of Brio Portal products.



5 Choose a destination location.

The installation points to the host machine on which the Web server is installed. The default installation directory is C:\Program Files\Brio\ONEPublisher. If desired, set up sharing on the installation directory.

✏✏


6 Click Finish to complete ONE/Administrator (Browser Version) installation.


7 Run ONE/Administrator from a local Windows machine.

Select File�Open from your Internet Explorer browser menu, and specify the file index.html located in C:\Program Files\Brio\ONEPublisher.

8 Share the ONEPublisher folder with execute privileges.

9 Email the network URL to your client users.

For example, file:\\machine.brio.com\ONEPublisher\index.html or \\machine.brio.com\ONEPublisher\index.html

Configuring ONE/AdministratorAfter you have finished installing ONE/Administrator, complete the following steps:

■ Set up the ONE/Administrator login

■ Change the ONE/Administrator password

■ Select a ONE/Administrator run-time model

Note If you installed the ONE/Administrator Browser version, proceed to Step 3: Select a ONE/Administrator runtime model.

1 Set up the ONE/Administrator login.

a. Start ONE/Administrator. The ONE/Administrator main menu appears.

✏


b. Start ONE/Users by clicking the ONE/Users icon.

The ONE/Administrator Login dialog box appears.

c. Enter the default username (administrator).

d. Enter the default password (administrator).

e. Enter the name and port number of the Brio Portal host.

The Brio Portal host is the server that is running ONE/ServiceBroker. If your system does not recognize the Brio Portal host name, use its IP address.

The main ONE/Users window appears.


2 Change the ONE/Administrator password.

a. Select the user administrator.

b. Click the User Properties icon.

The Brio Portal User Properties dialog box appears with the General page on top.

c. In the Password field, select and delete the current password; then, enter a new password.

d. Confirm the password change in the Confirm Password field.

3 Select a ONE/Administrator run-time model.

ONE/Administrator is designed to be scalable and can be configured to support any environment from a small work group to a large enterprise. The following table lists the available run-time models.


You specify a run-time model by changing the target properties of the ONE/Administrator Desktop shortcut.

Note These changes must be made on the host machine from the system console; they cannot be made remotely.

To change the target properties of the ONE/Administrator Desktop shortcut:

a. Use Windows Explorer to navigate to: C:\WINNT\Profiles\All Users\Start Menu\Programs\Brio\ONE Administrator. The file listing for this directory appears in the right window pane.

b. Select the ONE Administrator shortcut, and then right-click and choose Properties. The ONE Administrator Properties dialog box appears.

c. Click the Shortcut tab.

d. In the Target field, replace rmadmin.exe with the EXE file that corresponds to the run-time model you want to use.

e. Exit ONE/Administrator and restart.

Note To support a large configuration, you must have at least 384 MB RAM. (We recommend 512 MB.)

Tab le 8 ONE/Administrator Run-Time Models

Run-Time Model Number of Users Number of Objects Target

Small Less than 1,000 Less than 1,000 rmadmin32.exe

Medium 1,000–2,000 1,000–2,000 rmadmin.exe

Medium to Large 2,000–4,000 2,000–4,000 rmadmin128.exe

Large Greater than 4,000 Greater than 4,000 rmadmin256.exe

✏

✏


ONE/WebClient Installation and ConfigurationONE/WebClient is a servlet that provides the end-user interface to Brio Portal. ONE/WebClient can run on various commercial Web servers or as a standalone HTTP server. It can be run in any of three different configurations:

■ As a standalone HTTP server from the command line

■ As a standalone HTTP server running as a Windows service

■ As a servlet on a commercial Web server

The administrator can change ONE/WebClient’s configuration without impacting data stored in the Brio Portal. This makes it easy to change your ONE/WebClient configuration if necessary.

Running ONE/WebClient as a Windows service is an easy way to configure ONE/WebClient. This is the recommended configuration for initial installation and for pilot projects. A Windows service is desirable when ONE/WebClient must be up and running whenever the workstation is up and running. This configuration is implemented using HTTP and does not utilize secure sockets (HTTPS).

We recommend the use of a secure sockets-capable server (Microsoft IIS, for example) in any production environment, and in any environment where the local network is not protected by some other means (such as a firewall) or where public users are able to access the ONE/WebClient server. The absence of a secure sockets layer connection allows other users on the network to potentially listen to your network traffic, and thus access your data.

The standalone version is recommended for use in the following environments:

■ Your network is otherwise secured, such as an intranet with a firewall.

■ You are performing a low-security product evaluation.

■ You are operating a small production or development environment and are not concerned about data security.

■ You do not use Brio OnDemandServer as part of the BrioONE product suite.


Installing ONE/WebClient

Note The ONE/WebClient 7.0.3 installer overwrites any configuration information and templates that

exist in the installation directory. If you have a previous version of ONE/WebClient installed, we suggest that you back up any configurations files or templates before installing version 7.0.3. When installation is complete, you must manually reconfigure ONE/WebClient 7.0.3.

To install ONE/WebClient:

1 Remove previous versions of ONE/WebClient (formerly RM/WebSQRIBE).

Before installing ONE/WebClient 7.0.3, use Add/Remove Programs in your Windows Control Panel to remove any previous versions of ONE/WebClient. Brio Portal might not run properly if you have multiple versions of your ONE/WebClient server.

Note If you are installing multiple Brio Portal components in sequence, click OK when asked if you

want to proceed with installing ONE/WebClient, then go to Step 5.





6555-1212-0319-0224-5460-9911-1351

4 Select ONE/WebClient 7.0.3 for Windows NT 4 and click Install.


✏

✏✏

ONE/WebClient Installation and Configuration 71


Read the Welcome information and click Yes to continue with the installation.

6 Select an installation configuration.

■ WebClient - Standalone Version – Installs only ONE/WebClient for use with a standalone HTTP server. Choose this option if you want to test or debug the Web server, if you plan to run the standalone Web server in a production environment, or if you use Netscape Enterprise Server 3.5.x/3.6.x and prefer to use Netscape’s built-in Java servlet engine instead of JRun (not recommended).

Note The standalone method is not supported for BrioONE. If you are using OnDemandServer as a

BrioONE service with your portal, you must run ONE/WebClient through a commercial Web server.

■ WebClient - Web Server Version – Installs ONE/WebClient and provides options for configuring JRun or other servlet engines used in conjunction with a commercial Web server.

✏


■ Upgrade Standalone WebClient to Web Server Version – Configures JRun or other servlet engine to a previously installed WebClient. This option does not reinstall ONE/WebClient. After you accept the License Agreement, the installer proceeds to Step 11: Configure a servlet engine.

7 Accept the License Agreement, then choose a destination location.

The default installation directory is C:\Program Files\Brio, which places ONE/WebClient components in C:\Program Files\Brio\ONEWebClient. Select Browse to specify a different directory location. If the directory does not exist, it will be created for you.

8 Select a program folder.

The default program folder is Brio\ONEWebClient.

Click Next to continue the installation process. The installer copies the ONE/WebClient files into their target directories.

9 Specify the name used to reference ONE/WebClient.

The default name is WebClient. If you use the default name, use this address to invoke ONE/WebClient:

http://hostname:port/servlet/WebClient/main


10 Click Next to continue the installation process.

■ If you are installing the standalone version of ONE/WebClient, the installer proceeds to Step 12: Complete the installation.

■ If you are installing the Web Server version of ONE/WebClient, the installer proceeds to Step 11: Configure a servlet engine.

11 Configure a servlet engine.

■ Configure JRun – Installs and configures the JRun servlet engine used in conjunction with a commercial Web server.

This option invokes the JRun installer. After JRun is installed, supply the information requested and then exit the JRun installation program.

■ Configure Other – Configures either iPlanet (with native servlet engines) or Apache (with JServ servlet engine) Web servers. The native servlet engines must already be installed in order for the automatic configuration to occur.

Depending on which Web server you choose, you need to either select the iPlanet https or httpd directory, or specify the location of the Apache Web server conf directory.

■ Configure Web Server At A Later Time – Skips the Web server configuration and ends the installation process.


Note If you choose to configure a Web server at a later time, you can do so without reinstalling ONE/WebClient. Rerun the ONE/WebClient installation program and choose the upgrade option when asked to select an installation configuration. (See Step 6: Select an installation

configuration.)


View the Readme.txt file by selecting the Yes check box; then click Finish.

Running ONE/WebClient as a Standalone HTTP ServerYou can implement ONE/WebClient as a standalone HTTP server in two ways:

■ Run wsrun.bat – Type wsrun at a DOS command prompt to execute the wsrun.bat file located in the C:\Program Files\Brio\ONEWebClient \ directory.

This method is useful when you are testing or debugging the Web server. ONE/WebClient listens on the default port number 11111.

■ Run ONE/WebClient as a Windows service – Open Services from the Windows Control Panel, and start the Brio ONE/WebClient service. (The Brio ONE/WebClient service is installed with a default Manual startup mode. You may change this to Automatic so that it starts whenever the host machine is brought up.)

This method is useful when you are running the standalone Web server in a production environment. ONE/WebClient listens on the default port number 11111.

To use a port number other than 11111 with either method, change the port number in wsrun.bat and in the Windows Rregistry. Otherwise, there will be a disparity in the port settings.

To run ONE/WebClient, open your browser and type the following URL:

http://hostname:11111/servlet/WebClient/main

Note The standalone method is not supported for BrioONE. If you are using OnDemandServer as a BrioONE service with your portal, you must run ONE/WebClient through a commercial Web

server.

✏

✏


Changing the Windows Registry ValuesTo change an entry, such as the port number value, in the Windows Registry:

1 Run regedit from the Windows Start menu.

2 Click the “+” sign in front of the following folders, in succession:

HKEY_LOCAL_MACHINESOFTWARE

Brio Technology ONE/WebClient

3 Select the ONE/WebClient folder.

The keys and their values appear in the right-hand window.

4 Double-click port.

The Edit String dialog box appears.

5 Enter the new value data for the port number, and then click OK.

Note Changes to the Windows Registry values only affect ONE/WebClient if it is run as a Windows

service.

New Registry EntriesSince Brio Portal release 7.0, there are two new registry entries (under HKEY_LOCAL_MACHINE �SOFTWARE�Brio Technology�ONE/WebClient) that the ONE/WebClient Service uses. These entries replace the old jre_home entry.

Note While ONE/WebClient no longer uses jre_home, keeping the entry in the registry will not create problems.

The new registry entries are:

■ jre_exe – Specifies the path to the JRE executable.

■ jre_args – Specifies the command line arguments for the JRE executable.

The default values for jre_exe and jre_args run with JRE 1.2.2.

✏

✏


If you prefer to use Microsoft’s Java viewer (Jview) instead of JRE, change the Windows service as follows:

1 Update jre_exe with the path for the Jview executable.

2 Update jre_args with the appropriate command line arguments for Jview. Typically this will just require changing the classpath switch from -cp to /cp and removing the -mx switch.

Configuring ONE/WebClient on a Commercial Web ServerThe most efficient and secure way to configure ONE/WebClient is as a servlet running as part of a commercial Web server. This permits the use of secured sockets (HTTPS), which are supported by most commercial Web servers.

Secured sockets virtually eliminate the threat of someone on the network being able to view data transfers between the browser and the Web server. This solution also scales better because it can be used in conjunction with Web server load balancing techniques when running multiple instances of a Web server.

This configuration is ideal for large, secure, product environments. When configuring Web servers to run servlets, you should refer to specific Web server product documentation.

ONE/WebClient can be run with the following Web servers and browsers:

■ Browsers

❑ Netscape Browser versions 4.x

❑ Microsoft Internet Explorer versions 5.x

■ Web Servers

❑ Netscape Enterprise Server 3.5.x/3.6.x with JRun

❑ iPlanet 4.0/4.1 with JRun or native servlet engine

❑ Microsoft IIS 4.0/5.0 server with JRun

❑ Apache with JServ or JRun

❑ IBM HTTP WebServer with WebSphere


ONE/WebClient is based on Sun Microsystems’ Java Servlet API and runs on any Web server that supports this API.

JRun 2.3.3. is distributed with ONE/WebClient, and is automatically installed and configured depending on which installation option you choose. (Additional information about JRun available at http://www.allaire.com/).

Configuring Your Commercial Web ServerTo configure your commercial Web server:

1 Install ONE/WebClient on your local hard drive.

Install either the WebClient - WebServer version or the Upgrade Standalone WebClient To Web Server version. If you so choose, the installer automatically configures JRun 2.3.3, the iPlanet 4.0/4.1 native servlet engine, or JServ for Apache. See “Servlet Engine Configuration Settings (for Commercial Web Servers)” on page 79.

2 Configure ONE/WebClient for your Web server.

Refer to these sections for additional procedures for the Web servers listed:

■ Configuring Apache to Run ONE/WebClient with JServ

■ Configuring IBM HTTP WebServer to Run ONE/WebClient with WebSphere

■ Configuring Microsoft IIS 4.0/5.0 to Run ONE/WebClient with JRun

■ Configuring iPlanet 4.0/4.1 to Run ONE/WebClient with JRun

■ Configuring Netscape Enterprise Server 3.5.x/3.6.x to Run ONE/WebClient with JRun

■ Configuring Netscape Enterprise Server 3.5.x/3.6.x to Run ONE/WebClient Without JRun


Servlet Engine Configuration Settings (for Commercial Web Servers) If you elected to configure JRun, the iPlanet native servlet engine, or JServ for Apache during the ONE/WebClient installation process, the installer automatically configures the following servlet engine settings.

For JRun, you must manually configure additional document directories or virtual directories (depending on the terminology your Web server uses) once the installer completes the installation and configuration process.

■ Classpath

The Installer appends the following files to the classpath:

Note This information assumes you have installed ONE/WebClient under C:/Program Files/Brio.

C:/Program Files/Brio/ONEWebClient;C:/Program Files/Brio/ONEWebClient/classlib;C:/Program Files/Brio/ONEWebClient/classlib/ReportMart20.zip;C:/Program Files/Brio/ONEWebClient/classlib/comutil.jar;C:/Program Files/Brio/ONEWebClient/classlib/spf62.zip;C:/Program Files/Brio/ONEWebClient/classlib/jecf.jar;C:/Program Files/Brio/ONEWebClient/classlib/forms.jar;C:/Program Files/Brio/ONEWebClient/classlib/crawlerurl.jar;C:/Program Files/Brio/ONEWebClient/classlib/xml4j.jar;C:/Program Files/Brio/ONEWebClient/classlib/clientutil.jar;C:/Program Files/Brio/ONEWebClient/classlib/services.jar;

For JRun, the Installer also adds the jrun.jar file to the Java classpath.

■ Heap Size

The installer increases the heap size to 100 MB.

■ Servlet Engine Service Configuration

The installer adds the following Alias values to the Init Args settings, and configures ONE/WebClient to pre-load:

❑ Name – WebClient

❑ Class Name – com.sqribe.WS.WS

❑ Init Arguments – Root=c:\Program Files\Brio\ONEWebClient

✏


Verifying Servlet ConfigurationTo verify that the servlet engine is properly configured:

1 Stop and restart the servlet engine and the Web server

2 Invoke a sample servlet, such as the following for JRun:

http://hostname:port/servlet/Counter

where port is the port where the Web server listens. (The default is 80.) If necessary, double-check the port setting in your Web server.

For example, if the JRun servlet engine is correctly configured, a message appears that is similar to this:

Note For JRun, you must manually configure additional document directories or virtual directories

(depending on the terminology your Web server uses) once the installer completes the installation and configuration process.

3 Invoke ONE/WebClient by starting your browser and entering the URL:


replacing hostname and port with the appropriate information.

✏


Configuring Apache to Run ONE/WebClient with JRunTo configure Apache to run ONE/WebClient with JRun:

1 Append the following line to the end of the Apache httpd.conf file.

Alias /wsmedia/ "C:/Program Files/Brio/ONEWebClient/wsmedia/"

2 Modify the path to the JRun connectors.

Find the LoadModule line for JRun in the httpd.conf file and change it to read as follows:

LoadModule jrun_module C:/JRun/connectors/apache/intel-win/mod_jrun136.dll

The DLL file name reflects the Apache version. For Apache versions 1.3.6 or later, use the DLL file name shown. For Apache 1.3.2 and 1.3.4, use mod_jrun132.dll and mod_jrun134.dll respectively.

Configuring Apache to Run ONE/WebClient with JServTo configure Apache to run ONE/WebClient with JServ:

Change the ApJServVMTimeout setting in the jserv.conf file to a value greater than 100.

Note JServe should be configured to run with Java 1.2. For more information, see the appendix titled “Troubleshooting” in the Brio Portal Administrator’s Guide.

✏


Configuring IBM HTTP WebServer to Run ONE/WebClient with WebSphere The following instructions assume that you have installed ONE/WebClient under C:\Program Files\Brio.

To configure the IBM HTTP WebServer to run ONE/WebClient with WebSphere:

1 Start the IBM WebSphere Admin Server.

Choose Start�Programs�IBM WebSphere�Application Server�Start Admin Server.

2 Start the Administrator’s Console.

Choose Start�Programs�IBM WebSphere�Application Server�Administrator’s Console.

3 Configure the Web Application.

Expand the WebSphere Administrator Domain to select the name of the Web Application (under Application Server�Servlet Engine) on which to run ONE/WebClient. Create these items if necessary. The selected Web Application’s page appears.

4 Click the Advanced tab.


5 Specify the ONE/WebClient classpath, then click Apply.

Add the ONE/WebClient classpaths to the classpath definition. If you installed ONE/WebClient into the default location, the classpaths are:

c:/Program Files/Brio/ONEWebClient/classlib;c:/Program Files/Brio/ONEWebClient/classlib/ReportMart20.zip;c:/Program Files/Brio/ONEWebClient/classlib/comutil.jar;c:/Program Files/Brio/ONEWebClient/classlib/spf62.zip; c:/Program Files/Brio/ONEWebClient/classlib/jecf.jar; c:/Program Files/Brio/ONEWebClient/classlib/forms.jar;c:/Program Files/Brio/ONEWebClient/classlib/crawlerurl.jar; c:/Program Files/Brio/ONEWebClient/classlib/xml4j.jar;c:/Program Files/Brio/ONEWebClient/classlib/clientutil.jar;c:/Program Files/Brio/ONEWebClient/classlib/services.jar;


6 Create a servlet.

Right-click the selected Web Application and choose Create�Servlet. The Create Servlet dialog box appears.

a. On the General page, enter the following information and click Add.

❑ Servlet Name – Type WebClient.

❑ Servlet Class Name – Type com.sqribe.WS.WS.


b. On the Advanced page, specify the following information and click OK.

❑ Init ParmName – Type Root.

❑ Init Parm Value – Enter the path to the installation location. The default location is C:/Program Files/Brio/ONEWebClient.

❑ Load At Startup – Select True from the drop-down list.


Note To avoid performance degradation, increase the virtual memory used by Java.

From the Administrator’s Console, expand WebSphere Administrative Domain to select Default_Server under the computer hostname. Then, 0n the General page, type -mxXXXM in the Command Line Arguments field, where XXX is the amount of memory required (in

megabytes). If enough physical memory is available, start with 100 MB and increase it if java.lang.OutOfMemory errors occur.

7 Restart the Application Server.

Right-click the selected Application Server and choose Start.

8 Specify the ONE/WebClient aliases within the IBM HTTP WebServer.

a. Launch your Web browser and point it to the URL for the IBM Http WebServer, for example, http://localhost.

✏


b. Click Configure Server, and then expand the Mappings entry under IBM Administration Server to select Aliases.


c. Configure the following settings and click Apply:

❑ Set Alias Expressed As to URL Path.

❑ Enter //wsmedia// in the Alias For Directory For Filename field.

❑ Enter C:/Program Files/Brio/ONEWebClient/wsmedia/ in the Actual Directory Or Filename field.

Note Make sure you type two slashes before and after the alias for directory or filename. Use single slashes for the actual directory or filename.

9 Restart the IBM HTTP WebServer.

✏


Configuring Microsoft IIS 4.0/5.0 to Run ONE/WebClient with JRunThe following procedure assumes that you have installed JRun to run with Microsoft IIS 4.0/5.0.

To configure Microsoft Internet Information Server 4.0/5.0 to run ONE/WebClient with JRun:

1 From within IIS, run the Internet Service Manager.

2 Under the IIS server (name of the machine on which IIS is installed), select Default Web Site.

3 Right-click to get a menu and select New�Virtual Directory to invoke the Virtual Directory wizard.

4 Add the alias wsmedia.


5 Point to the physical path.

c:\Program Files\Brio\ONEWebClient\wsmedia

6 Click Next, accept the defaults, and choose Finish.

Note See “Servlet Engine Configuration Settings (for Commercial Web Servers)” on page 79 for

information on JRun configuration settings. ✏


Configuring iPlanet 4.0/4.1 to Run ONE/WebClient with JRunThis procedure assumes that you have installed JRun to run with iPlanet 4.0/4.1 and that you have installed Netscape Enterprise Server under c:\Netscape\Server4. If you have not chosen these defaults, please make the appropriate substitutions.

To configure iPlanet 4.0/4.1 to run ONE/WebClient with JRun:

1 Using the Netscape Server administration tool, disable the Servlet Engine by choosing No, OK, and then Save and apply changes.

2 Configure an additional document directory.

Specify the requested information as follows:

■ URL Prefix – wsmedia

■ Map To Directory — C:/Program Files/Brio/ONEWebClient/wsmedia


The additional document directory allows ONE/WebClient to locate the graphics it uses when a user navigates in Brio Portal.

3 Click OK and then Save and apply changes.




Configuring Netscape Enterprise Server 3.5.x/3.6.x to Run ONE/WebClient with JRunTo configure Netscape Enterprise Server 3.5.x/3.6.x to run ONE/WebClient with JRun:

1 Using the Netscape Server administration tool, activate the Java interpreter by selecting Yes and clicking OK, followed by Save and apply.

Generally the Netscape Server Administration tool automatically configures the paths. The defaults are normally correct.

2 Configure an additional document directory, using the prefix and directory illustrated below.

The additional document directory allows ONE/WebClient to locate the graphics used when a user navigates in Brio Portal.

3 Click OK and then Save and apply changes.




Configuring Netscape Enterprise Server 3.5.x/3.6.x to Run ONE/WebClient Without JRunThis procedure is optional but not recommended. It assumes that you prefer not to use JRun with Netscape Enterprise Server and that Netscape Enterprise Server has been installed under c:\Netscape35. If you have not chosen this default location, please make the appropriate substitutions.

To configure Netscape Enterprise Server 3.5.x/3.6.x to run ONE/WebClient without JRun:

1 Using the Netscape Server administration tool, activate the Java interpreter by choosing Yes, then OK, and then Save and apply.

Generally the Netscape Server Administration tool automatically configures the paths (as shown below). The defaults are generally correct.

2 Confirm that your server’s Java Servlet support has been correctly activated.

Using your browser, access the following page on your server:

http://hostname:port/servlet/BrowserDataServlet

replacing hostname and port with the appropriate information.

If the server’s Servlet support is functioning correctly, the browser displays a Web page similar to the following.


3 Edit the obj.conf file.

a. Locate obj.conf.

Part of the Netscape Server configuration is stored in a file called obj.conf. This file can be located under the Netscape installation directory.

The picture below shows the location of obj.conf on a sample system. Note that the Netscape server is installed under the directory Netscape35 and the machine name is z00.

b. Edit the classpath definition.

Open obj.conf using an editor and locate the classpath definition using your editor’s search feature to find the word classpath. The line you are looking for looks like:

Init classpath="c:/Netscape35/Server\\wai\\java\\nisb.zip;c:/Netscape35/Server\\js\\samples; c:/Netscape35/Server\\plugins\\Java\\classes\\serv3_0.zip;c:/Netscape35/Server\\plugins\\Java\\local-classes; c:/Netscape35/Server\\plugins\\Java\\classes\\servlet3_5.zip;"dpath=" c:/Netscape35/Server/plugins/Java/bin"fn="SJavaBootInit" “


Add the ONE/WebClient classpaths to the classpath definition. If you installed ONE/WebClient into the default location (c:/Program

Files/Brio), the ONE/WebClient classpaths are:

c:/Program Files/Brio/ONEWebClient/classlib;c:/Program Files/Brio/ONEWebClient/classlib/ReportMart20.zip;c:/Program Files/Brio/ONEWebClient/classlib/comutil.jar;c:/Program Files/Brio/ONEWebClient/classlib/spf62.zip; c:/Program Files/Brio/ONEWebClient/classlib/jecf.jar; c:/Program Files/Brio/ONEWebClient/classlib/forms.jar;c:/Program Files/Brio/ONEWebClient/classlib/crawlerurl.jar; c:/Program Files/Brio/ONEWebClient/classlib/xml4j.jar;c:/Program Files/Brio/ONEWebClient/classlib/clientutil.jar;c:/Program Files/Brio/ONEWebClient/classlib/services.jar;

After adding the ONE/WebClient classpaths to obj.conf, the lines that define the classpath will look like:

Init classpath="c:/Netscape35/Server\\wai\\Java\\nisb.zip; c:/Netscape35/Server\\Js\\samples; c:/Netscape35/Server\\plugins\\Java\\classes\\serv3_0.zip; c:/Netscape35/Server\\plugins\\Java\\local- classes;c:/Netscape35/Server\\plugins\\Java\\classes\\servlet3_5.zip;c:/Program Files/Brio/ONEWebClient/classlib; c:/Program Files/Brio/ONEWebClient/classlib/ReportMart20.zip; c:/Program Files/Brio/ONEWebClient/classlib/comutil.jar; c:/Program Files/Brio/ONEWebClient/classlib/spf62.zip; c:/Program Files/Brio/ONEWebClient/classlib/jecf.jar; c:/Program Files/Brio/ONEWebClient/classlib/forms.jar;c:/Program Files/Brio/ONEWebClient/classlib/crawlerurl.jar; c:/Program Files/Brio/ONEWebClient/classlib/xml4j.jar;c:/Program Files/Brio/ONEWebClient/classlib/clientutil.jar"c:/Program Files/Brio/ONEWebClient/classlib/services.jar;ldpath="c:/Netscape35/Server/plugins/Java/bin" fn="SJavaBootInit" “

Note Use a forward slash (/) for the path name.✏


Save obj.conf and click Apply at the top of the Netscape Server Administration tool. The following screen appears:

c. Click Load Configuration Files.

4 Configure an additional document directory using the prefix and directory illustrated below; then, click OK and Save and apply changes.

The additional document directory is used to allow ONE/WebClient to locate the graphics it uses when a user navigates Brio Portal.


5 In the servlets.properties file, located in c:\Program Files\Brio\ONEWebClient, add or update these two lines:

servlet.WebClient.code=com.sqribe.WS.WS servlet.WebClient.initArgs=Root=c:/Program Files/Brio/ONEWebClient

Note Use forward slashes (/).

6 Add the initfile path to the obj.conf file.

Find this entry at the end of obj.conf:

<Object name="servlets"> Service fn="Java-run" class="sun/servlet/netscape/NSRunner" vpath="/servlet" </Object>

Edit this entry so that it looks like the following entry. The text you must add is shown here is red italics.

<Object name="servlets">Service fn="Java-run" class="sun/servlet/netscape/NSRunner" vpath="/servlet" "initfile="c:/Program Files/Brio/ONEWebClient/servlets.properties" </Object>

✏


7 Restart the Netscape server.

As Netscape servers require, you need to start the server’s admin application, locate the server, and click Apply to apply changes. Please refer to your server documentation. Then restart the server.

8 Once configured correctly, start your browser and use the following URL to access ONE/WebClient:


Replace hostname and port with the appropriate information.

Manually Loading Class FilesThere is a known problem with Netscape Enterprise Server 3.5.x/3.6.x’s ability to load classes from JAR files. Therefore, you might need to unzip the JAR files and use the class files instead.

The following procedure outlines the steps for manually extracting the class files from the JAR files. This procedure assumes you installed ONE/WebClient under c:\Program Files\Brio, that JDK 1.1.x or JDK 1.2 is on this machine, and that JDK 1.1.x or JDK 1.2 is part of the path.

To manually load class files:

1 Stop Netscape Enterprise Server.

2 Open a DOS command window and go to the following directory:

c:\Program Files\Brio\ONEWebClient\classlib

3 Type the following commands at the DOS command prompt:

jar -xvf services.jarjar -xvf comutil.jarjar -xvf jecf.jarjar -xvf forms.jarjar -xvf crawlerurl.jarjar -xvf clientutil.jarjar -xvf xml4j.jar jar -xvf services.jar


4 Verify that the following directories exist and are not empty:

c:\Program Files\Brio\ONEWebClient\classlib\com\brio\comutil c:\Program Files\Brio\ONEWebClient\classlib\javax\commerce\utilc:\Program Files\Brio\ONEWebClient\classlib\com\brio\portal\forms101c:\Program Files\Brio\ONEWebClient\classlib\com\brio\portal\crawlerurlc:\Program Files\Brio\ONEWebClient\classlib\com\brio\portal\clientc:\Program Files\Brio\ONEWebClient\classlib\com\ibmc:\Program Files\Brio\ONEWebClient\classlib\org

5 Restart Netscape Enterprise Server.

Removing ONE/WebClient Software from Microsoft Windows SystemsTo remove ONE/WebClient, manually remove the service before uninstalling from the Control Panel. To do so, type the following on a DOS command line:

c:\Program Files\Brio\ONEWebClient\bin\WSService -u

replacing Program Files\Brio\ONEWebClient with your WebClient home directory if you did not use the default.


ONE/Integrator InstallationTo install ONE/Integrator:

Note If you are installing multiple Brio Portal components in sequence, click OK when asked if you want to proceed with installing ONE/Integrator, then go to Step 4.





6555-1212-0319-0224-5460-9911-1351

3 Select ONE/Integrator 7.0.3 for Windows NT and click Install.




5 Choose the destination location.

The default location is C:\Program Files\Brio.

6 Select a program folder.

The default program folder is Brio\ONEIntegrator.

✏

ONE/Integrator Installation 101

7 Click Next to complete the installation.

When the installation is finished, you should see the following (assuming that you installed at C:\Program Files\Brio):

■ C:\Program Files\Brio\lib contains authdriver.zip, comutil.jar, crawlerurl.jar, jcchart.jar, ReportMart20.zip, spf62.zip, sqrchart.jar, swing.jar, xerces.jar, and xml4j.jar.

■ C:\Program Files\Brio\jre\jre1.2 contains Sun Microsystems’ JRE 1.2 (122).

■ C:\Program Files\Brio\ONEIntegrator is the ONE/Integrator directory.

Note Within the ONEIntegrator directory, the bin directory contains the ONEScript.bat and onesh.bat DOS batch files generated by the installation program. The src directory

contains the shell.scr script file invoked by the onesh.bat file.

✏


Troubleshooting Your Brio Portal InstallationThis section contains troubleshooting information for these areas:

■ Installing Brio Portal 7.0.x with DB2 7.1

■ Connection Refused Errors in Log Files

■ Invalid Template Root Property in WebClient

■ Error Loading Runtime Library

■ LDAP Authentication Limitations

■ Setting Java Debug Properties

■ Java.lang.OutOfMemory Exception

Installing Brio Portal 7.0.x with DB2 7.1

Problem: When you install Brio Portal version 7.0.x with DB2 version 7.1 on a Microsoft Windows system, a problem occurs with the JDBC driver:

ERROR while opening DB connection: SQLException java.sql.SQLException: No suitable driver

Test Connection to JDBC URL jdbc:db2:DataSource failed.

Solution: In order to successfully install Brio Portal 7.0.x with DB2 7.1, set your LIBPATH environment variable to the location of the DB2 libraries.

1 Choose Start�Setting�Control Panel to open the Control Panel window.

2 Double-click the System option to open the System Properties window.

3 Click the Environment tab, and the click anywhere inside the System Variables list.

4 In the Variable field, type LIBPATH.

5 In the Value field, specify the full path to the location of the DB2 libraries.

6 Click Set to add the variable to the System Variables list.

7 Click Apply, and then click OK.

Note You may also use the Set command from the Windows command prompt.

Troubleshooting Your Brio Portal Installation 103

Connection Refused Errors in Log Files

Problem: Installation fails and the log files shows a Connection Refused error.

Solution: This usually indicates a problem connecting to the metadata database because either the database itself or its listener agent is not active.

Invalid Template Root Property in WebClient

Problem: The following error message appears in the message*.csv log file:

Template Root: /u01/app/brio/brioone/ONEWebClient/null

Solution: This happens when the parent category of the msgs directory is not in the classpath. This category must be in the classpath for WebClient to find any of the resource messages.


Error Loading Runtime Library

Problem: Error loading runtime library: ...bin\javai.dll

Solution: This is a Java bug that occurs in when the jre.exe file does not look in its own directory for the javai.dll (the Java interpreter) when the Windows Registry key JavaHome is not set (or invalid).

If the registry key JavaHome is set, jre.exe is supposed to use it as the JavaHome environment variable. The path it gives for the javai.dll is based on the value of the key.

This situation could happen if you installed jdk1.1.* or the jre1.1* from Javasoft, then deleted or moved their Java directories without running the un-install program to clean up the Windows Registry keys.

To fix this situation, either remove the key from the registry, or set the key to the active jre directory that is installed by Brio, for example \BrioONE\BrioPortal\jre\jre118.

The jre appends \bin\jre to the value in the key.

The complete registry key is:

HKEY_LOCAL_MACHINE\Software\JavaSoft\Java Development Kit\JavaHome

LDAP Authentication Limitations

Problem: What limitations are there with LDAP authentication when running the Brio Intelligence OnDemand Server as a Brio Portal service agent?

Solution: You can configure the Portal to use external authentication (LDAP, in this case). When ODS is present there is a requirement that users and groups be loaded into the Portal authentication repository. This means that the Portal authentication server should be configured to use manual user and group modes. These modes are documented in the Brio Portal Administrator’s Guide.

This introduces the requirement to keep users and groups that are stored in the Portal synchronized with those in the external system (LDAP). The best way to do this is to set up a process that periodically extracts users/groups from the LDAP directory and loads them into the Portal using the load utility (based on ONE/API). No passwords need to be populated in the Portal since all authentication is accomplished externally through LDAP.


Setting Java Debug Properties

Problem: What are Java debug properties and how are they set?

Solution: When starting up Java interpreter, called jre, properties can be set on the command line. These are treated similarly to UNIX environment variables. They are set on the command line like this:

jre -Dpropertyname=value

It is also often a good idea to add -nojit to the jre command line when troubleshooting problems. This helps Brio engineers locate the source of an error that may be occurring.

Brio has defined many properties that may be set to either help debug a problem or try and enhance some performance issue. In general, the properties do not need to be set, and it is suggested that they be set only at the request of Brio Technical Support or a Brio Sales Engineer. Some of the properties, if left set, can cause adverse effects on the system, like using large amounts of disk space writing to logs.

Some of the more common properties that are used:

■ debug=true – This property forces each service agent to verbosely dump the stack traces in the case of an exception/error condition. This is useful in all cases where exception messages appear on the client machine but there is no indication on the servers.

■ echo=true – Each service agent that starts when this property is set to true displays (to standard out) each command the agent receives and executes. Two messages appear when a command successfully completes:

Executing... command

Completed... command

Set this property to true if your server commands start failing.

■ jfdebug=true or jf_debug=true – This property applies only to the job factory service agents and generally only in a scenario involving problems running generic jobs. This property forces the job factory to display the commands sent and received between the job factory and the repository which are internal to the Brio Portal agents. The property also informs the job factory to take a snapshot of what it was attempting to


execute, in a directory named jftest in $JOBFACTORYHOME/tmp/jftest, the executed shell script and any files involved in the job execution will be stored.

■ verbose=true – This property results in the dump of the contents of all server commands received on the service agent. This is useful in most cases especially to insure that the command is fully populated with valid data.

■ print_config=true – This property results in the output of the configuration information received by the service agent at startup. The configuration information includes information regarding each service agent configured on the system. This is particularly useful when servers are unable to connect to the other service agents.

Error 2140: Internal WIN NT Error

Problem: When you try to start one of the Brio Portal agents as a Windows service, you receive the following error message:

Error 2140 internal WIN NT error

Solution: The configuration issues that can cause this error to occur are:

■ A bad database connection

■ No copy of Jview on the server when the service agents are configured to use Jview

■ A malformed path

■ An incorrect TCP/IP configuration

To troubleshoot this error, start the agents with batch files. If the batch file is configured the same as the service, the error occurs visibly in the console window. If the batch agent does start, compare the service agent configuration to the batch file. As most of the service agent configuration is in the registry, you should call Technical Support for assistance.


Java.lang.OutOfMemory Exception

Problem: The Java virtual machine runs out of memory trying to run an application.

Solution: This may be the problem itself, or it may be a symptom of another error that causes the memory to be used up.

To allocate more memory, the java -mx option may be set. By default, Java has a maximum memory allocation of 16 MB, called the heap size. To increase the heap size to 512 MB, which is the maximum setting Java uses, specify:

jre -mx512m

The Java interpreter does not automatically use all of the specified memory; rather, it gets memory as it is needed up to the maximum.

You can also specify the heap size at start up. However, since the Java interpreter gets more if it needs it (up to the maximum heap size), we do not suggest that specify the heap size at start up unless specifically requested by a Brio Sales engineer or technical support. If you specify a heap size larger than the actual amount of physical memory, the Java interpreter uses virtual memory.


Index

A

accounts, Windows user, creating, 8

advanced service agent properties

ONE/CrawlServer, 50

ONE/SearchServer, 50

agents. See service agents.

Apache, configuring, to run ONE/WebClient, 81

authentication limitations, LDAP, 105

B

Brio Portal

installing with DB2 7.1, 103

service agents

custom installation or upgrade, 30

installation verification, 44

typical installation or upgrade, 18

troubleshooting, 103

browser version, ONE/Administrator, installing, 60

browsers

troubleshooting Netscape, 64

Web, supported, 6

C

CD-ROM drive, requirements, 5

changing Windows Registry values, 76

class files, manually loading, 99

classes12.zip, 24

commercial Web servers

configuring ONE/WebClient, 77

servlet engine configuration settings, 79

communications protocol requirements, 5

config.dat, 43

configuration procedures, required, 7

configuration settings (for commercial Web servers), servlet engine, 79

configuration specifications, system requirements and, 5

configuration, servlet, verifying, 80

configuring

Apache

ONE/WebClient with JRun, 81

ONE/WebClient with JServ, 81

commercial Web servers, 78

IBM DB2, 8

IBM HTTP WebServer to run ONE/WebClient with WebSphere, 82

Informix, 10

iPlanet to run ONE/WebClient with JRun, 91

Microsoft IIS to run ONE/WebClient with JRun, 89

Microsoft SQL Server, 11

Netscape Enterprise Server to run ONE/WebClient with JRun, 93

Netscape Enterprise Server to run ONE/WebClient without JRun, 94

ONE/Administrator, 58, 66

ONE/WebClient, 70

ONE/WebClient on a commercial Web server, 77

Oracle, 13

Sybase, 14

connect string, 26

connection refused errors, in log files, 104

connection requirements, TCP/IP, 5

conventions, typographical, 3

creating Windows user accounts, 8

custom installation option, when to use, 21

custom installation or upgrade, Brio Portal service agents, 30

customer support, 4

D

databases, supported, 6

datasource, 26

DB2

configuring, 8

required information, 18, 30

troubleshooting, 8

versions supported, 6

db2java.zip, 18

debug properties, setting Java, 106

default installation directory, 20, 32

default password, BPAdministrator, 55

default values, service agent, 50

desktop version, ONE/Administrator, installing, 58

disk space requirements, 5

Drop.log, 28, 42

E

engine configuration settings (for commercial Web servers), servlet, 79

Error 2140, internal WIN NT error, 107

errors

connection refused, in log files, 104

loading runtime library, 105

Explorer, Internet, troubleshooting, 64

F

files

class, manually loading, 99

log, connection refused errors in, 104

Windows hosts, updating, 7

G

general service agent properties, 50

H

hardware requirements, 5

host name, 25

hosts file, Windows, updating, 7

HTTP server, standalone, running ONE/WebClient as, 75

I

IBM DB2

configuring, 8



IBM HTTP WebServer, configuring to run ONE/WebClient with WebSphere, 82

ifxjdbc.jar, 10

IIS

configuring to run ONE/WebClient with JRun, 89


Informix

configuring, 10



Install.log, 28, 42

installation directory, default

directory, installation, default, 20, 32

installation verification, Brio Portal service agents, 44

installation, available types, 20

installation, Brio Portal, troubleshooting, 103


installing

Brio Portal 7.0.2 with DB2 7.1, 103

Brio Portal service agents

custom, 30

typical, 18

KnowledgeServer, 46

ONE/Administrator

browser version, 60

browser version, without a Web server (IE only), 65

desktop version, 58

ONE/Integrator, 101

ONE/WebClient, 70

SQR Server, 16

Internet Explorer

troubleshooting, 64


invalid template root property, in WebClient, 104

iPlanet



J

Java debug properties, setting, 106

Java.lang.OutOfMemory exception, 108

JDBC driver

and IBM DB2, 9

and Informix, 10

and Oracle, 24

and Sybase, 14

JDK, versions supported, 6

JRun

configuring Apache to run ONE/WebClient with, 81

configuring Microsoft IIS to run ONE/WebClient with, 89

configuring Netscape Enterprise Server to run ONE/WebClient with, 93

configuring Netscape Enterprise Server to run ONE/WebClient without, 94

JServ, configuring Apache to run ONE/WebClient with, 81

K

KnowledgeServer installation or upgrade, 46

L

language property, ONE/SearchServer, setting, 57

LDAP authentication limitations, 105

library, runtime, error loading, 105

limitations, LDAP authentication, 105

loadall program, in SQR Server, 16

loadall program, running, 8

loading

class files, manually, 99

error, runtime library, 105

log files, 28, 42

log files, connection refused errors in, 104

M

manually loading class files, 99

Microsoft IIS



Microsoft Internet Explorer, versions supported, 6

Microsoft SQL Server

configuring, 11



Microsoft Windows systems, removing ONE/WebClient Software from, 100

N

Netscape browser, troubleshooting, 64

Netscape Enterprise Server

Index 111


configuring to run ONE/WebClient without JRun, 94

Netscape Navigator, versions supported, 6

netstat command, Windows, 22

new Registry entries, 76

O

ONE/Administrator

configuring, 66

installing

browser version, 60

desktop version, 58

without a Web server, 65

ONE/CrawlServer

default values and properties, 50

ONE/CrawlServer, number supported, 49

ONE/Integrator, installing, 101

ONE/SearchServer

default values and properties, 50

setting

language property, 57

URL encoding property, 57

ONE/SearchServer, number supported, 49

ONE/ServiceBroker, remote, configuring, 35

ONE/WebClient

configuring Apache to run with JRun, 81

configuring Apache to run with JServ, 81

configuring commercial Web servers on, 77

configuring IBM HTTP WebServer to run with WebSphere, 82

configuring iPlanet to run with JRun, 91

configuring Microsoft IIS to run with JRun, 89

configuring Netscape Enterprise Server to run with JRun, 93

configuring Netscape Enterprise Server to run without JRun, 94

installing, 71

invalid template root property in, 104

removing Microsoft Windows systems, 100

running as a standalone HTTP server, 75

running as a Windows service, 70

Oracle

configuring, 13


tnsnames.ora file, 18


P

passwords

default, 55

passwords, in log files, 43

passwords, stored in log files, 29

port number, 25

procedures, required configuration, 7

processor requirements, 5

properties, service agent, 50

properties, setting Java debug, 106

R

RAM requirements, 5

refused errors in log files, connection, 104

Registry entries, new, 76

Registry values, changing, 76

relational databases, supported, 6

removing ONE/WebClient software from Microsoft Windows systems, 100

ReportMart 1.x, upgrading from, 32

required configuration procedures, 7

requirements

hardware, 5

software, 6

system, and configuration specifications, 5

RM/Administrator, removing, 58

running ONE/WebClient as a standalone HTTP server, 75

runtime library, error loading, 105


S

servers, Web

supported for ONE/Administrator, 6

supported for ONE/WebClient, 7

service agents

custom installation or upgrade, 30

installation verification, 44

properties and default values, 50

typical installation or upgrade, 18

service packs, Windows

required for Brio Portal, 6

required for KnowledgeServer, 6

servlet configuration, verifying, 80


setting Java debug properties, 106

settings, servlet engine configuration, 79

software requirements, 6

specifications, system requirements and configuration, 5

SQL Server, configuring, 11

SQR Server

installing, 16


standalone HTTP server, running ONE/WebClient as, 75

startup files, location, 22

support, technical, 4

Sybase

configuring, 14



system permissions, for Brio Portal, 8

system requirements and configuration specifications, 5

T

TCP/IP connection requirements, 5

technical support, 4

template root property in WebClient, invalid, 104

tnsnames.ora file, Oracle, 18

troubleshooting

Brio Portal Installation, 103

Internet Explorer, 64

Netscape browser, 64

typical installation or upgrade, Brio Portal service agents, 18

typographical conventions, 3

U

upgrade installation option, when to use, 21

upgrade options, availability of, 20

upgrading

Brio Portal service agents

custom, 30

typical, 18

KnowledgeServer, 46

upgrading, from ReportMart 1.x, 32

URL encoding property, ONE/SearchServer, setting, 57

user accounts, Windows, creating, 8

V

values, Windows Registry, changing, 76

verifying

Brio Portal service agents installation, 44

servlet configuration, 80

W

Web clients, supported, 6

Web servers

commercial

configuring, 78

configuring ONE/WebClient on, 77


installing ONE/Administrator without, 65

supported for ONE/Administrator, 6

supported for ONE/WebClient, 7

Index 113

WebSphere, configuring IBM HTTP WebServer to run ONE/WebClient with, 82

Windows hosts file, updating, 7

Windows netstat command, 22

Windows Registry values, changing, 76

Windows service, running ONE/WebClient as, 70

Windows user accounts, creating, 8


brio.portal 7.0.3 installation guide -...

Documents