Upgrading to Actuate e.

Reporting Suite 4
Release 4.1

Information in this document is subject to change without notice. Examples provided are fictitious. No part of this document may be reproduced or transmitted in any form, or by any means, electronic or mechanical, for any purpose, in whole or in part, without the express written permission of Actuate Corporation. 1995 - 2000 by Actuate Corporation. All rights reserved. Printed in the United States of America. Contains information proprietary to: Actuate Corporation 701 Gateway Boulevard South San Francisco, CA 94080 http://www.actuate.com The software described in this manual is provided by Actuate Corporation under an Actuate License agreement. The software may be used only in accordance with the terms of the agreement. Actuate Corporation trademarks and registered trademarks: Actuate, e.Report, e.Reporting, Live Report Document, Live Report Extension, ReportBlast, ReportCast, Report Encyclopedia, SmartSearch, Transporter, Virtual Report Distribution, and XML Reports. Third party trademarks:
ActiveX, Microsoft, MSN, The Microsoft Network, Windows, Windows NT, Windows 95/98 and/or other Microsoft products are either trademarks or registered trademarks of Microsoft. CT-Library is a trademark of Sybase, Inc. Digital Creations and DCLC, are trademarks of Digital Creations, LC. Graphics Server is a trademark of Bits Per Second, Ltd. and Pinnacle Publishing, Inc. HDK is a registered trademark of Virtual Media Technology Pty Ltd. INFORMIX-ESQL/C is a trademark of Informix Software, Inc. InstallShield is a registered trademark of InstallShield Corporation. LEADTOOLS is a registered trademark of LEAD Technologies, Inc. Netscape, Netscape Communications, Netscape Communicator, Netscape Enterprise Server, Netscape FastTrack Server, and Netscape Navigator are either trademarks or registered trademarks of Netscape Communications Corporation. NobleNet and WinRPC are trademarks of NobleNet, Inc. ONC, Solaris, SPARC, Sun, and Sun Microsystems are trademarks of Sun Microsystems. Oracle Call Interface is a trademark of Oracle Corporation. Progress is a registered trademark of Progress Software Corporation. Sheridan Calendar Widgets is a trademark of Sheridan Software Systems, Inc. SmartHeap is a trademark of MicroQuill Software Publishing, Inc. Tools.h++ is a trademark of Rogue Wave Software, Inc. UNIX is a registered trademark of X/Open Company, Ltd. XPrinter is a trademark of Bristol Technology, Inc. XPAT, created by James Clark, is licenced under the Mozilla licence agreement. WinWidgets is a trademark of Simple Software, Inc.

All other brand or product names are trademarks or registered trademarks of their respective companies or organizations. Document No. 000501-2-430349 April 17, 2000

10

Contents
Chapter 1

Upgrading to Actuate e.Reporting Suite 4 . . . . . . . . . . . . . . . . . . . 1

Release information . . . . . . . . . . . . . . . . . . . . . . Late-breaking information . . . . . . . . . . . . . . . . . Supported products changes . . . . . . . . . . . . . . . Upgrade strategy. . . . . . . . . . . . . . . . . . . . . . . . Setting up a test environment . . . . . . . . . . . . . . . Setting up a production staging area . . . . . . . . . . . Setting up a production environment . . . . . . . . . . Installing Actuate Suite 4 with earlier Actuate releases . . Actuate 4 report file compatibility and migration . . . . . Report file compatibility . . . . . . . . . . . . . . . . . . Upgrading reports . . . . . . . . . . . . . . . . . . . . . AFC changes in Actuate 4 . . . . . . . . . . . . . . . . . AFC class hidden properties. . . . . . . . . . . . . . . . Report Encyclopedia compatibility and migration . . . . . Report Encyclopedia compatibility . . . . . . . . . . . . Upgrading the Report Encyclopedia . . . . . . . . . . . Upgrading by copying Release 3.x files to Actuate 4 Upgrading in place . . . . . . . . . . . . . . . . . . . Application compatibility and migration . . . . . . . . . . Application compatibility . . . . . . . . . . . . . . . . . Upgrading applications . . . . . . . . . . . . . . . . . . ReportCast compatibility and migration . . . . . . . . . . ReportCast compatibility . . . . . . . . . . . . . . . . . Upgrading ReportCast . . . . . . . . . . . . . . . . . . . Viewing and searching DHTML reports . . . . . . . Home folder URL . . . . . . . . . . . . . . . . . . . . User Preferences page . . . . . . . . . . . . . . . . . . Adding a View Report button . . . . . . . . . . . . . Supporting e.Reporting Server levels . . . . . . . . . Adding a logout link . . . . . . . . . . . . . . . . . . Setting a custom folder path separator character . . Supporting automatic archiving . . . . . . . . . . . . Supporting secure read privilege . . . . . . . . . . . Supporting open server . . . . . . . . . . . . . . . . . Changes to template variable availability. . . . . . . General compatibility and migration . . . . . . . . . . . . Considerations for Windows systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 . 2 . 2 . 2 . 3 . 4 . 4 . 5 . 6 . 6 . 7 . 8 . 9 .10 . 11 . 11 . 11 . 11 .12 .12 .12 .13 .13 .14 .15 .15 .16 .16 .16 .16 .17 .17 .20 .21 .24 .24 .25

Upgrading from Actuate 4 to Actuate 4.1 . . . . . . . . . Informix database connection changes . . . . . . . . . Concurrent Support of Native and ODBC Informix Considerations for release 4.1 for Windows systems .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

25 25 25 25

Appendix A

Installing Actuate desktop products . . . . . . . . . . . . . . . . . . . . . . . 27

Installing the End User Desktop, LRX, and Viewer on Windows 95, 98, and NT . . . . . . . . 28 Installing the Actuate LRX from the Actuate ReportCast download page . . . . . . . . . . . . 28 Distributing the Actuate Report Viewer over a network. . . . . . . . . . . . . . . . . . . . . . 29

Appendix B

Installing ODBC drivers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

About ODBC drivers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Finding the ODBC driver version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Updating ODBC drivers used with data sources . . . . . . . . . . . . . . . . . . . . . . . . . . 34

ii

Chapter

1
Chapter 1

Upgrading to Actuate e.Reporting Suite 4

This chapter describes how to upgrade to Actuate e.Reporting Suite 4 from previous Actuate releases.

