webfocus upgrade considerationsinfocenter.informationbuilders.com/wf80/topic/... · 11/30/2011 ·...

WebFOCUS Upgrade ConsiderationsRelease 8.0 Version 10

June 30, 2015

Active Technologies, EDA, EDA/SQL, FIDEL, FOCUS, Information Builders, the Information Builders logo, iWay, iWay Software,Parlay, PC/FOCUS, RStat, Table Talk, Web390, WebFOCUS, WebFOCUS Active Technologies, and WebFOCUS Magnify areregistered trademarks, and DataMigrator and Hyperstage are trademarks of Information Builders, Inc.

Adobe, the Adobe logo, Acrobat, Adobe Reader, Flash, Adobe Flash Builder, Flex, and PostScript are either registeredtrademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries.

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

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

Contents

WebFOCUS Upgrade Considerations Release 8.0 Version 10 . . . . . . . . . . . . . . . . . . . . . . . . 5Tools Consolidation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Installation and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Disabling the CSRF Token When Connecting From a Release 8.0.x Client. . . . . . . . . . . . . . . 15

Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

InfoAssist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

App Studio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

HTML Composer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Document Composer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Report Painter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

ReportCaster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

WebFOCUS Infrastructure and Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

WebFOCUS Operating Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Managed Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Business Intelligence Dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

WebFOCUS Visual Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

WebFOCUS Visual Discovery Analyst Edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Active Technologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Version Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

License Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

SET HTMLENCODE Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Handling a Hidden BY Column on an Active Technologies Chart. . . . . . . . . . . . . . . . . . . . . . . 37

Syntax: How to Handle a Hidden BY Column on an Active Technologies Chart. . . . . . 37

Saving an Active Technologies Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Using an Alternate Adobe Flex Compiler With the WebFOCUS Reporting Server. . . . . . . . . . 38

Procedure: How to Use an Alternate Adobe Flex Compiler With the WebFOCUS

Reporting Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Setting the Maximum Java Heap Size When Using an Alternate Adobe Flex Compiler. . . . . 39

Syntax: How to Set the Maximum Java Heap Size When Using an Alternate Adobe

Flex Compiler. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Customizing Styles With JavaScript Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Setting the Initial Active Technologies Chart Size. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Developer Studio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

WebFOCUS Upgrade Considerations 3

Developer Studio New Behavior. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Connecting to WebFOCUS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

WebFOCUS Environment Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Procedure: How to Change a User Password in the Developer Studio Security

Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Procedure: How to Change a User Password Through the Security Center. . . . 46

Developing Content in the Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Procedure: How to Update the Security Center to Allow Development Against

the Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Procedure: How to Restrict or Allow Access to the Data Servers Area. . . . . . . . 51

Developer Studio Upgrade Considerations and Product Changes. . . . . . . . . . . . . . . . . . . . . . 54

WebFOCUS Charts and Graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

HTML5 New Features and Upgrades. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Differences Between HTML5 Charts and Server-Generated Charts. . . . . . . . . . . . . . . . . . . . . 56

Supported Chart Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

WebFOCUS Maintain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

WebFOCUS Maintain Configuration Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

WebFOCUS Language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Compound Documents Change in Behavior. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

XLSX Worksheets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

ASIS Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

APP COPYF Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

FORMAT EXL07. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

FORMAT PPTX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Accordion By Row Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

WebFOCUS Font Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

HTML HFREEZE Reporting Feature Implementation Change. . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Variables Hidden with the -DEFAULTH Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Web Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Considerations for ReportCaster SOAP Web Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

WebFOCUS Magnify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Customer Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

4 WebFOCUS

Contents


These topics provide upgrade considerations and product changes for WebFOCUS Release8.0 Version 10.

Before reading this documentation, Information Builders recommends reviewing the upgradeconsiderations for all intermediate releases you are upgrading from, as well as theWebFOCUS Release Notes, which includes documentation enhancements, known issues,and product limitations. These documents, which are periodically updated as needed, arelocated at the following URL:

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

In this document:

WebFOCUS Operating EnvironmentsTools Consolidation

Installation and Configuration Managed Reporting

Server Configuration Business Intelligence Dashboard

WebFOCUS Visual DiscoveryMigration

InfoAssist

App Studio

HTML Composer

WebFOCUS Visual Discovery AnalystEdition

Active Technologies

Developer Studio

WebFOCUS Charts and Graphs

WebFOCUS Maintain

WebFOCUS Language

Document Composer

Report Painter

ReportCaster

WebFOCUS Infrastructure and SecurityWeb Services

WebFOCUS Magnify


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

Tools Consolidation

