dev studio install

WebFOCUS Developer Studio Installationand ConfigurationVersion 7 Release 6.4 and Higher

DN4500817.0908

EDA, EDA/SQL, FIDEL, FOCCALC, FOCUS, FOCUS Fusion, FOCUS Vision, Hospital-Trac, Information Builders, theInformation Builders logo, Parlay, PC/FOCUS, SmartMart, SmartMode, SNAPpack, TableTalk, WALDO, Web390,WebFOCUS and WorldMART are registered trademarks, and iWay and iWay Software are trademarks of InformationBuilders, Inc.

Due to the nature of this material, this document refers to numerous hardware and software products by theirtrademarks. In most, if not all cases, these designations are claimed as trademarks or registered trademarks by theirrespective companies. It is not this publisher’s intent to use any of these names generically. The reader is thereforecautioned to investigate all claimed trademark rights before using any of these names other than to refer to theproduct described.

Copyright © 2008, by Information Builders, Inc. and iWay Software. All rights reserved. Patent Pending. This manual,or parts thereof, may not be reproduced in any form without the written permission of Information Builders, Inc.

WebFOCUS

Contents

Preface................................................................................................................7Documentation Conventions..............................................................................................8

Related Publications..........................................................................................................9

Customer Support.............................................................................................................9

Information You Should Have.............................................................................................9

User Feedback................................................................................................................10

Information Builders Consulting and Training.....................................................................11

1. Introducing WebFOCUS and WebFOCUS Developer Studio............................13About WebFOCUS and Developer Studio...........................................................................14

WebFOCUS and Developer Studio Overview and Architecture..............................................15

Developer Studio Components..................................................................................15

WebFOCUS Environments and Components...............................................................16

WebFOCUS Processing.............................................................................................17

Developer Studio Processing....................................................................................18

Developer Studio Development Options.....................................................................18

Developer Studio Networked Installation...................................................................19

Developer Studio on a WebFOCUS Machine...............................................................20

Developer Studio Installation and Configuration Steps.......................................................20

Installation and Configuration Steps..........................................................................21

2. Installing Developer Studio...........................................................................23Developer Studio Requirements.......................................................................................24

Hardware Requirements...........................................................................................24

Software Requirements............................................................................................24

Provided Third Party Components..............................................................................25

Installing Developer Studio..............................................................................................25

Web and/or Application Server Options.....................................................................26

Installing Developer Studio and WebFOCUS on the Same Machine..............................26

Running the Installation...........................................................................................27

WebFOCUS Developer Studio Installation and Configuration 3

Developer Studio Directory Structure.........................................................................30

Installation Log Files................................................................................................32

WebFOCUS Reporting Server for Developer Studio......................................................32

User ID Issues........................................................................................................32

Tomcat Security and Settings...................................................................................33

Verifying Developer Studio...............................................................................................34

Web and/or Application Server Verification................................................................35

Developer Studio Web Server Configuration Verification Tool.......................................38

Migrating From Developer Studio Version 4.......................................................................40

Silent Developer Studio Installation..................................................................................41

3. Configuring the Web Server and/or Application Server................................45Configuration Options......................................................................................................46

Configuring Apache Tomcat..............................................................................................47

Tomcat Configuration Overview.................................................................................47

Configuring Tomcat..................................................................................................48

Additional Tomcat Configuration Options...................................................................51

Configuring Microsoft IIS..................................................................................................53

Configuring IIS Virtual Directories (Aliases)................................................................53

Setting Permissions.................................................................................................55

Configuring Microsoft IIS to Use the Tomcat Connector (Plug-In)..........................................56

Installing and Configuring the Tomcat Connector (Plug-In) for IIS..................................57

Verifying the Configuration........................................................................................61

Configuring Additional Web and/or Application Servers.......................................................62

Configuring the Web Server......................................................................................62

Configuring the Application Server.............................................................................63

Configuring Developer Studio....................................................................................64

A. Configuring a Network Installation...............................................................65Network Installation Steps...............................................................................................66

Ensuring Requirements Are Met................................................................................67

Installing Developer Studio.......................................................................................68

Configuring Developer Studio....................................................................................68

Setting Up Access to the Network Installation............................................................71

Installing Developer Studio Network Shortcuts...........................................................77

4 WebFOCUS

Contents

Launching Developer Studio.....................................................................................78

Customizing WebFOCUS Environments......................................................................79

Accessing Multiple Networked Developer Studio Installations.....................................80

Limiting Access to Developer Studio.........................................................................81

Accessing the Developer Studio Help System............................................................81

Creating Developer Studio Traces From a Client PC in Developer Studio Network

Edition...............................................................................................................82

B. Enabling WebFOCUS Quick Data....................................................................83Configuring WebFOCUS Quick Data...................................................................................84

C. Configuring the Local Reporting Server Security..........................................87WebFOCUS Reporting Server Security and User IDs...........................................................88

Configuring WebFOCUS Reporting Server Security and User IDs..................................88

Running the Server as a Service With Security OFF.....................................................90

D. Enabling and Accessing WebFOCUS Demo Applications...............................91Enabling and Accessing the WebFOCUS Demos.................................................................92

New Demo Application.............................................................................................92

Older NCC Demo Applications...................................................................................92

E. Troubleshooting Developer Studio................................................................95Troubleshooting Tips.......................................................................................................96

Tomcat Configuration Options...................................................................................96

Java Memory Issues................................................................................................96

Starting Developer Studio.........................................................................................98

Multiple Developer Studio Installations.....................................................................98

Troubleshooting Tools.....................................................................................................98

Accessing the Verification Tools in the WebFOCUS Administration Console..................99

WebFOCUS Client Traces.......................................................................................103

Developer Studio Trace Utility.................................................................................104

WebFOCUS Reporting Server Traces........................................................................106

Reader Comments...........................................................................................113


Contents

6 WebFOCUS

Contents

WebFOCUS

Preface

This documentation describes how to install and configure WebFOCUS Developer Studio onmachines running Windows 2000, XP, or 2003 operating systems. This documentation isintended for developers with some knowledge of Windows operating systems.

How This Manual Is Organized

This manual includes the following chapters:

ContentsChapter/Appendix

Provides an overview of WebFOCUS and DeveloperStudio and their installation configurations.

Introducing WebFOCUS andWebFOCUS DeveloperStudio

1

Provides the installation requirements andinstructions, as well as verification and migrationinformation.

Installing Developer Studio2

Provides information on configuring Web and/orapplication servers for stand-alone Project-baseddevelopment and local processing.

Configuring the Web Serverand/or Application Server

3

Provides information for a network installation ofDeveloper Studio.

Configuring a NetworkInstallation

A

Provides information to configure WebFOCUS QuickData.

Enabling WebFOCUS QuickData

B

Provides information needed to configure WebFOCUSReporting Server Security and User IDs.

Configuring the LocalReporting Server Security

C

Provides information to enable and access demoapplications.

Enabling and AccessingWebFOCUS DemoApplications

D


ContentsChapter/Appendix

Provides troubleshooting tips and information onusing verification and tracing tools.

Troubleshooting DeveloperStudio

E

Documentation ConventionsThe following table lists and describes the conventions that apply in this manual.

DescriptionConvention

Denotes syntax that you must enter exactly as shown.THIS TYPEFACE

or

this typeface

Represents a placeholder (or variable), a cross-reference, or animportant term.

this typeface

Indicates a default setting.underscore

Highlights a file name or command. It may also indicate a button,menu item, or dialog box option you can click or select.

this typeface

Indicates keys that you must press simultaneously.Key + Key

Indicates two or three choices; type one of them, not the braces.{ }

Indicates a group of optional parameters. None is required, butyou may select one of them. Type only the parameter in thebrackets, not the brackets.

[ ]

Separates mutually exclusive choices in syntax. Type one of them,not the symbol.

|

Indicates that you can enter a parameter multiple times. Type onlythe parameter, not the ellipsis points (...).

...

Indicates that there are (or could be) intervening or additionalcommands.

.

.

.

8 WebFOCUS

Documentation Conventions

Related PublicationsTo view a current listing of our publications and to place an order, visit our TechnicalDocumentation Library, http://documentation.informationbuilders.com. You can also contactthe Publications Order Department at (800) 969-4636.

Customer SupportDo you have any questions about this product?

Join the Focal Point community. Focal Point is our online developer center and more than amessage board. It is an interactive network of more than 3,000 developers from almostevery profession and industry, collaborating on solutions and sharing tips and techniques,http://forums.informationbuilders.com/eve/forums.

You can also access support services electronically, 24 hours a day, with InfoResponseOnline. InfoResponse Online is accessible through our World Wide Web site,http://www.informationbuilders.com. It connects you to the tracking system and known-problem database at the Information Builders support center. Registered users can open,update, and view the status of cases in the tracking system and read descriptions of reportedsoftware issues. New users can register immediately for this service. The technical supportsection of www.informationbuilders.com also provides usage techniques, diagnostic tips,and answers to frequently asked questions.

Call Information Builders Customer Support Service (CSS) at (800) 736-6130 or (212) 736-6130. Customer Support Consultants are available Monday through Friday between 8:00a.m. and 8:00 p.m. EST to address all your WebFOCUS Managed Reporting questions.Information Builders consultants can also give you general guidance regarding productcapabilities and documentation. Please be ready to provide your six-digit site code number(xxxx.xx) when you call.

To learn about the full range of available support services, ask your Information Buildersrepresentative about InfoResponse Online, or call (800) 969-INFO.

Information You Should HaveTo help our consultants answer your questions effectively, be prepared to provide the followinginformation when you call:

Your six-digit site code (xxxx.xx).

Your WebFOCUS configuration:

The front-end you are using, including vendor and release.

The communications protocol (for example, TCP/IP or HLLAPI), including vendor andrelease.


Preface

http://documentation.informationbuilders.com

http://forums.informationbuilders.com/eve/forums

http://www.informationbuilders.com

The software release.

Your server version and release. You can find this information using the Version optionin the Web Console.

The stored procedure (preferably with line numbers) or SQL statements being used inserver access.

The Master File and Access File.

The exact nature of the problem:

Are the results or the format incorrect? Are the text or calculations missing ormisplaced?

The error message and return code, if applicable.

Is this related to any other problem?

Has the procedure or query ever worked in its present form? Has it been changed recently?How often does the problem occur?

What release of the operating system are you using? Has it, your security system,communications protocol, or front-end software changed?

Is this problem reproducible? If so, how?

Have you tried to reproduce your problem in the simplest form possible? For example, ifyou are having problems joining two data sources, have you tried executing a querycontaining just the code to access the data source?

Do you have a trace file?

How is the problem affecting your business? Is it halting development or production? Doyou just have questions about functionality or documentation?

User FeedbackIn an effort to produce effective documentation, the Documentation Services staff welcomesyour opinions regarding this manual. Please use the Reader Comments form at the end ofthis manual to communicate suggestions for improving this publication or to alert us tocorrections. You can also use the Documentation Feedback form on our Web site,http://documentation.informationbuilders.com/feedback.asp.

Thank you, in advance, for your comments.

10 WebFOCUS

User Feedback

http://documentation.informationbuilders.com/feedback.asp

Information Builders Consulting and TrainingInterested in training? Information Builders Education Department offers a wide variety oftraining courses for this and other Information Builders products.