Chapter 1, Upgrading to Actuate e.Repor ting Suite 4

Release information
This section contains general information about the Actuate 4 release.

Late-breaking information
To view late-breaking information, available prior to shipping, about Actuate e.Reporting Suite 4, see the Readme file. If updates are necessary after shipping, the latest information is available in updated release notes and other documents posted on Actuate web sites Customer Support pages. See the following URL:
http://www.actuate.com/customer_zone/release_notes.htm

Supported products changes

There have been changes to the list of products that Actuate supports. Be sure to check the Supported products matrix for detailed information about supported databases, development environments, e-mail, operating systems, web browsers, and web servers. The Supported products matrix is on the Actuate web site at the following URL:
http://www.actuate.com/customer_zone/spm/spm.htm

Earlier versions refers to Releases 2.x and 3.x. Actuate desktop products refers to Administrator Desktop, Developer Workbench, End User Desktop, LRXs, APIs, Viewer, and ActiveX controls. Changes to supported products include:
s s s s

Web server support Web browser support Operating system support Compiler support

Upgrade strategy
Release 3 and Actuate 4 can coexist on the same machine. You can leave your Release 3 installation up and running while simultaneously testing the Actuate 4 products. How and when you upgrade to Actuate 4 depends on your site configuration and requirements. Follow your site policies when developing an upgrade

Upgrading to Actuate e.Repor ting Suite 4

strategy. The following is a general guideline to use when determining how to upgrade your site to Actuate 4.
s

Create a test environment for Actuate 4. Install the software and upgrade Release 3 SDK programs, report designs, and report executables. Verify that the application works properly in the test environment. Create a production staging area for Actuate 4. Install the software and upgraded Release 3.x SDK, report designs, and report executables. If required, install a limited number of Actuate 4 desktop products for testing in a production environment in conjunction with existing Release 3 desktop products. Verify that the production staging environment functions properly using Actuate 4. Install the remaining Actuate 4 desktop products, if required, in production environments on users workstations. Verify that the desktop products function properly. At this point, you have verified that the Actuate 4 production staging environment functions properly. On a suitable day, schedule time to make the switch from Release 3 to Actuate 4.

Setting up a test environment

Set up a test environment to test migrating Release 3.x files to Actuate 4, and to confirm that your applications perform as expected with Actuate 4. Applications developers and a limited number of users use the test environment during the testing process. 1 Create the Actuate 4 test environment. The test environment can be on the same machine that hosts the Release 3.x installation, or on a separate machine. For information about compatibility between Release 3.x and Actuate 4 products, see Installing Actuate Suite 4 with earlier Actuate releases, later in this document. If you have 3.x Web Agent with Microsoft Internet Information Server on your local machine, install a web server on a separate NT machine and install Actuate 4 ReportCast on that machine to test Actuate 4 ReportCast on NT with IIS. 2 Upgrade your Release 3.x report designs, report executables, SDK programs, etc. Details about upgrading your Release 3.x files to Actuate 4 are later in this document. 3 Verify that your reports and applications work correctly in the test environment.

Chapter 1, Upgrading to Actuate e.Repor ting Suite 4

Setting up a production staging area

Set up a production staging area to use for final testing. A production staging area is one that can be used for testing, and can also be easily configured as the live production system. The production staging area can be a separate configuration on the live production machine, or a separate machine. You can install all the Actuate 4 products, or install the Actuate 4 server products and a subset of the desktop products. If you plan to test Actuate 4 desktop products, identify the users to participate in the final testing. Developers and users use the production staging area to confirm that applications perform as expected in the Actuate 4 environment. 1 Install the Actuate 4 server software in a production staging area. 2 Install the Actuate 4 desktop software on the test users machines. Install the Actuate 4 desktop software in conjunction with the Release 3.x desktop software. The users can continue to use the Release 3.x software in production while testing the Actuate 4 desktop software. 3 Verify that the Actuate 4 production staging environment works correctly. 4 Install the remaining Actuate 4 desktop products if you installed a subset earlier. Verify that the Actuate 4 desktop products work correctly. You have now verified that the Actuate 4 production staging environment works correctly.

Setting up a production environment

Now that testing is complete and you have confirmed that your applications work as expected in the Actuate 4 environment, set up the production environment. Schedule a date and time to switch from Release 3 to Actuate 4. When you switch to Actuate 4: 1 Shut down the Release 3 and Actuate 4 servers 2 Back up the Release 3 Report Encyclopedia 3 Restore the Release 3 Report Encyclopedia into the Release 4 production area 4 Install upgraded designs and report executables. 5 Start the Release 4 server 6 Inform users that they can start using Actuate 4 desktop products.

Upgrading to Actuate e.Repor ting Suite 4

Installing Actuate Suite 4 with earlier Actuate releases

This section describes issues around installing Actuate Suite 4 products with existing Release 3.x installations. In general, Actuate 4 products can coexist with earlier releases of Actuate products. The following list describes product coexistence issues for Actuate 4 and Release 3.x installations.
s

One copy of Actuate Release 3.x and one copy of Actuate 4 can reside on the same machine. They must be installed in separate directory structures. Release 3.x and Actuate 4 report servers can run at the same time on the same machine. If an Actuate Release 3.x and Actuate 4 report server coexist on the same machine, Release 3.x desktop products automatically connect with Release 3.x servers, and Actuate 4 desktop products automatically connect with Actuate 4 servers. Release 3.x desktop products cannot connect to Actuate 4 report servers or ReportCast. Actuate 4 desktop products cannot connect to Release 3.x report servers or Web Agent. If an Actuate Release 3.x and Actuate 4 report server coexist on the same machine, you must start the Release 3.x report server before you start the Actuate 4 report server. You can install Release 3.x and Actuate 4 LRXs on the same machine. Release 3.x and Actuate 4 LRXs automatically connect with the appropriate Actuate releases. Release 3.x Web Agent and Actuate 4 ReportCast can coexist on the same Unix machine. They must be installed with different instances of the web server. Release 3.x Web Agent and Actuate 4 ReportCast cannot coexist on NT running the Microsoft Internet Information Server web server. On NT with the IIS web server, you must install either the Release 3.x Web Agent, or Actuate 4 ReportCast, but not both. Release 3.x Web Agent and Actuate 4 ReportCast can coexist on NT running Netscape web servers. They must be installed with separate instances of the web server, in separate web document root folders. If you create another instance of the Netscape web server on NT, create a different document root directory for the new instance. Netscapes default behavior on Windows is to use the same document root directory that the existing web server instance uses.