Information Builders continues to enhance its WebFOCUS product line and add new capabilitiesand tools in order to meet customer requirements. In recent years, this has meant applying newtechnologies to provide a rich, modern web-based experience for users of WebFOCUS. To thisend, in WebFOCUS 8, several legacy tools and interfaces, as well as some stabilized productoptions, are consolidated. The WebFOCUS 8 Tools Consolidation Statement is available from theInformation Builders InfoResponse Online website (https://techsupport.informationbuilders.com/).To provide advanced notice of the WebFOCUS 8 Tools Consolidation, a CTSS Advisory emailnotification was distributed on November 30, 2011 to InfoResponse Online subscribers.

The legacy web tools consolidation includes the retirement of the Report Assistant, GraphAssistant, Power Painter, and Advanced Graph Assistant tools. Information Builders has a generalpolicy of ensuring that our customers receive upgrades and new features as a standard part oftheir maintenance contracts. In this case, Information Builders is extending that program.Customers who have licensed Report Assistant and Graph Assistant under the Analytical Reporteror other licensing arrangements, upon upgrading to WebFOCUS 8 are entitled to trade thoselicenses in for no-cost InfoAssist Basic licenses. InfoAssist Basic, a subset of WebFOCUSInfoAssist, contains the capabilities found in Report Assistant and Graph Assistant. Contact yourlocal Information Builders representative regarding Power Painter and Advanced Graph Assistantcapabilities, which require the WebFOCUS InfoAssist license.

The web consolidation also includes the retirement of the following Java® applet-based interfacesand tools, which will eliminate the requirement to have a specific release of the Java VM presenton each end-user machine.

Managed Reporting (MR) Applet User Interface

Reporting Object Applet Tool

Alert Wizard Applet Tool

Publish Utility Applet Tool

Applet-based graphs, Graph Editor (accessible from applet-based graphs), and Old GraphEngine (GRAPH32)

ReportCaster Applet Interface and Scheduling Wizard

For Developer Studio, the Graph Assistant and the Managed Reporting Publish Utility are retired.The Developer Studio Graph option will utilize InfoAssist charting. The Developer Studio HTMLComposer tool is available to create HTML launch forms for Managed Reporting procedures.Customers who have active licenses for Developer Studio will receive this functionality as partof their standard maintenance contract.

6 WebFOCUS

Tools Consolidation

https://techsupport.informationbuilders.com/tech/wbf/wbf_rln_8_tools_consolidation.html

https://techsupport.informationbuilders.com/

The functionally stabilized product options that have been consolidated and discontinued as ofWebFOCUS 8 are:

WebFOCUS CGI and ISAPI client communication for WebFOCUS Self-Service applications.Applications using the CGI or ISAPI client should be converted to use the WebFOCUS Servlet.

Two-Way Email product offering is discontinued due to a lack of usage and the availability ofthe WebFOCUS Mobile Favorites Product offering.

ReportCaster Java Bean API is superseded by the ReportCaster Java API available as ofRelease 5.3. See the ReportCaster API manual for information on the ReportCaster Java API.

See the following product notifications for additional information for each of the consolidationareas including functionality available to evaluate in WebFOCUS 7.7.x, which is also availablefrom the WebFOCUS 8 Tools Consolidation Statement.

WebFOCUS 8 Managed Reporting Applet-based Tools Consolidation

WebFOCUS 8 Applet-based Graphs and Graph Engine Consolidation

WebFOCUS 8 ReportCaster Tools and Distribution Options Consolidation

WebFOCUS 8 Report and Graph Tools Consolidation

WebFOCUS CGI and ISAPI Client Depreciation and Support Statement

ReportCaster Two-Way Email Discontinued as of WebFOCUS 8

ReportCaster Java Bean API Discontinued as of WebFOCUS 8


WebFOCUS Upgrade Considerations Release 8.0 Version 10

https://techsupport.informationbuilders.com/tech/wbf/wbf_rln_8_mr_appletbased_tools_consolidation.html

https://techsupport.informationbuilders.com/tech/wbf/wbf_rln_8_appletbased_graph_consolidation.html

https://techsupport.informationbuilders.com/tech/wbf/wbf_rln_8_rcaster_tools_distoptions_consolidation.html

https://techsupport.informationbuilders.com/tech/wbf/wbf_rln_8_report_graph_tools_consolidation.html

https://techsupport.informationbuilders.com/tech/wbf/wbf_rln_77_cgiisapi_letter.html

https://techsupport.informationbuilders.com/tech/wbf/wbf_rln_8_rcaster_2wayemail_consolidation.html

https://techsupport.informationbuilders.com/tech/wbf/wbf_rln_8_rcaster_javabeanapi_consolidation.html

Installation and Configuration

The following are upgrade considerations for the installation and configuration of WebFOCUS:

The following directories are not created by the WebFOCUS Client when performing a fullinstallation:

ibi_html/template

ibi_html/publish

ibi_html/servletexec

The Service Pack installation will not remove these directories from the existing installation.

When configuring WebFOCUS Release 8.0 Version 04 and higher with WebLogic®, you mustperform the following post-installation step.

You must create a new file called weblogic.xml in the WEB-INF directory for the WebFOCUSweb application. It must contain the following information:

<?xml version="1.0" encoding="UTF-8"?> <wls:weblogic-web-app xmlns:wls="http://xmlns.oracle.com/weblogic/weblogic-web-app" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd http://xmlns.oracle.com/weblogic/weblogic-web-app

http://xmlns.oracle.com/weblogic/weblogic-web-app/1.4/weblogic-web-app.xsd"><wls:container-descriptor><wls:prefer-application-packages><wls:package-name>org.eclipse.persistence</wls:package-name></wls:prefer-application-packages></wls:container-descriptor></wls:weblogic-web-app>

Once the file is saved, you must recreate the .war file by adding it to webfocus.war. The .warfile can be renamed based on your naming convention, and then redeployed.

As of WebFOCUS Release 8.0 Version 01, the ibi_html alias has been removed from WebFOCUSpackaging. Application content located in the WebFOCUS Release 8.0 Version 01 or laterWebFOCUS Client ibi_html installation directory is by default accessed using the/ibi_apps/ibi_html alias path. If you are upgrading and ibi_html alias references exist in yourearlier applications as /ibi_html or a custom alias, see the WebFOCUS and ReportCasterInstallation and Configuration manual for your platform for information on how to manuallyconfigure the ibi_html soft alias for your application server.

8 WebFOCUS


The Run a Stored Procedure and Run an Ad Hoc Procedure pages, available from theWebFOCUS 7.7.x Welcome Page, are not available from the WebFOCUS 8 Welcome Page.Authorized users can run stored procedures and ad hoc requests from the WebFOCUS ReportingServer options, located under the Diagnostics, Verification section in the WebFOCUSAdministration Console.

WebFOCUS Release 8.0 Version 10 is packaged with a newer version of thejackson-all-1.9.11.jar file, which includes updated classes. To avoid conflicts with the currentversion of jackson-all-1.9.11.jar that is included and used by IBM WebSphere ApplicationServer Version 8.0 and 8.5, perform the following steps. These steps describe how to definea container-wide shared library that can be used by deployed WebFOCUS applications.

1. In the following directory, locate the jackson-all-1.9.11.jar file that is packaged withWebFOCUS:

ibi/WebFOCUS80/webapps/webfocus/WEB-INF/lib

2. Create an empty directory on your system and copy the jackson-all-1.9.11.jar file that ispackaged with WebFOCUS to this new directory. For example:

/appsrv1/IBM/shared

3. Log on to the WebSphere Integrated Solutions Console.

4. In the left pane, expand Environment and select Shared libraries, as shown in the followingimage.



The Shared Libraries pane opens, as shown in the following image.

5. Select a scope from the drop-down list, which specifies the level at which the resourcedefinition is visible, and click New.

10 WebFOCUS


The Shared Libraries > New pane opens, as shown in the following image.

6. In the Name field, enter a name for the new shared library that is being created (forexample, IBI Jackson 1.9).

7. Provide a description (optional).

8. In the Classpath field, enter the path to the folder on your system where you copied theupdated jackson-all-1.9.11.jar file (packaged with WebFOCUS).

9. In the Class Loading area, select the Use an isolated class loader for this shared librarycheck box.

10. Click OK, then click Apply.



Perform the following steps for each WebFOCUS web application, including when redeployed.

Note: Only the webfocus.war file for the WebFOCUS web application requires this change.The ibi_help.war, approot.war, and ibi_html.war files do not require the changes describedin this procedure.

1. In the left pane, expand Applications, and select WebSphere enterprise applications.

The Enterprise Applications pane opens, as shown in the following image.

2. Click the name of the webfocus.war file for the WebFOCUS web application (for example,15215webfocus_war).

12 WebFOCUS


In the References area, click Shared library references, as shown in the following image.

The Shared library references pane opens, as shown in the following image.

Note: The WebFOCUS Application being used in this example is called15215webfocus_war and the Module is called WebFOCUS 8.0.



3. Select the check box to the left of the WebFOCUS Application and click Reference sharedlibraries.

The Shared Library Mapping pane opens, as shown in the following image.

4. In the Available area, select the IBI Jackson 1.9 shared library, and then click the rightarrow icon.

The IBI Jackson 1.9 shared library is now listed in the Selected area.

5. Click OK.

6. Repeat steps 3 to 4 for the Module (for example, WebFOCUS 8.0) that is listed in theShared library references pane.

Ensure that the IBI Jackson 1.9 shared library for the Module is moved to the Selectedarea.

7. Click OK.

14 WebFOCUS


You are returned to the Shared library references pane, as shown in the following image.

Notice that the new shared library (IBI Jackson 1.9) is now listed in the Shared Librariescolumn for the Application and Module.

8. Click OK.

9. Restart your IBM WebSphere Application Server if it is already running.

Note: Restarting only the WebFOCUS application will not be sufficient.

Server Configuration

The following are upgrade considerations for the Version 7 Release 7.06 Server:

Disabling the CSRF Token When Connecting From a Release 8.0.x Client

The Version 7 Release 7.06 server supports a CSRF Token. This token is sent with each POSTrequest in order to prevent a Cross-Site Request Forgery attack. If you are using a Release 8.0.xWebFOCUS client that is supported with the 7.7.06/8.1.x server, you need to disable the CSRFtoken in order to successfully connect to the server’s HTTP Listener. You can disable the tokenfrom the server Workspace page.

1. Open the Special Services and Listeners folder.

2. Right-click TCP/HTTP, and select Properties of HTTP from the context menu.

The Listener Configuration page opens.



3. Open the security section of the page, and select zero (0) from the CSRF_TOKEN drop-downlist, as shown in the following image.

4. Click Save and Restart Server.

This adds the attribute CSRF_TOKEN = 0 to the HTTP listener block of the server odin.cfg file.

If you are connecting from a Release 8.1.x or higher client, the CSRF Token should be enabled.

Migration

The following are upgrade considerations for migration:

In WebFOCUS 8, the MR Repository Filter is no longer supported. You can use the WebFOCUS8 security rules to grant or deny access to content within the repository.

In WebFOCUS 8, to better support special characters, URLs are now stored as content witha type of URL. In previous versions of WebFOCUS, the URL was stored as the HREF.

16 WebFOCUS

Migration

InfoAssist

The following are upgrade considerations and product changes for InfoAssist:

As of WebFOCUS Release 8.0 Version 05, InfoAssist and InfoAssist Basic can be accessedwithin the same WebFOCUS configuration from the BI Portal when a WebFOCUS Client licensekey with InfoAssist and InfoAssist Basic is configured. If you are licensed for InfoAssist Basicand full InfoAssist, contact your local branch or Customer Support to obtain a WebFOCUS 8license key that includes both InfoAssist and Basic InfoAssist. The InfoAssist Basic productis available at no additional cost to customers upgrading to WebFOCUS 8 and have an activemaintenance agreement for Report Assistant and Graph Assistant through the AnalyticalReporter, Comprehensive User Services (CUS), or other licensing agreement that includesReport Assistant and Graph Assistant.

For information on the InfoAssist capabilities not included in InfoAssist Basic, see theWebFOCUS 8 Report and Graph Tools Consolidation statement. Access to InfoAssist andInfoAssist Basic within the BI Portal is authorized using WebFOCUS Client security privileges.For information on WebFOCUS Client security privileges, see the WebFOCUS Security andAdministration manual.

As of Release 8.0 Version 05, the default format for charts is HTML5.

In releases prior to Release 8.0 Version 05, you could specify an application theme inInfoAssist by clicking the Options button on the InfoAssist main menu. In Release 8.0 Version05 and higher, the application theme is retrieved from the BI Portal. Therefore, the ability tospecify an application theme in InfoAssist has been removed.

As of Release 8.0 Version 01, slicers cascade within a hierarchy (cube or dimensionbuilder-based), rather than in the order of user interaction, eliminating potential performanceissues.

When working with an SQL database and an alpha field is added to a Measure, the prefixbecomes MAX instead of CNT. This occurs because MAX is more efficient than CNT. You canchange the prefix using the Aggregation menu on the Field tab.

The Filter Values, Sort, and Visibility options have been removed from the right-click menu ofa Coordinated Field. These options still remain in the ribbon.

A new Use Default Stylesheet button has been added to the Select a Theme dialog box thatallows you to use the default style sheet. When you select this button, the dialog box willclose and the default style sheet will be used.



DOC, WP, WK1, DIF, and LOTUS formats are not supported. If you try to open a procedurewith one of these formats, an unsupported syntax warning message will display. If you chooseto continue, InfoAssist will convert the procedure to HTML format.

SUB-TOTAL syntax is not supported. If you try to open an existing procedure in InfoAssist froma legacy tool that contains SUB-TOTAL syntax, an unsupported syntax warning message willappear. If you choose to continue, InfoAssist will convert the syntax to SUBTOTAL and addthe converted syntax to all higher-level sort breaks.

SUMMARIZE syntax is not supported. If you try to open an existing procedure in InfoAssistfrom a legacy tool that contains SUMMARIZE syntax, an unsupported syntax warning messagewill appear. If you choose to continue, InfoAssist will convert the syntax to RECOMPUTE.

HTML FULL, FIXED, and PAGED syntax is not supported. If you try to open an existing procedurein InfoAssist from a legacy tool that contains any of these three options, an unsupportedsyntax warning message will appear. If you choose to continue, InfoAssist will convert theprocedure to regular HTML output.

COLUMN-TOTAL syntax is not supported. If you try to open an existing procedure in InfoAssistfrom a legacy tool that contains this syntax, an unsupported syntax warning message willappear. If you choose to continue, InfoAssist will convert the procedure to RECOMPUTE.

Line objects in a compound document imported from a legacy tool are not supported. If youtry to open an existing procedure that includes lines, an unsupported syntax message willappear. If you choose to continue, InfoAssist will remove the lines.

If you have a document with referenced procedures created by using Insert Existing Report,then the Data panel will be empty when the referenced procedure is the selected item on thecanvas.

When working with charts, nested X-axis text overlaps the legend area in the Interactive DesignView. However, this issue does not occur every time. This does not appear when you run thechart.

When creating a new chart procedure, the 3D effect option is no longer enabled by default.If you open an existing procedure that has the 3D effect option enabled, 3D effect will stillbe enabled.

18 WebFOCUS

InfoAssist

App Studio

The following is an upgrade consideration and product change for App Studio:

When using the Open File dialog box, the default option for displaying files has been changedfrom Show All Files in Associated Paths to Show Files in Selected Path Only. The causes theOpen File dialog box to only show the files in the folder you select, by default.

HTML Composer

The following are upgrade considerations and product changes for HTML Composer:

The Save as Thin-Client option, found in the HTML Composer File menu, which was used tocreate thin-client Visual Discovery pages, has been removed in favor of the new Visual DiscoveryAE product.

By default, form controls are shown in the template previews, shown in the Template selectordialog box. These form controls will not display when the template is opened in HTML Composerunless they are being used. For example, the form controls will display when you have variablesthat use them.

In order to use a theme but not use a template, you must select No, Thanks in the Templateselector dialog box. You can then select the theme you want using the Theme property. TheTheme property is a property of the DOCUMENT object.

For a Tab control, the default values for Edge color and Selected color are no longer displayedin the Properties window inline. Instead, they come from an external cascading style sheetfile.

When a graph is generated from an active report, using the Generate Graph right-click option,that graph is not shown as an active report in the Properties and Settings dialog box.

When using maps, the marker image will change to the selected marker image when thatmarker is clicked. When you click another marker, the previously selected marker will beunselected. You can press the Ctrl or Shift key while right-clicking your mouse to select multiplemarkers.

The Generate Graph and Add Filter right-click options are unavailable when using a guidedreport.

When using a Calendar, the Disable property disables both the edit box and the icon. Todisable only the edit box, use the Read only property.

The Google™ InfoWindow, used in prior releases with Google Maps™, has been replaced bya WebFOCUS generated InfoWindow.



When opening a Visual Discovery page created in a prior release, you will receive the followingwarning message:

The file was created prior to release 8 and contains Visual Discovery controls. They will not be migrated. You may exit Composer without saving, and the page will continue to run.

When pages that contain BW SAP data are migrated, a folder is created with the same nameas the domain folder from previous versions. For example, if in WebFOCUS 7.7.x your domainfolder was called user_domain, then in WebFOCUS 8 your folder name will still be user_domain,even though WebFOCUS 8 does not use domains. In order to run these migrated pages, youmust set the Reporting Server for the newly created folder. In this example, you would haveto set the Reporting Server for the user_domain folder.

The Tools menu has been removed. Options previously found in the Tools menu can be foundin the HTML Page tab, found in the Developer Studio Options dialog box. To apply settings tothe current layout, only use the Settings option in the File menu.

Any pages that have maps, that were created in previous versions, and are opened in HTMLComposer, will undergo a migration process. The migration will occur in memory. You mayexecute the page in the tool to verify execution. If you save the page, the migrated code willbe saved. If you exit the tool without saving, the migrated code will not be saved.

Document Composer

The following are upgrade considerations and product changes for Document Composer:

The live preview has been changed. If a component contains the -DEFAULT statement for itsparameters or variables, they will now be applied for the preview.

The Tools menu has been removed. Options previously found in the tools menu can be foundin the Document tab, found in the Developer Studio Options dialog box. To apply settings tothe current layout, only use the Settings option in the File menu.

Report Painter

The following are upgrade considerations and product changes for Report Painter:

When creating a report procedure where Measures and Dimensions are defined in the MasterFile, you must select the correct column type before dragging or double-clicking the field youwant to add. Dimensions can be either BY or Detail column types and Measures can be BY,SUM, or Detail column types. For example, if you double-click a Dimension when the SUMcolumn type is selected, the field will not be added to the report. You must change the columntype to BY or Detail and then double-click the field.

20 WebFOCUS

Document Composer

When creating a new report procedure, the default style sheet, or any of the PredefinedTemplate Files you use, are referenced instead of being copied into the repository folder. Ifyou want to copy the Predefined Template File instead of referencing it, select Copy insteadof Reference (selected by default) at the bottom of the Style File Selector Wizard, when in therepository area.

When a chart is generated from a report, the styling options of the report will be inherited bythe chart.

When browsing for an image using the Report Options Images tab, the image is directly addedto the list box instead of having to click the Add button.

Excel® 2007 and higher formatted reports will generate the XLSX format instead of the EXL07format in the syntax. This is so newer versions of Excel will not have 07 in the formatspecification.

The When and Insert Date options have been moved in the right-click menu of a subheading.These options are only available after Alignment Grid has been applied. The When option nowcomes after Cell Options. Insert Date can now only be accessed by right-clicking and selectingInsert Date from the Insert menu.

ReportCaster

The following are upgrade considerations and product changes for ReportCaster:

The Save On Demand Schedules for Job Duration option, which is specified in the DistributionServers folder, in the Configuration tool of the ReportCaster Console, is not functional.

In Release 7, the Report Library is separate from the repository tree. Because of this, a LibraryOnly user has access only to the Library and not the repository tree. In WebFOCUS 8, theReport Library is integrated into the repository tree. As a result, a migrated Library Only usercan see non-Library items that have been shared to everyone.

When entering a Reply Address in a schedule, the colon character (:) cannot be used. Inreleases prior to WebFOCUS 8, the use of this character was allowed. If a schedule with aReply Address containing a colon (:) is migrated to WebFOCUS 8, the schedule will fail whenexecuted on demand.



In WebFOCUS 8, the legacy ReportCaster API uses the ReportCaster and Library Contentfolders that are created by the migration process. If you have not migrated content toWebFOCUS 8 from an earlier release of WebFOCUS, then you must manually create theReportCaster folder in order to use the legacy ReportCaster API to create a schedule (unlessyou specify the full IBFS path in the Schedule description). The ReportCaster folder must becreated with the Auto Create My Content Folders property set. The Library Content folder orfolders created during migration are the default destinations for Library output from scheduledManaged Reporting procedures and Reporting Server procedures. These folders must existunless a full IBFS path is specified as the destination for Library output at schedule creationtime.

When a Library schedule has the access option Shared (Appears under Shared Content folder)and the Send Email after Report Saved to Library check box selected simultaneously,ReportCaster will only send email messages to the schedule owner.

As of WebFOCUS Release 8.0 Version 03, the DSTRUN subroutine is supported.

In WebFOCUS 8, an administrator can no longer globally update the Owner ID of ReportCastercontent because the content is integrated with IBFS security in the WebFOCUS Repository.

When the ReportCaster API is called to retrieve Category information, the Category Namereturned is the name of a folder. The Category ID returned is the full IBFS path to that folder.In earlier releases, if the Category name was the name of an MR Domain, the Category IDwas the href to that Domain. Otherwise, the Category ID was blank.

Charts scheduled in HTML format generate embedded images instead of references to applets.Therefore, charts can be distributed by any distribution method and are not limited to Librarydistribution.

ReportCaster is fully integrated with the WebFOCUS 8 Client security authorizationimplementation. Users, Groups, Schedules, Distribution Lists, Access Lists, and LibraryReports are stored in the WebFOCUS Repository. Any custom applications that reported directlyagainst the ReportCaster User and Group tables will need remediation to report against theWebFOCUS 8 Repository tables.

The Library Management tool has been removed and replaced with equivalent functionalityavailable in the ReportCaster Explorer in Manager mode.

You must be at a WebFOCUS 7.6.x or 7.7.x level to migrate your ReportCaster repository toWebFOCUS 8. If you are using an earlier release of WebFOCUS, contact Customer SupportServices for assistance.

22 WebFOCUS

ReportCaster

The Schedule option selected from an HTML Composer Page invokes the WebFOCUS 8 BasicScheduling tool. In prior releases, the Single Page Scheduling Tool was invoked. This hasbeen discontinued in WebFOCUS 8 due to the ReportCaster Scheduling tools consolidation,which replaces all prior scheduling tools with an intuitive ribbon-based implementation.

When the template for the HTML Composer Page Schedule button contains multiple distributionoptions, the user is prompted to select one of the options before accessing the Scheduletool, as shown in the following images:

In prior releases, the Single Page Scheduling tool was invoked directly and the Distributereport by field listed the distribution options available to the user to select.

The Public flag in Public Distribution lists has been removed. Users can now share DistributionLists with other users.

The Google Library Search has been desupported. The Magnify replacement is not yet available.

The Legacy ReportCaster API supports the management of Distribution and Access Lists, thescheduling of WebFOCUS Server procedures and WebFOCUS Repository procedures migratedfrom an earlier release, Library distribution and retrieval, Log management, and Consolefunctionality.



In WebFOCUS 8, the ReportCaster legacy API requires that the system propertyIBI_DOCUMENT_ROOT be set. It does not need to be an environment variable. ReportCasteruses IBI_DOCUMENT_ROOT to request that the IBFS security system provide the informationneeded to connect to the WebFOCUS Repository and obtain configuration information forinitialization.

In previous releases, this was accomplished by using the CasterManagedConnectionFactorymethods setServerName and setPortNumber to connect to the Distribution server. Thisconnection to the Distribution server for initialization has been replaced by the connectionto the IBFS security system using the system property IBI_DOCUMENT_ROOT.

The CasterManagedConnectionFactory methods setServerName and setPortNumber havebeen deprecated. Use of these methods has no effect in WebFOCUS 8.

For an example of setting the system property IBI_DOCUMENT_ROOT, see the setenv script(setenv.bat file on Windows), located in the ibi/WebFOCUS80/ReportCaster/Samples/Toolsdirectory.

Library Access Lists utilize the WebFOCUS Client Security sharing functionality to authorizegroups and users access to Library reports in WebFOCUS 8. As of WebFOCUS Release 8.0Version 01, Access List support of subgroups is available.

Users must be authorized to share Library reports with the groups and users specified in theAccess List for the library report to be shared with them when distributed to the WebFOCUSRepository. Changes to the Access Lists are applied at the next schedule execution. If theLibrary report access changes are required before the next schedule execution, they can bemanually applied by accessing the Library report from the resource tree in the BusinessIntelligence Portal (BI Portal), Dashboard, or ReportCaster Explorer and selecting the Shareor Share Advanced options. The resource tree sharing options are available to users who havebeen authorized to share library reports.

The Library Access option Public has been replaced with Share to Everyone. Share to Everyonemeans the report is available to all users who are authorized to List and View Library contentin the folder where the Library item resides.

The Library Access option Access List has been replaced with Share Advanced. Share Advancedmeans the report is shared at distribution time to the users and groups that are on the AccessList. If users or groups are added or removed from the Access List, the change is not effectiveuntil the next time the schedule is executed.

24 WebFOCUS

ReportCaster

Library Reports are now stored in folders in the WebFOCUS repository. The Category field isstill available and can be used to sort reports displayed in the ReportCaster Explorer. Thefolder that a Library report is stored in must exist at the time a schedule is created. A Libraryitem is added to the selected folder when the schedule executes for the first time. Subsequentversions are added to this item. The name of the item is the name of the schedule or, in thecase of a burst report, the burst value.

Running a schedule with traces is not yet implemented when selecting a schedule from thetree in BI Portal, Dashboard, or the ReportCaster Explorer. A schedule can be run with traceoptions from within the Basic or Advanced Scheduling tools.

In WebFOCUS 8, in order to retrieve a dynamic multi-select list using the Schedule tool, youmust click the Value button. In WebFOCUS 7.7.x, a Value button did not exist.

In a schedule, there are two new properties: Name and Title. Description, which is no longera property, has been replaced by Name. Title displays in the BIP tree by default, however,this can be changed to display the name. WebFOCUS 8 allows duplicate titles, but not duplicatenames.

Using the legacy ReportCaster API, you can create schedules with duplicate Titles, but theNames must be unique. The legacy ReportCaster API must be passed the unique Name whenrunning a schedule to ensure that the correct schedule is run.

WebFOCUS Infrastructure and Security

The following are upgrade considerations and product changes for WebFOCUS security:

The Version 7 Release 7.06 server supports a CSRF Token. This token is sent with each POSTrequest in order to prevent a Cross-Site Request Forgery attack. If you are using a Release8.0.x WebFOCUS Client that is supported with the 7.7.06/8.1.x server, you need to disablethe CSRF token in order to successfully connect to the server HTTP Listener. You can disablethe token from the server Workspace page.

1. Open the Special Services and Listeners folder.

2. Right-click TCP/HTTP, and select Properties of HTTP from the context menu.

The Listener Configuration page opens.

3. Open the security section of the page, and select zero (0) from the CSRF_TOKEN drop-downlist, as shown in the following image.



4. Click Save and Restart Server.

This adds the attribute CSRF_TOKEN = 0 to the HTTP listener block of the server odin.cfgfile.

If you are connecting from a Release 8.1.x or higher Client, the CSRF Token should be enabled.

Generally, Kerberos appends the Windows Domain of the user to the user ID passed toWebFOCUS, in the format [email protected]. As of Release 8.0 Version 09, by default,WebFOCUS strips the domain from the value, leaving just the user ID. The user ID is thenused to complete the sign-in process. To append the domain, change the stripDomainSuffixsetting to false in the kerberosPreference section of the securitysettings.xml file.

26 WebFOCUS


Selecting a hyperlink to drill down from within Microsoft Office products will fail, since theproducts are launched outside of the browser. The current security context and any previouslyestablished session-related cookies are not retained, changing the user authorization. Thedrill-down feature in Microsoft Office products functioned in WebFOCUS Release 7.7.x sinceanonymous drill-down access was permitted.

The following options are available to allow the feature in WebFOCUS Release 8.x:

Set up WebFOCUS security such that the PUBLIC user has the necessary permissions todrill down to reports.

Enable the Remember Me feature on the Sign-in page. If the end-user uses the RememberMe feature, a persistent cookie is used.

Use SSO with IIS/Tomcat Integrated Windows Authentication. Renegotiation occursautomatically and the Excel report displays correctly.

For more information on how Microsoft Office products work with session related information,see the Microsoft Office support site at http://support.microsoft.com/kb/218153.

In releases prior to WebFOCUS Release 8.0 Version 06, ipv6 using the tcnative-1.dll is disabled.In WebFOCUS Release 8.0 Version 06 and higher, the .dll that enables ipv6 is no longer used.

Due to its new and more flexible security model, WebFOCUS 8 no longer includes the ManagedReporting Realm Driver. Customers that used the Realm Driver should adopt one of thefollowing new approaches, depending on the scenario.

Trusted Authentication. Configure WebFOCUS for Pre-Authentication. For moreinformation, see the Authentication chapter in the WebFOCUS Security and Administrationmanual.

External Authentication to LDAP or Active Directory. Configure the Reporting ServerLDAP provider and then configure WebFOCUS to authenticate to the Reporting Server. Formore information, see the Authentication chapter in the WebFOCUS Security andAdministration manual.

External Authorization to LDAP or Active Directory. Configure the Reporting ServerLDAP provider and then configure WebFOCUS to authorize to the Reporting Server. Formore information, see the Authorization chapter in the WebFOCUS Security andAdministration manual.



External Authorization to RDBMS. Configure a custom security provider on the ReportingServer that reads the RDBMS data and then configure WebFOCUS to authorize to theReporting Server. For more information, and to download a sample WFSQL provider, goto:

https://techsupport.informationbuilders.com/tech/wbf/v8templates/wbf_8_server_custom_provider.html

Custom Plug-in. In WebFOCUS 8, custom authentication and authorization solutions canbe developed using the Reporting Server Custom security provider interface. The customsecurity logic is written in FOCUS and Dialogue Manager. If your business logic is in Java,you can reference this using the CALLJAVA feature. The custom provider can accesssecurity information from any source accessible to one of the Reporting Server dataadapters. For more information, see the Security chapter in the Server Administration forUNIX, Windows, OpenVMS, IBM i, and z/OS manual. You can also download a samplecustom provider, and modify it to suit your needs from the following website:


As of WebFOCUS Release 8.0 Version 02, LDAP and Active Directory authentication andauthorization is facilitated through the Reporting Server LDAP security provider and WebFOCUSis configured to authenticate and authorize users to the Reporting Server. Accordingly, theLDAP Interface page has been removed from the WebFOCUS Administration Console.

To provide time to transition to the new Server LDAP configuration, WebFOCUS still supportspreviously configured Client LDAP configurations. However, changes to the Client LDAP providerproperties must now be made manually through edits to webconfig.xml.

All customers are encouraged to move to the new Server LDAP configuration, which includesa number of enhancements over Client LDAP. For more information, see the New Featuresmanual and the Authentication and Authorization chapters in the WebFOCUS Security andAdministration manual.

The WebFOCUS 7.7.x and earlier Managed Reporting internal repository (/basedir) is notdistributed in WebFOCUS 8 as it is superseded by the WebFOCUS 8 Client and securityauthorization model. See the WebFOCUS New Features manual for information about theWebFOCUS Client Security and Authorization Model and the Migration documentation forinformation on migrating Managed Reporting content from WebFOCUS 7.x.

28 WebFOCUS






In WebFOCUS 8, the WF_Role_RunOnlyUser can:

Create and save reports created from a Reporting Object.

Create a My Content Folder.

In WebFOCUS 7.x, a RunOnlyUser could not save reports from a Reporting Object, but couldsave parameterized reports, if given the saveparmreport privilege.

For improved performance in WebFOCUS, by default, a ResponseHeaderFilter has beenimplemented. This enables caching of static content that is sent to the browser from theWebFOCUS application context. The settings for this filter are established in the web.xml filefor the web application and are always enabled by default. Below are the default andrecommended parameters that are used. You can modify these parameters for individualimplementation requirements.

<context-param> <param-name>ResponseHeaderFilter.enabled</param-name> <param-value>true</param-value></context-param>

<context-param> <param-name>ResponseHeaderFilter.Cache-Control</param-name> <param-value>public, max-age=259200</param-value> </context-param>

<context-param> <param-name>ResponseHeaderFilter.expires</param-name> <param-value>259200</param-value> </context-param>

The ResponseHeaderFilter sets the Cache-Control header to public, max-age=259200, andthe expires header to a value of 259200 seconds or 30 days for the following extension types,served by the WebFOCUS web application.

<filter-mapping> <filter-name>ResponseHeaderFilter</filter-name> <url-pattern>*.htm</url-pattern></filter-mapping>

<filter-mapping> <filter-name>ResponseHeaderFilter</filter-name> <url-pattern>*.html</url-pattern></filter-mapping>

<filter-mapping> <filter-name>ResponseHeaderFilter</filter-name> <url-pattern>*.css</url-pattern></filter-mapping>

<filter-mapping> <filter-name>ResponseHeaderFilter</filter-name> <url-pattern>*.gif</url-pattern></filter-mapping>

<filter-mapping> <filter-name>ResponseHeaderFilter</filter-name> <url-pattern>*.png</url-pattern></filter-mapping>

<filter-mapping> <filter-name>ResponseHeaderFilter</filter-name> <url-pattern>*.jpeg</url-pattern></filter-mapping>

<filter-mapping> <filter-name>ResponseHeaderFilter</filter-name> <url-pattern>*.jpg</url-pattern></filter-mapping>

<filter-mapping> <filter-name>ResponseHeaderFilter</filter-name> <url-pattern>*.txt</url-pattern></filter-mapping>

The net effect is that if you are upgrading a WebFOCUS web application, all cache will needto be cleared, so that you obtain the latest version of the software. This includes the browsercache, and any caching servers in the environment.

30 WebFOCUS


Using Internet Explorer® 9, there is an additional option of Preserve Favorites website data,as shown in the following image, which should remain unchecked when clearing that versionof the browser cache.

WebFOCUS Operating Environments

The following is an upgrade consideration and product change for WebFOCUS operatingenvironments:

The i5 environment now supports 64-bit packed arithmetic with a resulting performanceenhancement when using long packed numbers.



Managed Reporting

The following items are upgrade considerations and product changes for Managed Reporting:

As of WebFOCUS Release 8.0 Version 07, if Auto Prompting is enabled when the Prompt forParameters property is unchecked, you will still be prompted if there are any parameters thatdo not have a value supplied. This applies to running procedures (FEX) stored in the WebFOCUSRepository Content folder path.

In Release 8.0 Version 10, the WebFOCUS Client AutoPrompting IBIMR_promptingUnsetsetting is available to enable or disable parameter prompting for Managed Reporting procedures(FEXes) when IBIMR_prompting is set to XMLPROMPT or XMLRUN, and the Prompt forParameters setting is unchecked in the FEX Properties dialog box.

As of WebFOCUS Release 8.0 Version 02, the Managed Reporting Deferred Ticket CleanupUtility is supported. Due to WebFOCUS 8 architecture changes, this utility only processes therepository defined in the WebFOCUS Client configuration for which it is being run.

As of WebFOCUS 8, the WebFOCUS Client processing of Managed Reporting requests appliesstricter rules to referenced files. When a referenced file is not located in the WebFOCUSRepository IBFS path, a Resource not found error is displayed. Therefore, all referenced fileslocated on the Reporting Server must have:

-MRNOEDIT at the beginning of the line.

or

Replace the name with the fully qualified IBFS path to the file located on the ReportingServer.

This includes evaluating StyleSheet file (STY) references and procedure (FOCEXEC=filename)references. For example, a Resource not found error will be displayed if the StyleSheet fileSTHS001, referenced in the following command in a Managed Reporting procedure, is locatedon the Reporting Server:

ON TABLE SET STYLE STHS0001

The correct coding of this reference for the STHS001.sty file, located on the EDASERVEReporting Server, is either:

-MRNOEDIT ON TABLE SET STYLE STHS001

or

ON TABLE SET STYLE IBFS:/EDA/EDASERVE/STHS001.STY

32 WebFOCUS

Managed Reporting

Business Intelligence Dashboard

The following are upgrade considerations and product changes for Business IntelligenceDashboard:

When a WebFOCUS 8 Reporting Server is configured with external security, for example, LDAP,in order to access WebFOCUS you have to enter credentials, after which you are already loggedin as an authenticated user. This is a difference in behavior from WebFOCUS 7.7.x, wherepublic views could be seen before entering Dashboard.

In WebFOCUS 8, the Business Intelligence Dashboard Change Management utility is onlyaccessible from View Builder.

Public user authorization in a Public view is based on user permissions. In WebFOCUS 8, thePublic ID is migrated and automatically assigned the WF_Role_Public permission set. Analternate user ID designated as the Public user needs to be assigned the WF_Role_Publicpermission set.

Prior to WebFOCUS 8, the Business Intelligence Dashboard Login page was accessed usingthe following URL:

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

In WebFOCUS 8, the Business Intelligence Dashboard Login page is accessed using thefollowing URL:

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

The user ID defined as the Anonymous User is used to authenticate and access Public Views.By default, it is set to the Public user ID. Dashboard will issue Anonymous sign-on requestswhen a public page is opened.

The Public User is a named user and its user ID can be used to log in to WebFOCUS as anauthenticated user.

The Public User ID and Password is no longer required to be changed in View Builder. TheUser ID and Password will need to be changed from the Security Center, along withmodifications to the IBI_Anonymous_User parameter located in the Configuration, ApplicationSettings, Security section in the WebFOCUS Administration Console. For more information onthe Anonymous user, see the WebFOCUS Security and Administration manual.

Setting a Server User ID and Password for the Public User will no longer be configured in ViewBuilder. Instead, the IBI_Anonymous_WFRS_User and IBI_Anonymous_WFRS_Pass parametervalues need to be modified from the Configuration, Application Settings, Security section inthe WebFOCUS Administration Console. For more information on the Anonymous user, seethe WebFOCUS Security and Administration manual.



The Role Tree has been discontinued. The new security model will allow for similar functionalitywithin a List block.

The Dashboard Editor has limited functionality.

Favorites and Mobile Favorites content will now be stored in the database repository and notin the user favorites.xml file on disk.

The Tree and Content Block colors cannot be customized from View Builder.

Personalize Options has been discontinued.

Scroll button scrolling options are no longer available for the Tree and different block types.Scroll bars will be enabled, by default.

The USER_MAX_INACTIVE and the PUBLIC_MAX_INACTIVE idle limit parameters have beenremoved. It is recommended to set the global session timeout parameter found in the webapplication web.xml file.

The Publish report feature has been discontinued.

The Content Search Date Range feature and Search Preferences are not available.

A migrated Library Only user is not able to sign into the Library View. Instead, the user issigned into the Group View.

WebFOCUS Visual Discovery

The following are upgrade considerations and product changes for WebFOCUS Visual Discovery(Thick Client):

In WebFOCUS 8, HTML Composer does not support opening VisDis.htm files developed priorto WebFOCUS 8. WebFOCUS 7.x Visual Discovery applications are supported with WebFOCUS8 for run time.

Thin Client is not supported.

Visual Discovery is no longer opened through the ActiveX control button on the componentstoolbar. To open Visual Discovery from HTML Composer, click the Vis button on the componentstoolbar.

34 WebFOCUS

WebFOCUS Visual Discovery

In WebFOCUS 8, you select a Data Pool and access Visual Discovery control settings througha new Properties and Settings dialog box. When you insert a new Visual Discovery controlonto an HTML page, the Properties and Settings dialog box opens. If the Properties andSettings dialog box does not open automatically, or it does not appear when you select anexisting control, click Properties and Settings from the View menu. For more information, seethe Using WebFOCUS Visual Discovery to Develop Analytic Dashboards manual.

The <PARAM NAME="Files"> value no longer displays the table name used by the chart controlin the .htm code. This information is contained in other sections of the code and should onlybe edited using HTML Composer.

WebFOCUS Visual Discovery Analyst Edition

New tracks for WebFOCUS Visual Discovery Analyst Edition (AE) require fresh installations. As aresult, any previous versions of WebFOCUS Visual Discovery AE must be completely uninstalled.

Note: The WebFOCUS Visual Discovery AE installer does not prevent an upgrade existinginstallation option from being selected. As a result, unsupported issues can occur.

The following are important considerations:

On the system where WebFOCUS Visual Discovery AE Server is installed, navigate to Programand Features from the Control Panel. Click Turn Windows features on or off. The WindowsFeatures dialog box opens, as shown in the following image.



Expand Internet Information Services, Web Management Tools, and ensure IIS ManagementScripts and Tools is selected. Click OK.

If this option is not set, then an error message indicating Could not load file or assembly or asimilar error message may be displayed.

When publishing a project using WebFOCUS Visual Discovery Workbench AE, the Embed Datacheck box is no longer selected by default in the Publish Dashboard dialog box. It isrecommended to select the Embed Data check box only as required. If you are republishingexisting projects where the Embed Data check box was originally selected, you must selectthis option manually in the Publish Dashboard dialog box.

Data Sheet default for Coloring Mode is set to Use Foreground Color. To include the DataSheet in color by associations, change this property to Color By Data.

Active Technologies

The following are upgrade considerations and product changes for Active Technologies (WebFOCUSReporting Server Release 7.7 Version 05).

Version Requirements

The following version of software is required.

In order to run a report created with the active report for Adobe Flash® Player (FLEX) format,Adobe Flash Player 10.2.159.1 or higher is required to render Active Flash content.

In order to run a report created with the active report for PDF (APDF) format, Adobe Reader®

9.4.5 or higher is required so that the Adobe Flash Player run-time code included in the Readercan render the SWF files that are Adobe Flash Player compatible.

Starting with WebFOCUS Reporting Server Release 7.7 Version 04, Active Technologies requireInternet Explorer 8 or higher.

License Requirements

Starting with WebFOCUS Reporting Server Release 7.7 Version 04, you no longer need a validlicense for Adobe Flex Builder™ 3 Professional in order to render charts in active report for AdobeFlash Player output.

SET HTMLENCODE Command

Starting with WebFOCUS Reporting Server Release 7.7 Version 04, the behavior of the SETHTMLENCODE command has changed.

36 WebFOCUS

Active Technologies

SET HTMLENCODE=ON removes the data value that is displayed on top of a cell menu when youclick a data value in a cell. This is the default behavior for WebFOCUS Reporting Server Release7.7 Version 04 and higher, regardless of the HTMLENCODE setting.

SET HTMLENCODE=OFF retains the data value that is displayed on top of a cell menu when youclick a data value in a cell. This is the default behavior for WebFOCUS Reporting Server Release7.7 Version 03 and lower, regardless of the HTMLENCODE setting.

Handling a Hidden BY Column on an Active Technologies Chart

The SET ARNOPRINTHIDE command enables you to specify how the server handles a hidden BYcolumn when NOPRINT is used in a GRAPH request.

This command applies when the setting for the chart engine is JSCHART.

How to Handle a Hidden BY Column on an Active Technologies ChartSyntax:

The syntax is

SET ARNOPRINTHIDE = {ON|OFF}

where:

ON

Excludes a hidden BY column (BY column with the NOPRINT option) from the sort processingof an active chart. Data for the hidden BY column is not displayed in the active chart output.This is the default value.

Using this setting with a NOPRINT column produces the same result as using HIDE=ON syntaxfor the BY column in the procedure.

The data for a hidden BY column is available for use elsewhere. For example, you can useit to populate the global filter drop-down list or other filter control on an active dashboard.

OFF

Includes a hidden BY column (BY column with the NOPRINT option) in the sort processing ofan active chart. The chart is sorted by all the hidden BY columns, and data from all thecolumns is displayed in the active chart output.

Saving an Active Technologies Report

The following upgrade considerations apply when you save an active report from your browserFile menu, using the Save Page As option. For example, in Internet Explorer, you can select Saveas from the File menu, and in the Save as type drop-down list, select Webpage, HTML only.



As of WebFOCUS Release 8.0 Version 01, if you have included the command SET AROUTPUT= EXTJS in the profile or in a WebFOCUS procedure that generates an active report or document,you cannot use the browser Save as option to save the active report or document. Make sureto change the command to SET AROUTPUT = ALL to allow users to save the report or documentwith the browser Save as option. For more information on the SET AROUTPUT command, seethe Active Technologies User's Guide.

As of WebFOCUS Release 8.0 Version 02, make sure that the IBIF_active_extjs parameter isset to NO in the WebFOCUS Administration Console to use an active report or document(format AHTML) in a fully disconnected mode that supports the browser Save as option. Youcan find this parameter in the General category of Client Settings in the Configuration menuof the WebFOCUS Administration Console. For details on this parameter, see the WebFOCUSSecurity and Administration manual. Alternatively, you can add the command SET AROUTPUT= ALL to the WebFOCUS procedure that generates the active report or document.

Using an Alternate Adobe Flex Compiler With the WebFOCUS Reporting Server

An active report for Adobe Flash Player is generated using a Java-based compiler that comes withthe Adobe Open Source Flex® SDK. The SDK is installed on the WebFOCUS Reporting Server andused to create an active report for Adobe Flash Player. As of WebFOCUS Reporting Server Release7.7 Version 04, the compiler has been upgraded to Flex 4.5.1.

Active Technologies provide backward compatibility, enabling you to use earlier SDKs to compileyour existing interactive PDF and Flex documents with active reports for Adobe Flash Player. Youcan run an earlier version of the compiler, such as the compiler that comes with the Adobe OpenSource Flex SDK 3.5, with WebFOCUS Reporting Server Release 7.7 Version 04 and higher.

If you are using the interactive PDF feature, make sure to copy the necessary WebFOCUS Enablefor Adobe Flex SWC files to the \frameworks\libs directory of your Flex SDK installation. For moreinformation, see the WebFOCUS Enable for Adobe Flex 4.x User's Guide.

How to Use an Alternate Adobe Flex Compiler With the WebFOCUS Reporting ServerProcedure:

1. Download the Adobe Flex SDK. Previous releases produced by Adobe, including 3.5, areavailable at the Adobe SourceForge site.

2. To install a copy of the SDK on your system, extract the ZIP file to your drive.

3. In the WebFOCUS procedure that contains SET HTMLFORMTYPE=FLEX to generate theinteractive PDF or Flex document with an active report for Adobe Flash Player, add the followingcommand

SET FLEXSDK = path_to_sdk

38 WebFOCUS

Active Technologies

where:

path_to_sdk

Is the full path to the SDK whose compiler you want to use to generate the interactivePDF or Flex document with the active report for Adobe Flash Player.

Setting the Maximum Java Heap Size When Using an Alternate Adobe Flex Compiler

If you are using the SET FLEXSDK command, as described in Using an Alternate Adobe FlexCompiler With the WebFOCUS Reporting Server on page 38, you can also use the SET FLEXMEMcommand to specify the maximum Java heap size allocated to the Flex compiler to compile Flashor Flex files. If there is not enough available memory allocated to the Flex compiler at compilationtime, errors may occur.

By default, the maximum Java heap size is typically set to 384m (megabytes) in a script filenamed mxmlc, in a variable named $VMARGS. The mxmlc file resides in the Flex SDK \bindirectory installed on your system.

How to Set the Maximum Java Heap Size When Using an Alternate Adobe FlexCompiler

Syntax:

In the WebFOCUS procedure that contains the SET FLEXSDK command, add the following

SET FLEXMEM = maximum_java_heap_size

where:

maximum_java_heap_size

Is the maximum Java heap size allocated to the Flex compiler to compile Flash or Flex files.For example, the command

SET FLEXMEM = 640m

increases the maximum Java heap size from the default value (384 megabytes) to 640megabytes.

Customizing Styles With JavaScript Files

If a JavaScript file, such as irpfsty.js, irpstd.js, or irpfstd.js, was created prior to WebFOCUSReporting Server Release 7.7 Version 04 and resides in your application folder, you must removeit and move the custom contents into the corresponding irpcusf.js file for AHTML, irpuflex.js filefor FLEX/APDF, or irpcfgu.js file for all the default styles.



Setting the Initial Active Technologies Chart Size

When you create an active chart using GRAPH FILE syntax, GRAPH FILE automatically sets theinitial chart size to 768 x 480 pixels, by default. This feature applies to all chart engines.

Developer Studio

The following section provides information on new behavior in Developer Studio. It also includesupgrade considerations and product changes for Developer Studio.

Developer Studio New Behavior

Connection to WebFOCUS is performed at the WebFOCUS Environment level. Based on privileges,users will be able to work with areas to which they have been given access, for example, DataServers, Web Applications, and Repository.

The Repository area allows you to use Developer Studio to administer and develop against aManaged Reporting environment.

Under the Repository, folders can be created to develop Managed Reporting content.

For example, users can develop procedures or web applications, create ad hoc reports, and buildcustom user content. Development and Administration options are enabled based on userprivileges defined in the Security System.

Credentials can be saved in the environment properties to avoid reprompting. Saved credentialsare encrypted for security.

40 WebFOCUS

Developer Studio

To change or remove stored credentials, open the WebFOCUS Environment Properties dialog boxand click the WebFOCUS object to make the required changes.

Note:

The Repository area is not visible for Developer Studio standalone installations. TheRepository is installed only with WebFOCUS.

The Logoff option available at the environment level is applicable to all areas of theenvironment.

Logoff is also available in the Data Servers area for the configured Reporting Servers.Logoff at this level will be applied to the selected Reporting Server.



Connecting to WebFOCUS

To connect to a WebFOCUS environment (local or remote) or to the local WebFOCUS Client thatis included with Developer Studio, a connection to WebFOCUS is required.

For Developer Studio standalone configurations (no WebFOCUS on the same machine), the productis configured to use the user ID wfdesktop to connect to its local WebFOCUS Client. This user IDis automatically stored in the localhost environment properties.

When Developer Studio connects to WebFOCUS, a logon screen displays, prompting you to enterthe user name and password. The Logon dialog box has the user ID wfdesktop already enteredas a default user name, as shown in the following image.

The user ID wfdesktop, without a password, allows full development against Developer Studio.The user ID admin, with a password of admin, provides administrative tasks, such as access tothe WebFOCUS Administration Console and the Security Center.

If you have WebFOCUS installed on your local PC as well, the connection will be performed againstthe WebFOCUS configuration.

Derby Security database. A Derby database is installed with Developer Studio editions thatallow local, standalone development. It is used to store user accounts and policies required forDeveloper Studio to connect to its local WebFOCUS Client. The Derby database comes preloadedwith user IDs that have developer and administration permissions.

The Security Center that is available with Developer Studio provides the capability to change userpasswords. Other tasks, such as creation or removal of existing user IDs and operations, arenot permitted.

The embedded Derby database runs as part of the ibi_apps web application.

42 WebFOCUS

Developer Studio

The Derby database that is optionally installed with WebFOCUS runs as a service and will notinterfere with the Developer Studio Derby database if both products are installed on the samemachine.

WebFOCUS Environment Properties

As of Developer Studio Release 8.0 Version 01, the WebFOCUS Environment Properties dialogbox has changed, as shown in the following image.

When you configure a WebFOCUS Environment in Developer Studio, you must set the HTML Aliasto:

/ibi_apps/ibi_html



where:

ibi_apps

Is the name of the ibi_apps alias configured with WebFOCUS or Developer Studio. This aliascan be customized.

ibi_html

Is constant.

An ibi_html alias may be required if you have created applications from a previous DeveloperStudio release that contains hard coded references to the ibi_html alias. For these cases, youneed to set the HTML Alias as /ibi_html. For more information on how to configure this alias,see the Developer Studio Installation and Configuration manual.

In addition, you must set the Client Path to:

/ibi_apps/WFServlet

where:

ibi_apps

Is customizable, and requires that you type the same value as in the HTML Alias field.

Note: You can no longer modify the Client Path in the WebFOCUS properties area.

For more information, see the Developer Studio Application Development Getting Started manual.

How to Change a User Password in the Developer Studio Security DatabaseProcedure:

1. Assuming that you are using a default configuration of Tomcat with port 8080 and alias ofibi_apps, open the WebFOCUS Welcome Page using http://localhost:8080/ibi_apps/.

2. Sign in with the user ID for which you want to change the password, for example, wfdesktop.

3. Click the description of the user that displays in the upper-right pane after you sign in.

44 WebFOCUS

Developer Studio

For example, click on Developer Studio guest account and select Change Password, as shownin the following image.

The Change Password dialog box appears, as shown in the following image.

Enter the password information and click OK.



How to Change a User Password Through the Security CenterProcedure:

Users have access to the Security Center if they sign in using an Administrator account, such asadmin.

1. Select Security Center in the Administration drop-down menu, as shown in the followingimage.

2. From the Security Center, the administrator can change the password of any user byright-clicking a user and selecting Set Password, as shown in the following image.

46 WebFOCUS

Developer Studio

Developing Content in the Repository

To work against WebFOCUS 8 and develop content in the Repository, the security system needsto be updated.

The user ID admin can perform development and has full access to the Repository. User IDwfdesktop can perform self-service development work in the Projects, Data Servers, and WebApplications areas.

The WebFOCUS Security Center can be customized to add new users and allow developmentfrom Developer Studio:

Create new users or use existing users and assign them to a group that has the requiredDeveloper Studio privileges.

To connect to WebFOCUS from Developer Studio, users are required to have the privilegeDesktop Connect (privilege name opDTConnect). This privilege is included, by default, in theexisting rule, WF_DesktopConnect.

Developers will need privileges, such as create item, run, delete, and so on. These privilegesare available in the existing rule (WF_Role_Developer).

New Roles can be created and customized to control tools and operations developers are permittedto use. For example, allow the use of specific Developer Studio tools, such as Report Painter,the Join Tool, and the SET Tool, and exclude options, such as the Text Editor. Users can also belimited in the actions they can perform, for example, allow users to run requests immediately,but not give the option to run as deferred or allow publishing of an item.



How to Update the Security Center to Allow Development Against the RepositoryProcedure:

1. Connect to the Business Intelligence Portal using an administrator ID, such as admin.

2. Right-click Content (this is the descriptive name of Repository), point to Security, and thenRules, as shown in the following image.

48 WebFOCUS

Developer Studio

3. In the Security Rules dialog box, clear the Only show Groups with Rules check box.

4. Under Groups, the Developers and SelfServiceDevelopers groups allow development, andconnection to WebFOCUS from Developer Studio. The Developers group does not containany users, by default. You can create new users and add them to this group to allowdevelopment in the Repository.

The Developers group has the WF_DesktopConnect and WF_Role_Developer rules applied.

The SelfServiceDevelopers group has a user ID wfdesktop with no password assigned, bydefault. This group has privileges that allow development in the Projects, Data Servers, andWeb Applications areas. Users from this group can see the Repository area and can accesscontent available to anonymous users, such as the Public folder, but cannot create content.

The SelfServiceDevelopers group has the WF_DesktopConnect rule applied.



Users can be added to both groups, Developers and SelfServiceDevelopers, to allowdevelopment in all areas of Developer Studio.

5. As an example of creating user IDs and applying them to the Developers group, selectAdministration, then Security Center from the main toolbar.

6. Click New User and assign new users to the required group (the Developers group, in thiscase).

The following image shows an example of creating a new user.

50 WebFOCUS

Developer Studio

How to Restrict or Allow Access to the Data Servers AreaProcedure:

To allow access to the Data Servers area for a group, such as the Developers Group, performthe following steps:

1. Right-click Content, point to View, then click Full View, as shown in the following image.

The view will change, as shown in the following image.

2. Right-click EDA, point to Security, and then Rules.

The Security Rules dialog box opens.



3. Clear the Only Show Groups with Rules check box.

4. Select the Developers group.

5. Click the List rule in the lower part of the window that displays the rules for the selectedgroup.

6. Select Permitted from the Access column drop-down list.

7. Click Apply and then OK to close the dialog box and save the changes.

The Data Servers area will now display, when connecting from Developer Studio to thisenvironment, with any user that belongs to the Developers group.

To restrict permission, you need to select Deny from the Access column drop-down list forthe permission you want to remove.

The same steps can be applied to restrict or enable access to the Web Applications area byfollowing the same steps and selecting the WEB component, instead of EDA.

52 WebFOCUS

Developer Studio

Note:

Developer Studio Release 8.0 Version 10 is recommended to be used with WebFOCUSRelease 8.0 Version 10. Developer Studio cannot connect to WebFOCUS Release 8.0Version 01 or WebFOCUS 7.x environments, and development against such environmentsis not supported.

If you have an earlier release of Developer Studio, it is recommended that you uninstallthe earlier version prior to installing WebFOCUS Release 8.0 Version 10. You can alsoupgrade the earlier release to WebFOCUS Release 8.0 Version 10. Existing applicationsand configured environments will not be impacted.

For single sign on (SSO) security systems, such as SiteMinder, to avoid issues with sessiontimeouts, it is recommended that you set your application server with a long sessiontimeout period. The default setting for some application servers is between 20 and 30minutes, but this may be too low for some developers. WebFOCUS is configured, by default,with a session timeout of 120 minutes.

If a session timeout occurs, the developer will not be able to continue working againstWebFOCUS. At this point, if a manual refresh is performed using menu View/Refresh orpressing F5, the WebFOCUS Environments area will be refreshed. Only the Repository areawill display and the user will be switched to the Anonymous user, which does not have anydeveloper privileges.

To continue working, the developer must perform a logoff at the environment level and signin using a proper user ID.

For non-SSO configured environments, Developer Studio will reconnect silently when itreceives a message that a session timeout occurred. This will allow developers to continuedevelopment without having to sign out and sign in again.

For security purposes, many application servers are configured to transmit HttpOnly sessionID cookies to mitigate the risk of common cross-site scripting (XSS) attacks.

Use of Internet Explorer® 8 or later is required to ensure that requests run properly if theapplication server is configured for HttpOnly.

Creating content has differences between Developer Studio and the Business IntelligencePortal.

Developer Studio prompts for the Name of the item. Creating content in the BusinessIntelligence Portal prompts for the Title of the item.



Developer Studio Upgrade Considerations and Product Changes

The following are upgrade considerations and product changes for Developer Studio 8:

In the WebFOCUS Administration Console, the default Google Maps API version has beenchanged from 2 to 3. This is to reflect the most recent version of the Google Maps API.

In the WebFOCUS Environments Properties dialog box, the Managed Reporting/ReportCasterbutton is no longer available because this option is not valid when connecting to a WebFOCUS8 environment. There is no separate logon for Managed Reporting or ReportCaster. Instead,there is a single logon for WebFOCUS. Based on privileges, users will be able to work withinthe areas they can access. This applies to Managed Reporting content and ReportCasteroptions. You can store WebFOCUS credentials in the WebFOCUS Environment Propertiesdialog box by clicking the WebFOCUS button.

When connecting to WebFOCUS and prompted to log on, the User Name field is no longerpopulated with the user ID wfdesktop. The User Name field is now blank to allow the developerto enter any valid user ID for their environment. The user ID wfdesktop is still available in theproduct and allows self-service development in the Projects, Data Servers, and Web Applicationsareas. Access to the Repository is restricted and users cannot create new content with thisuser ID.

When upgrading from an earlier release of Developer Studio, such as Release 8.0 Version01 to Release 8.0 Version 10, you must update the localhost environment to ensure theHTML Alias is configured accordingly (/ibi_apps/ibi_html). The same applies for configuredWebFOCUS environments that have also been upgraded to Release 8.0 Version 10.

If you select the installation option, to configure Tomcat or IIS, the configuration of the HTMLAlias is based on the WebFOCUS Release 8.0 Version 05 implementation.

When opening an Alert procedure created in an earlier release, the Alert procedure (.fex),must be updated to a fully qualified WebFOCUS 8 path.

To update the Alert path:

1. Expand the Repository folder.

2. Right-click the Alert procedure that contains the -INCLUDE procedure for the Alert report,and select Edit in Alert Wizard.

The Alert Wizard opens.

3. Click Next until the Alert Wizard, Select a Report dialog box opens.

54 WebFOCUS

Developer Studio

4. Verify that the selected Alert is highlighted, and click Save.

Note: The Save button appears the first time you open an existing Alert procedure inthe Alert Wizard. When you reopen a migrated Alert procedure in the Alert Wizard, thisSave button is replaced by the Next button.

The Alert Wizard, Finish dialog box opens.

5. Click Finish.

As of Developer Studio Release 8.0 Version 06, sample files have been removed from theibidemo folder, under the apps directory that is created during the installation program. Thesesample files include the IBI Demonstration project (.gfa) and various procedure, HTML, andimage files. If you perform an upgrade installation, these files will still exist in your directory,and you are able to use them as templates for your applications. However, these files will nolonger be supported because of issues that occur at run time.

As of Release 8.0 Version 05, Developer Studio will not display a sign-in dialog box for oneminute after a user cancels out of the dialog box to enter WebFOCUS credentials. This is toprevent multiple sign-in prompts for a WebFOCUS environment. If a user needs to reconnectto the WebFOCUS environment for which they canceled the connection, they need to wait oneminute.


The following are upgrade considerations and product changes for WebFOCUS charts and graphs:

In WebFOCUS 8, HTML5 graph output replaces the applet-based graphs supported in priorreleases. The following graph parameter settings are no longer supported. If they are present,they will be ignored:

SET GRAPHENGINE = {GRAPH32|OLD}SET GRAPPLET ONLY=ON SET GRAPHEDIT=OFF SET GRAPHEDIT=ON ON GRAPH SET GRAPPLETONLY ON ON GRAPH SET GRAPHEDIT OFF ON GRAPH SET GRAPHEDIT ON ON GRAPH SET GRAPHENGINE {GRAPH32|OLD}ON TABLE SET GRAPPLETONLY ON ON TABLE SET GRAPHEDIT OFF ON TABLE SET GRAPHEDIT ON



HTML5 New Features and Upgrades

This topic lists HTML5 new features and upgrades.

Two new marker shapes are available. The marker shape, circlePlus, displays a circle with aplus sign (+) centered in it. The marker shape, circleMinus, displays a circle with a minussign (-) centered in it.

The SET CURRSYMB command, which specifies a currency symbol to be displayed with currencyvalues whose format specifications include the M or N display options, is now supported forall output formats, except AHTML, APDF, and AFLEX.

Using the JSCHART property, chart.dataLabels.UseNegativeColor, you can apply a differentcolor to data labels for negative values than the color used for positive values. The color usedwill be the one defined by the chart.colorMode.negColor property. You can insert thechart.dataLabels.UseNegativeColor property into the chart by issuing thesetUseNegativeDataTextColor(true) API call.

Differences Between HTML5 Charts and Server-Generated Charts

This topic lists known differences between HTML5 charts and the legacy server-generated charts.

The HTML5 chart engine, which is also used by AHTML, APDF, and AFLEX formats, uses adifferent algorithm for formatting datatext for risers than the legacy chart engine. The HTML5automatic numeric formatting determines whether the datatext for risers displays decimalplaces, and if so, how many. Values under 10000 get decimal precision, so that 22.8 isdisplayed as 22.8, but 33.0 is displayed as 33. Above that, rounding occurs, and the numbersmay be compressed and displayed with a factor, such as K.

In addition, while the x-axis tooltips in HTML5 charts are displayed with a separator, such asa comma (,) for the thousands digit, those in the server-generated charts are not.

For HTML5, as well as AFLEX, APDF, and AHTML charts, underlining is not supported for anyfont object.

The highlight effect applied in an HTML5 chart depends on the GRAPHTYPE parameter. Theriser may be made brighter or a different color, or, in the case of area charts with no markers,show a little circle that represents the current data point.

Legend Orientation is not currently supported in HTML5 chart output. The top and bottompositions are always HORIZONTAL and the left and right positions are always VERTICAL.

56 WebFOCUS


Supported Chart Types

The term static graphs refers to server-generated images (usually .PNG format). In contrast, client-side HTML5-rendered charts are highly interactive dynamic graphs, built using a JavaScript chartingengine and attached to the Document Object Model (DOM) in SVG format.

The following chart types are available for HTML5 charts.

Pie. Pie bar and proportional pie subtypes are currently supported only for static graphs.

Bar. BiPolar splits with Y1 on top and Y2 on bottom are currently supported only for staticgraphs.

Column. BiPolar splits with Y1 on top and Y2 on bottom are currently supported only for staticgraphs.

Line. BiPolar splits with Y1 on top and Y2 on bottom are currently supported only for staticgraphs.

Combo (bar/line/area).

3D Bars.

3D Ribbons.

3D Other. 3D spheres, pyramids, and cones are currently supported only for static graphs.

Histogram.

Stock.

Circular Gauge.

Funnel/Pyramid.

Scatter.

Bubble.

Waterfall.

Radar (circular line).

Polar (circular scatter).

BoxPlot.

SpectralMap.

TagCloud.



Mekko.

TreeMap.

Parabox.

Streamgraphs.

Note: Thermometer charts are currently only supported for static graphs.

WebFOCUS Maintain

The following are upgrade considerations and product changes for WebFOCUS Maintain:

When running Maintain applications from the MDE or Developer Studio, the Developer StudioViewer must be used to display the output. This is the default setting in Developer Studio.Changing this setting to use Internet Explorer output with Maintain may result in unexpectedbehavior. For more information on the Developer Studio Viewer, see the Developer StudioApplication Development Getting Started manual.

As of WebFOCUS 8, the Applaunch form to run Maintain applications is no longer included.

As of WebFOCUS Release 8.0 Version 06, using an exit button to close a Maintain applicationthat was invoked from Developer Studio or the Maintain Development Environment will displaythe wfmstart.html page in the Developer Studio viewer.

WebFOCUS Maintain Configuration Considerations

WebFOCUS Maintain uses the same WebFOCUS Client as regular WebFOCUS reportingapplications, and no Maintain-specific client configuration is needed. The WebFOCUS ReportingServer installed for normal reporting applications can run Maintain applications.

When configuring a WebFOCUS Server to run Maintain applications, consider the following:

Add outbound nodes to the odin.cfg files. For procedures invoked on remote servers (CALLAT, EXEC AT), you must add outbound nodes to the WebFOCUS Server odin.cfg file for thetarget servers. You can use the Web Console to edit all server files, including the odin.cfgfile.

Provide credentials for remote server execution. To allow your WebFOCUS Maintain applicationto CALL or EXEC procedures on remote servers that have security enabled, you can passcredentials in one of three ways:

Through the SQL EDA SET servername/userid password statement in the source serveredasprof.prf or user profile.

58 WebFOCUS

WebFOCUS Maintain

With SECURITY=PWP in the source server odin.cfg file. If appropriate, allow credentialsfor the source server to be passed to the target server.

Using the WebFOCUS Maintain SYS_MGR syntax to pass the credentials from within yourcalling procedure.

Fine-tune the agent_refresh parameter. The default value for agent_refresh, in the edaserve.cfgfile, for a WebFOCUS Reporting Server, is 100. Depending on your application, you may wantto set this value to a lower number for WebFOCUS Maintain, as connections to agents persistand therefore more activity is seen per agent. A lower number, such as 5 or 10, allows anagent that has been heavily used to be stopped and restarted more often, providing cleanenvironments for incoming connections.

Use Deployment=Private in edaserve.cfg. You must have deployment=private in theedaserve.cfg file. This is the default for a WebFOCUS Reporting Server.

For more information on configuring outbound nodes, SQL EDA commands, changing edaserve.cfgparameters, and using the Web Console, see the Server Administration for UNIX, Windows,OpenVMS, IBM i, and z/OS manual. For more information about the WebFOCUS Maintain SYS_MGRsyntax, refer to the Maintain Language Reference manual.

WebFOCUS Language

The following are upgrade considerations and product changes for the WebFOCUS reportinglanguage.

Compound Documents Change in Behavior

As of Release 8.0, when a component in a Compound document contains a report that generatesan error or attempts to create a HOLD file to be used in other components, but 0 records areproduced, error messages will be displayed and processing of the document will be terminated.

(FOC32584) WARNING: FILE HOLD(n) IS EMPTY

(FOC3298) ERROR FOUND IN A COMPOUND REPORTCompound Report is TERMINATING.....

XLSX Worksheets

In previous releases, when there was not enough space under the BY columns to display the fullSUBTOTAL TAG text, SUBTOTAL and RECOMPUTE lines within a report displayed across two rows.As of WebFOCUS Reporting Server Release 7.7.06M Gen 801, these SUBTOTAL rows will showon a single line and any TAG text larger than the BY columns will display only what can fit in thisspace. The full value can be seen in the formula bar.



ASIS Function

As of Version 7 Release 7.05, the ASIS function no longer considers a dot (.) and a blank spaceas equal.

APP COPYF Command

In WebFOCUS 8.0.x and higher, the DROP option of the APP COPYF command is not optional.Omitting it will generate an error.

FORMAT EXL07

Using XLSPAGESETS will automatically set the page margins to the default values of .25 inches.This will cause a change for procedures from EXL2K to EXL07. The only page setup featuresupported in EXL2K is orientation. Margins are set to the Excel default for a new workbook: 1inch top and bottom and .75 inch left and right.

FORMAT PPTX

The new PPTX output format is supported as of WebFOCUS Release 8.0 Version 08 and WebFOCUSReporting Server Release 7.7.05M Gen 157.

The Release 8.0 Version 08 WebFOCUS Client Redirection configuration file (mime.wfs) containsthe file type entries to support PPTX and PPTM presentations. You can configure earlier WebFOCUSClient 8.0.x releases to support PPTX and PPTM presentations created by the Reporting ServerJSCOM functionality by manually adding the PPTX and PPTM file type entries to the WebFOCUSClient Redirection configuration file (mime.wfs).

The mime.wfs file is location in the \client\wfc\etc directory of the WebFOCUS Client installation.The default directory path is:

C:\ibi\WebFOCUS8\client\wfc\etc

Note: PPTX and PPTM presentations created with the WebFOCUS Client Servlet functionalityis only supported in Release 8.0 Version 08 and higher.

To add the PPTX and PPTM file type entries to the WebFOCUS Client Redirection configurationfile (mime.wfs):

1. Backup the mime.wfs file located in the WebFOCUS Client \client\wfc\etc directory.

60 WebFOCUS

WebFOCUS Language

2. Edit the mime.wfs file and add the .potm and .potx entries after the .png entry. Each<ADDTYPE> entry is on a single line.

<ADDTYPE> .potm application/application/vnd.ms-powerpoint.template.macroEnabled.12binary no DEFAULT no .potm

<ADDTYPE> .potx application/vnd.openxmlformats-officedocument.presentationml.templatebinary no DEFAULT no .potx

3. Add the following entries for .pptm and .pptx after the .ppt entry. Each <ADDTYPE> entry ison a single line.

<ADDTYPE> .pptm application/vnd.ms-powerpoint.presentation.macroEnabled.12binary no DEFAULT no .pptm

<ADDTYPE> .pptx application/vnd.openxmlformats-officedocument.presentationml.presentationbinary no PPTX no .pptx

4. Save the mime.wfs file.

5. If the WebFOCUS web application is running, the WebFOCUS Client cache needs to be clearedby using the WebFOCUS Administration Console Clear Cache option or restarting the applicationserver the WebFOCUS Client is deployed on.

6. Sign on to the WebFOCUS Administration Console and access the Redirection Settings fromthe Configuration option to verify that the .potm, .potx, .pptm, and .pptx file types list correctly.The following image of the WebFOCUS Administration Console Redirection Settings showsthe added PowerPoint file types.

Note: These steps add the capability only to interactive reporting. ReportCaster distributionis not available.



Accordion By Row Reports

The following are upgrade considerations and product changes for Accordion By Row reports.

As of WebFOCUS Release 8.0 Version 01, Accordion By Row reports will display a grand totalor column total row under the data table and above the page and report footings. This newfeature can be turned off by setting ON TABLE NOTOTAL within the request. For existing reportswhere ON TABLE NOTOTAL exists in the request (the default for reports generated by InfoAssistand Report Painter), this will cause no change in behavior. For reports where ON TABLENOTOTAL is not defined, the grand total row will now be present. To remove this row andreturn to earlier behavior, add ON TABLE NOTOTAL syntax to the request.

As of WebFOCUS Reporting Server Release 7.7.05M Gen 134, multi-verb requests aresupported in Accordion By Row reports that contain sort fields on the highest level displaycommand.

WebFOCUS Font Support

As of WebFOCUS Reporting Server Release 7.7 Version 05 Gen 705 and higher, you can selectivelyembed a subset of Unicode (Arial Unicode and MS Lucida Sans Unicode) or Non-Unicode (Tahoma,Times New Roman, Trebuchet MS, and Courier New) TrueType fonts into a PDF file. The generatedPDF file will contain only the characters required to render the document.

HTML HFREEZE Reporting Feature Implementation Change

An implementation change was required for the HTML HFREEZE reporting feature to fix alignmentissues and provide non-Internet Explorer browser support. The HFREEZE measuring mechanismuses an extra data row to calculate the column width correctly. The report width measuringmechanism will use an extra data row. For the row of data to be measured properly, the extradata row has to be visible. This visible extra row increases the space on the report in each ofthe three HTML table (<TABLE>) sections created for the report HEADING, column titles and data,and FOOTING. The extra space has been minimized and must be displayed to measure the widthof the columns correctly.

The implementation change also provides non-Internet Explorer browser support with the HFREEZEreporting feature. The HFREEZE reporting feature is certified with the following browsers whenusing the WebFOCUS 8 WebFOCUS Client with a Release 7.7 Version 04 Reporting Server.

Internet Explorer 9 (32-bit) Compatibility Mode ON or OFF

Internet Explorer 8

Firefox® 10.02

Firefox 8

62 WebFOCUS

WebFOCUS Language

Firefox 3.6 (3.6.28 version tested)

Safari® 5.1.2

Chrome™ 17

Opera® 11.61

For the most current information related to browser version or configuration, view the WebFOCUSBrowser Support statement at the following URL:

https://techsupport.informationbuilders.com/tech/wbf/wbf_tmo_027.html

Variables Hidden with the -DEFAULTH Command

As of WebFOCUS Reporting Server Release 7.7 Version 05, the Dialogue Manager query command-? no longer displays the values of hidden variables defined with the -DEFAULTH command.

Web Services

As of WebFOCUS Release 8.0, WebFOCUS RESTful web services have been introduced. RESTfulweb services are developed on the REpresentational State Transfer (REST) architecture. Anyapplications that have been built in development environments such as Visual Studio .NET andJava should now be using WebFOCUS RESTful web services to integrate with WebFOCUS Release8.0. These web services provide comprehensive integration that can be used for tasks such assecurity maintenance, running WebFOCUS reports, and ReportCaster scheduling.

WebFOCUS SOAP web services are only being supported in WebFOCUS Release 8.0 for migratedenvironments. This means that WebFOCUS SOAP web services can only run WebFOCUS reportsin WebFOCUS Release 8.0 against a migrated folder structure.

The following image shows an example of the folder structure that is currently supported whenusing WebFOCUS SOAP web services.



https://techsupport.informationbuilders.com/tech/wbf/wbf_tmo_027.html

As of WebFOCUS Release 8.0, only the webFocusRunFex operation is being supported to runWebFOCUS reports against a migrated environment. In addition, the MREDeleteDomainfromGroupoperation is not supported.

The ability to create a WSDL file making a specific WebFOCUS report its own web service operationis no longer supported in WebFOCUS Release 8.0. Over time, applications built in developmentenvironments such as Visual Studio .NET and Java should be modified to use WebFOCUS RESTfulweb services to integrate with WebFOCUS Release 8.0.

Considerations for ReportCaster SOAP Web Services

This section describes upgrade considerations for ReportCaster SOAP web services.

You can access the WSDL launch page using the following URL:

http://host:port/ibi_apps/services/listServices

Creating Any Schedule

When creating any schedule, ibfsPath must be set to the folder where the schedule will be stored.

Visual Basic .NET Example:

mySchedule.ibfsPath="IBFS:/WFC/Repository/ReportCaster/carreportschedules"

Java Example:

mySchedule.setIbfsPath("IBFS:/WFC/Repository/ReportCaster/carreportschedules");

Creating a Schedule With a Report Library Distribution

When creating a schedule with a Report Library distribution, destinationPath must be set to thefolder where the library content will be stored.


distributionInfo.destinationPath="IBFS:/WFC/Repository/ReportCaster/carreportschedules"

Java Example:

distributionInfo.setDestinationPath("IBFS:/WFC/Repository/ReportCaster/carreportschedules");

Creating a Schedule With a WebFOCUS Report

When creating a schedule with a WebFOCUS report, domainHREF and folderHREF are no longerused. The procedureName attribute is used to define the path to the report to be run.


task1.procedureName="IBFS:/WFC/Repository/ReportCaster/carreportschedules/Car_Report.fex"

64 WebFOCUS

Web Services

Java Example:

task1.setProcedureName("IBFS:/WFC/Repository/ReportCaster/carreportschedules/Car_Report.fex");

Creating a Schedule With a Server Procedure Task

When creating a schedule with a server procedure task, procedureName includes the applicationname.


task1.procedureName="ibisamp/carinst.fex"

Java Example:

task1.setProcedureName("ibisamp/carinst.fex");

WebFOCUS Magnify

As of WebFOCUS Release 8.0 Version 09, WebFOCUS Magnify will only be available to the adminuser by default. As a result, you must initially log into WebFOCUS before using any Magnify-relatedfunctionality for the first time.

To restore the default behavior found in previous WebFOCUS releases, you must now configurethe public user separately to enable access to Magnify.



66 WebFOCUS

WebFOCUS Magnify

Customer ConnectionsWhere users partner with Information Builders to provide feedback and create qualitydocumentation.

Partner With Us

Information Builders Technical Content Management team is comprised of many talentedindividuals who work together to design and deliver quality technical documentation products.Your feedback supports our ongoing efforts!

You can also join a usability study to get an early look at new documentation products andservices. Your participation helps us create documentation products that meet your needs.

To send us feedback or make a customer connection, contact Michele Brady, Service Director,Technical Content Management at [email protected].

Request Permission to Use Copyright Material

To request permission to repurpose copyrighted material, please contact Frances Gambino, VicePresident, Technical Content Management at [email protected].

Visit the Information Builders Technical Content Library

To visit the Technical Content Library, go to http://documentation.informationbuilders.com/.

mailto:[email protected]?subject=Partner With Us

mailto:[email protected]?subject=Request Permission to Use Copyright Material

http://documentation.informationbuilders.com/

Information Builders, Inc.Two Penn PlazaNew York, NY 10121-2898

Developer Studio A

pplication Developm

ent G

etting StartedVersion 8 Release 1.0


DN4501241.0615