wf761mradmin

WebFOCUS Managed Reporting Administrator'sManualVersion 7 Release 6.1 and Higher

DN4500809.1208

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................................................................................................................9Documentation Conventions............................................................................................11

Related Publications........................................................................................................12

Customer Support...........................................................................................................12

Information You Should Have...........................................................................................13

User Feedback................................................................................................................14

Information Builders Consulting and Training.....................................................................14

1. Introducing WebFOCUS Managed Reporting..................................................15Managed Reporting Overview...........................................................................................16

WebFOCUS Products.......................................................................................................16

Managed Reporting..................................................................................................17

Business Intelligence Dashboard..............................................................................17

ReportCaster...........................................................................................................17

Managed Reporting Concepts..........................................................................................18

Managed Reporting Capabilities...............................................................................18

Managed Reporting Deployment Process..........................................................................21

Using Managed Reporting................................................................................................23

Using the Browser Toolbar .......................................................................................24

Accessing Dashboard......................................................................................................26

Using the Mozilla Firefox Browser With Dashboard View Builder...................................27

Customizing Dashboard...................................................................................................28

Setting Up a WebFOCUS Environment...............................................................................29

Working With Environment Properties........................................................................29

Local Machine Properties.........................................................................................33

Web Component Properties......................................................................................35

WebFOCUS Client Properties....................................................................................36

Managed Reporting/ReportCaster Properties.............................................................37

Data Server Properties.............................................................................................39

WebFOCUS Managed Reporting Administrator's Manual 3

Project Development Properties................................................................................39

2. Creating Domains, Groups, Roles, and Users................................................41Using the Managed Reporting Administration Interface.......................................................42

Creating Domains...........................................................................................................43

Working With the Server and Application Path Properties............................................45

Creating Groups..............................................................................................................46

Creating Users................................................................................................................48

Searching for Users.................................................................................................50

Assigning the Group Administrator Privilege...............................................................50

Assigning Development Domains..............................................................................51

Setting Up Users to Save Parameter Values..............................................................53

Creating Roles................................................................................................................53

User Roles Defined..................................................................................................54

User Privileges Defined............................................................................................59

Customizing the Interface................................................................................................62

3. User Management..........................................................................................63User Management Tree Object in Domain Builder..............................................................64

Managing a User's Reports..............................................................................................66

Promoting a Custom Report to a Standard Report..............................................................68

4. Managing Dashboard.....................................................................................69Managing Public Views....................................................................................................70

Managing Library Access in a Public View..................................................................71

Managing Group Views....................................................................................................71

Managing Library Only Views............................................................................................71

Managing Private Views...................................................................................................72

Logging On to Dashboard and View Inheritance.................................................................72

Logon Process for All Users (Excluding Library Only Users)..........................................73

Logon Process for Library Only Users........................................................................74

Managing Users..............................................................................................................75

Setting an ID and Password for the Public User..........................................................77

Setting a Server User ID and Password for the Public User.........................................79

Controlling the Idle Limit for Authenticated and Public Users..............................................81

4 WebFOCUS

Contents

Handling Messages.........................................................................................................83

Hiding Report Types in the Domain Tree............................................................................83

Hiding Report Types in the Domain Tree for All Role Types..........................................85

Hiding the Share Report Option for Finished My Reports.....................................................86

Displaying Optional Properties in Dashboard.....................................................................87

Creating Standard Reports in Dashboard..........................................................................88

5. Creating Public and Group Views..................................................................91What Is a Public View?....................................................................................................92

What Is a Group View?....................................................................................................92

What Is a Library Only Group View?...................................................................................93

Adding a Group or Public View..........................................................................................93

Group Administrator Access to the View Builder.........................................................96

Directing Users to a Group View Upon Login......................................................................96

Adding a Library Only View...............................................................................................97

Removing a Public or Group View......................................................................................98

Editing a Public or Group View..........................................................................................98

Customizing Dashboard Pages for a Public or Group View...................................................99

Copying a Public or Group View......................................................................................102

Exiting the Public Views or Group Views Window..............................................................103

6. Customizing Dashboard...............................................................................105Before You Begin Customizing Dashboard.......................................................................106

Opening the View Builder...............................................................................................107

Selecting a Template.....................................................................................................109

Creating a Custom Template..................................................................................111

Selecting Custom Colors................................................................................................115

Positioning the Domain Tree, Role Tree, and Banner........................................................123

Selecting Scrolling Options for Domain Trees and Role Trees....................................125

Inserting a Logo............................................................................................................125

Customizing the Banner.................................................................................................127

Displaying a Welcome Message in the Banner.........................................................131

Creating a Custom Toolbar.............................................................................................132

Adding a Message of the Day.........................................................................................135

Customizing the Logoff Window......................................................................................136


Contents

Changing the ReportCaster Scheduling Tool....................................................................138

Resetting the View Builder.............................................................................................139

Saving Selections and Exiting a Customization................................................................139

Exiting the View Builder.................................................................................................140

7. Creating a Role Tree....................................................................................141What Is a Role Tree?.....................................................................................................142

Adding a Role Tree........................................................................................................142

Editing a Role Tree........................................................................................................144

8. Creating Dashboard Content........................................................................147Creating Dashboard Content Overview............................................................................148

Content Window............................................................................................................148

Creating Content Pages.................................................................................................150

Creating Library Content for a Public View................................................................152

Adding a Content Block..................................................................................................153

Creating a Locked Content Block............................................................................158

Adding Report Library Content to a Content Block....................................................159

Removing a Content Block......................................................................................159

Editing a Content Block.................................................................................................160

Enabling Automatic Block Refresh...........................................................................163

Selecting Scrolling Options.....................................................................................165

Hiding the Toolbar in a Content Block......................................................................166

Creating Filters For Standard Reports.............................................................................167

Executing a Domain Profile in Dashboard........................................................................167

Selecting Content Layout...............................................................................................167

9. Managed Reporting Extract Utility..............................................................171Managed Reporting Extract Utility...................................................................................172

Running the Managed Reporting Extract Utility.................................................................172

Managed Reporting Extract Utility Output Files.................................................................174

Master Files and Sample Procedure...............................................................................176

Reporting From Extract Files...........................................................................................182

Sending the Data Files...........................................................................................182

Allocating the Extract Files to the WebFOCUS Reporting Server.................................183

6 WebFOCUS

Contents

Output File Relationships.......................................................................................184

Property Flags...............................................................................................................185

10. Change Management.................................................................................189Understanding the Change Management Process............................................................190

Managed Reporting Development Environment................................................................191

Understanding Internal Managed Reporting References....................................................192

Managed Reporting Change Management Features..........................................................193

Copying Files Between Environments Using Developer Studio...................................194

Copying a Domain Between Environments Using Developer Studio............................196

Change Management Extract Utility................................................................................197

Change Management Load Utility...................................................................................201

Alternate Change Management Load Program..........................................................204

Dashboard Change Management....................................................................................207

11. Additional Administration Topics...............................................................211Selecting the Tool Type for ReportCaster.........................................................................212

Debugging....................................................................................................................213

Your Browser's Java Console..................................................................................213

Tracing the Java Applets........................................................................................214

Tracing the WebFOCUS Client.................................................................................214

Enabling Tracing Options in Dashboard...................................................................215

Setting Up Traces for Managed Reporting User Requests.................................................218

Repository File Name Processing....................................................................................218

Obtaining a List of Available Master Files........................................................................219

12. Application Integration Topics...................................................................221Invoking the Deferred Report Status Interface Directly......................................................222

Managed Reporting Browser Window Feature..................................................................223

WebFOCUS Managed Reporting Implementation......................................................223

Site Customization................................................................................................224

Browser Window Options........................................................................................226

Browser Window Exceptions...................................................................................227

Customizing the Amper Auto-Prompting Facility........................................................227

Using Launch Pages Outside the Default Repository........................................................228


Contents

13. Two-Way Email Administration...................................................................231Accessing the Administrator Console..............................................................................232

Adding or Deleting a Subscriber......................................................................................233

Maintaining an E-mail Address.......................................................................................235

Refreshing a User's Templates......................................................................................236

Using the Job Log..........................................................................................................237

Viewing the Status of an Executed Job....................................................................237

Purging the Job Log...............................................................................................239

Using the Event Log......................................................................................................240

Monitoring E-mail Traffic.........................................................................................242

Purging the Event Log............................................................................................244

Checking the Status of a Job or Canceling a Job..............................................................245

14. Managing Deferred Tickets........................................................................247Managing Deferred Workload.........................................................................................248

Understanding Alternate Deferred Servers...............................................................248

Configuring Deferred Services.................................................................................249

Deferred Report Expiration Setting..........................................................................250

Reading Saved Deferred Output Created by WebFOCUS CGI/ISAPI Client...................251

Managing the Deferred Ticket Cleanup Utility...................................................................252

Deferred Ticket Cleanup Utility Processing...............................................................253

MR Repository and User Credentials.......................................................................253

WebFOCUS Reporting Server and User Credentials...................................................254

Log File and Backup of User HTM File.....................................................................256

Running the MR Deferred Ticket Cleanup Utility........................................................259

Processing Multiple MR Repositories in Silent Mode................................................269

Troubleshooting.....................................................................................................270

Reader Comments...........................................................................................287

8 WebFOCUS

Contents

WebFOCUS

Preface

This documentation describes the WebFOCUS Managed Reporting Administrators environment,which enables the creation of powerful EIS and decision-support applications that delivereasy access to the information that users need, regardless of hardware platforms, databasestructures, or application programs. It is intended for system administrators.

How This Manual Is Organized

This manual includes the following chapters:

ContentsChapter/Appendix

Describes Managed Reporting, ReportCaster, andDashboard. Explains Managed Reporting concepts,Dashboard customization, and how to access anduse Managed Reporting and Dashboard. Describeshow to add, edit, and review properties of WebFOCUSenvironments.

Introducing WebFOCUSManaged Reporting

1

Describes how to create domains, groups, roles, andusers with the Managed Reporting Administrationinterface.

Creating Domains, Groups,Roles, and Users

2

Describes how the User Management tree object isused to view all types of user’s reports and to open,edit, run, save, and delete Managed Reporting user’sreports.

User Management3

Describes how the Administrator controls what userscan access in the general public view, the custompublic view, and in group views. This includes thedomains they can view and certain functionality suchas the Domain Search.

Managing Dashboard4



Describes how to create and manage public views(general and custom) and group views from the PublicViews and Group Views windows in the View Builder.From the Public/Group Views windows you can add,remove, edit, or copy a public or group view.

Creating Public and GroupViews

5

Describes how to customize the Dashboard bychoosing colors, adding a logo, selecting the positionof the Domain Tree, Role Tree, and banner, and more.

Customizing Dashboard6

Describes how to create Role Trees, which allowDashboard users access to items (reports, graphs,launch forms, and URLs) that have been associatedwith their Managed Reporting User Groups.

Creating a Role Tree7

Describes how to create content blocks, which displaywhen you open the Dashboard. Content blocks cancontain launched reports, links to reports, or links toInternet resources.

Creating Dashboard Content8

Describes how the Managed Reporting Extract utilityallows you to extract data from your ManagedReporting Repository in order to generate reportsabout users, groups, domains, and domain content.

Managed Reporting ExtractUtility

9

Describes features in Managed Reporting that canbe used to facilitate change management, which isthe process of moving application componentsbetween WebFOCUS environments.

Change Management10

Provides additional information for administratorsabout Deferred Receipt, Report Assistant and GraphAssistant, and tracing the WebFOCUS Client, JavaApplet, and Dashboard.

Additional AdministrationTopics

11

Provides information on invoking the Deferred ReportStatus Interface, browser window features, andlaunch pages.

Application IntegrationTopics

12

Describes how to use the Two-Way EmailAdministrator console.

Two-Way EmailAdministration

13

10 WebFOCUS


Provides information for Administrators to managedeferred workload and the Deferred Ticket CleanupUtility.

Managing Deferred Tickets14

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) in syntax for a value thatyou or the system must supply.

this typeface

Indicates a default setting.underscore

Represents a placeholder (or variable), a cross-reference, or animportant term. It may also indicate a button, menu item, ordialog box option you can click or select.

this typeface

Highlights a file name or command.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 are required,but you may select one of them. Type only the parameter in thebrackets, not the brackets.

[ ]

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

|

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

...


Preface

DescriptionConvention

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

.

.

.

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.

12 WebFOCUS

Related Publications

http://documentation.informationbuilders.com

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

http://www.informationbuilders.com

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.

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?


Preface

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.

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.

14 WebFOCUS

User Feedback

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

WebFOCUS

Introducing WebFOCUS Managed Reporting1Topics:

WebFOCUS is a complete, Web-ready,enterprise data access and reportingsystem, which takes advantage of thelow-cost, low-maintenance, and widedistribution capabilities of the World WideWeb and internal corporate Web sites.

Managed Reporting Overview

WebFOCUS Products

Managed Reporting Concepts

Managed Reporting DeploymentProcess

Using Managed Reporting

Accessing Dashboard

Customizing Dashboard

Setting Up a WebFOCUS Environment


Managed Reporting OverviewWebFOCUS enables application developers and Web designers to create powerful EIS anddecision-support applications that deliver easy access to the information that users need,regardless of hardware platforms, data source structures, or application programs. Developerscan create sophisticated Web pages that enable end users to view static reports, to rundynamic reports, and to create parameterized queries for individual requests.

The WebFOCUS Business Intelligence Dashboard is an HTML-based thin client that enablesyou to create a customized user interface for access to WebFOCUS Managed Reporting.

When you connect to Dashboard you are also connecting to WebFOCUS Managed Reporting,which means all of the Standard Reports and Reporting Objects that are available in ManagedReporting are also available in Dashboard.

You define and manage your WebFOCUS environments from the WebFOCUS EnvironmentProperties dialog box in Developer Studio. You access this dialog box from either theWebFOCUS Environments node in the Explorer or from the Environments List dialog box.

WebFOCUS Products

In this section:

Managed Reporting

Business Intelligence Dashboard

ReportCaster

To develop Web-based reporting applications, WebFOCUS provides integrated Java-baseddevelopment tools that are seamlessly integrated with the WebFOCUS server-side softwarecomponents. WebFOCUS enables Developers to prototype, test, and deploy Web-basedreporting applications quickly, without requiring knowledge of HTML, Web serveradministration, or the FOCUS 4GL reporting language. WebFOCUS offers the followingapplication development and deployment tools:

Managed Reporting on page 17.

Business Intelligence Dashboard on page 17.

ReportCaster on page 17.

16 WebFOCUS

Managed Reporting Overview

Managed ReportingManaged Reporting provides a streamlined reporting environment that virtually eliminatesthe complexities of today's corporate data. Managed Reporting Administrators can use theDomain Builder tool in the browser version to develop Managed Reporting, including StandardReports and Reporting Objects. With the User Administrator tool available from the ManagedReporting browser or Developer Studio environments, Administrators can manage accessto Managed Reporting domains. Administrators grant authorized users access to theinformation they need, while restricting unauthorized users from sensitive or confidentialcorporate data.

Users of Managed Reporting can create and save reports that meet their individual businessneeds without knowing the details and complexities of the underlying data source or of theFOCUS reporting language. Managed Reporting ensures that users can access the informationthey require, while protecting sensitive or confidential data.

Business Intelligence DashboardThe WebFOCUS Business Intelligence Dashboard allows you to create a customized userinterface for access to WebFOCUS Managed Reporting.

From Dashboard you can:

Customize the look of the WebFOCUS environment (administrators only).

Create personalized content blocks that can contain launched reports, links to reports,and links to Internet resources.

Search domains available in the WebFOCUS environment.

Create and manage public views (administrators only).

Dynamically access non-WebFOCUS documents.

View the status of deferred reports.

Access reporting tools such as Power Painter, Report Assistant, Graph Assistant, andReportCaster.

ReportCasterReportCaster is an optional Java-based tool that provides a single point of management forreport scheduling and distribution using the Web, e-mail, Managed Reporting, or a printer.ReportCaster enables you to provide essential, updated information directly to the peoplewho need it, on time, automatically.


1. Introducing WebFOCUS Managed Reporting

You can access ReportCaster by clicking the ReportCaster icon in the Managed Reportingbrowser or Developer Studio. All ReportCaster functions are available from your reportingenvironment, including:

Scheduling reports to be run once or repeatedly.

Bursting reports to send specific values in a report to different users, files, or printers.

Distributing report output using e-mail, FTP, printer, or Managed Reporting.

Maintaining scheduled jobs, the address book of distribution lists, and log files.

For more information about ReportCaster, see the ReportCaster Development andAdministration manual.


In this section:

Managed Reporting Capabilities

Managed Reporting Administrators create and manage user environments. Managed ReportingDevelopers develop content for users. Managed Reporting users can run Standard Reports,defined in advance by a Managed Reporting Administrator or a Developer. In addition,Managed Reporting users can create and save reports that meet their individual businessneeds without knowing the details and complexities of the underlying data source or of theFOCUS reporting language.

To organize the Standard Reports and Reporting Objects available to users, ManagedReporting Administrators create a series of domains, using the Managed Reporting DomainBuilder in the browser or the Explorer in the full Developer Studio. Organizing StandardReports and Reporting Objects by domains ensures that users can access the informationthey require, while protecting sensitive or confidential data.

Managed Reporting CapabilitiesAs a Managed Reporting Administrator or Developer, you create the Standard Reports thatusers run, as well as publish the HTML launch pages used to call reports that requireparameters. In addition, you can perform the following actions:

Create access rights to Managed Reporting. To enable a user to access ManagedReporting, you must create a user account for every user, assign the user a role, andspecify the groups to which every user is a member. You also specify which reportingdomains belong to each group. User accounts and groups are created with the ManagedReporting Administration interface.

18 WebFOCUS


For more information about the Managed Reporting Administration interface, see CreatingDomains, Groups, Roles, and Users on page 41. The Managed Reporting Administrationinterface is not available in Managed Reporting Developer for Windows.

Create and access the metadata for data sources. To create a report that accessesa data source, you must first create and access the metadata for that data source.Metadata is information about the structure of the data itself, such as the columns orfields in the data source, their format, or the location of the data sources.

You create and manage metadata from the Data Servers feature in Domain Builder inthe browser or in the Explorer in Developer Studio. You can enhance this metadata withadditional descriptive information like the business context of a particular field.

Build the reports that retrieve and format data. Using Managed Reporting, you canbuild, test, and deploy sophisticated tabular reports and graphs, without knowing theFOCUS reporting language. In addition to creating new report procedures, you can moveexisting procedures from the WebFOCUS Reporting Server to the WebFOCUS ManagedReporting Repository in order to modify or enhance them. For information about creatingtabular reports and graphs, see the WebFOCUS Managed Reporting End User's Manual.

For information about creating advanced graphs and using report procedures stored onthe WebFOCUS Reporting Server, see the WebFOCUS Managed Reporting Developer'sManual.

Create Reporting Objects for users. Managed Reporting lets you create ReportingObjects for Managed Reporting and Dashboard users. Reporting Objects arerepresentations of data sources, which present the available data using terms and formatsmeaningful to the user. Using predefined Reporting Objects, Managed Reporting usersbuild and save their own reports without having to know the details and complexities ofthe underlying data sources.

For more information about creating Reporting Objects, see the WebFOCUS ManagedReporting Developer's Manual.

Create OLAP-enabled reports. Managed Reporting enables you to update metadatafiles to make them OLAP-enabled as well as to create OLAP-enabled Standard Reportsand Reporting Objects for your users. Users can run OLAP-enabled reports and use theOLAP selections panel or the OLAP Control Panel to manipulate the reports in order toview different representations of the data, without modifying the actual Standard Reportor Reporting Object. For more information, see the WebFOCUS Managed Reporting EndUser's Manual.



Publish HTML launch pages for the reports. After you create and test your reports,you can use Managed Reporting to publish the report to the Web. When you publish areport, you create a launch page, a complete HTML file that calls the report procedure.You can create an HTML launch page for any report stored using Managed Reporting.These launch pages can be published back to Managed Reporting or they can beincorporated into a self-service application.

You can customize launch pages by editing the HTML file to add additional HTML tagsand syntax. For example, the HTML launch page can include image files (GIF or JPG files),tables, frames, JavaScript™ functions, and hypertext links to other Web pages. In addition,the launch pages that you create can be accessed through HTML hyperlinks from otherWeb pages.

For more information about publishing launch pages, see the WebFOCUS ManagedReporting Developer's Manual.

Schedule reports. Managed Reporting provides access to ReportCaster, where you canschedule and distribute Standard Reports. ReportCaster enables you to provide essential,updated information directly to the people who need it, on time, automatically. Forinformation about scheduling and distributing report output with Managed Reporting, seethe ReportCaster Development and Administration manual.

Distribute reports when certain test conditions are met using ReportCaster Alerts.A ReportCaster Alert sends notification to a user whenever a specified event takes place.You are able to create test conditions (rules) and specify how often you would like theserules or events to be checked against a data source. ReportCaster can then generate areport or sections of that report (burst option) as a result of the alert.

ReportCaster Alerts work with all e-mail clients and WAP-enabled mobile phones. Alertscan also be sent to any PC or laptop computer with e-mail capability.

For more information about ReportCaster Alerts administration, see the WebFOCUSManaged Reporting Developer's Manual.

Receive a WebFOCUS report by Two-Way Email. As a Managed Reporting Administratoror Developer, you use Managed Reporting to create and maintain Two-Way Emailtemplates, the means by which a user requests a report. A Managed ReportingAdministrator can also use the Two-Way Email Administrator Console to manage subscriberinformation, monitor the execution of report requests, cancel requests, and perform otheradministrative tasks.

For more information about Two-Way Email administration, see Two-Way EmailAdministration on page 231.

20 WebFOCUS


Customize Managed Reporting. Managed Reporting lets you customize the userenvironment by adding profiles and customized help files to domains. A profile, whichruns each time a user opens a Managed Reporting domain, can provide an introductoryreport or information about the Managed Reporting domain. Customized help files, whichusers access from the Managed Reporting domain, provide additional information specificto the Managed Reporting domain, such as detailed explanations of Standard Reportsand Reporting Objects.

For more information, see Creating Domains on page 43.

Managed Reporting Deployment ProcessManaged Reporting (MR) has many features that enable security integration with yourbusiness at the enterprise level. If security integration is not your immediate concern, youcan skip this section because Managed Reporting is installed out of the box with its ownbuilt-in user repository.

The first step in an enterprise Managed Reporting deployment is to identify roles andresponsibilities. It is possible in a large enterprise that there are different people chargedwith the following roles:

WebFOCUS Administrator has access to the WebFOCUS Administration Console andcan configure global settings including Managed Reporting security, multi-languagesupport, data server access, and so on. You can access the iServer Console from theWebFOCUS Administration Console.

iServer Administrator has access to the iServer Console and has rights to configureadapter settings and also global settings such as server security. They can also identifyand set access rights for other individuals who can use the iServer Console.

iServer Application Administrator has access to the iServer Console and has rightsto create metadata and application resources. For a complete description of this andother iServer privilege levels, consult your Server documentation.

Managed Reporting Administrator has access to the Managed Reporting Administrationinterface and can create MR users, groups, domains, and roles. They can also assignGroup Administration rights to specified users and define which reports are available towhich groups of users.

Managed Reporting Group Administrator can add and remove users from the groupsto which they are granted administration rights, and can create users with somelimitations. Group Administrators can also access the View Builder to create and updateGroup Views for groups they administer.



Managed Reporting Developer can use the Developer Studio (Windows) and DomainBuilder (Java applet) interfaces to create report content for MR domains. This includesReporting Objects which enable end users to create their own ad-hoc reports. If grantedaccess, these users can create metadata on the server.

Managed Reporting Users based on their role and privilege settings can create andrun reports and access other features such as Report Library.

Before deploying Managed Reporting, an enterprise may follow the process described in thefollowing image.

After you have identified roles and responsibilities, the WebFOCUS Administrator shoulddecide how users will be authenticated and authorized to use Managed Reporting (MR). Forexample, if users will be authenticated by Active Directory this is configured in the WebFOCUSAdministration Console. Likewise, the Managed Reporting Administration interface supportsuser maintenance in a relational DBMS. To configure this security option, you use theWebFOCUS Administration Console. It is possible to grant multiple people access to theWebFOCUS Administration Console, so that MR security settings can be made by the MRadministrator. For more information, see the WebFOCUS Security and Administration manual.

22 WebFOCUS

Managed Reporting Deployment Process


In this section:

Using the Browser Toolbar

As a Managed Reporting Administrator or Developer, use the following tools to create andmanage the Managed Reporting user environment:

Developer Studio MR Component and Domain Builder applet enable you to createStandard Reports that users run, launch pages that make those reports available on theWeb, and Reporting Objects for users to create their personal reports. The ManagedReporting Repository supports long file names (up to 64 characters) for My Reports,Standard Reports, Reporting Objects, and Other files.For more Domain Builder information,see Creating Domains on page 43.

Managed Reporting Administration enables you to configure user access to ManagedReporting by specifying user profiles, roles, and the domains that the users can access.Grouping users and domains ensures that users can access the information they need,while protecting sensitive or confidential data. Managed Reporting Administration is onlyavailable to Administrators and limited functionality is available for Developers that areassigned the Group Administrator privilege. For more information, see Creating Domains,Groups, Roles, and Users on page 41. This tool is not available in Managed ReportingDeveloper for Windows.

ReportCaster is an optional tool that enables you to schedule the execution of StandardReports, and distribute the information directly to the people who need it, on time,automatically. ReportCaster requires ReportCaster Administrator privileges. For moreinformation, see the ReportCaster Development and Administration manual.

Two-Way Email enables mobile business professionals to request and receive WebFOCUSreports through e-mail, using a handheld device, laptop, or desktop. For more information,see Two-Way Email Administration on page 231.

Data Servers lets you create, access, and use data source descriptions and procedurefiles that reside on the WebFOCUS Reporting Server. The Data Servers component containsthe stored procedures and Master Files called by the reports that you create. The DomainBuilder in the browser and the Explorer in Developer Studio display the Data Serverscomponent in a hierarchical, tree-like structure.

Note: If you are a Developer using the browser, or you are not using the full edition ofDeveloper Studio and you do not have the Data Server privilege, the Data Servers nodeis hidden. Developers with the Data Server privilege will be able to view and edit theServer and Application path properties on a Domain. Without the Data Server privilege,Developers will only be able to view these properties.



Domains reside on the Web server in the Managed Reporting Repository and are usedto build and test Standard Reports, Reporting Objects, and the Web pages that launchthose procedures. Each domain that you create (in the browser or the full DeveloperStudio) contains a group of folders for the different types of objects you create forManaged Reporting users. The Domain Builder in the browser and the Explorer in DeveloperStudio display the domains in a hierarchical, tree-like structure.

The following image shows the Developer Studio window with the standard Windows menubar and two rows of toolbar. The window is then divided into two sections, the left sectiondisplays the hierarchical structure of the objects created for Managed Reporting users andthe right section contains the available domains.

Using the Browser ToolbarThe WebFOCUS Managed Reporting Domain Builder and Domains environments both provideaccess to the toolbar.

The toolbar contains the tools required to create, test, edit, and publish report proceduresand Web launch pages. Using the toolbar, you can create the metadata for data sources,build the reports that retrieve and format that data, and generate Web pages that enableusers to run the reports. The following image shows the Managed Reporting toolbar whichis later described in a table.

You perform these tasks using the toolbar buttons as outlined in the following table. Thetables provides the name of the button and a description of the task you can perform fromthe button.

DescriptionButton

Adds a new component. For example, if you highlight the Domainsfolder and then click New, you create a new domain.

New

Opens/closes a selected object.Open/Close

Displays the code for the selected object (report, procedure, or launchpage) in the text editor window.

Edit Source

Enables you to search the selected domain, folder, or object.Search

24 WebFOCUS


DescriptionButton

Updates the contents of the Managed Reporting Repository window.This button is useful when more than one Administrator is working inManaged Reporting. Changes one Administrator makes to theRepository may not always be visible to other Administrators.

This feature is context sensitive; only the selected object will refresh.

Refresh

Executes the selected report or displays the selected launch page.Run

Executes the selected report in deferred mode.Run Deferred

Displays the Deferred Report Status Interface in a new browserwindow.

Deferred Status

Creates an HTML launch page for the selected report. For moreinformation, see the WebFOCUS Managed Reporting Developer'sManual.

Publish

Opens the Managed Reporting Administration interface. For details,see Creating Domains, Groups, Roles, and Users on page 41.

ManagedReportingAdministration

Enables you to access ReportCaster. For more information, see theReportCaster Development and Administration manual.

ReportCaster

Enables you to access the ReportCaster Console. For moreinformation, see the ReportCaster Development and Administrationmanual.

ReportCasterConsole

Enables you to access the content in the Report Library.Report Library

Removes an object (Standard Report, Reporting Object, launch page,or Other File) from the domain and copies it to the clipboard.

Cut

Copies an object to the clipboard.Copy

Removes the selected folder or object.Delete

Places the clipboard item into the indicated destination.Paste

Displays the name and data source of the selected object.Properties

Displays online help.Help



The Managed Reporting toolbars are positioned at the top of both Managed Reportinginterfaces.

Accessing Dashboard

In this section:

Using the Mozilla Firefox Browser With Dashboard View Builder

How to:

Open Dashboard

There are several views in Dashboard:

Public. This view is accessible to public users and cannot be personalized. Public usershave execute-only access; they cannot save report requests or report output to a domain.For details, see How to Open Dashboard on page 26.

Group. A group view is accessible to users with a valid Managed Reporting user ID andpassword. The user must be a member of the group to gain access to the view. Groupviews cannot be personalized by users.

Private. This view is accessible to users with a valid Managed Reporting user ID andpassword. From this view a user can add to or edit the content blocks the administratorhas set up. For details, see How to Open Dashboard on page 26.

You use the View Builder to create a unique look for each public and group view.

How to Open DashboardProcedure:

You can open the Dashboard View Builder, Group Views page, and Public Views pagefrom the WebFOCUS Welcome page (http://hostname/ibi_apps/).

Alternatively, you can:

Enter the following URL in your Web browser:

http://hostname[:port]/ibi_apps/bid

where:

hostname

Is the host name and optional port number (specified only if you are not using thedefault port number) where Dashboard is deployed.

26 WebFOCUS

Accessing Dashboard

You can access the following pages directly by entering the URL:

http://hostname [:port]/ibi_apps/bid/pagename

where:

pagename

In one of the options listed in the following table. The first column lists the pagenames, the second column lists their descriptions.

DescriptionPage Name

Opens the View Builder login page.vblogin

Opens the public views index page. This page lists allexisting public views.

mpv

Opens the general public view.public

Opens the specified public view. Viewname is automaticallygenerated when the view is created in the View Builder.

viewname_mpv

Opens the specified group view. Viewname is automaticallygenerated when the view is created in the View Builder.

viewname_gbv

Opens the user login page.login

Opens the change password page.passchange

Using the Mozilla Firefox Browser With Dashboard View Builder

How to:

Change Firefox Browser Settings

If you are accessing the Dashboard View Builder using the Mozilla Firefox browser, there isa security setting that must be changed. When you are creating a Public or Group View, thebrowser setting "security.checkloaduri" must be set to false so that the View Builder cancheck image dimensions (for example, an image file you are using for the logo in your banner).This setting change is required due to the fact that Firefox does not allow access to fileproperties by default.

Note: This setting change is only required for the Dashboard administrators using the ViewBuilder. Dashboard users do not need to make any changes.



How to Change Firefox Browser SettingsProcedure:

1. In the Firefox browser address bar, enter about:config.

2. Press Enter or click Go.

3. In the Preference Name column, scroll down to security.checkloaduri.

4. Double click security.checkloaduri to change the value to false.

Customizing DashboardWhen you create a customized view of Dashboard you can:

Create a unique customization for each public and group view. This includes selecting atemplate, selecting custom colors, positioning the Domain Tree, Role Tree and banner,inserting a company logo, and much more.

Create the default content blocks that the user sees when a Dashboard public or groupview is opened.

Create and edit public and group views.

Identify the Managed Reporting password that the Dashboard will use to connect thepublic user to Managed Reporting.

Set a default user ID and password for the public user. When a user ID and passwordare set, the public user does not have to enter logon information when accessing a publicview.

Create Role Trees for Managed Reporting User Groups.

When a user opens Dashboard, a single logon page appears. You can set a user ID andpassword for the public user so they do not have to enter logon information when theyopen Dashboard.

For additional security, you can configure the Dashboard logon page so users log on toboth Dashboard and the WebFOCUS Reporting Server. For more information, see theInstallation and Configuration manual for your platform. You can also integrate theDashboard logon with other systems such as Web server or LDAP security. See theWebFOCUS Security and Administration manual for details.

28 WebFOCUS

Customizing Dashboard


In this section:

Working With Environment Properties

Local Machine Properties

Web Component Properties

WebFOCUS Client Properties

Managed Reporting/ReportCaster Properties

Data Server Properties

Project Development Properties

A WebFOCUS environment consists of a Web server, a WebFOCUS Client, and WebFOCUSReporting Servers. To add a WebFOCUS environment, you specify a Web server containingthe WebFOCUS Client and the connection method it uses (servlet, CGI, or ISAPI). DeveloperStudio then finds all of the WebFOCUS Reporting Servers that the WebFOCUS Client canaccess.

You add WebFOCUS environments and edit existing environments in Developer Studio usingthe WebFOCUS Environment Properties dialog box or the Explorer tree itself. Use either ofthese approaches to create and manage additional environments, such as test andproduction.

Working With Environment Properties

How to:

Add a WebFOCUS Environment

When you set up access to WebFOCUS environments, your settings are retained when yourestart or even reinstall Developer Studio. WebFOCUS environment settings are normallystored in:

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

where:

user_id

Is your logged on Windows ID.



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.

In Developer Studio Version 5 Release 3 and earlier, this file was named wfscom.wfs.When you launch Developer Studio Version 7 Release 1 and higher, an existing wfscom.wfsfile is renamed to wfscom.xml.

If an existing wfscom.xml or wfscom.wfs file existed and had a localhost environment,the existing localhost environment gets updated with settings based on the installationand configuration options selected during the installation. If localhost did not exist, it iscreated with settings based on the installation and configuration options selected duringinstallation.

User IDs and passwords stored in wfscom.xml are encrypted to keep them confidential.

WebFOCUS environment properties apply to your current Developer Studio configuration.It will not impact other users or the WebFOCUS configuration.

How to Add a WebFOCUS EnvironmentProcedure:

Note: You can also add a WebFOCUS Environment by right-clicking WebFOCUS Environmentson the Developer Studio Explorer and selecting Add.

30 WebFOCUS


1. Select the File menu and choose Show Environments. The Environments List dialog boxopens as shown in the following image.

This dialog lists all the WebFOCUS Environments defined for Developer Studio, whichmay already be defined if previously installed. If not installed, only the localhostenvironment exists. To edit an existing environment, select it and click Properties.

Note: The Set Development Environment button does not pertain to Managed Reportingand is only used for a self-service deployment paradigm.

2. Click the Add button.



The WebFOCUS Environment Properties dialog box opens as shown in the followingimage. At the top part of the dialog box is the Description text box followed by theEnvironment Settings section where you will find up to six clickable objects. At the bottompart of the dialog box are two sections, Web Component and Web ComponentAuthentication. In the Web Component section, you enter the IP Address (hostname),select Protocol type, enter Port number information, and optionally supply an HTML Alias.In the Web Component Authentication section, you enter User ID and Passwordinformation.

Use the WebFOCUS Environment Properties dialog box to define which componentsmake up the environment. You can optionally enter authentication information forcomponents that require logon credentials.

32 WebFOCUS


3. At the top of the window, type a Description for the WebFOCUS environment. Thisdescription will appear in the Developer Studio Explorer under WebFOCUS Environments.

As shown in the following image, the top area contains a series of buttons, arranged ina diagram, each of which depicts one component in the WebFOCUS environment. TheWeb Components button is selected by default. Note that the Project DevelopmentEnvironment Settings are only available in the full edition of Developer Studio.

4. At the bottom of the Web Environment Properties page, specify the information neededto access the Web server.

For some environments, after you specify the Web server, all other options are set bydefault. If the WebFOCUS environment you are accessing does not use default settingsor the components require authentication, click the appropriate button in the top paneto provide parameters. The sections that follow explain the parameters available foreach component.

Note: WebFOCUS environment properties must be supplied in a particular order. Forexample, if Web server security is enabled, you cannot set the WebFOCUS Client scriptname until you have provided valid Web server credentials. Similarly, you cannot retrievea list of WebFOCUS Reporting Servers until you have provided a valid WebFOCUS ClientPath. As you select a component button in the dialog box, Developer Studio ensuresthat it has the necessary information before it displays that component's properties inthe lower part of the dialog box. If the required information is not available, you will notbe able to proceed to the next component.

Local Machine PropertiesLocal Machine properties are optional. You can select the Local Machine button to indicatewhether to cache files when accessing the WebFOCUS environment.



The following image shows the WebFOCUS Environment Caching section of the WebFOCUSEnvironment Properties dialog box.

In caching, copies of files or information stored on a remote machine are temporarily storedon your local Developer Studio machine. Developer Studio then works with the locally storedfiles. Caching speeds Developer Studio performance because remote machines are notaccessed and queried every time you request information. This is especially useful whenaccessing mainframes or when a network connection is slow. However, caching should notbe used when multiple developers are working with the same files because the possibilityexists that you may overwrite each others changes. By default, caching is not enabled.

Two properties are available:

Cache remote directory and file information. This option caches information aboutfiles stored on the WebFOCUS environment. This does not actually cache files, onlyinformation about them. If selected, Developer Studio does not re-query the WebFOCUSReporting Server every time it needs a list of files stored on the server.

Enable file content caching. This option caches files normally stored on the server.Developer Studio only retrieves files once and then when you wish to read or edit them,it uses a cached copy. Be aware that when you edit a cached file, the edited cached fileis returned to the server and replaces the actual file on the server.

Developer Studio retrieves information and files the first time you request them and thencaches them locally. Developer Studio then uses the cached copies until Developer Studiois restarted or you click the Clear buttons for each level. You can perform a manual refreshand clear all cache files by clicking View, then Refresh, or by pressing F5. Refresh is performedfor the area that is selected in the Explorer when you perform this action.

Note:

If you create a new synonym, you must manually perform a refresh to view the new filesin the Developer Studio Explorer when caching is enabled.

You cannot use the caching options for the local development environment if the SourceControl feature is enabled.

34 WebFOCUS


Web Component PropertiesThe Web Components button is normally selected by default. Web Component propertiesspecify how Developer Studio accesses the Web server. The Web server must be identifiedbefore any other components. The following image shows the Web Component section ofthe WebFOCUS Environment Properties dialog box.

The following properties are available:

Host Name/IP Address. This specifies the hostname or IP address where your Webserver is running. This field is required and will not default. For a network installation,ensure this is the actual hostname and not localhost.

Protocol. This is the protocol to use for accessing the Web server (HTTP, HTTPS, FTP).

Port. This the TCP/IP port for accessing the Web server. Port 80 is the default for HTTPwith most servers. However with Tomcat, this is port 8080.

HTML Alias. This is the alias defined on the Web server for the environment's ibi_htmldirectory. If your WebFOCUS environment does not use the default ibi_html alias, specifythe custom alias defined on the remote Web server. Developer Studio must know thisalias to retrieve key information from WebFOCUS Client files such as cgipath.js andibiapplets.txt.

Use Default. This specifies whether to use the default ibi_html alias. Leave this checkedunless you change the HTML Alias.



Web Component Authentication. This specifies whether authentication is required onthe Web server. To set security, select Basic in the drop-down list and type a Web serverUser ID and Password. If this is set to None, the Web server must allow anonymousaccess. Additional custom security methods can be added, such as SiteMinder. For moreinformation, see the WebFOCUS Security and Administration manual.

WebFOCUS Client PropertiesWhen you click the WebFOCUS Client button, Developer Studio makes a connection to yourWeb server to retrieve information about the WebFOCUS environment. Therefore, you mustfirst specify Web Component properties and your Web server must be running. The followingimage shows the WebFOCUS Client section of the WebFOCUS Environment Properties dialogbox.

Note: If the Client Path field is empty and the Use Default option is selected, there is aproblem connecting to the WebFOCUS Client. Ensure your Web server is started and thatyou typed the correct properties on the Web Components page. If you cannot connect, contactyour WebFOCUS Administrator.


Client Path. This specifies how calls are made from Developer Studio to the Web server.By default, when you add a new WebFOCUS environment, it is set to use the WebFOCUSServlet with the default ibi_apps context path:

/ibi_apps/WFServlet

36 WebFOCUS


If the WebFOCUS environment does not use servlet or uses a non-default context path,uncheck Use Default and provide the correct Client Path. Common default settings appearin the Client Path drop-down list. They are:

/ibi_apps/WFServlet (Servlet)

/cgi-bin/ibi_cgi/ibiweb.exe (CGI)

/cgi-bin/ibi_cgi/webapi.dll (ISAPI)

Servlet is required for Managed Reporting or Tomcat. If the Client Path is incorrect forthe environment, you receive an error when you click the Data Servers button on the topof the page. If you do not know your path, ask your WebFOCUS Administrator or checkthe WebFOCUS Administration Console of the environment to which you want to connect.The Client Path settings for the environment are located under Utilities and Client Selection.

Select Language. This specifies the language of the WebFOCUS Client.

Supply Credentials. If required, you can check this box and type a WebFOCUS ClientUser ID and Password. These credentials are only used for Project-based developmentand do not apply to Managed Reporting. They are used to ensure that a developer isauthorized to perform certain activities such as deploying an application and writing toWeb server directories.

WebFOCUS Client user IDs are the same IDs used to access the WebFOCUS AdministrativeConsole in Developer mode. If authentication is enabled for the Console and these fieldsare empty, you are prompted to log on to the WebFOCUS Client when you access theenvironment. Your WebFOCUS Administrator will let you know if you must supplyWebFOCUS Client credentials.

When the correct WebFOCUS Client Path is provided, you can specify properties for theremaining component.

Managed Reporting/ReportCaster PropertiesIf you plan to work with Managed Reporting (MR) and/or ReportCaster, you can optionallyselect the Managed Reporting/ReportCaster button. This allows you to set logon credentialsor change the default Managed Reporting repository.

This feature is not applicable to the Power Reporter edition of Developer Studio.



The following image shows the Managed Reporting Repository section of the WebFOCUSEnvironment Properties dialog box.


Path. This lets you specify a non-default Managed Reporting repository. For a defaultManaged Reporting repository, the Path field is empty and the Use Default check box isselected. Your WebFOCUS Administrator may instruct you to deselect the Use Defaultcheck box and enter a path, for example:

e:\user_test\basedir01/usr/user_test/basedir01

You will not see a value in this field when Use Default is checked, because it is notcurrently possible for WebFOCUS to detect the list of potential repositories on the Webserver.

Note: ReportCaster only supports the Managed Reporting Repository as defined in theWebFOCUS Client Configuration file MR_BASE_DIR.

Supply Credentials. If required, you can check this box and type a ManagedReporting/ReportCaster logon. Developer Studio will automatically use this logon eachtime it accesses MR or ReportCaster. If this is blank, Developer Studio prompts you forthe logon when it requires access to MR or ReportCaster.

Note: If your WebFOCUS Administrator has integrated MR authentication with Web serverauthentication, do not supply MR credentials here. They will be picked up from the Webserver component properties.

38 WebFOCUS


Data Server PropertiesYou can set authentication and view available WebFOCUS Reporting Servers by clicking theData Servers button. When you select Data Servers, Developer Studio connects to theWebFOCUS Client and retrieves a list of servers from its communication configuration file(odin.cfg).

The following image shows the WebFOCUS Servers section of the WebFOCUS EnvironmentProperties dialog box.

The following property is available:

Supply Credentials. If checked, you can type a WebFOCUS Server ID and password for theserver highlighted in the list. Clicking Set stores the credentials with the environmentproperties, and the ID entered is shown next to the server in the list. The credentials arechecked the next time you use a feature on that server, not when you click the Set button.

Project Development PropertiesProject development is not a feature supported by Managed Reporting. For more informationabout this feature, see Project Development Properties in the Introducing WebFOCUS andDeveloper Studio chapter in the Developer Studio Application Development Getting Startedmanual.



40 WebFOCUS


WebFOCUS

Creating Domains, Groups, Roles, and Users2Topics:

You can create domains, groups, roles,and users with the Managed ReportingAdministration interface. Administratorscreate domains, add them to groups, andassign these groups to users anddevelopers. Developers can then buildreports in these domains for the users.Administrators can also create roles tomake it easier to assign combinationsof privileges to the users and developers.

Using the Managed ReportingAdministration Interface

Creating Domains

Creating Groups

Creating Users

Creating Roles

Customizing the Interface


Using the Managed Reporting Administration InterfaceThe Managed Reporting Administration interface can be accessed from the link on theWebFOCUS Welcome page, the Developer Studio toolbar (except for the MR Developer forWindows edition), and the toolbar in the Managed Reporting Domain Builder applet.

You can also access the interface directly from your Web browser by entering the followingURL:

http://webserver/ibi_apps/mradmin

where:

webserver

Indicates the name of the Web server that is running the Managed ReportingAdministration interface.

Depending on your site's Managed Reporting security settings, you may be prompted foryour MR credentials. The logon page is bypassed when coming from the toolbar link inDomain Builder, and from the toolbar in Developer Studio when Developer Studio has yourvalid MR credentials.

At the top of the interface, a series of tabs take you to pages where you can perform varioustasks. Each page has a list pane on the left and a detail pane on the right, as shown in thefollowing image.

42 WebFOCUS

Using the Managed Reporting Administration Interface

The tabs that appear, and your capabilities on each of the pages, depend on your role andprivileges:

MR Administrators have full access to each of the four tabs: Groups, Users, Roles, andDomains.

Users with Group Administration privileges have limited access to the Groups and Userstabs.

Developers with the Data Server privilege have limited access to the Domains tab.

Some aspects of the interface’s behavior can be customized. For more information, seeCustomizing the Interface on page 62.

Creating Domains

In this section:

Working With the Server and Application Path Properties

The Domains tab is used by Managed Reporting Administrators to create, edit, and deletedomains. Developers who have the Data Server privilege can use the Domains tab to editthe Server and Application Path properties on domains to which they have developmentaccess. To learn how to control which domains developers have development access to,see Assigning Development Domains on page 51.


2. Creating Domains, Groups, Roles, and Users

The following image shows four domains in the list pane on the left, and the properties forthe selected domain, Sales Reporting, in the detail pane on the right.

You can change the alphabetical sort order of the domains in the list pane by clicking theName column.

You can create a new domain by clicking the New icon on the toolbar and entering thename of the domain in the Name field of the detail pane. Optionally, you can define a specificReporting Server and/or server application path to be used for reports run from this domain.For more information about these properties, see Working With the Server and ApplicationPath Properties on page 45.

You can modify a domain's properties by selecting it in the list and clicking the Edit iconon the toolbar. You can also double-click a domain in the list to display and/or edit thedomains properties.

You can delete domains by selecting them in the list pane and clicking the Delete iconon the toolbar. You can also press the delete key to delete selected domains. The list panesupports multi-select functionality by holding down the Shift or Ctrl key while selecting.

44 WebFOCUS

Creating Domains

Note: Administrators can create, edit, and delete domains from within Developer Studio(except for the MR Developer for Windows edition) and in the Managed Reporting DomainBuilder applet. Developers with the Data Servers privilege can edit a domain's Server andApplication Path properties from within these tools. Administrators can also create domainswith the MR Change Management load utility. For details, see Change Management on page189.

Working With the Server and Application Path Properties

How to:

Specify the Application Path

Managed Reporting administrators and developers (if the developer has the Data Serverprivilege) can edit a domain's Server and Application Path properties. By default, theseproperties are initially unselected and the default Reporting Server appears in the Serverlist as shown in the following image.

When the Server option is unchecked, WebFOCUS determines which server to use for reportrequests and displays it in the list. Typically, the server shown is the IBI_REPORT_SERVERvalue defined in the Configuration area of the WebFOCUS Administration Console in theReporting Server selection under Client Settings. A different server may be shown in somecustomized configurations.

You can check the Server option to choose a server from the list when you have multipleservers and want to control which server is used to run reports from this domain.



When the Application Path option is unchecked, the WebFOCUS Reporting Server determineswhich application folders to search for metadata and included procedure files. The searchpath is determined by a number of factors including APP PATH commands found duringserver profile processing and in the report request itself. For more information about serverprofile processing, see the WebFOCUS Security and Administration manual.

You can check the Application Path option to override the server's search path for reportsrun from this domain. When you check this option, a request is sent to the server shown inthe Server list to retrieve the set of available applications. Depending on your securityconfiguration, you may be prompted for your server credentials.

How to Specify the Application PathProcedure:

1. Select the desired application(s) from the Available Applications list.

2. Click the Add icon to move the desired applications to the Selected Applications list.

Alternatively, you can double-click applications to move them to the Selected Applicationslist.

You can also remove applications from the Selected Applications list by selecting theapplication(s) and clicking the Remove icon.

3. To reorder items in the Selected Applications list, select an item and click the Move Upicon or the Move Down icon.

Note: The server searches applications in top to bottom order.

4. Click Save to save the applications you specified for the Application Path.

Creating Groups

How to:

Create a Group

Add Users to a Group

Remove Users From a Group

Add or Remove Domains in a Group

The Groups tab is used by Managed Reporting Administrators to create, edit, and deletegroups. Users with Group Administration privileges have limited access to the Groups tab.For more information, see Assigning the Group Administrator Privilege on page 50.

46 WebFOCUS

Creating Groups

Managed Reporting groups are used to associate users with domains. Users can not accessdomain resources, including report procedures and some Report Library content, unlessthey belong to groups that include those domains. An exception is users with MRadministration privileges, who always have access to all groups and domains in the system.

You can also create a customized Dashboard view for each group if you want to presenttailored presentation and content to users of these groups. For more information, seeCreating Public and Group Views on page 91.

How to Create a GroupProcedure:

1. In the Managed Reporting Administration interface, click Groups.

2. Click the New icon.

3. Type a name for the Group.

4. Click Save.

How to Add Users to a GroupProcedure:


2. In the Existing Groups list, double-click the group to which you want to add users.

3. In the User Information field, click the Add Users tab.

4. Double-click users in the All Users list to move them to the Users to Add list.

5. When you have selected all of your users, click the Add icon.

6. Click Save.

How to Remove Users From a GroupProcedure:


2. In the Existing Groups list, double-click the group from which you want to remove users.

3. In the Member Information field, click the Members tab.

4. Double-click users in the This group's members box to move them to the Members toremove from this group box.

5. Click Save.

Note: The Add and Remove buttons above the Members to remove from this group box onlyadd or remove users from that box, users are not added or removed from the group untilyou click Save.



How to Add or Remove Domains in a GroupProcedure:


2. In the Existing Groups list, double-click the group to which you want to add or removedomains.

3. In the Domain Information field:

To add domains, double-click the domains in the Available Domains box to add themto the This group's domains box.

To remove domains, double-click the domain in the This group's domains box.

4. Click Save.

Note: The Add and Remove buttons above the This group's domains box only add or removedomains from that box, domains are not added or removed from the group until you clickSave.

Creating Users

In this section:

Searching for Users

Assigning the Group Administrator Privilege

Assigning Development Domains

Setting Up Users to Save Parameter Values

How to:

Create a User

The Users tab is used by Managed Reporting Administrators to create, edit, and deleteusers. Users with Group Administration privileges have limited access to the Users tab. Formore information, see Assigning the Group Administrator Privilege on page 50.

How to Create a UserProcedure:

1. In the Managed Reporting Administration interface, click Users.


The New User dialog box opens in the right pane.

48 WebFOCUS

Creating Users

3. Enter the General Information:

User ID. Is the user ID used to sign on to this user account. This value can be amaximum of 128 characters and cannot include spaces or double quotation marks (").You can restrict other characters from this field. For details, see Customizing the Interfaceon page 62.

You can edit the User ID value after the account is created. This is a required property.

Name. Is the description displayed for the user account in most places of ManagedReporting and ReportCaster. If you have many users, you may consider a conventionsuch as Lastname, Firstname for values in this field. This will make it easier to locateusers in the lists. This is a required property.

Password/Confirm Password. You can assign a password for the user account orleave it blank. At any time, you can reset the user's password. The user can also resettheir password themselves on the logon page. This is an optional property.

Email Address. An e-mail address is required for the Report Library, but you do notneed to include it for ReportCaster scheduling without using the Report Library.

In certain Managed Reporting security configurations, the Name, Email Address,Password, and Confirm Password fields are disabled because WebFOCUS cannot updatepassword information stored in the external authentication directory. For example, whenyou are configured to authenticate to LDAP/Active Directory, the Password and ConfirmPassword fields are disabled because an MR Administrator cannot update yourauthentication directory. Additionally, when configured for LDAP/Active Directoryauthentication, RDBMS authorization, and the property USER.INFO.LOOKUP is set to'dual', the Name and Email Address fields are also disabled because this user informationcomes from your authentication directory. Your WebFOCUS Administrator controls thesesettings using the WebFOCUS Administration Console. For more information, see ManagedReporting Security Settings in the WebFOCUS Security and Administration manual.

Role. Is the Managed Reporting role. For details on roles, see User Roles Defined onpage 54.

Disable logon rights for this user. Prohibits the user from logging into ManagedReporting.

4. Assign additional Privileges (optional).

Once you select a role, a set of privileges is automatically assigned to the user andcannot be changed. However, you can add additional privileges as necessary. For detailson user privileges, see User Privileges Defined on page 59.

5. Select the groups for which you want the user to be a member.

To add a user to a group, double click the group in the Available Groups list to move itto the Member of list.



6. Click Save.

Note: To modify or delete a user, select user from the Users tab and click the appropriateicon.

Searching for UsersThe Managed Reporting Administration interface supports the ability to search for entriesby name or user ID. Large search result sets are broken up into a series of navigable pagesto improve performance.

In the Groups tab, you can perform pattern searches. For example, you can enter “Sa” andit will return all of the groups that begin with those two letters. In the Users tab, you canperform pattern searches by name or user ID.

To restore your list after performing a search, click Refresh in your browser or type an asterisk(*) in the search text box and click the green arrow.

Assigning the Group Administrator Privilege

How to:

Assign the Group Administrator Privilege

A Managed Reporting administrator can delegate some of their administration responsibilitiesto designated users. Group administration is a user privilege that enables a user to manageone or more of the groups to which they belong. From the Managed Reporting Administrationinterface, the group administrator can add or remove any user from the group(s) theyadminister. However, a group administrator cannot add, remove, or change the domainsthat are associated with their groups.

Group Administrators can also create users and assign them roles and privileges. However,Group Administrators cannot:

Assign a role higher than their own role (from high to low, roles are Developer, AnalyticalUser, User).

Assign a privilege they do not possess.

Edit existing users if the user belongs to a group(s) that the Group Administrator doesnot administer.

The Group Administrator privilege can be assigned by an administrator to any user; however,it cannot be assigned to a role. A user can be the Group Administrator for more than onegroup and there can be multiple Group Administrators for one group. Group Administratorsuse the same Managed Reporting Administration interface that Administrators do, thoughthe features presented to them are limited.

50 WebFOCUS

Creating Users

How to Assign the Group Administrator PrivilegeProcedure:

1. In the Managed Reporting Administration interface, click Users.

2. Select the user you want to grant the Administrator privilege to and click the Edit icon.

3. In Group & Domain Management properties, select the Groups tab.

4. In the Member of list, select the Group to which you want the user to be the Administrator.

5. Click the Administrator icon.

An asterisk appears in the Administrator column of the Member Of list to indicate theuser is the Administrator of the group.

6. Click Save.

Assigning Development DomainsWhen a user is assigned the Developer role (or a role that is based on the Developer role)the Domains tab appears in the Group & Domain Management area of the User Propertiespane.



By default, the Developer in all assigned domains check box is selected. This means thatthe user is a developer for all the domains for which they have access. The domains shownin the Assigned Domains list are available in the Domain Builder interface (accessed fromthe blue Managed Reporting toolbar or in Developer Studio), the Domains environment, andfrom Dashboard.

If the Developer in all assigned domains check box is deselected you can specify whichdomains the user can develop in. Only the domains listed in the Developer Domains list onthe right appear in the Domain Builder interface (or Developer Studio). The domains in theAssigned Domains list on the left appear in the Domains interface and in Dashboard.

52 WebFOCUS

Creating Users

Setting Up Users to Save Parameter Values

How to:

Set Up Users to Save Parameter Values

You can set up users so when they run reports they can save the parameter values theyselect as a My Report. The Save Entered Values privilege enables users to save parametervalues as a My Report. The Save Entered Values privilege is not enabled by default for anyuser or role. This privilege is not available for the Dashboard Public User.

The WebFOCUS Client amper auto-prompting feature inserts a Save Parameters button onthe form for users that have the Save entered values privilege. Developers can also add theSave Parameters button to a form from the HTML Composer. For complete details, see theWebFOCUS Managed Reporting Developer's Manual.

Note: If the report properties are changed and the Prompt for Parameters property isdeselected, the user will not see the Save Parameters button when they run the report.

How to Set Up Users to Save Parameter ValuesProcedure:

1. Open the Managed Reporting Administration interface.

2. For the user or role, select the Save entered values privilege.

3. Click Save to save your changes.

Note: If the user is currently logged into Managed Reporting they must log out and backin again for the change in their privileges to take effect.

Creating Roles

In this section:

User Roles Defined

User Privileges Defined

WebFOCUS Managed Reporting supports roles, making it easier to administer large numbersof users. A role is a collection of user privileges and each user has one role. Users inheritthe privileges that are associated with their role; in addition, they can also be assigned otherprivileges as necessary. Roles are created and maintained by a Managed ReportingAdministrator. Roles can be assigned to users by MR Administrators and MR GroupAdministrators.



There are several base roles (User, Analytical User, Developer, and MR Administrator) andcustom roles (Run Only User, Power User, and Content Manager) provided with ManagedReporting. Custom roles extend base roles and provide flexibility by allowing the administratorto add or remove certain privileges. You can create custom roles of your own as well ascustomize the provided base and custom roles.

Note:

The Dashboard Role Tree and the Managed Reporting role features are not related.Dashboard Role Tree allows an administrator to define a set of Managed Reporting reportsthat can be assigned to users. One Role Tree is allowed per Managed Reporting group.The Managed Reporting role feature allows an administrator to more easily manageprivileges assigned to users. Each user can have only one role regardless of the numberof groups to which they belong.

The base roles (User, Analytical User, Developer, and Administrator) cannot be removedfrom the Managed Reporting Administration interface. You can remove any custom rolesyou create, and the custom roles (Run Only User, Power User, and Content Manager)that are included with WebFOCUS.

User Roles Defined

Reference:

User Role Matrix

Role Inheritance

Each user role has a set of default and optional privileges. The following table provides adescription of each role along with a list of associated privileges.

PrivilegesRole Description

Default Privileges: none

Optional Privileges: Enable accessibility features(Section 508), Save entered values, Library

The Save My Reports, Share My Reports,Advanced, Data Server, ReportCasterAdministrator, and Schedule privileges are notavailable for the User role.

Users with the User role can runStandard Reports (in immediate anddeferred mode) and can run shared MyReports created by other users.

54 WebFOCUS

Creating Roles


Default privileges: Library

Optional privileges: Enable accessibility features(Section 508)

The Save My Reports, Share My Reports,Advanced, Data Server, ReportCasterAdministrator, and Schedule privileges are notavailable for the Library Only User role.

The Library Only User role providesthe ability to create Dashboard userswho can only access content stored inthe Report Library. This content can beviewed in the Report Library and in aDashboard page when displayed as alist, launch, or output block. LibraryOnly Users cannot run reports, view theDomain Tree, view the Role Tree,access other WebFOCUS environments,and have limited access to Dashboardcomponents.

Default privileges: none

Optional privileges: Enable accessibility features(Section 508), Save entered values, Library

The Save My Reports, Share My Reports,Advanced, Data Server, ReportCasterAdministrator, and Schedule privileges are notavailable for the Run Only User role.

The Run Only User role is based onthe Analytical User role. The Run OnlyUser role can do everything a user withthe User role can do. In addition, thisuser can access the Assistant toolsand create My Reports. The Run OnlyUser cannot save My Reports.

Default privileges: Save My Reports

Optional privileges: Share My Reports,Advanced, Enable accessibility features (Section508), Save entered values, Schedule, Library

The ReportCaster Administrator and Data Serverprivileges are not available for the AnalyticalUser role.

The Analytical User role can doeverything a user with the Run OnlyUser role can do. In addition, the usercan save My Reports from the Assistanttools. If granted, the user can alsoshare My Reports and create CustomReports. The user can also savedeferred output from the DeferredStatus interface.

Default privileges: Save My Reports, Share MyReports, Advanced

Optional privileges: Enable accessibility features(Section 508), Save entered values, Schedule,Library

The Data Server and ReportCaster Administratorprivileges are not available for the Power Userrole.

The Power User role is based on theAnalytical User role. The Power Userrole is another example of how you cancustomize roles. It extends theAnalytical User role with the Advancedand Share My Report privileges.




Default privileges: Save My Reports

Optional privileges: Share My Reports,Advanced, Enable accessibility features (Section508), Data Server, Save entered values,Schedule, Library

The ReportCaster Administrator privilege is notavailable for the Developer role.

The Developer role can do everythingan Analytical User can do. In addition,they have access to the Domain Builderwhere they can create StandardReports and Reporting Objects forthose domains to which they haveaccess. By default, users who have theDeveloper role do not have access tothe Data Servers feature unless it isgranted to them explicitly or theDeveloper role is changed to have DataServer selected.

Default privileges: Save My Reports, Share MyReports, Advanced, Data Server

Optional privileges: Enable accessibility features(Section 508), Save entered values, Schedule,Library

The ReportCaster Administrator privilege is notavailable for the Content Manager role.

The Content Manager role is basedon the Developer role. The ContentManager role is an example of acustomized role. It extends theDeveloper role with the Data Server,Advanced, and Share My Reportprivileges.

Default privileges: Save My Reports, Advanced,Data Server

Optional privileges: Share My Reports, Saveentered values, ReportCaster Administrator,Schedule, Library, Enable accessibility features(Section 508)

Note: The Enable accessibility features (Section508) optional privilege is available beginning inVersion 7 Release 6.5.

The MR (Managed Reporting)Administrator role has unrestrictedaccess to Managed Reporting.

If a user with the MR Administrator rolebut without the ReportCasterAdministrator privilege creates otherMR Administrators, the ReportCasterAdministrator privilege will not beavailable to grant to the user.

When the ReportCaster Administratorprivilege is assigned, the Schedule andReport Library privileges areautomatically assigned and theSchedule privilege cannot beunassigned.

56 WebFOCUS

Creating Roles

User Role MatrixReference:

The following table lists each user role and its corresponding default and optional privileges.The role abbreviations below are used in the table:

LO = Library Only User

US = User

RO = Run Only User

AU = Analytical User

PU = Power User

DV = Developer

CM = Content Manager

MA = Managed Reporting Administrator

MACMDVPUAUROUSLOUser Roles

Privileges (O=Optional; D=Default; F=Fixed )

OOOOOOOOEnable accessibility (Section 508)

FDODOAdvanced

DDOData Server

OOOOOOOSave Entered Values (My Reports)

FFFDDSave Reports (My Reports)

ODODOShare Reports (My Reports)

OOOOOSchedule (ReportCaster)

OOOOOOOFLibrary (ReportCaster)

OAdministrator (ReportCaster)

Note: Optional privileges are turned off initially, but can be turned on. Default privileges areturned on initially, but can be turned off. Fixed privileges are turned on and can not be turnedoff. Also, the Enable accessibility features (Section 508) optional privilege for the ManagedReporting Administrator role is available beginning in Version 7 Release 6.5.



The following table lists the Managed Reporting functional capabilities that are provided withthe default privileges for each user role.

MACMDVPUAUROUSLOUser Roles

Functional Capabilities *

*Limited dashboard component access

*Only access Report Library content

*******Run other users' shared My Reports

*******Run Standard Reports (immediate)

*******Run Standard Reports (deferred)

******Access Assistant tools (see Note)

***Advanced Graph Assistant

*****Save My Reports from Assistant tools

*****Save deferred output

***Create Standard Reports & ReportingObjects

*Create Managed Reporting Users

*Manage and promote User’s MyReports to Standard Reports

Note: Assistant tools refers to the HTML Report Assistant, HTML Graph Assistant, andPower Painter tools. The Power Painter license code must be specified in the WebFOCUSClient configuration to make Power Painter accessible to users.

Role InheritanceReference:

Inheritance between the base role and any new roles you create only occurs at the time youcreate the role. If the base role is modified, changes will not be reflected in any roles youcreated based on this role.

58 WebFOCUS

Creating Roles

For example, you want to create a new role based on the Analytical User role. The AnalyticalUser role is a base role that is included with WebFOCUS Managed Reporting and has theSave My Reports privilege by default. When you create your new role, named NewRole, itinherits the Save My Reports privilege from the Analytical User base role. You can thencustomize the NewRole and add any available privileges.

If the Analytical User base role is modified after you create your NewRole, this does noteffect your NewRole since inheritance between roles only occurs at the time you create therole.

User Privileges Defined

How to:

Create a New Role

Customize an Existing Role

Privileges effect Managed Reporting and ReportCaster user interface behavior. Generallyspeaking, having a privilege means you can use the corresponding product feature. Oneexception is the 'inactive' privilege, which means you are denied logon rights to ManagedReporting. Privileges are associated with Roles. An MR Administrator or Group Administratorcan also assign privileges to users directly, though there are some limitations.

Note: When ReportCaster is not installed, the ReportCaster Schedule, Library, andAdministrator privileges are not available.

The following is a table that lists the privileges and a description of each privilege.

DescriptionPrivilege

General

Specifies that a user can utilize Section 508 compliant onlinehelp, user interfaces, and tools.

Enable accessibilityfeatures (Section 508)




Only users who are assigned the Advanced privilege, regardlessof their role, are enabled to:

Create and edit Custom Reports, which appear in their ownfolder under the My Reports tab in the Domains environment.Unlike other My Reports, Custom Reports are not built fromReporting Objects. Users build these reports with toolsincluding the text editor, Power Painter, Report Assistant,and Graph Assistant. Note that only users who are assignedthe Advanced privilege can create Custom Reports.

View all data sources in the domain path when creatingdynamic parameters using the Variable Editor. Without theAdvanced privilege, users can only view data sources usedin the Reporting Objects.

Advanced

Specifies whether a user can access the Domain Builder DataServers component. Also controls whether or not the server andapplication path properties on a domain, report, or ReportingObject can be modified by the user.

Data Server

My Reports

Enables users to save their selected parameter values as a MyReport. When a user runs the My Report, a launch page openswith their parameter values already selected and they can thenrun the report.

Save Entered Values

Enables the user to create and save My Reports. The Advancedprivilege is also needed to create My Reports that are CustomReports.

Save Reports

Is required for a user to share a My Report or Custom Reportwith other users who have access to the same domain. Once auser shares a My Report or a Custom Report, other users canrun the report and copy the report into their own My Reports tabif they have the Save My Reports privilege. The Share My Reportsprivilege does not have to be active for a user to run or copyreports that have been shared by others.

Share Reports

60 WebFOCUS

Creating Roles


ReportCaster

Designates the user as a ReportCaster Administrator.Administrator

Allows a user to schedule procedures using ReportCaster. Thiscapability is available only when ReportCaster is installed.

Schedule

Allows a user to access the Report Library, which is aReportCaster storage and retrieval facility. This capability isavailable only when ReportCaster is installed and configuredwith the RDBMS repository option.

Library

How to Create a New RoleProcedure:

1. In the Managed Reporting Administration interface, click Roles.


The New Role dialog box opens in the right pane.

3. Type the Role Name.

4. Select the Base Role.

This is the role for which the new role is based. For details on what privileges come witheach role, see User Roles Defined on page 54.

5. Select the Privileges. For details on privileges, see User Privileges Defined on page 59.

6. Click Save.

How to Customize an Existing RoleProcedure:

1. In the Managed Reporting Administration interface, click Roles.

2. Click the Edit icon.

The Selected Role - rolename dialog box opens in the right pane.

3. Make any necessary modifications and click Save.



Customizing the InterfaceYou can customize some of the behavior of the MR Administration interface by editing itsconfiguration file, WebFOCUS76\config\mradmin-config.xml. You can:

Alter the default session time-out of 30 minutes by editing the value of the sessionTimeoutproperty.

Choose to not automatically load the user list when you click on the Users tab by settingthe autoLoadUserList property to false.

Change the number of users retrieved per page from the default of 100 by changing thevalue of the maxNumberOfUsersToShow property. Note that performance degradessignificantly above 200 items per page because of Java Script processing overhead.

Restrict specific characters from being entered in the User ID field when creating a newuser or editing an existing user. You can do this by editing the charFilter parameter.

Do not make other changes to this file unless instructed to do so by Customer Support.Changes to this file are recognized each time you click one of the three tabs in the interface.

62 WebFOCUS

Customizing the Interface

WebFOCUS

User Management3Topics:

The User Management tree object inDomain Builder enables ManagedReporting Administrators to view user'sreports. All types of reports aredisplayed, including My Reports, CustomReports, saved deferred output, anddistributed ReportCaster output.Managed Reporting Administrators canopen, edit, run, save, and deleteManaged Reporting user's reports. Savedand distributed output can be deleted orhave its properties changed. Both activeand inactive users are displayed andeach user displays regardless of whetherthey have created any reports.

User Management Tree Object inDomain Builder

Managing a User's Reports

Promoting a Custom Report to aStandard Report


User Management Tree Object in Domain BuilderWhenever a Managed Reporting Administrator logs into Managed Reporting, the DomainBuilder interface includes a User Management tree object. The User Management featureenables the Managed Reporting Administrator to access each user's reports. Each userdisplays regardless of whether they have created any reports. A folder is listed under eachuser, and contains the domains to which the user has access.

The User Management feature displays only for Managed Reporting Administrators. It doesnot display for Managed Reporting Developers.

When you open a folder, all types of user reports display, including My Reports, CustomReports, saved deferred output, and distributed ReportCaster output. Opening a user'sdomain shows either their report folders, which can be opened or a message that no userreports were found.

The following image shows four reports under Adam Abernathy's User's Reports folder.

64 WebFOCUS

User Management Tree Object in Domain Builder

The Managed Reporting Administrator can access reports made by inactive users. This isso they can easily delete or review these reports.

The Administrator can also access Custom Reports in a User's Reports folder if the userhas advanced privileges. The available options are the same as for My Reports. Theseoptions, shown in the following image for weekly_sales in the Custom Reports folder, areOpen, Edit Source, Run, Run Deferred, Delete, and Properties.


3. User Management

Managing a User's ReportsFrom the User Management tree shown in the following image, Managed ReportingAdministrators can perform the following tasks:

Open the report. It displays in Power Painter, Report Assistant, or Graph Assistant justas it does for the user. From there, you can make changes and then either Save to thesame file, or Save As a new file name (recommended because this leaves the originalreport untouched, which the user can view for comparison).

Edit the source code for the report directly with the Java Editor. Do not alter the internalDialogue Manager code in the procedure or the report may not run.

Run the report.

Run the report deferred.

Delete the report. A confirmation displays before the file is removed.

View and change properties. For example, a report can be unshared.

Access deferred output using the Deferred Status option on the browser toolbar. If areport is Run Deferred, it is run using the Managed Reporting Administrator's user ID.

66 WebFOCUS

Managing a User's Reports

Access users' Saved Parameter reports. You can edit saved parameter values that areselected by default when the auto prompt form launches or you can edit the -DEFAULTvalues for the procedure using the text editor. Note that the Edit Parameters option isnot available for auto prompt reports saved with parameter values.

Note: A report runs with the WebFOCUS Server ID of the Managed Reporting Administrator,not the user, which may produce different report results.

For finished output such as saved deferred output and distributed ReportCaster output, theoptions are different as shown below. The following image shows the Deferred ReportsOutput folder open with a highlighted deferred report item displaying a pop-up menu withtwo options: Delete and Properties.

The finished output cannot be opened, run, run deferred, or edited because it may containsecured data that is only visible to the user who ran the report initially. However, it can bedeleted and its properties can be changed.


3. User Management

Folder options include Close and Delete. The following image shows a pop-up menu for asubfolder of the Acme Manufacturing domain that contains two options: Close and Delete.

If delete is selected, a confirmation displays before deleting all the user's reports in thisfolder.

When you are logged in to Domain Builder as a Managed Reporting Administrator, you viewa snapshot of information available in User Management. However, Managed Reporting isa dynamic system. Users, domains, and reports are constantly being added, deleted, orchanged. In order to view the most recent status, you can use the refresh options below:

Reload User Management. Refreshes the list of users.

Reload User. Refreshes the list of domains to which the user has access.

Reload Domain. Refreshes the list of reports this user has created for this domain.

Promoting a Custom Report to a Standard ReportYou can promote a Custom Report to a Standard Report.

To accomplish this, a Managed Reporting administrator can copy and paste the CustomReport from the Custom Reports folder in User Management to the Standard Reports folder.When the Custom Report is moved into the Standard Reports folder, the properties of thenew Standard Report are the same as the Custom Report with the exception of the Shareproperty (since this is only available for My Reports). You can change the properties afteryou move the report to the Standard Reports folder.

The report can only be moved within the same domain, not across domains.

68 WebFOCUS

Promoting a Custom Report to a Standard Report

WebFOCUS

Managing Dashboard4Topics:

The following views are available withinthe WebFOCUS Business IntelligenceDashboard: Managing Public Views

The general public view. Managing Group Views

Custom public views. Managing Library Only Views

Group views. Managing Private Views

Library Only views. Logging On to Dashboard and ViewInheritancePrivate views.Managing UsersEach view has different rights and

different levels of security. Controlling the Idle Limit forAuthenticated and Public UsersThe Administrator controls the user's

access in the general public view, thecustom public view, group views, andLibrary Only views. This includes thedomains the users can view and certainfunctionality such as the Domain Search.

Handling Messages

Hiding Report Types in the DomainTree

Hiding the Share Report Option forFinished My ReportsThe Administrator also controls the look

of the Dashboard for all views.Displaying Optional Properties inDashboard

Creating Standard Reports inDashboard


Managing Public Views

In this section:

Managing Library Access in a Public View

Public views allow you to publish information on the Web and allow users to view reportsand other information without having to log in. There are two types of public views:

General public view. Contains any type of information and is intended for a wide varietyof audiences.

Custom public view. Provides detailed information targeted for specific groups of users.Access to a custom public view is the same as the general public view, with the defaultuser ID and password as the authentication information. Therefore, the public user canview reports and data that are available in the general public view and custom publicviews.

Custom and public views can be made secure through the addition of Web server security.To increase security on public views so that each public page has access only to the intendedinformation, you can restrict the public pages on the HTML files that display the view. Fordetails, see Creating Public and Group Views on page 91.

In addition, since the information in each public view (general or custom) may not be relevantto every public user who connects to Dashboard, you may want to prohibit certainfunctionalities by excluding the display of available domains from the general and custompublic views. In other words, you control the information a public user can view. To manageaccess so that users only see relevant information:

Allow access to only those domains with public information.

Eliminate the display of the Domain Tree and Role Tree in the Dashboard.

Eliminate the domain search.

Restrict the ability to run reports. If there is a high volume of traffic to a public view(general or custom), decrease the load on the Web server and the WebFOCUS ReportingServer by restricting users from running reports that directly access data. This is usefulif a public view contains launch blocks in which the report runs automatically when thepublic user opens the Dashboard.

To prevent public users from running reports, you can select only pre-built reports fromthe Report Library for the Role Tree, List blocks, and Launch blocks. To allow public usersto view updated reports without having to run them, use ReportCaster to generate reportoutput and send the output to the Report Library. The content for public pages can becreated using reports archived in the Report Library. For more information, see theReportCaster Development and Administration manual.

70 WebFOCUS

Managing Public Views

Managing Library Access in a Public ViewDashboard public pages include static content retrieved from the Report Library repository.This eliminates the need for the public page to execute a report each time the page is viewed.This functionality is implemented by increasing the capabilities of the public user from withinDashboard.

If a Managed Reporting user, designated as a public user, has Library privileges, theDashboard allows those privileges to be surfaced in a public view and also when a developeris building content pages for the public user.

A user who is designated as a public user must have Library privileges to view output. Librarycontent is displayed on the public page only if the content is available to the public user.Dashboard works within the constraints applied to user access of reports and does notoverride any access limitations imposed by the Report Library.

The available Library content includes the Library tab as a content page and Library contentadded to a Launch, Output or List block.

Managing Group ViewsGroup views allow you to create a secure Dashboard view for the members of an ManagedReporting repository group. Only members of the group can see the view. The user mustenter a valid Managed Reporting user ID and password to access the group view.

In each view, the Administrator selects a banner, the colors, composition, and content. Sincethe Administrator selects the content of the group view, the user can only access certainapplications or reports.

Users will not be able to personalize a group view. This means the users cannot customizethe look or the content.

When a user logs into Dashboard, they can see the views that have been created for eachgroup, including a link to "My View.” They can also personalize their own Dashboard view(not the group view).

A group member who has the Library Only User role can not access the Group View. A LibraryOnly Group View is available to these users.

Managing Library Only ViewsThe Library Only User role provides the ability to create Dashboard users who can only accesscontent stored in the Report Library. This content can be viewed in the Report Library andin a Dashboard page when displayed as a list, launch, or output block. Library Only Userscannot run reports, view the Domain Tree, view the Role Tree, access other WebFOCUSenvironments, and have limited access to Dashboard components. This role is assigned inthe Managed Reporting interface. Note that the Library Only User role cannot be deleted.


4. Managing Dashboard

Managing Private ViewsPrivate views are each user's personalized view of Dashboard. A user can personalize theDashboard by placing reports from the available domains in the Content area of theDashboard. Users cannot customize the look of the Dashboard.

A private view is created for users when they connect to the Dashboard with their ownManaged Reporting user ID and password. The private view is based on the general publicview or custom public view from where the user logs in. From here, the user can begin topersonalize the content in the private view.

Private views are secure in that a user must enter a valid Managed Reporting user ID andpassword. Each user can only access domains that the Administrator makes available inthe Managed Reporting Administration interface.

Private views are not available to Library Only Users.

Logging On to Dashboard and View Inheritance

In this section:

Logon Process for All Users (Excluding Library Only Users)

Logon Process for Library Only Users

Dashboard users log on to Dashboard and inherit the look and content of views in differentways depending on where they log on from, whether they are logging on for the first time orsubsequent times, and whether the GoToPersonalViewOnLogin setting in the bid-config.xmlfile, located in the WebFOCUS76\worp\conf directory, is set to "true" or "false".

Users can log on to Dashboard using the:

Business Intelligence Dashboard Login link on the Welcome Page

Business Intelligence Dashboard Public Views link on the Welcome Page

Group view URL

72 WebFOCUS

Managing Private Views

Logon Process for All Users (Excluding Library Only Users)The following processing takes place when a user, who is not a Library Only User, logs onto Dashboard.

First Time Logon to Dashboard (GoToPersonalViewOnLogin=true)

Users who:

Log on from the Business Intelligence Dashboard Login page, log on to their ownpersonal view and inherit the look and content of the General Public view.

Log on from a public view, log on to their own personal view and inherit the look andcontent of the public view from which they logged on.

Log on by accessing a group view URL directly, log on to that group view and inheritthe look and content of that group view as their own personal view.

For all methods of logging on to Dashboard for the first time, the inherited view is copiedto the user's folder created in the worp_users directory upon logon. Additionally, userswho click the Views link have access to all of the group views accessible to them.

Subsequent Logons to Dashboard (GoToPersonalViewOnLogin=true)

Users with access to any number of, or no, group views are logged on to their own personalview.

First Time Logon to Dashboard (GoToPersonalViewOnLogin=false)

Users with:

Access to no group views, log on from the Business Intelligence Dashboard Loginpage into their own personal view and inherit the look and content of the GeneralPublic View.

Access to one group view, log on to that group view and inherit the look and contentof that group view as their own personal view.



Access to multiple group views, log on to a page displaying all of the group viewsaccessible to them including a link to their My View. Clicking a group view from thispage logs users on to the selected group view, and their own personal view inheritsthe look and content of that group view. Clicking the My View link logs users on totheir own personal view which inherits the look and content of the General PublicView.

Note: For users with access to multiple group views who log on from a public view,clicking the My View link logs users on to their own personal view which inherits thelook and content of that public view.

For all methods of logging on to Dashboard for the first time, the inherited view is copiedto the user's folder created in the worp_users directory upon logon.

Subsequent Logons to Dashboard (GoToPersonalViewOnLogin=false)

Users with:

No group views, log on to their own personal view.

One group view, log on to that group view.

Multiple group views, log on to a page displaying all of the group views accessible tothem.

Logon Process for Library Only UsersThe following scenario shows the processing that takes place when a Library Only User logson to Dashboard. The behavior is the same for all logon attempts including the first logon,subsequent logons, and whether the GoToPersonalViewOnLogin setting in the bid-config.xmlfile is set to "true" or "false".

Users with:

No Library Only Views, are presented with the message, "No Library Only Group Viewsavailable for this user."

One Library Only View, log on to this view.

Multiple Library Only Views, log on to a page displaying all of the views accessible tothem.

For all of the above methods of logging on to Dashboard for Library Only Users, a user'sfolder is not created in the worp_users directory.

74 WebFOCUS

Logging On to Dashboard and View Inheritance

Managing Users

In this section:

Setting an ID and Password for the Public User

Setting a Server User ID and Password for the Public User

How to:

Edit User Content

Reassign a User's View

Remove Users From Dashboard

You can manage user's views (public, group, and personal) from the View Builder. TheManage Users option allows you to view and update the content of the user's personalpages and the look of their Dashboard view.

Changing, or reassigning, a user's view and content is useful when you want to update thelook or the content of a view without having to start over from scratch. It's also useful if auser changes groups and you need to update their view and/or content for example, fromthe Human Resources group page to the Accounting group page.

The Manage Users window provides the following information:

User Name, User Description, and User Folder for users who have logged into Dashboard.

The View Folder, View Type, and View Description of the look the user currently hasassigned to them.



How to Edit User ContentProcedure:

1. From the View Builder, click Manage Users.

2. Select the user you want to edit content for and click Edit Content.

The Content Window opens.

3. Edit content as necessary.

4. Click Manage Users to save changes and return to the Manage Users window.

Note: You can only edit content for one view at a time.

How to Reassign a User's ViewProcedure:


2. Select the user or users you want to reassign.

3. Click Reassign.

4. Select the new view look from the drop-down list.

5. If you want to replace the user's content with the content from the new view, click theReplace User Content with View Content check box.

When you replace content, the user still has access to all of the domains (and the itemsin those domains) they are assigned to. Only Dashboard specific items are replaced,such as content pages and content blocks. The user's Favorites and Recent lists arecleared when you select the Replace User Content with View Content check box.

6. Click Submit.

How to Remove Users From DashboardProcedure:

Note: This only removes the user from Dashboard, not Managed Reporting. If a user islogged in to Dashboard when you remove the user from Dashboard using the View BuilderManage Users page, a HTTP 500 error is displayed in the browser window. If the user logsin to Dashboard again, they will be added to the Manage Users list again.


2. Select the user or users you want to remove.

3. Click Remove.

4. Click OK to the confirmation pop-up dialog box.

76 WebFOCUS

Managing Users

Setting an ID and Password for the Public User

How to:

Set the Public User ID and Password

If you choose to restrict a public user's access to WebFOCUS Managed Reporting by settinga password when the public user is created, that password must also be stored in Dashboardto allow the user to view the public pages without entering a password. Setting the passwordis optional. However, if the password is set in WebFOCUS Managed Reporting, it must alsobe set in Dashboard to the same value.

Dashboard administrators can select a specific Managed Reporting user ID and passwordother than Public that is used to access Dashboard Public views.

When a Public view opens in a browser, Dashboard logs into Managed Reporting with adefault user ID and password that you can set in the View Builder. The public user ID andpassword are stored in the file:

ibi\webfocus\worp\conf\worp_mre.mpd

If a user attempts to login from the Dashboard login page with the Managed Reporting userID that has been designated as the public user in Dashboard, a message (19102) appears.

Anytime public user credentials are changed outside of Dashboard's scope, the changesmust be propagated to Dashboard using the View Builder. This includes changes to the userID or password used to connect the public user to Managed Reporting or the WebFOCUSReporting Server. If the changes are not reflected in the View Builder, the public user willnot use the updated credentials when connecting to Dashboard.

Note that Dashboard issues public sign-on requests when a public page is opened if any orall of the following conditions are met:

The Public user is not signed on.

The /worp/conf/worp_mre.mpd was changed due to a user ID or password change inthe View Builder.

The /worp/conf/worp_eda.epd was changed due to user ID or password change in theView Builder.



Note:

You can only designate one public user per Dashboard installation.

When setting the Public user in the View Builder to a Managed Reporting user ID otherthan Public, the public user ID should not be set to the administrator ID used to administerDashboard.

When the password for the public user is changed in the Managed Reporting Administrationinterface, the password also needs to be set in the View Builder Public User window sothat Dashboard can connect the public user to the Managed Reporting repository.

How to Set the Public User ID and PasswordProcedure:

1. From the Public Views window in the Dashboard ViewBuilder, click Public User.

2. Type the user ID and password, and confirm the password in the designated text boxes.

3. Click Save.

Note: The user ID and password are stored in encrypted format in the worp_mre.mpd filein the directory WebFOCUS76/worp/conf.

78 WebFOCUS

Managing Users

Setting a Server User ID and Password for the Public User

How to:

Set the Public User ID and Password for the Server

In the View Builder, you can set a user ID and password for the public user to connect tothe default WebFOCUS Reporting Server without having to enter login information. Settinga user ID and password is optional. However, to allow public access to the default WebFOCUSReporting Server through Dashboard without requiring a login window, a value must be sethere. For details on setting the WebFOCUS server user ID and password in the server profilefiles, see the WebFOCUS Security and Administration manual.

The user ID and password entered here will be used for connecting to the default WebFOCUSReporting Server. To set a different user ID and password to connect to alternate servers,the user ID and password must be set in the server profile. For details, see the WebFOCUSSecurity and Administration manual.

Note:

The View Builder does not attempt to match the user ID and password with a valid userID and password for the WebFOCUS Reporting Server. This option is available to give youa way to set the value for the Dashboard public user without setting it for all WebFOCUSconnections to the server.

If you are using a configuration with WebFOCUS Server security enabled, the Public viewis only accessible if a user ID and password are set in the View Builder. If an incorrectuser ID or password is supplied in the Server window of the View Builder, message 19101will appear when a users attempts to access a Public view.



The following image shows the WebFOCUS Server Connection window containing text boxesfor User ID, Password, and Confirm Password.

How to Set the Public User ID and Password for the ServerProcedure:

1. From the View Builder, click Server.

2. Enter the user ID in the Enter User ID input box.

3. Enter the password in the Enter Password input box.

4. Enter the password again in the Confirm Password input box.

5. Click Save and a message appears indicating the user ID and password have beensuccessfully saved.

The user ID and password are stored in encrypted format in the worp_eda.epd file inthe directory WebFOCUS76/worp/conf.

80 WebFOCUS

Managing Users

Controlling the Idle Limit for Authenticated and Public Users

How to:

Set the Idle Limit for Authenticated Users Using ServletExec

Set the Idle Limit for Authenticated Users Manually

Set the Idle Limit for Public Users Using ServletExec

Set the Idle Limit for Public Users Manually

You can define the number of minutes that a user's Dashboard session can be inactivebefore an automatic logout occurs. The public user and the authenticated user can beseparately configured to automatically disconnect after a number of minutes, or to staylogged in no matter how long idle. By default, the public user's connection to the Dashboardtimes out after 30 minutes and the authenticated user never times out.

You can edit the idle limit directly in the web.xml file or you can use Servlet Exec.

Note:

If a user has the Report Assistant or Graph Assistant open, the idle limit is not imposed.

If the User_max_inactive and the Public_max_inactive parameters are not set forDashboard in the web.xml, then the Application Server session time out setting is usedin the Dashboard environment.

How to Set the Idle Limit for Authenticated Users Using ServletExecProcedure:

1. Open the ServletExec Administration tool.

2. Under Web Applications, click Manage.

3. Under WebFOCUS76 Application Name, click web.xml.

4. Under Servlets, click Manage.

5. Under Servlet Name, click WORP_Loader.

6. Under Initialization Parameters, edit the following:

name: USER_MAX_INACTIVE

value: Enter -1 (the default value) if you do not want the server to ever time out.Otherwise, enter the number of minutes before time out occurs.

Descriptions are optional.

7. Click Submit.



8. From the Configure Web Applications window, click Reload for the WebFOCUS76application.

How to Set the Idle Limit for Authenticated Users ManuallyProcedure:

1. From the WEB-INF directory, open the web.xml file.

2. Edit the param-value as desired.

<init-param> <param-name>USER_MAX_INACTIVE</param-name> <param-value>-1</param-value></init-param>

Enter -1 (the default setting) if you do not want the server to ever time out. Otherwiseenter the number of minutes before time out occurs.

3. Save and close the file.

How to Set the Idle Limit for Public Users Using ServletExecProcedure:






6. Under Initialization Parameters, edit the following:

name: PUBLIC_MAX_INACTIVE

value: The default setting is 30 minutes. You can change this value to any numberof minutes you want. Enter a value of -1 if you never want time out to occur.


7. Click Submit.


How to Set the Idle Limit for Public Users ManuallyProcedure:


82 WebFOCUS

Controlling the Idle Limit for Authenticated and Public Users

2. Edit the param-value as desired.

<init-param> <param-name>PUBLIC_MAX_INACTIVE</param-name> <param-value>30</param-value></init-param>

The default setting is 30 minutes. You can change this value to any number of minutesyou want. Enter a value of -1 if you never want time out to occur.


Handling MessagesA standard message appears for all HTTP 500 series errors, which reads:

"A HTTP 500 error has been returned when attempting to communicate with the WebFOCUSweb components. The application server log contains information on why this error hasoccurred. Contact your WebFOCUS Administrator or Information Builders Customer SupportServices for further assistance."

All other HTTP errors are handled by the Web server.

By default, all Dashboard specific error messages are generated by WORP_Error.jsp. Youcan implement your own error page by editing the "ERROR" entity in theWebFOCUS76\worp\conf\bid-config.xml file:

<!ENTITY ERROR "&JSP;/WORP_Error.jsp">

All messages that display on the user's screen are written to the Web Application server logfile. The location of the Web Application server log file is different for different Web Applicationservers. Check your Web Application server documentation for the location of the log file.

Hiding Report Types in the Domain Tree

In this section:

Hiding Report Types in the Domain Tree for All Role Types

How to:

Hide Report Types in the Domain Tree in All Views

You can customize the Domain Tree to display or hide any or all of the available report andfile types (Standard Reports, Shared Reports, My Reports, Reporting Objects, and OtherFiles) for specific role types in all views. If you do not want to hide report and file types forall users of an existing role type, you can create a new role for specific users. Note that ifyou choose to hide My Reports from displaying in the Domain Tree, users will not have theoption to save parameter reports since parameter reports are a type of My Report.



Note: You can also hide report and file types in the Domain Tree of specific views using theEdit Settings functionality available in the Dashboard View Builder. For more information,see Customizing Dashboard Pages for a Public or Group View on page 99.

How to Hide Report Types in the Domain Tree in All ViewsProcedure:

1. In the WebFOCUS76\worp\conf directory, open the bid-config.xml file in a text editor.

2. Find the following lines to hide Standard Reports, Shared Reports, Reporting Objects,My Reports, and Other Files:

<internal-var name="hideStandardReportsFromTheseRoles" value=""/>

<internal-var name="hideSharedReportsFromTheseRoles" value=""/>

<internal-var name="hideReportingObjectsFromTheseRoles" value=""/>

<internal-var name="hideMyReportsFromTheseRoles" value=""/>

<internal-var name="hideOtherFilesFromTheseRoles" value=""/>

3. To hide report types in the Domain Tree, add one or more role types to the value variable.

For example, to show only Standard Reports for any user ID set to the "#User" role type,enter the following:

<internal-var name="hideSharedReportsFromTheseRoles" value="#User"/>

<internal-var name="hideReportingObjectsFromTheseRoles" value="#User"/>

<internal-var name="hideMyReportsFromTheseRoles" value="#User"/>

<internal-var name="hideOtherFilesFromTheseRoles" value="#User"/>

Note:

If the value is set to a role HREF, any user ID that has that role will not see thespecified report or file type in Dashboard. You can determine the HREF for a role bylooking at the basedir/role.htm file. To specify more than one role, separate the roleHREFs by a coma and no spaces.

Default role types include: #User, #RunOnlyUser, #LibraryOnlyUser, #AnalyticalUser,#Developer, #ContentManager, #MRAdministrator, and #PowerUser. For moreinformation on user types see User Roles Defined on page 54.

Because Other Files are hidden by default from all user roles except the Developerrole, the MR Administrator role, and any custom role based on either of these tworoles, you can effectively hide Other Files from only the previously mentioned roles.

84 WebFOCUS

Hiding Report Types in the Domain Tree


After making changes to the bid-config.xml file, use the WebFOCUS Console to clear memorycache. Until this is done, the change is not effective.

Hiding Report Types in the Domain Tree for All Role Types

How to:

Hide Report Types in the Domain Tree for All Role Types

In Dashboard, you can customize the Domain Tree to display or hide any or all of the availablereport and file types (Standard Reports, Shared Reports, My Reports, Reporting Objects,and Other Files) for all users of all role types by using the “ALL-ROLES” value in the existingbid-config.xml file, as shown in the following procedure.

How to Hide Report Types in the Domain Tree for All Role TypesProcedure:


2. Find the following lines to hide Standard Reports, Shared Reports, Reporting Objects,My Reports, and Other Files, and substitute “ALL-ROLES” for the value variable for thereport or file types you want to hide:

<internal-var name="hideStandardReportsFromTheseRoles" value=""/>

<internal-var name="hideSharedReportsFromTheseRoles" value=""/>

<internal-var name="hideReportingObjectsFromTheseRoles" value=""/>

<internal-var name="hideMyReportsFromTheseRoles" value=""/>

<internal-var name="hideOtherFilesFromTheseRoles" value=""/>

For example, to hide My Reports for all users of all role types, use the following:

<internal-var name="hideMyReportsFromTheseRoles" value="ALL-ROLES"/>


After making changes to the bid-config.xml file, use the WebFOCUS Console to clear memorycache. Until this is done, the change is not effective.



Hiding the Share Report Option for Finished My Reports

How to:

Hide the Share Report Option for Finished My Reports in All Views

Hide the Share Report Option for Finished My Reports in Specific Views

You can hide the Share Report option that is displayed by default in the properties of finishedDeferred Reports Output and OLAP Reports saved in the My Reports directory. Hiding theShare Report option provides another layer of security to safeguard sensitive content inthese types of finished reports. This functionality can be set globally in all views by editinga variable setting in the bid-config.xml file or set in specific views using the Dashboard ViewBuilder.

How to Hide the Share Report Option for Finished My Reports in All ViewsProcedure:


2. To hide the Share Report option for Deferred Reports Output, edit the following variableto change it from:

<internal-var name="showPropertiesShareOptionForDeferredReportsOutput" value="true"/>

to

<internal-var name="showPropertiesShareOptionForDeferredReportsOutput" value="false"/>

3. To hide the Share Report option for OLAP Reports, edit the following variable to changeit from:

<internal-var name="showPropertiesShareOptionForOLAPReports" value="true"/>

to

<internal-var name="showPropertiesShareOptionForOLAPReports" value="false"/>

Note: After making changes to the bid-config.xml file, use the WebFOCUS Console to clearmemory cache, or restart the application. Until this is done, the change is not effective.

86 WebFOCUS

Hiding the Share Report Option for Finished My Reports

How to Hide the Share Report Option for Finished My Reports in Specific ViewsProcedure:

1. Log on to the Dashboard View Builder.

2. Select a view.

3. Click Edit Settings.

4. To hide the Share Report option for Deferred Reports Output, click the False option tothe right of showPropertiesShareOptionForDeferredReportsOutput in the Settings pane.

5. To hide the Share Report option for OLAP Reports, click the False option to the right ofshowPropertiesShareOptionForOLAPReports in the Settings pane.

6. Click Save Settings.

7. Click Close.

For more information about using the Edit Settings functionality in the Dashboard ViewBuilder, see Customizing Dashboard Pages for a Public or Group View on page 99.

Displaying Optional Properties in Dashboard

How to:

Display Optional Dashboard Properties

The Dashboard Properties dialog displays the optional Created By and Last Modified Byproperties based on a variable setting in the bid-config.xml file.

How to Display Optional Dashboard PropertiesProcedure:

To display the optional Created By and Last Modified By properties in the DashboardProperties dialog:


2. Edit the following variable to change it from:

<internal-var name="showItemPropertyCreatorModifier" value="false"/>

to

<internal-var name="showItemPropertyCreatorModifier" value="true"/>




Creating Standard Reports in Dashboard

How to:

Enable the Creation of Standard Reports in All Views

Enable the Creation of Standard Reports in Specific Views

You can enable administrators and developers to create Standard Reports in Dashboardwith any of the available reporting tools. Additionally, they can create new folders underStandard Reports and set properties at the Standard Report level. However, new domainscan only be created in the Managed Reporting Administration interface. The creation ofStandard Reports by administrators and developers can be enabled for all views by editinga variable setting in the bid-config.xml file or enabled for specific views using the DashboardView Builder.

How to Enable the Creation of Standard Reports in All ViewsProcedure:

To enable administrators and developers to create Standard Reports in all Dashboard views:



<internal-var name="enableExtendedMenu" value="false"/>

to

<internal-var name="enableExtendedMenu" value="true"/>


How to Enable the Creation of Standard Reports in Specific ViewsProcedure:

To enable administrators and developers to create Standard Reports in specific Dashboardviews:


2. Select a view.


4. Click the True option to the right of enableExtendedMenu in the Settings pane.


6. Click Close.

88 WebFOCUS


90 WebFOCUS


WebFOCUS

Creating Public and Group Views5Topics:

A public view allows users to viewinformation in Dashboard withoutentering login information. Logininformation is managed in Dashboardfrom the Server and Public User windowsin the View Builder. For details, seeCustomizing Dashboard on page 105.

What Is a Public View?

What Is a Group View?

What Is a Library Only Group View?

Adding a Group or Public ViewThere are two types of public views,general and custom. The general publicview is the default public view and isintended for a wide variety of audiences.Custom public views contain detailedinformation that is relevant to morespecific groups.

Directing Users to a Group View UponLogin

Adding a Library Only View

Removing a Public or Group View

Editing a Public or Group ViewGroup views are secure views that candeliver information to a specific group ofusers.

Customizing Dashboard Pages for aPublic or Group View

You create and manage public views(general and custom) and group viewsfrom the Public Views and Group Viewswindows in the View Builder. From thePublic/Group Views windows you canadd, remove, edit or copy a public orgroup view.

Copying a Public or Group View

Exiting the Public Views or GroupViews Window

After you create a public or group view,content needs to be added. For details,see Creating Dashboard Content on page147.

Note: Users who access any public view(general or custom) or group view willonly be able to view information. Theywill not be able to change information orthe look of the Dashboard.


What Is a Public View?A public view allows public users to view information in Dashboard without having to enterlogin information. A default public view is provided with Dashboard and allows you to buildadditional custom public views containing specific reports and information for a particulargroup of users. For example, you can create a Human Resources public view that will containinformation that is pertinent to someone who works in that group, and an Accounting publicview that will only contain information for that group.

Dashboard uses the Managed Reporting User ID "public" to gain access to ManagedReporting content for public views. (You can change the ID used for the public user, seeSetting an ID and Password for the Public User on page 77.) Content for public views ismaintained by the Administrator in Managed Reporting User Management. The content forpublic views comes from the public user's membership in a group or by the assignment ofa domain to the public user. This content is available to the Dashboard Administrator whencreating a public view.

Each public view contains different content blocks and you can create a unique customizationfor each public view.

From the Welcome page, you can access the Public Views window. The Public Views windowlists all of the existing public views. From this page, users can navigate from one public viewto another by clicking the links on the page. Alternatively, you can give users one URL thatdirects them to the public view intended for their group.

What Is a Group View?A group view is a view based on WebFOCUS Managed Reporting repository groups. When auser logs into Dashboard, they will be able to see all of the views for each group they belongto. Users must be members of the Managed Reporting group associated with thecorresponding Dashboard group view in order to be able to login to them.

You can create a unique view for each group view. When you update a view, the view will beupdated for all members of the group, even members logged into Dashboard with personalviews.

Users cannot make any changes to group views. When a user logs into Dashboard, they canpersonalize their view to add personal pages in addition to the group pages.

Users can access the group views that are accessible to them by logging on to Dashboardand clicking the Views link. Alternatively, you can give users one URL that directs them to aspecific group.

92 WebFOCUS

What Is a Public View?

What Is a Library Only Group View?Library Only User views are based on Group Views. MR Administrators can create a GroupView in the View Builder for an MR Group. This Group View is available for any members ofthe group that are not Library Only Users. When the Group View is created, it is linked toanother Group View configured specifically for the Library Only user.

The Library Only Group View inherits the page appearance, banner location, banner links,and toolbars from the original Group View. If there is no banner in the original Group View,it is not shown in the Library Only Group View. Banner links are further reduced if the originalgroup view includes links not accessible to the Library Only User. The Logoff, Library, Views,and Help banner links are shown by default, and the developer of the view is able to removeany or all of these links. Additional toolbars can optionally be added to the Library Only View.

The Content window automatically includes the Library Page. The MR Administrator canupdate content pages in the View Builder to add additional content pages with direct linksto list or output blocks, and Report Library content in a launch block. The Library Page canbe removed by the developer of the view.

Adding a Group or Public View

In this section:

Group Administrator Access to the View Builder

How to:

Open the View Builder to Create a Public or Group View

Add a Public View

Add a Group View

You create a public or group view from the Public Views or Group Views window in the ViewBuilder.

Note that the Public Views and Group Views window accessible through the View Builder aredifferent than the Public Views and Group Views windows you can access from the WebFOCUSBusiness Intelligence Dashboard index page.

When you create a public or group view, you must supply a description for the view. Thename of your view is automatically generated and you can find it in the Link URL column.

The following folders, files, and links are created for each public and group view:

A folder using the link URL name is created in the worp_users folder.

Files named content.xml, layout.xml, and user-preferences.xml are created in theworp_users folder.


5. Creating Public and Group Views

For each public and group view, a link is added to the Public Views and Group Views windowsaccessible from the WebFOCUS Business Intelligence Dashboard index page. The descriptiondefined for the public or group view is the text for the link when the view was created.

The following image shows the Group Views window containing an available group, itsdescription, and URL link.

Note: When you enter the Public Views window for the first time, the default public viewdisplays. This view cannot be deleted although you can modify the description, look, andcontent.

How to Open the View Builder to Create a Public or Group ViewProcedure:

1. Enter the following URL in your Web browser:

http://webserver[:portnumber]/ibi_apps/bid

where:

webserver

Indicates the name of the Web server that is running Dashboard.

portnumber

Is the Web server port where WebFOCUS is running. This is not required if it is thedefault port.

The WebFOCUS Business Intelligence Dashboard Index Page opens.

Alternatively, you can enter:

http://webserver[:portnumber]/ibi_apps/bid/vblogin

to directly access the View Builder Login Page.

2. Click WebFOCUS BI Dashboard View Builder Login Page.

3. Enter your user ID and password.

94 WebFOCUS

Adding a Group or Public View

4. Click Logon. The Public Views window opens. To create a group view, click Group Views.

How to Add a Public ViewProcedure:

1. Open the View Builder.

2. Click Public Views.

3. Click Add. An input form displays at the bottom of the Public Views window.

4. Enter a description for the public view.

5. Click Submit. The new view is added to the Public Views list.

How to Add a Group ViewProcedure:

1. Open the View Builder.

2. Click Group Views.

3. Click Add. An input form displays at the bottom of the Group Views window.

4. Select a group name from the drop-down list.

5. Enter a description for the group view.

6. Click Submit. The new view is added to the Group Views list.



Group Administrator Access to the View BuilderGroup Administrators can access the View Builder to create and edit Group Views and LibraryViews for the groups they administer. The following image shows the View Builder with accessto Group Views.

The following are applicable for all such Group Administrators when accessing the ViewBuilder:

Group Views is the default page displayed upon login to the View Builder.

Only Group Views the Group Administrator is administrator for are displayed in the GroupViews page.

Options for Public Views, User Views, Public User, Server, Role Tree, Toolbox, ManageUsers, and Management are not available.

Directing Users to a Group View Upon Login

How to:

Select a Group View Upon Login

You can setup login so that when a user enters their ID and password they are automaticallylogged into a Group View of Dashboard or to a window where they can view the group viewsthat are available to them (if there are multiple views).

96 WebFOCUS

Directing Users to a Group View Upon Login

How to Select a Group View Upon LoginProcedure:

1. Back up the file /ibi/WebFOCUS76/worp/conf/bid-config.xml.

2. Open bid-config.xml using a text editor.

3. Search for the string “GoToPersonalViewOnLogin”. You will see the following code:

<internal-var name="GoToPersonalViewOnLogin" value="true"/>

4. Change the value to “false” as shown in the following code:

<internal-var name="GoToPersonalViewOnLogin" value="false"/>

5. Close and save bid-config.xml.

After the setting is changed, the following login processing is enabled:

If the user is a member of a single group view, the user is automatically logged intothat group view.

If the user is a member of multiple group views, the user is logged into a windowdisplaying the group views available to them.

Adding a Library Only ViewIf you access the View Builder and select the Library Views option, you can add, remove,and edit LIbrary Only Group Views using the interface shown in the following image.

Both the Library Only Group View and the original Group View are available from the sameView URL. When logging on, Dashboard routes a user to the Library Only Group View if theuser is a Library Only User. All other users are routed to the original Group View.




How to:

Remove a Public or Group View

From the Public Views or Group Views window, you can remove a public or group view. Notethat you can remove one or more views at a time.

How to Remove a Public or Group ViewProcedure:

1. Open the View Builder and click Public Views or Group Views.

2. Click the check box(es) next to the public/group view(s) you want to remove.

3. Click Remove. A message displays confirming the removal.

4. Click OK.

Editing a Public or Group View

How to:

Edit a Public or Group View's Description

After you create a public or group view, you can edit the description and the contents. Fordetails on editing content blocks, see Creating Dashboard Content on page 147.

How to Edit a Public or Group View's DescriptionProcedure:

1. Open the View Builder and click Public Views or Group Views.

2. Click the check box next to the public or group view you want to edit.

3. Click Edit Content. To edit the description, delete the current description and enter anew one.

4. Click Update.

For details on editing content blocks, see Creating Dashboard Content on page 147. Fordetails on editing the look of a view, see Customizing Dashboard on page 105.

98 WebFOCUS


Customizing Dashboard Pages for a Public or Group ViewFrom the Dashboard View Builder, Administrators and Group Administrators can customizethe Dashboard page for a selected public or group view, which overrides the default view,without editing any files. The View Builder's Edit Setting button launches a dialog box whichprovides you with a user interface to enable and disable features, display or hide types ofreports in the Domain Tree, change the appearance of the view, and perform othercustomizations.

The following image shows the Settings pane in the View Settings dialog box.

The following list of variable descriptions shows the settings you can change in the Settingspane and the default settings (where applicable), which are underlined:

Tab style - Round (display round corner tabs) or Square (display square corner tabs). Toapply globally for all views, see How to Display Square Corner Page Tabs in All Views onpage 122.

Enable Creation of Standard Reports - True (enable administrators and developersto create Standard Reports) or False (disable this functionality). To apply globally for allviews, see How to Enable the Creation of Standard Reports in All Views on page 88.



New ReportCaster Scheduler - True (set report Schedule option to open theReportCaster single page Scheduler tool) or False (set report Schedule option to openthe multi-page ReportCaster Scheduling Wizard). To apply globally for all views, see Howto Change the ReportCaster Scheduling Tool in All Views on page 139.

Display Created By and Last Modified By Properties - True (display the Create Byand Last Modified By properties in the Dashboard Properties dialog box) or False (hidethese properties). To apply globally for all views, see Displaying Optional Properties inDashboard on page 87.

Show Banner Greeting - True (display welcome message) or False (hide message). Toapply globally for all views, see Displaying a Welcome Message in the Banner on page131.

Reload Pages on Tab Navigation - True (reload pages) or False (do not reload pages).

Enable Upload Data File Feature - True (enable feature) or False (disable feature).

Enable Standard Browser Context Menu - True (enable menu) or False (disable menu).

Reload Block Content on Maximize - True (reload block) or False (do not reload block).

Show Properties Share option for Deferred Reports output - True (display ShareReport check box) or False (hide check box). To apply globally for all views, see Hidingthe Share Report Option for Finished My Reports on page 86.

Show Properties Share option for OLAP Reports - True (display Share Report checkbox) or False (hide check box). To apply globally for all views, see Hiding the Share ReportOption for Finished My Reports on page 86.

Show Folder Block as Collapsible Tree - True (display folder block as a tree) or False(display standard folder block). To apply globally for all views, see How to Display aCollapsible Tree in the Folder Blocks of All Views on page 157.

Hide Reporting Objects from these Roles - Select from a valid list of user roles. Toapply globally for all views, see Hiding Report Types in the Domain Tree on page 83.

Hide My Reports from these Roles - Select from a valid list of user roles. To applyglobally for all views, see Hiding Report Types in the Domain Tree on page 83.

Hide Shared Reports from these Roles - Select from valid list of user roles. To applyglobally for all views, see Hiding Report Types in the Domain Tree on page 83.

Hide Other Files from these Roles - Because Other Files are hidden by default fromall user roles except the Developer role, the MR Administrator role, and any custom rolebased on either of these two roles, you can effectively hide Other Files from only thepreviously mentioned roles. To apply globally for all views, see Hiding Report Types in theDomain Tree on page 83.

100 WebFOCUS

Customizing Dashboard Pages for a Public or Group View

Hide Standard Reports from these Roles - Select from valid list of user roles. To applyglobally for all views, see Hiding Report Types in the Domain Tree on page 83.

Note: The list of user roles you can select from includes Analytical User, Content Manager,Developer, MR Administrator, Power User, Run Only User, User, any custom user roles youhave created, and the ability to select all user roles that have access to the selected view.

The following image shows the User Links pane in the View Settings dialog box, which youcan access by clicking the down-arrow to the left of User Links.

The User Links pane contains the Available Links list box and the Selected Links list box.When a personal view is created, all banner links that were made available by theadministrator are selected to display in the view by default. You can remove links from theSelected Links list box and add back previously removed links that are in the Available Linkslist box.

The following image shows the Redirects pane in the View Settings dialog box, which youcan access by clicking the down-arrow to the left of Redirects.



The Redirects pane contains the Redirect context type drop-down menu and the RedirectURL text box. When users log off from a view, they are redirected to the Welcome Page bydefault. You can redirect users to a different logoff window by selecting context-redirect orx-redirect from the Redirect context type drop-down list and entering the desired URL in theRedirect URL field. The context-redirect option is the default setting and is used to addadditional segments to the default redirect URL to redirect a user to a different URL insidethe application context upon logoff. The x-redirect option is used to redirect a user to a fullyqualified URL outside the application. For more information, see Customizing the LogoffWindow on page 136.

All changes made to the selected view are saved in the following location:

\ibi\WebFOCUS76\worp\worp_users\viewname\view-config.xml

where:

viewname

Indicates the name of the customized view created in the View Builder.

When all Settings, User Links, and Redirects changes to the view are completed, click theSave Settings button. If you click the Reset to Default button, the customized view is deletedfrom the view-config.xml file and all default settings are restored. Click Close to return to theView Builder.


How to:

Copy a Public View

Copy a Group View

If there is an existing public view that contains content blocks you want to include in a newview, you can save time by copying the existing public view. By copying a public view, a newview is created that contains the same content blocks. When copying a group view, only thelook and feel is copied, the content blocks are not copied. After you copy an existing publicor group view, the new view has a different name and description than the old view. You canedit the content blocks after the view is copied.

Views are copied from the Public Views or Group Views window. The text of the descriptionis used as the link on the Public Views and Group Views pages.

102 WebFOCUS


How to Copy a Public ViewProcedure:

1. Open the View Builder and click Public Views.

2. Click the check box next to the public view to copy.

3. Click Copy. An input form displays at the bottom of the Public Views window.

4. Enter a description for the new public view.

5. Click Submit. The new public view is added to the Public Views list.

For details on content blocks, see Creating Dashboard Content on page 147.

How to Copy a Group ViewProcedure:

1. Open the View Builder and click Group Views.

2. Click the check box next to the group view to copy.

3. Click Copy. An input form displays at the bottom of the Group Views window.

4. Select a Group Name from the drop-down list.

5. Enter a description for the new group view.

6. Click Submit. The new group view is added to the Group Views list.

For details on content blocks, see Creating Dashboard Content on page 147.

Exiting the Public Views or Group Views WindowExit the Public Views and Group Views window by clicking Done. After doing so, the WebFOCUSBusiness Intelligence Dashboard index page opens.



104 WebFOCUS

Exiting the Public Views or Group Views Window

WebFOCUS

Customizing Dashboard6You can customize the WebFOCUS Business Intelligence Dashboard by choosing colors, adding a logo,selecting the position of the Domain Tree, Role Tree, banner, and more. To customize the WebFOCUSBusiness Intelligence Dashboard, use the View Builder.

You can create a unique customized view for each public and group view.

Before you begin, you must create the public user. For details, see Before You Begin Customizing Dashboardon page 106.

When you open the View Builder after upgrading from a previous version of Dashboard, the followingmessage displays:

The View Builder is now migratingthe existing customization andpersonalizations to the newversion. Please wait.

Note: The Dashboard view should not be updated while users are connected to Dashboard.

Topics:Creating a Custom Toolbar

Before You Begin Customizing Dashboard Adding a Message of the Day

Opening the View Builder Customizing the Logoff Window

Selecting a Template Changing the ReportCaster Scheduling Tool

Selecting Custom Colors Resetting the View Builder

Positioning the Domain Tree, Role Tree, andBanner

Saving Selections and Exiting a Customization

Exiting the View BuilderInserting a Logo

Customizing the Banner


Before You Begin Customizing Dashboard

Reference:

Public User Rights

Before you create a public or group view or begin to customize the WebFOCUS BusinessIntelligence Dashboard, the public user must exist. The public user is set up to allow usersto view information without having to enter a user ID or password. In addition, the publicuser has access to the WebFOCUS Managed Reporting domains you associate with thatuser. The public user has limited access to Dashboard. For details, see Public User Rightson page 106.

In most cases, the public user is automatically generated. To verify this, see the ManagedReporting Administration interface.

You can select any Managed Reporting user ID as the Public user. See Setting an ID andPassword for the Public User on page 77.

Public User RightsReference:

The public user can:

View and run the contents of the Standard Reports folder for the domains available tothe user. The user can only execute reports contained in this folder.

Perform a Domain Search, although the Look In option is not available to the user. Youcan remove the Domain Search option from a public view.

The public user cannot:

Create content blocks or content pages.

Access reporting tools, such as Report Assistant, Graph Assistant, ReportCaster, orLibrary.

Access the My Reports, Shared Reports, or Reporting Objects folders.

Save report output or report requests to a domain.

Run deferred requests or view deferred status.

Run OLAP-enabled reports. OLAP-enabled reports do not display in the Domain Tree orRole Tree for the public user.

106 WebFOCUS

Before You Begin Customizing Dashboard

Opening the View Builder

How to:

Open the View Builder to Customize a View

Reset the View Builder

You can customize your Dashboard look by using the View Builder. From the View Builder,you can open the following windows:

Look. Select a template for Dashboard.

Colors. Select custom colors for your template.

Composition. Select the position of the Domain Tree, Role Tree, and the banner.

Logo & Links. Select an image for the banner such as a company logo. You can alsocustomize the links that display in the banner of the public view.

Message. Add a customized Message of the Day to your Dashboard view.

Toolbar. Add a customized toolbar to your Dashboard view that contains any type of linkthat the Internet or intranet supports, such as Web sites, other tools, applications, anddocuments.

Toolbox. Create toolboxes that contain the items you want to insert in your customcontent tool bar.

Login. Select the login options, dual or single, for each public or group view.

Only one session of the View Builder can be open at any time. If you try to access the ViewBuilder while another administrator is using it, you will receive the following message:

A customization is currently in progress.

If you want to cancel the current customization, you can reset the View Builder. See How toReset the View Builder on page 109 for details.

Note: Do not use your browser's Back and Forward buttons to navigate in the View Builder.Instead, use the links provided on the left side of the View Builder.


6. Customizing Dashboard

How to Open the View Builder to Customize a ViewProcedure:

1. Click Business Intelligence Dashboard View Builder from the WebFOCUS Welcome page(http://webserver/ibi_apps/).

or

Click the View Builder button on the toolbar when you are in the Managed Reporting areaof Developer Studio.

or

Type the following URL in your Web browser:

http://hostname[:port]/wf_context_root/bid

where:

hostname[:port]

Is the name of the Web Server and optional port number (specified only if you arenot using the default port number) where the WebFOCUS Web application is deployed.

wf_context_root

Is the site-customized context root for the WebFOCUS Web application deployed onyour Application Server. The default value is ibi_apps.

The WebFOCUS Business Intelligence Dashboard Index page opens.

Alternatively you can type:

http://hostname[:port]/wf_context_root/bid/vblogin

to directly access the View Builder Login page (bypassing the Index page).

2. From the Index page, click WebFOCUS BI Dashboard View Builder Login Page.

If you used the alternative method to directly access the Login page, skip this step.

3. From the Login page, enter your user ID and password.

4. Click Logon to open the Public Views window.

If you want to customize a group view, click Group Views.

5. Select the check box next to the public or group view you want to customize.

6. Click Edit Look.

108 WebFOCUS

Opening the View Builder

How to Reset the View BuilderProcedure:

1. Click Reset View Builder from the window that displays the error message.

The Login to Reset Customization window opens.

2. Enter your user ID and password, then click Logon and the following message displays:

WebFOCUS BI Dashboard ViewBuilder customization session ended.

3. Click View Builder Login.

4. Enter your user ID and password again, then click Logon.

Note: When you disconnect the previously connected session, any customizations that werein progress will be lost.

Selecting a Template

In this section:

Creating a Custom Template

How to:

Select a Template

You can select a template for the Dashboard interface from the Look window in the ViewBuilder. A different template can be selected for each public and group view.



The following image shows the Look window divided into two parts. The top part of the windowcontains thumbnails of template styles and the bottom part is the preview of a selectedtemplate.

There are several templates available, each with different options. The options includeselecting custom colors and selecting a background image. For descriptions of all thetemplates, see Dashboard Templates on page 112.

How to Select a TemplateProcedure:

1. From the View Builder, click Look. The Look window opens.

2. Click an image in the Look window. The selected template displays in the Preview area.

3. Click Colors to change the colors for the look. For details, see Selecting Custom Colorson page 115.

110 WebFOCUS


Creating a Custom Template

How to:

Create a Custom Template

Reference:

Dashboard Templates

There are two templates available from the Look window in the View Builder that you canuse to create a Dashboard view that does not have a separate area for the logo embeddedin the banner.

Additionally, you can create a custom template for your Dashboard view and access it throughthe View Builder.

How to Create a Custom TemplateProcedure:

1. Navigate to the worp_html folder in the worp directory structure.

In this directory there are folders for each of the Dashboard looks, or templates (worp0through worp7).

2. Copy and rename one of these directories (the one that most closely resembles thelook you want to create) to a new directory under worp_html.

The new directory name should begin with "custom_", for example "custom_new".

3. In the directory for your new look, edit the file profile.prf.

This file contains two references to the directory name for the template. Change bothof these references to reflect the new directory name. If you do not make these changes,your template will still work correctly. However, these references need to be updatedfor the Dashboard Migration Utility to correctly migrate the views that use the customtemplates.



4. Edit the HTML and CSS files as necessary to make your customizations.

The tags bg1, bg2, etc. should be maintained in these files so that the color selectionsappear in the View Builder Colors page.

a. The banner.html and banner.css files control the banner display.

b. Domain.css controls the appearance of the left sidebar containing the Domain Treeand Role Tree.

c. Ctrl.css controls the appearance of the toolbar that displays over the content blocks.

d. Content.css controls the appearance of the content blocks.

e. Ibitools.css controls the appearance of toolbar 1, and customtools.css controls theappearance of toolbar 2.

5. Open the View Builder and select the new look, which will show up under the distributedlooks.

Note: When you make changes to the view outside of the View Builder, you will needto go back into the View Builder and select your customized view again in order to seeyour changes reflected in the template.

Dashboard TemplatesReference:

Following are the templates available for Dashboard. The numbers correspond to thethumbnail images in the Look window. If you place your mouse over the thumbnail, the nameof the template appears. For example, template 1 would appear as WORP0.

Template 1 (WORP0)

The colors for this template are customizable. The following image shows the first templatecontaining the white background with muted blue and mustard yellow foreground color andtext.

112 WebFOCUS


Template 2 (WORP1)

The colors for this template are customizable. You may also use an image for a wallpapereffect in the banner background area. The following image shows the first template containingthe white background with two shades of blue and gray for foreground color and text.

Template 3 (WORP2)

The colors for this template are customizable. You may also use an image for a wallpapereffect in the banner background area. The following image shows the first template containingthe white background with two shades of muted green and mustard yellow for foregroundcolor and text.

Template 4 (WORP3)

The colors for this template are customizable. You may also use an image for a wallpapereffect in the banner background area. The following image shows the first template containingthe white background with dark shades of blue and green for foreground color and text.

Template 5 (WORP4)

The colors for this template are customizable. The following image shows the first templatecontaining the white background with red and mustard yellow for foreground color and text.



Template 6 (WORP5)

The colors for this template are customizable. The following image shows the first templatecontaining the white background with gray and blue for foreground color.

Template 7 (WORP6)

The colors for this template are customizable. You may also use an image for a wallpapereffect in the banner background area. This template does not require a logo.

Template 8 (WORP7)

The colors for this template are customizable. You may also use an image for a wallpapereffect in the banner background area. This template does not require a logo and the banneris shorter than the other templates.

114 WebFOCUS


Selecting Custom Colors

How to:

Customize the Look of the HTML Report and Graph Assistant in Dashboard

Choose Custom Colors for a Template

Create a Wallpaper Effect in a Template

Display Square Corner Page Tabs in All Views

Reference:

Banner Custom Color Areas

Toolbar Custom Color Areas

Domain Custom Color Areas

Page Tabs Custom Color Areas

Content Block Custom Color Areas

Message Custom Color Areas

Toolbar 1 and Toolbar 2 Custom Color Areas

You can customize the templates by selecting colors (or images, where applicable) for thefollowing areas:

Banner. You can select the background colors, and the text and link color for the banner.If you have selected template 2, 4, or 5 you can alternatively select an image to createa wallpaper effect for the banner background area instead of a color.

Toolbar. You can select the background color and text color for the Domain Tree, RoleTree, and content block toolbars.

Domain. You can select the domain background color, text color, and link colors.

Page Tabs. For content pages, you can select the text color for the selected page tab,the text color for unselected page tabs, and the background color for all page tabs whenthe default round corner style page tabs are in use. When the optional square cornerstyle page tabs are enabled, you can select both the text color and background color forthe selected page tab and the unselected page tabs. You can enable square corner stylepage tabs for specific views using the Edit Settings functionality available in the DashboardView Builder. For more information, see Customizing Dashboard Pages for a Public orGroup View on page 99. To enable square corner tabs for all views, see How to DisplaySquare Corner Page Tabs in All Views on page 122.



Content Block. You can select the content block background color and link colors. Notethat you can only select colors for list blocks and folder blocks.

Message. You can select the background color and the text color for the message.

Toolbar 1 and Toolbar 2. You can select the background colors and the link colors forany custom tool bars you create.

Note: Depending on the template and the items selected to be included in the view, certainitems may not appear on the Custom Colors window.

The following image shows the Custom Colors window containing color choices for Banner,Control, Domain, Page Tabs, and Content Block.

The color areas vary for each template (for example, Background 1).

For details, see:

Banner Custom Color Areas on page 118.

Toolbar Custom Color Areas on page 119.

Domain Custom Color Areas on page 120.

Page Tabs Custom Color Areas on page 120.

Content Block Custom Color Areas on page 121.

Message Custom Color Areas on page 121.

116 WebFOCUS


Toolbar 1 and Toolbar 2 Custom Color Areas on page 121.

When you select the colors and/or wallpaper for your Dashboard banner, you can also selectthat these customizations be inherited by the HTML Report Assistant and Graph Assistant(when used from the Dashboard view).

How to Customize the Look of the HTML Report and Graph Assistant in DashboardProcedure:

1. From the View Builder, click Colors.

2. Select the colors and/or wallpaper.

Background color 1 is the top area, background color 2 is the main body area of thetool.

3. Click the Report Assistant and Graph Assistant inherit banner colors check box.

4. Click Preview.

5. Click Save.

Note: For changes in this window to be effective, you must click Preview and Save beforeyou exit this window.

How to Choose Custom Colors for a TemplateProcedure:

1. From the View Builder, click Colors. The Custom Colors window opens.

2. Click the colored rectangle adjacent to the area for which you want to select the color.



The Color Palette window opens as shown in the following image.

3. Click a color from the palette or enter a hex value in the area provided. The hex valueis not case sensitive. You are not limited to the colors that appear in the Color Palettewindow; you can use any color you want by entering the hex value.

4. Click Done to close the Color Palette window and save changes. Click Close to close theColor Palette window without saving changes.

You return to the Custom Colors window.

5. Click Preview to see how the colors display.

6. Click Save to save changes.

Banner Custom Color AreasReference:

The following table describes the color areas for the banner:

Designates...Custom ColorArea

The area that does not contain a logo or links for templates 2, 3,4, and 5. In templates 1 and 6, it is the area behind the links.

Background 1

118 WebFOCUS


Designates...Custom ColorArea

In template 1 it is the narrow bar above "Your Company LOGO".The area behind the links in templates 2, 3, and 4. In templates5 and 6, it is the narrow bar at the bottom of the banner.

Background 2

In templates 1 and 3 it is the narrow bar below "Your CompanyLOGO". In template 2 it is the bar beneath background area 1. Thelogo area in templates 3, 4, and 5. This is not applicable intemplate 6.

Background 3

In template 1, the area behind "Your Company LOGO". In template3, the line between "Your Company LOGO" and the link bar. Thisis not applicable for templates 2, 4, 5, and 6.

Background 4

In template 3, the line between "Your Company LOGO" and themessage of the day. This is not applicable for templates 1, 2, 4,5, and 6.

Background 5

The text color for links in the banner and for the optional welcomemessage.

Link

The text color for links when the cursor is positioned over the link.Hover

Toolbar Custom Color AreasReference:

The following table describes the color areas for the toolbar:

Designates...Custom Color Area

The color of the toolbar at the top of the Domain Tree, Role Tree,and content blocks.

Background

The content block name.Text



Domain Custom Color AreasReference:

The following table describes the color areas for the domain:


The background color behind the Domain Tree. This is also thebackground color for the Domain Tree that opens when a userselects the Tree link in the banner.

Background

The color of the text in the Domain Tree, including folder names.Text

The color of domain items such as links and reports.Link

The color of domain items such as links and reports after beingaccessed.

Visited Link

The text color for domain items such as links and reports whenthe cursor is positioned over the item.

Hover

Page Tabs Custom Color AreasReference:

The following table describes the color areas for page tabs:


The background color for the selected page tabs.Selected TabBackground

The background color for the unselected page tabs.

Note: When default round corner tabs are used, the backgroundcolor is the same for both selected and unselected tabs.

Unselected TabBackground

The text color for the selected page tab.Selected Tab Text

The text color for the unselected page tabs.Unselected TabText

120 WebFOCUS


Content Block Custom Color AreasReference:

The following table describes the color areas for content blocks:


The background color behind List and Folder blocks and Outputblocks if the block is empty. It is also the background color forthe Dashboard login page when accessed from a public or groupview.

Background

The color of links displayed in List and Folder blocks.Link

The text color for links in a List block after being accessed.Visited Link

The text color for links in a List block when the cursor ispositioned over the link.

Hover

Folder names in a Folder block.Text

Message Custom Color AreasReference:

The following table describes the color areas for the message:


The background color for the Message of the Day block.Background

The color of the Message of the Day text.Text

Toolbar 1 and Toolbar 2 Custom Color AreasReference:

The following table describes the color areas for toolbar 1 and toolbar 2:


The area behind the text.Background 1

The tool bar item outline.Background 2

The tool bar background (area behind the items in the tool bar).Background 3

The text color of links in the tool bar.Link




The text color for links in the tool bar after being accessed.Visited Link

The text color for links in the tool bar when the cursor ispositioned over the link.

Hover

How to Create a Wallpaper Effect in a TemplateProcedure:

1. From the View Builder, click Colors. The Custom Colors window opens.

You can add a wallpaper effect in templates 2, 4, and 5.

2. Enter the location of the image in the space provided or click Browse to search for theimage. Note that the image must be a GIF, JPG, or BMP file.

If the image is smaller than the banner area, it is repeated to fill the area.

Note: Dragging and dropping items, including images, is not supported in Dashboard.

3. Click the Click to Set Wallpaper check box only if you are changing the image or removingthe image.

4. Click Preview to view how the image displays. The Preview window must be updatedbefore exiting the Custom Colors window or your changes will not be saved.

The selected image file is copied to the WebFOCUS directory for access while runningDashboard. If the image file is modified in its original location you will need to reinsertthe image from Dashboard; it will not be automatically updated.

The name of the image will not display when you re-enter the View Builder.


How to Display Square Corner Page Tabs in All ViewsProcedure:


2. Edit the following variable to change it from the default setting for round corner pagetabs:

<internal-var name="tabStyle" value="0"/>

to the following setting for square corner page tabs:

<internal-var name="tabStyle" value="1"/>


122 WebFOCUS


Positioning the Domain Tree, Role Tree, and Banner

In this section:

Selecting Scrolling Options for Domain Trees and Role Trees

How to:

Position the Domain Tree, Role Tree, and Banner

Select the position of the Domain Tree, Role Tree, and banner from the Composition window.The Domain Tree and Role Tree share a column that can be placed on the right or left sideof the window, or removed. The banner can be placed at the top or bottom of the window,or removed.

Note: The composition should not be updated when users are connected to Dashboard.

Choose to hide or display the Domain Tree, Role Tree, and banner. Display options includethe following:

Check to use Banner. When this option is selected, the banner displays in yourDashboard view. If you deselect this option, the banner does not display. Note that ifyou remove the banner, authenticated users will not have access to links they may need,such as Login and Personalize.

Check to use Sidebar. When this option is selected, the sidebar (Domain Tree andRole Tree) display in your Dashboard view. If you deselect this option, the sidebar ishidden in your Dashboard view. Note that if you hide the Domain Tree/Role Tree, userscan still access the Domain Tree/Role Tree from the Tree banner link.

Check to use Frame Separator. Choose to keep or omit frame separators from theDashboard view. If you omit frame separators, a seamless look is created between thebanner and the sidebar (Domain/Role Tree).

Domain Tree only. This is the default selection and displays only the Domain Tree.

Role Tree only. Displays only the Role Tree.

Both Domain Tree and Role Tree. Displays the Domain Tree and the Role Tree. Whenthis option is selected, a button displays in the toolbar that allows the user to togglebetween the Domain Tree and the Role Tree. With this option, you also select to haveeither the Role Tree or the Domain Tree as the default display list.

If you choose to display the Role Tree, you must create a Role Tree for all groups that willuse the Dashboard view that contains a Role Tree. For details, see Creating a Role Tree onpage 141.

You can also select either scroll buttons or scroll bars for the Domain Tree and Role Tree.For details, see Selecting Scrolling Options for Domain Trees and Role Trees on page 125.



The following image shows the Composition window containing three parts: first part is thecheck boxes for banner, sidebar, and frame separator, second part is the position of thebar and sidebar, and the third part is content for the sidebar and tree link.

How to Position the Domain Tree, Role Tree, and BannerProcedure:

1. From the View Builder, click Composition. The Composition window opens.

2. To position the banner, click one of the combinations in the Composition window. Thebanner can be placed at the top or bottom of the window, and the Domain Tree andRole Tree share a column on the right or left side of the window. Not all combinationsare available for every display option.

The Preview area automatically updates when you select a combination.

3. To position the Domain Tree and Role Tree, select one of the following option buttons:

Domain Tree only. Displays only the Domain Tree.

Role Tree only. Displays only the Role Tree.

Both Domain Tree and Role Tree. Displays the Domain Tree and the Role Tree.When this option is selected, a button displays that allows the user to toggle betweenthe Domain Tree and the Role Tree. With this option you also select to have eitherthe Role Tree or the Domain Tree as the default display list.

Note that this also controls the content that displays when a user selects the Treebanner link.


124 WebFOCUS

Positioning the Domain Tree, Role Tree, and Banner

Selecting Scrolling Options for Domain Trees and Role Trees

How to:

Select Scrolling Options for Domain Trees and Role Trees

You can select either scroll buttons or scroll bars for the Domain Tree and Role Tree.

When scroll buttons are enabled, up, down, left, and right arrows display in the toolbarallowing you to navigate the Domain Tree or Role Tree.

When scroll bars are enabled, scroll bars display when content exists that cannot be viewedwithin the displayed window. When this option is selected, scroll buttons do not display inthe toolbar.

How to Select Scrolling Options for Domain Trees and Role TreesProcedure:

1. From the View Builder, click Composition. The Composition window opens.

2. Select the Enable Scroll Buttons or Enable Scroll Bars option button. This controls scrollingoptions in the sidebar list:

When Enable Scroll Buttons is selected, the buttons display in the Domain Tree orRole Tree toolbar.

When Enable Scroll Bars is selected, a scroll bar displays in the sidebar list whennecessary.

Inserting a Logo

How to:

Insert a Logo

Reference:

Logo Size

From the Logo & Links window you can insert an image such as a company logo in thebanner. The selected image file is copied to the WebFOCUS directory for access while runningDashboard. If the image file is modified in its original location, you will need to reinsert theimage from Dashboard; it will not be automatically updated.

The logo image must be a GIF, JPG, or BMP file. The logo size is determined by the size ofthe available space on the banner, and therefore, is different for the various templates. Fordetails, see Logo Size on page 126.



For information on links, see Customizing the Banner on page 127.

Note: If you have selected a banner template that does not require a logo, your windowdisplays the title Links, rather than Logo & Links.

The following image shows the Logo & Links window containing the image filename text boxfor displaying company logo with option buttons indicating a left, center or right position,and an Available Links list box for adding links and a Selected Links list box to order thelinks.

Logo SizeReference:

The following table provides information about the maximum height and width supported forthe logo in each template.

Width (pixels)Height (pixels)Look Template #

413481

207532

354743

200804

126 WebFOCUS

Inserting a Logo

Width (pixels)Height (pixels)Look Template #

160915

188646

How to Insert a LogoProcedure:

1. From the View Builder, click Logo & Links. The Logo & Links window opens.

2. Enter the location of the image in the space provided or click Browse to search for theimage.

Note that the image must be a GIF, JPG, or BMP file.

3. Select the horizontal alignment for the logo image from the Left, Center, or Right optionbuttons. The default is Center.

4. Select the vertical alignment for the logo image from the Top, Middle, or Bottom optionbuttons. The default is Middle.

5. Click Preview.



In this section:

Displaying a Welcome Message in the Banner

How to:

Add Links to the Banner

Remove Links From the Banner

Clear All Links From the Banner

Remove the Banner

Change the Banner Height

You can customize the links that display in the banner area for the public user and for GroupViews. You can also change the height of the banner, remove the banner, and display awelcome message in the banner.



From the Logo & Links window in the View Builder, you can customize the display of all linksthat are available to the public user and in Group Views. By default, the links available forGroup Views are Logoff, Accessibility, Tree, Tools, Recent, Favorites, Group Views, Utilities,and Help.

When a user logs into Dashboard to their personal view (My View) all available links appear.

Note:

When creating a new Public View, by default all banner links in the Available Links listare also in the Selected Links list. After creating a new Public View, you can change theSelected Links by editing the Look for the view and navigating to the Logo & Links pagewhere you can remove any banner links that should not show in the Public View.

The Language link only displays if you have installed multiple languages.

If you have selected a banner template that does not require a logo, your window displaysthe title Links, rather than Logo & Links.

The following image shows the Logo & Links window containing the image filename text boxfor displaying company logo with option buttons indicating a left, center or right position,and an Available Links list box for adding links and a Selected Links list box to order thelinks.

128 WebFOCUS


How to Add Links to the BannerProcedure:


2. Highlight the link you want to add in the Available Links list.

3. Click:

Add to add a link to the bottom of the Selected Links list.

Insert to insert a link above the highlighted position in the Selected Links list.

The order the links display in the Selected Links list is how they appear in Dashboard.You can move the links using the up and down arrows between the Available Links andSelected Links lists.

4. Click Preview.


How to Remove Links From the BannerProcedure:


2. Highlight the link you want to remove from the Selected Links list.

3. Click Remove. The link is removed from the Selected Links list.

4. Click Preview.


How to Clear All Links From the BannerProcedure:


2. Click Clear. All links in the Selected Links list clear, including the default Login link.

3. Click Preview.


How to Remove the BannerProcedure:

1. From the View Builder, click Composition.

2. Deselect the Check to use Banner check box.

3. Click Preview.

4. Click Save.



How to Change the Banner HeightProcedure:

1. Open the profile.prf file for editing. This file is located in WebFOCUS76/worp/worp_html/in one of the following folders:

worp0

worp1

worp2

worp3

worp4

worp5

worp6

worp7

The number of the folder depends on the template you have chosen. To determine thenumber, hover your mouse over the template in the Look window. Alternatively, thenumbers are in order (0–7) from left to right starting with the top left template.

2. Edit the bannerHeight section of the file to the desired height. The number representsthe number of pixels for the banner height. The default value is 105.

Note: The banner height must be a minimum of 50 pixels in order to sufficiently displaythe banner links. Some banner links, such as Help, have a drop-down menu associatedwith them. If the banner height is too small, the drop-down menu will not display andthe functionality will not be available to the user.

3. Save and exit the profile.prf file.

4. Open the View Builder and select the Public or Group view that uses the banner.

5. Select the banner in the Look window for the change to be propagated to the user'sDashboard view.

130 WebFOCUS


Displaying a Welcome Message in the Banner

How to:

Display a Welcome Message in the Banner of All Views

Display a Welcome Message in the Banner of Specific Views

A welcome message can be displayed in the left top corner of the banner, where the nameof the user logged into the view appears as “Welcome, user name”, as shown in the followingimage.

The welcome message can be set to display globally in all views by editing a variable settingin the bid-config.xml file or set to display in specific views using the Dashboard View Builder.Note that the text in the welcome message inherits the same color used for the bannerlinks.

How to Display a Welcome Message in the Banner of All ViewsProcedure:



<internal-var name="showBannerUserGreeting" value="false"/>

to

<internal-var name="showBannerUserGreeting" value="true"/>


How to Display a Welcome Message in the Banner of Specific ViewsProcedure:


2. Select a view.


4. Click the True option to the right of showBannerUserGreeting in the Settings pane.




6. Click Close.


Creating a Custom Toolbar

How to:

Create a Toolbox

Copy a Toolbox

Create a Toolbar

You can insert custom toolbars in Dashboard that can contain any type of link that theInternet or intranet supports, such as Web sites, other tools, applications, and documents.When a user clicks one of the links, a new browser window opens and displays the contents.

Toolbars can be placed in various positions in Dashboard and you can select different colorsfor the toolbars so they fit in with your Dashboard look. For details on selecting colors, seeSelecting Custom Colors on page 115.

You can have up to two toolbars per Dashboard view. The number of items a toolbar cancontain is only limited by the display space. Toolbars do not scroll, but you can maximizeyour space by positioning the toolbar appropriately (for example, a vertical toolbar can containmore items than a horizontal toolbar in most cases).

Since toolbars are created from items in your toolbox(es), you must create a toolbox beforeyou create a toolbar. You can create as many toolboxes as you require and each toolboxcan contain an unlimited number of items.

Once a toolbox is created, it is available in all public and group views.

How to Create a ToolboxProcedure:

1. From the View Builder, click the Toolbox link.

132 WebFOCUS


The Toolbox window opens as shown in the following image.

2. Below the Select Toolbox list box, click Add.

The Explorer User Prompt dialog box opens.

3. Type a name for the toolbox in the Explorer User Prompt dialog box and click OK.

Note:

Toolbox names and link captions are limited to alphanumeric characters only.

Toolboxes are stored in the ibi\WebFOCUS\worp\conf directory with a .tbx fileextension. The file is given a default name based on the current date and time, soevery toolbox has a unique name. This does not effect the display name you type inthe Explorer User Prompt dialog box.

4. In the Link Caption field, type the name for the link. This is the text that displays in thetoolbar.

5. In the Link URL field, type the URL for the link in the format:

http://websitename

For example, http://www.informationbuilders.com.

6. Click Insert and the link is added to the Available Links list box.

7. Click Clear and repeat steps 4–6 to add additional items to the toolbox. The number ofitems you can put in a toolbox is unlimited.

8. Click Save when you are finished.

How to Copy a ToolboxProcedure:

1. From the View Builder, click the Toolbox link.

The Toolbox window opens.

2. Highlight a toolbox from the Select Toolbox list and click Save As.

The Explorer User Prompt dialog box opens.



3. Type a name for the new toolbox in the Explorer User Prompt dialog box and click OK.

Note that toolbox names and link captions are limited to alphanumeric characters only.


How to Create a ToolbarProcedure:

1. From the View Builder, select a view and click the Edit Look link.The Look page opens.

2. Click the Toolbar link.

The Toolbar window opens as shown in the following image.

3. Select the Toolbar 1 or Toolbar 2 option.

4. Select the Check to use selected Toolbar check box.

5. Highlight a toolbox in the Select Toolbox list.

6. From the Available Links list, highlight a link and click Add.

7. Repeat steps 3 and 4 until your toolbar is complete.

8. Use the up and down arrows to the right of the Selected Links list box to position theorder of the selected links.

9. Select the toolbar position (top, bottom, left, or right) by clicking the appropriate imageat the bottom of the Toolbar window. (You may need to scroll down to view these images.)


134 WebFOCUS


Adding a Message of the Day

How to:

Add a Message of the Day

You can add a message of the day that will display for public users and for authorized users.You can display any text message up to 100 characters. By default, the message is includedin Dashboard. The message can be removed by deselecting the Check to use Message ofthe Day check box.

You can change the message of the day outside of the View Builder by editing themessage.html file. This file is located in:

drive:\ibi\WebFOCUS76\worp\worp_custom\dirname\message.html

where:

dirname

Is public for the general public view. Otherwise it is the directory specified in the PublicViews or Group Views window.

Open this file in any HTML editor and update the message text, which is the <TD elementwithin the table.

The following image shows the Message of the Day window where you type the message ina text box.

How to Add a Message of the DayProcedure:

1. From the View Builder, select a view and click the Message link.

The Message of the Day window opens.

2. Type the desired text in the Message field. The message can contain up to 100characters.



3. Click Preview to view the message in the preview area.


Customizing the Logoff Window

How to:

Customize the Logoff Window for Specific Views

Customize the Logoff Window for All Views

When users log off from a view in Dashboard, they are redirected to the Welcome Page bydefault. The logoff window can be customized to direct users to another page withinDashboard or a Web page outside of Dashboard. For example, when a user clicks the Logofflink in the Dashboard banner, you can have your company's Web site open. This functionalitycan be set for specific views using the View Builder or set globally for all views by editing avariable setting in the bidconfig.xml file.

How to Customize the Logoff Window for Specific ViewsProcedure:

Administrators and Group Administrators have the ability to redirect users of a specific publicor group view to a different URL upon logoff.

1. Log on to the Dashboard View Builder and select a view.


The View Settings dialog box opens.

3. Click the down arrow to the left of Redirects located in the lower left corner of the ViewSettings dialog box.

The Redirects area of the dialog box appears.

4. Click the down arrow to the left of Redirect Summary.

5. Select context-redirect or x-redirect from the Redirect context type drop-down list, thentype the desired URL in the Redirect URL field.

The context-redirect option is the default setting and is used to add additionalsegments to the default redirect URL to redirect a user to a different URL inside theapplication context upon logoff. The default URL redirects a user to the WelcomePage upon logoff, which is:

http://webserver[:port]/ibi_apps

136 WebFOCUS

Customizing the Logoff Window

For example, to redirect a user to the Group View login page for the aa_gbv groupview, select the context-redirect option and set the Redirect URL field to:

/bid/aa_gbv

The x-redirect option is used to redirect a user to a fully qualified URL outside theapplication upon logoff. For example, to redirect a user to the IBI Web site uponlogoff, select the x-redirect option and set the Redirect URL field to:

http://www.informationbuilders.com

If the Redirect URL field is left blank, the user is redirected to the Welcome Page uponlogoff by default.

6. Click Save Settings, then click Close.

How to Customize the Logoff Window for All ViewsProcedure:


2. Search for the string "logoff-success" and then comment out the lines immediatelybelow it, beginning with "<context" and ending with "</context".

Add "" to end the comment, as shown below.

<response-redirect request-context="logoff-success"> </response-redirect>

3. Add the following line below the closing comment tag (-->):

<x-redirect url="my_url"/>

where:

my_url

Specifies the URL.

Your code should now look similar to this:

<response-redirect request-context="logoff-success">  <x-redirect url="http://www.informationbuilders.com"/></response-redirect>

Here the URL is set to http://www.informationbuilders.com so when a user selects theLogoff link in the banner, they are disconnected from Dashboard and the InformationBuilders Web site opens.

4. Save and close the bid-config.xml file.

Changing the ReportCaster Scheduling Tool

How to:

Change the ReportCaster Scheduling Tool in All Views

Change the ReportCaster Scheduling Tool in Specific Views

When a Dashboard user selects the Schedule option for a selected report, the multi-pageReportCaster Scheduling Wizard opens by default. The tool that opens with the Scheduleoption can be changed to the ReportCaster single page Scheduler Tool, which provides allscheduling fields and settings in one interface. The ReportCaster scheduling tool that openswith the Schedule option can be changed globally in all views by editing a variable settingin the bid-config.xml file or changed in specific views using the Dashboard View Builder. Forinformation about scheduling and distributing report output with Managed Reporting, seethe ReportCaster Development and Administration manual.

138 WebFOCUS

Changing the ReportCaster Scheduling Tool

How to Change the ReportCaster Scheduling Tool in All ViewsProcedure:

To change the Schedule option for reports in all views to open the ReportCaster single pageScheduler Tool, perform the following:



<internal-var name="useNewScheduleURL" value="false"/>

to

<internal-var name="useNewScheduleURL" value="true"/>


How to Change the ReportCaster Scheduling Tool in Specific ViewsProcedure:

To change the Schedule option for reports in specific views to open the ReportCaster singlepage Scheduler Tool, perform the following:


2. Select a view.


4. Click the True option to the right of useNewScheduleURL in the Settings pane.


6. Click Close.


Resetting the View BuilderYou can reset the View Builder to the last saved version. When you click the Reset button,the View Builder will revert to the last saved version, whether it is from the current sessionor from a previous session.

Saving Selections and Exiting a CustomizationAfter you have finished your Dashboard customizations and have previewed the CustomColors, Logo & Links, and Message of the Day, you can save your selections by clickingSave in the View Builder.



Note: Be sure you have clicked the Preview button in the Custom Colors, Logo & Links, andMessage windows before you click Save in the View Builder. The selections you have madein these windows will not be saved if you have not clicked the Preview button in the respectivewindow.

To exit the customization, select the Public Views or Group Views link from the side menu.You return to either the Public Views or the Group Views page.

If you click Public Views or Group Views before saving changes that were made in the Preview,a prompt displays asking whether the changes should be saved. You can save the changesby clicking OK, or discard the changes by clicking Cancel. These are only changes that havebeen made since the last time the Save link was selected.

Exiting the View Builder

How to:

Exit the View Builder

When you log out of the View Builder, you are also logged out of Managed Reporting andthe WebFOCUS Reporting Server, and any set cookies are cleared.

How to Exit the View BuilderProcedure:

1. If you are customizing a public view, click Public Views. If you are customizing a groupview, click Group Views.

Depending on which view you were customizing, the Public Views or Group Views windowopens.

2. Click Done.

The Dashboard index page opens and displays links to the Dashboard views and theView Builder.

140 WebFOCUS

Exiting the View Builder

WebFOCUS

Creating a Role Tree7Topics:

A Domain Tree contains all items in adomain including items from theReporting Objects, My Reports, andShared Reports folders. By contrast, RoleTrees are created for WebFOCUSManaged Reporting User Groups andcontain some or selected items from thedomains to which the User Groups areassociated.

What Is a Role Tree?

Adding a Role Tree

Editing a Role Tree


What Is a Role Tree?Role Trees allow Dashboard users access to items such as reports, graphs, launch forms,and URLs, that have been associated with their Managed Reporting User Groups. Theadvantage of creating a Role Tree is that you can limit the items a user can access.

As shown in the following image, if a user belongs to the Century Corporation and Publicgroups, they will only have access to the items in the Role Trees assigned to those groups.

Role Trees display in the same area of the Dashboard as the Domain Tree. For details onmanaging the display of and positioning the Domain Tree and the Role Tree, see CustomizingDashboard on page 105.

If you choose to display the Role Tree in a Dashboard view, you must create a Role Tree forall groups that will use that view.

Adding a Role Tree

How to:

Add a Role Tree

You can create a Role Tree for any Managed Reporting User Group. To create a Role Tree,select the:

User Group.

Domains. You can add items from more than one domain. Items are taken from theStandard Reports folder of the respective domain.

Items (reports, graphs, launch pages, and URLs). Role Trees can only contain singleitems; folders cannot be added.

142 WebFOCUS

What Is a Role Tree?

The following image shows the Role Tree window containing the selection of Accounts asthe User Group, and Acme Manufacturing as the Domain.

How to Add a Role TreeProcedure:

1. From the View Builder, click Role Tree. The Role Tree window opens.

2. From the Group List, select a User Group.

3. From the Domain Tree, open a domain.

4. Expand the folders and click the items you want to add. Only items (reports, graphs,launch forms, URLs) can be added to a Role Tree. Folders cannot be added.

5. To add items from another domain, select a different domain from the Domain Tree andclick Submit.

6. Expand the folders and click the items you want to add.

7. Repeat steps 5 and 6 as necessary.

8. Click Save when you have completed selecting items for the Role Tree for a particularUser Group.

9. Click Public Views or Group Views to return to the respective page. Click Done if you wantto exit the View Builder.


7. Creating a Role Tree

Editing a Role Tree

How to:

Add Items to a Role Tree

Remove Items From a Role Tree

Clear Items From a Role Tree

Cancel Changes to a Role Tree

You can edit the Role Trees you have created for the User Groups by adding items, removingitems, or clearing all items. If you need to cancel the Role Tree you are creating, click Cancelin the Role Tree window. The last saved Role Tree list opens.

How to Add Items to a Role TreeProcedure:


2. From the Group List, select the User Group’s Role Tree to which you want to add items.

3. From the Domain Tree, open a domain.

4. Expand the folders and click the items you want to add. Only items (reports, graphs,launch forms, URLs) can be added to a Role Tree. Folders cannot be added.

5. To add items from another domain, select the domain from the Domain Tree and clickSubmit.

6. Expand the folders and click the items you want to add.

7. Repeat steps 5 and 6 as necessary.

8. Click Save when you have completed adding items to the Role Tree for a particular UserGroup.


How to Remove Items From a Role TreeProcedure:


2. From the Group List, select the User Group’s Role Tree from which you want to removeitems.

3. In the Content List, click the item you want to remove. You can remove multiple itemsby holding down the Shift or Control keys.

144 WebFOCUS

Editing a Role Tree

4. Click Remove.

5. Click Save when you have completed removing items from the Role Tree for a particularUser Group.


How to Clear Items From a Role TreeProcedure:


2. From the Group List, select the User Group’s Role Tree from which you want to clear allitems.

3. Click Clear. All items are removed from the Content List.

4. Click Save.


How to Cancel Changes to a Role TreeProcedure:

From the Role Tree window, click Cancel. The Role Tree window remains open and displaysthe last saved Role Tree list.


7. Creating a Role Tree

146 WebFOCUS

Editing a Role Tree

WebFOCUS

Creating Dashboard Content8Topics:

When opening Dashboard, content blocksdisplay and contain launched reports,hyperlinks to reports, hyperlinks toInternet resources, or output. Thefollowing are the types of content blocks:

Creating Dashboard Content Overview

Content Window

Creating Content PagesLaunch blocks.

Adding a Content BlockList blocks.

Editing a Content BlockFolder blocks.

Creating Filters For Standard ReportsOutput blocks.

Executing a Domain Profile inDashboard

Watch list blocks.

Selecting Content Layout


Creating Dashboard Content OverviewWhen creating a content block, select the block type, the block contents, and the blocklayout, and for administrators, the public or group view to which the block is associated.

The content blocks you create from the Public Views page are the blocks available to thepublic user. The public user has limited access to Dashboard. For details, see CustomizingDashboard Pages for a Public or Group View on page 99. Content blocks created from theGroup Views page only display to members of that group.

When accessing Dashboard, an authenticated user is able to add, edit, and remove contentblocks from their personal view using the personalize feature.

You can create content pages in order to increase content space, organize Dashboardcontent, and add pages that display the ReportCaster, Report Library, Watch List, or DeferredStatus user interfaces. For details, see Creating Content Pages on page 150.

Content Window

How to:

Open the Content Window

Exit the Content Window

From the Content window, you create the content blocks that appear in a public or groupview when Dashboard opens. You can:

Create content pages that contain content blocks, or the ReportCaster, Report Library,or Deferred Status user interfaces.

Add, remove, and edit content blocks.

Select the content layout.

When you open the Content window, a list of the current content blocks appears. When youplace your cursor over a content item, the full path of the procedure appears, including thedomain name and folder name.

Access the Content window from the Public Views or Group Views window.

148 WebFOCUS

Creating Dashboard Content Overview

The following image shows a sample administrator’s Content window with three distinctpanes. The first two sections contain a description text box and buttons to add and createcontent pages, and the third section contains buttons for adding, editing, or removing contentblocks.

How to Open the Content WindowProcedure:

1. Type the following URL in your Web browser:

http://hostname[:port]/wf_context_root/bid

where:

hostname[:port]

Is the host name and optional port number (specified only if you are not using thedefault port number) where the WebFOCUS Web application is deployed.

wf_context_root

Is the site-customized context root for the WebFOCUS Web application deployed onyour Application Server. The default value is ibi_apps.

The WebFOCUS Business Intelligence Dashboard Index page opens.


8. Creating Dashboard Content

Alternatively, you can type:

http://hostname[:port]/wf_context_root/bid/vblogin

to directly access the View Builder Login page (bypassing the Index page).

2. Click WebFOCUS BI Dashboard View Builder Login Page to open the View Builder Loginpage.

If you used the alternative method to directly access the Login page, skip this step.

3. Enter your user ID and password.

4. Click Submit to open the Public Views window.

If you want to view the Group Views window, click Group Views.

5. Select the check box next to the public or group view to which you want to add content.

6. Click Edit Content to open the Content window.

How to Exit the Content WindowProcedure:

For administrators, you exit the Content window by clicking Public Views or Group Views.Your changes are saved and you return to the Public Views or Group Views window.

Creating Content Pages

In this section:

Creating Library Content for a Public View

How to:

Create Content Pages

You can create content pages for Dashboard that contain content blocks, and theReportCaster, Report Library, Watch List, or Deferred Status user interfaces. Adding theReportCaster, Report Library, Watch List, or Deferred Status interfaces to a content page isdifferent than accessing them from banner hyperlinks, which open a new browser windowwhen the hyperlink is clicked. Each interface appears in its own content page directly in theDashboard.

You can add content pages for the ReportCaster, Report Library, Watch List, and the DeferredStatus interfaces to a Public view for authenticated users. When an authenticated userinherits the Public View as their My View, they will see this content; this content is hiddenfrom Public Users.

150 WebFOCUS


Content pages appear as tabs that display the name of the content page across the top ofthe content area. Pages can be viewed by clicking the appropriate tab.

Using content pages enables you to:

Expand the amount of space you have to display content in Dashboard.

Organize Dashboard content.

Keep the default view that was set up by the Dashboard Administrator while simultaneouslycreate personalized content pages.

Content pages are optional. If you have only one content page, tabs do not appear in theactual Dashboard view when you add content blocks.

Users can create as many content pages as they need and design the page layout.Administrators can also customize the color of content page tabs (background and textcolor). For details, see Selecting Content Layout on page 167 and Customizing Dashboard onpage 105.

When creating content pages, note that:

You can rearrange the order of the pages using the Move Left, Move Right, and SetDefault buttons in the Content window. The Set Default button promotes the current pageto the first page.

Only one output block is allowed per page.

When Dashboard opens, only the reports on the current content page execute. All otherreports execute when you click the respective content page tab.

Reports on content pages do not automatically refresh when tabbing from one page toanother. To refresh a report, click the Refresh button in the toolbar for that report.

How to Create Content PagesProcedure:

Note: When creating a content page, wait until all page items appear before using thebuttons on the page. If an error occurs due to premature use of the buttons, refresh thepage using your browser's Refresh button.

1. Select the Personalize link in the banner, then select Content from the submenu thatappears.

The Content window opens.

2. From the Content window, click:

Add Page to add a page that contains content blocks.



Add Library Page to add a page that contains the Report Library user interface. Youcan also add the Watch List interface after adding a library page.

Add Schedules Page to add a page that contains the ReportCaster user interface.

Add Deferred Status Page to add a page that contains the Deferred Status userinterface.

Note: When creating a Public View, the Add Library, Schedules and Deferred Statusbuttons are available. However, these pages are not displayed on the Public page if theyare included in the Public View. They will show for any user who inherits the Public viewas their My View when they log in to Dashboard.

Additionally, users who do not have access to Report Caster or Report Library will notbe able to view the Library or Schedule pages. The Library Page will display in PublicViews if the Public User has been given Library privileges.

3. Enter the tab name in the Page Description text box.

4. Click Update.

When a page is added, it is added as the last page. You can rearrange the order of thecontent pages using the Move Left, Move Right, or Set Default buttons. The Set Defaultbutton promotes the current page to the first page.

Creating Library Content for a Public ViewWhen creating content for a public view, the Administrator can add a Library page to theView. Clicking the Add Library Page button in the View Builder adds the Library tab, as shownin the following image.

When adding a content block, the Administrator can select content from the Library to beplaced in a launch, list, output, or watch list block. An additional tab, labeled Library, isavailable when adding or editing a content block that allows the Administrator to view Librarycontent available to the public user and select it to be added to a public view.

152 WebFOCUS


The following image shows the Library tab that provides access to Library content.

Adding a Content Block

In this section:

Creating a Locked Content Block

Adding Report Library Content to a Content Block

Removing a Content Block

How to:

Add a Content Block

Add Items to a Content Block Using Domain Search

Display a Collapsible Tree in the Folder Blocks of All Views

Display a Collapsible Tree in the Folder Blocks of Specific Views

From the Add Block window, you can create content blocks that the public or group userssee when opening Dashboard.



The following are the types of content blocks you can create:

Launch blocks can contain only one item. When Dashboard opens, the item automaticallylaunches.

A launch block that is created to display a report in EXL2K, EXCEL, or DOC formats shoulduse scroll bars instead of scroll buttons.

List blocks can contain many items from one or many domains. The items can be fromany folder in any domain to which a user has access. Users can run a report or accessan Internet resource by clicking a hyperlink from the list.

Folder blocks list the entire contents of a folder (including its subfolders) that havebeen created in Managed Reporting. Only one folder can be added to a folder block.When the contents of a Managed Reporting folder are modified outside of Dashboard,the folder block in Dashboard automatically updates to reflect any changes. You can addfolders from the Standard Reports, My Reports, and Shared Reports folders. For a publicview, you can only add folders from the Standard Reports folder.

By default, all subfolders in a folder block are expanded and cannot be collapsed.Optionally, all subfolders can be displayed as a collapsible tree and expanded as needed.This functionality can be set globally for all views by editing a variable setting in the bid-config.xml file or set for specific views using the Dashboard View Builder. For details,see How to Display a Collapsible Tree in the Folder Blocks of All Views on page 157 or Howto Display a Collapsible Tree in the Folder Blocks of Specific Views on page 158.

Output blocks may or may not contain default content. They are blocks where reports,graphs, or Web pages appear. When a report is run or an Internet resource is accessed,the report output or Web page appears in the output block. This is useful because a newbrowser window does not open each time a report or graph is executed, or a Web pageis launched from a Domain Tree, Role Tree, List, or Folder block. Instead, the outputblock refreshes with the new content.

When you create an output block, scrolling options are not available. Scroll bars appearwhen necessary.

Tree blocks provide a way to add a Domain Tree to a Public or Group View page. TheDomain Tree is displayed without the sidebar frame.

Watch list blocks add the Report Library Watch List interface to a page. The watch listblock type is available only when the Library tab is selected from the Add Block page.

Note: Some Web sites bring their page to the top of a frameset when launched and takeover the browser session. When these sites are opened in a launch or output block,Dashboard content is lost. It is recommended that these types of Web sites not be selectedfor a launch or output block.

154 WebFOCUS


When you add items to a content block, you can use the Domain Search from the Add Blockand Edit Block windows. For details, see How to Add Items to a Content Block Using DomainSearch on page 157.

Across the top of the Add Block window is a drop-down menu for selecting a domain, aDomain Search button, and option buttons to select from Launch, List, Folder, Output, orTree for the Block Type. At the left side of the window is a tree view of the selected domain.The right side of the window contains the Content List showing selected items with up anddown arrows to the right, and Remove and Clear buttons at the bottom.

Below the Content List is a text box for entering the Block Name and a series of check boxesthat are available to enable the following functionality:

Deactivate Block

Lock Block (available to administrators only)

Hide Block Toolbar

MS Office output options

Automatic Block Refresh (available to administrators only)



There are also option buttons to enable Scroll Buttons or Scroll Bars, and Save and Cancelbuttons. The following image shows the Add Block window.

How to Add a Content BlockProcedure:

1. From the Content window, select the content page in which to add content. If you needto add content pages, see How to Create Content Pages on page 151.

2. Click Add Block. The Add Block window opens.

3. Select the Launch block, List block, Folder block, Output block, or Tree block optionbutton.

4. Select a domain from the drop-down list. You can also add items to a content blockusing Domain Search. See How to Add Items to a Content Block Using Domain Searchon page 157.

Note: If you are creating an Output block, adding domain items is optional since Outputblocks do not require default output.

5. Click Submit to retrieve the contents of the selected domain.

156 WebFOCUS


6. Expand the domain folders you want to select items from by clicking the plus sign (+)located next to the folder icon.

Note: Only one report in EXL2K PIVOT format can be active at a time. Therefore, it isnot recommended to place output of this format type into a content block. Subsequentattempts to execute a report in this format will fail, since the original report will still beactive.

7. Click the items in the domain folders to populate the Content List.

If you are creating a List block you can position the items using the arrows next to theContent List.

8. Accept the default Block name or change the name in the Block name text box.

Note:

If you name your content block before you select content, the block name may beoverwritten with the name of the Domain item you select. You can change the nameafter selecting content.

If you create an empty launch, list, or folder block and enter a Block name, when youclick Save the name is overwritten with Empty Block. This occurs only with launch,list, and folder blocks. Output blocks retain the name you enter.

9. Select the Enable Scroll Buttons or Enable Scroll Bar option button.

10. Click Save when you have finished selecting the content for your block.

How to Add Items to a Content Block Using Domain SearchProcedure:

1. From the Add Block or Edit Block window, click Domain Search.

2. Enter the criteria for your search and then click Search.

3. From the results on the right side of the window, click on an item to add it to your contentblock. View your content block to see the items you have added.

How to Display a Collapsible Tree in the Folder Blocks of All ViewsProcedure:

1. Open the bid-config.xml file in a text editor. For example:

C:\ibi\WebFOCUS76\worp\conf\bid-config.xml




<internal-var name="showFolderBlockAsCollapsibleTree" value="false"/>

to

<internal-var name="showFolderBlockAsCollapsibleTree" value="true"/>


How to Display a Collapsible Tree in the Folder Blocks of Specific ViewsProcedure:


2. Select a view.


4. Click the True option to the right of showFolderBlockAsCollapsibleTree in the Settingspane.


6. Click Close.


Creating a Locked Content Block

How to:

Create a Locked Content Block

You can create a content block for a Public View that cannot be edited or deleted by a userafter they create their personal view from the Public View.

In a user's personal view, the Edit option is not available for locked content blocks. Inaddition, the option to delete or edit locked blocks from the Content window is not available.A Dashboard user cannot remove a page containing a locked block.

The locked block is designated with a lock icon in the View Builder, Personalize content, andManage Users sections of Dashboard. Users receive an error message if they attempt toremove a content page that contains a locked block.

The Lock Block check box is also available in the Manage Users area of the View Builder.

158 WebFOCUS


How to Create a Locked Content BlockProcedure:

1. From the Public Views or the Manage Users window, select the Public View you want toadd content to and click Edit Content.

2. From the Content window, select the content page in which to add content.

3. Click Add Block. The Add Block window opens.

4. Select the block type and contents.

5. Click the Lock Block check box.

6. Click Save.

Adding Report Library Content to a Content BlockDashboard administrators and authenticated users can place Report Library content in acontent block using the View Builder or Personalize option. You can add Report Librarycontent to a launch, list, output, or watch list block. The latest available version of the reportalways appears in the content block.

A tree of Library reports is available for selection when creating content blocks. The treeconsists of the top level domain or category. Below the domain or category is the report. Inthe case of a bursted report, an intermediate level also appears.

The Report Library has two sets of reports. Dashboard can access both, the domain forManaged Reporting users and the category for non-Managed Reporting users.

Note:

If you are adding Report Library content from the Manage Users or Group Views areas inthe View Builder, you also need to be a ReportCaster administrator.

To view Report Library content, you must have Report Library access.

Removing a Content Block

How to:

Remove a Content Block

From the Content window, you can remove a content block. Note that you can remove morethan one content block at a time.

How to Remove a Content BlockProcedure:

1. From the Content window, select the content page where the content block is located.

2. Click the check box(es) next to the block(s) you want to remove.



3. Click Remove. An alert window appears to confirm the removal.

4. Click OK.

Editing a Content Block

In this section:

Enabling Automatic Block Refresh

Selecting Scrolling Options

Hiding the Toolbar in a Content Block

How to:

Change the Content Block Type

Remove Items From a Block

Change the Block Contents

Change the Name of a Content Block

Temporarily Remove a Content Block

From the Edit Block window, you can edit existing content blocks. When you select the editoption, the name of the content block and its attributes appear in the Edit Block window.You can edit the block type, block contents, block name, scrolling options, and severaloptional features.

You can also deactivate a content block. This is useful when you want to temporarily removea content block from a Dashboard view. When a content block is deactivated, it is designatedin the Content window with a red icon. Green designates an active content block.

Across the top of the Edit Block window is a drop-down menu for selecting a domain, aDomain Search button, and option buttons to select from Launch, List, Folder, Output, orTree for the Block Type. At the left side of the window is a tree view of the selected domain.The right side of the window contains the Content List showing selected items with up anddown arrows to the right, and Remove and Clear buttons at the bottom.

Below the Content List is a text box for entering the Block Name and a series of check boxesthat are available to enable the following functionality:

Deactivate Block

Lock Block (available to administrators only)

Hide Block Toolbar

MS Office output options

160 WebFOCUS


Automatic Block Refresh (available to administrators only)

There are also option buttons to enable Scroll Buttons or Scroll Bars, and Save and Cancelbuttons. The following image shows the Edit Block window.

How to Change the Content Block TypeProcedure:

Note: When you change the content block type, all of the items in the block are removedand the block name clears.


2. Click the check box next to the block you want to edit.

3. Click Edit Block. The Edit Block window opens.

4. Select the block type option button.

5. Click Save.

How to Remove Items From a BlockProcedure:

1. From the Content window, select the content page where the block is located.



2. Click the check box next to the list block you want to edit.


4. In the Content List highlight the item you want to remove.

5. Click Remove.

6. Click Save.

How to Change the Block ContentsProcedure:

1. From the Content window, select the content page where the block is located.



4. Select a domain from the drop-down list and click Submit.

You can also add items to a content block using Domain Search. For details, see Howto Add Items to a Content Block Using Domain Search on page 157.

5. Navigate to the item you want to add in the Domain Tree.

6. Click the item or folder to add it to the Content List.

Note: The block name may be overwritten with the name of the Domain item you select.You can change the block name after selecting content.

7. Click Save.

How to Change the Name of a Content BlockProcedure:




4. In the Block name text box, type the new name for the block. This must be a uniquename within Dashboard.

5. Click Save.

How to Temporarily Remove a Content BlockProcedure:




162 WebFOCUS


4. Select the Deactivate Block check box.

5. Click Save.

Enabling Automatic Block Refresh

How to:

Change the Default Minimum Refresh Value

Disable Automatic Block Refresh for All Views

Administrators can enable automatic block refresh functionality on a per block basis toprovide users with the option of setting a time interval (in seconds) when content blocks areautomatically refreshed. The Automatic Block Refresh check box is displayed to administratorson the Edit Block and Add Block pages for all block types, and is hidden to users who areediting content for their personal views. Note that users who log in for the first time to theirpersonal views, from a view that contains a block enabled for refresh, will inherit automaticblock refresh functionality from that view.

The following image shows the Automatic Block Refresh check box selected for the HumanResources Main View content block.

Note: Selecting the Hide Block Toolbar check box disables Automatic Block Refreshfunctionality for the selected block.



When automatic block refresh functionality is enabled for a content block, a Refresh checkbox and refresh time interval field are displayed in the block toolbar. The Refresh check boxis unselected by default every time a user logs in to the view. Users have the option to setautomatic block refresh by entering a refresh value in seconds (or using the default value)and then selecting the Refresh check box, as shown in the following image:

The minimum refresh value is set to 30 (seconds) by default. The default minimum refreshvalue can be changed by editing the bid-config.xml file. For details, see How to Change theDefault Minimum Refresh Value on page 164.

If a user enters a non-integer value or a value less than the minimum refresh value, anappropriate error message is generated. When a user selects the Refresh check box, therefresh time interval field is disabled, which prevents the value from being changed.Deselecting the Refresh check box enables the refresh time interval field again.

How to Change the Default Minimum Refresh ValueProcedure:

You can change the default minimum refresh value that appears in the block toolbar for allcontent blocks that have automatic block refresh functionality enabled. Users will not beable to set a refresh time interval value that is less than the default minimum value.



2. Edit the following variable to change the minimum refresh value, which is set to 30(seconds) by default:

<internal-var name="autoReloadMinInterval" value="30"/>

164 WebFOCUS


The autoReloadMinInterval value must be an integer value that represents the minimumnumber of seconds when content blocks can be set to automatically refresh. For example,to set the default minimum refresh value to 2 minutes, enter 120 for the value of thisvariable.

How to Disable Automatic Block Refresh for All ViewsProcedure:

Automatic Block Refresh functionality can only be enabled by administrators on the EditBlock and Add Block pages for all block types. If your organization wants to disable thisfunctionality for all views, perform the following.

Note: The Automatic Block Refresh check box will still be visible to administrators, but notselectable.



2. Edit the allowAutoReload variable and set the value to false, as shown in the followingcode:

<internal-var name="allowAutoReload" value="false"/>


Selecting Scrolling Options

How to:

Select Scrolling Options for a Content Block

You can select either scroll buttons or scroll bars for launch blocks, list blocks, and folderblocks. Scroll buttons cannot be selected for output blocks and launch blocks that launchWeb pages. Output blocks automatically contain scroll bars when necessary.

When scroll buttons are enabled, up, down, left, and right arrows display in the toolbarallowing you to navigate the content block. Up and down arrows display for all content blocktypes. Left and right arrows only display for launch blocks. In folder blocks and list blocksinformation automatically wraps, therefore eliminating the need to scroll to the left or right.

When scroll bars are enabled, scroll bars display when content exists that cannot be viewedwithin the displayed window. When this option is selected, scroll buttons do not display inthe toolbar.

Note: A launch block that is created to display a report in EXL2K, EXCEL, or DOC formatsshould use scroll bars instead of scroll buttons.



How to Select Scrolling Options for a Content BlockProcedure:

1. From the Content window, select the content block you want to add scrolling options forand click Edit Block. The Edit Block window opens.

2. Select the Enable Scroll Buttons or Enable Scroll Bars option button.

3. Click Save.

Hiding the Toolbar in a Content Block

How to:

Hide the Toolbar in a Content Block

When you hide the content block toolbar, automatic block refresh functionality is not available.Additionally, scrolling is automatically set to use scroll bars because scroll buttons are notavailable when the block toolbar is hidden.

How to Hide the Toolbar in a Content BlockProcedure:

1. From the Add Block or Edit Block window, select the Hide Block Toolbar check box.

Note: The Lock Block and Automatic Block Refresh check boxes are available toadministrators only.

166 WebFOCUS


2. Click Save.

Creating Filters For Standard ReportsFilters allow users to apply pre-defined criteria to a report at the time of execution. Filtersare created by a Developer or Administrator when the report is built. These types of reportsare created as Reporting Objects and given the property "Show as Standard Report" so aDashboard user can view the report in their Domain Tree.

For details on creating filters, see the WebFOCUS Managed Reporting Developer's Manual.

For details on using filters in Dashboard, see the WebFOCUS Managed Reporting End User'sManual.

Executing a Domain Profile in DashboardEvery time a user opens a domain in the Domain Tree, a domain profile executes. The domainprofile can display an HTML page or the results of a WebFOCUS procedure prior to enteringa domain.

You create a domain profile by either writing a WebFOCUS procedure (.fex) or defining anHTML page (.htm). For example, you can write a WebFOCUS procedure that displays a reportor defines an HTML page that displays company information each time a user opens aparticular domain. The profile is not run each time a user submits a request to the WebFOCUSReporting Server.

For complete details on domain profiles, see the WebFOCUS Managed Reporting Developer'sManual.


How to:

Add a Column

Adjust Column Width

By default, content blocks are displayed in one column in Dashboard. From the Layoutwindow, you can change the content block layout. You can select a different layout for eachcontent page. When selecting the layout for your content page, you can:

Add/remove columns.

Specify column width.

Rearrange column order.



The following image shows a sample Layout window. There are list boxes for the contentsof Column 1 and Column 2 with up/down and right/left arrows. The Column 1 list box includesa text box and plus (+) and minus (-) controls to adjust column width. There are buttons toAdd Column, Remove Column, Move Column Left and Move Column Right, as well a Contentbutton to return to the Content window.

Note: If you remove all content blocks from a column, the column is not automaticallyremoved from the Dashboard View. If there are no content blocks in a column, emptyspace is shown in the Dashboard View.

How to Add a ColumnProcedure:

1. From the Content window, select a content page and then click Page Layout.

2. Click Add Column. To move:

Items from one column to another, highlight the item and use the left and right arrowsbetween the columns.

The position of a column, select the column and click Move Column Left or MoveColumn Right.

3. Click Content to return to the Content window.

168 WebFOCUS


How to Adjust Column WidthProcedure:

1. From the Content window, select a content page and click Page Layout.

2. Click the plus (+) or minus (-) signs in the column to adjust column width.

Note that you cannot adjust the width for the last column. Since column width total mustequal 100%, the last column is always the remainder of all the other columns. Forexample, if you have 3 columns and column 1 is 50% and column 2 is 25%, column 3is 25%.

Note: If you make your content blocks too small, the popup menu may not fully display.

3. Click Content to return to the Content window.



170 WebFOCUS


WebFOCUS

Managed Reporting Extract Utility9Topics:

The Managed Reporting Extract utilityallows you to extract data from yourManaged Reporting Repository in orderto generate reports about users, groups,domains, and domain content.

Managed Reporting Extract Utility

Running the Managed ReportingExtract Utility

Note: You can now also extractmetadata remotely using the ChangeManagement interface. For details, seeChange Management on page 189.

Managed Reporting Extract UtilityOutput Files

Master Files and Sample Procedure

Reporting From Extract Files

Property Flags


Managed Reporting Extract UtilityYou can extract and process the following types of information from the Managed ReportingRepository using the Managed Reporting Extract utility:

User information and the groups to which they belong.

Role information.

Group information and the domains to which they are associated.

Domain information.

Domain content information.

The Managed Reporting Extract utility is based on the Managed Reporting Java API. Thesource code for this utility is available on demand through Information Builders' CustomerSupport. It can be helpful to evaluate how the Managed Reporting API can be used.

Running the Managed Reporting Extract Utility

How to:

Run the Managed Reporting Extract Utility

Call IBIExtractRepos Programmatically

The Managed Reporting Extract utility is run on the machine where WebFOCUS is installed.You can use Telnet or another form of remote access to execute the utility when it is notpossible to physically be at the WebFOCUS machine. For convenience, a batch file is providedto call the utility with standard arguments.

Note: If you are using the Realm Driver to authenticate to another directory, you need tomodify the batch file (mrextract.bat) so that the classpath includes the necessary .jar files.

How to Run the Managed Reporting Extract UtilityProcedure:

1. Navigate to the WebFOCUS76/utilities directory.

2. Execute the mrextract.bat file (Windows systems) or mrextract file (UNIX systems).

172 WebFOCUS

Managed Reporting Extract Utility

A series of messages appear:

----------------------------------------------- Managed Reporting Repository Extract Utility WebFOCUS Release 7-----------------------------------------------Extracting MR User Data...Extracting MR Role Data...Extracting MR Group Data...Extracting MR Domain Data...Extracting MR Domain Content Data...Finished.Press any key to continue . . .

The utility creates the output files in the WebFOCUS76/utilities directory. For informationabout the format of these files, see Managed Reporting Extract Utility Output Files onpage 174. For information about reporting from these files with WebFOCUS, see ReportingFrom Extract Files on page 182.

How to Call IBIExtractRepos ProgrammaticallySyntax:

The underlying program that extracts information from the Managed Reporting Repository iswritten in Java and is contained in the archive WebFOCUS76/utilities/IBIExtractRepos.jar.

You call the program by using the following arguments

java –cp archivepath ibi.util.IBIExtractRepos configpath option [option] > outputfile

where:

archivepath

Is the full or relative path to the IBIExtractRepos.jar file and a number of other supportingjar files, depending on your configuration. For details, please review the contents ofmrextract.bat (mrextract on UNIX) in the WebFOCUS76\utilities directory.

configpath

Is the full or relative path to the directory containing the WebFOCUS Web application'sdeployment descriptor web.xml (for example,d:\ibi\WebFOCUS76\webapps\webfocus76\WEB-INF). From this file, the value ofwebfocus_client_root is read and used to determine the location of the WebFOCUS scriptfiles.

option

Program options include [-users] [-roles] [-groups] [-domains] [-domaincontent].

>

Redirects the utility's output to a file.


9. Managed Reporting Extract Utility

outputfile

The name of the output file.

You can tailor the extract utility for your own purposes.

Managed Reporting Extract Utility Output FilesOutput files extracted by the Managed Reporting Extract utility contain comma-delimitedinformation.

Extracting User InformationExample:

When you generate an output file for user information, the data is written in the followingformat:

"user_htm","mr_id","user_properties","user_description","group_href"

One line is generated in the output file for each group to which the user belongs. For example,

"wfuser.htm","wfuser","active,htmluser,","user descript.","#default""abcuser2.htm","abcuser2","active","ABC User 2 Desc","#abccommongro""abcuser2.htm","abcuser2","active","ABC User 2 Desc","#abcgroup2""abcuser1.htm","abcuser1","active","ABC User 1 Desc","#abccommongro""abcuser1.htm","abcuser1","active","ABC User 1 Desc","#abcgroup1""verylong.htm","verylongusernameindeed","active","jimsmith","#abccommongro""admin.htm","admin","admin,robot,robot,shared,sync","defaultuser","#default""phil.htm","phil","active,shared,robot","phil","#default""phil.htm","phil","active,shared,robot","phil","#verylonggrou""javauser.htm","javauser","active,robot,shared","javauser","#default""javauser.htm","javauser","active,robot,shared","javauser","#verylonggrou"

Extracting Group InformationExample:

When you generate an output file for group information, the data is written in the followingformat:

"group_href","group_description","domain_htm"

174 WebFOCUS

Managed Reporting Extract Utility Output Files

For example,

"#verylonggrou","verylonggroup name indeed","untitled/untitled.htm""#verylonggrou","verylonggroup name indeed","a77q8wik/a77q8wik.htm""#verylonggrou","verylonggroup name indeed","jimv0o1e/jimv0o1e.htm""#abccommongro","ABC Common Group","abccommo/abccommo.htm""#default","default group","untitled/untitled.htm""#abcgroup2","ABC Group 2","a77q8wik/a77q8wik.htm""#abcgroup2","ABC Group 2","db5cwlin/db5cwlin.htm""#abcgroup1","ABC Group 1","abcdomai/abcdomai.htm""#mrgroup2","MR Group 2","samplere/samplere.htm""#mrgroup1","MR Group 1","salesrep/salesrep.htm"

Extracting Domain InformationExample:

When you generate an output file for domain information, the data is written in the followingformat:

"domain_htm","domain_properties","domain_description"

For example,

"jimssumm/jimssumm.htm","disabled","Jim's Summit Domain""untitled/untitled.htm","none","zzManagement Reporting (Development Area)""db5cwlin/db5cwlin.htm","none","ABC Domain 2""samplere/samplere.htm","none","zzSales Reporting (Development Area)""philipse/philipse.htm","none","Company Reporting""abccommo/abccommo.htm","none","ABC Common Domain""a77q8wik/a77q8wik.htm","none","ABC Domain 2 (test)""salesrep/salesrep.htm","none","Sales Reporting""jimv0o1e/jimv0o1e.htm","","jim""abcdomai/abcdomai.htm","none","ABC Domain 1"

Extracting Domain Content InformationExample:

When you generate an output file for domain content information, the data is written in thefollowing format:

"domain_htm","record_type","record_subtype","item_href","item_description","item_flags","item_folder"

Note:

The record_type indicates the type of item found. Possible values are: HELP, PROFILE,OTHER (Others Files), STDRPT (Standard Report), or RPTOBJ (Reporting Object).

The record_subtype indicates the type of Standard Report or Reporting Object item found.Possible values are: ITEM or FOLDER. If the type is not ITEM or FOLDER, record_subtypeis empty.



The item_href is the item's reference. This is prefixed with the following charactersdepending on its type:

#foldername when the item is a folder.

app/standardreportname.fex when the item is a Standard Report.

mrv/reportingobjectname.fex when the item is a Reporting Object.

For example,

"domain01/domain01.htm","HELP","","app/help.htm","Help","","""domain01/domain01.htm","STDRPT","FOLDER","#dailyreports","Daily Reports","belongsto=#salesreports","#salesreports""domain01/domain01.htm","STDRPT","ITEM","app/salestra.fex","Sales Transactions","node=UNIXSRV8E,appname=salesdtl","#dailyreports""domain01/domain01.htm","STDRPT","FOLDER","#salesreports","Sales Reports","none","""domain01/domain01.htm","STDRPT","FOLDER","#weeklyreport","Weekly Reports","belongsto=#salesreports","#salesreports""domain01/domain01.htm","STDRPT","ITEM","app/salesana.fex","Sales Analysis","runasolap","#weeklyreport""domain01/domain01.htm","STDRPT","ITEM","app/salesbyb.fex","Sales by Branch","none","#weeklyreport""domain01/domain01.htm","RPTOBJ","FOLDER","#salesdatau5t","Sales Data","none","""domain01/domain01.htm","RPTOBJ","ITEM","mrv/customer.fex","Customers","suffix","#salesdatau5t""domain02/domain02.htm","HELP","","app/help.htm","Help","","""domain02/domain02.htm","STDRPT","FOLDER","#inventoryrep","Inventory Reports","none",""


Reference:

IBIMRUSR.MAS

IBIMRROL.MAS

IBIMRGRP.MAS

IBIMRDOM.MAS

IBIMRDMC.MAS

The following Master Files (.MAS) and sample procedures (.FEX) are provided for yourreference:

IBIMRUSR.MAS on page 177

176 WebFOCUS


IBIMRROL.MAS on page 177

IBIMRGRP.MAS on page 178

IBIMRDOM.MAS on page 178

IBIMRDMC.MAS on page 179

Using the MRSAMP01 Procedure to Relate Users to Domains on page 180

Using the MRSAMP02 Procedure to List Domain Contents on page 181

On Windows systems, these files are found in the drive:\ibi\apps\ibisamp directory. OnUNIX systems, these files are found in the /ibi/apps/ibisamp directory. The IBISAMPapplication is configured as the server's default search path.

On z/OS systems, the Master Files are in the library allocated to EDAMFD and the FOCEXECfiles are in the library allocated to EDARPC.

IBIMRUSR.MASReference:

IBIMRUSR.MAS Master File$-----------------------------------------------------------------------$ IBIMRUSR.MAS$-----------------------------------------------------------------------FILE=IBIMRUSR, SUFFIX=COMSEGNAME=IBIMRUSR, SEGTYPE=S0FIELD=USER_HTM, ALIAS=E01, ACUTAL=A12, USAGE=A12, $FIELD=USER_ID, ALIAS=E02, ACUTAL=A48, USAGE=A48, $FIELD=ROLE_HREF, ALIAS=E06, ACUTAL=A48, USAGE=A48, $FIELD=USER_PROP, ALIAS=E03, ACUTAL=A256, USAGE=A256, $FIELD=USER_DESC, ALIAS=E04, ACUTAL=A256, USAGE=A256, $FIELD=GROUP_HREF, ALIAS=E05, ACUTAL=A13, USAGE=A13, $

IBIMRROL.MASReference:

IBIMRUSR.MAS Master File$-----------------------------------------------------------------------$ IBIMRROL.MAS$-----------------------------------------------------------------------FILE=IBIMRROL, SUFFIX=COMSEGNAME=IBIMRROL, SEGTYPE=S0FIELD=ROLE_HREF, ALIAS=E01, ACUTAL=A48, USAGE=A48, $FIELD=ROLE_NAME, ALIAS=E02, ACUTAL=A48, USAGE=A48, $FIELD=FIX_PROP, ALIAS=E03, ACUTAL=A255, USAGE=A255, $FIELD=OPT_PROP, ALIAS=E04, ACUTAL=A255, USAGE=A255, $FIELD=SEL_PROP, ALIAS=E05, ACUTAL=A255, USAGE=A255, $



IBIMRGRP.MASReference:

IBIMRGRP.MAS Master File$-----------------------------------------------------------------------$ IBIMRGRP.MAS$-----------------------------------------------------------------------FILE=IBIMRGRP, SUFFIX=COMSEGNAME=IBIMRGRP, SEGTYPE=S0FIELD=GROUP_HREF, ALIAS=E01, ACUTAL=A13, USAGE=A13, $FIELD=GROUP_DESC, ALIAS=E02, ACUTAL=A256, USAGE=A256, $FIELD=DOMAIN_HTM, ALIAS=E03, ACUTAL=A21, USAGE=A21, $

IBIMRDOM.MASReference:

IBIMRDOM.MAS Master File$-----------------------------------------------------------------------$ IBIMRDOM.MAS$-----------------------------------------------------------------------FILE=IBIMRDOM, SUFFIX=COMSEGNAME=IBIMRDOM, SEGTYPE=S0FIELD=DOMAIN_HTM, ALIAS=E01, ACUTAL=A21, USAGE=A21, $FIELD=DOMAIN_PROP, ALIAS=E02, ACUTAL=A40, USAGE=A40, $FIELD=DOMAIN_DESC, ALIAS=E03, ACUTAL=A256, USAGE=A256, $

178 WebFOCUS


IBIMRDMC.MASReference:

IBIMRDMC.MAS Master File;Master Files:IBIMRDMC.MAS$------------------------------------------------------------------$ IBIMRDMC.MAS$------------------------------------------------------------------FILE=IBIMRDMC, SUFFIX=COM, REMARKS='MR Domain Content Data', SEGNAME=IBIMRDMC, SEGTYPE=S0FIELD=DOMAIN_HTM, ALIAS=E01, ACTUAL=A21, USAGE=A21, TITLE='Domain,Reference', DESC='Joins many to one with DOMAIN_HTM in domains extract.',$FIELD=REC1, ALIAS=E02, ACTUAL=A6, USAGE=A6, TITLE='Record,Type', DESC='Values: HELP, OTHER, STDRPT, RPTOBJ, or PROFILE', $FIELD=REC2, ALIAS=E03, ACTUAL=A6, USAGE=A6, TITLE='Record,Sub-type',DESC='Values: ITEM, FOLDER, or null', $FIELD=ITEM_HREF, ALIAS=E04, ACTUAL=A16, USAGE=A16, TITLE='Item,Reference', DESC='Item reference', $FIELD=ITEM_DESC, ALIAS=E05, ACTUAL=A256, USAGE=A256, TITLE='Item Name', DESC='Item description.',$FIELD=ITEM_PROP, ALIAS=E06, ACTUAL=A256, USAGE=A256,TITLE='Item,Properties',DESC='The properties for this item.',$FIELD=ITEM_FOLDER, ALIAS=E07, ACTUAL=A13, USAGE=A13, TITLE='Item Folder',DESC='Folder href this item belongs in.',$



Using the MRSAMP01 Procedure to Relate Users to DomainsExample:

SET PCOMMA=ON-* Windows/UNIX: edit FILEDEFs below as appropriate or put in EDASPROF.PRF insteadFILEDEF IBIMRUSR DISK c:\ibi\WebFOCUS76\utilities\IBIMRUSR.TXTFILEDEF IBIMRGRP DISK c:\ibi\WebFOCUS76\utilities\IBIMRGRP.TXTFILEDEF IBIMRDOM DISK c:\ibi\WebFOCUS76\utilities\IBIMRDOM.TXT-* z/OS: remove FILEDEFs, uncomment and edit DYNAMs below as appropriate-* DYNAM ALLOC FILE IBIMRUSR DSN 'hlq.IBIMRUSR.TXT' SHR REU-* DYNAM ALLOC FILE IBIMRGRP DSN 'hlq.IBIMRGRP.TXT' SHR REU-* DYNAM ALLOC FILE IBIMRDOM DSN 'hlq.IBIMRDOM.TXT' SHR REU-RUNSET ALL=ONTABLE FILE IBIMRUSRPRINTON TABLE HOLD AS USERINFO FORMAT FOCUS INDEX GROUP_HREFEND-RUNTABLE FILE IBIMRDOMPRINT *ON TABLE HOLD AS DOMINFO FORMAT FOCUS INDEX DOMAIN_HTMEND-RUNTABLE FILE IBIMRGRPPRINT *ON TABLE HOLD AS GROUP FORMAT FOCUS INDEX GROUP_HREFEND-RUNJOIN GROUP_HREF IN USERINFO TO ALL GROUP_HREF IN GROUP AS J1JOIN DOMAIN_HTM IN USERINFO TO DOMAIN_HTM IN DOMINFO AS J2-RUNTABLE FILE USERINFOPRINTDOMAIN_HTMBY USER_IDBY USER_DESCBY GROUP_DESCBY DOMAIN_DESCEND

Note: The SET PCOMMA=ON command is required to report from these files. It can be setin the procedure (as it is in the sample report) or in the WebFOCUS Reporting Server's profile.

180 WebFOCUS


Using the MRSAMP02 Procedure to List Domain ContentsExample:

* ----------------------------------------------------------------* MRSAMP02.FEX-* For use with MR Extract utility. See MR administrator documentation.-* ----------------------------------------------------------------

SET PCOMMA=ON-* Windows/UNIX: edit FILEDEFs below as appropriate or put in EDASPROF.PRFFILEDEF IBIMRDOM DISK c:\ibi\WebFOCUS76\utilities\IBIMRDOM.TXTFILEDEF IBIMRDMC DISK c:\ibi\WebFOCUS76\utilities\IBIMRDMC.TXT-* z/OS:remove FILEDEFs,uncomment and edit DYNAMs below as appropriate-* DYNAM ALLOC FILE IBIMRDOM DSN 'hlq.IBIMRDOM.TXT' SHR REU-* DYNAM ALLOC FILE IBIMRDMC DSN 'hlq.IBIMRDMC.TXT' SHR REU-RUNSET ALL=ONTABLE FILE IBIMRDOMPRINT *ON TABLE HOLD AS DOMINFO FORMAT FOCUS INDEX DOMAIN_HTMEND-RUNTABLE FILE IBIMRDMC PRINT *ON TABLE HOLD AS CONTENT FORMAT FOCUS INDEX DOMAIN_HTMEND-RUNJOIN DOMAIN_HTM IN DOMINFO TO ALL DOMAIN_HTM IN CONTENT AS J1-RUNTABLE FILE DOMINFO PRINTITEM_HREF ITEM_FOLDER ITEM_PROP BY DOMAIN_DESCBY REC1BY REC2BY ITEM_DESCEND




In this section:

Sending the Data Files

Allocating the Extract Files to the WebFOCUS Reporting Server

Output File Relationships

You can use WebFOCUS to report from the Managed Reporting extract files (for example,ibimrusr.txt, ibimrgrp.txt, ibimrdom.txt), provided that:

The extract files reside on the WebFOCUS Reporting Server.

File allocations (FILEDEF or DYNAM ALLOC) are either:

Specified within the procedure.

Specified within a WebFOCUS Reporting Server profile.

You set PCOMMA=ON in your WebFOCUS request since the extract data iscomma-delimited with double-quotation marks around each value.

Sending the Data FilesIf you are running the WebFOCUS Client and WebFOCUS Reporting Server on differentmachines, you must FTP the extract files to the WebFOCUS Reporting Server machine.Perform this in ASCII mode using the FTP utility of your choice.

Note: If you are sending the files to an z/OS-based system, your system administrator mayhave configured the FTP server to truncate incoming data at a fixed width, such as 128characters. Your IBIMRUSR.TXT file may exceed 128 characters per line. During FTP, takenote of the command log to see if the data was truncated. If this is the case, issue thefollowing command at the FTP prompt:

QUOTE SITE LRECL=nnn

where:

nnn

Is the number of characters to set for the maximum line width.

Reissue the FTP PUT command and verify that the data was not truncated.

182 WebFOCUS


Allocating the Extract Files to the WebFOCUS Reporting Server

How to:

Allocate Extract Files on Windows Systems

Allocate Extract Files on UNIX-Based Systems

Allocate Extract Files on z/OS-Based Systems

Allocate Extract Files on OpenVMS and AS/400-Based Systems

Depending on the platform on which your WebFOCUS Reporting Server is running, thecommand syntax is different. However, in all cases you may place the commands individuallywithin each report procedure or globally in a WebFOCUS Reporting Server profile.

How to Allocate Extract Files on Windows SystemsSyntax:

IBIMRDMC.MAS Master FileFILEDEF IBIMRUSR DISK drive:\path\IBIMRUSR.TXTFILEDEF IBIMRROL DISK drive:\path\IBIMRROL.TXTFILEDEF IBIMRGRP DISK drive:\path\IBIMRGRP.TXTFILEDEF IBIMRDOM DISK drive:\path\IBIMRDOM.TXTFILEDEF IBIMRDMC DISK drive:\path\IBIMRDMC.TXT

where:

drive:\path

Is the disk location of the files.

How to Allocate Extract Files on UNIX-Based SystemsSyntax:

FILEDEF IBIMRUSR DISK /path/IBIMRUSR.TXTFILEDEF IBIMRROL DISK /path/IBIMRROL.TXTFILEDEF IBIMRGRP DISK /path/IBIMRGRP.TXTFILEDEF IBIMRDOM DISK /path/IBIMRDOM.TXTFILEDEF IBIMRDMC DISK /path/IBIMRDMC.TXT

where:

path




How to Allocate Extract Files on z/OS-Based SystemsSyntax:

DYNAM ALLOC FILE IBIMRUSR DSN 'hlq.IBIMRUSR.TXT' SHR REUDYNAM ALLOC FILE IBIMRROL DSN 'hlq.IBIMRROL.TXT' SHR REUDYNAM ALLOC FILE IBIMRGRP DSN 'hlq.IBIMRGRP.TXT' SHR REUDYNAM ALLOC FILE IBIMRDOM DSN 'hlq.IBIMRDOM.TXT' SHR REUDYNAM ALLOC FILE IBIMRDMC DSN 'hlq.IBIMRDMC.TXT' SHR REU

where:

hlq

Is the high-level qualifier for the extract files.

How to Allocate Extract Files on OpenVMS and AS/400-Based SystemsSyntax:

filedef ibimrusr disk disk$pm:[ibimrusr.txt]filedef ibimrrol disk disk$pm:[ibimrrol.txt]filedef ibimrgrp disk disk$pm:[ibimrgrp.txt]filedef ibimrdom disk disk$pm:[ibimrdom.txt]filedef ibimrdmc disk disk$pm:[ibimrdmc.txt]

where:

disk$pm


Output File RelationshipsThe following diagram illustrates the relationships between the output files:

A user appears in the IBIMRUSR data multiple times if they belong to multiple groups.Similarly, a group appears in the IBIMRGRP data multiple times if it contains multiple domains.A domain only appears once in the IBIMRDOM data. A domain always appears more thanonce in the IBIMRDMC data because each item record is qualified with its domain.

184 WebFOCUS


Property Flags

Reference:

User.htm and Role.htm Flags

Mrrepos.htm Flags

Domainname.htm Flags

The WebFOCUS Client writes property flags to the user.htm, role.htm, mrrepos.htm, anddomain.htm files to control the behavior of Managed Reporting. Knowledge of these flagscan help administrators to better understand reports written from the extract files.

User.htm and Role.htm FlagsReference:

The following table describes the flags that may be encountered in the USER_PROP field inthe IBIMRUSR.MAS Master File as well as the FIX_PROP, OPT_PROP, and SEL_PROP fieldsof the IBIMRROL.MAS file.

DescriptionFlag

Indicates the user has Managed ReportingAdministrator privileges.

admin

Indicates the user has the Advanced privilege.advanced

Indicates the Analytic User can save reports andcreate My Reports.

auser

Indicates the developer is restricted toadministering only the default domain, which hasthe internal reference "untitled," and the SalesDomain. The characters %2c delimit the domainswhen there is more than one domain.

dadomains=untitled%2csalesdom

Indicates the developer has access to the DataServers feature and can set the server andapplication path properties of a Domain.

dataserver

Indicates the user is a developer.domadmin

Used with ReportCaster library.email=address



DescriptionFlag

Indicates that the user is a group administratorfor the Default Group, which has the internalreference "default." The characters %2c delimitmultiple group values similar to the dadomainsflag.

gagroups=group%2cgroup

Indicates the user account is disabled.inactive

Indicates to the Managed Reporting Dashboarduser interface to invoke tools and online help thatare in compliance with federal Section 508accessibility regulations. For more information,see Handicapped Accessibility in WebFOCUS in theDeveloping Reporting Applications manual.

is508

User can use ReportCaster Library.library

Indicates that a user can save the parametervalues entered in a form into a new My Report.

parmrpt

ReportCaster Administrator.rcadmin

Indicates the user has scheduling privileges.robot

Indicates an Analytical User can Save My Reports.savemyreports

Indicates the user can share reports.shared

Basedir in Managed Reporting. Cannot use tools;can only run reports.

user

Note: The user flags are not order-dependent. The flags display based upon the order theywere added from within the Managed Reporting Administration interface.

186 WebFOCUS

Property Flags

Mrrepos.htm FlagsReference:

The following table describes the flags that may be encountered in the DOMAIN_PROP fieldin the IBIMRDOM.MAS Master File:

DescriptionFlag

Indicates the domain is active.'' or 'none'

Indicates the domain was deleted.disabled

Domainname.htm FlagsReference:

Each Domain has its own control file, which maintains the metadata for its resources. Thefollowing table describes the flags that are in the control files.

DescriptionFlag

Application path. Series of one or more applicationnames, separated by encoded spaces. For example,appname=financials%20inventory

appname=application_path

Parent of subfolder.belongsto=#parentfoldername

User who last modified a property item. The encodedvalue of a user name concatenated with a user ID, suchas lastmodby=Doe%2C+John+%28jd12345%29.

createdby

Date and time when a user created a property item.Specifies elapsed milliseconds since 1970, which istranslated into the appropriate date and time format.

createdon

Run with drag and drill.dragdrill

Filter is present in request.filter

Report is hidden from view.hidden

User who last modified a property item. The encodedvalue of a user name concatenated with a user ID, suchas lastmodby=Doe%2C+John+%28jd12345%29.

lastmodby

Published launch file.launch



DescriptionFlag

WebFOCUS Reporting Server.node=servernodename

No flags are set.none

A saved OLAP report.olapreport

Link to Two-Way Email procedure.ptmfex=applicationname/fexname.fex

OLAP enables a report.runasolap

Allows the Reporting Object to appear as a Standardreport.

showasreport

Shows a Reporting Object only as a report.showonlyreport

Does not prompt for parameter.skipamper

Used with a TABLE and GRAPH combination to specifyto split the frame.

splithorizontal

Reporting Object contains a suffix.suffix

Request is for Two-Way Email.tellme

Specifies that a Standard Report is a URL.url

188 WebFOCUS

Property Flags

WebFOCUS

Change Management10Topics:

Change management is the process ofmoving application components betweenWebFOCUS environments. Typically, Understanding the Change

Management ProcessDevelopers move componentsbetween development and testingenvironments.

Managed Reporting DevelopmentEnvironment

Systems or production controlprofessionals move componentsbetween testing and productionenvironments.

Understanding Internal ManagedReporting References

Managed Reporting ChangeManagement Features

There are features and methodologiesin Managed Reporting that can be usedto facilitate these important tasks.

Change Management Extract Utility

Change Management Load UtilityFor more information about configuringmultiple WebFOCUS environments, seethe Best Practices guide titled EnterpriseImplementation Considerations forWebFOCUS Reporting.

Dashboard Change Management


Understanding the Change Management ProcessDeveloping an application is an iterative process. Developers are constantly revising piecesof their application and periodically moving these components to the test environment forfeedback. At some point, user feedback must be solicited and the application must bestabilized. After an application is released for general use, problems must be fixed, tested,and incorporated into the production environment. This is the essence of changemanagement, which is also sometimes referred to as configuration management or productioncontrol.

Organizations vary widely in how they approach change management. Some delegate muchof the responsibility to developers while others establish separate organizations to maintaina higher degree of control. Typically, developers prefer to stay in their development toolenvironment to perform these duties while change management professionals prefer batch-oriented and API-based methods to move application components between environments.Developers may be required to implement a user-developed change management applicationin order to initiate changes after the application is moved to production. A combination ofthese approaches is often used in larger companies.

The examples that follow illustrate two different change management processes that mightbe found in a company. These sections describe product features and methodologies thatcan be utilized by companies to meet their change management objectives with ManagedReporting.

Moving Application Files: A Simple Change Management ProcessExample:

As shown in the following image, developers move application files between the developmentand test environments using their development tool. When the application is finished, asystems person copies the application from test to production using operating systemutilities. There may only be a single test environment.

190 WebFOCUS

Understanding the Change Management Process

Moving Application Files: A Comprehensive Change Management ProcessExample:

In this example, four WebFOCUS environments are established to increase the level of controlover the process. Developers use the Explorer window in Managed Reporting Developer forWindows and Developer Studio to move application files from development to test. Developersthen sign on to the Change Management Extract Utility when they are ready to move theirchanges to the user acceptance test environment. The Change Management Extract Utilityallows the Developer to select the file(s) to be moved and creates a change package on theWeb platform that an administrator can subsequently insert into an acceptance test usingthe Change Management Load Utility or (Java) Load Program called IBILoadRepos. Someorganizations may choose to call the Load program from an automated process in order toachieve better integration with their business processes.

As shown in the following image, when the application is deemed ready for release, thechange management organization initiates a file system copy of the application to theproduction environment. Users begin using the application and the change managementprocess shifts into an application maintenance support role. From this point forward,incremental updates to production are facilitated by administrators using the CM Loadprogram.

Managed Reporting Development EnvironmentWhen you are developing a Managed Reporting application, you are working with files thatare controlled by the WebFOCUS Client and stored in a centralized location called the ManagedReporting Repository. There is no decentralized local developer copy of this repository or ofManaged Reporting files. Regardless of whether the Developer is using the Java applet orDeveloper Studio tools, the process entails retrieving a copy of the file(s), making changesto the file, and saving the files back to the repository.

All Managed Reporting developers work in a common repository simultaneously and movetheir application components to a common test environment. Managed Reporting enablestwo or more developers to work on different parts of the application simultaneously, withoutaffecting each other. However, when two or more developers are working on files in a singleDomain, the responsibility is on the developers to coordinate their changes. For example,if two developers are working on the same report file at the same time, the last one savingthe file overwrites any changes the first developer may have made.


10. Change Management

Understanding Internal Managed Reporting ReferencesDevelopers and end users see and use Descriptions to navigate their way about ManagedReporting. Managed Reporting uses internal references instead to locate and processrequests for Managed Reporting resources.

At any time, developers are free to change these Descriptions. Users will see changes thenext time they log on to Managed Reporting (or refresh their view). A Description changedoes not affect how the file is processed, since the internal reference remains the same.

The following are internal references for Managed Reporting objects:

Domain. Visible on the Domain Properties dialog box (for example, untitled/untitled.htm).

Standard Report. Visible on the Report Properties dialog box (for example,app/prospect.fex or app/launchpa.htm).

Reporting Object. Visible on the Reporting Object Properties dialog box (for example,mrv/salesdat.fex).

Folders and Sub-Folders. Visible on the object's Property dialog box (for example,#westernregio).

Repository. This is not visible from within the Java applet tools, but you can specify tooverride the default value on the signon page. Developers using Developer Studio canspecify the repository within the WebFOCUS Environment Properties dialog box. (For moreinformation, see the Developing Reporting Applications With Graphical Tools manual.) Thevariable MR_BASE_DIR specifies the full operating system path to the root of the ManagedReporting Repository (for example, d:\ibi\WebFOCUS76\basedir) and is defaulted in theWebFOCUS script file, cgivars.wfs.

When you create a Domain, Report, or Folder with the tools, Managed Reporting generatesthe internal reference for the object and stores it. The Description you provided is used tocreate the reference.

Note: When you create a Description, spaces and special characters are removed and thereference is truncated to a fixed length.

If you create another object with a similar Description, Managed Reporting will randomlygenerate the reference to ensure that each reference is unique within its namespace.

Products and features that use internal Managed Reporting references include:

Published Launch pages (inside or outside the repository).

ReportCaster (to retrieve the report at execution time).

Drill down links.

End user My Reports.

192 WebFOCUS

Understanding Internal Managed Reporting References

When moving files between Managed Reporting Repositories, such as between yourdevelopment and test environments, it is critical that these references (and the Descriptions)remain the same. This can be accomplished by:

Creating the domains in each of your environments in the same order. The internalreferences will be created the same in each.

Using the Properties dialog box to check references.

Paying attention to alert windows when copying files.

Testing your application before moving it into the production environment.

Using the CM Extract and CM Load program to move Domain files between environments.

Managed Reporting Change Management Features

In this section:

Copying Files Between Environments Using Developer Studio

Copying a Domain Between Environments Using Developer Studio

The following sections describe features or methodologies that can help organizationsachieve their change management objectives with Managed Reporting.



Copying Files Between Environments Using Developer StudioFrom the Windows Explorer window, you can drag and drop (or copy/paste) a modifiedprocedure called Prospecting Activity from your Development environment to the WesternRegion folder of the User Test environment as shown in the following image.

194 WebFOCUS


A status window shows the progress of the copy operation. Note the internal folder reference,#westernregio, of the procedure being copied as shown in the following image.

If the procedure already exists in the destination (meaning that this procedure's internalreference is already being used), an alert window appears to confirm replacing the existingprocedure as shown in the following image.

If you are sure that the procedure you are copying is an update of the one in the target, clickYes (or Yes to All) and it will be updated. If you click No, your file will be copied to the targetRepository and a new internal reference will be generated for it. In this case, it is yourresponsibility to resolve problems with other products and features that may be relying onthis reference, which you have agreed to change. See Understanding Internal ManagedReporting References on page 192.



Copying a Domain Between Environments Using Developer StudioFrom the Explorer window, you can drag and drop (or copy/paste) the contents of an entireDomain called Sales from your Development environment to the Domains folder of the UserTest environment as shown in the following image.

A status window shows the progress of the copy operation. Note the internal reference,salesrep/salesrep.htm, of the Domain being copied.

If the Domain already exists in the destination (meaning that this Domain's internal referenceis already being used), an alert window appears.

If you are sure that the Domain you are copying is a complete replacement for the one inthe target, click Yes or Yes to All and it will be updated. If you click No, your Domain will becopied to the target Repository and a new internal reference will be generated. In this case,it is your responsibility to resolve problems with other products and features that may berelying on this reference, which you have agreed to change. See Understanding InternalManaged Reporting References on page 192 for more information.

196 WebFOCUS



How to:

Access and Use the Change Management Extract Utility

Reference:

Extracting Repository Metadata

Many organizations do not grant developers write access to the user acceptance test andproduction environments. Access to these environments is controlled and granted only toadministrators and/or automated change management processes. Yet only developers knowwhich changes are ready to be moved into test. The Change Management Extract Utilitypresents developers with a graphical view of the Managed Reporting domains they manageand allows them to build a change package. This package is then loaded into anotherenvironment by a Managed Reporting Administrator using the Change Management LoadUtility or the (Java) Load Program named IBILoadRepos.

How to Access and Use the Change Management Extract UtilityProcedure:

1. Launch the WebFOCUS Welcome Page in the environment where you want to create achange package with the Change Management Extract Utility.

http://hostname[:port]/ibi_apps/

where

hostname[:port]

Is the name of the Web server and optional port number (specified only if you arenot using the default port number) where the WebFOCUS Web application in thedesired environment is deployed.

2. Click the Managed Reporting Change Management Extract link.

3. Type your Managed Reporting Administrator or Developer user ID and password andclick Logon.

The Change Management Extract Utility loads and displays the Domains to which thedeveloper or administrator has access.



The following image shows the Change Management Extract Utility available toadministrators, which displays the Domains Tree pane on the left and the Selected Filesand Domains pane on the right. The available options include Download File (default)and Save on Server.

Note: The Extract Repository Metadata button only displays for administrators. For moreinformation, see Extracting Repository Metadata on page 200.

4. Expand the folders in the Domains Tree pane. You can select individual items from adomain or the contents of an entire domain for your change package.

You can single-click (or drag and drop) one or more items from a domain. You can alsoselect the domain's help and profile files.

You can also double-click (or drag and drop) a domain to conveniently select all of thecontent from this domain. Properties of the domain, for example, its Server and/orApplication Path, are not propagated by the change management process. Note that aselected domain is a collection of the domain's content, not a complete clone of theoriginal domain.

When you select an item or domain, it appears in the Selected Files and Domains list.If you select duplicate items or domains, they are only added to the change packageonce. You should not select individual items from a domain that is already selected.

5. If you need to remove an item or domain from the Selected Files and Domains list,select the item and press the Delete key.

To remove all items and domains from the Selected Files and Domains list, click theClear File List button.

198 WebFOCUS


6. By default, the Download File option is selected. Click Create Change Package to downloadthe change package to your browser. You will then have the option to open it or save itlocally, as shown in the following image.

The naming format for the change package is: YYYYMMDD_admin_HHMMSS.zip. Theformat is Java Zip (which is WinZip compatible). If you have WinZip installed locally, openthe change package. To ensure that the Change Management utility recognizes the fileand processes it correctly, do not change the file name or the .zip file extension.

The contents of the change package includes the extracted file(s) and a cmRepos.xmldocument that contains metadata about the file(s), such as their internal referencesand properties, as shown in the following image.

If the Save on Server option is selected, the following window opens to provide you withthe name of the change package created on the server.



Consider whether you want developers to download and e-mail change packages to acoordinator, or create the packages on the Web server platform. Packages created onthe server are written to install_dir/WebFOCUS76/utilities/cm/extract. You can changethis location by editing the WebFOCUS deployment descriptor (web.xml) and changingthe value of the context-parameter MRCMEXTRACTDIR. The directory specified by thissetting must exist and be writable by the servlet container. You may want to havedevelopers create the package on the server, and also download and e-mail them to acoordinator. This may help audit the change process since you have a record of theDeveloper's intent, and can load the packages from a controlled location.

Note: To ensure that the contents of a change package are not altered in any way,Information Builders recommends that you always load change packages that werecreated on the server.

Extracting Repository MetadataReference:

The Extract Repository Metadata link takes you to a pane where you can extract metadatafrom the Repository for analysis. Administrators can query the Repository for metadata fromthis page. This may be helpful in planning or debugging. For more information about theoutput generated from these options (Users, Roles, Groups, Domains, Domains Contents),see Managed Reporting Extract Utility on page 171. To return to the Change ManagementExtract Utility, click Return to Change Package Window.

The following image shows the Extract Repository Metadata pane containing metadatainformation for Extract Roles.

200 WebFOCUS


Note: For additional convenience, the MR Change Management Extract Utility is also availablefrom the Administration Console in the Utilities section of the main menu. The interface isslightly different, but the functionality is the same. For more information, see the WebFOCUSSecurity and Administration manual.

Change Management Load Utility

In this section:

Alternate Change Management Load Program

How to:

Access and Use the Change Management Load Utility

Reference:

Change Management Load Utility Options

The Change Management Load Utility enables Managed Reporting administrators to loadspecific change packages created with the Change Management Extract Utility into anotherenvironment.

Change packages are loaded into the target repository using a Java program calledIBILoadRepos. If an item's domain does not exist during the load process, the ChangeManagement Load Utility creates the domain automatically and a message is written to thecmevent.log file.

It is recommended that you create domains in the development environment using theDomain Builder and allow the Change Management Load Utility to automatically createdomains in your test and production environments. This is beneficial because creating andthen deleting a domain in the target repository results in the Change Management LoadUtility being unable to load items into it. When a domain is deleted, its entry in mrrepos.htmis set to disabled instead of being deleted. The Change Management Load Utility is unableto load items into a disabled domain and cannot create a new domain with the correct HREF.In this situation, an error is written to the cmevent.log file and the item is not loaded.

How to Access and Use the Change Management Load UtilityProcedure:

1. Move the desired change packages from the source \utilities\cm\extract directory orother specified location, to the target environment's \utilities\cm\load directory or anyof the subdirectories of \utilities\cm.

Note: If the Realm Driver is being used in the target environment to authenticate and/orauthorize to a relational DBMS, make sure that the path to the JDBC drivers are definedin your application server classpath. For example, if using MSSQL Server for MRauthentication, the path to the drivers would be defined in the Java Classpath for Tomcat.



2. Go to the WebFOCUS Welcome Page on the target environment where you want to loadthe change package created with the Change Management Extract Utility.

http://hostname[:port]/ibi_apps/

where

hostname[:port]

Is the name of the Web server and optional port number where the WebFOCUS Webapplication in the desired target environment is deployed.

3. Click the Managed Reporting Change Management Load link.

4. Type your Managed Reporting Administrator user ID and password and click Logon.

The Change Management Load Utility loads and displays any folders in the \utilities\cmdirectory that contain .zip files.

5. Select a desired .zip file change package in the Available Change Packages pane tocopy it to the Selected Change Packages pane. You can single-click, double-click, ordrag and drop the change package as shown in the following image.

The options you can select include Overwrite duplicates (default), Backup packages(available only when Overwrite duplicates is selected), Preserve Creation info, andPreserve Modifier info. For details, see Change Management Load Utility Options on page203.

202 WebFOCUS


6. To remove a selected change package from the Selected Change Packages list, selectthe item and press the Delete key. To remove all selected change packages, click theClear File List button.

7. Click Load Change Package to load the change package into the MR repository of yourtarget environment.

A pop-up message appears when the load process is completed. Click Open Log File toview the contents of the cmevent.log file that was created in the \utilities\cm\ directory.The log file displays helpful information about the success or failure of the load process.

Note: For additional convenience, the MR Change Management Load Utility is also availablefrom the WebFOCUS Adminstration Console in the Utilities section of the main menu. Formore information, see the WebFOCUS Security and Administration manual.

Change Management Load Utility OptionsReference:

The following describes the options you can apply when using the Change Management LoadUtility to load change packages into an environment.

Overwrite duplicates - If any files have the same internal reference in the source andtarget repositories, this option determines whether or not the internal reference ispreserved when the change package is loaded. For example, if a report with the description"Sales Report" and internal reference "app/salesrep.fex" already exists in the targetrepository, enabling the Overwrite duplicates option allows the report to be loaded withthe same description and internal reference. If Overwrite duplicates is unselected, a newreport file is created with the description "Sales Report (Copy 1)" and a new internalreference, for example, "app/gwrwko31.fex."

Backup packages - This option is only available if the Overwrite duplicates option isenabled. If selected, a back-out package is created that contains the original versionsof the files that are about to be overwritten. The back-out package is created in the\utilities\cm\backout directory with the same name as the package being loaded.

Preserve Creation Info - This option retains the report creation date and time, and thename (and user ID) of the person who created the report, by preserving the createdonand createdby flags found in the change package.

Preserve Modifier Info - This option retains the last modification date and time for theitems in the change package by preserving the lastmodby flag that is found in the package.



Alternate Change Management Load Program

How to:

Run the Alternate Change Management Load Program

Reference:

Preparing to Run the Alternate Change Management Load Program

IBILoadRepos Usage

The following topics explain how to prepare for, and how to run, the alternate ChangeManagement Load program.

Preparing to Run the Alternate Change Management Load ProgramReference:

In some cases you must edit the script file that calls IBILoadRepos before running the utility.This script file is found in the inst_dir\WebFOCUS76\utilities\cm directory and is namedcmload.bat (cmload on UNIX).

1. Verify that the setting MRID=admin is valid for your installation. You must set the variableMRID inside this script to a valid Managed Reporting (MR) user ID. Initially, this variableis set to admin to match the default MR administrator account. The ID specified doesnot need to have MR administration privileges; it must be a valid MR ID.

2. Set JDBC_DRIVER_JARS, if necessary. When using the Realm Driver to authenticateand/or authorize to a relational DBMS system you must set JDBC_DRIVER_JARS to thefull path to your driver's Jar file(s). If your driver is made up of multiple files, use thesemi-colon ';' as a separator on Windows and a colon ':' as the separator on UNIX.

3. If you are using a custom Realm Driver extension, you may need to include additionalJar file(s) in the class path of this utility to use it. Simply append these to theJDBC_DRIVER_JARS variable.

How to Run the Alternate Change Management Load ProgramProcedure:

1. Move the desired change packages from your source environment's /utilities/cm/extractdirectory to the target environment's /utilities/cm/load directory. By default, all changepackages in this directory will be loaded. Make sure that only the change packages youwant to process are located here.

2. Navigate to the WebFOCUS76/utilities/cm directory.

204 WebFOCUS


3. Execute the cmload.bat file (Windows systems) or cmload file (UNIX systems). A seriesof messages appear:

------------------------------------------------- Managed Reporting Change Management Load Utility WebFOCUS Release 7-------------------------------------------------Finished.Press any key to continue . . .

A log file, WebFOCUS76/utilities/cm/cmevent.log, is created with helpful informationabout the load. Each time a package is loaded, information is appended to cmevent.logfile.

IBILoadRepos UsageReference:

The underlying program that loads change packages into a Managed Reporting Repositoryis written in Java and is contained in the archive WebFOCUS76/utilities/cm/IBILoadRepos.jar.You call the program directory (or modify the cmload batch file) by using the following usagereference.

java [options] -cp archivepath ibi.srv.cm.IBILoadRepos arguments-createBackout-backoutDir -preserveCreationInfo -preserveModifierInfo

where options include:

-DinfoLogType={FILE|CON|OFF}

Optional. If you want informational messages associated with the load to be logged,select FILE to write them to cmevent.log in the current directory. Each time the loadprogram is run, messages are appended to this file. If you want these messages echoedto the command console, select CON, otherwise select OFF. Not specifying this optionis equivalent to selecting CON.

-DerrorLogType={FILE|CON|OFF}

Optional. If you want error messages associated with the load to be logged, select FILEto write them to cmevent.log in the current directory. Each time the load program is run,messages are appended to this file. If you want these messages echoed to the commandconsole, select CON, otherwise select OFF. Not specifying this option is equivalent toselecting CON.



where:

archivepath

Is the full or relative path to the IBILoadRepos.jar file, and the following supporting files:ibi_resolver_1_1.jar, ibi_xalan_2_7_0.jar, ibi_xalan_2_7_0_serializer.jar,ibi_xerces_2_7_1.jar, and ibi_xml_apis_1_3.jar. If you are using the Realm Driver, youmust also include uas.jar and supporting files (if any) such as your JDBC .jar files if theRealm Driver is using an RDBMS.

where arguments include:

-user userid

Required. The ID specified is required to initialize the IBILoadRepos program. This IDdoes not need to have MR administration privileges; it just needs to be a valid MR ID.

-confDir configpath

Required. Specifies the full or relative path to the directory containing the WebFOCUSdeployment descriptor file (web.xml). IBILoadRepos reads this file to locate severalsettings necessary to initialize itself, including webfocus_client_root and WFENCR (optionalencryption setting). With some application servers, this web.xml file is deployed to adifferent location in the file system. In this case, you may need to keep these filessynchronized or point -confDir to the deployed file.

-d loaddirectory | -f loadfile

Either -d or -f is required. Specifies the absolute or relative path to the directory containingthe change package .zip files or a single .zip file (depending on selection). If -d is selected,all .zip files in the specified directory are loaded (in sort order).

-noOverwrite

Optional. If specified, files found with the same internal reference are not overwrittenduring the load, and are loaded with a new internal reference instead. For example, if areport with the description "Sales Report" and internal reference "app/salesrep.fex" isbeing loaded with the -noOverwrite option and the same file already exists in the targetrepository, a new file is created with the description "Sales Report (Copy 1)" and newinternal reference, for example, "app/gwrwko31.fex".

A back-out package containing the original versions of the files you are about to update canbe created during the load. Open the batch file that calls IBILoadRepos and add:

-createBackout

By default, the back-out package is created in the backout subdirectory of the currentdirectory. If the backout directory does not exist, the utility creates it automatically. Thename of the back-out package is the same name as the package being loaded, this is whythe load and back-out directories must be different.

206 WebFOCUS


To specify a different directory, include the following with either a fully qualified or relativepath:

-backoutDir

This directory must exist or an error is written to the log file and the item is not loaded.

To back-out a change, move the back-out package into the load directory and rerun the Loadprogram.

You should create a different batch file for backing out changes because you do not wantto specify the -createBackout option when running the utility to back out a change. If theitems being added do not yet exist in the target environment, there will be no correspondingitems in the back-out package, and you must use the GUI tools to back-out the added items.

To preserve change history creation information, include:

-preserveCreationInfo

This retains the report creation date and time, and the name (and user ID) of the personwho created the report, by preserving the createdon and createdby flags found in the changepackage.

To preserve change history modifier information, include:

-preserveModifierInfo

This retains the last modification date and time for the report by preserving the lastmodbyflag found in the change package.


How to:

Access the Dashboard Change Management Utility

Export Dashboard Files

Import Dashboard Files

Dashboard Change Management enables administrators to move Dashboard Views fromone environment to another (for example, from a development environment to a testingenvironment). Dashboard Change Management enables you to selectively move individualpieces of your Dashboard (customizations, personalizations, Public/Group views, and soon) so that you can introduce incremental updates from one environment to another.

Dashboard Change Management works in conjunction with Managed Reporting ChangeManagement. You move procedures using Managed Reporting Change Management, andDashboard views using Dashboard Change Management.



All Dashboard Change Management export and import files are stored in theWebFOCUS\worp\management directory.

How to Access the Dashboard Change Management UtilityProcedure:

You must be an administrator to access the Dashboard Change Management utility. Alsonote that the Change Management Utility is a single-user system and shares logon informationwith the Dashboard View Builder. Therefore, if someone is logged on the View Builder, anotheruser will not be able to run the Change Management utility on that system.

1. Access the Dashboard Change Management utility from the:

WebFOCUS Welcome page (http://server/ibi_apps/). Click Business IntelligenceDashboard Change Management in the Dashboard and Managed Reporting category.

Dashboard View Builder. Click Management.

URL http://server/ibi_apps/bid/bidcmlogin

The Login page opens.

2. Enter your user ID and password and click Logon.

How to Export Dashboard FilesProcedure:

1. In the Dashboard Change Management utility, click the Export tab.

2. Select the Automatically select Users assigned to selected View check box to automaticallyselect users assigned to any views you select for export.

3. Open each category (Public Views, Group Views, Users, Role Tree, Toolboxes, Templates)and select the check box adjacent to the files you want to export.

4. Click Export Selected. The file is named time_date.zip.

5. From the list of available WebFOCUS BID Management files, select your file and clickDownload File to save the file to a local directory.

The Save As dialog box opens.

6. Navigate to the location where you want to save the file and click Save.

Note: Both the file name and the .zip file extension should not be changed in order for theDashboard Change Management utility to recognize the file and process it correctly.

208 WebFOCUS


How to Import Dashboard FilesProcedure:

1. Log in to the Change Management utility or the Dashboard View Builder for the targetsystem.

2. In the Dashboard Change Management utility, click the Import tab.

Note: You can also use FTP to import files from one system to another. If you use thismethod, place the file to import in the WebFOCUS\worp\management directory of thetarget system. The file must be transferred in binary format.

3. If the file you want to import is not already listed in the list of available WebFOCUS BIDManagement files:

a. Click the Browse button and navigate to the file.

b. Click Upload File.

The file appears in the list of available WebFOCUS BID Management files.

4. Select the file to import from the list of available WebFOCUS BID Management files andclick Import File.

5. Select the items from the file you want to import. Select the Check to automatically selectUsers assigned to selected View check box to automatically select users assigned to anyviews you select for import.

6. Click Import Selected.

Note: Importing a large Change Management file may result in an HTTP500 error. If theerror occurs, recreate the Change Management extract file as multiple files and importeach file separately.



210 WebFOCUS


WebFOCUS

Additional Administration Topics11Topics:

These topics contain additionalinformation for administrators aboutReportCaster, debugging, setting uptraces, repository file names, andobtaining a list of Master Files.

Selecting the Tool Type forReportCaster

Debugging

Setting Up Traces for ManagedReporting User Requests

Repository File Name Processing

Obtaining a List of Available MasterFiles


Selecting the Tool Type for ReportCaster

How to:

Configure Managed Reporting Tool Types

You can configure tool types for a Managed Reporting Administrator, Developer, and AnalyticalUser. The selections include ReportCaster Scheduling Wizard and HTML User Interface orthe Java Web Start-based ReportCaster Development and Administration Interface. Thisselection is not applicable to Analytical Users as they use the ReportCaster HTML userinterfaces.

How to Configure Managed Reporting Tool TypesProcedure:

1. In the WebFOCUS Administration Console, click Utilities.

The MR Tool Type Selection options appear.

2. Select Administrator, Developer, or Analytical User.

If you select Administrator or Developer, the MR Tool Type Selection window appearswith the following defaults.

Note: The ReportCaster User Interface cannot be configured for Managed ReportingAnalytical Users, who must use the HTML-based Scheduling Wizard and User Interface.

3. To configure a Managed Reporting Administrator or Developer to use the HTML-basedScheduling Wizard and User Interface, select the HTML option button.

4. Click Save to save your changes.

If you are using the WebFOCUS Servlet, you must reload your WebFOCUS Web applicationin order for your changes to take effect. In addition, users must log out of Managed Reportingand log back in.

212 WebFOCUS

Selecting the Tool Type for ReportCaster

Debugging

In this section:

Your Browser's Java Console

Tracing the Java Applets

Tracing the WebFOCUS Client

Enabling Tracing Options in Dashboard

These topics describe how you can access debugging information and enable tracing options.

Your Browser's Java ConsoleWhen you encounter problems with Java applets in the Internet Explorer, you can receivevaluable debugging information by looking in the Internet Explorer Java Console. Access thisfrom the menu bar by clicking View and then Java Console. The Java Console (as shown inthe following image) shows you which Microsoft Java Virtual Machine release you are using.You can also see messages from the IBI Java code, such as the Managed Reporting JavaGen number. Information Builders Customer Support Service (CSS) may ask you to checkfor specific messages in this console to aid in problem determination.

If the Java Console does not appear in your View menu, you may need to activate it. Theway to activate this varies with each Internet Explorer release. In Internet Explorer version6.0, enable the Java Console by selecting Tools, Internet Options, Advanced, Microsoft VM,and Java Console enabled. You must restart your browser for the changes to take effect.


11. Additional Administration Topics

Tracing the Java Applets

How to:

Trace the Domain Builder Applet

It is possible to increase the level of trace messages written to the Internet Explorer JavaConsole. This can be helpful for debugging purposes. Before carrying out the following steps,you should back up your mr_ie.htm file in case you accidentally corrupt it.

How to Trace the Domain Builder AppletProcedure:

1. Edit webfocus76/ibi_html/workbnch/mr_ie.htm and search for the JavaScript function:

function showDomainAdmin()

2. Under this function, uncomment the following lines (remove the two slashes):

// innerHTML += "<PARAM NAME=FOCUStrace value='true'>";// innerHTML += "<PARAM NAME=PROGRAMtrace value='true'>";

3. Save the file and either log onto Managed Reporting again or click your browser's Refreshbutton (if you are already logged on). You now see detailed trace messages in your JavaConsole.

Note: While tracing is on and the Java Console is open, applet performance will bedecreased. Keep the Java Console closed until you have reproduced the steps you aredebugging in order to improve performance.

You can copy the following trace lines to other JavaScript functions in order to trace thebehavior of other applets:

showUserAdmin() - the User Administration appletshowDomains() - the Domains applet

Tracing the WebFOCUS ClientSee the WebFOCUS Security and Administration manual. To turn tracing on, set Trace=ON.

214 WebFOCUS

Debugging

Enabling Tracing Options in Dashboard

How to:

Add the TRACE_LEVEL Parameter for Windows

Add the TRACE_LEVEL Parameter for UNIX and z/OS

Remove or Modify the TRACE_LEVEL Parameter for Windows

Remove or Modify the TRACE_LEVEL Parameter for UNIX and z/OS

Turn On Dynamic Tracing in Dashboard

Reference:

Dashboard Trace File Names

Dashboard Trace File Contents

By default, the Dashboard tracing option is not turned on. Tracing should only be turned onwhen requested to do so by an Information Builders representative.

Tracing is only active when the TRACE_LEVEL parameter exists with a valid value. To turnthe Dashboard tracing option on, add the TRACE_LEVEL initialization parameter in the servletengine configuration. For details, see How to Add the TRACE_LEVEL Parameter for Windowson page 215 and How to Add the TRACE_LEVEL Parameter for UNIX and z/OS on page 216.

All trace files are created under the ibi\WebFOCUS76\worp\log directory. A trace file iscreated for every session, therefore it is possible to have many trace files generated for oneuser.

You can turn on traces dynamically by editing the bid-config.xml file. See How to Turn OnDynamic Tracing in Dashboard on page 217.

How to Add the TRACE_LEVEL Parameter for WindowsProcedure:






6. Under Initialization Parameters, add the following:

name: TRACE_LEVEL



value: FATAL, ERROR, WARN, INFO, or DEBUG. FATAL is for minimum tracing, DEBUGis for maximum tracing, and OFF turns the tracing option off.


7. Click Submit.


How to Add the TRACE_LEVEL Parameter for UNIX and z/OSProcedure:


2. Add the following immediately preceding the line </servlet>:

<init-param> <param-name>TRACE_LEVEL</param-name> <param-value>DEBUG</param-value></init-param>


How to Remove or Modify the TRACE_LEVEL Parameter for WindowsProcedure:






6. Under Initialization Parameters, delete the TRACE_LEVEL parameter, or change the valueto OFF.

7. Click Submit.


How to Remove or Modify the TRACE_LEVEL Parameter for UNIX and z/OSProcedure:


216 WebFOCUS

Debugging

2. Change the value in the TRACE_LEVEL parameter to OFF, as follows:

<init-param> <param-name>TRACE_LEVEL</param-name> <param-value>OFF</param-value></init-param>

Alternatively, you can delete the lines that were added for TRACE_LEVEL in the web.xmlfile.


How to Turn On Dynamic Tracing in DashboardProcedure:


Find the following line:

<trace-option trace-flag="false" trace-level="DEBUG"/>

2. Change the value to true.


You do not need to reload the servlet.

Dashboard Trace File NamesReference:

Trace files are named as follows:

<username>_<date>_<timestamp>.logADMIN_20010829_140159.log

where:

username

Is the name that the user logged in with, not the description in Managed Reporting.

date

Is the date in yyyymmdd format. For example, 20010829.

timestamp

Is the time using 24-hour time. For example, 24hhmmss, such as 14015959.

The log file for a user logged in as ADMIN on Aug 29th, 2001 at 2:01:59 PM would be:

ADMIN_20010829_140159.log



Dashboard Trace File ContentsReference:

Trace files contain the following information:

<thread number> <date> <time> <level> <location> <message>

where:

thread number

Is the number generated for each new task performed in the servlet

date

Is the date when the line of trace code is created. The format is MM/DD/YYYY.

time

Is the time when the particular trace code has been written to the trace file. The formatis hh:mm:ss:nnn.

level

Is the TRACE_LEVEL defined in the servlet parameters. Valid entries are FATAL, ERROR,WARN, INFO, DEBUG or OFF.

location

Is the internal location called by the Dashboard. The format is <Java class name>.<Javamethod name>.

message

Is the internal trace text.

Setting Up Traces for Managed Reporting User RequestsThe MRUSERLOG and cgi_mrreq_log traces are available for logging Managed Reporting userrequests.

MRUSRLOG determines whether a log file of user actions is created and, if so, how frequently.

The cgi_mrreq_log trace can be used to detect which applications are still making calls tothe CGI or ISAPI to run Managed Reporting requests. For complete details see TechnicalMemo 4575: WebFOCUS Managed Reporting and CGI/ISAPI Requests.

For complete details on tracing, see the WebFOCUS Security and Administration manual.

Repository File Name ProcessingThe Managed Reporting Repository supports long file names for My Reports, StandardReports, Reporting Objects, and Other files. The maximum length of a file name is 64characters followed by a dot and an extension of up to 5 additional characters.

218 WebFOCUS

Setting Up Traces for Managed Reporting User Requests

File names are created by Managed Reporting when procedures are copied into a Domainfrom Data Servers, imported from the file system, or created by a tool. The file name isbased on the report description when created by a tool, or the file name when importing aprocedure. When a file name is being created, only lowercase alphanumeric characters,underscores, and spaces are retained (all other characters are removed). Spaces areconverted to underscores, and repeating underscores are replaced by a single underscore.The result is trimmed to 64 characters and the file extension is applied.

If this file name is unique, the file is written. If the file name is not unique, a random stringcontaining alpha and numeric characters is created and added to the file name, and the filename is tested again for uniqueness. After a file name is created, it becomes the reportHREF referenced by launch pages, drill-downs, includes, and schedules.

Obtaining a List of Available Master FilesYou can obtain a list of available Master Files more quickly while you work in the ManagedReporting or Data Servers areas if you do not retrieve information based on the REMARKSattribute that is stored within the Master File.

By default, Developer Studio opens and parses all available Master Files and determines ifthe REMARKS attribute is available in order to display information in the Table List dialogbox. You can change this behavior and decrease the time required to display the list ofavailable tables because each table will not be opened and parsed for available remarks.

If you do not want Developer Studio to check for the REMARKS attribute, modify theibiapplets.txt file, typically located in the following directory:

install_drive:\IBI\WebFOCUS76\ibi_html\javaassist

In the ibiapplets.txt file, change the following text from

TABLE FILE SYSTABLEPRINT REMARKS AS 'BY NAME AS ''

to:

TABLE FILE SYSTABLE-*PRINT REMARKS AS ''-*BY NAME AS ''PRINT NAME AS ''



220 WebFOCUS

Obtaining a List of Available Master Files

WebFOCUS

Application Integration Topics12Topics:

This topic describes applicationintegration topics.

Invoking the Deferred Report StatusInterface Directly

Managed Reporting Browser WindowFeature

Using Launch Pages Outside theDefault Repository


Invoking the Deferred Report Status Interface DirectlyYou can invoke the Deferred Report Status Interface directly using an HTML page that callsthe WebFOCUS Client. Note that Deferred Receipt is a Managed Reporting feature.

Deferred Receipt functionality leverages the WebFOCUS and Managed Reporting securityand repository for storage and access to deferred output. The following guidelines shouldbe followed:

Valid Managed Reporting and WebFOCUS Signon must be done before invoking theDeferred Status Interface.

The Deferred Status Interface Save option displays for all Managed Reporting users whoare assigned the Administrator, Developer, or Analytical User role and have the privilegeto create and save My Reports.

Invoking the Deferred Report Status InterfaceExample:

The following HTML page calls the WebFOCUS Client (configured with Servlet) and places a"Deferred Status" button on the page that when clicked, invokes the Deferred StatusInterface.

<html><! --HTML to call Deferred Status interface --><title>Deferred Status </title><BODY BGCOLOR="White"LEFTMARGIN=0 TOPMARGIN=0><TABLE<TR><TD><FONT FACE="Arial,Helvetica,sans-serif" SIZE="2"><A HREF=/ibi_apps/WFServlet?IBIMR_action=MR_DEFER&IBIMR_return=html&IBIMR_sub_action=MR_DEFER_CONTROL&>Deferred Status </A></TD></TR></TABLE></body></html>

222 WebFOCUS

Invoking the Deferred Report Status Interface Directly

Managed Reporting Browser Window Feature

In this section:

WebFOCUS Managed Reporting Implementation

Site Customization

Browser Window Options

Browser Window Exceptions

Customizing the Amper Auto-Prompting Facility

You can utilize all available JavaScript options for controlling the way a browser windowlooks. This allows you to customize Web browser windows so that they conform to theirapplication and organizational standards.

This feature does not change the default appearance or functionality of WebFOCUS ManagedReporting. It specifically enables you to control the browser window look and options.

Note: This feature is only available when using an Internet Explorer browser.

WebFOCUS Managed Reporting Implementation

Reference:

JavaScript Code

You can control the way a browser window looks in Managed Reporting with the addition ofJavaScript code to the following:

Managed Reporting logon page—mr_ie.htm is located under /ibi_html/workbnch/ onthe server where WebFOCUS is installed.

Note: This technique applies to the HTM Managed Reporting logon pages. The JSPManaged Reporting logon pages dynamically create the Managed Reporting logon pageso this technique is not available if you are using the JSP Managed Reporting logonpages.

OLAP Control Panel file—drill.html is located under /ibi_html/javaassist on the serverwhere WebFOCUS is installed.

Deferred Report Status Interface—xxmrchft.def is located underdrive:\ibi\WebFOCUS76\client76\conf\etc on the server where the WebFOCUS Clientis installed. Note that xx is the 2 letter abbreviation for the language you select whenyou log on to Managed Reporting.


12. Application Integration Topics

JavaScript CodeReference:

The following JavaScript code, located in the heading of the HTML logon pages for ManagedReporting and the OLAP Control Panel file, launches the default browser window look andoptions.

<SCRIPT LANGUAGE=JAVASCRIPT>function doShowDoc(u,t){t=t.replace(' ','A');window.open(u,t);}</SCRIPT>

where:

u

Is the URL where the HTML for the browser window is located.

t

Is the new browser window name.

Caution: These parameters are set internally by WebFOCUS and must not be changed.

Site Customization

How to:

Control a Browser Window in the Deferred Report Status Interface

To customize the look of a window created by WebFOCUS Managed Reporting, you mustmake manual changes to the JavaScript code and migrate them to any future version ofWebFOCUS.

To customize the browser window, determine the desired browser window options (for moreinformation, see Browser Window Options on page 226) and JavaScript code additions, andadd them after the last parameter in the JavaScript window.open call.

224 WebFOCUS


Customizing a Browser WindowExample:

If you want to suppress all browser controls, including the location bar (address or URL),the JavaScript code presented in JavaScript Code on page 224 must be changed as follows:

window.open(u,t);

to

window.open(u,t,"location=0");

The following image shows the browser window without controls such as location bars,toolbars, and scrollbars.

If you want to suppress the location bar and status bar but display the scroll bars, you mustchange the JavaScript code presented in JavaScript Code on page 224 as follows:

window.open(u,t);

to

window.open(u,t,"location=0,status=0,scrollbars=1");



How to Control a Browser Window in the Deferred Report Status InterfaceProcedure:

1. Make a backup or copy of xxmrchft.def, located indrive:\ibi\WebFOCUS76\client76\conf\etc.

Where xx is the 2 letter abbreviation for the language you select when you log on toManaged Reporting.

2. Edit xxmrchft.def, located in drive:\ibi\WebFOCUS76\client76\conf\etc.

3. Search for the following string:

window.open

4. Add the browser option ("location=0") to the window.open options before the last closingparenthesis. For example, change:

nl,text,window.open(fixurl(aa),name);

to

nl,text,window.open(fixurl(aa),name,"location=0");

Note:

There are several instances of window.open. Apply this change to each instance.

The xxmrchft.def file is a WebFOCUS internal script file. Each line or continuation ofa line must begin with the text “nl,text”.

5. Clear the browser cache prior to testing.

Browser Window OptionsYou can modify the following browser window options:

Menu bar

Toolbar

Location bar

Directories bar

Status line

Scroll bars

Ability to resize the window

Closing a child window when a parent window closes

Width (in pixels)

226 WebFOCUS


Height (in pixels)

Screen alignment (from the left of the screen, from the top of the screen)

When using JavaScript, you must specify all the options you want in your Managed Reportingbrowser window. Once an option is specified, there are no default values assumed.

Caution: The first two parameters (u and t) in the window.open call are set internally byWebFOCUS and must not be changed.

Setting Browser Window OptionsExample:

The following example shows how to open a new window, called open_window, in the upperleft corner of the window that displays the front page of Managed Reporting. The size of thenew window will be 640x480 pixels. To accomplish this, include the following HTML codein the head of the original document:

<SCRIPT LANGUAGE=JAVASCRIPT>function doShowDoc(u,t){t=t.replace(' ','A');window.open(u,t,menubar,toolbar,location,directories,status,scrollbars,resizable,dependent,width=640,height=480,left=0,top=0);}</SCRIPT>

Browser Window ExceptionsWebFOCUS Managed Reporting does not create a new browser window when you:

Right-click a drill-down link in a WebFOCUS report and select Open.

Use the Ctrl+N sequence to create a new browser instance.

Access the following administrator tools from Managed Reporting:

The ReportCaster Console. When you run a log report from the Console, the browseroptions cannot be controlled, since the applet does not create the browser window.

Two-Way Email. When you run the Job Log or Event Log from the Managed ReportingTwo-Way Email option on the blue toolbar, the browser options cannot be controlled,since the applet does not create the browser window.

Customizing the Amper Auto-Prompting FacilityYou can customize the look and feel of the amper auto-prompting facility by editing thelaunch page template file you are using. All of the available launch page templates arelocated in the ibi\WebFOCUS76\ibi_html\javaassist\ibi\html\describe directory. The defaulttemplate is autoprompt_top.css.



If you want to customize the banner, create an image, save it in the describe directory, andchange the background-image property, which is shown in bold type in the following CascadingStyle Sheet (CSS) code:

#idBannerDiv {height:45px;background-image: url(logo_banner.gif);background-position: top left;background-repeat: no-repeat; margin: 0;margin-top:2px;cursor:hand;}

The option to select different launch page templates can be set in the WebFOCUSAdministration Console using the Parameter Prompting selection under Client Settings, whereyou can set the IBIF_describe_xsl value to one of the launch page templates.

You can also enter the name of the desired launch page template in a FOCEXEC using thefollowing code:

<describe_xsl>template</describe_xsl>

where:

template

Is set to one of the following launch page template values:

autoprompt_top - Displays the parameters horizontally at the top of the page and isthe default template value.

autoprompt_top_checked - Same as autoprompt_top, but the Run in a new windowcheck box is pre-selected.

autoprompt - Displays the parameters vertically at the left side of the page.

autoprompt_checked - Same as autoprompt, but the Run in a new window check boxis pre-selected.

autoprompt_simple - Basic input form.

Using Launch Pages Outside the Default RepositoryMost sites will only use the Managed Reporting Repository directory, basedir, created bythe installation program, which is found under install_dir/WebFOCUS76. This repository isreferred to as the default repository because it is referenced by the variable MR_BASE_DIRin the WebFOCUS script file named install_dir/WebFOCUS76/client76/wfc/etc/cgivars.wfs.If you modify your Managed Reporting signon page to include the MR_BASE_DIR variable forthe purpose of overriding this setting, your launch pages will generate an error because theyassume that the Standard Report will be found in the default repository.

228 WebFOCUS

Using Launch Pages Outside the Default Repository

You can make these launch pages work by adding the MR_BASE_DIR variable to your launchpages as shown in the following example:

<INPUT TYPE="HIDDEN" NAME="MR_BASE_DIR"VALUE="e:\ibi\WebFOCUS76\basedir_alt">

For more information on customizing signon pages, see Customizing the User Interface inWorking with Localized Versions in the National Language Support for International Computingmanual.



230 WebFOCUS

Using Launch Pages Outside the Default Repository

WebFOCUS

Two-Way Email Administration13Topics:

As a Managed Reporting Administratorand ReportCaster Administrator, you usethe Two-Way Email Administrator consoleto manage subscriber information,monitor the execution of report requests,cancel requests, and perform otheradministrative tasks.

Accessing the Administrator Console

Adding or Deleting a Subscriber

Maintaining an E-mail Address

Refreshing a User's TemplatesFor information on developing Two-WayEmail templates, see the WebFOCUSManaged Reporting Developer's Manual.

Using the Job Log

Using the Event Log

Checking the Status of a Job orCanceling a Job



How to:

Access the Console and View Current Subscribers

The Two-Way Email Administrator console enables the Managed Reporting Administrator toperform the following:

View Managed Reporting users currently subscribed to Two-Way Email and their e-mailaddresses.

Add a new subscriber or delete an existing one.

Maintain a user's e-mail address.

Re-send all templates to a user. This feature is called refreshing the templates.

View the status of an executed job using the Job Log and purge the Job Log.

Monitor e-mail traffic using the Event Log and purge the Event Log.

Check the status of an executing job or a queued job (one that is waiting to be sent tothe WebFOCUS Reporting Server for execution). You can also cancel a queued job.

How to Access the Console and View Current SubscribersProcedure:

In the Managed Reporting browser's blue toolbar, click Two-Way Email. In the Developer

Studio Explorer, click the Two-Way Email Administrator button in the toolbar.

232 WebFOCUS


The Two-Way Email Administrator console opens in a scrollable window as shown in thefollowing image.

The console displays the following:

All Managed Reporting users currently subscribed to Two-Way Email, listed on the leftunder Two-Way Email subscribers.

All e-mail addresses for a selected user, listed on the right under Addresses for subscriber.

You can only select one user at a time from the left-hand list. However, you can select morethan one address from the right-hand list when you are deleting multiple addresses orselecting addresses for a refresh task.


How to:

Add a New Subscriber

Delete an Existing Subscriber

Use the Administrator console to add a new subscriber to the Two-Way Email database ordelete an existing subscriber from the database.

When a Managed Reporting Administrator adds a new subscriber using the Two-Way EmailAdministrator console, the subscriber receives a confirmation message from Two-Way Email,acknowledging the subscription request. The user must reply to the message. The subscriptionis activated once the confirmation process is complete.


13. Two-Way Email Administration

How to Add a New SubscriberProcedure:

1. Select Two-Way Email on the Managed Reporting browser's blue toolbar to access theTwo-Way Email Administrator console. In the Developer Studio Explorer, click the Two-Way

Email Administrator button in the toolbar.

2. Click Add user. The Add Two-Way Email Subscriber window opens as shown in thefollowing image.

3. Enter the Managed Reporting user ID and password.

4. Enter the WebFOCUS Reporting Server user ID and password. To use default valuesspecified in the Two-Way tab in the ReportCaster Server Configuration Tool, click Usedefault credentials.

5. Enter the user's e-mail address in the field under Two-Way Email Subscription. Click Addand Two-Way Email will list the new user under Two-Way Email subscribers.

If the user already has a Two-Way Email account, you receive a message informing youthat the subscription procedure failed for that reason.

If you make a typing error on the window, click Reset to clear the fields and start over.

234 WebFOCUS


How to Delete an Existing SubscriberProcedure:



2. Select the name of the subscriber you want to delete from the list on the left, underTwo-Way Email subscribers.

Click Delete user. A window opens, with the name of the selected subscriber.

3. Click Delete to remove the subscriber from the Two-Way Email database.

Maintaining an E-mail Address

How to:

Add a New E-mail Address

Delete an Existing E-mail Address

For any Two-Way Email user, you can:

Add a new e-mail address to the Two-Way Email database.

Delete an existing e-mail address from the Two-Way Email database. You can deletemultiple addresses at one time.

When you add a new e-mail address, the user receives a confirmation message at the newaddress from Two-Way Email and must reply to it. The new address is activated once theconfirmation process is complete.

How to Add a New E-mail AddressProcedure:



2. Using the console, select the user from the list on the left, under Two-Way Emailsubscribers.

3. Click Add Email.

4. On the next dialog box, type the new e-mail address in the field. Click Add.



How to Delete an Existing E-mail AddressProcedure:




3. Select the address, or addresses, you want to remove from the list on the right, underAddresses for subscriber.

4. Click Delete Email.

5. On the next dialog box, click Delete.

If you delete the only e-mail address associated with a user, the user's subscription toTwo-Way Email (that is, the user's account) is cancelled. You have an opportunity toproceed with that action or discontinue the procedure.

Refreshing a User's Templates

How to:

Refresh a User's Templates

You can re-send a user's templates to a single e-mail address or to multiple addresses forthat user.

How to Refresh a User's TemplatesProcedure:




3. Select the address, or addresses, that the templates will be sent to using the list onthe right, under Addresses for subscriber.

4. Click Refresh Templates.

5. Click OK to re-send the templates the subscriber is authorized to use.

236 WebFOCUS

Refreshing a User's Templates

Using the Job Log

In this section:

Viewing the Status of an Executed Job

Purging the Job Log

Use the Job Log to view information about a job (Standard Report procedure) sent to theWebFOCUS Reporting Server for execution.

The Job Log is an HTML page that opens in a browser window.

Viewing the Status of an Executed Job

How to:

View the Status of an Executed Job

The Job Log displays information about the activities that occurred during the execution anddistribution of a report. It enables you to confirm that a report was executed and distributedsuccessfully. If a job does not conclude as expected, the Job Log states the reason why.

The following image is a sample entry from a Job Log.

It includes the following:

Two-Way Email Job Description. The name of the template associated with the job.

Server User. The WebFOCUS Reporting Server user ID.

Managed Reporting User. The Managed Reporting user ID.

Process. A unique, system-generated key that identifies a specific execution of thetemplate.



Job Name. The name of the Managed Reporting Standard Report procedure, precededby app and the delimiter /.

Start Time. The date and time the job started running.

End Time. The date and time the job finished running.

Messages. Details on the activities that took place during job execution and distribution.

How to View the Status of an Executed JobProcedure:



2. Click the Job Log button on the left to display the Job Log Report information as shownin the following image.

238 WebFOCUS

Using the Job Log

3. Apply selection criteria to define the information that will be retrieved:

Use the drop-down lists for Start Date and Start Time to specify the beginning of thetime frame. Information on all jobs run from that date and time up to the current dateand time will be retrieved.

Enter the name of a specific Two-Way Email template in the Job Description field.Information only for the jobs associated with that template during the specified timeframe will be retrieved.

Select Yes for Last Executed. Information only for the most recently executed jobassociated with the template (Job Description) during the specified time frame willbe retrieved.

4. Click Click to View to display the Job Log report.

Purging the Job Log

How to:

Purge the Job Log

Because the Job Log accumulates information and can become difficult to navigate, it is agood idea to periodically purge it to conserve space.

You can control automatic purging of the Job Log at predefined intervals of time. Edit theparameter LOG_PURGE_PERIOD in the schedule section of the Distribution Server'sbkrsched.cfg file.

For example, to automatically purge Job Log reports every two days, enter:

LOG_PURGE_PERIOD 2

This parameter applies to the Two-Way Email Job Log and the ReportCaster Job Log. Formore information, see the ReportCaster Development and Administration manual.

How to Purge the Job LogProcedure:

1. Select Two-Way Email on the Managed Reporting blue toolbar to access the Two-WayEmail Administrator console. In the Developer Studio Explorer, click the Two-Way Email

Administrator button in the toolbar.



2. Click the Job Log button on the left to display the Job Log Report information as shownin the following image.

3. Using the drop-down lists for Ending Date, specify a date through which the Job Log willbe purged.

4. Click Click to Purge. Respond to the confirmation message on the next dialog box.Two-Way Email will delete all reports from the beginning of the Job Log through thespecified ending date.

Using the Event Log

In this section:

Monitoring E-mail Traffic

Purging the Event Log

Use the Event Log to monitor the status of a Two-Way Email request as it is received,assessed for security, sent to the WebFOCUS Reporting Server for execution, and distributedas a report.

The Event Log is an HTML page that opens in a browser window.

240 WebFOCUS

Using the Event Log

You can customize the content of the Event Log. Edit the parameter EVENTLOG in the Two-Way Email tab window of the Distribution Server's file as shown in the following image.

The descriptions for each setting are outlined in the following table.

DescriptionSetting

Turns off the Event Log. Nothing is displayed.OFF

Displays only errors.ERROR

Displays all events.ON



Monitoring E-mail Traffic

How to:

Monitor E-mail Traffic

The following image shows sample entries from an Event Log that displays only errors.

Each entry includes the following:

Time. The date and time the event occurred.

Server User. The WebFOCUS Reporting Server user ID.

Managed Reporting User. The Managed Reporting user ID.

Email Address. The user's e-mail address.

Message. Description of the error that occurred.

How to Monitor E-mail TrafficProcedure:



242 WebFOCUS

Using the Event Log

2. Click the Event Log tag on the left to display the Event Log Report information as shownin the following image.

3. Apply selection criteria to define the information that will be retrieved:

Use the drop-down lists for Start Date to specify the beginning of the time frame thatyou are interested in. Information on all events that occurred from that date up tothe current date will be retrieved.

Enter an Managed Reporting user ID in the Managed Reporting User field. Informationonly for the events associated with that user ID during the specified time frame willbe retrieved.

Enter a WebFOCUS Reporting Server user ID in the WebFOCUS User field. Informationonly for the events associated with the supplied Managed Reporting user ID andWebFOCUS Reporting Server user ID during the specified time frame will be retrieved.

Enter an e-mail address in the Email Address field. Information only for the eventsassociated with the supplied IDs and address during the specified time frame willbe retrieved.

4. Click Click to View to display the Event Log report.



Purging the Event Log

How to:

Purge the Event Log

Because the Event Log accumulates information and can become difficult to navigate, it isa good idea to periodically purge it to conserve space.

How to Purge the Event LogProcedure:



2. Click the Event Log tag on the left to display the Event Log Report information as shownin the following image.

3. Using the drop-down lists for Ending Date, specify a date through which the Event Logwill be purged.

4. Click Click to Purge. Respond to the confirmation message on the next dialog box.Two-Way Email will delete all reports from the beginning of the Event Log through thespecified ending date.

244 WebFOCUS

Using the Event Log

Checking the Status of a Job or Canceling a Job

How to:

Check the Status of a Job

Cancel a Queued Job

You can check the status of an executing job or one that is waiting to be sent to theWebFOCUS Reporting Server for execution (a queued job). You can also cancel a queuedjob.

How to Check the Status of a JobProcedure:



2. Click the Job Status button on the left to display a scrollable window as shown in thefollowing image.

Jobs currently running on the WebFOCUS Reporting Server are displayed at the top ofthe window, under Running Jobs.

Jobs waiting to be sent to the WebFOCUS Reporting Server for execution are displayednear the bottom of the window, under Queued Jobs.



The following information identifies a job:

Job Number. The unique, system-generated key for a specific execution of a report.

Started On (under Running Jobs). The date and time the job started running onthe WebFOCUS Reporting Server.

Submitted (under Queued Jobs). The date and time the job was submitted to theWebFOCUS Reporting Server for execution.

Two-Way Fex. The name of the procedure for the Managed Reporting StandardReport.

Originator. The e-mail address from which the request originated.

3. The option Refresh this window every n seconds is checked by default, retrieving thelatest information after the specified interval of time. You can accept the default intervalof 10, as shown in the following image, or supply the interval in seconds. Click Refreshto immediately retrieve the latest information.

How to Cancel a Queued JobProcedure:



2. Click the Job Status button on the left.

3. Select one or more jobs from the list under Queued Jobs. Click Delete to cancel execution.

246 WebFOCUS

Checking the Status of a Job or Canceling a Job

WebFOCUS

Managing Deferred Tickets14Topics:

The topics in this chapter containinformation to help Managed ReportingAdministrators manage deferredworkload and the Deferred TicketCleanup Utility.

Managing Deferred Workload

Managing the Deferred Ticket CleanupUtility



In this section:

Understanding Alternate Deferred Servers

Configuring Deferred Services

Deferred Report Expiration Setting

Reading Saved Deferred Output Created by WebFOCUS CGI/ISAPI Client

You can connect from a single WebFOCUS Client installation to multiple WebFOCUS ReportingServers. This means that it is possible for a single user to have deferred tickets for outputresiding on multiple servers. Moreover, these servers can be on different platforms and mayrequire different user IDs. Users have access to all deferred output, regardless of location,and are prompted for credentials automatically as needed.

There are administrator settings for managing deferred workload. There can be up to onealternate deferred server per immediate server to separate interactive and deferredprocessing. You can limit the number of server agents allocated to handling deferred requestsand the number of deferred requests a given user can process at one time (these featuresare not available on OS/390 MVS). On OS/390 MVS, the UNIQUE global keyword restrictssimultaneous server connections to one per logon ID, which can be used to manage bothdeferred and interactive workload when server authentication is used.

Understanding Alternate Deferred ServersYou can configure an alternate deferred server for one or more of your interactive servers.This causes deferred requests to run against a specific server and be routed to anotherserver for processing. For example, if you are building a report in a domain that has a serverset to HPUXPROD, as shown in the following image, and you do not change this setting.

248 WebFOCUS


The report will run against HPUXPROD, but will run deferred against HPPRODDF because ofthe relationship configured in the WebFOCUS Administration Console, as shown in thefollowing image.

Configuring alternate deferred servers is one way to manage deferred workload. Typically,the alternate deferred server is given fewer processing resources since users are not waitinginteractively for the request to finish. This allows the interactive servers to have relativelymore processing resources.

If you do not have access to the WebFOCUS Administration Console, contact your WebFOCUSAdministrator or see the WebFOCUS Security and Administration manual.

Configuring Deferred ServicesYou can also manage the resources allocated to processing deferred requests withoutconfiguring additional servers. The WebFOCUS Server Web Console for a specific serverallows you to configure workload settings for deferred requests independently of interactiverequests.


14. Managing Deferred Tickets

As an example shown in the following image, you can set the max_connections_per_userto 1 for the Deferred Service while allowing users to submit unlimited concurrent interactiverequests.

If you do not have access to the WebFOCUS Server Web Console, contact your WebFOCUSServer Administrator or see the Server Administration for UNIX, Windows, OpenVMS, i5/OS,and z/OS manual.

Deferred Report Expiration Setting

How to:

Control Purging of Deferred Output

The WebFOCUS Reporting Server has an output expiration setting that controls when deferredoutput is purged from the WebFOCUS Reporting Server. This setting is made in the serverconfiguration file (Windows and UNIX) and the deferred receipt listener node block (on z/OS).

250 WebFOCUS


How to Control Purging of Deferred OutputSyntax:

dfm_maxage={0|n}

where:

0

Indicates no expiration is configured.

n

Indicates n days until expiration.

No setting means that the default of 30 days will be in effect.

The number of days until expiration are displayed next to each report. On the last day, thevalue Today is displayed.

Note: Cleanup of deferred output stored on the WebFOCUS Reporting Server is facilitatedby the Deferred Management listener, which checks every time it wakes up. The listener'ssleep interval is defined by the dfm_int_max parameter which defaults to 30 seconds if notspecified. For more information about this and related parameters, click Deferred, followedby Keyword Reference under the WebFOCUS Reporting Server's Web Console Help link.

If a deferred report is not saved or deleted prior to its expiration, the output is automaticallydeleted from the WebFOCUS Reporting Server's dfm_dir directory and the deferred report ismoved to the Unknown category in the Deferred Report Status Interface. From here, the usercan only delete the orphaned report. For more information about cleaning up orphaneddeferred tickets, see Managing the Deferred Ticket Cleanup Utility on page 252.

Reading Saved Deferred Output Created by WebFOCUS CGI/ISAPI ClientIn previous releases, when WebFOCUS was configured to use the CGI/ISAPI client, deferredoutput saved to a user's My Reports folder in the Managed Reporting Repository was writtenin a format that was incompatible with the WebFOCUS Servlet (WFServlet). This meant thatif you upgraded to WebFOCUS Version 7 Release 1, which required the WFServlet configurationfor Managed Reporting, you could not access your saved deferred output. The WFServletnow detects and reads the legacy output format, while continuing to read and write with thenewer format.

The WF_CGI_ENDIANNESS setting is located in the Managed Reporting section of theConfiguration menu of the WebFOCUS Administration Console. This setting is used byWFServlet to determine the byte order of the deferred output. If your legacy saved deferredoutput was created on a platform with a little-endian byte order, such as Intel x86, you shouldkeep the default setting of LITTLE. If the output was created on a big-endian platform suchas IBM S/390, z/Series, and some UNIX and Linux systems, you should change the settingto BIG. Some platforms can be configured either way so consult with your administrator orexperiment if you are unsure of the proper setting for your environment.



Because WFServlet runs on Java™ technology, which is always big-endian, new deferredoutput will always be written in big-endian format. WF_CGI_ENDIANNESS is therefore usedby WFServlet only to know which way to read legacy saved deferred output created by theWebFOCUS CGI/ISAPI Client.

Managing the Deferred Ticket Cleanup Utility

In this section:

Deferred Ticket Cleanup Utility Processing

MR Repository and User Credentials

WebFOCUS Reporting Server and User Credentials

Log File and Backup of User HTM File

Running the MR Deferred Ticket Cleanup Utility

Processing Multiple MR Repositories in Silent Mode

Troubleshooting

The Managed Reporting (MR) Deferred Ticket Cleanup Utility (mrdtcleanup) enables a ManagedReporting Administrator to clean up (delete) deferred tickets across all MR users that donot have corresponding report output on the WebFOCUS Reporting Server to which thedeferred request was submitted. Running this utility cleans up the deferred tickets (withinthe specified Managed Reporting Repository) for deferred report output deleted by theWebFOCUS Reporting Server as specified by the dfm_maxage deferred managementparameter. The dfm_maxage parameter defines the maximum number of days that deferredreports are kept on the WebFOCUS Reporting Server after they are created.

Additionally, deferred requests submitted to WebFOCUS Reporting Servers that are notdefined in the WebFOCUS Client configuration file (odin.cfg) are also deleted. Before runningthis utility, it is important to confirm that there have not been any WebFOCUS ReportingServer nodes temporarily removed from the WebFOCUS Client's odin.cfg file.

The Deferred Ticket Cleanup Utility (mrdtcleanup) is located in the /ibi/WebFOCUS76/utilitydirectory. On Windows, there is a mrdtcleanup.bat file and on UNIX-based platforms thereis a mrdtcleanup script file. You can run the Deferred Ticket Cleanup Utility in interactivemode, silent mode, or help mode. Silent mode is useful for overnight batch processing. Forinformation on running the utility in all modes, see Running the MR Deferred Ticket CleanupUtility on page 259.

252 WebFOCUS


Deferred Ticket Cleanup Utility ProcessingThe Deferred Ticket Cleanup Utility processes the information within a Managed ReportingRepository. Multiple MR repositories can be processed, but each MR Repository is processedindividually. All active and inactive MR users' deferred tickets within the specified ManagedReporting Repository are processed.

Each MR user's deferred reports are processed individually, making a single connection toeach WebFOCUS Reporting Server to which the user has submitted deferred tickets. If theWebFOCUS Reporting Server is not defined in the WebFOCUS Client Configuration file(odin.cfg), the deferred tickets submitted to that node are deleted from the Managed ReportingRepository because the WebFOCUS Client cannot make a connection to that server to processthe user's deferred tickets.

When a successful connection is made to the WebFOCUS Reporting Server, it returns statusinformation for each of the user's deferred tickets submitted to that server. The WebFOCUSClient processes the status information to confirm the existence of deferred report output.Deferred tickets, for which report output does not exist, are deleted from the ManagedReporting Repository.

If the WebFOCUS Reporting Server is defined in the WebFOCUS Client Configuration file(odin.cfg), but the WebFOCUS Client cannot establish a connection, the user's deferredtickets for that WebFOCUS Reporting Server are not deleted. Deferred tickets are only deletedupon confirmation that deferred report output does not exist.

Each time the Deferred Ticket Cleanup Utility runs, a log file and a backup of each MR user'sHTML file are created. For information on the log file and backup files the Deferred TicketCleanup utility creates, see Log File and Backup of User HTM File on page 256.

MR Repository and User CredentialsThe Deferred Ticket Cleanup Utility processes the default MR Repository in the WebFOCUSClient configuration (MR_BASE_DIR). When running in interactive mode, the utility promptsyou for the location of the MR Repository so you can specify a different MR Repositorylocation.

When running in silent mode, edit the mrdtcleanup utility file in the WebFOCUS Client /utilitiesdirectory and set the REPOS variable to the fully qualified path of the MR Repository to beprocessed. If you want to process multiple MR repositories in silent mode, make a copy ofthe mrdtcleanup utility file for each MR Repository you want to process, and set the REPOSvariable in each to the MR Repository to be processed. For information on how to create autility file to process multiple MR repositories when running in silent mode, see ProcessingMultiple MR Repositories in Silent Mode on page 269.



The user running the Deferred Ticket Cleanup Utility must be a Managed ReportingAdministrator. When running in interactive mode, the utility prompts for MR credentials.When running in silent mode, the MR credentials must be passed as parameters to theutility. For more information, see Running the MR Deferred Ticket Cleanup Utility on page 259.

WebFOCUS Reporting Server and User Credentials

How to:

Specify Server Credentials in Site.wfs

Reference:

Validation of Server Credentials in Silent Mode

WebFOCUS Reporting Server Processing

Trusted Reporting Server Connection Restriction

One or more WebFOCUS Reporting Servers and user credentials can be optionally specifiedin the site.wfs file for running in interactive mode, and these are required in site.wfs forrunning in silent mode. You can edit the site.wfs settings in the WebFOCUS AdministrationConsole from the Custom Settings panel under the Configuration menu. There is an optionin the console to encrypt the site.wfs file, which is recommended to secure the usercredentials.

How to Specify Server Credentials in Site.wfsSyntax:

Edit the site.wfs file using the following syntax:

<ifdef> IBIMR_dtcleanupWF_CCREDENTIALS=node1:id1:pwd1|node2:id2:pwd2|...<endif>

where:

node1

Is a WebFOCUS Reporting Server node name (NODE) that must be defined in theWebFOCUS Client's odin.cfg configuration file (/ibi/WebFOCUS76/client76/etc/odin.cfg).This file is accessible in the WebFOCUS Administration Console from the Remote Servicespanel under the Reporting Servers menu.

You can use an asterisk (*) for the node name if you want to specify the same user IDand password for all server nodes. This is useful if there are servers in a cluster. Youcan also use a combination of * and specific node names for some WebFOCUS ReportingServers.

254 WebFOCUS


id1

Specifies the WebFOCUS Reporting Server user ID for the first server node specified.

pwd1

Specifies the password for the WebFOCUS Reporting Server user ID.

The Deferred Ticket Cleanup Utility reads the odin.cfg file to obtain the WebFOCUS ReportingServer node connection information. In interactive mode, the user may specify a differentWebFOCUS Reporting Server user ID and password and additional WebFOCUS ReportingServer node names and credentials than those specified in the site.wfs file. In silent mode,the WebFOCUS Client automatically attempts to log on to the WebFOCUS Reporting Serverswithout prompting for credentials.

Validation of Server Credentials in Silent ModeReference:

Validation of WebFOCUS Reporting Server credentials is not performed when a user specifiescredentials initially. This is because the WebFOCUS Reporting Servers to which the deferredtickets were submitted are not determined until the utility processes MR user deferred reportinformation. Additionally, there may be WebFOCUS Reporting Servers running that are notin secure mode, making credentials unnecessary for establishing a connection. Not performingvalidation when the utility begins processing eliminates the unnecessary overhead ofconnecting to servers to which no MR users have submitted deferred requests.

WebFOCUS Reporting Server ProcessingReference:

Each MR user's HTM file is separately processed to obtain deferred ticket information. Thenumber of times a connection is made to a WebFOCUS Reporting Server depends on thenumber of MR users that have deferred tickets for that server. Only one connection is madeper user for the processing of deferred tickets for each server.

Trusted Reporting Server Connection RestrictionReference:

Because the Deferred Ticket Cleanup Utility is a standalone program, you cannot run theutility in an environment that uses a Trusted connection to the Reporting Server. As astandalone program, the Deferred Ticket Cleanup Utility is unable to retrieve credentials toconnect to the Reporting Server. If you must cleanup deferred tickets with a Trusted ReportingServer connection, use the Deferred Status Interface. For more information, see the Usingthe Deferred Report Status Interface chapter in the WebFOCUS Managed Reporting End User'sManual.



Log File and Backup of User HTM File

Reference:

Log File

Backup of MR User HTM File

Each time the Deferred Ticket Cleanup Utility runs, the WebFOCUS Client creates a log fileand a backup of each MR user HTM file.

Log FileReference:

The log file contains processing details such as timestamp information at the beginning ofeach file. All information appears, and if MR user credentials are written to the file, thepassword is masked for security reasons. The file name of the log file is in the followingform:

mrdtcleanup_date_time.log

where:

date

Is the date the log file was created in Year Month Day (YYYY-MM-DD) format.

time

Is the time the log file was created in Hour Minute Second (HMS) format.

256 WebFOCUS


Log files are created in the drive:\ibi\WebFOCUS\logs directory and can be viewed by clickingthe MR Deferred Ticket Cleanup Utility option on the Traces menu under the Diagnosticssection of the WebFOCUS Administration Console, as shown in the following image.

To view information for a log file, click the link with the desired date and time that has a .logfile extension listed in the right pane of the console. To delete a log file, select the checkbox next to the file and click the Delete button at the bottom of the console. You can alsouse the Select All and Deselect All options as needed, or click the Refresh option to ensurethat the latest information appears in the console.

For an example of a log file created in interactive mode, see Sample Log File Created inInteractive Mode on page 258.



Sample Log File Created in Interactive ModeExample:

:================================================================1: user log opened Wed Mar 29 13:43:32 EST 20062:===============================================================3:createWFLog(WFContext.java:1712):Starting WebFOCUS log-file for mrdrdelMRDTCleanup : 1 argument(s) has been received :-cd:\ibi\webfocus76\webapps\webfocus76\WEB-INF4:main(MRDTCleanup.java:104):The Utility to delete Unknown DeferredReport Tickets has started...5:isSilentMode(MRDTCleanup.java:174):as there was no option "-s" passedchecking if silent mode is set in site.wfs file.6:isSilentMode(MRDTCleanup.java:176):MRDT_AUTODELETE is set to : null7:main(MRDTCleanup.java:116):Utility is running in interactive mode8:runInInteractiveMode(MRDTCleanup.java:367):MR Default Repository willbe processed9:runInInteractiveMode(MRDTCleanup.java:378):Authenticating MR useragainst specified Repository.10:runInInteractiveMode(MRDTCleanup.java:381):authenticating MR User:admin11:runInInteractiveMode(MRDTCleanup.java:382):for MR Repository :12:checkWFCCredentials(MRDTCleanup.java:487):Checking WF credentialsinformation...13:checkWFCCredentials(MRDTCleanup.java:501):No WF Server credentialsspecified in site.wfs WF configuration file.14:checkWFCCredentials(MRDTCleanup.java:502):The Utility will prompt forthe credentials to be provided by user15:deleteUnknownDeferTickets(WFMRRepository.java:2055):Processing of MR repository D:/ibi/WebFOCUS76/basedir starting.16:deleteUnknownDeferTickets(WFMRRepository.java:2067):Getting a list ofusers on the repository17:deleteUnknownDeferTickets(WFMRRepository.java:2078):Processingdeferred tickets for admin18:deleteUnknownDeferTickets(WFMRRepository.java:2090):Creating a backupof user's html file admin.htm19:deleteUnknownDeferTickets(WFMRRepository.java:2114):user's html fileexists, - copying it to D:/ibi/WebFOCUS76/basedir\admin_mrdrdel_060329_134332.bak20:readFile(WFFileUtil.java:667):reading file D:/ibi/WebFOCUS76/basedir\admin.htm21:readFile(WFFileUtil.java:758):new FileInputStream is created to readthe file admin.htm22:readFile(WFFileUtil.java:765):Successfully finished reading fileadmin.htm...42:deleteUnknownDeferTickets(WFMRRepository.java:2197):MR user adminprocessing ended

258 WebFOCUS


Backup of MR User HTM FileReference:

A backup is created for each MR user HTM file processed in the MR Repository beingaccessed. The default MR Repository is specified by the MR_BASE_DIR variable in theWebFOCUS Client configuration file (cgivars.wfs). OS level tools can be used to view thecontents of the MR user HTM backup file or restore the user's working file with the backupfile. After restoring the user's working file, the WebFOCUS Client Memory must be refreshed,which can be done via the WebFOCUS Administration Console.

The file name of the MR user HTM backup file is in the following form:

user_mrdrdel_date_time.bak

where:

user

Is the MR user's HREF value.

date

Is the date in YYMMDD format.

time

Is the time in HHMMSS format.

MR user HTM backup files must be deleted manually.

Running the MR Deferred Ticket Cleanup Utility

How to:

Run the MR Deferred Ticket Cleanup Utility

Run the MR Deferred Ticket Cleanup Utility in Silent Mode

Run the MR Deferred Ticket Cleanup Utility in Interactive Mode

Run the MR Deferred Ticket Cleanup Utility in Help Mode

Reference:

Requirements for Running the Deferred Ticket Cleanup Utility

MR Deferred Ticket Cleanup Utility File Comments

The Deferred Ticket Cleanup Utility is an operating system-specific command program(mrdtcleanup) that calls Java program MRDTCleanup and is installed in the /utilities directoryunder the WebFOCUS Client installation.



In a Windows environment, to run in interactive mode, select from the Programs menu(Information Builders, WebFOCUS76, Utilities, and then Cleanup Unknown Deferred Tickets).To run in silent mode or obtain help information on the Java program (MRDTCleanup),open a command window and navigate to the installation_drive:\ibi\WebFOCUS76\utilitydirectory. For parameter values to specify for running in silent mode, or to obtain helpinformation for Java program (MRDTCleanup) arguments, see How to Run the MR DeferredTicket Cleanup Utility on page 262.

In a UNIX environment, to run in interactive mode, select the mrdtcleanup script file,which is located in the /ibi/WebFOCUS76/utility directory. The UNIX script file onlysupports lowercase letters (-I, -s, -h) as the first parameter for each argument. Forparameter values to specify for running in silent mode, or for information on Java program(MRDTCleanup) arguments, see How to Run the MR Deferred Ticket Cleanup Utility onpage 262.

Requirements for Running the Deferred Ticket Cleanup UtilityReference:

The following are the requirements for running the Deferred Ticket Cleanup Utility:

The user must be a Managed Reporting Administrator.

The application server on which the WebFOCUS Client is installed and configured mustbe available. The WebFOCUS Client is called by the application server for MR securityauthorization and authentication, deferred reporting, and communication to WebFOCUSReporting Servers.

The fully qualified path to the location of web.xml in the WebFOCUS Client installationdirectory must be provided.

The user ID that is running the Deferred Ticket Cleanup Utility must have read and writeaccess to read and delete deferred tickets and to create the backup HTML file for eachMR user repository file that is processed.

When WebFOCUS is configured for Managed Reporting Realm Driver for DBMS ExternalAuthentication and/or DBMS External Authorization, the path to the JDBC driver needsto be supplied. Set the JDBC_DRIVER_JARS variable to the full path to the JDBC driverjar file(s).

If your JDBC driver consists of more than one Jar file, separate the multiple jar file pathswith a semi-colon in a Windows environment, or a colon in a UNIX environment. Forexample:

JDBC_DRIVER_JARS=C:\Program Files\Microsoft SQL Server 2000 Driver for JDBC\lib\mssqlserver.jar;C:\Program Files\Microsoft SQL Server 2000 Driver for JDBC\lib\msutil.jar;C:\Program Files\Microsoft SQL Server 2000 Driver for JDBC\lib\msbase.jar

260 WebFOCUS


When running in silent mode:

WebFOCUS Reporting Server node names and credentials must be specified in theWebFOCUS Client configuration file, site.wfs. For information on specifying server anduser credentials in site.wfs, see WebFOCUS Reporting Server and User Credentials onpage 254.

The MR Administrator user ID and password must be specified as parameters on thecall to the mrdtcleanup utility. For information on specifying the MR Administrator userID and password values as parameters, see How to Run the MR Deferred TicketCleanup Utility on page 262.

MR Deferred Ticket Cleanup Utility File CommentsReference:

The .bat and UNIX script files contain comments with the following sections clearly identified:

Parameters - Contains information on parameters accepted by the utility from the commandline.

Purpose - Explains functional purpose of the utility.

Requirements - Explains information required for running the utility, and user authorizationand authentication requirements.

Usage Notes - Contains information on arguments the Java program (MRDTCleanup) accepts.You can obtain the help information by specifying '-h' as the first parameter. See AdditionalAdministration Topics on page 211.

Variable Definition - Variables created and used by the utility, including:

Mode in which the utility is running (interactive, silent, help).

MR Repository.

MR user credentials for running in silent mode.

Directory path information. Note that the variable name WFJAVAASSIST uses relativereferencing, so it is recommended that you run the utility from the /utilities directoryunder the WebFOCUS Client installation.

CLASSPATH the Java program (MRDTCleanup) will use.

Interactive Mode - Command block for running in interactive mode. This is the defaultmode of execution.

Silent Mode - Command block for running in silent mode.

Help Mode - Command block for running in help mode to get usage information for the Javautility.



Interactive Mode - Command block for running in interactive mode. This is the defaultmode of execution.

Silent Mode - Command block for running in silent mode.

Help Mode - Command block for running in help mode to get usage information for the Javautility.

How to Run the MR Deferred Ticket Cleanup UtilityProcedure:

To run the MR Deferred Ticket Cleanup Utility in silent mode or help mode, you must supplyappropriate parameters. If no parameters are supplied, the utility runs in interactive modeand you are prompted for each parameter.

From the /utilities directory under the WebFOCUS Client installation (for example, on UNIX:/ibi/WebFOCUS76/utility), enter the following on the operating system command line:

mrdtcleanup parm1 parm2 parm3

where:

parm1

Is the mode in which the utility is run. If no value is entered, the default is interactivemode.

-i runs the utility in interactive mode.

-s runs the utility in silent mode.

-h returns argument information for the Java program (MRDTCleanup).

parm2

Is the value of the MR Administrator user ID, which is required for silent mode.

parm3

Is the password for the MR Administrator user ID, which is required for silent mode.

How to Run the MR Deferred Ticket Cleanup Utility in Silent ModeProcedure:

When you run the Deferred Ticket Cleanup Utility in silent mode, the MR Administrator userID and password and the WebFOCUS Reporting Server node names and user credentials,must be provided because there is no user interaction while the utility is running.

By default, the MR Repository specified by the WebFOCUS Client variable MR_BASE_DIR isthe one that is processed. To process a different MR Repository, make a copy of themrdtcleanup utility file. Edit the copied file and set the REPOS variable to the fully qualifiedpath of the directory of the MR Repository to be processed.

262 WebFOCUS


To run the utility in silent mode, from the /utilities directory under the WebFOCUS Clientinstallation (for example: /ibi/WebFOCUS76/utility on UNIX), enter the following on theoperating system command line:

mrdtcleanup -s parm2 parm3

Informational messages appear, informing you of processing status. Review the log filecreated by the utility to confirm that processing completed successfully.

Note: For information on how to create a utility file to process multiple MR repositories whenrunning in silent mode, see Processing Multiple MR Repositories in Silent Mode on page 269.

How to Run the MR Deferred Ticket Cleanup Utility in Interactive ModeProcedure:

When you run the Deferred Ticket Cleanup utility in interactive mode, it provides promptsand informational messages to help guide you through each step of the process of deletingunknown deferred tickets. To run the utility in interactive mode, perform the following steps.

1. On Windows, select the following from the Programs menu:Information Builders,WebFOCUS76, Utilities, and then Cleanup Unknown Deferred Tickets.

On UNIX, from the /utilities directory under the WebFOCUS Client installation(/ibi/WebFOCUS76/utility directory), on the operating system command line enter:

mrdtcleanup

The following messages appear:

Managed Reporting utility to delete Unknown Deferred Report tickets isbeing called in Interactive Mode.The Utility to delete Unknown Deferred Report Tickets has started.

2. The utility prompts you to enter MR Repository information.

Enter MR Repository location to cleanup (press Enter to use the default MR Repository):

The default MR Repository is specified by the MR_BASE_DIR variable in the WebFOCUSClient configuration file (cgivars.wfs). The utility validates that the directory path enteredis a valid MR Repository by confirming that the user.htm and mrrepos.htm files residein that directory. If confirmation is not successful, the following message appears andthe utility continues to prompt for MR Repository information:

Location specified <location> is not a valid MR Repository.



3. The utility displays the following prompts for MR user ID and password (with maskingon the password) and validates that the credentials entered belong to an MRAdministrator.

Enter valid MR Administrator user ID for repository specified:<value> (must be a non-blank value)

Enter password for MR Administrator user(press Enter for empty password value):** (blank value permitted and value entered is masked by * for each character entered)

Please, re-enter password for MR Administrator user(press Enter for empty password value):** (blank value permitted and value entered is masked by * for each character entered)

If credentials are not successfully validated, the following messages appear:

The passwords you typed do not match.Please enter your password again.

Enter password for MR Administrator user (press Enter for empty password value):** (blank value permitted and value entered is masked by * for each character entered)

Please, re-enter password for MR Administrator user(press Enter for empty password value):** (blank value permitted and value entered is masked by * for each character entered)

264 WebFOCUS


If the MR user credentials do not belong to a valid MR Administrator, the followingmessages appear and the utility continues to prompt for MR Administrator credentials:

Enter valid MR Administrator user ID for repository specified:<user ID>

Enter password for MR Administrator user(press Enter for empty password value):*

Please, re-enter password for MR Administrator user(press Enter for empty password value):**Authenticating MR User: <user ID>

Provided user is not an MR Administrator.Would you like to enter another MR User ID and password?(yes/no)Enter "no" to skip processing of this repository orpress Enter to continue with "yes" value:

Enter valid MR Administrator user ID for repository specified:<user ID>

Enter password for MR Administrator user(press Enter for empty password value):*

When credentials are validated, the following message appears:

MR Administrator credentials successfully authenticated

4. The WebFOCUS Reporting Server node names are read from the WebFOCUS Client'sodin.cfg file and verified in the “indef” block of the site.wfs file, which defines the validWebFOCUS Reporting Servers and user credentials that can be used by this utility. Thefollowing prompt appears:

Checking for WF Server credentials optionally specifiedin WF Client configuration file (site.wfs)...

Following WF Server is configured in odin.cfg:

Node name : <server name> Host name : <host name>

If server nodes are not defined in site.wfs, the following prompt appears:

No WF Server credentials specified in site.wfs WF configuration file.Would you like to provide credentials for WF Servers? (yes/no)Press Enter to continue with "yes" value:



If server nodes are defined in site.wfs, the following prompt appears:

The following WF Servers have credentials specified in site.wfs:<server1 name>

Would you like to change existing WF Server credentials orprovide credentials for additional WF Servers?(yes/no)Press Enter to continue with "yes" value:

If you want to provide additional WebFOCUS Reporting Server node names and usercredentials, enter the appropriate information when the following prompts appear:

Enter WF Server name: <server name>

Enter user ID for WF Server: <user id>

Enter password for WF user(press Enter for empty password value):*******

Please, re-enter password for WF user(press Enter for empty password value):*******

Would you like to provide credentials for another WF server? (yes/no)Press Enter to continue with "yes" value:

5. When you are finished entering and validating WebFOCUS Reporting Server node namesand user credentials, the utility begins processing each MR user's HTM file in the MRRepository. The following messages appear on the screen in both interactive and silentmodes.

WF Server credentials have been checked/updated.Starting processing MR repository...

Processing of MR repository d:/ibi/WebFOCUS76/basedir starting.Processing the repository for all users

MR user admin processing started.Creating a backup of user's html file admin.htm

Successfully created user's backup file:d:/ibi/WebFOCUS76/basedir\admin_mrdrdel_<date>_<time>.bak

Retrieving deferred report information and verifying status...

MR user admin processing ended

266 WebFOCUS


6. When all MR users' HTM files are processed, the following information appears:

Processing completed for MR repository d:/ibi/WebFOCUS76/basedirReview log file mrdrdel_<date>_<time>.log located in/logs directory under WF Client install to confirm status of processing

Processing completed for MR repositoryWould you like to process another MR repository? (yes/no)Enter "no" to finish processing orPress Enter to continue with "yes" value:

How to Run the MR Deferred Ticket Cleanup Utility in Help ModeProcedure:

To run the MR Deferred Ticket Cleanup Utility in help mode, from the /utilities directory underthe WebFOCUS Client installation (for example: /ibi/WebFOCUS76/utility on UNIX), enterthe following on the operating system command line:

mrdtcleanup -h

The screen displays help information for Java program (MRDTCleanup) arguments. If additionalarguments are included, they are ignored.

The argument information returned by the Java program (MRDTCleanup) provides informationon the requirements and options for running the program. With this information, you cancreate a site-customized utility file to process your MR deferred report tickets to performtasks such as processing multiple MR repositories in silent mode.



The following is an example of what is displayed when the MR Deferred Ticket Cleanup Utilityis run in help mode:

Managed Reporting utility to delete Unknown Deferred Report ticketsis being called with -h argument to request usage information.ECHO is off.USAGE :java MRDTCleanup [-?] [-s] -c(confpath) [-r[reposlocation.userID.pass[+...]]]

ARGUMENT (args) FORMAT:-(?/h) Get help; if no arguments, help information is displayed If more args after '-?' or '-h', they are ignored.

-s If present, turns on the silent mode. MR repository location MUST be specified using -r argument. WF Server credentials MUST be specified in site.wfs as: <ifdef> IBIMR_dtcleanup WF_CCREDENTIALS=edanode1:id:pass|edanode2:id:pass|... <endif> Credentials information MUST be provided for each WF Server node in odin.cfg that deferred tickets have been submitted to.

-c(confpath) Fully qualified path to the installation directory where WebFOCUS application configuration file, web.xml, is located. This parameter MUST be provided. -cC:\ibi\WebFOCUSXX\webapps\webfocusXX\WEB-INF where 'XX' is a WebFOCUS release number.

-r(reposlocation.id.pwd[+reposlocation.id.pwd[+...]]) This argument is ignored if this utility is run in interactive mode! MR repository location(s) as well as MR Administrator credentials (id and password) for each location. MR repository value is optional. When not specified, default MR repository (MR_BASE_DIR) is processed. When specified, is fully qualified path to location of the MR repository to be processed. MR credentials MUST be a MR Administrator. Multiple sets can be specified using '+' char as a separator between repository and MR credential sets. Format processing default MR repository with MR credentials specified: -r.id.password Format specifying single MR repository: -rrepositorylocation.id.password Format for multiple repository and credential sets: -rrepositorylocation.id.password+repositorylocation.id.password

268 WebFOCUS


Processing Multiple MR Repositories in Silent ModeTo process multiple MR repositories in silent mode, you can create your own site-customizedutility file to call the Java program (MRDTCleanup). For argument information for the Javaprogram (MRDTCleanup), see How to Run the MR Deferred Ticket Cleanup Utility in Help Modeon page 267.

When running the Java program (MRDTCleanup), your CLASSPATH must include the followingfiles from the WebFOCUS Client installation:

installation_drive:\ibi\WebFOCUS76\webapps\webfocus76\WEB-INF\lib\tools.jar installation_drive:\ibi\WebFOCUS76\webapps\webfocus76\WEB-INF\lib\srv.jar installation_drive:\ibi\WebFOCUS76\webapps\webfocus76\WEB-INF\lib\uas.jar

installation_drive:\ibi\WebFOCUS76\webapps\webfocus76\WEB-INF\lib\nlslt.jar installation_drive:\ibi\WebFOCUS76\ibi_html\javaassist\WFAPI.jar

The command to call the Java program (MRDTCleanup) and process multiple repositoriesin silent mode is:

java MRDTCleanup -s -cconfpath-rreposlocation1.id1.pass1+reposlocation2.id2.pass2+...

where:

confpath

Specifies the fully qualified path to the installation directory where the WebFOCUSapplication configuration file, web.xml, is located. This value must be provided. The pathto the web.xml file is installation_drive:\ibi\WebFOCUS76\webapps\webfocus76\WEB-INF. For related information, see CONFPATH Error on page 271.

reposlocation1.id1.pass1+reposlocation2.id2.pass2+...

When reposlocation1 is specified, it is the fully qualified path to the location of theMR Repository to be processed (the default MR Repository, MR_BASE_DIR, is used whenyou do not specify this value). Specify MR credentials (id1 and pass1) using a '.'character as a separator after the repository location. These credentials must be thoseof an MR Administrator. You can specify multiple sets using a '+' character as a separatorbetween repository and credential sets.

For example, the following parameter value specifies two MR repositories and MR usercredentials for each repository:

d:\ibi\WebFOCUS76\basedir.mradminid1.adminpass1+d:\ibi\WebFOCUS76\testenvir.mradmin2.adminpass2

To process the default MR Repository, MR_BASE_DIR, do not specify a value forreposlocation1 and use the '.' separator to specify MR credentials. For example:

.mradminid1.adminpass1+d:\ibi\WebFOCUS76\testenvir.mradmin2.adminpass2



Troubleshooting

Reference:

Trace File

CONFPATH Error

WebFOCUS Reporting Server Connection Failure

Silent Mode Failure

The following topics will help you troubleshoot possible error codes, exception messages,and connection failures when running the Deferred Ticket Cleanup Utility.

Trace FileReference:

A trace file is available in the WebFOCUS Administration Console to view processing detailsfor the Deferred Ticket Cleanup Utility. You must first turn on the WFServlet trace option,which is turned off by default. A trace file is created each time the utility is executed.

The file name of the trace file is in the following form:

00100_mrdtcleanup_WFAPI_date_time.trace

where:

date

Is the date the trace file was created in Year Month Day (YYYY-MM-DD) format.

time

Is the time the trace file was created in Hour Minute Second (HMS) format.

270 WebFOCUS


To view the resulting trace files, click the MR Deferred Ticket Cleanup Utility option on theTraces menu under the Diagnostics section of the WebFOCUS Administration Console, asshown in the following image.

To view information for a trace file, click the link with the desired date and time that has a.trace file extension listed in the right pane of the console. To delete a trace file, select thecheck box next to the file and click the Delete button at the bottom of the console. You canalso use the Select All and Deselect All options as needed, or click the Refresh option toensure that the latest information appears in the console.

CONFPATH ErrorReference:

The WebFOCUS Client installation program installs the mrdtdcleanup files to the /utilitiesdirectory under the WebFOCUS76 directory and substitute the {confpath} value.

When running the MR Deferred Ticket Cleanup Utility, if the value of CONFPATH is not thevalid directory path to web.xml, the utility displays error exception information including areference to the CONFPATH location and a message indicating that the utility encounteredan error. There is no log file available for troubleshooting because the log file is only createdupon successful initialization of the utility.

If you encounter this error, from the command line edit the mrdtcleanup.bat file on Windows,or the mrdtcleanup script file on UNIX, and manually correct the CONFPATH variable settingto be:

set CONFPATH=installation_drive:\ibi\webfocus76\webapps\webfocus76\WEB-INF



WebFOCUS Reporting Server Connection FailureReference:

When deferred tickets are processed and the credentials provided are not valid, theWebFOCUS Reporting Server is unavailable, or there are no available agents on the server,no tickets for that server are deleted. The log information informs the MR Administrator thatprocessing for that server failed by stating that a connection could not be made to theWebFOCUS Reporting Server. The MR Administrator can then investigate the processingfailure, make adjustments, and run the utility again.

The Deferred Ticket Cleanup Utility receives the standard error codes and exception messagesreturned to the WebFOCUS Client for failed connections. The WebFOCUS Client file/ibi/WebFOCUS76/client76/wfc/etc/xxib00e.htm (where xx is the language prefix) mapseach error code with an explanation. For example, the following sample log file containserror code 32033, which appeared when attempting to connect to WebFOCUS ReportingServer EDASERVE:

27:deferredExecution(WFMRActions.java:3011):executing deferredGetStatus()failed for the WF Server EDASERVE 28:deferredExecution(WFMRActions.java:3012):WFErrorException has been thrown!29:deferredExecution(WFMRActions.java:3013):Exiting deferredExecution() with the error code 3203330:deleteUnknownDeferTickets(WFMRRepository.java:2168):deleteUnknownDeferTickets: MR Error has occurred!31:deleteUnknownDeferTickets(WFMRRepository.java:2169):WFMRError code : 3203332:deleteUnknownDeferTickets(WFMRRepository.java:2170):WFMRError message : Error occurred, rc = 32033<ERROR 32033><ERROR 32034><HTML><HEAD><Title>WebFOCUS Message: Security Violation</Title></Head><Body><H2>Invalid Credentials</H2></Body></HTML></ERROR>

272 WebFOCUS


In the WebFOCUS Client error file D:\ibi\WebFOCUS76\client76\wfc\etc\isib00e.html,search for the error code to view more detailed information about the error.

<ERROR 32033><ERROR 32034><HTML><HEAD><Title>WebFOCUS Message: Security Violation</Title></Head><Body><H2>Invalid Credentials</H2></Body></HTML></ERROR>

Silent Mode FailureReference:

When you run the utility in silent mode and the WebFOCUS Client configuration file site.wfsdoes not contain WebFOCUS Reporting Server node name information, the log file containsthe following information. Review the site.wfs file and confirm the following:

There are no errors in the syntax of the <ifdef> IBIMR_dtcleanup block.

The WebFOCUS Reporting Server node name is the value of the NODE variable in theWebFOCUS Client odin.cfg file.



Sample Log File Created in Silent ModeExample:

The following is an example of a log file created in silent mode:

0:=================================================================1: user log opened Mon Sep 25 06:32:00 EDT 20062:=================================================================3:createWFLog(WFContext.java:1728):Starting WebFOCUS log-file formrdtcleanup4:main(MRDTCleanup.java:135):The Utility to delete Unknown Deferred Report Tickets has started...5:isSilentMode(MRDTCleanup.java:253):as option "-s" is passed the Utilityis going to work in the silent mode.6:isSilentMode(MRDTCleanup.java:254):This mode requires all the parameters/credentials being pre-set.7:main(MRDTCleanup.java:154):Utility is running in the silent mode8:runInSilentMode(MRDTCleanup.java:324):NO WF Server credentials provided!9:runInSilentMode(MRDTCleanup.java:325):Deferred status information can only be retrieved from unsecured servers.10:runInSilentMode(MRDTCleanup.java:361):retrieved MR Repository to be processed : d:\ibi\WebFOCUS71\basedir11:runInSilentMode(MRDTCleanup.java:364):Files "mrrepos.htm" and "user.htm" have been found in the specified location12:runInSilentMode(MRDTCleanup.java:365):MR Repository location is valid,continue processing...13:runInSilentMode(MRDTCleanup.java:390):MR Default Repository beingprocessed d:\ibi\WebFOCUS71\basedir14:runInSilentMode(MRDTCleanup.java:406):authenticating MR User :admin15:isMRAdministratorUser(MRDTCleanup.java:650):Authenticating MR User: admin16:runInSilentMode(MRDTCleanup.java:420):MR Administrator user is authenticated for MR Repository :d:\ibi\WebFOCUS71\basedir17:runInSilentMode(MRDTCleanup.java:421):The utility will proceed to process Unknown Deferred Tickets for this repository...18:deleteUnknownDeferTickets(WFMRRepository.java:2058):Processing of MR repository d:\ibi\WebFOCUS71\basedir starting.

274 WebFOCUS


19:deleteUnknownDeferTickets(WFMRRepository.java:2070):Getting a list ofusers on the repository20:deleteUnknownDeferTickets(WFMRRepository.java:2081):Processing deferred tickets for admin21:deleteUnknownDeferTickets(WFMRRepository.java:2093):Creating a backupof user's html file admin.htm22:deleteUnknownDeferTickets(WFMRRepository.java:2117):user's html fileexists, copying it to d:\ibi\WebFOCUS71\basedir\admin_mrdtcleanup_060925_063200.bak23:readFile(WFFileUtil.java:678):reading file d:\ibi\WebFOCUS71\basedir\admin.htm24:readFile(WFFileUtil.java:758):new FileInputStream is created to read the file admin.htm25:readFile(WFFileUtil.java:765):Successfully finished reading admin.htm 26:writeFile(WFFileUtil.java:1323):file admin_mrdtcleanup_060925_063200.bak does NOT exist, - create one...27:writeFile(WFFileUtil.java:1332):created the file admin_mrdtcleanup_060925_063200.bak28:writeFile(WFFileUtil.java:1352):writing the file admin_mrdtcleanup_060925_063200.bak29:writeFile(WFFileUtil.java:1366):successfully wrote content into the file admin_mrdtcleanup_060925_063200.bak30:deleteUnknownDeferTickets(WFMRRepository.java:2133):Successfully created user's backup file d:\ibi\WebFOCUS71\basedir\admin_mrdtcleanup_060925_063200.bak31:deferredExecution(WFMRActions.java:3026):executing deferredGetStatus()failed for the WF Server EDASERVE 32:deferredExecution(WFMRActions.java:3027):WFErrorException error code 3203333:deferredExecution(WFMRActions.java:3026):executing deferredGetStatus()failed for the WF Server DEFERRED34:deferredExecution(WFMRActions.java:3027):WFErrorException error code 3203335:deleteUnknownDeferTickets(WFMRRepository.java:2200):MR user admin processing ended ...

(between lines 35 and 60 additional MR users are processed)60:deleteUnknownDeferTickets(WFMRRepository.java:2218):Processing completed for MR repository d:\ibi\WebFOCUS71\basedir61:main(MRDTCleanup.java:158):MRDTCleanup utility finished processing.62:=================================================================63: user log closed Mon Sep 25 06:32:01 EDT 200664:=================================================================



276 WebFOCUS


WebFOCUS

Index

A

accessing metadata 18

Add Block window 153

Add Two-Way Email Subscriber dialog box 233, 234

adding a column 168

adding items to Role Trees 144

allocating extract files 183

alternate deferred servers 248

amper auto-prompting 53, 227customizing launch pages 227launch page templates 227

amper variables 227

applets 214

application files 190moving 190

Application Path 45, 46properties 45specifying 46

assigning domains 51

auto-prompting 227launch page templates 227

B

back-out packages 206

background images 115, 122

banners 115, 118, 123, 124, 127, 129, 130, 131adding links 129adjusting height for 127, 130customizing colors 115, 118deleting 127, 129positioning 123, 124

banners (continued)welcome message 131

bid-config.xml 83, 84, 86, 131, 136, 139, 217

browser windows 99, 223, 224, 225, 226, 227customizing 223, 224, 225, 226, 227enabling context menu 99

C

cancelling changes to Role Trees 145

change management 190, 191, 192, 193, 194, 196, 207

copying domains 196copying files 194in Dashboard 207internal references 192Managed Reporting Repository and 191moving files 190

changing a user's Dashboard view 75

changing the public user ID 77

Color Palette window 115, 117

Color Scheme window 115

colors 115, 117background 115of content blocks 115of domains 115of messages 115of text 115

columns 168, 169adjusting width 169positioning 168

components 190

Composition window 123, 124

content block types 153


content blocks 115, 121, 147, 148, 150, 152, 153, 157, 159, 160, 161, 162, 166, 167, 168, 169

adding 153adding items 160adding items from domain search 157and EXL2K PIVOT format 157changing names of 162creating 148, 153custom color areas 121deleting 159deleting items 160, 161editing 160, 161hiding 162hiding the toolbar 166layout 167, 168saving 150types 147

Content List 153

content pages 150, 151, 167creating multiple 150rearranging 150selecting layout 167

Content window 148, 150exiting 150

control bars 119

copying domains between environments 196

copying domains using Developer Studio 196

copying files between environments 194

copying files using Developer Studio 194

creating objects 192

creating Role Trees 141

Custom Colors window 115

custom public views 69, 70managing 70

Custom Reports 68promoting to Standard Reports 68

custom templates 111

customizations 139saving 139

customizing browser windows 223, 224, 225, 226, 227

restrictions 227

customizing Dashboard 148

customizing Dashboard logoff window 136

customizing error messages in Dashboard 83

customizing the HTML Report/Graph Assistant in

Dashboard 117

DDashboard 17, 26, 28, 69, 96, 99, 105, 111,

112, 115, 148, 167custom templates 111customizing 28, 99, 105, 112, 115, 148domain profiles 167logging on 26managing 69opening 26templates 111

Dashboard change management 207, 208, 209

Dashboard logoff window 136

Dashboard Properties 87, 88displaying optional properties 87, 88

debugging Java applets 213

default repository 228

deferred listener options 250

Deferred Report Status interface 148, 150, 151

Deferred Report Status Interface 222, 226, 250expiration setting 250invoking directly 222

deferred reports 211, 248, 250, 251managing 248purging 251

Deferred Status option 68

278 WebFOCUS

Index

Deferred Ticket Cleanup Utility 252, 253, 254, 255, 256, 259, 260, 261, 262, 263, 267, 269, 270, 271, 272, 273

creating backup HTML file 253, 256, 259, 260creating log file 253, 256Managed Reporting Repository 253, 262, 263MR repositories 269multiple repositories in silent mode 269processing Managed Reporting Repository 252, 253running in help mode 261, 262, 267running in interactive mode 254, 259, 261, 263running in silent mode 254, 259, 260, 261, 262specifying server credentials 254troubleshooting CONFPATH Error 270, 271troubleshooting server connection failure 270, 272troubleshooting silent mode error 273troubleshooting silent mode failure 270Trusted connection restriction 255UNIX 259, 261, 263using with Realm Driver 260validating server credentials 255, 263WebFOCUS Administration Console 254, 255Windows 259, 263

deferred tickets 248, 253, 260deleting 253, 260

deleting items from Role Trees 144, 145

deleting My Reports 66

deployment process 21

descriptions for navigating Managed Reporting 192

Developer role 51

Developer Studio 42, 192, 194, 196accessing MR Administration interface 42copying domains 196copying files 194

directories bar 226, 227

Domain Admin 191

Domain Builder 23, 42, 51, 63, 68accessing MR Administration interface 42components 23

domain builder applets 214tracing 214

domain content information 172

domain information 172

domain profiles 167in Dashboard 167

Domain property flags 185, 187

domain search 153, 157adding items to content blocks 157

Domain Trees 83, 84, 123, 124displaying 123, 124hiding 123, 124hiding reports 83positioning 123, 124showing only Standard Reports 83, 84

domains 41, 43, 48, 51, 115, 120, 191, 196adding in a group 48assigning to a developer 51changing color of 115colors 115copying 196creating 43custom color areas 120deleting 43modifying properties 43removing in a group 48

Domains output files 175

DYNAM ALLOC command 182

E

Edit window 160

editing My Reports 66

editing Role Trees 144

empty blocks 148


Index

environments 16, 35, 38Managed Reporting/ReportCaster properties 38Web server properties 35

error messages in Dashboard 83

Event Log for Two-Way Email 240purging 240

EXL2K PIVOT format 157in Dashboard 157

extract files 182

extracting information from MR Repository 172,

174, 175

F

file allocations 182

FILEDEF command 182

finished My Reports 86, 87, 88hiding the share option 86, 87, 88

folder blocks 99, 147, 153, 160changing contents 160reloading content 99

folders 23, 24deleting 24

frame separators 123

FTP output files 182

Ggeneral public views 69, 70

managing 70Graph Assistant 117, 211

customizing in Dashboard 117Group Administrator 46, 48, 50, 51, 53, 96

assigning privilege 50, 51

group information 172

Group output files 174

group views 69, 71, 91, 92, 93, 95, 96, 97, 98, 102, 103

adding 93copying 102, 103creating 93, 95deleting 98directing users to upon login 96, 97editing 98exiting 103managing 71window 93, 103

groups 41, 46, 47, 48, 50adding domains to 48adding users to 47creating 46, 47removing domains from 48removing users from 47

H

hiding content blocks 162

hiding the toolbar in a content block 166

HTML Graph Assistant 117customizing in Dashboard 117

HTML Report Assistant 117customizing in Dashboard 117

HTML User Environment 226

http errors in Dashboard 83

IIBIExtractRepos utility 171, 172, 173, 174

output files 174

IBIMRDMC.MAS Master File 176, 184

IBIMRDOM.MAS Master File 176, 185, 187

IBIMRGRP.MAS Master File 176

IBIMRROL.MAS Master File 176

IBIMRUSR.MAS Master File 176, 185

280 WebFOCUS

Index

idle limit 81, 82for authenticated users 81, 82for public users 82

internal references 192

invoking the Deferred Report Status Interface 222

J

JavaScript options 223, 224, 225, 226

Job Log for Two-Way Email 237, 239purging 239

Llaunch blocks 147, 152, 153, 160, 162

changing contents 160, 162launch pages 227, 228

coding a FOCEXEC 227settings in Administration Console 227

layout of content blocks 167

Library content in Dashboard 159

Library Only User role 71

Library page 152

link colors 115

links 127, 129adding 129deleting 129

list blocks 147, 152, 153, 160, 161adding items 160deleting items 160, 161

list of users 68

location bars 226, 227

locked content block 158

logging on to the Dashboard 26

Logo & Links window 125, 127

logos 125, 126, 127inserting 125, 127maximum size 125, 126

Look templates 112

Look window 109

M

Manage Users 75

Managed Reporting 18, 23, 24, 192, 212configuring tool types 212Data Servers 23domains 23internal references 192navigating 192tool types 212toolbars 24

Managed Reporting Administration interface 23, 41, 42, 47, 48, 50, 51, 53, 61, 62

customizing 62

Managed Reporting Administrator 18, 41, 43, 45,

46, 48, 50, 53, 252, 253, 260, 262, 263, 272

Managed Reporting deployment process 21

Managed Reporting Extract utility 171, 172

Managed Reporting logon page 223

Managed Reporting Repository 38, 171, 172, 192, 228

extracting information 172

Managed Reporting/ReportCaster properties 38

managing group views 71

managing private views 72

managing public views 70

managing users in Dashboard 75

Master Files 176IBIMRDMC.MAS 176IBIMRDOM.MAS 176IBIMRGRP.MAS 176


Index

Master Files (continued)IBIMRROL.MAS 176IBIMRUSR.MAS 176

menu bars 226, 227

Message of the Day 121, 135custom color areas 121editing outside of Dashboard 135

messages in Dashboard 83

metadata 18OLAP-enabled 18

migrating existing customizations 105

moving components between environments 190

MR Deferred Ticket Cleanup Utility 270trace files 270

MR_BASE_DIR variable 228

MRSAMP01.FEX sample procedure 176

multiple content pages 150

My Reports 53, 63, 66, 83, 84, 99deleting 66editing 66hiding 83hiding from user roles 99hiding from users 84

O

OCP (OLAP Control Panel) 223

OLAP Control Panel (OCP) 223

OLAP-enabled reports 18manipulating 18running 18

organizing Dashboard content 150

Other Files 99hiding from user roles 99

output blocks 147, 152, 153

output files 174, 182, 183, 184allocating 183FTP 182

output files (continued)relationships 184

P

page tabs 99, 120

pages 99reloading 99

passwords 77, 79, 80for the public user 77, 79, 80

positioning columns 168

private views 26, 69, 72logging on 26managing 72

promoting Custom Reports to Standard Reports 68

propertiesdisplaying Created By 99displaying Last Modified By 99share option 99

property flags 185

public groups 106

public user 71, 106Library privileges 71rights 106

public user ID 77changing 77

public view links 127, 128, 129adding 129deleting 128, 129editing 128

public views 26, 71, 79, 80, 91, 92, 93, 95, 98, 102, 103, 127, 148, 150, 151

adding 93copying 102, 103creating 93, 95customizing 127deleting 98editing 98exiting 103Report Library access 71setting user ID and password 79, 80

282 WebFOCUS

Index

public views (continued)window 93, 103

Public Views button 150

PUBLIC_MAX_INACTIVE parameter 82

R

read-only content block 158

refresh options 68

Reload Domain option 68

Reload User Management option 68

Reload User option 68

removing banners 127, 129

Report Assistant 117, 211customizing in Dashboard 117

Report Library 71, 148, 150, 151, 152, 159window 148

ReportCaster 17, 18, 23, 59, 99, 148, 150, 151, 212

Scheduler 99

ReportCaster Alerts 18

ReportCaster single page Scheduler Tool 138, 139

Reporting Objects 18, 83, 84, 99creating 18hiding 83hiding from user roles 99hiding from users 84organizing by domains 18

reports 18, 64, 68creating 18deleting 64editing 64publishing 18running 64running deferred 68

REPOSITORY_CACHE setting 251

resetting the View Builder 107, 109

resizing browser windows 226, 227

role information 172

role inheritance 58

role property flags 185

Role Tree window 142

Role Trees 123, 124, 141, 142, 143, 144, 145adding items 144cancelling 145creating 142, 143deleting items 144, 145displaying 123, 124editing 144hiding 123, 124positioning 123, 124

roles 41, 50, 53, 54, 58, 61Analytical User 54assigning 50base roles 53, 58Content Manager 54creating 53creating new 61customizing existing 61defined 54Developer 54inheritance 58Library Only User 54Run Only User 54user 54

S

Save Entered Values privilege 53

saving content blocks 150

saving customizations 139

screen alignment 226, 227

scroll bars 166, 226, 227

scroll buttons 166


Index

scrolling options 125, 160, 165

Section 508 186user flag 186

server properties 45

Server window 79

Share Report option 86, 87, 88hiding 86, 87, 88

Shared Reports 83, 84, 99hiding 83hiding from user roles 99hiding from users 84

sidebar list position 123, 124

site customization 223, 224, 225, 226, 227restrictions 227

Standard Reports 18, 68, 84, 88, 99creating 18creating from a Custom Report 68creating in Dashboard 88, 99hiding from user roles 99limiting display in the Domain Tree 84organizing by domains 18synchronizing 18

status lines 226, 227

storing credentials on a WebFOCUS Server 39

subscribers 232

Ttemplates 109, 110, 111, 112, 115, 117, 125,

126color schemes 115custom 111custom colors 115, 117in Dashboard 111logos 125, 126selecting 109, 110

text colors 115

time out period 81, 82for authenticated users 81, 82

time out period (continued)for public users 82

tool types 212associating users with tools 212

toolbar 166

toolbars 23, 24, 115, 121, 132, 134, 226, 227changing colors for 115custom color areas 121

toolboxes 132, 133

trace file names 217

trace files 218

TRACE_LEVEL parameter 215, 216

traces 270MR Deferred Ticket Cleanup Utility 270

tracing 215dynamically in Dashboard 215

tracing domain builder applets 214

tracing in Dashboard 217

tracing Java applets 213, 214

tracing options in Dashboard 215, 216for OS/390 215, 216for UNIX 215, 216for Windows 215, 216

Two-Way Email 18, 232, 233, 237, 238, 240adding subscribers 233deleting subscribers 233Event Log 240Job Log 237viewing current subscribers 232viewing job status 237, 238

Two-Way Email Administrator console 232, 233, 234, 235, 236, 237, 240, 242, 243, 244, 245, 246

accessing 232adding addresses 235adding subscribers 233, 234canceling reports 245, 246deleting addresses 235, 236deleting subscribers 233, 235monitoring e-mail traffic 242, 243

284 WebFOCUS

Index

Two-Way Email Administrator console (continued)purging the Event Log 244purging the Job Log 240refreshing templates 236using the Event Log 240using the Job Log 237viewing current subscribers 232viewing job status 245

U

updating a user's Dashboard view 75

upload data file 99

user environments 18customizing 18

user information 172

User Management tree 63, 64, 66

User output files 174

user privileges 59General 59My Reports 59

user property flags 185

user roles 53, 54

USER_MAX_INACTIVE parameter 81, 82

users 41, 48, 50, 53, 59creating 48privileges 59saving parameter values 53searching for 50setting up 53

utilities 212

VView Builder 28, 87, 88, 94, 96, 99, 105, 107,

108, 109, 111, 131, 139, 140, 152customizing 108Edit Setting 99

View Builder (continued)exiting 140migrating 105opening 94, 107, 108resetting 109, 139templates 111

viewing My Reports 63

views 26custom public 26multiple public 26private 26public 26

W

wallpaper in banners 115, 122

watch list 153blocks 147, 152, 153interface 148, 150, 151

Web server properties 35

WebFOCUS Administration Console 45, 251REPOSITORY_CACHE setting 251servers 45

WebFOCUS Business Intelligence Dashboard 69, 105

managing 69WebFOCUS Client 36, 252, 253, 254, 256, 259,

260, 262, 263, 267, 271, 272, 273properties 36

WebFOCUS Client Path parameter 36

WebFOCUS Client traces 270MR Deferred Ticket Cleanup Utility 270

WebFOCUS Environment Properties 33

WebFOCUS Environment Properties dialog box 32,

192

WebFOCUS environments 16, 29adding 29

WebFOCUS Reporting Server 45, 252, 253, 254,

255, 262, 263, 272, 273


Index

WebFOCUS Server Connection window 79

WebFOCUS Server properties 39

welcome message 99, 131displaying 99

window height 226, 227

window resizing 226, 227

window width 226, 227

286 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 Managed Reporting Administrator's Manual DN4500809.1208Version 7 Release 6.1 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 Managed Reporting Administrator's Manual DN4500809.1208Version 7 Release 6.1 and Higher

wf761mradmin

Documents

Transcript of wf761mradmin