Chapter 1, Upgrading to Actuate e.Repor ting Suite 4

For optimal performance, all Actuate e.Reporting Suite 4 products must be at the same release level.

Actuate 4 report file compatibility and migration

This section describes:
s

Compatibility issues between Actuate e.Reporting Suite 4 report file formats and the report file formats for earlier Actuate releases. Upgrading Release 3.x reports to Actuate 4. Changes to the Actuate Foundation Classes that affect existing report designs.

s s

Report file compatibility

s

Report design files (.RODs and .ROLs), report executable files (.ROXs), and report parameter files (.ROVs) have a new format in Actuate 4. Actuate 4 products read Release 3.x report files and automatically save them in Actuate 4 format. Report document files (.ROIs) have a new format in Actuate 4. Actuate 4 products generate report documents in Actuate 4 format. Release 3.x report documents (.ROIs) are viewable using Actuate 4 Viewer LRX, Administrator Desktop, Developer Workbench, and End User Desktop. You cannot view Release 3.x report documents as DHTML reports, or as XML or PDF format documents. Release 3.x report executables (.ROXs) can be run using Actuate 4 and the resulting report documents (.ROIs) can be viewed using the Actuate 4 LRX or Viewer in the native Actuate format. Report documents cannot be viewed in DHTML format or as XML or PDF format documents. These formats are supported only for report documents generated from Actuate 4 report executables. Release 3.x products cannot read Actuate 4 report files. You cannot use Actuate 4 report documents, report designs, or report executables with Release 3.x. Releases 3.2.3 and later display a warning message if you attempt to open a report design file that was created or edited with a newer release of the Actuate Reporting System. Opening a Release 3.2.3 or later report design file using a release earlier than 3.2.3 is not supported and has unpredictable results.

Upgrading to Actuate e.Repor ting Suite 4

The Actuate 4 default connection for Oracle is Oracle8. The Release 3.x default connection for Oracle is Oracle 7. To use Actuate 4 desktop products with Oracle databases, you must either install the Oracle 8 client, or configure Actuate to use the Oracle 7 client.

Upgrading reports
To take advantage of the new features, performance enhancements, and fixes in Actuate 4, you must upgrade your reports. You can upgrade reports individually or in batches. To upgrade an individual report:
s s

Start Actuate 4 Developer Workbench. Open the Release 3.x or earlier report design in Actuate 4 Developer Workbench. Rebuild, run, and view the report design. Viewing the report document verifies that it works correctly in Actuate 4. Save the report design. Add the new report executable to the Actuate 4 Report Encyclopedia.

s s

The report is now upgraded to Actuate 4. To upgrade reports in batches, use the Developer Workbench executable, DESIGNER.EXE, to convert multiple report designs and executables. When you use DESIGNER.EXE from a command line, a Developer Workbench window is visible during the conversion process. Following is the syntax for using DESIGNER.EXE from a command prompt:
designer [ [-b] [file1 file2 ... filen] ] [-f filename.log]

b (optional) Specifies that the Developer Workbench rebuild the report design file and exit. If the -b option is not used, the Developer Workbench starts and opens the specified report design. file1, file2, filen (optional) Specifies Actuate report design files. The option assumes an .ROD file extension .ROD. You can specify multiple report design files to be rebuilt. When you specify multiple files, you must use the b option.The designer assumes the files are in the current directory unless you add the path to the file name. Enclose file names that include spaces within quotes.

Chapter 1, Upgrading to Actuate e.Repor ting Suite 4

f filename.log (optional) Specifies a log file that contains processing information for the reports being rebuilt. If you do not specify a log file, any error messages are sent to the command line window.

Examples
The following command starts the Developer Workbench DESIGNER.EXE and opens the forecast report design for editing. In this example, FORECAST.ROD is in the current directory:
c:\Actuate4\dwb\bin> Designer forecast.rod

This command rebuilds FORECAST.ROD and creates the files FORECAST.BAS and FORECAST.ROX. If there were errors in either the codegeneration phase or compilation phase, they are displayed in the command prompt window. The following example uses the -b option:
c:\Actuate4\dwb\bin > designer b detail

In this example, the Developer Workbench DESIGNER.EXE rebuilds three design files, DETAIL.ROD, FORECAST.ROD and BYFR.ROD. The first two report designs are in subdirectories. The third is in the current directory. The following examples uses the -f option:
c:\Actuate4\dwb\bin> designer b detail\detail.rod forecast\forecast byfr f build.log

The f option specifies that a log file named BUILD.LOG be created. The log file contains processing information and any errors encountered when rebuilding the report designs.

AFC changes in Actuate 4

This section lists specific changes to the Actuate Foundation Classes in Actuate 4 that may affect existing report designs.Changes include certain properties removed and certain properties changed to hidden properties.
s

Actuate 4 requires that you completely qualify subclasses. Previous releases allowed calling a subclass without qualifying it if the subclass name was unique. Certain properties have been removed. If your reports set values for properties that have been removed, generating code will result in warnings in the output window. The warnings are similar to:
There is no property member for this property value.

Upgrading to Actuate e.Repor ting Suite 4

To resolve the warnings: 1 Choose ReportValidate DesignFull Check. 2 Choose Build/Run/View to recompile and run the report. 3 When the first warning appears, choose Yes All. The removed properties are:
s

AcLine no longer includes the size property. The size property has no meaning for line controls. AcFlow and AcBaseFrame no longer include the BackgroundIsClear variable and property.

s s

Actuate now hides properties that do not apply to a component. The DefineInputParameter, DefineOutputParameter, and DefineReturnParameter methods previously returned True on success, or False on failure. Now Actuate raises a database error if it cannot define the parameter.

AFC class hidden properties

The following table lists the hidden properties for specific Actuate Foundation Classes. Class AcReport Hidden property TocAddContents TocAddComponent TocValueExp AcBasePage XMLAddContents XMLAttributes XMLTag XMLType TocAddContents TocAddComponent TocValueExp SearchAlias Searchable AcPage AcFlow Position ObjectVariable XMLAddContents

Chapter 1, Upgrading to Actuate e.Repor ting Suite 4

Class