For information on course descriptions, locations, and dates, or to register for classes, visitour World Wide Web site (http://www.informationbuilders.com) or call (800) 969-INFO tospeak to an Education Representative.


Preface

12 WebFOCUS

Information Builders Consulting and Training

WebFOCUS

Introducing WebFOCUS and WebFOCUSDeveloper Studio

1

Topics:The following topics provide an overviewof WebFOCUS and WebFOCUS DeveloperStudio. About WebFOCUS and Developer

Studio

WebFOCUS and Developer StudioOverview and Architecture

Developer Studio Installation andConfiguration Steps


About WebFOCUS and Developer StudioWebFOCUS is a complete Web-ready data access and reporting system that connects usersto data. WebFOCUS accesses and processes information located in any format on anyplatform and presents that information to users through a Web browser or through formatssuch as PDF, HTML, and Excel.

WebFOCUS Developer Studio is a Windows-based development environment for creatingWebFOCUS applications. Developer Studio provides intuitive graphical tools that help withinterface design, business logic, and data manipulation. Using Developer Studio, developerscan build powerful Web page interfaces that allow users to create and view reports.

WebFOCUS data access, network communications, and server operations are providedthrough WebFOCUS technology. WebFOCUS technology accesses data without concern for the complexities and incompatibilities of different operating systems, databases, file systems,file formats, and networks. You can access both local and remote data on over 35 platformsfrom more than 65 database formats, including FOCUS, MS SQL Server, Sybase, Oracle,Informix, Ingres, and DB2.

Other WebFOCUS products and features include the following:

WebFOCUS Maintain allows you to create applications which update, as well as reporton your data. Maintain development components are installed with Developer Studiodepending on your license.

WebFOCUS Visual Discovery lets you create advanced data visualizations for executivelevel Dashboards. Visual Discovery displays data as involved geometric shapes (forexample, points, lines, circles, rectangles) with many attributes (for example, proximity,size, color). This lets you view and manipulate your data in a new light to discoverrelationships that are not apparent in normal tables, reports, or graphs. You can useVisual Discovery to turn raw data into insightful images to understand and discover trendsand patterns. If you license Visual Discovery, then its development components areinstalled with Developer Studio. For more information, see the Using WebFOCUS VisualDiscovery Components With Developer Studio manual.

ReportCaster is an independent application that enables you to schedule the deliveryand automatic running of WebFOCUS reports and alerts as well as independent files andURLs. ReportCaster is not installed with Developer Studio.

14 WebFOCUS

About WebFOCUS and Developer Studio

WebFOCUS and Developer Studio Overview and Architecture

In this section:

Developer Studio Components

WebFOCUS Environments and Components

WebFOCUS Processing

Developer Studio Processing

Developer Studio Development Options

Developer Studio Networked Installation

Developer Studio on a WebFOCUS Machine

Developer Studio is used to develop and manage WebFOCUS applications as well as toadminister Managed Reporting environments. It is normally assumed, but not required, thatWebFOCUS is installed, or will be installed, somewhere in your enterprise. In addition,Developer Studio architecture and functionality are based on the architecture of WebFOCUS.

Developer Studio ComponentsThere are two pieces involved when developing or administering with Developer Studio.

Developer Studio itself is technically the graphical development and code generationtools that organize and create WebFOCUS files. Depending on your license, it may alsoinclude the Maintain Development Environment. It lets you design reports and organizeapplications.

The graphical and code generation tools do not actually process reports and access data.Instead, they connect to a WebFOCUS environment.

A WebFOCUS Environment is a complete implementation of WebFOCUS. When youinstall Developer Studio, you have the option to install and create a developmentWebFOCUS environment along with Developer Studio (available for the Developer Studioedition only--this allows local, standalone development). After installing Developer Studio,you can choose to connect to a WebFOCUS Environment installed elsewhere in yourenterprise or use one installed locally.

Note: For all other editions, including installations of the Network editions, you configureDeveloper Studio to access a WebFOCUS environment you installed separately. This stepis performed from within Developer Studio.


1. Introducing WebFOCUS and WebFOCUS Developer Studio

WebFOCUS Environments and ComponentsIn a WebFOCUS environment, WebFOCUS connects a Web server and/or application serverto your data. End users then access WebFOCUS applications through a Web browser. Yourenterprise may have multiple WebFOCUS environments each containing the followingcomponents:.

Third Party Web and/or Application Server. Users access WebFOCUS by makingrequests to a Web or application server. WebFOCUS functionality can be implementedusing either CGI, ISAPI, or Java servlet calls. Java servlets are the default and not allfeatures are supported with CGI and ISAPI. When Developer Studio communicates withWebFOCUS, it does so through the Web and/or application server as well.

Apache Tomcat is provided along with Developer Studio and WebFOCUS for Windows, sono separate Web or application server is required to get started. Apache Tomcat is aservlet container that Developer Studio can use as a Web server and application server.

Note: Web servers handle traditional Web content like static HTML and GIF files as wellas CGI requests. Application servers generally handle Java and other processes, butmany application servers can also handle the traditional Web content. If your applicationserver can handle traditional Web content, then a Web server is not required. The termapplication server is used to refer to either an application server or servlet container inWebFOCUS documentation. A servlet container general handles a subset of what anapplication server can handle.

WebFOCUS Client resides on the Web server and/or application server. When a usermakes a request to the Web server from a Web page or Developer Studio, WebFOCUSClient receives the request, processes it, and passes it to the WebFOCUS ReportingServer. The WebFOCUS Client connection can be implemented through Java servlets,CGI, or ISAPI, although some features are only supported with Java servlets. In addition,WebFOCUS Client may include other WebFOCUS products and interfaces such as ManagedReporting.

A scaled down WebFOCUS Client is installed with Developer Studio. The functionality available is based on the Developer Studio edition for which you are licensed.

WebFOCUS Reporting Server. The WebFOCUS Reporting Server provides data access,data processing, and report generation functionality. WebFOCUS Reporting Serversreside on machines that can access your data. There can be multiple WebFOCUSReporting Servers in a WebFOCUS environment. A WebFOCUS Reporting Server isalways installed with Developer Studio because some components are required bythe development tools.

16 WebFOCUS


WebFOCUS employs a distributed architecture. This means that the WebFOCUS Client andits WebFOCUS Reporting Servers can either be on the same machine and operating systemor distributed across multiple machines running different operating systems. You can easilyconnect an Apache Web server running on UNIX to SQL Server data on Windows and DB2data on z/OS.

For more information on WebFOCUS components and configuration options, refer to theinstallation and configuration documentation.

Note: To ensure proper communication, WebFOCUS components should be the same releasenumber as each other and Developer Studio.

WebFOCUS ProcessingThe following steps accompany the figure below and describe how WebFOCUS or DeveloperStudio processes requests:

1. A user requests a report and passes parameters by calling the WebFOCUS servlet throughlinks and forms on a Web page or through Developer Studio.

2. The request and parameters come to the WebFOCUS Client through the Web and/orapplication servers, and the WebFOCUS Client processes the parameters to create arequest for the WebFOCUS Reporting Server.

3. The WebFOCUS Reporting Server receives the request, processes it, and accesses anyneeded data.

4. Data is retrieved from data sources to process the request.

5. The WebFOCUS Reporting Server processes the user's request using the retrieved data.

6. The response is returned to the WebFOCUS Client.

7. The response is returned to the user.



Developer Studio ProcessingDeveloper Studio processes requests the same way that WebFOCUS does. Developer Studiomakes calls to a Web and/or application server that is configured to accept a WebFOCUSCGI, ISAPI, or servlet request. The CGI, ISAPI, or servlet then connects to the WebFOCUSReporting Server to process the report request.

Note: CGI and ISAPI are not supported with Developer Studio at this time.

The Web and/or application server can be located on the same machine as Developer Studioor located elsewhere in your enterprise.

Local Web and/or application server. When you install Developer Studio, you canchoose to install and configure a Web and/or application server. Manual configurationinstructions are also provided in Configuring the Web Server and/or Application Server onpage 45. Using a local Web and/or application server creates a development WebFOCUSenvironment and allows you to process reports on the Developer Studio machine.

Remote Web and/or application server. If you do not wish to use a local Web and/orapplication server, you can configure Developer Studio to connect to a WebFOCUSenvironment elsewhere on your network. Developer Studio then processes reports andfiles on the remote WebFOCUS machines.

You can also use a combination of local and remote processing.

Developer Studio Development OptionsDeveloper Studio provides flexibility in how you develop and maintain your WebFOCUSapplications and reports. There are several ways to develop with Developer Studio.

Project-Based Development. In Project-based development, you use Developer Studioto create and manage applications. These applications are referred to as projects. Whenyou create a project with Developer Studio, a special file with a .gfa (graphical FOCUSapplication) extension is created. The GFA file helps control and organize your applicationthrough the development, testing, deployment, and maintenance phases. Project-baseddevelopment also provides tools to organize your applications based on file types.

You can test and run your projects either from within Developer Studio or through a Webbrowser. When an application is ready for production, Developer Studio provides toolsto transfer and deploy project files to machines running production WebFOCUSenvironments.

18 WebFOCUS


There are two types of Project-based development:

In Stand-Alone Project-Based Development, files are developed on the samemachine where you install Developer Studio, or files are accessed through a third-partysource management system (such as Visual SourceSafe). Developers who work alonehave all their files where they can easily edit them. Developers on separate desktopscan share files controlled by a source management system.

Note: Third party source management client software must be installed on theDeveloper Studio machine to use source management tools.

With stand-alone Project-based development, a Web and/or application server isrequired on the machine where you run Developer Studio.

In Remote Project-Based Development, you use Developer Studio to connect toa WebFOCUS environment running elsewhere in your enterprise. Files are then storedin the remote WebFOCUS environment or files are accessed through a third-partysource management system (such as Visual SourceSafe).

It is recommended for Remote Project-based development that all WebFOCUScomponents in the remote environment reside on the same machine as each other.

Remote Development. In remote development, a GFA file is not used to organize thefiles in your applications and some tools, such as source management and the deploytool, are not available. In remote development, you use Developer Studio to connect toWebFOCUS environments running elsewhere in your enterprise. After you are connected,you can create and edit files on the remote machines and perform application developmentthrough the Data Servers area or use the Managed Reporting area to perform ManagedReporting development and administration.

For more information about Developer Studio configurations and development environments,see the Developer Studio Application Development Getting Started manual.

Developer Studio Networked InstallationNormally Developer Studio is installed on the desktop of each developer. However, anetworked Developer Studio installation option is available as well.

In a networked configuration, Developer Studio is installed on a single shared machine,rather than each developer's desktop. Developers then launch Developer Studio on theirdesktops by executing files that have been installed on the shared machine. This simplifiesadministration, installation, and upgrading and it allows all developers to use a commonpre-configured environment.



A network installation of Developer Studio includes only the GUI tools to develop, organize,maintain, and deploy applications and procedures. Full WebFOCUS Client connectivity (CGI,ISAPI, servlet) is not included. After installing the networked Developer Studio option, youmust set up a connection to a WebFOCUS environment somewhere on your network. DeveloperStudio then uses the Web server configuration, application server configuration, WebFOCUSClient connectivity, and WebFOCUS Reporting Server of that WebFOCUS environment.

Network installations are discussed in Configuring a Network Installation on page 65.

Developer Studio on a WebFOCUS MachineDeveloper Studio and WebFOCUS can be installed on the same machine provided WebFOCUSis installed first. The Developer Studio installation program will detect that WebFOCUS isalready installed and use the existing WebFOCUS environment and components. DeveloperStudio then runs using the existing WebFOCUS Client configuration, application root directories(APPROOT), Web server aliases (virtual folders), and WebFOCUS Reporting Server. All productscan co-exist and use the same WebFOCUS environment through Developer Studio or abrowser.

Developer Studio Installation and Configuration Steps

In this section:

Installation and Configuration Steps

The steps to install and configure Developer Studio vary depending on how you plan todevelop applications.

Local Processing. Install Developer Studio on each developer's machine and thenensure a Web and/or application server is configured on each machine. To access data,configure the local WebFOCUS Reporting Server. Developers will develop applicationsand run reports on their machines.

Remote Processing. Install Developer Studio on each developer's machine. Then, setup a connection from each Developer Studio machine to a WebFOCUS environmentinstalled somewhere on your network. To access data, configure the WebFOCUS ReportingServer in the WebFOCUS environment. A Web and/or application server is not neededon the Developer Studio machines because developers connect to environments runningelsewhere to develop applications and run reports.

20 WebFOCUS


Network Installation. Install Developer Studio on one shared machine. Developers willrun Developer Studio from their desktop by accessing the files installed on the sharedmachine over the network. You must set up a connection from Developer Studio on theshared machine to a WebFOCUS environment. To access data, configure the WebFOCUSReporting Server in the WebFOCUS environment. A special license code is needed for anetwork installation.

Installation on a WebFOCUS Machine. Install Developer Studio after WebFOCUS isinstalled and configured. Developer Studio connects to the WebFOCUS environment thatis already installed.

Installation and Configuration StepsPerform the following steps to install and configure Developer Studio:

1. Ensure all requirements are met (see Installing Developer Studio on page 23).

2. Run the Developer Studio installation (see Installing Developer Studio on page 23).

3. Ensure a Web and/or application server is configured either locally or remote.

For local processing, verify the automatic Web and/or application server configuration(see Installing Developer Studio on page 23) or manually configure a Web and/orapplication server (see Configuring the Web Server and/or Application Server on page45).

For remote processing or network installations, ensure a WebFOCUS environment hasbeen configured somewhere on your network. See the WebFOCUS and ReportCasterInstallation and Configuration manual for your platform to install WebFOCUS.

4. Start Developer Studio.

5. Set up a connection to a WebFOCUS environment.

For local processing and installation on a WebFOCUS machine, this should occurautomatically if the Web server is configured. In some environments, you may needto specify the Web server port to set up the connection. You can also createconnections to additional WebFOCUS environments running on your network.

For remote processing or network installations, set up connections to WebFOCUSenvironments and specify the default environment to use for development.

6. Configure data adapters and metadata to report on your data through the WebFOCUSReporting Server (see Developer Studio Application Development Getting Started guide).For remote processing and network installations, you use the adapters and metadata ofthe remote environment.



7. For network installations, configure access from developer's desktops to the sharedmachine where you installed Developer Studio (see Configuring a Network Installation onpage 65).

22 WebFOCUS


WebFOCUS

Installing Developer Studio2Topics:

The following topics explain how to runthe Developer Studio installationprogram. In addition, these topics explainhow to verify the configuration andmigrate applications from DeveloperStudio 4.x releases.

Developer Studio Requirements

Installing Developer Studio

Verifying Developer Studio

Migrating From Developer StudioVersion 4

Silent Developer Studio Installation



In this section:

Hardware Requirements

Software Requirements

Provided Third Party Components

Review the following requirements to ensure your machine supports Developer Studio.

Hardware RequirementsVerify that your Windows machine meets the Developer Studio hardware requirements:

Pentium 3 or higher at 600 MHz or higher.

VGA or higher resolution graphics card. Display of 1027x768 is recommended.

512 MB of RAM.

500 MB free hard disk space for CD installation. 1 GB for downloaded installation.

Software RequirementsYour Windows machine must meet the following Developer Workbench software requirements:

Windows XP Professional, Windows Vista Business and Ultimate editions, 2000,or Windows 2000 and 2003 Professional and Server editions. Windows 2000 musthave Service Pack 2 or higher.

Internet Explorer 6 and higher. Internet Explorer components are required for DeveloperStudio. If possible, upgrade to the most recent version of Internet Explorer.

Adobe Acrobat Reader 6.0 and higher. Acrobat Reader 6, 7, and 8 are certified toview PDF reports generated by Developer Studio.

Note: You must be an administrator to the Windows machine to run the installation.

To use the WebFOCUS servlet, the required third party components are included withDeveloper Studio. Developer Studio can install and configure Apache Tomcat for use as botha Web server and application server. However, to use local processing with CGI or ISAPI, aWeb server that supports aliasing and the CGI or ISAPI protocol must be separately installed.At this time though, CGI and ISAPI are not supported with Developer Studio.

24 WebFOCUS


Provided Third Party ComponentsThe following third party components are provided for use with Developer Studio. If they arenot present on your machine, you have the option to install them with Developer Studio:

Java 2 SDK 1.6.0_03. A Java SDK is required for WebFOCUS features such as servletconnectivity, graph generation, and OLAP. If a Java SDK 1.4.1 or higher is not installedon your machine, you must allow Developer Studio to install the SDK. If you choose toinstall Apache Tomcat 5.5, you must use a Java SDK 1.5.0 or higher.

Apache Tomcat 5.5. A Web and/or application server is required for stand-aloneProject-based development and local report processing. Apache Tomcat is provided andcan be automatically configured for use as either both a Web and application server oras only an application server.

Apache Tomcat is not required if you are using another Web and/or application serversupported with WebFOCUS.

Without a Web and/or application server, you can create and process reports by connectingDeveloper Studio to an instance of WebFOCUS installed somewhere else. However, filescannot be processed or stored locally without a Web or application server on the DeveloperStudio machine.


In this section:

Web and/or Application Server Options

Installing Developer Studio and WebFOCUS on the Same Machine

Running the Installation

Developer Studio Directory Structure

Installation Log Files

WebFOCUS Reporting Server for Developer Studio

User ID Issues

Tomcat Security and Settings

There are two ways to run the installation utility:

Graphical (GUI) Installation. The default installation mode launches windows thatprompt for parameters. You should use the GUI installation the first time you installDeveloper Studio Version 7 Release 6 (7.6). This section describes the standard GUIinstallation of Developer Studio.


2. Installing Developer Studio

Silent Installation. In a silent installation, you launch the installation and specify a textfile. The text file contains the installation parameters, so no GUI windows are launched.For silent installations, see Silent Developer Studio Installation on page 41.

Caution: When updating Developer Studio from a previous 7.6 release, either apply a servicepack installation or completely uninstall the older 7.6 product before running the fullinstallation. To uninstall Developer Studio, use the Uninstall option in the WebFOCUS 76Developer Studio program group. If you manually delete Developer Studio directories, youmay leave files and registry settings that could affect future installs. If prompted to rebootafter uninstalling, do so before reinstalling.

Web and/or Application Server OptionsThe Developer Studio installation can automatically configure one of the following for you:

Apache Tomcat Standalone. You can use Apache Tomcat as both a Web and applicationserver. The Developer Studio installation can install and configure this for you. This isthe simplest configuration. However, this configuration does not support the WebFOCUSCGI or ISAPI.

Microsoft IIS and Apache Tomcat. You can use IIS as the Web server with ApacheTomcat as the application server, if IIS is installed. In this configuration, traditional Weband CGI processing are handled by IIS and servlet processing is handled by Tomcat. Callsare made to IIS and IIS then routes requests to Tomcat when servlet processing isneeded. This is done using the Tomcat JK 1.2 connector (plug-in) for IIS. This is notsupported if ServletExec ISAPI is installed. IIS cannot use both the Tomcat plug-in andServletExec ISAPI.

This document assumes IIS listens on port 80 and Tomcat listens on port 8080. If youchange the defaults, substitute accordingly.

You can manually configure a different application server as explained in Configuring theWeb Server and/or Application Server on page 45.

Note: New Atlanta ServletExec ISAPI is not supported at this time.

Installing Developer Studio and WebFOCUS on the Same MachineWhen installing WebFOCUS and Developer Studio on the same machine, do the following:

1. Ensure that your machine meets the WebFOCUS requirements.

2. Completely install and configure WebFOCUS.

3. Install Developer Studio.

26 WebFOCUS


The Developer Studio installation program will detect that WebFOCUS is already installedand will not provide options to automatically configure a Web and/or application server. Youdo not need to configure a Web and/or application server for Developer Studio if one isalready configured for WebFOCUS on the machine. Developer Studio will use the existingWebFOCUS environment including the Web and/or application server configuration. Allproducts can co-exist and use the WebFOCUS environment through Developer Studio or abrowser.

Running the Installation

How to:

Install Developer Studio

Follow this procedure to install Developer Studio.

Note: You must be an administrator to the Windows machine to run the installation.

How to Install Developer StudioProcedure:

You may receive the Developer Studio installation on CD or through an Internet download.

1. Execute the installation program:

For a CD installation, insert the installation CD in the CD drive and follow theinstructions on the screen. If the installation program does not start automatically,run the Setup.exe application in the root directory of the CD.

For a downloaded installation, run the downloaded file and respond when promptedto unpack files needed during the installation. When the files are unloaded, the actualinstallation begins.

The installation begins with a Welcome window.

2. Click Next at the Welcome window.

The License Agreement appears.

3. Click Yes if you accept the License Agreement.

If an earlier version of a Developer Studio 7.6 is already installed, you may be promptedto either Update or perform a Full Install. If you choose update, the installation beginsimmediately and your older version is replaced. When updating, be sure to reload theWeb application and reconfigure any changes in the cgipath.js file.

You are prompted for the product serial number if no earlier version of Developer Studio7.6 is found.



4. Type the product serial number when prompted and click Next. The serial number canbe found on the back of the CD case.It is based on your license agreement and controlsthe software edition that is installed.

Note: If you wish to use Visual Discovery or a network installation, ensure you have thecorrect license.

If you type a valid serial number, the Registration Confirmation window appears.

5. Click Yes to accept the Registration Confirmation.

A window appears describing Developer Studio requirements.

6. Review the requirements and click Next.

A list of components and options appears.

The following installation options appear. If an option is already installed or unavailable,it is greyed out:

WebFOCUS Developer Studio. When selected, this installs the Developer Studiodevelopment environment. This is required.

28 WebFOCUS


Java 2 SDK, SE 1.6.0_03. When selected, this installs Java components neededfor Developer Studio. If Java SDK 1.4.1 or higher is not already installed, you mustinstall this SDK. If you choose to install Tomcat 5.5, and Java SDK 1.5.0 or higheris not installed, you must install this SDK.

Apache Tomcat 5.5.25. When selected, this installs Apache Tomcat for use as theWeb and/or application server. Java SDK 1.5.0 or higher is required.

The following configuration options appear:

Configure Apache Tomcat 5.5.25 standalone. When selected, this configuresApache Tomcat 5.0 or 5.5 for use with Developer Studio as both a Web andapplication server. This can also be manually configured as explained in Configuringthe Web Server and/or Application Server on page 45.

Configure Apache Tomcat 5.5.25 connector (plug-in) for Microsoft IIS. Whenselected, this configures Apache Tomcat 5.0 or 5.5 as the application server,configures IIS as the Web server, and configures communications between IIS andTomcat. IIS must be installed to use this option. This can also be manually configuredas explained in Configuring the Web Server and/or Application Server on page 45.

WebFOCUS Quick Data. This option installs an Excel Add-In that allows developersto create WebFOCUS reports directly from Microsoft Excel. Developers create reportsusing the HTML Report Assistant, and output is displayed in the active ExcelWorkbook.

Enabling this option through Developer Studio provides a single-user license applicableonly to the Developer Studio user and functions against the local Developer Studioenvironment or against licensed WebFOCUS environments.

This feature must be licensed separately for use in multi-user WebFOCUSenvironments. This also applies when Developer Studio and WebFOCUS are installedon the same PC. For configuration information on WebFOCUS Quick Data, see EnablingWebFOCUS Quick Data on page 83.

The configuration options are not available if WebFOCUS is detected, if you perform anetwork installation, or if you install the Managed Reporting Developer edition. IfWebFOCUS is detected, Developer Studio uses the existing WebFOCUS environment.For a network installation or Managed Reporting Developer edition, you must connectDeveloper Studio to a WebFOCUS environment after installation.

To manually configure a different application server, deselect the configuration optionsand refer to Configuring Additional Web and/or Application Servers on page 62.

7. Select the components you wish to install and configure, and then click Next.

You are prompted for the directory where Developer Studio components are installed.



8. Choose the directory for Developer Studio components and click Next. You cannot includespaces in the folder name.

Note: If you are installing Developer Studio on the same machine as other WebFOCUSproducts, it is recommended that all products be installed on the same drive in thesame ibi directory.

The Start Copying Files window appears.

9. Review the settings at the Start Copying Files window and click Next to begin theinstallation.

The installation may take some time. When the installation completes, you have theoption to view the WebFOCUS New Features PDF.

10. Click Finish to complete the installation.

Note: If you choose the Tomcat connector (plug-in) option and receive a message that says"Unable to Create Filter," some manual configuration is required. To do this, open the InternetServices Manager, right-click your Web site, and choose Properties. On the ISAPI Filters tab,determine if a jakarta or ServletExec filter appears. If neither appear, click Add and add theisapi_redirect.dll file using the filter name jakarta. For more information, review the remainderof this chapter and then see Configuring Microsoft IIS to Use the Tomcat Connector (Plug-In)on page 56. Also, be aware that you cannot use the Tomcat plug-in if ServletExec ISAPI isinstalled.

Developer Studio Directory StructureAfter installation, the Developer Studio directory structure is created. The default locationis:

C:\ibi

The following are some of the main subdirectories. The actual directories may vary basedon your license:

\apps

Contains applications and data. By default, this is the APPROOT directory whereWebFOCUS looks for application files. Sample files are provided in the \ibinccen and\ibisamp directories.

\DevStudio76\backup

Contains a backup of the cgivars.wfs file. If your main cgivars.wfs configuration becomescorrupt, you can use this backup file to replace a corrupt version.

\DevStudio76\bin

Contains the graphical front-end components for creating WebFOCUS applications.

30 WebFOCUS


\DevStudio76\client

Contains WebFOCUS Client configuration files. Many of these files were installed withthe WebFOCUS Reporting Server in previous versions. However, the main communicationsfile odin.cfg is still installed under the srv76\wfs\etc directory instead.

\DevStudio76\config

Contains the install.cfg that holds information about the installation.

\DevStudio76\ibi_html

Contains Web page components that provide local processing, Web based tools, andother features.

\DevStudio76\logs

Contains space for logs.

\DevStudio76\QuickLinks

Contains links for sample applications.

\DevStudio76\srv76

Contains a WebFOCUS Reporting Server installed and configured for Developer Studio.

\DevStudio76\temp

Contains space for local processing.

\DevStudio76\Templates

Contains reporting and maintain templates.

\DevStudio76\Utilities

Contains tools and files for additional configurations.

\DevStudio76\Webapps

Contains the WebFOCUS Web application.

\profiles

Contains space for the WebFOCUS Reporting Server profiles.

If you installed Tomcat, the default location is:

C:\Program Files\Apache Software Foundation\Tomcat 5.5

If you are using Tomcat and IIS together, the Tomcat plug-in (connector) is installed in:

C:\Program Files\Apache Software Foundation\Jakarta Isapi Redirector



Installation Log FilesThe following log file is created by the Developer Studio installation:

C:\wf_ds_76_inst.log

This log file provides information about the Developer Studio installation. If you contactCustomer Support Services with an installation problem, have this file available.

If you license the Visual Discovery feature, the following log is created by its installation:

C:\wf_ds_76_vis_ins.log

If you install the Java SDK with Developer Studio, the following files are also created:

C:\jdk_6u3.logC:\jre_6u3.log

WebFOCUS Reporting Server for Developer StudioThe Developer Studio development tools require certain components installed with theWebFOCUS Reporting Server. Therefore, a Reporting Server is always installed with DeveloperStudio even when one is already installed or you use Developer Studio for remote processing.

This server is configured for Developer Studio and installed within the Developer Studiodirectory structure. On the Start menu, it is under Programs, Information Builders, WebFOCUS76 Developer Studio, and WebFOCUS 76 Server for DevStudio.

Note: By default, the server only starts with security OFF and can only be started by theuser who installed Developer Studio. To change these defaults, see WebFOCUS ReportingServer Security and User IDs on page 88.

If you install Developer Studio on the same machine as WebFOCUS, be sure to configurethe server installed for WebFOCUS and not the server installed with Developer Studio. Theserver installed for WebFOCUS should be started before Developer Studio. Otherwise,Developer Studio starts the server installed with Developer Studio instead.

User ID IssuesThe Developer Studio installation created registry settings under HKEY_CURRENT_USERthat are only available to the user ID that installed Developer Studio. If you log on to theDeveloper Studio machine as another user ID and attempt to run Developer Studio, themissing registry settings may cause problems with certain features (e.g., Quick Links, ImpactAnalysis, etc.).

To run Developer Studio as a user ID that did not install Developer Studio, log on to themachine as the user ID under which you wish to run Developer Studio and executing thefollowing utility:

drive:\ibi\DevStudio76\Utilities\import_reg.bat

32 WebFOCUS


This adds the registry settings for the user ID logged on when you execute it. If you receivean error, ensure that the user ID can write to the registry under HKEY_CURRENT_USER.

In addition, you must also configure security for the WebFOCUS Reporting Server as explainedin WebFOCUS Reporting Server Security and User IDs on page 88. By default only the userthat installed Developer Studio can start the WebFOCUS Reporting Server, so this must bechanged if you use the local server.

Tomcat Security and Settings

Reference:

Apache Tomcat Installation Information

If you are not using Tomcat, proceed to Verifying Developer Studio on page 34.

Apache Tomcat Installation InformationReference:

If you installed Tomcat with Developer Studio, the installation is done silently and usesdefault settings.

The default installation directory is:

C:\Program Files\Apache Software Foundation\Tomcat 5.5

To start, stop, and restart Tomcat, you can use the Services window (Control Panel,Administrative Tools, Services). The Tomcat service is listed as Apache Tomcat and isconfigured to start automatically with Windows.

By default, a Tomcat user ID of "admin" is defined with no password. This user ID is onlyfor Tomcat Web-based administration tools and is not related to WebFOCUS or Windowsuser IDs. Tomcat user IDs and passwords are defined, unencrypted in:

C:\Program Files\Apache Software Foundation\Tomcat 5.5\conf\tomcat-users.xml

If you are not safely behind a firewall, you can add a password for the admin user ID byediting this file. For example:

<user username="admin" password="xxxxxxx" roles="admin,manager"/>

Tomcat uses TCP ports 8080, 8009, and 8005 by default. Port 8080 is the HTTP listenerthrough which you access Tomcat in a Web browser. Port 8009 is needed for the TomcatConnector (plugin) for IIS. If you need to change these ports, you must edit the followingfile:

C:\Program Files\Apache Software Foundation\Tomcat 5.5\conf\server.xml



See Tomcat Ports on page 51. If you change defaults, substitute accordingly in proceduresand examples. You also need to update Developer Studio's connection settings so itknows the correct Tomcat HTTP port if you change the default.

If you choose to install the Tomcat Connector (plugin) for IIS, it is installed silently in:


The default Tomcat Java memory settings are increased when Tomcat is installed withWebFOCUS 7.6. If you did not install Tomcat with Developer Studio 7.6, you shouldincrease the Java memory options as explained in Java Memory Issues on page 96.

The Tomcat Administration Tool is not installed automatically with the Tomcat installation.It is included in the Developer Studio package (CD or extracted files) in:

DISK1\tomcat5.5.25\apache_tomcat_5.5.25_admin

This is available for debugging purposes and is not fully stabilized for creating contexts.


In this section:

Web and/or Application Server Verification

Developer Studio Web Server Configuration Verification Tool

Developer Studio connects to a WebFOCUS environment in order to create and processreports.

If you chose to have the installation configure Apache Tomcat, a development WebFOCUSenvironment should exist for Developer Studio. Verify the Web and/or application serverconfiguration as explained in Web and/or Application Server Verification on page 35.

If Developer Studio is installed on the same machine as WebFOCUS, Developer Studiouses the already installed WebFOCUS environment. In some environments, you mightneed to specify the Web server port or change default connection settings in the DeveloperStudio WebFOCUS Environment Properties dialog box.

For a network installation, proceed to Configuring a Network Installation on page 65 toset up a connection to a WebFOCUS environment and configure shared access.

To manually configure a Web and/or application server for local processing, proceed toConfiguring the Web Server and/or Application Server on page 45.

34 WebFOCUS


Web and/or Application Server Verification

How to:

Start Apache Tomcat or Microsoft IIS

Verify the Web Server

Verify the WebFOCUS Web Application Deployment

If Tomcat is configured for you, you should restart it to ensure all settings are correct. If youare using Tomcat with IIS, you should restart IIS as well.

How to Start Apache Tomcat or Microsoft IISProcedure:

1. Open the Services window by opening the Control Panel, Administrative Tools, and thenServices.

Tip: On Windows XP, if the Administrative Tools option does not appear, select Switchto Classic View in the upper left of the Control Panel.

2. Right-click Apache Tomcat and/or IIS Admin Service and choose Start, Stop, or Restart.For IIS, also make sure the World Wide Web Publishing Service is started.

Note:

If you install Tomcat with Developer Studio, the Tomcat service starts automaticallywith Windows. If you want to change this behavior, right-click Apache Tomcat in theServices window, choose Properties, and change the Startup type to Manual. However,be sure to start Tomcat before starting Developer Studio.

You can also start Tomcat from the Start menu by selecting Programs, Apache Tomcat5.5, and Configure Tomcat. A window appears where you can start Tomcat and changesome settings related to how Tomcat runs as a service.

A WebFOCUS 76 Server for Developer Studio service appears in the Services windows.However, you should not start this server from here. This WebFOCUS Reporting Servercannot run as a service or with security OPSYS until you configure security asexplained in WebFOCUS Reporting Server Security and User IDs on page 88.



How to Verify the Web ServerProcedure:

After starting or restarting your Web server, confirm that it is running by accessing it througha browser.

For IIS, go to the following page in your browser:

http://localhost

For Tomcat, go to the following page in your browser:

http://localhost:8080

When using Tomcat standalone, you use port 8080 when accessing Tomcat in a Webbrowser or through Developer Studio. When using Tomcat with IIS, you normally do notgo through port 8080 when running Developer Studio, but you can go to this port toensure Tomcat is running and configure Tomcat.

The Tomcat home page should appear.

If the home page does not appear, the Tomcat may still be loading. Wait a few minutesand try again.

36 WebFOCUS


How to Verify the WebFOCUS Web Application DeploymentProcedure:

The WebFOCUS Web application is installed with Developer Studio in:

drive:\ibi\DevStudio76\webapps\webfocus76

and

drive:\ibi\DevStudio76\webapps\webfocus76.war

If you chose the automatic configuration option, Tomcat is configured to access the expandedwebapps\webfocus76 directory when it receives a request for

/ibi_apps

If you are using IIS with Tomcat, then IIS receives the request for /ibi_apps and passes thatrequest to Tomcat.

You should test this by going to the about.jsp page installed with the WebFOCUS Webapplication. If you are not using the default ports, substitute accordingly.

If you are using Tomcat either standalone or with IIS, go to the following URL:

http://localhost:8080/ibi_apps/about.jsp

A page displaying information about the build should display. When using Tomcat withIIS, there may be a broken image. When using Tomcat with IIS, you normally do not accessTomcat at port 8080, but can use it for testing and configuration.

If you are using Tomcat standalone, you can also go to the WebFOCUS Welcome page:

http://localhost:8080/ibi_apps/homepage.jsp

If you are using IIS with Tomcat, go to the following URL:

http://localhost/ibi_apps/about.jsp

When using Tomcat with IIS, IIS should route the ibi_apps request to Tomcat and returnthe about.jsp page. In this configuration, you should go through IIS when accessingTomcat. If both IIS and Tomcat are running and you choose to configure the plug-in,ensure ServletExec ISAPI is not installed.

If you are using IIS as the Web server, you can also go to the WebFOCUS Welcome page:

http://localhost/ibi_apps/homepage.jsp



Developer Studio Web Server Configuration Verification Tool

How to:

Run the Verification Tool

A verification tool is installed along with Developer Studio as part of the WebFOCUSAdministration Console.

How to Run the Verification ToolProcedure:

1. Ensure the Tomcat and/or IIS are started.

2. Go to the WebFOCUS Administration Console home page using Internet Explorer. Youcan access this by clicking WebFOCUS Administration Console at the WebFOCUS Welcomepage. If you are using Apache Tomcat standalone, you can also go to:

http://localhost:8080/ibi_apps/console/webfocusconsole.jsp

For IIS with Tomcat, you can go to:

http://localhost/ibi_apps/console/webfocusconsole.jsp

A logon page appears. If a logon page does not appear, ensure your Web server isstarted. If the Web server is started and this page does not appear, you may need tomanually configure the Web server as explained in Configuring the Web Server and/orApplication Server on page 45.

3. Log on using an administrator user ID. By default, "admin" is a valid administrator ID,and the password is not initially authenticated.

The WebFOCUS Administration Console appears.

38 WebFOCUS


Using this console, you can edit communication and security settings. This console isdocumented in the WebFOCUS Security and Administration manual and relevant sectionsare available by clicking Help. The WebFOCUS Administration Console contains averification tool to further test the configuration.

4. On the left of the WebFOCUS Administration Console, click Diagnostics.

5. Below Diagnostics and Verification, click Automatic.

A page similar to the following appears on the right with a list of tests. The list variesdepending on your license and configuration. For a Tomcat standalone configuration,the Web Server tests may not appear.

The verification tool is supported only with Internet Explorer at this time, and you mayreceive errors if you use other browsers.



6. Review the test results and troubleshoot accordingly.

Additional verification tools are discussed in Troubleshooting Developer Studio on page 95.

Note: The WebFOCUS Administration Console does not have its own authenticationmechanism and by default, none is used. If you wish to secure the console, theIBIWFC_Authentication setting is under Configuration and Startup Parameters. See theWebFOCUS Security and Administration manual for more information. Setting authenticationto this console may require additional authentication when using Developer Studio.

Migrating From Developer Studio Version 4If you are upgrading from Developer Studio 5.2 or later, no migration is necessary.

In Developer Studio 4.3.x or 4.2.x (4), applications were controlled by a GFA file located inthe directory above the directory containing the application files. In Developer Studio 5, theGFA file is located in the same directory as its application files. Therefore, when upgradingfrom Developer Studio 4, you must use the Project Migration Tool to convert older applicationsfor use with Developer Studio 5.

If your APPROOT directory (drive:\ibi\apps by default) contains Developer Studio applicationsthat require migration, the first time Developer Studio opens, you are prompted to migratethem. You can also launch the Project Migration Tool from the Windows Start menu byselecting Programs, Information Builders, WebFOCUS 76 Developer Studio, WebFOCUSDeveloper Studio Utilities, and Project Migration Tool.

40 WebFOCUS

Migrating From Developer Studio Version 4

When you open the Project Migration Tool, it lists any GFA files for Developer Studio 4applications in the APPROOT directory.

If you have applications in a different directory, specify the directory by clicking the Browsebutton next to the Look for projects in field. Uncheck any applications that you do not wantto migrate, and then click the Migrate button to migrate the checked applications. The migrateutility updates the application files and places a new GFA file inside the application directory.


How to:

Create the Installation Parameters File

Launch a Silent Installation

After you are familiar with the Developer Studio installation, you can install in silent modeif you need to reinstall Developer Studio on several different machines. In a silent installation,dialog boxes do not appear to prompt you for parameters. Instead, you place the parametersin a text file that you specify when launching the silent installation. This is useful for siteswhere Developer Studio is installed on many developer machines.



To install in silent mode, you must first create a file containing your installation parameters.

Note: If you received the installation via a download rather than a CD, you need to run theinstallation and choose the option to keep the unpacked files on your computer. The silentinstallation must be run with the files on the CD or the files that are unpacked from adownloaded installation.

How to Create the Installation Parameters FileProcedure:

Create a file in a text editor with the options you wish to use for your installation. The followingtable explains the options. Place each option on its own line.

ExampleValueOption

-license 000000000

Should be followed by the 9-digit Developer Studiolicense.

-license

-installdir C:\Should be followed by the drive letter or locationwhere you wish to install the root ibi directory.Developer Studio components are installed into aroot ibi directory no matter what you enter. If youenter:

c:\ibi\

components are installed in:

c:\ibi\ibi\

-installdir

–noupgradeCan optionally appear if Developer Studio is alreadyinstalled and you do not want to upgrade it.

–noupgrade

-tomcatCan optionally appear to install Apache Tomcat 5with Developer Studio if it is not already installed.

-tomcat

42 WebFOCUS


ExampleValueOption

-config tcCan optionally appear to configure Apache Tomcatand Microsoft IIS. It should be followed by one ofthe following:

tc

Configures Tomcat standalone.

tc_iis

Configures Tomcat and IIS.

Tomcat or IIS must be installed to use this option.You can install Tomcat using the -tomcat option.

-config

-jdkupgrade onCan optionally appear to determine whether toinstall a Java SDK with Developer Studio. It shouldbe followed by one of the following:

on

The Java SDK included with Developer Studiois installed unless the exact SDK release isalready installed. This is the default if theoption does not appear.

off

No Java SDK is installed with Developer Studio.If Java SDK 1.4.1_03 or higher is not alreadyinstalled, the installation will not complete andan error messages will be available in the logfile.

-jdkupgrade

An example of an entire file is the following:

-license 000000000-installdir C:\-noupgrade-tomcat-config tc-jdkupgrade on



How to Launch a Silent InstallationProcedure:

1. Open a command prompt and navigate to the directory containing the setup.exe file forthe Developer Studio installation.

2. Enter the following:

setup -opt drive:\PATH_TO\optionsFile.txt

where:

drive:\PATH_TO\optionsFile.txt

Is the full path to the text file containing your installation options.

A log of the installation is provided for troubleshooting:

c:\wf_ds_76_inst_userID.log

This log contains important information about the installation process. If the log indicatesthat the installation did not complete, adjust the options in the file you used to installDeveloper Studio. In some cases, an incorrect option setting can prevent the installationfrom completing.

If you do not choose to have the installation configure Tomcat, you can manually configureWeb and application servers as explained in Configuring the Web Server and/or ApplicationServer on page 45.

44 WebFOCUS


WebFOCUS

Configuring the Web Server and/orApplication Server

3

Topics:The following topics explain how tomanually configure Web and/orapplication servers for stand-aloneProject-based development withDeveloper Studio.

Configuration Options

Configuring Apache Tomcat

Note: CGI and ISAPI are not supportedwith Developer Studio at this time.

Configuring Microsoft IIS

Configuring Microsoft IIS to Use theTomcat Connector (Plug-In)

Configuring Additional Web and/orApplication Servers


Configuration OptionsThis chapter is not necessary if any of the following apply:

This chapter is not needed if you chose the automatic configuration option during theDeveloper Studio installation and successfully ran the verification tool in InstallingDeveloper Studio on page 23. You can optionally review this information to understandthe configuration or proceed to Configuring the Local Reporting Server Security on page87.

This chapter is not needed if you installed Developer Studio on a machine whereWebFOCUS was already installed and configured. In this case, Developer Studio can usethe existing WebFOCUS configuration. Proceed to Configuring the Local Reporting ServerSecurity on page 87.

This chapter is not needed if you plan to perform only remote development or a networkinstallation. In this case, you must configure Developer Studio to access a WebFOCUSenvironment installed elsewhere. See Configuring the Local Reporting Server Security onpage 87 for information on connecting to WebFOCUS environments. See Configuring aNetwork Installation on page 65 for additional network installation steps.

This chapter is needed if a Web or application server is not configured or if you need totroubleshoot the configuration. Developer Studio requires a Web and/or application serverto perform standalone Project-based development and to process reports locally. Configurationsteps vary depending on which Web and/or application servers you use:

Apache Tomcat Stand Alone

Tomcat can be used as both the Web server and application server. If you choose thisoption, be aware that the default HTTP port for Tomcat is 8080 rather than 80. Thereforewhen calling Web server pages in a browser, you must use:

http://hostname:8080

rather than:

http://hostname

Manual configuration is described in Configuring Apache Tomcat on page 47.

Microsoft IIS and Apache Tomcat

Tomcat can be used as the application server while Microsoft IIS can be used as theWeb server. This requires two servers and the configuration of their communications.

Manual configuration is described in Configuring Apache Tomcat on page 47, ConfiguringMicrosoft IIS on page 53, and Configuring Microsoft IIS to Use the Tomcat Connector (Plug-In) on page 56.

46 WebFOCUS

Configuration Options

Other

Other Web and/or application servers, such as IBM WebSphere, can be manuallyconfigured as explained in Configuring Additional Web and/or Application Servers on page62.

Note: New Atlanta ServletExec ISAPI is not supported at this time.

For convenience, the term application server is used to refer to either a servlet container,J2EE Engine, or application server.


In this section:

Tomcat Configuration Overview

Configuring Tomcat

Additional Tomcat Configuration Options

The Developer Studio installation provided the option to install and configure Apache Tomcatfor you. If you chose this option and the verification tool ran successfully, you do not needto manually configure Tomcat. However, if you are not familiar with Tomcat, you may wishto review this section to understand the configuration process.

Note:

If Tomcat is not yet installed, install it at this time. You can install Tomcat by restartingthe Developer Studio installation program, choosing the Full Install option, choosing theApache Tomcat installation option, and deselecting the Developer Studio option.

Tomcat uses TCP ports 8080, 8009, and 8005 by default. If you need to change them,see Tomcat Ports on page 51.

If Developer Studio installs Tomcat, it increases the default Java VM memory options. Ifyou manually install Tomcat or need to troubleshoot memory issues, see Java MemoryIssues on page 96.

Tomcat Configuration OverviewTo configure Tomcat, you tell Tomcat where Developer Studio files are located and thecontexts in which to use them. For example, the WebFOCUS Web application is installedwith Developer Studio in:

drive:\ibi\DevStudio76\webapps\webfocus76


3. Configuring the Web Server and/or Application Server

Tomcat must know to serve files from the Web application when it receives a request forthe ibi_apps context path. For example:

http://localhost:8080/ibi_apps

Tomcat can be used as both a Web server and application server, so Tomcat can also servefiles outside of a Web application after it knows their location and context. On a traditionalWeb server you create aliases. With Tomcat, an alias is treated like a context root, evenwhen serving files outside of a Web application.

When using Tomcat as both Web and application server, the following contexts must becreated:

Directory (DocumentBase)Context (path)

drive:\ibi\DevStudio76\Webapps\webfocus76/ibi_apps

drive:\ibi\DevStudio76\ibi_html/ibi_html

drive:\ibi\apps/approot

When using Tomcat as the application server and IIS as the Web server, create only onecontext on Tomcat:

Directory (DocumentBase)Context (path)

drive:\ibi\DevStudio76\Webapps\webfocus76/ibi_apps

The ibi_html and approot contexts are then created as aliases (Virtual Directories) on IISand IIS is configured to send requests for ibi_apps to Tomcat.

Configuring Tomcat

How to:

Create Contexts for Apache Tomcat

Test the Tomcat Configuration

There are many ways to configure Tomcat. Information Builders recommends creating XMLfiles under TOMCAT_HOME\conf\Catalina\localhost. The Tomcat 5.5 Admin Tool is usefulfor debugging, but is not a stable environment for creating contexts. Creating XML files underTOMCAT_HOME\conf\Catalina\localhost works with both Tomcat 5.0 and Tomcat 5.5.

48 WebFOCUS


Note: In Tomcat 5.5, do not create contexts using the Manager tool. The Managed Toolcopies directories under Tomcat 5.5/webapps rather than creating the XML files that definecontexts.

How to Create Contexts for Apache TomcatProcedure:

1. Stop Tomcat from the Windows Services window by right-clicking Apache Tomcat andchoosing Stop.

2. Navigate to the following directory in Windows Explorer or My Computer:

C:\Program Files\Apache Software Foundation\Tomcat 5.5\conf\Catalina\localhost

This directory can contain XML files that define contexts. If the Developer Studioinstallation installed and configured Tomcat for you, the following file should appear todefine the ibi_apps context that deploys the webfocus76 directory:

ibi_apps.xml

If you are using Tomcat standalone, the follows should appear as well:

approot.xmlibi_html.xml

The XML files are named for the context root you would use to access the Web applicationand should have the following syntax:

<?xml version='1.0' encoding='utf-8'?><Context docBase="path_To_WebApplication" path="/contextRoot"></Context>

where:

path_To_WebApplication

Is the absolute path to the WAR file or directory you are deploying.

contextRoot

Is the context root.

Note: They can optionally contain additional information as explained in Tomcatdocumentation.

3. If the ibi_apps.xml file does not exist, create it using Notepad. For example:

<?xml version='1.0' encoding='utf-8'?><Context docBase="c:\ibi\DevStudio76\Webapps\webfocus76" path="/ibi_apps"></Context>

Be sure to specify the correct directory on your machine and change the context root ifyou are not using the default (ibi_apps).



4. If you are using Tomcat standalone and approot.xml does not exist, create it usingNotepad. For example:

<?xml version='1.0' encoding='utf-8'?><Context docBase="C:\ibi\apps" path="/approot"></Context>

Be sure to specify the correct directory on your machine.

5. If you are using Tomcat standalone and ibi_html.xml does not exist, create it usingNotepad. For example:

<?xml version='1.0' encoding='utf-8'?><Context docBase="c:\ibi\DevStudio76\ibi_html" path="/ibi_html"></Context>

Be sure to specify the correct directory on your machine.

Note: The ibi_bid context is no longer needed in WebFOCUS 7.6.

6. Restart Tomcat from the Services window.

How to Test the Tomcat ConfigurationProcedure:

1. Ensure Tomcat has been restarted.

2. Test the ibi_apps context by going to the following URL in a Web browser:


A page displaying information about the build should appear. If you receive an error, seeTroubleshooting Developer Studio on page 95.

3. If you created the ibi_html context, test it by going to the following URL in a Web browser:

http://localhost:8080/ibi_html/index.html

The WebFOCUS home page should appear.

Note: Until you start the WebFOCUS Reporting Server, you cannot actually run reportsfrom this page.

50 WebFOCUS


Additional Tomcat Configuration Options

How to:

Set Security for the Tomcat Web Tools

Reference:

Tomcat Ports

Reloading Web Applications

Additional Configuration Steps

You should be aware of how to secure the Administration and Manager tools, Tomcat's TCPports, and how to reload Web applications.

How to Set Security for the Tomcat Web ToolsProcedure:

You can secure the Tomcat Administration and Manager tools if you wish. By default, a userID "admin" is available and no password is needed to access these tools. If you wish to seta password, perform the following steps.

1. Open the following file in a text editor:

C:\Program Files\Apache Software Foundation\Tomcat 5.5\conf\tomcat-users.xml

2. Edit the admin line to specify a password. For example:

<user username="admin" password="xxxxxxx" roles="admin,manager"/>

The user IDs and passwords in this file have no relationship with WebFOCUS or operatingsystem user IDs.

3. Save and exit the file.

4. Restart Tomcat.

Tomcat PortsReference:

By default, Tomcat uses the three TCP ports listed below:

UseNameDefault Port

You access Tomcat in a Web browser using this port.For example:


HTTP ListenerPort

8080



UseNameDefault Port

Web servers can route servlet requests to Tomcat onthis port. The Tomcat connector (plug-in) for IIS usesthis port. Tomcat listens on this port even if no Webserver is connecting.

ConnectorPort

8009

Tomcat uses this port for internal operations and forshutting down.

ShutdownPort

8005

If these ports are not available or you wish to change them, do the following:

1. Open the following file in a text editor:

C:\Program Files\Apache Software Foundation\Tomcat 5.5\conf\server.xml

2. Search for the port numbers you wish to replace (8080, 8009, 8005) and replace themwith the ports you wish to use.


4. Restart Tomcat.

If you change defaults, substitute accordingly in procedures and examples. You also needto update Developer Studio's connection settings so it knows the correct Tomcat HTTP portif you change the default.

Reloading Web ApplicationsReference:

This is not a consideration if you just installed Tomcat with Developer Studio for the firsttime; only when installing a service pack or new release. When you upgrade Developer Studioor install a service pack, Tomcat must use the new Web application rather than cachedcopies of the old version.

If the expanded webfocus76 directory was deployed, the new Web applications shouldbe used automatically, but you should remove the following directory and restart Tomcat.

C:\Program Files\Apache Software Foundation\Tomcat 5.5\work\Catalina\localhost\ibi_apps

For a Tomcat standalone configuration, also remove the approot and ibi_html directories.

If you deploy the webfocus76.war file or your new release is located in a different directoryfrom the old release, remove the following, recreate the context, and restart Tomcat:

C:\Program Files\Apache Software Foundation\Tomcat 5.5\webapps\ibi_apps

C:\Program Files\Apache Software Foundation\Tomcat 5.5\work\Catalina\localhost\ibi_apps

C:\Program Files\Apache Software Foundation\Tomcat 5.5\conf\Catalina\localhost\ibi_apps.xml

52 WebFOCUS


For a Tomcat standalone configuration, remove the approot.xml and ibi_html.xml files aswell.

Additional Configuration StepsReference:

If you are using Tomcat as both a Web and application server, proceed to Configuring theLocal Reporting Server Security on page 87.

If you are using Tomcat as the application server and IIS as the Web server, configureIIS as explained in the next section.


In this section:

Configuring IIS Virtual Directories (Aliases)

Setting Permissions

This section only applies when using Microsoft IIS as your Web server.

IIS is a Web server and does not process Java on its own. Therefore, to run the WebFOCUSServlet, IIS should be used with Apache Tomcat or another application server. This documentassumes you are using Apache Tomcat. New Atlanta ServletExec ISAPI is not supported atthis time.

Configuration steps are the following:

1. Configure Tomcat as explained in Configuring Apache Tomcat on page 47.

2. Define aliases that map directories containing Developer Studio files to directories theWeb server can reference as explained in How to Confirm or Create Virtual Directories(Aliases) on page 54. IIS calls these mappings Virtual Directories.

3. Configure communications between IIS and Tomcat as explained in Configuring MicrosoftIIS to Use the Tomcat Connector (Plug-In) on page 56.

Configuring IIS Virtual Directories (Aliases)

How to:

Confirm or Create Virtual Directories (Aliases)

Developer Studio connectivity components and other Web based features sometimes runas part of the Web server. Therefore, IIS must be told the locations of Developer Studio filesand have sufficient access to those files.



Before configuring IIS, it is a good idea to restart it. You can start and stop IIS from theServices Window as explained in How to Start Apache Tomcat or Microsoft IIS on page 35.

How to Confirm or Create Virtual Directories (Aliases)Procedure:

1. Open the Internet Services Manager. You can access this from the Start menu byselecting Run and entering the following:

inetmgr

The Internet Information Services window appears when you press Enter.

2. Expand and select your hostname on the left side.

3. On the left, select the Web site you are using:

On Windows 2000 on the left, select Default Web Site or the site you are using.

On Windows XP and 2003 on the left, expand Web Sites and then select Default WebSite or the site you are using.

4. Confirm that the Name and Path columns of the following table appear on the right ofthe window:

PurposeAccessPathName

Directory containing Webbased front-endcomponents.

ReadOnly

drive:\ibi\DevStudio76\ibi_html

ibi_html

Directory where you storeapplication files.

ReadOnly

drive:\ibi\appsapproot

If the above names and paths appear, proceed to Setting Permissions on page 55.

If ibi_html or approot do not appear, you should add them.

5. To add ibi_html or approot, select the Default Web Site or site you are using forWebFOCUS, and then use the menu bar to select Action, New, and then Virtual Directory.

This launches the New Virtual Directory Wizard. Go through the wizard one time for eachvirtual directory you wish to create.

6. Click Next at the first panel.

7. Specify the alias name (approot or ibi_html) and click Next.

54 WebFOCUS


8. For the directory, browse to and select the directory for the alias. For example:

DirectoryPathAlias

drive:\ibi\DevStudio76\ibi_htmlibi_html

drive:\ibi\appsapproot

The window for setting permissions displays.

9. Leave the defaults when defining ibi_html or approot and click Next.

10. Click Finish.

11. Select the Default Web Site or site you are using for WebFOCUS, and then use the menubar to select Action, New, and then Virtual Directory.

Repeat the steps if you need to define another virtual directory. Your Web site must beselected so that the virtual directories become its subdirectories. After creating a virtualdirectory, ensure your site is selected and not the virtual directory you just created.

12. Restart IIS from the Services window.

Setting PermissionsTwo kinds of permissions issues are involved when using IIS:

IIS permissions determine what IIS is allowed to do. You can set this through the InternetServices Manager for the WebFOCUS aliases (virtual directories).

If the Developer Studio installation configures IIS for you, they should default correctly.However, on some Windows Servers, the ibi_html alias may require Scripts executablepermissions to serve .html files (though not .htm files).

NTFS permissions determine what each user ID is allowed to do through the file system.You can set this in Windows Explorer or My Computer by right-clicking a folder, choosingProperties, and clicking the Security tab. NTFS permissions take precedence over IISpermissions. If the user ID that IIS runs under does not have NTFS permissions to writeto a directory, then IIS cannot write to that directory.

IIS and Tomcat need access to the Developer Studio directories. However, when usingIIS with Apache Tomcat, you normally do not need to set NTFS permissions. IIS needsonly Read NTFS permissions, which it should have by default. Tomcat runs as the LocalSystem account, which automatically has full access. These defaults can be changed ifyou require.



If you need to set NTFS permissions, determine which user IDs require access to DeveloperStudio directories. Then set NTFS permissions to allow those user IDs full access.

Configuring Microsoft IIS to Use the Tomcat Connector (Plug-In)

In this section:

Installing and Configuring the Tomcat Connector (Plug-In) for IIS

Verifying the Configuration

To use Tomcat as the application server, while using Microsoft IIS as the Web server, youmust do the following if the installation did not do it for you:

1. On Tomcat, deploy the WebFOCUS Web application by creating the ibi_apps context asexplained in Configuring Tomcat on page 48.

2. On IIS, set the /ibi_html and /approot aliases (virtual directories) as explained inConfiguring IIS Virtual Directories (Aliases) on page 53.

3. Install and configure the Tomcat plug-in (Jakarta Tomcat Connector JK1.2 for IIS) asexplained in this section.

Note:

The Tomcat Connector (plug-in) for IIS is not supported on 64 bit Windows systems.

If ServletExec ISAPI is installed, stop IIS, uninstall it, and reboot. If this is not possible,you can disable the filter. To disable the filter, open the Internet Service Manager,right-click your Web site, choose Properties, and remove the ISAPI filter from the ISAPIFilters tab. If no filter appears, move the ServletExec_ISAPI.dll file out of theC:\Inetpub\Scripts directory.

56 WebFOCUS


Installing and Configuring the Tomcat Connector (Plug-In) for IIS

How to:

Configure the Redirection for Developer Studio

Configure a Windows 2003 Server to Use the Tomcat Plug-In

Reference:

Tomcat Connector (Plug-In) Installation

A simple installation program installs the Tomcat plug-in and configures the default IIS Website to use it. After installing the plug-in, you can change which IIS Web sites use the plug-in if you wish. If you chose to configure the Tomcat plug-in when installing Developer Studio,the plug-in should be installed in:


The installation program is self explanatory and prompts you for the location to install theconnector.

Note: If you manually install the connector a workers.properties.minimal file appears insteadof a workers.properties file. The files are the same except for their names.

Tomcat Connector (Plug-In) InstallationReference:

The Developer Studio or Tomcat Connector installation program performed the followingsteps. You normally do not need to perform these steps manually. However, you should beaware of them in case you need to troubleshoot. In addition, if you wish to change which IISWeb site uses the plug-in, you may need to perform some manual configurations.

1. The plug-in is installed by default in the following location:


2. The following table shows the registry settings that are created under:

HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\ Jakarta Isapi Redirector\1.0

Value DataValue Name

/jakarta/isapi_redirect.dllextension_uri

C:\Program Files\Apache Software Foundation\Jakarta

Isapi Redirector\log\isapi_redirect.log

log_file





Isapi Redirector\conf\workers.properties

worker_file


Isapi Redirector\conf\uriworkermap.properties

worker_mount_file


/jakarta/isapi_redirect.dllextension_uri


Isapi Redirector\log\isapi_redirect.log

log_file


Isapi Redirector\conf\workers.properties

worker_file


Isapi Redirector\conf\uriworkermap.properties

worker_mount_file

The following image shows those settings in the registry.

58 WebFOCUS


3. A Virtual Directory (alias) with scripts and executables permissions is created under thedefault IIS Web site.

PathAlias

C:\Program Files\Apache Software Foundation\Jakarta Isapi Redirector\bin\

/jakarta

If you wish to use the plug-in with a different Web site, create this Virtual Directory underthat site as well or instead.

4. The following file is added to the default Web site as an ISAPI Filter.

C:\Program Files\Apache Software Foundation\Jakarta Isapi Redirector\bin\isapi_redirect.dll

In some environments, WebFOCUS does not successfully add this and you must do itmanually. You can confirm or add this by right-clicking your Web site in the InternetServices Manager, choosing Properties, and selecting the ISAPI Filters tab. If the jakartafilter does not appear as it does in the following image, click Add and add it.

If you wish to use the plug-in with a different Web site, create this filter under that siteas well or instead.



Note: If Developer Studio installed the Tomcat Connector, you can manually uninstall it byremoving the registry settings, ISAPI Filter, Virtual Directory, and Jakarta Isapi Redirectordirectory. If you ran the Tomcat Connector installation utility, you can uninstall it usingAdd/Remove Programs in the Control Panel.

How to Configure the Redirection for Developer StudioProcedure:

The following file installed with the Tomcat Connector tells IIS when to route requests toTomcat.

C:\Program Files\Apache Software Foundation\Jakarta Isapi Redirector\conf\uriworkermap.properties

1. In a text editor, open uriworkermap.properties.

Tip: If this file appears odd in Notepad use WordPad. However, if you use WordPadensure the file is saved as Text.

2. Confirm that the following line appears and manually add it if it does not appear:

/ibi_apps/*=ajp13w

This line tells IIS to send requests for ibi_apps to Tomcat. If you changed the defaultcontext root, substitute accordingly. The /ibi_apps/* context can only appear once.

3. Save and exit the editor.

4. Restart IIS. Any changes require restarting IIS.

Note: The workers.properties file tells IIS where the Tomcat host and port are located. Thisis a different port (8009) than the port used for HTTP (8080). If you changed the defaultports, edit this file accordingly.

How to Configure a Windows 2003 Server to Use the Tomcat Plug-InProcedure:

If you are not using Windows 2003 Server, you can proceed to Verifying the Configurationon page 61.

On Windows 2003 Server, you must create a Web Services Extension for the Tomcat plug-in.

1. Open the Internet Services Manager. You can access this from the Start menu byselecting Run and typing the following:

inetmgr

The Internet Information Services window appears when you press Enter.

2. Expand your hostname on the left, right-click Web Service Extensions, and select Add anew Web service extension.

60 WebFOCUS


3. In the Extension name field, type:

jakarta

4. Check Set extension status to allow.

5. Click Add and browse to select the isapi_redirect.dll file. For example:

C:\Program Files\Apache Software Foundation\Jakarta Isapi Redirector\bin\isapi_redirect.dll

6. Click Open and then OK to close windows and return to the main Internet ServicesManager window.

7. Ensure the Jakarta-Tomcat Web service extension status is set to allow.

8. Restart IIS.

Verifying the Configuration

How to:

Run Test Calls

After configuring the Tomcat plug-in, ensure that IIS can route requests to Tomcat.

How to Run Test CallsProcedure:

1. If they are not started, start the following:

IIS

Tomcat

2. Ensure the ibi_apps context is created on Tomcat by typing the following URL:


A page displaying information about the build should display. If there is a broken image,do not be concerned. If nothing displays, ensure that Tomcat is started and that youcreated this context as explained in Configuring Apache Tomcat on page 47. If you receivean error, see Troubleshooting Developer Studio on page 95.

3. Ensure IIS routes a request for ibi_apps to Tomcat by typing the following URL:

http://localhost/ibi_apps/about.jsp

The same page should display without the broken image. If IIS is not on port 80,substitute accordingly.



If you receive an error:

Ensure that all steps have been performed to configure the connector/plug-in.

Ensure that both IIS and Tomcat are started and try restarting them.

Ensure that "/ibi_apps/*" appears only once in the uriworkermap.properties file.

Ensure that ServletExec ISAPI is not installed or is disabled.

4. Proceed to Configuring the Local Reporting Server Security on page 87.

Configuring Additional Web and/or Application Servers

In this section:

Configuring the Web Server

Configuring the Application Server

Configuring Developer Studio

This section explains how to manually configure other Web and/or application servers.

Configuring the Web Server

How to:

Configure Aliases

Developer Studio connectivity components and other Web based features sometimes runas part of the Web server. Therefore, your Web server must be told the locations of DeveloperStudio files. To enable this, you define aliases that map directories containing DeveloperStudio files to directories the Web server can reference.

How to Configure AliasesProcedure:

1. Review your Web server documentation and define the following aliases:

AccessPathName

Readdrive:\ibi\DevStudio76\ibi_htmlibi_html

Readdrive:\ibi\appsapproot

62 WebFOCUS


2. To use CGI, define the following script alias for the directory containing the WebFOCUSCGI executable:

DirectoryAlias (Prefix)

drive:\ibi\DevStudio76\srv76\wfs\web\cgi/cgi-bin/ibi_cgi

Note: For Apache based Web servers, the /cgi-bin/ibi_cgi/ ScriptAlias must precedethe generic /cgi-bin/ ScriptAlias.

Configuring the Application Server

How to:

Configure the Application Server

WebFOCUS Java servlets are provided as a Web application installed as the following:

drive:\ibi\DevStudio76\webapps\webfocus76.war

The Web application is also provided as an expanded directory:

drive:\ibi\DevStudio76\webapps\webfocus76\

You can deploy either the webfocus76.war file or the webfocus76 directory depending onyour application server.

To run the servlets, you need either a Web server with native servlet support, a Web serverwith a servlet engine plug-in (for example, ServletExec), or a Web application server (forexample, WebSphere

®, WebLogic

®). Servlet support must meet the J2EE 1.2 Web Container,

JSP 1.1, and Servlet API 2.2 specifications.

How to Configure the Application ServerProcedure:

Configuration procedures vary depending on your Web server, application server, or servletcontainer. Review the third party documentation for information on how to deploy Webapplications.

1. Deploy the WebFOCUS Web application using the ibi_apps context root:

URL Context PathDoc base or location

/ibi_appsdrive:\ibi\WebFOCUS76\webapps\webfocus76.war



2. If necessary, ensure your Web server can route servlet requests to the application server.

3. If necessary, restart your Web and/or application servers.

Configuring Developer StudioDeveloper Studio is supported with all Web and/or application servers supported withWebFOCUS. However, Developer Studio settings default for Tomcat and/or IIS. Therefore,if you are not using IIS or Tomcat, be aware of the following:

Developer Studio attempts to call the Web server on either port 80 or port 8080. If yourWeb server listens on a different port, set the port for the WebFOCUS Environment asexplained in Configuring the Local Reporting Server Security on page 87.

By default, Developer Studio attempts to connect to the local Web server using Servletcalls. To use CGI, review the information on WebFOCUS environments in Configuring theLocal Reporting Server Security on page 87 to switch the WebFOCUS Client Path parameterfor the localhost WebFOCUS environment. CGI and ISAPI are not supported with DeveloperStudio at this time.

By default, Developer Studio attempts to start IIS when you start Developer Studio. Youcan change this behavior as explained in Configuring the Local Reporting Server Securityon page 87.

64 WebFOCUS


WebFOCUS

Configuring a Network InstallationATopics:

The following topics explain a networkinstallation of Developer Studio.

You must install Developer Studio withthe correct license to use a networkinstallation.

Network Installation Steps



In this section:

Ensuring Requirements Are Met



Setting Up Access to the Network Installation

Installing Developer Studio Network Shortcuts

Launching Developer Studio

Customizing WebFOCUS Environments

Accessing Multiple Networked Developer Studio Installations

Limiting Access to Developer Studio

Accessing the Developer Studio Help System

Creating Developer Studio Traces From a Client PC in Developer Studio Network Edition

This section explains a network installation of WebFOCUS Developer Studio. In a networkinstallation, Developer Studio is installed on a single shared machine, rather than eachdeveloper's desktop. Developers then launch Developer Studio on their desktops by executingfiles that have been installed on the shared machine. This simplifies administration,installation, and upgrading and it allows all developers to use a common pre-configuredenvironment.

A network installation of Developer Studio does not include full WebFOCUS Client connectivity.After installing Developer Studio, you must configure it to access a WebFOCUS environmentsomewhere on your network. Developer Studio then uses the Web server configuration,application server configuration, WebFOCUS Client connectivity, and WebFOCUS ReportingServer of that WebFOCUS environment.

A Developer Studio network installation involves the following steps:

1. Ensuring Requirements Are Met on page 67.

2. Installing Developer Studio on page 68.

3. Configuring Developer Studio on page 68.

4. Setting Up Access to the Network Installation on page 71.

5. Installing Developer Studio Network Shortcuts on page 77.

6. Launching Developer Studio on page 78.

66 WebFOCUS


Ensuring Requirements Are MetA network installation of Developer Studio can consist of three types of machines. Eachmachine has its own requirements.

WebFOCUS Machine Requirements

WebFOCUS requirements and installation steps are provided in the WebFOCUS andReportCaster Installation and Configuration manual for your platform. To use Project-baseddevelopment, the WebFOCUS environment must store both server files (FEX, MAS, ACX)and client files (HTML, GIF, CSS) in the same directory for each project. This meansWebFOCUS Client and the WebFOCUS Reporting Server must use the same APPROOTdirectory on the same machine. For example:

C:\ibi\apps

Note: The release of WebFOCUS must be the same release number as Developer Studio.

Developer Studio (Shared) Machine Requirements

Developer Studio can be installed on the same machine as WebFOCUS or on a separatemachine. The requirements for a network installation of Developer Studio are the sameas those of a non-networked installation. See Installing Developer Studio on page 23 forrequirements.

Note: You must provide a license for a network edition.

Since this machine will be accessed by multiple users over the network, you should usea machine that supports multiple connections and frequent network access.

Developer Studio End User (Remote) Machine Requirements

Machines from which you run Developer Studio off the network, should meet the followingrequirements:

Windows 2000, XP, or 2003 Server and Professional Editions. Windows 2000must have Service Pack 2 or higher.

Internet Explorer 6.0 or higher. Internet Explorer components are required forDeveloper Studio. If possible, upgrade to the most recent version of Internet Explorerbefore accessing Developer Studio.

Java 2 JDK 1.4.2 and higher. A Java JDK 1.4.1 or higher is required for certainfeatures. Using JDK 1.4.2_06 or higher is recommended.

Adobe Acrobat Reader 6.0 and higher. Acrobat Reader 6.0 is certified to view PDFreports generated by Developer Studio.

Administrator Rights. Administrator rights are required when first configuring accessto Developer Studio.


A. Configuring a Network Installation

Installing Developer StudioInstall Developer Studio as explained in Installing Developer Studio on page 23. Be awarethat when providing a network installation license, you will not have the option to install orconfigure Tomcat or other supported configurations.

You must install using the proper license code for a network installation.


How to:

Define a WebFOCUS Environment

To configure a network installation of Developer Studio, you must set up access to instancesof WebFOCUS that are installed on your network. You do this by defining WebFOCUSenvironments.

How to Define a WebFOCUS EnvironmentProcedure:

1. If WebFOCUS and Developer Studio are on the same machine, start the WebFOCUSReporting Server and ensure the Web and/or application servers are started.

2. Start Developer Studio from the Start menu by selecting Programs, Information Builders,WebFOCUS 76 Developer Studio, and WebFOCUS Developer Studio.

3. If prompted to log on, log on to the WebFOCUS Reporting Server.

4. If the Developer Studio Explorer appears, click the File menu and then Show Environmentsto display the Environments List. In some environments, the Environments List appearsby default.

68 WebFOCUS


The Environments List lets you define connections to WebFOCUS environments.

The Environments List shows all WebFOCUS environments defined for Developer Studio.If you had previously installed Developer Studio, WebFOCUS environments may alreadybe defined. Otherwise, only the localhost environment displays.

Note: If you previously set up this machine for a Developer Studio network installation,select your development environment and click Set Development Environment. Then clickOK and restart Developer Studio.

5. Select localhost and click Properties to edit the default settings.



The WebFOCUS Environment Properties window opens.

6. Change the Description field to a name end users should see when they launch DeveloperStudio from remote machines. The name localhost will be misleading since they will beon their local machines.

7. Change the Host Name and port to access the Web server where WebFOCUS isconfigured. Do not use "localhost" for the hostname even if WebFOCUS is installed onthe same machine as Developer Studio. When end user's launch Developer Studio,localhost will resolve to the end user's machine and not the Developer Studio machine.

70 WebFOCUS


8. Click through the panes of the WebFOCUS Environment Properties window to changeany default options that are customized in your environment.

For additional information on defining environments, see Configuring the Local ReportingServer Security on page 87.

9. Click OK when you have set up the default environment.

If you wish to define additional WebFOCUS environments, click Add on the EnvironmentsList.

10. Click OK on the Environments List when you have defined all your environments.

The Developer Studio Explorer opens.

11. If prompted to log on, log on to the WebFOCUS Reporting Server.

12. Ensure that the Developer Studio Explorer functions properly and that your WebFOCUSenvironments are accessible.

13. Stop and start the product again to ensure that you can reconnect to the environmentand to confirm operability.

Note: The WebFOCUS Reporting Server in the WebFOCUS environment should not be theWebFOCUS Reporting Server installed as part of Developer Studio. The WebFOCUS ReportingServer installed as part of Developer Studio supports a very limited number of users (agents)at one time.

Setting Up Access to the Network Installation

How to:

Set Up Network Shares

Copy the WebFOCUS Environments File (wfscom.xml)

Configure the Network Settings

For developers to run Developer Studio off the network, you must do the following on theDeveloper Studio machine:

1. How to Set Up Network Shares on page 72.

2. How to Copy the WebFOCUS Environments File (wfscom.xml) on page 74.

3. How to Configure the Network Settings on page 75.



How to Set Up Network SharesProcedure:

You must set up two network shares before launching Developer Studio from another machine.

1. Turn the ibi directory where Developer Studio is installed into a network share. If this isnot practical for security reasons, then turn the DevStudio76 directory into a networkshare (if the share name is different from ibi, ensure the new share name is used inthe runfocshell.dat configuration file, as described in How to Configure the NetworkSettings on page 75):

a. Open Windows Explorer or My Computer on the Developer Studio machine.

b. Navigate to and right-click the ibi directory.

c. Choose Properties.

d. Select the Sharing tab.

e. Select Share this folder.

72 WebFOCUS


f. Click the Security tab and set permissions for the ibi share directory to Read &Execute and set permissions for the Developer Studio temp folder(install_directory\ibi\DevStudionn\temp) to Write access.

where:

install_directory

Is the directory in which Developer Studio is installed.

nn

Is the Developer Studio release number.

g. Grant access to the share locations for users accessing the network install. Youcan add users individually or you can add users to a group. A group is easier tomaintain, and you can grant the required privileges to the group.

h. Click OK.

2. Turn the Java JDK directory into a network share named java:

a. Open Windows Explorer or My Computer on the Developer Studio machine.

b. Navigate to and right-click the Java JDK directory. For example, one of the following:

C:\Program Files\Java\jdk1.5.0_09

C:\j2sdk1.4.2_10

c. Choose Properties.

d. Select the Sharing tab.

e. Select Share this folder.



f. In the Share name field, type:

java

If the share name is different from java, ensure the new share name is used in therunfocshell.dat configuration file, as described in How to Configure the NetworkSettings on page 75.

g. Click the Security tab and set permissions for the java directory to Read & Execute.

h. Grant access to the share locations for users accessing the network install. Youcan add users individually or you can add users to a group. A group is easier tomaintain, and you can grant the required privileges to the group.

i. Click OK.

How to Copy the WebFOCUS Environments File (wfscom.xml)Procedure:

Copy the WebFOCUS environment settings (wfscom.xml) into the DevStudio76\bin directoryso they are available to remote Developer Studio users.

74 WebFOCUS


When you define WebFOCUS environments, settings are stored in the following file:

drive:\Documents and Settings\userID\Application Data\Information Builders\wfscom.xml

where:

userID

Is the user ID logged on to Windows.

Note: This file and directory may not be visible by default. To see this directory, open WindowsExplorer, click Tools, choose Folder Options, and select the View tab. Then select Showhidden files and folders and click OK.

For remote machines to access the wfscom.xml file, you must copy it to a shared directory.The default location to use is:

drive:\ibi\DevStudio76\bin

When running Developer Studio off the network, a developer can use settings in this file orsettings stored on the developer's machine. The first time Developer Studio is run off thenetwork, the settings in this file are used. When settings in this file are used, this wfscom.xmlfile is placed in the end user's /Application Data/Information Builders/ directory on theremote machine each time Developer Studio is run off the network. If all developers use thesettings in this file, they always see the same WebFOCUS environments.

Caution:

If a previous copy of wfscom.xml or wfscom.wfs is on a remote user's machine, it isoverwritten.

If a remote user changes WebFOCUS environment settings while accessing DeveloperStudio from the network, those changes are only saved to the end user's machine. Theywill not be available to other users. They will also be overwritten the next time DeveloperStudio is launched, unless the user chooses not to update the environments from thenetwork as explained in Customizing WebFOCUS Environments on page 79.

To change WebFOCUS environment settings for all users, you must change them on theshared Developer Studio machine and not from a remote machine. Then, you must recopythe wfscom.xml file to the DevStudio76\bin directory so it is available when DeveloperStudio is run from a remote machine.

In Developer Studio 5.3 and earlier, wfscom.xml was named wfscom.wfs.

How to Configure the Network SettingsProcedure:

Settings for when Developer Studio is launched off the network are in the following file:

drive:\ibi\DevStudio76\bin\runfocshell.dat



You must edit this file before launching Developer Studio from another machine.

1. Open the runfocshell.dat file in a text editor such as Notepad.

2. Find the following line:

REGSTRING:LastUsedServer=Name to be supplied by Administrator

3. Change this line to specify the name of the default WebFOCUS environment. For example:

REGSTRING:LastUsedServer=WFEnvironment

You should have set up this environment as explained in How to Define a WebFOCUSEnvironment on page 68.

4. Ensure that the correct hostname, share name, and UNC directory path appears foraccessing the DevStudio76 directory. The hostname is set by the install, but you shouldconfirm it and ensure the share name is correct. Several lines contain this. For example:

WFSCOM:\\hostname\Ibi\DevStudio76\bin\wfscom.xmlSHLPATH:\\hostname\Ibi\DevStudio76\bin

If the hostname is incorrect or you changed the share name, update all lines where thehostname appears.

Be aware that the WFSCOM value specifies where remote machines look for thewfscom.xml file. You can change the name and location of this file if needed, but thefile name must end in .xml. The file specified is copied to a remote user's /ApplicationData/Information Builders/ directory on the remote machine. The file name on theremote machine will always be wfscom.xml regardless of the file specified by the WFSCOMvalue.

5. Ensure that the correct hostname, share name, and UNC directory path appears foraccessing the shared Java directory you set up in How to Set Up Network Shares on page72. For example:

REGSTRING:IBIJAVAPATH=\\hostname\java\jre\bin\javaw -classpath \\hostname\java\jre\lib\rt.jar;"\\hostname\Ibi\DevStudio76\ibi_html\javaassist\IBIGraphEditorFrame.jar" IBIGraphEditorFrame hold.htm "\\hostname\Ibi\DevStudio76" \\hostname\Ibi\DevStudio76\temp


Most of the settings in this file are created by the installation and should not be editedunless directed by Customer Support.

Warning: The DLL and OCX files listed in runfocshell.dat are loaded on remote machineswhen Developer Studio is loaded on those machines.

76 WebFOCUS


Installing Developer Studio Network Shortcuts

How to:

Install Developer Studio Network Shortcuts

An installation program is provided to create shortcuts to launch Developer Studio. Sinceno disk space is needed on the remote machine, this is referred to as a Zero FootprintWebFOCUS Developer Studio deployment.

Note: A Java JDK must be installed and you should be an administrator to the remotemachine.

How to Install Developer Studio Network ShortcutsProcedure:

To install shortcuts, perform the following on machines from which you wish to run DeveloperStudio off the network:

1. Open Windows Explorer or My Computer on the remote machine.

2. In the Address bar, type the hostname of the machine where Developer Studio is installedusing the Universal Naming Convention (UNC). This has the form:

\\hostname

where:

hostname

Is the hostname or IP Address of the machine where Developer Studio is installed.

You should see a list of shared directories including the ibi and java shared directoriesyou created.

3. Navigate the shared directories to:

\\hostname\ibi\DevStudio76\Utilities\Local_setup

4. Run the setup.exe application to install Developer Studio shortcuts.

The installation wizard launches and a Welcome window appears.

5. Click Next at the Welcome window.

You are prompted to create shortcuts.

6. Select which shortcuts to create and click Next.

Shortcuts are created.

7. Click Finish.



Note: To remove the shortcuts from the remote machine, use the Add/Remove Programsoption in the Windows Control Panel. The shortcuts appear as Zero-Footprint WebFOCUSDeveloper Studio. Be aware that this does not remove the registry settings or files describedin Network Developer Studio Settings on Remote Machines on page 78.

Launching Developer Studio

Reference:

Network Developer Studio Settings on Remote Machines

After installing the Developer Studio shortcuts, you can start Developer Studio off the networkby selecting Programs from the Start menu, and then Zero-Footprint WebFOCUS DeveloperStudio.

If the WebFOCUS Reporting Server runs with security OPSYS, you may be prompted to logon.

If you receive an error that says, "Sorry same demo was reinstalled," ensure you haveadministrator access to the desktop where you wish to run Developer Studio.

If you receive other errors, review the steps in Setting Up Access to the Network Installationon page 71 and ensure WFSCOM is defined correctly in runfocshell.dat.

Network Developer Studio Settings on Remote MachinesReference:

The first time you launch Developer Studio on a remote machine, the wfscom.xml file iscopied from the shared networked machine to the remote machine. The file is placed onthe remote machine in:

drive:\Documentsand Settings\userID\Application Data\Information Builders\wfscom.xml

where:

userID


Other files are also created in this directory. This directory may not be visible by default. Tosee this directory, open Windows Explorer, click Tools, choose Folder Options, and selectthe View tab. Then select Show hidden files and folders and click OK.

When you launch Developer Studio on a remote machine, registry settings are created under:

HKEY_LOCAL_MACHINE\SOFTWARE\Information Builders

HKEY_CURRENT_USER\SOFTWARE\Information Builders

78 WebFOCUS


In addition, DLL and OCX files listed in the \\hostname\ibi\DevStudio76\bin\runfocshell.datfile are loaded.

Customizing WebFOCUS EnvironmentsThere are two ways to handle WebFOCUS environment settings when running DeveloperStudio off the network. Developers can use the common settings on the network or usesettings specific to the developer's machine.

Option 1: Use the common WebFOCUS environment settings on the network (default).

With this option, whenever a developer launches Developer Studio, the wfscom.xml fileon the network installation is copied to the developer's machine from the followinglocation.

\\hostname\ibi\DevStudio76\bin\wfscom.xml

where:

hostname


This means all developers who launch Developer Studio from this network location usethe same environment settings. It also means that any WebFOCUS environment settingsthat developers change on their machines will not appear the next time they launchDeveloper Studio.

Option 2: Use customized WebFOCUS environment settings on a developer's localmachine.

With this option, the first time a developer launches Developer Studio, the wfscom.xmlfile is copied from the network to the developer's machine. However, after DeveloperStudio is started on the developer's machine, you can allow the developer to prevent thewfscom.xml file from being copied over in the future. By default, developers have theoption to choose whether to copy over wfscom.xml or not.

On a developer's machine, after Developer Studio has started:

1. Click Windows on the menu bar.

2. Click Options.

3. On the General tab, under Other Settings, uncheck Remote Update Server Environmentfrom Network.

This creates a registry setting on that machine that tells Developer Studio not to copyover wfscom.xml when Developer Studio is launched from the network.



You can control whether the Remote Update Server Environment from Network appears andwhether wfscom.xml is automatically copied by editing the runfocshell.dat file. This file wasintroduced in How to Configure the Network Settings on page 75. The runfocshell.dat filespecifies registry entries that great created on developer machines. The registry entries arecreated each time a developer launches Developer Studio off the network and will overwriteany previous entries.

By default the following lines appear:

REGISTRY:HKEY_CURRENT_USER\SOFTWARE\Information Builders\ DeveloperStudio

REGDWORD:IsRemote=1

With these lines, wfscom.xml is copied and developers can choose whether or not tocontinue copying the file in the future.

You can choose not to show the option by changing the lines to:

REGISTRY:HKEY_CURRENT_USER\SOFTWARE\Information Builders\DeveloperStudio

REGDWORD:IsRemote=0

With these lines, wfscom.xml is always copied and developers do not have the optionto change this behavior.

You can add the following line if you want to force the copying of wfscom.xml regardless ofwhat a developer has chosen in the past:


REGDWORD:IsRemote=0 REGDWORD:BypassWFSUpdate=0

With these lines, wfscom.xml is always copied, even if a developer has chosen not tocopy it in the past. This is a good way to force all developers to use a new version ofwfscom.xml if you make a major change in the environment settings.

If you never want wfscom.xml to be copied from the network, use the following line:


REGDWORD:IsRemote=0 REGDWORD:BypassWFSUpdate=1

With these lines wfscom.xml is never copied and developers do not have the option tochange this.

Accessing Multiple Networked Developer Studio InstallationsThe shortcuts provide an easy way to run Developer Studio off the network. However, installingthe shortcuts is not required. You can manually run Developer Studio off the network byexecuting the following file:

\\hostname\ibi\DevStudio\bin\DevStudioLaunch.exe

80 WebFOCUS


where:

hostname


When this is launched, files and registry settings are created as described in NetworkDeveloper Studio Settings on Remote Machines on page 78.

If developers need to launch Developer Studio from multiple machines, you can create anHTML page containing links that point to the appropriate DevStudioLaunch.exe file of eachnetwork install.

Limiting Access to Developer StudioThere are several ways to limit access to Developer Studio.

You can restrict access to the file system of the Developer Studio machine by settingNTFS permissions on the shared directory.

or

You can specify which user IDs can run Developer Studio by editing the following file onthe Developer Studio machine:

drive:\ibi\DevStudio76\bin\devstdpw.dat

By default, this file contains an * indicating that any user ID can run Developer Studio.If you wish to restrict which user IDs can run Developer Studio, remove the *. Then,specify each user ID that is allowed to run Developer Studio. Each user ID should beentered on a single line (one line per user ID). These are the user IDs used to log on toWindows. This file is case-sensitive. Do not enter the domain as part of your user ID.

Accessing the Developer Studio Help SystemOn some machines, the Developer Studio help system may not be accessible when runningDeveloper Studio off the network. This is due to a Microsoft security change that takes placewhen you apply certain Windows service packs, as explained in:

http://support.microsoft.com/kb/896358http://support.microsoft.com/kb/896054

If you cannot access the help system on certain machines, you can create registry entrieson those machines that allow Windows to access the help system. One way to do this is to:

1. Create a text file containing:

REGEDIT4[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\HTMLHelp][HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\HTMLHelp\1.x\ItssRestrictions]"MaxAllowedZone"=dword:00000001



2. Save this file as chm.reg.

3. Place the chm.reg file on the machine that cannot access the help system or on a networklocation that is accessible to that machine.

4. On the machine that cannot access the help system, use Windows Explorer or MyComputer to navigate to and right-click the chm.reg file.

5. Choose Merge.

6. Close Developer Studio if it is open.

The required values are added to the registry.

If you still cannot access the help system, edit the registry and try setting the MaxAllowedZonevalue to 4. (If you do this through the text file use dword:00000004.) The MaxAllowedZonevalues are discussed in:

http://support.microsoft.com/kb/896054

Creating Developer Studio Traces From a Client PC in Developer Studio Network EditionFor the network version of Developer Studio, the Developer Studio trace utility can be usedto trace requests from a client PC. To accomplish this, copy the Developer Studiocommunications layer trace utility (install_directory\Devstudio71\bin\wfscomtrace.exe) fromthe network PC to any location on the client PC. Run this utility prior to performing the taskthat is having issues and needs to be analyzed by IBI. From the trace utility, enable tracesand specify location of trace files.

82 WebFOCUS


WebFOCUS

Enabling WebFOCUS Quick DataBTopics:

The following topics explain how toenable WebFOCUS Quick Data.

Configuring WebFOCUS Quick Data



How to:

Configure the WebFOCUS Quick Data Excel Add-In

The Developer Studio installation places the WebFOCUS Quick Data Add-In in the properlocation so that it is detected by Excel. After the installation is complete, you must openMicrosoft Excel and add the Add-In to your Excel configuration.

How to Configure the WebFOCUS Quick Data Excel Add-InProcedure:

Ensure that you have properly installed Developer Studio and verified its functionality.

1. Launch Microsoft Excel.

2. Select Tools, then Add-Ins.

The Add-Ins dialog box appears. WebFOCUS Quick Data should be listed.

3. Select WebFOCUS Quick Data and click OK.

84 WebFOCUS


A new menu, called WebFOCUS, is enabled in Excel, as shown in the following image.

4. From the WebFOCUS menu, select Create Query to start building queries.

The Web Server Connection dialog box appears.

a. Provide the WebFOCUS Reporting Server URL.

b. If you need to provide a custom alias, click Advanced and edit as appropriate, thenclick OK.


B. Enabling WebFOCUS Quick Data

5. Click Next.

Note: If the Reporting Server is running with security on, you are prompted to log in.

A list of available master files appears.

6. Select a file, then click Finish.

Note: An error message appears if your environment is not properly licensed.

86 WebFOCUS


WebFOCUS

Configuring the Local Reporting ServerSecurity

CTopics:

The following topics explain how toconfigure the Developer Studio ReportingServer to run with security. This appliesonly for the Developer Studio Edition. Allother editions do not use a localReporting Server; instead, they requirea remote WebFOCUS environment anduse the Reporting Server(s) configuredwith that environment.

WebFOCUS Reporting Server Securityand User IDs


WebFOCUS Reporting Server Security and User IDs

In this section:

Configuring WebFOCUS Reporting Server Security and User IDs

Running the Server as a Service With Security OFF

By default, the WebFOCUS Reporting Server installed with Developer Studio can only bestarted by the user who installed it. In addition, the WebFOCUS Reporting Server is notenabled by default to run with security. For use with Developer Studio, this is sufficientbecause Developer Studio starts the WebFOCUS Reporting Server with security OFF. Thisserver is used by a developer for local standalone development (not to be shared by otherdevelopers) and it is not licensed for group development.

Configuring WebFOCUS Reporting Server Security and User IDs

How to:

Set Server Security and User IDs

You must configure server security if either of the following apply:

Users that did not install Developer Studio log on to the Windows machine and useDeveloper Studio.

The WebFOCUS Reporting Server stores a list of user IDs that the server recognizes asserver administrators. To start the WebFOCUS Reporting Server in any security mode,you must be logged on to Windows as a user ID that the server recognizes as anadministrator. By default, the server only recognizes the user ID that was used when youinstalled Developer Studio. To start the server as a different ID, you must add additionaluser IDs through the Reporting Server Console.

Note: If a user that did not install Developer Studio needs to run Developer Studio, thatuser should also execute drive:\ibi\DevStudio76\Utilities\Import_reg.bat.

You wish to run the WebFOCUS Reporting Server with security OPSYS.

The WebFOCUS Reporting Server can encrypt and store passwords for administrator userIDs. To start with security OFF, the passwords are not required. However, to start withsecurity OPSYS, the server must know both the Windows user ID and its password. Bydefault, the WebFOCUS Reporting Server does not know any passwords and thereforecannot start with security OPSYS.

88 WebFOCUS


How to Set Server Security and User IDsProcedure:

To set security on the server:

1. Close Developer Studio if it is open and ensure the WebFOCUS Reporting Server stops.

2. Start the WebFOCUS Reporting Server with security OPSYS by using the Start menu andPrograms, Information Builders, WebFOCUS 76 Developer Studio, WebFOCUS 76 Serverfor Developer Studio, and Start Security OPSYS.

Note: If the Server is already started, stop it, and then start it with security OPSYS.

3. Access the Reporting Server Console. You do this through the Windows Start menu byselecting Programs, Information Builders, WebFOCUS 76 Developer Studio, WebFOCUS76 Server for Developer Studio, and Web Console. You can also go to the following pagein Internet Explorer:


If no password is defined, the server starts in safe mode and an error displays.

'admin_id' has no valid member

4. Click fix now if the error appears. If no error appears, on top of the Web Console, clickWorkspace and Access Control.

The Access Control page appears. User IDs defined as server administrators appear onthe left under Users and Server Administrator. By default, this is only the Windows userID used to install Developer Studio. Expand Users and Server Administrator if they arenot expanded.

5. If you need to run with security OPSYS, click your user ID and select Properties. Thenenter and confirm the password used to log on to the Windows machine. Then, clickApply and Restart.

If a user other than the user who installed Developer Studio needs to use DeveloperStudio, click Users and choose New User. Then, type the authentication information, setthe Administration Level to Server Administrator, and click Create. This should be aWindows user ID and password.

Note: The WebFOCUS Reporting Server must be started by an ID that has administrationrights on the PC. If non-administrators need to run Developer Studio, you can set apassword for the user ID that installed the server. Then set the server's service to startautomatically with Windows.

6. Click the disk icon to save.

You are prompted to restart the server.

7. Click OK to restart the server.


C. Configuring the Local Reporting Server Security

Note:

The passwords and user IDs stored by the server must be kept in sync with thoseused to log on to Windows. If you change your Windows password, you must accessthe Server Console to change the password stored by the server.

When using security OPSYS, user IDs and passwords are also needed to run reportson the server. By default, any ID that can log on to the Windows machine can beused to run reports. The IDs and passwords needed to run reports do not need tobe stored by the server. Only IDs and passwords used to start and configure theserver must be stored by the server.

Running the Server as a Service With Security OFF

How to:

Configure the Server to Run as a Service With Security OFF

To run the Developer Studio development tools, you do not need to be an administrator tothe local machine. However, the WebFOCUS Reporting Server must run as an administratorto the Windows machine.

To allow users who are not Windows administrators to use the WebFOCUS Reporting Server,you can configure the server service to run automatically with Windows. If you want to runit with security off, you can change the user ID it runs under as a service. Normally whenthe server runs as a service, it runs with security OPSYS and uses a local systemadministrator account that was created by Windows.

How to Configure the Server to Run as a Service With Security OFFProcedure:

1. Open the Windows Services window and right-click WebFOCUS 76 Server for DevStudio.

2. Choose Properties.

3. Click the Log On tab.

4. Click the This account radio-button and specify a Windows user ID and password withadministrator rights to the local machine.

5. Click Apply.

6. Click the General tab.

7. Change the Startup type to Automatic.

8. Click OK.

90 WebFOCUS


WebFOCUS

Enabling and Accessing WebFOCUS DemoApplications

DTopics:

The following topics explain how toenable and access the WebFOCUS demoapplications. The new demo requires noconfiguration steps, but a proceduremust be run to use the older demo.

Enabling and Accessing theWebFOCUS Demos


Enabling and Accessing the WebFOCUS Demos

In this section:

New Demo Application

Older NCC Demo Applications

Two demo applications are installed with Developer Studio 7.6. These applications help youlearn the Developer Studio interface and develop ideas for your own applications.

New Demo ApplicationWebFOCUS 7.6 includes a new demo that introduces many of the advanced WebFOCUS 7features and capabilities. This demo is for a fictional manufacturing company named CenturyElectronics. Century Electronics has thousands of employees in plants, warehouses, andoffices worldwide. The demo allows the analysis of Century business, from Key PerformanceIndicator reports to typical business reports such as sales trends reports and detailed orderanalysis.

This demo requires no steps to configure. It is installed in:

drive:\ibi\apps\ibidemo

After Developer Studio is installed and configured, you can access the demo through theDeveloper Studio Explorer and through a Web browser. For example, depending on your Webserver and port:

http://localhost:8080/approot/ibidemo/index.htm

or

http://localhost/approot/ibidemo/index.htm

Note: At this time, the new demo is only available in English.

Older NCC Demo Applications

How to:

Enable the New Century Corp Demo Data

Access the Older Demo

The older WebFOCUS NCC Demo is still installed with WebFOCUS 7.6 and can be enabledto help learn basic WebFOCUS features.

92 WebFOCUS


The English demo is installed in the following directory:

drive:\ibi\apps\ibinccen

A procedure needed to set up the demo is installed as:

drive:\ibi\apps\ibisamp\loadord.fex

How to Enable the New Century Corp Demo DataProcedure:

Before using the older demo, you need to run a quick procedure to generate data it needs.The demo is only partially usable unless you perform the following:

1. Start Developer Studio. If the WebFOCUS Reporting Server is not started with DeveloperStudio, start it with security OFF.

2. Go to the WebFOCUS Welcome page in your Web browser. For example, depending onyour Web server and port:

http://localhost:8080/ibi_apps/homepage.jsp

or

http://localhost/ibi_apps/homepage.jsp

Note: Your Web server must be started to access this page.

3. On the WebFOCUS Welcome page, click Run a stored procedure.

A form appears where you can launch FOCEXEC (.fex) files.

4. In the Procedure name field, type the following:

loadord

5. Clear the Parameters field.

6. In the Application path field, leave the default IBISAMP.

7. Click Run to execute the procedure and wait for it to complete. The following file shouldbe generated:

drive:\ibi\apps\ibinccen\centord.foc

Note: By default, the ibinccen directory containing the demo is not in APP PATH. This meansit is not in the WebFOCUS Reporting Server's search path. The demo functions properly without this. However, if you wish to follow along with examples in WebFOCUS documentation,it is a good idea to add this directory to APP PATH. To do this, opendrive:\ibi\DevStudio76\srv76\wfs\etc\edasprof.prf in a text editor and add IBINCCEN tothe end of the APP PATH line.


D. Enabling and Accessing WebFOCUS Demo Applications

How to Access the Older DemoProcedure:

The English version of the demo is accessible using Internet Explorer at a page like thefollowing, depending on your Web server and port:

http://localhost/approot/ibinccen/default.htm

or

http://localhost:8080/approot/ibinccen/default.htm

94 WebFOCUS


WebFOCUS

Troubleshooting Developer StudioETopics:

The following topics explain how totroubleshoot Developer Studio.

Troubleshooting Tips

Troubleshooting Tools



In this section:

Tomcat Configuration Options

Java Memory Issues

Starting Developer Studio

Multiple Developer Studio Installations

Review the following tips when troubleshooting Developer Studio.

Tomcat Configuration OptionsSince Tomcat runs as a service, Tomcat Java settings and other parameters are written intothe registry. They can be configured through the Apache Tomcat Properties window. You canlaunch this from the Start menu by selecting Programs, Apache Tomcat 5.5, and ConfigureTomcat.

If you need to adjust the Java release, click the Java tab to changed where Tomcat looksfor Java components. Be aware that Tomcat 5.5 requires Java 1.5 and Tomcat 5.0 requiresJava 1.4.

Note: Tomcat 5.0 requires a Java 1.4 JDK. If during the Tomcat installation, Tomcat 5.0used Java 1.5 or a Java 1.4 JRE as its JAVA_HOME, then JSP page compilations will fail andyou receive errors like "Unable to find a javac compiler." To fix this, update the paths topoint to the jvm.dll file of the JRE inside a Java 1.4 JDK and add the JDK/lib/tools.jar fileto the Tomcat CLASSPATH.

Java Memory IssuesIf the Developer Studio installation configured Tomcat for you, Tomcat’s Java VM memorysettings are automatically increased. This is done because default application server JavaVM memory options may not be sufficient for some WebFOCUS features. If you need totroubleshoot further or if you manually install Tomcat or another application server, you mayneed to manually increase the Java VM memory options.

The most common Java VM options you need to set involve the size of the Java heap andstack, which determine memory availability for Java programs and the Java VM. Errors canoccur if not enough memory is available, and the heap size impacts performance, since itdetermines how often garbage collection occurs.

96 WebFOCUS


The following are the most common Java VM options related to memory settings. Replacethe ### with the size you wish to set:

-Xmx###M

Sets the maximum Java heap size. It is common to make this 1/4 of the system RAM.

-Xms###M

Sets the initial Java heap size. It is common to make this 1/8 of the system RAM.

-Xss###M

Sets the Java thread stack size. You do not need to set this unless you are fine tuningyour environment.

The size is normally set in Megabytes, for example:

-Xms128M-Xmx512M

Optimum sizes vary depending on your total memory, the needs of your application, howmany other processes require memory, the type of Java VM, and other considerations. Agood starting place is to set the minimum to 1/8 of the total RAM and set the maximum to1/4 of total RAM.

Where to set these and other Java VM options, depend on your application server.

For Tomcat on Windows, you can set these options using the Apache Tomcat Propertieswindow.

1. From the Start menu, select Programs, Apache Tomcat 5.5, and Configure Tomcat.

2. Click the Java tab.

3. In the Initial memory pool (-Xms) field, specify the initial Java heap size in megabytes.For example:

256

4. In the Maximum memory pool (-Xmx) field, specify the maximum Java heap size inmegabytes. For example:

512

5. Click OK.

6. Restart Tomcat.

For other application servers, refer to your application server documentation.


E. Troubleshooting Developer Studio

Starting Developer StudioIf you close Developer Studio and then cannot restart it, you may need to manually stop theunderlying focshell.exe process. To do this:

1. Hit Ctrl-Alt-Delete and choose Task Manager.

2. Click the Processes tab.

3. Find and select a focshell.exe Image Name if it appears.

Note: You can click the Image Name column to sort by name.

4. Click End Process.

You should be able to restart Developer Studio if no focshell.exe processes appear.

Multiple Developer Studio InstallationsThere is normally no reason to install more than one instance or release of Developer Studioon a single machine. When you install Developer Studio, it partially disables any otherinstances of Developer Studio. If you must switch between instances, be aware that youmay need to reconfigure your Web and/or application servers. In addition, you must reregisterthe correct DLL files with the operating system. Developer Studio provides a batch file toregister DLL files. It appears in the bin directory for the Developer Studio release. For example:

drive:\ibi\DevStudio76\bin\thisfoci.bat


In this section:

Accessing the Verification Tools in the WebFOCUS Administration Console

WebFOCUS Client Traces

Developer Studio Trace Utility

WebFOCUS Reporting Server Traces

Tools to troubleshoot Developer Studio are available in the WebFOCUS AdministrationConsole, Developer Studio program folder, and WebFOCUS Reporting Server Console.

98 WebFOCUS


Accessing the Verification Tools in the WebFOCUS Administration Console

How to:

Access the WebFOCUS Administration Console

Use Automatic Verification

Verify WebFOCUS Client Connections and Permissions

Test the WebFOCUS Reporting Server

To run the verification tools installed with the WebFOCUS Administration Console, accessthe console.

Note: The verification tools are only supported with Internet Explorer, and you may receiveerrors if you use other browsers.

How to Access the WebFOCUS Administration ConsoleProcedure:

1. Ensure the Web and/or application server is started.

2. Click WebFOCUS Administration Console on the WebFOCUS Welcome page or manuallygo to the console. For Tomcat:

http://localhost:8080/ibi_apps/console/webfocusconsole.jsp

For IIS:

http://localhost/ibi_apps/console/webfocusconsole.jsp

A logon page appears. If a logon page does not appear, ensure your Web server isstarted. If the Web server is started and this page does not appear, you may need tomanually configure the Web server as explained in Configuring the Web Server and/orApplication Server on page 45.

If the page appears but an error appears, you may need to edit the following file tospecify the WebFOCUS Servlet:

drive:\ibi\DevStudio76\ibi_html\javaassist\cgipath.js

3. Log on using an administrator user ID. By default, "admin" is a valid administrator ID,and the password is not initially authenticated.



The WebFOCUS Administration Console appears.

Using this console, you can edit communication and security settings. This console isdocumented in the WebFOCUS Security and Administration manual and relevant sectionsare available by clicking Help. The WebFOCUS Administration Console contains averification tool to further test the configuration.

4. On the left of the WebFOCUS Administration Console, click Diagnostics.

Several tests are available from the Diagnostics menu.

100 WebFOCUS


How to Use Automatic VerificationProcedure:

Click Automatic on the Verification menu.

This checks directory permissions and common WebFOCUS and WebFOCUS Client operations.The tests vary depending on your configuration. For a Tomcat standalone configuration, theWeb server tests may not appear.

If a test fails, a Possibilities link appears proving information on what the problem might beand possible solutions. The verification tools are only supported with Internet Explorer, andyou may receive errors if you use other browsers.



How to Verify WebFOCUS Client Connections and PermissionsProcedure:

Click WebFOCUS Client on the Verification menu to test the connection between theWebFOCUS Client and the Web server as well as permissions for your application directory,configuration files, and Managed Reporting.

The Client Path specifies how the connection is made. The default servlet URL appears.

If Managed Reporting is installed, Managed Reporting Logon fields appear.

Click Start to test the connection. A screen appears showing whether each area exists andis configured properly.

How to Test the WebFOCUS Reporting ServerProcedure:

Click WebFOCUS Reporting Server on the Verification menu to test the connection betweenthe client and the WebFOCUS Reporting Server. It shows your Client Path and allows you toselect a node.

The Client Path specifies how the connection is made. The default servlet URL appears.

You can test the following areas:

Automatic Test. This selection checks connections and checks to see if you can listapplications under the approot directory, if you can create and delete an application, andif you can run stored procedures and ad hoc reports. When you are finished, click Backto return to the previous screen.

Test Ad Hoc Procedure. This selection opens a window containing a default ad hocprocedure. You will be prompted for credentials if the server is secure. Click Run toexecute the procedure, or you can edit the procedure first. You can also change theapplication path (using APP PATH, not EDAPATH). The procedure can consist of WebFOCUSor SQL commands. When you are finished, click Back to return to the previous screen.

Test Existing Procedure. This selection lets you type a procedure name and anynecessary parameters. The procedure must be stored on the WebFOCUS Reporting Server.You can also change the application path. Click Run to execute the procedure. When youare finished, click Back to return to the previous screen.

Open Server Console. This selection opens the WebFOCUS Reporting Server's console.

102 WebFOCUS


WebFOCUS Client Traces

How to:

Turn on Tracing

View WebFOCUS Client Traces

The Diagnostics menu in the WebFOCUS Administration Console lets you view and deleteWebFOCUS Client trace files. Trace files track requests processed by the WebFOCUS Client.You must turn on traces before viewing them in the console. Since tracing can slowperformance, you should only turn on traces when troubleshooting.

How to Turn on TracingProcedure:

1. On the left of the WebFOCUS Administration Console, click Configuration.

2. Under Configuration, click Startup Parameters.

3. Select the TRACE button and click Modify.

4. Select the ON button and click Save.

5. Select Clear Memory Cache on the top of the menu.



How to View WebFOCUS Client TracesProcedure:

After traces are turned on, you can view them by selecting the type of trace. For example,to view traces generated by the WebFOCUS Servlet, on the left of the WebFOCUSAdministration Console under Diagnostics and Traces, select WFServlet.

A page lists any generated traces. The first column lists the generated trace file. The secondcolumn shows a timestamp for when the request ran. You can view a trace file by clickingit.

Developer Studio Trace Utility

How to:

Use the Communication Layer Trace

Developer Studio's trace utility (Communication Layer Trace) generates trace files for tasksperformed by the Developer Studio development environment's communication layer. Itcaptures information for tasks performed by Developer Studio when a request is submittedor retrieved by the product.

You can use this utility to help troubleshoot issues such as communicate failures, connectionproblems, and transfer of files.

To generate traces for issues you might encounter at startup, you should start the traceutility prior to launching Developer Studio.

104 WebFOCUS


To generate traces for a failure to connect to a Data Server or to determine why applicationsare not listed, you should start and enable the trace at the point prior to performing the taskthat fails.

How to Use the Communication Layer TraceProcedure:

1. Launch the Communication Layer Trace from the Windows Start menu by selectingPrograms, Information Builders, WebFOCUS 76 Developer Studio, WebFOCUS DeveloperStudio Utilities, and Communication Layer Trace.

The Communication Layer Trace tool opens.

2. Click the On radio button to enable tracing.

3. The Trace File field indicates the location and name of the trace file. The default tracefile is created in:

C:\Documents and Settings\User_ID\Application Data\Information Builders\wfscom.trc

where:

User_ID




Note: The Application Data directory may not be visible by default. To see this directory,open Windows Explorer, click Tools, choose Folder Options, and select the View tab.Then select Show hidden files and folders and click OK.

4. In the Trace Levels area, keep the default All levels to capture all required informationor specify a specify level.

WebFOCUS Reporting Server Traces

How to:

View a Trace File

You can turn WebFOCUS Reporting Server traces on when you start the server or dynamicallyafter the server has started.

To start the server with traces, you should start it before Developer Studio by selectingPrograms from the Start menu, then Information Builders, WebFOCUS 76 Developer Studio,WebFOCUS 76 Server for DevStudio, Diagnostic Functions, and Start Security OFF withTraces.

To turn traces on dynamically, access the Server Console and select Workspace,Diagnostics, and Traces.

Note: Viewing traces is only available to a server administrator.

You can use the WebFOCUS Reporting Server Web Console to view server traces as well asturn them dynamically on or off for a running server.

If tracing is set to off and it was never turned on, the page shows that no traces are availableand enables you to turn traces on. If tracing is on, the page displays the available traces indrop-down boxes. Which traces are available depends on what requests were made againstthe server.

To turn traces on dynamically, click Enable Traces. Be aware that a dynamic trace is not thesame as turning traces on at server startup. A dynamic trace is usually not sufficient forfollowing a problem through with Customer Support, but it may suffice for other purposes,such as seeing how something is parsed.

Note: The default for tracing is to trace all components when tracing is turned on. However,the trace settings file (ibitrace.fex) may have been altered. Therefore, components that youexpect to be traced may not be traced. Click Configuration to access the Traces Configurationpage to view and set a trace setting.

How to View a Trace FileProcedure:

1. From the Web Console, select Workspace, then Diagnostics, then Traces.

106 WebFOCUS


2. Click a specific trace file and then choose from the following options:

Open. Displays the trace in the right-hand browser pane.

Open in New Window. Displays the trace in a new browser window.

Open or Save. Enables you to open the trace in a local editor or to save it to a localdisk.

Delete. Deletes the selected trace.

The file opens (or is deleted) according the option you choose.



108 WebFOCUS


WebFOCUS

Index

A

Administration Console 38, 100

Adobe Acrobat requirements 24

aliases for WebFOCUS Developer Studio 53

Apache Tomcat 25, 26, 29, 33, 46, 51, 56, 96Administration Tool 51configuration options 26, 46IIS plug-in/connector configuration 26, 29, 46, 56Java configuration 96ports 51security 33standalone configuration 26, 29, 46troubleshooting 96

application server requirements 24

application servers 16, 26, 29, 46configuration options 26, 29, 46overview 16

APPROOT directory 54

automatic verification 38, 101

C

CGI requirements 24

Communication Layer Trace 104

creating aliases for Developer Studio 54

D

debugging 95

demos for Developer Studio 91

Developer Studio 14, 15, 18, 20, 23, 24, 26, 27, 28, 30, 41, 54, 65, 95

aliases 54components 15, 28configuration options 20directory structure 30installation options 18installing 18, 26, 27installing non-interactive version 41network installation 65processing 18requirements 24silent installation 41troubleshooting 95

diagnostic tools 39, 100, 104, 106Developer Studio 104WebFOCUS Client 104WebFOCUS Reporting Server 106

Eenvironments

overview for WebFOCUS 16remote development 18

Ffile permissions 55

for ServletExec ISAPI 55

G

GUI installation 25

H

hardware requirements for Developer Studio 24


I

IBI Demonstration application 91

IIS (Internet Information Server) 26, 29, 46, 53, 54

configuration options 26, 29, 46configuring for Developer Studio 53starting and stopping 54

installation options 18

installation verification tool 39

installing Developer Studio 26, 27

Internet Explorer requirements 24, 67

J

Java requirements 25, 67

L

local development environments 18

M

Maintain development 14

Microsoft IISconfiguration options 26, 29, 46configuring for Developer Studio 53starting and stopping 54

migrating applications 40

N

network installation for Developer Studio 65

New Century Corp application 91

non-interactive (silent) Developer Studio installation

41

NTFS permissions 55for ServletExec ISAPI 55

O

operating system requirements for Developer Studio

24, 67

P

prefixes for WebFOCUS 53

Project Migration Tool 40

Project-based development environments 18

Q

Quick Data 83

R

remote development environments 18

report processing 17

ReportCaster 14

requirements for Developer Studio 24, 26

S

sample applications 91

security 88

security for the WebFOCUS Reporting Server 88

Server Consolesecurity 88troubleshooting 106

server diagnostic trace files 106

110 WebFOCUS

Index

ServletExec 26, 29, 55automatic configuration option 26, 29file permissions 55

servlets for WebFOCUS 16, 47, 63configuring manually 63configuring with Tomcat 47

silent installations 26

software requirements for Developer Studio 24

starting and stopping 35, 54, 89IIS 35, 54Tomcat 35WebFOCUS Reporting Server 89

T

third party components for Developer Studio 25

Tomcat 25, 26, 29, 33, 46, 51, 96Administration Tool 51configuration options 26, 46IIS plug-in/connector configuration 26, 29, 46Java configuration 96ports 51security 33standalone configuration 26, 29, 46troubleshooting 96

tracing 98, 103, 104, 106CGI 103Developer Studio 104servlet 103WebFOCUS Client 103WebFOCUS Reporting Server 106

troubleshooting Developer Studio 95

troubleshooting servers 106

Uutilities in Developer Studio 40, 100, 104

Communication Layer Trace 104verification tool 100

Vverification 38, 101, 102

automatic 38, 101WebFOCUS Reporting Server 102

verification tool 38, 100, 101, 102

verifying Client connections 102

virtual directories for Developer Studio 53

Visual Discovery 14, 28

W

Web server requirements 24

Web servers 16, 26, 29, 46configuration options 26, 29, 46overview 16

webapps 63

WebFOCUS 14

WebFOCUS Administration Console 38, 40, 99, 100

accessing 38, 99authentication 40security 40verification tool 100

WebFOCUS Client 16, 39, 103tracing 103verification tool 39

WebFOCUS configurations 17

WebFOCUS environmentsoverview 16

WebFOCUS Maintain 14

WebFOCUS processing 17

WebFOCUS Quick Data 83

WebFOCUS Reporting Server 16, 32, 88, 102, 106connection 102for Developer Studio 32security 88tracing 106


Index

WebFOCUS servletsautomatic deployment 37configuring 63

WebFOCUS Visual Discovery 14

WebFOCUS Web applications 37, 63

112 WebFOCUS

Index

WebFOCUS

Reader Comments

In an ongoing effort to produce effective documentation, the Documentation Services staffat Information Builders welcomes any opinion you can offer regarding this manual.

Please use this form to relay suggestions for improving this publication or to alert us tocorrections. Identify specific pages where applicable. You can contact us through the followingmethods:

Documentation Services - Customer SupportMail:Information Builders, Inc.Two Penn PlazaNew York, NY 10121-2898

(212) 967-0460Fax:

[email protected]:

http://www.informationbuilders.com/bookstore/derf.htmlWeb form:

Name:

Company:

Address:

Telephone: Date:

Email:

Comments:

Information Builders, Two Penn Plaza, New York, NY 10121-2898 (212) 736-4433WebFOCUS Developer Studio Installation and Configuration DN4500817.0908Version 7 Release 6.4 and Higher

mailto:[email protected]

http://www.informationbuilders.com/bookstore/derf.html

Reader Comments

Information Builders, Two Penn Plaza, New York, NY 10121-2898 (212) 736-4433WebFOCUS Developer Studio Installation and Configuration DN4500817.0908Version 7 Release 6.4 and Higher