WebFOCUS Upgrade Considerations Release 8.0 Version 10

Transcription

1 WebFOCUS Upgrade Considerations Release 8.0 Version 10 June 30, 2015

2 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 are registered 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 registered trademarks 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 all claimed 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 parts thereof, may not be reproduced in any form without the written permission of Information Builders, Inc.

3 Contents WebFOCUS Upgrade Considerations Release 8.0 Version Tools Consolidation Installation and Configuration Server Configuration Disabling the CSRF Token When Connecting From a Release 8.0.x Client Migration InfoAssist App Studio HTML Composer Document Composer Report Painter ReportCaster WebFOCUS Infrastructure and Security WebFOCUS Operating Environments Managed Reporting Business Intelligence Dashboard WebFOCUS Visual Discovery WebFOCUS Visual Discovery Analyst Edition Active Technologies Version Requirements License Requirements SET HTMLENCODE Command Handling a Hidden BY Column on an Active Technologies Chart Syntax: How to Handle a Hidden BY Column on an Active Technologies Chart Saving an Active Technologies Report Using an Alternate Adobe Flex Compiler With the WebFOCUS Reporting Server Procedure: How to Use an Alternate Adobe Flex Compiler With the WebFOCUS Reporting Server Setting the Maximum Java Heap Size When Using an Alternate Adobe Flex Compiler Syntax: How to Set the Maximum Java Heap Size When Using an Alternate Adobe Flex Compiler Customizing Styles With JavaScript Files Setting the Initial Active Technologies Chart Size Developer Studio WebFOCUS Upgrade Considerations 3

4 Contents Developer Studio New Behavior Connecting to WebFOCUS WebFOCUS Environment Properties Procedure: How to Change a User Password in the Developer Studio Security Database Procedure: How to Change a User Password Through the Security Center Developing Content in the Repository Procedure: How to Update the Security Center to Allow Development Against the Repository Procedure: How to Restrict or Allow Access to the Data Servers Area Developer Studio Upgrade Considerations and Product Changes WebFOCUS Charts and Graphs HTML5 New Features and Upgrades Differences Between HTML5 Charts and Server-Generated Charts Supported Chart Types WebFOCUS Maintain WebFOCUS Maintain Configuration Considerations WebFOCUS Language Compound Documents Change in Behavior XLSX Worksheets ASIS Function APP COPYF Command FORMAT EXL FORMAT PPTX Accordion By Row Reports WebFOCUS Font Support HTML HFREEZE Reporting Feature Implementation Change Variables Hidden with the -DEFAULTH Command Web Services Considerations for ReportCaster SOAP Web Services WebFOCUS Magnify Customer Connections WebFOCUS

5 WebFOCUS Upgrade Considerations Release 8.0 Version 10 These topics provide upgrade considerations and product changes for WebFOCUS Release 8.0 Version 10. Before reading this documentation, Information Builders recommends reviewing the upgrade considerations for all intermediate releases you are upgrading from, as well as the WebFOCUS Release Notes, which includes documentation enhancements, known issues, and product limitations. These documents, which are periodically updated as needed, are located at the following URL: In this document: Tools Consolidation Installation and Configuration Server Configuration Migration InfoAssist App Studio HTML Composer Document Composer Report Painter ReportCaster WebFOCUS Infrastructure and Security WebFOCUS Operating Environments Managed Reporting Business Intelligence Dashboard WebFOCUS Visual Discovery WebFOCUS Visual Discovery Analyst Edition Active Technologies Developer Studio WebFOCUS Charts and Graphs WebFOCUS Maintain WebFOCUS Language Web Services WebFOCUS Magnify WebFOCUS Upgrade Considerations 5