Hidden property XMLAttributes XMLTag XMLType TocAddContents TocAddComponent TocValueExp SearchAlias Searchable

AcPageList

XMLAddContents XMLAttributes XMLTag XMLType TocAddContents TocAddComponent TocValueExp

AcLineControl

Size Searchable SearchAlias SearchAttributeName

AcRectangleControl

Searchable SearchAlias SearchAttributeName

AcEllipseControl

Searchable SearchAlias SearchAttributeName

Report Encyclopedia compatibility and migration

This section describes compatibility issues between Actuate 4 and Release 3.x Report Encyclopedias. This section also describes the upgrade procedure for Release 3.x Report Encyclopedias.

10

Upgrading to Actuate e.Repor ting Suite 4

Report Encyclopedia compatibility

s

Actuate 4 report servers read Release 3 Report Encyclopedias and automatically upgrade them to Actuate 4. Release 3.x report servers cannot read Actuate 4 Report Encyclopedias. Actuate 4 supports assigning privileges on the root folder. To ensure compatibility for existing applications, upgrading a Release 3.x Report Encyclopedia to Actuate 4 grants Write privilege to the All role on the root folder of the Report Encyclopedia.

s s

Upgrading the Report Encyclopedia

Upgrade the Report Encyclopedia by either upgrading in place, or copying Release 3.x files into the Actuate 4 Report Encyclopedia.

Upgrading by copying Release 3.x files to Actuate 4

To upgrade the Report Encyclopedia to Actuate 4 using the copy in place method:
s s s s

Do a full backup of the 3.x Report Encyclopedia Stop the 3.x and Actuate 4 report servers Delete the Actuate 4 admin, object, and request folders Copy the 3.x Report Encyclopedias admin, object, and request folders to the Actuate 4 Report Encyclopedia Restart the Actuate 4 report server As Report Encyclopedia administrator, grant the All role write privilege to the root folder of the Report Encyclopedia. Set the default web viewer for the Report Encyclopedia to LRX in the Report Encyclopedia Server Properties dialog box. The default web viewer for the Actuate 4 Report Encyclopedia is Dynamic HTML.

s s

Upgrading in place
Upgrade a Release 3.x Report Encyclopedia to Actuate 4 in place means installing Actuate 4 over the Release 3.x Report Encyclopedia.
s s

Do a full backup of the 3.x Report Encyclopedia. Install the Actuate 4 report server according to the instructions in the e.Reporting Server installation guide.

Chapter 1, Upgrading to Actuate e.Repor ting Suite 4

11

The Actuate 4 installation retains the 3.x Report Encyclopedia. Actuate 4 e.Reporting Server automatically upgrades the Report Encyclopedia at e.Reporting Server start-up.

Application compatibility and migration

This section describes compatibility issues between Actuate 4 and Release 3.x applications. This section also describes the upgrade procedure for Release 3.x applications.

Application compatibility
s

Programs built with Release 3.x Request and report server APIs, or that use the Viewer or Desktop ActiveX controls, will not work with Actuate 4 servers. You must rebuild your programs using the Actuate 4 APIs Software Development Kit (SDK), and/or with the Actuate 4 ActiveX controls. The name of the RSAPI DLL is ACRQ4060.DLL. The names of the Viewer and Desktop ActiveX controls have been changed. This allows Release 3.x and Actuate 4 programs to co-exist on the same machine. Release 3.x Viewer and ActiveX controls cannot work with Actuate 4 file formats. Rebuild programs that use these controls with Actuate 4 to use them with other Actuate 4 products. The Actuate 4 factory server changes the object ID of .ROIs it replaces. The previous .ROI object ID and any AcPersistentObject objects created using the previous .ROI name and version are no longer valid once the Actuate 4 factory server replaces them. Earlier Actuate releases did not change the .ROI object ID. This may affect report server API applications that depend on the object ID.

s s

Upgrading applications
To upgrade Release 3.x applications, rebuild them using the Actuate 4 APIs Software Development Kit (SDK). To upgrade applications that use Release 3.x Viewer and ActiveX controls, rebuild them using Actuate 4.

12

Upgrading to Actuate e.Repor ting Suite 4

ReportCast compatibility and migration

This section describes compatibility issues between Actuate 4 ReportCast and Release 3.x Web Agent. This section also describes the upgrade considerations for Release 3.x Web Agent.

ReportCast compatibility
Actuate 4 ReportCast and 3.x Web Agent both refer to Actuates reporting web site functionality.
s

Release 3.x Web Agent and Actuate 4 ReportCast cannot interoperate. Actuate 4 ReportCast cannot connect with a Release 3.x report server. Actuate 4 desktop products cannot interoperate with Release 3.x servers and Web Agent. Release 3.x desktop products cannot interoperate with Actuate 4 servers and ReportCast. The default Actuate 4 ReportCast configuration has been changed from the directory named enu to a new directory named default. Actuate 4 template images reside with each configuration. For example, instead of one images directory, each ReportCast configuration contains an images directory. This provides support for localizing template images, such as buttons and banners. Actuate 4 ReportCast can read Release 3.x Web Agent templates. No changes are necessary to Release 3.x Web Agent templates to have them work with Actuate 4. However, Release 3.x templates generated web pages do not provide support for the Actuate 4 login/logout or user preferences features, or for the following Actuate 4 features: Product Area Open server Actuate 4 feature Scheduling and Adhoc request Viewing Icons Auto-archive View process Setting properties Submitting requests DHTML report viewing

Actuate 4 does not support the 16-bit LRX.

Chapter 1, Upgrading to Actuate e.Repor ting Suite 4

13

Upgrading ReportCast
Release 3.x templates can be used as-is with Actuate 4. However, some changes are necessary to use the new features available in Actuate 4. As part of providing support for Actuate 4 features, copy the following files from your Actuate 4 ReportCast installations default/standard configuration directory to your Release 3.x default configurations standard directory: File acstyle.css array.js browsererror.html browsertest.achtml cookie.js converter.js external.js headerscript.achtml layer.js pageheaderx.achtml report.js resize.js saveas.achtml search.js searchrequest.achtml searchresults.achtml searchtoolbar.html toctree.js userpreferences.achtml viewframeset.achtml Used by the dynamically generated DHTML pages produced by the DHTML converter Submits the DHTML search request Provides support for navigating through DHTML search results Displays the DHTML Search toolbar Draws the DHTML reports Table of Contents Provides the User Preferences page Sets up the report viewing framework Used by the dynamically generated DHTML pages produced by the DHTML converter Provides default Actuate 4 headers and tabs Used by the dynamically generated DHTML pages produced by the DHTML converter Description Cascading style sheet for the Actuate 4 templates Javascript for processing DHTML search results Displays error message if users browser does not support Actuate 4 ReportCast features Tests whether or not users browser supports Actuate 4 ReportCast features Provides web cookie handling for the DHTML report viewing and searching features Used by the dynamically generated DHTML pages produced by the DHTML converter Used by the dynamically generated DHTML pages produced by the DHTML converter

14

Upgrading to Actuate e.Repor ting Suite 4

File viewnav.achtml viewnav.js viewtoc.achtml

Description Sets up the report viewing navigation toolbar Javascript to generate and display the navigation toolbar Displays the report viewing Table of Contents

Viewing and searching DHTML reports

To add support for viewing and searching DHTML reports to your Release 3.x templates, change template directive references from ?View to ?ViewDefault. For example, edit your Release 3.x FOLDERLIST.ACHTML template and replace lines such as:
<!-- #Actuate elseif AbbreviatedType = ROI then --> <td><img src=$(imgRoi) width=16 height=16></td> <td><a href=$(URL)?View> $(ItemBaseName)</a></td>

with
<!-- #Actuate elseif AbbreviatedType = ROI then --> <td><img src=$(imgRoi) width=16 height=16></td> <td><a href=$(URL)?ViewDefault> $(ItemBaseName)</a></td>

When the user clicks the ROI link on the reporting web page, ReportCast displays the report document using the users default viewing choice. If the report document is a DHTML report, the ViewDefault command ensures that ReportCast displays the DHTML report with the navigation bar and search field. Customize the DHTML navigation and search toolbar by modifying the following files:
s

SEARCH.JS, the Javascript file that provides navigation and search functionality SEARCHTOOLBAR.HTML, the HTML file that provides the structure for the navigation and search toolbar

Home folder URL

Actuate 4 ReportCast features a new home folder URL: $(RootFolderURL)_ _home. To add support for the new home folder URL to your Release 3.x templates, change template references from $(HomeFolderURL) to $(RootFolderURL)_ _home. For example, edit the FOLDERLIST.ACHTML template and replace lines such as:

Chapter 1, Upgrading to Actuate e.Repor ting Suite 4

15

<a href=$(HomeFolderURL)><img src=$(imgFolder) border=0></a></ td>

with
<a href=$(RootFolderURL)_ _home><img src=$(imgFolder) border=0></a></td>

User Preferences page

A new User Preferences page is available. To access it, add code similar to the following to your Release 3.x FOLDERLIST.ACHTML:
<a href=$(RootFolderURL)_ _requestUserPreferences>User Preferences</a>

Customize the User Preferences page by modifying the USERPREFERENCES.ACHTML template.

Adding a View Report button

Add a View Report button by including code similar to the following in REQUEST.ACHTML or REQUESTDETAILS.ACHTML:
<!-- #Actuate if RequestStatus = Completed then --> <! -- Actuate View Report button --> <tr> <td><a href=$(ViewURL)><img src=$(imgViewReport) border=0></ a></td> </tr> <!-- #Actuate end if -->

Supporting e.Reporting Server levels

Add support for the Advanced e.Reporting Server by adding the following to the header.achtml template file:
<!-- #Actuate Set serverFeatureLevelNone = "0" --> <!-- #Actuate Set serverFeatureLevelStandard = "1" --> <!-- #Actuate Set serverFeatureLevelAdvanced = "2" -->

Adding a logout link

If you do not use Basic Authentication, you can add a Logout link to your reporting web site pages. Include code similar to the following in FOLDERLIST.ACHTML:
<!-- #Actuate if LoginForm = TRUE and ReportCastAdmin <> TRUE then -> <a href=$(RootFolderURL)_ _logout>Log Out</a>

16

Upgrading to Actuate e.Repor ting Suite 4

Setting a custom folder path separator character

You can set a custom folder path separator character. ReportCast uses the separator character when constructing folder path names. To set a custom folder path separator, include code similar to the following in FOLDERLIST.ACHTML:
<!-- #Actuate Set customLinkedFolderPathSeparator = character -->

where character is the character to use as a separator. For example, to use > as the separator character:
<!-- #Actuate Set customLinkedFolderPathSeparator = > -->

Supporting automatic archiving

The Actuate 4 e.Reporting Server supports automatic archiving. To add support for automatic archiving to your Release 3.x templates, include code similar to the following in REQUEST.ACHTMLs Version section:
<td> <input type=checkbox name="__limit" value="limit"><font size="2" face="Arial">Keep only the latest</font>&nbsp; <input type="text" size="4" name="__limitNumber">&nbsp; <font size="2" face="Arial">version(s)</font> </td>

Add a new Archive Policy section to REQUEST.ACHTML after the Notify Channel section. After the line:
<!-- #Actuate end if --> <!-- Actuate if Has Channels -->

add code similar to the following:

<table border="0" cellpadding="0" cellspacing="0"> <tr> <td>&nbsp;</td> <td> <table width = "600" border="0" cellpadding="0" cellspacing="0" bgcolor="#E1E1E1" width="540"> <tr> <td>&nbsp;</td> <td><font size="2" face="Arial"><strong>Archive Policy</strong></font></td> <td>&nbsp;</td> <td>&nbsp;</td> </tr> <tr> <td>&nbsp;</td> <td>&nbsp;</td> <td>&nbsp;</td> <td>&nbsp;</td> </tr> <tr>

Chapter 1, Upgrading to Actuate e.Repor ting Suite 4

17