6 Tools Consolidation Tools Consolidation Information Builders continues to enhance its WebFOCUS product line and add new capabilities and tools in order to meet customer requirements. In recent years, this has meant applying new technologies to provide a rich, modern web-based experience for users of WebFOCUS. To this end, in WebFOCUS 8, several legacy tools and interfaces, as well as some stabilized product options, are consolidated. The WebFOCUS 8 Tools Consolidation Statement is available from the Information Builders InfoResponse Online website ( To provide advanced notice of the WebFOCUS 8 Tools Consolidation, a CTSS Advisory notification was distributed on November 30, 2011 to InfoResponse Online subscribers. The legacy web tools consolidation includes the retirement of the Report Assistant, Graph Assistant, Power Painter, and Advanced Graph Assistant tools. Information Builders has a general policy of ensuring that our customers receive upgrades and new features as a standard part of their maintenance contracts. In this case, Information Builders is extending that program. Customers who have licensed Report Assistant and Graph Assistant under the Analytical Reporter or other licensing arrangements, upon upgrading to WebFOCUS 8 are entitled to trade those licenses in for no-cost InfoAssist Basic licenses. InfoAssist Basic, a subset of WebFOCUS InfoAssist, contains the capabilities found in Report Assistant and Graph Assistant. Contact your local Information Builders representative regarding Power Painter and Advanced Graph Assistant capabilities, which require the WebFOCUS InfoAssist license. The web consolidation also includes the retirement of the following Java applet-based interfaces and tools, which will eliminate the requirement to have a specific release of the Java VM present on 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 Graph Engine (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 HTML Composer 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 part of their standard maintenance contract. 6 WebFOCUS

7 WebFOCUS Upgrade Considerations Release 8.0 Version 10 The functionally stabilized product options that have been consolidated and discontinued as of WebFOCUS 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 product offering is discontinued due to a lack of usage and the availability of the WebFOCUS Mobile Favorites Product offering. ReportCaster Java Bean API is superseded by the ReportCaster Java API available as of Release 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 consolidation areas including functionality available to evaluate in WebFOCUS 7.7.x, which is also available from 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 Discontinued as of WebFOCUS 8 ReportCaster Java Bean API Discontinued as of WebFOCUS 8 WebFOCUS Upgrade Considerations 7

8 Installation and Configuration 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 full installation: 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 must perform the following post-installation step. You must create a new file called weblogic.xml in the WEB-INF directory for the WebFOCUS web application. It must contain the following information: <?xml version="1.0" encoding="utf-8"?> <wls:weblogic-web-app xmlns:wls=" xmlns:xsi=" xsi:schemalocation=" <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.war file 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 WebFOCUS packaging. Application content located in the WebFOCUS Release 8.0 Version 01 or later WebFOCUS 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 your earlier applications as /ibi_html or a custom alias, see the WebFOCUS and ReportCaster Installation and Configuration manual for your platform for information on how to manually configure the ibi_html soft alias for your application server. 8 WebFOCUS

9 WebFOCUS Upgrade Considerations Release 8.0 Version 10 The Run a Stored Procedure and Run an Ad Hoc Procedure pages, available from the WebFOCUS 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 Reporting Server options, located under the Diagnostics, Verification section in the WebFOCUS Administration Console. WebFOCUS Release 8.0 Version 10 is packaged with a newer version of the jackson-all jar file, which includes updated classes. To avoid conflicts with the current version of jackson-all jar that is included and used by IBM WebSphere Application Server Version 8.0 and 8.5, perform the following steps. These steps describe how to define a container-wide shared library that can be used by deployed WebFOCUS applications. 1. In the following directory, locate the jackson-all jar file that is packaged with WebFOCUS: ibi/webfocus80/webapps/webfocus/web-inf/lib 2. Create an empty directory on your system and copy the jackson-all jar file that is packaged 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 following image. WebFOCUS Upgrade Considerations 9

10 Installation and Configuration 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 resource definition is visible, and click New. 10 WebFOCUS

11 WebFOCUS Upgrade Considerations Release 8.0 Version 10 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 (for example, 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 the updated jackson-all jar file (packaged with WebFOCUS). 9. In the Class Loading area, select the Use an isolated class loader for this shared library check box. 10. Click OK, then click Apply. WebFOCUS Upgrade Considerations 11

12 Installation and Configuration 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 described in 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

13 WebFOCUS Upgrade Considerations Release 8.0 Version 10 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 called 15215webfocus_war and the Module is called WebFOCUS 8.0. WebFOCUS Upgrade Considerations 13

14 Installation and Configuration 3. Select the check box to the left of the WebFOCUS Application and click Reference shared libraries. 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 right arrow 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 the Shared library references pane. Ensure that the IBI Jackson 1.9 shared library for the Module is moved to the Selected area. 7. Click OK. 14 WebFOCUS

15 WebFOCUS Upgrade Considerations Release 8.0 Version 10 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 Libraries column 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 POST request in order to prevent a Cross-Site Request Forgery attack. If you are using a Release 8.0.x WebFOCUS client that is supported with the /8.1.x server, you need to disable the CSRF token in order to successfully connect to the server s HTTP Listener. You can disable the 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. WebFOCUS Upgrade Considerations 15

16 Migration 3. Open the security section of the page, and select zero (0) from the CSRF_TOKEN drop-down list, 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 WebFOCUS 8 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 with a type of URL. In previous versions of WebFOCUS, the URL was stored as the HREF. 16 WebFOCUS

17 WebFOCUS Upgrade Considerations Release 8.0 Version 10 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 accessed within the same WebFOCUS configuration from the BI Portal when a WebFOCUS Client license key with InfoAssist and InfoAssist Basic is configured. If you are licensed for InfoAssist Basic and full InfoAssist, contact your local branch or Customer Support to obtain a WebFOCUS 8 license key that includes both InfoAssist and Basic InfoAssist. The InfoAssist Basic product is available at no additional cost to customers upgrading to WebFOCUS 8 and have an active maintenance agreement for Report Assistant and Graph Assistant through the Analytical Reporter, Comprehensive User Services (CUS), or other licensing agreement that includes Report Assistant and Graph Assistant. For information on the InfoAssist capabilities not included in InfoAssist Basic, see the WebFOCUS 8 Report and Graph Tools Consolidation statement. Access to InfoAssist and InfoAssist Basic within the BI Portal is authorized using WebFOCUS Client security privileges. For information on WebFOCUS Client security privileges, see the WebFOCUS Security and Administration 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 in InfoAssist by clicking the Options button on the InfoAssist main menu. In Release 8.0 Version 05 and higher, the application theme is retrieved from the BI Portal. Therefore, the ability to specify an application theme in InfoAssist has been removed. As of Release 8.0 Version 01, slicers cascade within a hierarchy (cube or dimension builder-based), rather than in the order of user interaction, eliminating potential performance issues. When working with an SQL database and an alpha field is added to a Measure, the prefix becomes MAX instead of CNT. This occurs because MAX is more efficient than CNT. You can change 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 of a 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 that allows you to use the default style sheet. When you select this button, the dialog box will close and the default style sheet will be used. WebFOCUS Upgrade Considerations 17

18 InfoAssist DOC, WP, WK1, DIF, and LOTUS formats are not supported. If you try to open a procedure with one of these formats, an unsupported syntax warning message will display. If you choose to 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 from a legacy tool that contains SUB-TOTAL syntax, an unsupported syntax warning message will appear. If you choose to continue, InfoAssist will convert the syntax to SUBTOTAL and add the converted syntax to all higher-level sort breaks. SUMMARIZE syntax is not supported. If you try to open an existing procedure in InfoAssist from a legacy tool that contains SUMMARIZE syntax, an unsupported syntax warning message will 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 procedure in InfoAssist from a legacy tool that contains any of these three options, an unsupported syntax warning message will appear. If you choose to continue, InfoAssist will convert the procedure to regular HTML output. COLUMN-TOTAL syntax is not supported. If you try to open an existing procedure in InfoAssist from a legacy tool that contains this syntax, an unsupported syntax warning message will appear. 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 you try to open an existing procedure that includes lines, an unsupported syntax message will appear. 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 the canvas. When working with charts, nested X-axis text overlaps the legend area in the Interactive Design View. However, this issue does not occur every time. This does not appear when you run the chart. 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 still be enabled. 18 WebFOCUS

19 WebFOCUS Upgrade Considerations Release 8.0 Version 10 App Studio HTML Composer 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 changed from Show All Files in Associated Paths to Show Files in Selected Path Only. The causes the Open File dialog box to only show the files in the folder you select, by default. 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 to create thin-client Visual Discovery pages, has been removed in favor of the new Visual Discovery AE product. By default, form controls are shown in the template previews, shown in the Template selector dialog box. These form controls will not display when the template is opened in HTML Composer unless they are being used. For example, the form controls will display when you have variables that use them. In order to use a theme but not use a template, you must select No, Thanks in the Template selector dialog box. You can then select the theme you want using the Theme property. The Theme property is a property of the DOCUMENT object. For a Tab control, the default values for Edge color and Selected color are no longer displayed in the Properties window inline. Instead, they come from an external cascading style sheet file. 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 that marker is clicked. When you click another marker, the previously selected marker will be unselected. You can press the Ctrl or Shift key while right-clicking your mouse to select multiple markers. The Generate Graph and Add Filter right-click options are unavailable when using a guided report. When using a Calendar, the Disable property disables both the edit box and the icon. To disable only the edit box, use the Read only property. The Google InfoWindow, used in prior releases with Google Maps, has been replaced by a WebFOCUS generated InfoWindow. WebFOCUS Upgrade Considerations 19

20 Document Composer Document Composer Report Painter When opening a Visual Discovery page created in a prior release, you will receive the following warning 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 name as the domain folder from previous versions. For example, if in WebFOCUS 7.7.x your domain folder 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, you must set the Reporting Server for the newly created folder. In this example, you would have to set the Reporting Server for the user_domain folder. The Tools menu has been removed. Options previously found in the Tools menu can be found in the HTML Page tab, found in the Developer Studio Options dialog box. To apply settings to the 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 HTML Composer, will undergo a migration process. The migration will occur in memory. You may execute the page in the tool to verify execution. If you save the page, the migrated code will be saved. If you exit the tool without saving, the migrated code will not be saved. 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 its parameters 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 found in the Document tab, found in the Developer Studio Options dialog box. To apply settings to the current layout, only use the Settings option in the File menu. The following are upgrade considerations and product changes for Report Painter: When creating a report procedure where Measures and Dimensions are defined in the Master File, you must select the correct column type before dragging or double-clicking the field you want 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 SUM column type is selected, the field will not be added to the report. You must change the column type to BY or Detail and then double-click the field. 20 WebFOCUS

21 WebFOCUS Upgrade Considerations Release 8.0 Version 10 When creating a new report procedure, the default style sheet, or any of the Predefined Template Files you use, are referenced instead of being copied into the repository folder. If you want to copy the Predefined Template File instead of referencing it, select Copy instead of Reference (selected by default) at the bottom of the Style File Selector Wizard, when in the repository area. When a chart is generated from a report, the styling options of the report will be inherited by the chart. When browsing for an image using the Report Options Images tab, the image is directly added to 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 EXL07 format in the syntax. This is so newer versions of Excel will not have 07 in the format specification. 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 now comes after Cell Options. Insert Date can now only be accessed by right-clicking and selecting Insert 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 Distribution Servers 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 Library Only user has access only to the Library and not the repository tree. In WebFOCUS 8, the Report Library is integrated into the repository tree. As a result, a migrated Library Only user can see non-library items that have been shared to everyone. When entering a Reply Address in a schedule, the colon character (:) cannot be used. In releases prior to WebFOCUS 8, the use of this character was allowed. If a schedule with a Reply Address containing a colon (:) is migrated to WebFOCUS 8, the schedule will fail when executed on demand. WebFOCUS Upgrade Considerations 21

22 ReportCaster In WebFOCUS 8, the legacy ReportCaster API uses the ReportCaster and Library Content folders that are created by the migration process. If you have not migrated content to WebFOCUS 8 from an earlier release of WebFOCUS, then you must manually create the ReportCaster folder in order to use the legacy ReportCaster API to create a schedule (unless you specify the full IBFS path in the Schedule description). The ReportCaster folder must be created with the Auto Create My Content Folders property set. The Library Content folder or folders created during migration are the default destinations for Library output from scheduled Managed Reporting procedures and Reporting Server procedures. These folders must exist unless a full IBFS path is specified as the destination for Library output at schedule creation time. When a Library schedule has the access option Shared (Appears under Shared Content folder) and the Send after Report Saved to Library check box selected simultaneously, ReportCaster will only send 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 ReportCaster content because the content is integrated with IBFS security in the WebFOCUS Repository. When the ReportCaster API is called to retrieve Category information, the Category Name returned 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 ID was 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 Library distribution. ReportCaster is fully integrated with the WebFOCUS 8 Client security authorization implementation. Users, Groups, Schedules, Distribution Lists, Access Lists, and Library Reports are stored in the WebFOCUS Repository. Any custom applications that reported directly against the ReportCaster User and Group tables will need remediation to report against the WebFOCUS 8 Repository tables. The Library Management tool has been removed and replaced with equivalent functionality available 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 to WebFOCUS 8. If you are using an earlier release of WebFOCUS, contact Customer Support Services for assistance. 22 WebFOCUS

23 WebFOCUS Upgrade Considerations Release 8.0 Version 10 The Schedule option selected from an HTML Composer Page invokes the WebFOCUS 8 Basic Scheduling tool. In prior releases, the Single Page Scheduling Tool was invoked. This has been 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 distribution options, the user is prompted to select one of the options before accessing the Schedule tool, as shown in the following images: In prior releases, the Single Page Scheduling tool was invoked directly and the Distribute report 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 Distribution Lists 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, the scheduling of WebFOCUS Server procedures and WebFOCUS Repository procedures migrated from an earlier release, Library distribution and retrieval, Log management, and Console functionality. WebFOCUS Upgrade Considerations 23

24 ReportCaster In WebFOCUS 8, the ReportCaster legacy API requires that the system property IBI_DOCUMENT_ROOT be set. It does not need to be an environment variable. ReportCaster uses IBI_DOCUMENT_ROOT to request that the IBFS security system provide the information needed to connect to the WebFOCUS Repository and obtain configuration information for initialization. In previous releases, this was accomplished by using the CasterManagedConnectionFactory methods setservername and setportnumber to connect to the Distribution server. This connection to the Distribution server for initialization has been replaced by the connection to the IBFS security system using the system property IBI_DOCUMENT_ROOT. The CasterManagedConnectionFactory methods setservername and setportnumber have been 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/tools directory. Library Access Lists utilize the WebFOCUS Client Security sharing functionality to authorize groups and users access to Library reports in WebFOCUS 8. As of WebFOCUS Release 8.0 Version 01, Access List support of subgroups is available. Users must be authorized to share Library reports with the groups and users specified in the Access List for the library report to be shared with them when distributed to the WebFOCUS Repository. Changes to the Access Lists are applied at the next schedule execution. If the Library report access changes are required before the next schedule execution, they can be manually applied by accessing the Library report from the resource tree in the Business Intelligence Portal (BI Portal), Dashboard, or ReportCaster Explorer and selecting the Share or Share Advanced options. The resource tree sharing options are available to users who have been authorized to share library reports. The Library Access option Public has been replaced with Share to Everyone. Share to Everyone means the report is available to all users who are authorized to List and View Library content in the folder where the Library item resides. The Library Access option Access List has been replaced with Share Advanced. Share Advanced means the report is shared at distribution time to the users and groups that are on the Access List. If users or groups are added or removed from the Access List, the change is not effective until the next time the schedule is executed. 24 WebFOCUS

25 WebFOCUS Upgrade Considerations Release 8.0 Version 10 Library Reports are now stored in folders in the WebFOCUS repository. The Category field is still available and can be used to sort reports displayed in the ReportCaster Explorer. The folder that a Library report is stored in must exist at the time a schedule is created. A Library item is added to the selected folder when the schedule executes for the first time. Subsequent versions are added to this item. The name of the item is the name of the schedule or, in the case of a burst report, the burst value. Running a schedule with traces is not yet implemented when selecting a schedule from the tree in BI Portal, Dashboard, or the ReportCaster Explorer. A schedule can be run with trace options from within the Basic or Advanced Scheduling tools. In WebFOCUS 8, in order to retrieve a dynamic multi-select list using the Schedule tool, you must 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 longer a 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 duplicate names. Using the legacy ReportCaster API, you can create schedules with duplicate Titles, but the Names must be unique. The legacy ReportCaster API must be passed the unique Name when running 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 POST request in order to prevent a Cross-Site Request Forgery attack. If you are using a Release 8.0.x WebFOCUS Client that is supported with the /8.1.x server, you need to disable the CSRF token in order to successfully connect to the server HTTP Listener. You can disable the 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-down list, as shown in the following image. WebFOCUS Upgrade Considerations 25

26 WebFOCUS Infrastructure and Security 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. Generally, Kerberos appends the Windows Domain of the user to the user ID passed to WebFOCUS, in the format userid@domain.com. 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 then used to complete the sign-in process. To append the domain, change the stripdomainsuffix setting to false in the kerberospreference section of the securitysettings.xml file. 26 WebFOCUS

27 WebFOCUS Upgrade Considerations Release 8.0 Version 10 Selecting a hyperlink to drill down from within Microsoft Office products will fail, since the products are launched outside of the browser. The current security context and any previously established session-related cookies are not retained, changing the user authorization. The drill-down feature in Microsoft Office products functioned in WebFOCUS Release 7.7.x since anonymous 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 to drill down to reports. Enable the Remember Me feature on the Sign-in page. If the end-user uses the Remember Me feature, a persistent cookie is used. Use SSO with IIS/Tomcat Integrated Windows Authentication. Renegotiation occurs automatically 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 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 Managed Reporting Realm Driver. Customers that used the Realm Driver should adopt one of the following new approaches, depending on the scenario. Trusted Authentication. Configure WebFOCUS for Pre-Authentication. For more information, see the Authentication chapter in the WebFOCUS Security and Administration manual. External Authentication to LDAP or Active Directory. Configure the Reporting Server LDAP provider and then configure WebFOCUS to authenticate to the Reporting Server. For more information, see the Authentication chapter in the WebFOCUS Security and Administration manual. External Authorization to LDAP or Active Directory. Configure the Reporting Server LDAP provider and then configure WebFOCUS to authorize to the Reporting Server. For more information, see the Authorization chapter in the WebFOCUS Security and Administration manual. WebFOCUS Upgrade Considerations 27

28 WebFOCUS Infrastructure and Security External Authorization to RDBMS. Configure a custom security provider on the Reporting Server that reads the RDBMS data and then configure WebFOCUS to authorize to the Reporting Server. For more information, and to download a sample WFSQL provider, go to: wbf_8_server_custom_provider.html Custom Plug-in. In WebFOCUS 8, custom authentication and authorization solutions can be developed using the Reporting Server Custom security provider interface. The custom security 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 access security information from any source accessible to one of the Reporting Server data adapters. For more information, see the Security chapter in the Server Administration for UNIX, Windows, OpenVMS, IBM i, and z/os manual. You can also download a sample custom provider, and modify it to suit your needs from the following website: wbf_8_server_custom_provider.html As of WebFOCUS Release 8.0 Version 02, LDAP and Active Directory authentication and authorization is facilitated through the Reporting Server LDAP security provider and WebFOCUS is configured to authenticate and authorize users to the Reporting Server. Accordingly, the LDAP Interface page has been removed from the WebFOCUS Administration Console. To provide time to transition to the new Server LDAP configuration, WebFOCUS still supports previously configured Client LDAP configurations. However, changes to the Client LDAP provider properties must now be made manually through edits to webconfig.xml. All customers are encouraged to move to the new Server LDAP configuration, which includes a number of enhancements over Client LDAP. For more information, see the New Features manual and the Authentication and Authorization chapters in the WebFOCUS Security and Administration manual. The WebFOCUS 7.7.x and earlier Managed Reporting internal repository (/basedir) is not distributed in WebFOCUS 8 as it is superseded by the WebFOCUS 8 Client and security authorization model. See the WebFOCUS New Features manual for information about the WebFOCUS Client Security and Authorization Model and the Migration documentation for information on migrating Managed Reporting content from WebFOCUS 7.x. 28 WebFOCUS

29 WebFOCUS Upgrade Considerations Release 8.0 Version 10 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 could save parameterized reports, if given the saveparmreport privilege. For improved performance in WebFOCUS, by default, a ResponseHeaderFilter has been implemented. This enables caching of static content that is sent to the browser from the WebFOCUS application context. The settings for this filter are established in the web.xml file for the web application and are always enabled by default. Below are the default and recommended parameters that are used. You can modify these parameters for individual implementation 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> <!-- 30 days --> </context-param> <context-param> <param-name>responseheaderfilter.expires</param-name> <param-value>259200</param-value> <!-- 30 days --> </context-param> WebFOCUS Upgrade Considerations 29

30 WebFOCUS Infrastructure and Security The ResponseHeaderFilter sets the Cache-Control header to public, max-age=259200, and the expires header to a value of 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 need to be cleared, so that you obtain the latest version of the software. This includes the browser cache, and any caching servers in the environment. 30 WebFOCUS

31 WebFOCUS Upgrade Considerations Release 8.0 Version 10 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 version of the browser cache. WebFOCUS Operating Environments The following is an upgrade consideration and product change for WebFOCUS operating environments: The i5 environment now supports 64-bit packed arithmetic with a resulting performance enhancement when using long packed numbers. WebFOCUS Upgrade Considerations 31

32 Managed Reporting 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 for Parameters property is unchecked, you will still be prompted if there are any parameters that do not have a value supplied. This applies to running procedures (FEX) stored in the WebFOCUS Repository Content folder path. In Release 8.0 Version 10, the WebFOCUS Client AutoPrompting IBIMR_promptingUnset setting 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 for Parameters setting is unchecked in the FEX Properties dialog box. As of WebFOCUS Release 8.0 Version 02, the Managed Reporting Deferred Ticket Cleanup Utility is supported. Due to WebFOCUS 8 architecture changes, this utility only processes the repository defined in the WebFOCUS Client configuration for which it is being run. As of WebFOCUS 8, the WebFOCUS Client processing of Managed Reporting requests applies stricter rules to referenced files. When a referenced file is not located in the WebFOCUS Repository IBFS path, a Resource not found error is displayed. Therefore, all referenced files located 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 Reporting Server. 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 file STHS001, referenced in the following command in a Managed Reporting procedure, is located on the Reporting Server: ON TABLE SET STYLE STHS0001 The correct coding of this reference for the STHS001.sty file, located on the EDASERVE Reporting Server, is either: -MRNOEDIT ON TABLE SET STYLE STHS001 or ON TABLE SET STYLE IBFS:/EDA/EDASERVE/STHS001.STY 32 WebFOCUS

33 WebFOCUS Upgrade Considerations Release 8.0 Version 10 Business Intelligence Dashboard The following are upgrade considerations and product changes for Business Intelligence Dashboard: 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 logged in as an authenticated user. This is a difference in behavior from WebFOCUS 7.7.x, where public views could be seen before entering Dashboard. In WebFOCUS 8, the Business Intelligence Dashboard Change Management utility is only accessible from View Builder. Public user authorization in a Public view is based on user permissions. In WebFOCUS 8, the Public ID is migrated and automatically assigned the WF_Role_Public permission set. An alternate user ID designated as the Public user needs to be assigned the WF_Role_Public permission set. Prior to WebFOCUS 8, the Business Intelligence Dashboard Login page was accessed using the following URL: In WebFOCUS 8, the Business Intelligence Dashboard Login page is accessed using the following URL: 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 requests when 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 an authenticated user. The Public User ID and Password is no longer required to be changed in View Builder. The User ID and Password will need to be changed from the Security Center, along with modifications to the IBI_Anonymous_User parameter located in the Configuration, Application Settings, Security section in the WebFOCUS Administration Console. For more information on the 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 View Builder. Instead, the IBI_Anonymous_WFRS_User and IBI_Anonymous_WFRS_Pass parameter values need to be modified from the Configuration, Application Settings, Security section in the WebFOCUS Administration Console. For more information on the Anonymous user, see the WebFOCUS Security and Administration manual. WebFOCUS Upgrade Considerations 33

34 WebFOCUS Visual Discovery The Role Tree has been discontinued. The new security model will allow for similar functionality within a List block. The Dashboard Editor has limited functionality. Favorites and Mobile Favorites content will now be stored in the database repository and not in 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 been removed. It is recommended to set the global session timeout parameter found in the web application 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 is signed 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 prior to WebFOCUS 8. WebFOCUS 7.x Visual Discovery applications are supported with WebFOCUS 8 for run time. Thin Client is not supported. Visual Discovery is no longer opened through the ActiveX control button on the components toolbar. To open Visual Discovery from HTML Composer, click the Vis button on the components toolbar. 34 WebFOCUS

35 WebFOCUS Upgrade Considerations Release 8.0 Version 10 In WebFOCUS 8, you select a Data Pool and access Visual Discovery control settings through a new Properties and Settings dialog box. When you insert a new Visual Discovery control onto an HTML page, the Properties and Settings dialog box opens. If the Properties and Settings dialog box does not open automatically, or it does not appear when you select an existing control, click Properties and Settings from the View menu. For more information, see the Using WebFOCUS Visual Discovery to Develop Analytic Dashboards manual. The <PARAM NAME="Files"> value no longer displays the table name used by the chart control in the.htm code. This information is contained in other sections of the code and should only be edited using HTML Composer. WebFOCUS Visual Discovery Analyst Edition New tracks for WebFOCUS Visual Discovery Analyst Edition (AE) require fresh installations. As a result, any previous versions of WebFOCUS Visual Discovery AE must be completely uninstalled. Note: The WebFOCUS Visual Discovery AE installer does not prevent an upgrade existing installation 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 Program and Features from the Control Panel. Click Turn Windows features on or off. The Windows Features dialog box opens, as shown in the following image. WebFOCUS Upgrade Considerations 35

36 Active Technologies Active Technologies Version Requirements License Requirements Expand Internet Information Services, Web Management Tools, and ensure IIS Management Scripts and Tools is selected. Click OK. If this option is not set, then an error message indicating Could not load file or assembly or a similar error message may be displayed. When publishing a project using WebFOCUS Visual Discovery Workbench AE, the Embed Data check box is no longer selected by default in the Publish Dashboard dialog box. It is recommended to select the Embed Data check box only as required. If you are republishing existing projects where the Embed Data check box was originally selected, you must select this option manually in the Publish Dashboard dialog box. Data Sheet default for Coloring Mode is set to Use Foreground Color. To include the Data Sheet in color by associations, change this property to Color By Data. The following are upgrade considerations and product changes for Active Technologies (WebFOCUS Reporting Server Release 7.7 Version 05). 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 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 or higher is required so that the Adobe Flash Player run-time code included in the Reader can render the SWF files that are Adobe Flash Player compatible. Starting with WebFOCUS Reporting Server Release 7.7 Version 04, Active Technologies require Internet Explorer 8 or higher. Starting with WebFOCUS Reporting Server Release 7.7 Version 04, you no longer need a valid license for Adobe Flex Builder 3 Professional in order to render charts in active report for Adobe Flash Player output. SET HTMLENCODE Command Starting with WebFOCUS Reporting Server Release 7.7 Version 04, the behavior of the SET HTMLENCODE command has changed. 36 WebFOCUS

37 WebFOCUS Upgrade Considerations Release 8.0 Version 10 SET HTMLENCODE=ON removes the data value that is displayed on top of a cell menu when you click a data value in a cell. This is the default behavior for WebFOCUS Reporting Server Release 7.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 you click a data value in a cell. This is the default behavior for WebFOCUS Reporting Server Release 7.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 BY column when NOPRINT is used in a GRAPH request. This command applies when the setting for the chart engine is JSCHART. Syntax: How to Handle a Hidden BY Column on an Active Technologies Chart The syntax is SET ARNOPRINTHIDE = {ON OFF} where: ON OFF Excludes a hidden BY column (BY column with the NOPRINT option) from the sort processing of 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 syntax for the BY column in the procedure. The data for a hidden BY column is available for use elsewhere. For example, you can use it to populate the global filter drop-down list or other filter control on an active dashboard. Includes a hidden BY column (BY column with the NOPRINT option) in the sort processing of an active chart. The chart is sorted by all the hidden BY columns, and data from all the columns 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 browser File menu, using the Save Page As option. For example, in Internet Explorer, you can select Save as from the File menu, and in the Save as type drop-down list, select Webpage, HTML only. WebFOCUS Upgrade Considerations 37

38 Active Technologies 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 sure to change the command to SET AROUTPUT = ALL to allow users to save the report or document with the browser Save as option. For more information on the SET AROUTPUT command, see the Active Technologies User's Guide. As of WebFOCUS Release 8.0 Version 02, make sure that the IBIF_active_extjs parameter is set 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. You can find this parameter in the General category of Client Settings in the Configuration menu of the WebFOCUS Administration Console. For details on this parameter, see the WebFOCUS Security 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 with the Adobe Open Source Flex SDK. The SDK is installed on the WebFOCUS Reporting Server and used to create an active report for Adobe Flash Player. As of WebFOCUS Reporting Server Release 7.7 Version 04, the compiler has been upgraded to Flex Active Technologies provide backward compatibility, enabling you to use earlier SDKs to compile your existing interactive PDF and Flex documents with active reports for Adobe Flash Player. You can run an earlier version of the compiler, such as the compiler that comes with the Adobe Open Source 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 Enable for Adobe Flex SWC files to the \frameworks\libs directory of your Flex SDK installation. For more information, see the WebFOCUS Enable for Adobe Flex 4.x User's Guide. Procedure: How to Use an Alternate Adobe Flex Compiler With the WebFOCUS Reporting Server 1. Download the Adobe Flex SDK. Previous releases produced by Adobe, including 3.5, are available 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 the interactive PDF or Flex document with an active report for Adobe Flash Player, add the following command SET FLEXSDK = path_to_sdk 38 WebFOCUS

39 WebFOCUS Upgrade Considerations Release 8.0 Version 10 where: path_to_sdk Is the full path to the SDK whose compiler you want to use to generate the interactive PDF 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 Flex Compiler With the WebFOCUS Reporting Server on page 38, you can also use the SET FLEXMEM command to specify the maximum Java heap size allocated to the Flex compiler to compile Flash or Flex files. If there is not enough available memory allocated to the Flex compiler at compilation time, errors may occur. By default, the maximum Java heap size is typically set to 384m (megabytes) in a script file named mxmlc, in a variable named $VMARGS. The mxmlc file resides in the Flex SDK \bin directory installed on your system. Syntax: How to Set the Maximum Java Heap Size When Using an Alternate Adobe Flex Compiler 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 640 megabytes. Customizing Styles With JavaScript Files If a JavaScript file, such as irpfsty.js, irpstd.js, or irpfstd.js, was created prior to WebFOCUS Reporting Server Release 7.7 Version 04 and resides in your application folder, you must remove it and move the custom contents into the corresponding irpcusf.js file for AHTML, irpuflex.js file for FLEX/APDF, or irpcfgu.js file for all the default styles. WebFOCUS Upgrade Considerations 39

40 Developer Studio Setting the Initial Active Technologies Chart Size Developer Studio When you create an active chart using GRAPH FILE syntax, GRAPH FILE automatically sets the initial chart size to 768 x 480 pixels, by default. This feature applies to all chart engines. The following section provides information on new behavior in Developer Studio. It also includes upgrade 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, Data Servers, Web Applications, and Repository. The Repository area allows you to use Developer Studio to administer and develop against a Managed 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 build custom user content. Development and Administration options are enabled based on user privileges defined in the Security System. Credentials can be saved in the environment properties to avoid reprompting. Saved credentials are encrypted for security. 40 WebFOCUS

41 WebFOCUS Upgrade Considerations Release 8.0 Version 10 To change or remove stored credentials, open the WebFOCUS Environment Properties dialog box and click the WebFOCUS object to make the required changes. Note: The Repository area is not visible for Developer Studio standalone installations. The Repository is installed only with WebFOCUS. The Logoff option available at the environment level is applicable to all areas of the environment. 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. WebFOCUS Upgrade Considerations 41

42 Developer Studio Connecting to WebFOCUS To connect to a WebFOCUS environment (local or remote) or to the local WebFOCUS Client that is included with Developer Studio, a connection to WebFOCUS is required. For Developer Studio standalone configurations (no WebFOCUS on the same machine), the product is configured to use the user ID wfdesktop to connect to its local WebFOCUS Client. This user ID is automatically stored in the localhost environment properties. When Developer Studio connects to WebFOCUS, a logon screen displays, prompting you to enter the user name and password. The Logon dialog box has the user ID wfdesktop already entered as 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 to the WebFOCUS Administration Console and the Security Center. If you have WebFOCUS installed on your local PC as well, the connection will be performed against the WebFOCUS configuration. Derby Security database. A Derby database is installed with Developer Studio editions that allow local, standalone development. It is used to store user accounts and policies required for Developer Studio to connect to its local WebFOCUS Client. The Derby database comes preloaded with user IDs that have developer and administration permissions. The Security Center that is available with Developer Studio provides the capability to change user passwords. Other tasks, such as creation or removal of existing user IDs and operations, are not permitted. The embedded Derby database runs as part of the ibi_apps web application. 42 WebFOCUS

43 WebFOCUS Upgrade Considerations Release 8.0 Version 10 The Derby database that is optionally installed with WebFOCUS runs as a service and will not interfere with the Developer Studio Derby database if both products are installed on the same machine. WebFOCUS Environment Properties As of Developer Studio Release 8.0 Version 01, the WebFOCUS Environment Properties dialog box has changed, as shown in the following image. When you configure a WebFOCUS Environment in Developer Studio, you must set the HTML Alias to: /ibi_apps/ibi_html WebFOCUS Upgrade Considerations 43

44 Developer Studio where: ibi_apps Is the name of the ibi_apps alias configured with WebFOCUS or Developer Studio. This alias can be customized. ibi_html Is constant. An ibi_html alias may be required if you have created applications from a previous Developer Studio release that contains hard coded references to the ibi_html alias. For these cases, you need 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. Procedure: How to Change a User Password in the Developer Studio Security Database 1. Assuming that you are using a default configuration of Tomcat with port 8080 and alias of ibi_apps, open the WebFOCUS Welcome Page using 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

45 WebFOCUS Upgrade Considerations Release 8.0 Version 10 For example, click on Developer Studio guest account and select Change Password, as shown in the following image. The Change Password dialog box appears, as shown in the following image. Enter the password information and click OK. WebFOCUS Upgrade Considerations 45

46 Developer Studio Procedure: How to Change a User Password Through the Security Center Users have access to the Security Center if they sign in using an Administrator account, such as admin. 1. Select Security Center in the Administration drop-down menu, as shown in the following image. 2. From the Security Center, the administrator can change the password of any user by right-clicking a user and selecting Set Password, as shown in the following image. 46 WebFOCUS

47 WebFOCUS Upgrade Considerations Release 8.0 Version 10 Developing Content in the Repository To work against WebFOCUS 8 and develop content in the Repository, the security system needs to be updated. The user ID admin can perform development and has full access to the Repository. User ID wfdesktop can perform self-service development work in the Projects, Data Servers, and Web Applications areas. The WebFOCUS Security Center can be customized to add new users and allow development from Developer Studio: Create new users or use existing users and assign them to a group that has the required Developer Studio privileges. To connect to WebFOCUS from Developer Studio, users are required to have the privilege Desktop Connect (privilege name opdtconnect). This privilege is included, by default, in the existing rule, WF_DesktopConnect. Developers will need privileges, such as create item, run, delete, and so on. These privileges are available in the existing rule (WF_Role_Developer). New Roles can be created and customized to control tools and operations developers are permitted to 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 be limited 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. WebFOCUS Upgrade Considerations 47

48 Developer Studio Procedure: How to Update the Security Center to Allow Development Against the Repository 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 then Rules, as shown in the following image. 48 WebFOCUS

49 WebFOCUS Upgrade Considerations Release 8.0 Version 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, and connection to WebFOCUS from Developer Studio. The Developers group does not contain any users, by default. You can create new users and add them to this group to allow development 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, by default. This group has privileges that allow development in the Projects, Data Servers, and Web Applications areas. Users from this group can see the Repository area and can access content available to anonymous users, such as the Public folder, but cannot create content. The SelfServiceDevelopers group has the WF_DesktopConnect rule applied. WebFOCUS Upgrade Considerations 49

50 Developer Studio Users can be added to both groups, Developers and SelfServiceDevelopers, to allow development in all areas of Developer Studio. 5. As an example of creating user IDs and applying them to the Developers group, select Administration, then Security Center from the main toolbar. 6. Click New User and assign new users to the required group (the Developers group, in this case). The following image shows an example of creating a new user. 50 WebFOCUS

51 WebFOCUS Upgrade Considerations Release 8.0 Version 10 Procedure: How to Restrict or Allow Access to the Data Servers Area To allow access to the Data Servers area for a group, such as the Developers Group, perform the 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. WebFOCUS Upgrade Considerations 51

52 Developer Studio 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 selected group. 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 this environment, with any user that belongs to the Developers group. To restrict permission, you need to select Deny from the Access column drop-down list for the permission you want to remove. The same steps can be applied to restrict or enable access to the Web Applications area by following the same steps and selecting the WEB component, instead of EDA. 52 WebFOCUS

53 WebFOCUS Upgrade Considerations Release 8.0 Version 10 Note: Developer Studio Release 8.0 Version 10 is recommended to be used with WebFOCUS Release 8.0 Version 10. Developer Studio cannot connect to WebFOCUS Release 8.0 Version 01 or WebFOCUS 7.x environments, and development against such environments is not supported. If you have an earlier release of Developer Studio, it is recommended that you uninstall the earlier version prior to installing WebFOCUS Release 8.0 Version 10. You can also upgrade the earlier release to WebFOCUS Release 8.0 Version 10. Existing applications and configured environments will not be impacted. For single sign on (SSO) security systems, such as SiteMinder, to avoid issues with session timeouts, it is recommended that you set your application server with a long session timeout period. The default setting for some application servers is between 20 and 30 minutes, 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 against WebFOCUS. At this point, if a manual refresh is performed using menu View/Refresh or pressing F5, the WebFOCUS Environments area will be refreshed. Only the Repository area will display and the user will be switched to the Anonymous user, which does not have any developer privileges. To continue working, the developer must perform a logoff at the environment level and sign in using a proper user ID. For non-sso configured environments, Developer Studio will reconnect silently when it receives a message that a session timeout occurred. This will allow developers to continue development without having to sign out and sign in again. For security purposes, many application servers are configured to transmit HttpOnly session ID 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 the application server is configured for HttpOnly. Creating content has differences between Developer Studio and the Business Intelligence Portal. Developer Studio prompts for the Name of the item. Creating content in the Business Intelligence Portal prompts for the Title of the item. WebFOCUS Upgrade Considerations 53

54 Developer Studio 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 been changed 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/ReportCaster button is no longer available because this option is not valid when connecting to a WebFOCUS 8 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 within the areas they can access. This applies to Managed Reporting content and ReportCaster options. You can store WebFOCUS credentials in the WebFOCUS Environment Properties dialog box by clicking the WebFOCUS button. When connecting to WebFOCUS and prompted to log on, the User Name field is no longer populated with the user ID wfdesktop. The User Name field is now blank to allow the developer to enter any valid user ID for their environment. The user ID wfdesktop is still available in the product and allows self-service development in the Projects, Data Servers, and Web Applications areas. Access to the Repository is restricted and users cannot create new content with this user ID. When upgrading from an earlier release of Developer Studio, such as Release 8.0 Version 01 to Release 8.0 Version 10, you must update the localhost environment to ensure the HTML Alias is configured accordingly (/ibi_apps/ibi_html). The same applies for configured WebFOCUS 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 HTML Alias 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

55 WebFOCUS Upgrade Considerations Release 8.0 Version Verify that the selected Alert is highlighted, and click Save. Note: The Save button appears the first time you open an existing Alert procedure in the Alert Wizard. When you reopen a migrated Alert procedure in the Alert Wizard, this Save 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 the ibidemo folder, under the apps directory that is created during the installation program. These sample files include the IBI Demonstration project (.gfa) and various procedure, HTML, and image 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 no longer 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 one minute after a user cancels out of the dialog box to enter WebFOCUS credentials. This is to prevent multiple sign-in prompts for a WebFOCUS environment. If a user needs to reconnect to the WebFOCUS environment for which they canceled the connection, they need to wait one minute. WebFOCUS Charts and Graphs 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 prior releases. 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 WebFOCUS Upgrade Considerations 55

56 WebFOCUS Charts and Graphs 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 a plus sign (+) centered in it. The marker shape, circleminus, displays a circle with a minus sign (-) centered in it. The SET CURRSYMB command, which specifies a currency symbol to be displayed with currency values whose format specifications include the M or N display options, is now supported for all output formats, except AHTML, APDF, and AFLEX. Using the JSCHART property, chart.datalabels.usenegativecolor, you can apply a different color to data labels for negative values than the color used for positive values. The color used will be the one defined by the chart.colormode.negcolor property. You can insert the chart.datalabels.usenegativecolor property into the chart by issuing the setusenegativedatatextcolor(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 a different algorithm for formatting datatext for risers than the legacy chart engine. The HTML5 automatic numeric formatting determines whether the datatext for risers displays decimal places, and if so, how many. Values under get decimal precision, so that 22.8 is displayed as 22.8, but 33.0 is displayed as 33. Above that, rounding occurs, and the numbers may 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 as a 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 any font object. The highlight effect applied in an HTML5 chart depends on the GRAPHTYPE parameter. The riser 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 bottom positions are always HORIZONTAL and the left and right positions are always VERTICAL. 56 WebFOCUS

57 WebFOCUS Upgrade Considerations Release 8.0 Version 10 Supported Chart Types The term static graphs refers to server-generated images (usually.png format). In contrast, clientside HTML5-rendered charts are highly interactive dynamic graphs, built using a JavaScript charting engine 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 static graphs. Column. BiPolar splits with Y1 on top and Y2 on bottom are currently supported only for static graphs. Line. BiPolar splits with Y1 on top and Y2 on bottom are currently supported only for static graphs. 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. WebFOCUS Upgrade Considerations 57

58 WebFOCUS Maintain 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 Studio Viewer 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 unexpected behavior. For more information on the Developer Studio Viewer, see the Developer Studio Application 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 application that was invoked from Developer Studio or the Maintain Development Environment will display the wfmstart.html page in the Developer Studio viewer. WebFOCUS Maintain Configuration Considerations WebFOCUS Maintain uses the same WebFOCUS Client as regular WebFOCUS reporting applications, and no Maintain-specific client configuration is needed. The WebFOCUS Reporting Server 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 (CALL AT, EXEC AT), you must add outbound nodes to the WebFOCUS Server odin.cfg file for the target servers. You can use the Web Console to edit all server files, including the odin.cfg file. Provide credentials for remote server execution. To allow your WebFOCUS Maintain application to CALL or EXEC procedures on remote servers that have security enabled, you can pass credentials in one of three ways: Through the SQL EDA SET servername/userid password statement in the source server edasprof.prf or user profile. 58 WebFOCUS

59 WebFOCUS Upgrade Considerations Release 8.0 Version 10 With SECURITY=PWP in the source server odin.cfg file. If appropriate, allow credentials for the source server to be passed to the target server. Using the WebFOCUS Maintain SYS_MGR syntax to pass the credentials from within your calling procedure. Fine-tune the agent_refresh parameter. The default value for agent_refresh, in the edaserve.cfg file, for a WebFOCUS Reporting Server, is 100. Depending on your application, you may want to set this value to a lower number for WebFOCUS Maintain, as connections to agents persist and therefore more activity is seen per agent. A lower number, such as 5 or 10, allows an agent that has been heavily used to be stopped and restarted more often, providing clean environments for incoming connections. Use Deployment=Private in edaserve.cfg. You must have deployment=private in the edaserve.cfg file. This is the default for a WebFOCUS Reporting Server. For more information on configuring outbound nodes, SQL EDA commands, changing edaserve.cfg parameters, 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_MGR syntax, refer to the Maintain Language Reference manual. WebFOCUS Language The following are upgrade considerations and product changes for the WebFOCUS reporting language. Compound Documents Change in Behavior XLSX Worksheets As of Release 8.0, when a component in a Compound document contains a report that generates an error or attempts to create a HOLD file to be used in other components, but 0 records are produced, 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 REPORT Compound Report is TERMINATING... In previous releases, when there was not enough space under the BY columns to display the full SUBTOTAL TAG text, SUBTOTAL and RECOMPUTE lines within a report displayed across two rows. As of WebFOCUS Reporting Server Release M Gen 801, these SUBTOTAL rows will show on a single line and any TAG text larger than the BY columns will display only what can fit in this space. The full value can be seen in the formula bar. WebFOCUS Upgrade Considerations 59

60 WebFOCUS Language ASIS Function APP COPYF Command FORMAT EXL07 FORMAT PPTX As of Version 7 Release 7.05, the ASIS function no longer considers a dot (.) and a blank space as equal. In WebFOCUS 8.0.x and higher, the DROP option of the APP COPYF command is not optional. Omitting it will generate an error. 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 feature supported in EXL2K is orientation. Margins are set to the Excel default for a new workbook: 1 inch top and bottom and.75 inch left and right. The new PPTX output format is supported as of WebFOCUS Release 8.0 Version 08 and WebFOCUS Reporting Server Release M Gen 157. The Release 8.0 Version 08 WebFOCUS Client Redirection configuration file (mime.wfs) contains the file type entries to support PPTX and PPTM presentations. You can configure earlier WebFOCUS Client 8.0.x releases to support PPTX and PPTM presentations created by the Reporting Server JSCOM functionality by manually adding the PPTX and PPTM file type entries to the WebFOCUS Client 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 functionality is only supported in Release 8.0 Version 08 and higher. To add the PPTX and PPTM file type entries to the WebFOCUS Client Redirection configuration file (mime.wfs): 1. Backup the mime.wfs file located in the WebFOCUS Client \client\wfc\etc directory. 60 WebFOCUS

61 WebFOCUS Upgrade Considerations Release 8.0 Version 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.12 binary no DEFAULT no.potm <ADDTYPE>.potx application/vnd.openxmlformats-officedocument.presentationml.template binary no DEFAULT no.potx 3. Add the following entries for.pptm and.pptx after the.ppt entry. Each <ADDTYPE> entry is on a single line. <ADDTYPE>.pptm application/vnd.ms-powerpoint.presentation.macroenabled.12 binary no DEFAULT no.pptm <ADDTYPE>.pptx application/vnd.openxmlformats-officedocument.presentationml.presentation binary 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 cleared by using the WebFOCUS Administration Console Clear Cache option or restarting the application server the WebFOCUS Client is deployed on. 6. Sign on to the WebFOCUS Administration Console and access the Redirection Settings from the 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 shows the added PowerPoint file types. Note: These steps add the capability only to interactive reporting. ReportCaster distribution is not available. WebFOCUS Upgrade Considerations 61

62 WebFOCUS Language Accordion By Row Reports The following are upgrade considerations and product changes for Accordion By Row reports. WebFOCUS Font Support As of WebFOCUS Release 8.0 Version 01, Accordion By Row reports will display a grand total or column total row under the data table and above the page and report footings. This new feature can be turned off by setting ON TABLE NOTOTAL within the request. For existing reports where ON TABLE NOTOTAL exists in the request (the default for reports generated by InfoAssist and Report Painter), this will cause no change in behavior. For reports where ON TABLE NOTOTAL is not defined, the grand total row will now be present. To remove this row and return to earlier behavior, add ON TABLE NOTOTAL syntax to the request. As of WebFOCUS Reporting Server Release M Gen 134, multi-verb requests are supported in Accordion By Row reports that contain sort fields on the highest level display command. As of WebFOCUS Reporting Server Release 7.7 Version 05 Gen 705 and higher, you can selectively embed 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 generated PDF 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 alignment issues and provide non-internet Explorer browser support. The HFREEZE measuring mechanism uses an extra data row to calculate the column width correctly. The report width measuring mechanism will use an extra data row. For the row of data to be measured properly, the extra data row has to be visible. This visible extra row increases the space on the report in each of the 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 width of the columns correctly. The implementation change also provides non-internet Explorer browser support with the HFREEZE reporting feature. The HFREEZE reporting feature is certified with the following browsers when using 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 Firefox 8 62 WebFOCUS

63 WebFOCUS Upgrade Considerations Release 8.0 Version 10 Firefox 3.6 ( version tested) Safari Chrome 17 Opera For the most current information related to browser version or configuration, view the WebFOCUS Browser Support statement at the following URL: Variables Hidden with the -DEFAULTH Command Web Services 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. As of WebFOCUS Release 8.0, WebFOCUS RESTful web services have been introduced. RESTful web services are developed on the REpresentational State Transfer (REST) architecture. Any applications that have been built in development environments such as Visual Studio.NET and Java should now be using WebFOCUS RESTful web services to integrate with WebFOCUS Release 8.0. These web services provide comprehensive integration that can be used for tasks such as security maintenance, running WebFOCUS reports, and ReportCaster scheduling. WebFOCUS SOAP web services are only being supported in WebFOCUS Release 8.0 for migrated environments. This means that WebFOCUS SOAP web services can only run WebFOCUS reports in WebFOCUS Release 8.0 against a migrated folder structure. The following image shows an example of the folder structure that is currently supported when using WebFOCUS SOAP web services. WebFOCUS Upgrade Considerations 63

64 Web Services As of WebFOCUS Release 8.0, only the webfocusrunfex operation is being supported to run WebFOCUS reports against a migrated environment. In addition, the MREDeleteDomainfromGroup operation is not supported. The ability to create a WSDL file making a specific WebFOCUS report its own web service operation is no longer supported in WebFOCUS Release 8.0. Over time, applications built in development environments such as Visual Studio.NET and Java should be modified to use WebFOCUS RESTful web 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: 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 the folder where the library content will be stored. Visual Basic.NET Example: 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 longer used. The procedurename attribute is used to define the path to the report to be run. Visual Basic.NET Example: task1.procedurename="ibfs:/wfc/repository/reportcaster/carreportschedules/car_report.fex" 64 WebFOCUS

65 WebFOCUS Upgrade Considerations Release 8.0 Version 10 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 application name. Visual Basic.NET Example: 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 admin user by default. As a result, you must initially log into WebFOCUS before using any Magnify-related functionality for the first time. To restore the default behavior found in previous WebFOCUS releases, you must now configure the public user separately to enable access to Magnify. WebFOCUS Upgrade Considerations 65

66 WebFOCUS Magnify 66 WebFOCUS

67 Customer Connections Where users partner with Information Builders to provide feedback and create quality documentation. Partner With Us Information Builders Technical Content Management team is comprised of many talented individuals 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 and services. 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 Michele_Brady@ibi.com. Request Permission to Use Copyright Material To request permission to repurpose copyrighted material, please contact Frances Gambino, Vice President, Technical Content Management at Frances_Gambino@ibi.com. Visit the Information Builders Technical Content Library To visit the Technical Content Library, go to

68 WebFOCUS Upgrade Considerations Release 8.0 Version 10 Information Builders, Inc. Two Penn Plaza New York, NY DN