<td>&nbsp;</td> <td><input type="radio" checked name="__archivePolicy" value="folder"><font size="2" face="Arial">Use the archive policy for the distribution folder(s)</font></td> <td>&nbsp;</td> <td>&nbsp;</td> </tr> <tr> <td>&nbsp;</td> <td> <input type="radio" name="__archivePolicy" value="age"><font size="2" face="Arial">Delete objects older than</font> <input type="text" size="4" name="__ageDays"> <font size="2" face="Arial">&nbsp;days&nbsp;</font> <input type="text" size="4" name="__ageHours"> <font size="2" face="Arial">&nbsp;hours</font> </td> <td>&nbsp;</td> <td>&nbsp;</td> </tr> <tr> <td>&nbsp;</td> <td> <table cellpadding=0 cellspacing=0 border=0> <td nowrap><input type="radio" name="__archivePolicy" value="date"><font size="2" face="Arial">Delete objects on</font> <input type="text" size="12" maxlength="10" name="__dateToDelete" value="$(DefaultDate)"><font size="2" face="Arial">&nbsp;(mm/dd/yyyy) at</ font> <input type="text" size="9" maxlength="8" name="__timeToDelete" value="$(DefaultTime)"><font size="2" face="Arial">&nbsp;(hh:mm:ss)</font> </td> </table> </td> <td>&nbsp;</td> <td>&nbsp;</td> </tr> <tr> <td>&nbsp;</td> <td>&nbsp;</td> <td>&nbsp;</td> <td>&nbsp;</td> </tr> </table> </td> </tr> </table> <table border="0" cellpadding="0" cellspacing="0"> <tr><td height="10"></td></tr> </table> <table border="0" cellpadding="0" cellspacing="0">

18

Upgrading to Actuate e.Repor ting Suite 4

<tr> <td>&nbsp;</td> <td> <table width = "600" border="0" cellpadding="0" cellspacing="0" bgcolor="#E1E1E1" width="540"> <tr> <td>&nbsp;</td> <td><font size="2" face="Arial"><strong>Archive Options</strong></font></ td> <td>&nbsp;</td> <td>&nbsp;</td> </tr> <tr> <td>&nbsp;</td> <td>&nbsp;</td> <td>&nbsp;</td> <td>&nbsp;</td> </tr> <tr> <td>&nbsp;</td> <td><font size="2" face="Arial">(Only takes effect if overriding archive policy for distribution folder)</font></td> <td>&nbsp;</td> <td>&nbsp;</td> </tr> <tr> <td>&nbsp;</td> <td>&nbsp;</td> <td>&nbsp;</td> <td>&nbsp;</td> </tr> <tr> <td>&nbsp;</td> <td><input checked type="radio" name="__archiveBeforeDelete" value="TRUE"><font size="2" face="Arial">Archive objects before deletion</ font></td> <td><font size="2" face="Arial"></font>&nbsp;</td> <td>&nbsp;</td> </tr> <tr> <td>&nbsp;</td> <td><input type="radio" name="__archiveBeforeDelete" value="FALSE"><font size="2" face="Arial">Permanently delete objects without archiving</font></ td> <td><font size="2" face="Arial"></font>&nbsp;</td> <td>&nbsp;</td> </tr> <td>&nbsp;</td> <td>&nbsp;</td> <td>&nbsp;</td> <td>&nbsp;</td>

Chapter 1, Upgrading to Actuate e.Repor ting Suite 4

19

</tr> </table> </td> </tr> </table> <table border="0" cellpadding="0" cellspacing="0"> <tr><td height="10"></td></tr> </table>

Supporting secure read privilege

The advanced e.Reporting Server supports a new secure read privilege feature. To add support for the secure read privilege feature, include code similar to the following in FILEDETAIL.ACHTML:
<table border="0" cellpadding="0" cellspacing="0"> <tr> <td>&nbsp;</td> <td> <table width = "600" border="0" cellpadding="0" cellspacing="0" bgcolor="#E1E1E1" width="540"> <tr> <td>&nbsp;</td> <td><font size="2" face="Arial"><strong>Privilege for Request Results</ strong></font></td> <td>&nbsp;</td> <td>&nbsp;</td> </tr> <tr> <td>&nbsp;</td> <td>&nbsp;</td> <td>&nbsp;</td> <td>&nbsp;</td> </tr> <tr> <td>&nbsp;</td> <td><input checked type="radio" name="__accessToGrant" value="Read"><font size="2" face="Arial">Automatically grant Read access to channel subscribers</font></td> <td><font size="2" face="Arial"></font>&nbsp;</td> <td>&nbsp;</td> </tr> <tr> <td>&nbsp;</td> <td><input type="radio" name="__accessToGrant" value="Secure Read"><font size="2" face="Arial">Automatically grant Secure Read access to channel subscribers</font></td> <td><font size="2" face="Arial"></font>&nbsp;</td> <td>&nbsp;</td>

20

Upgrading to Actuate e.Repor ting Suite 4

</tr> <tr> <td>&nbsp;</td> <td>&nbsp;</td> <td>&nbsp;</td> <td>&nbsp;</td> </tr> </table> </td> </tr> </table> <table border="0" cellpadding="0" cellspacing="0"> <tr><td height="10"></td></tr> </table>

Supporting open server

If you have the advanced e.Reporting Server, you can provide open server support in your 3.x ReportCast templates. To provide support for open server functionality in your 3.x ReportCast templates, use the editor of your choice to modify your configurations folderlist.achtml template file. Open folderlist.achtml and make the following changes: 1 The following code determines whether or not the current folder has items:
<!-- #Actuate list items --> <!-- #Actuate content --> <!-- #Actuate if FolderPath<>"/" or ( ItemBaseName<>"$$$TempROVs" and ItemBaseName<>"$$$CUTCOPY" ) then --> <!-- #Actuate Set FolderHasItems = "TRUE" --> <!-- #Actuate end if --> <!-- #Actuate end list -->

Find the folder has items code, and replace it with the following code:
<!-- #Actuate list items --> <!-- #Actuate content --> <!-- #Actuate if FolderPath <> "/" or ( ItemBaseName <> "$$$TempROVs" and ItemBaseName <> "$$$CUTCOPY" ) then --> <!-- #Actuate Set FolderHasItems = "TRUE" --> <!-- #Actuate end if --> <!-- #Actuate if IsExecutable = "TRUE" then --> <!-- #Actuate Set FolderHasExecutableItems = "TRUE" --> <!-- #Actuate end if --> <!-- #Actuate if IsExecutable <> "TRUE" and AbbreviatedType <> "Directory" then --> <!-- #Actuate Set FolderHasViewableItems = "TRUE" --> <!-- #Actuate end if --> <!-- #Actuate end list -->

Chapter 1, Upgrading to Actuate e.Repor ting Suite 4

21

Save folderlist.achtml, but do not close it yet. Reload your templates, then navigate to your 3.x configurations reporting web site. Verify that the expected folders and items display in your reporting web site pages. 2 The following code determines the folder objects file type, and sets up the request URL:
<!-- #Actuate if AbbreviatedType = "ROX" then --> <td><img src="$(imgRox)"></td> <td><font size="2" face="Arial"><a href="$(URL)?Request">$(ItemBaseName)</font></a></td> <!-- #Actuate elseif AbbreviatedType = "ROV" then --> <td><img src="$(imgRov)" width="16" height="16"></td> <td><font size="2" face="Arial"><a href="$(URL)?Request">$(ItemBaseName)</font></a></td> <!-- #Actuate elseif AbbreviatedType = "ROI" then --> <td><img src="$(imgRoi)" width="16" height="16"></td> <td><font size="2" face="Arial"><a href=$(URL)?View>$(ItemBaseName)</ font></a></td> <!-- #Actuate elseif AbbreviatedType = "ROW" then --> <td><img src="$(imgRow)" width="16" height="16"></td> <td><font size="2" face="Arial"><a href=$(URL)?View>$(ItemBaseName)</ font></a></td> <!-- #Actuate elseif AbbreviatedType = "ROD" then --> <td><img src="$(imgRod)" width="16" height="16"></td> <td><font size="2" face="Arial"><a href=$(URL)?View>$(ItemBaseName)</ font></a></td> <!-- #Actuate elseif AbbreviatedType = "ROL" then --> <td><img src="$(imgRol)" width="16" height="16"></td> <td><font size="2" face="Arial"><a href=$(URL)?View>$(ItemBaseName)</ font></a></td> <!-- #Actuate elseif AbbreviatedType = "BAS" then --> <td><img src="$(imgBas)" width="16" height="16"></td> <td><font size="2" face="Arial"><a href=$(URL)?View>$(ItemBaseName)</ font></a></td> <!-- #Actuate else --> <td><img src="$(imgDocument)"></td> <td><font size="2" face="Arial"><a href=$(URL)>$(ItemBaseName)</font></ a></td> <!-- #Actuate end if -->

Find the request or view URL setup code, and replace it with the following code:
<!-- #Actuate if SmallIconURL <> "" then --> <!-- #Actuate set iconURL = SmallIconURL --> <!-- #Actuate else --> <!-- #Actuate set iconURL = imgDocument --> <!-- #Actuate end if --> <!-- #Actuate if AbbreviatedType="ROI" then --> <!-- #Actuate set DefaultAction="?ViewDefault" --> <!-- #Actuate elseif IsBundledOutput ="TRUE" then -->

22

Upgrading to Actuate e.Repor ting Suite 4

<!-- #Actuate set DefaultAction="?View" --> <!-- #Actuate else --> <!-- #Actuate set DefaultAction="" --> <!-- #Actuate end if --> <!-- #Actuate if IsExecutable="TRUE" and ServerFeatureLevel=serverFeatureLevelAdvanced then --> <!-- #Actuate set DefaultAction="?Request" --> <!-- #Actuate elseif AbbreviatedType="ROW" or IsThirdPartyViewable="TRUE" then --> <!-- #Actuate set DefaultAction="?View" --> <!-- #Actuate else --> <!-- #Actuate set DefaultAction="" --> <!-- #Actuate end if --> <td><img src="$(iconURL)"></td> <td><font size="2" face="Arial"><a href="$(URL)$(DefaultAction)">$(ItemBaseName)</font></a></td>

Save folderlist.achtml, but do not close it yet. Reload your templates, then navigate to your 3.x configurations reporting web site. Verify that the expected folders and items display in your reporting web site pages. 3 The following code sets up a request or view URL for a specified file version name:
<!-- #Actuate if AbbreviatedType = "ROX" or AbbreviatedType = "ROV" then -> <td><font size="2" face="Arial"><a href="$(URL)?Request">$(FileVersionName)</font></a></td> <!-- #Actuate elseif AbbreviatedType = "ROI" then --> <td><font size="2" face="Arial"><a href=$(URL)?View>$(FileVersionName)</font></a></td> <!-- #Actuate elseif AbbreviatedType = "ROW" then --> <td><font size="2" face="Arial"><a href=$(URL)?View>$(FileVersionName)</font></a></td> <!-- #Actuate else --> <td><font size="2" face="Arial"><a href=$(URL)>$(FileVersionName)</font></a></td> <!-- #Actuate end if -->

Find the file version name URL setup code, and replace it with the following code:
<!-- #Actuate if SmallIconURL <> "" then --> <!-- #Actuate set iconURL = SmallIconURL --> <!-- #Actuate else --> <!-- #Actuate set iconURL = imgDocument --> <!-- #Actuate end if --> <!-- #Actuate if AbbreviatedType="ROI" then --> <!-- #Actuate set DefaultAction="?ViewDefault" --> <!-- #Actuate elseif IsBundledOutput ="TRUE" then -->

Chapter 1, Upgrading to Actuate e.Repor ting Suite 4

23

<!-- #Actuate set DefaultAction="?View" --> <!-- #Actuate else --> <!-- #Actuate set DefaultAction="" --> <!-- #Actuate end if --> <!-- #Actuate if IsExecutable="TRUE" and ServerFeatureLevel=serverFeatureLevelAdvanced then --> <!-- #Actuate set DefaultAction="?Request" --> <!-- #Actuate elseif AbbreviatedType="ROW" or IsThirdPartyViewable="TRUE" then --> <!-- #Actuate set DefaultAction="?View" --> <!-- #Actuate else --> <!-- #Actuate set DefaultAction="" --> <!-- #Actuate end if --> <td><font size="2" face="Arial"><a href=$(URL)$(DefaultAction)>$(FileVersionName)</font></a></td>

Save folderlist.achtml, but do not close it yet. Reload your templates, then navigate to your 3.x configurations reporting web site. Verify that the expected folders and items display in your reporting web site pages. 4 Close folderlist.achtml. Your 3.x reporting web pages display your Report Encyclopedia folders and objects as before, and they now support open server functionality. This means that you can now open non-Actuate objects, and these objects have the appropriate file types and icons as set up in the Administrator Desktop. See Administering the Report Encyclopedia for more information.

Changes to template variable availability

The following lists changes to template variables availability:
s s

$(LinkedFolderPath) is now available on request.achtml $(LinkedFolderPath) is now available on confirm.achtml

General compatibility and migration

s

The SFDATA sample database shipped with Actuate 4 has changed. Reports developed using 3.x or earlier versions of SFDATA may display different data when run against the Actuate 4 SFDATA. To ensure that the correct data displays, rebuild reports that use SFDATA using Actuate 4. Actuate 4 does not support Sybase DBLib connections. If you are upgrading a report server on Windows NT from release 3.2.1 or earlier, you must uninstall the older release of the report server before installing the release 4 report server.

s s

24

Upgrading to Actuate e.Repor ting Suite 4

Considerations for Windows systems

s s s

The name of the program group is Actuate e.Reporting Suite 4 The default installation folder is C:\Actuate4 The report server registry key is Actuate\Report Server\4.0

Upgrading from Actuate 4 to Actuate 4.1

Informix database connection changes
Actuate e.Reporting Suite 4.1 does not support Informix Connect 7.2. All pre4.1 .ROXs that previously used Informix Connect 7.2 default to Informix Connect 2.01. If you are running Informix Connect 7.2, upgrade to Informix Connect 2.0.x or Informix Connect 2.4. New e.reports default to using Informix Connect 2.4, supplied with Informix Dynamic Server 2000. If you use a different Informix client version, specify the version as part of AcInformixConnections DllPath connection property. Use DLLPath to set the version of Informix Connect that the connection should use. Informix Connect version 2.01 2.4 AcInformixConnection::DllPath acinfx201 acinfx240

For pre-4.1 .ROXs, the default DllPath is acinfx720. If you run a pre-4.1 .ROX in 4.1 Actuate products, Actuate automatically maps the DllPath to acinfx201.

Concurrent Support of Native and ODBC Informix

Actuate 4.1 does not support using both native Informix and ODBC Informix connections from the same e.Reporting Server.

Considerations for release 4.1 for Windows systems

s s

The report server registry key is Actuate\Report Server\4.1 The ReportCast registry key is Actuate\Actuate Web Agent\4.1

Chapter 1, Upgrading to Actuate e.Repor ting Suite 4

25

26

Upgrading to Actuate e.Repor ting Suite 4

Appendix

A
AppendixA

Installing Actuate desktop products

This appendix describes how to install the Actuate desktop products. You must have local system administrator privileges to install the desktop products.

Installing Actuate desktop products

27

Installing the End User Desktop, LRX, and Viewer on Windows 95, 98, and NT
This section describes installation for the End User Desktop, LRX, and Viewer products. 1 Insert the CD in your drive. 2 In the Control Panel, double-click Add/Remove Programs. 3 Choose Install to start the Install Wizard. The Wizard takes you through the installation process. 4 Choose Finish. Follow the instructions provided by the Wizard to complete the installation. After installation is complete, restart your computer to activate the help system.

Installing the Actuate LRX from the Actuate ReportCast download page
This installation is available if you have installed Actuate ReportCast and have a reporting web site. 1 Open a web browser and navigate to your reporting web site. 2 When you log in to your reporting web site, the main reporting web page appears in the browser window. 3 Choose the My Profile tab. 4 Under Download LRX Viewer, right-click the appropriate LRX executable link. 5 Save the LRX executable: 1 Choose Save Link As (in Netscape) or Save Target As (in Microsoft Internet Explorer). The Save As dialog box appears. 2 Choose a location for the LRX executable. 6 In Windows Explorer, double-click the LRX executable to start the Install Wizard. Follow the instructions provided by the Install Wizard to complete the installation.

28

Upgrading to Actuate e.Repor ting Suite 4

Distributing the Actuate Report Viewer over a network

The Actuate Report Viewer is a royalty-free product. You may distribute it to end users within your organization with no further permission or fees to Actuate. To distribute the Actuate Report Viewer over a network: 1 Create a folder on the network machines drive from which users can access the Actuate Report Viewer. For example, if your network drive is mapped to drive G on your users machines, create the folder G:\Actuate\Distribution. 2 Copy the Actuate Report Viewer directory from the CD to the folder you just created on the network machine. In our example, users now see this directory as G:\Actuate\Distribution\ Viewer. 3 On each user machine that accesses the Actuate Report Viewer over the network: 1 Go to the network drive's Viewer distribution folder. For example, G:\Actuate\Distribution\Viewer. 2 Double-click SETUP.EXE. 3 Follow the screen prompts to complete the installation. 4 To verify that the Actuate Report Viewer works from the user machine, on the user machine, choose StartProgramsActuate e.Reporting Suite 4Actuate Report Viewer.

Appendix A, Installing Actuate desktop products

29

30

Upgrading to Actuate e.Repor ting Suite 4

Appendix

B
Appendix B

Installing ODBC drivers

This appendix describes how to install ODBC drivers.

Installing OD BC dr ivers

31

About ODBC drivers

Actuate desktop products that use the sample reports that ship with our products require ODBC 2.0 or later to run Actuate reports. Actuate ships ODBC 3.0 drivers with the Actuate Developer Workbench. These drivers are supplied to enable you to run the Actuate sample reports. To ensure that you are using a supported level of the ODBC drivers, see Finding the ODBC driver version later in this document. Contact your vendor for the appropriate version ODBC driver to use with your data source. To update the ODBC driver used with your data source, see Updating ODBC drivers used with data sources later in this appendix.

Finding the ODBC driver version

To find the version of ODBC drivers on your system: 1 Choose StartSettingsControl Panel. 2 Choose one of the following options to start the ODBC Data Source Administrator application:
s s

On Windows 95 and Windows 98 systems, choose 32bit ODBC. On Windows NT systems, choose ODBC.

The ODBC Data Source Administrator window appears.

32

Upgrading to Actuate e.Repor ting Suite 4

The Actuate Developer Workbench installs ODBC software that uses this version of the Data Source Administrator. If the ODBC Data Source Administrator window does not look like the previous one, you are running an older version of ODBC. 3 Choose the ODBC Drivers tab. The ODBC Drivers window appears.

Appendix B, Installing OD BC dr ivers

33

Updating ODBC drivers used with data sources

To update the ODBC drivers used with your data sources: 1 Start the ODBC Data Source Administrator. 2 Choose the User DSN or System DSN tab as appropriate. 3 Remove the data source. 4 Add the data source using the updated ODBC drivers. 5 Choose OK. After you have installed the product, verify that your reports work by running them with the updated drivers.

34

Upgrading to Actuate e.Repor ting Suite 4