x

The following additional installations are required:

• An active report for Adobe Flash Player is generated using a Java®-based compiler engine that comes with Adobe Open Source Flex® SDK included on the WebFOCUS Reporting Server. JSCOM3 is a listener installed with the WebFOCUS Reporting Server that is used when the server compiles an active report for Adobe Flash Player. Ensure that the JSCOM3 service is started on the WebFOCUS Reporting Server and that enough memory for Java is allocated to the JSCOM3 service by setting the Maximum Java Heap Size. The recommended Maximum Java Heap Size is 512 megabytes.

  For more information, see the WebFOCUS and ReportCaster Installation and Configuration for Windows manual.

• In order to run a report created using the active report for Adobe Flash Player (FLEX) format, Adobe Flash Player 10 or higher is required. If your machine does not detect a Flash Player, you will be prompted to download a Flash Player. If an older version of Flash Player exists, you will need to upgrade.
• If there is no valid license for Active Technologies, the report output displays the text Active Technologies Trial Version above the data, and charts display the text in the background of the chart image.
• In order to use the Chart option in the active report for Adobe Flash Player output, a valid license for Flex® Builder™ 3 Professional is required. If there is no valid license, the charts will display a Flex Data Visualization Trial watermark across the chart image.

  If Flex Builder 3 Professional is already installed on your machine in the same location as your WebFOCUS Reporting Server, it automatically looks for the license in the license.properties file in the Flex Builder 3 Professional application data folder.

  If you have a valid Flex Builder 3 Professional license but Flex Builder 3 Professional is not installed on the same machine where the WebFOCUS Reporting Server is installed, you can enter the 24-digit Flex Builder 3 Professional license number in the licenses section of the flex-config.xml file, along with the Flex Builder 3 Professional product name in lowercase, as flexbuilder3, found in the \home\etc\flex\frameworks folder. Make sure that the licenses section of the flex-config.xml file is not commented out. Save the flex-config.xml file and run the procedure. The compiled SWF file, which is Adobe Flash Player compatible, no longer displays the trial message across the chart image.

• The following browser setting is required to prevent a script error when opening an active report for Adobe Flash Player file in Internet Explorer.
  • In Windows Internet Explorer 7, or Internet Explorer 6 in Windows Server 2003 Service Pack 2, click Internet Options from the Tools menu.
  • Select the Advanced tab.
  • Scroll to the Security section and ensure that Allow active content to run in files on My Computer is not selected.
  • Click OK to close the Internet Options dialog box.

x

Adobe Reader® 9 or higher is required so that the Adobe Flash Player run-time code included in the Adobe client can render the SWF content compatible with Adobe Flash Player.

x

An active report for Adobe Flash Player is generated using a Java-based compiler engine that is included with the Adobe Open Source Flex SDK for the WebFOCUS Reporting Server. There is a known issue with the Adobe Flex compiler not working properly with the IBM® version of Java.

Active Technologies for Adobe Flash Player require one of the following when using IBM Java:

• A version of IBM Java 1.5.
• IBM Java 1.6.0 SR4 only.

  IBM Java 1.6.0 SR1 through SR3, and SR8 and higher, throw a Java Exception error.

Also, there is a conflict between the version of Xerces that Flex uses and the one that is included with the IBM JVM. As a work-around, ensure that the JVM loads the version of Xerces supplied with Flex instead of the version supplied with the IBM JVM.

Make sure that the Flex compiler uses the xercesImpl.jar file that is provided in the Flex library folder under the ibi folder. Add the following syntax to the user ID profile that starts the WebFOCUS Reporting Server:

export CLASSPATH=/ibi/srv77/home/etc/flex/lib/xercesImpl.jar:$CLASSPATH

You must set this value in the CLASSPATH since the Flex compiler does not read the IBI_CLASSPATH when it is executed.

x

z/OS (traditional MVS) users running under PDS deployment must allocate their temporary HTML data sets so that the data sets have a wider LRECL to use HOLD FORMAT AHTML syntax.

x

On some UNIX® systems, such as Linux and Oracle® Solaris, the system locale may be set by default to a UTF-8 encoding value, such as en_US.UTF-8.

Unless you are running the WebFOCUS Reporting Server in Unicode, this setting causes JSCOM to run in UTF-8 mode and corrupts the buffer.

On these systems, you can check the language that is set by typing:

locale

Make sure that the setting reflects the language that you are planning to use on the WebFOCUS Reporting Server. For example, if the WebFOCUS Reporting Server is set to 437 English only, make sure that the server is started with the correct English system locale.

You can add the LANG setting to the edastart shell script, or you can add it to the profile of the user ID that starts the server. For example, add the following to set the language to English on Linux:

export LANG=en_US.iso88591

On Oracle Solaris, you need to set LC_ALL, in addition to LANG. For more information, contact your UNIX administrator.

If data in active reports contains National Language Support (NLS) characters, you must configure the server for NLS in order to display the correct characters. For more information, see the WebFOCUS Server Administration for UNIX, Windows, OpenVMS, IBM i, and z/OS manual.

The Web server must support NLS file names if you are using NLS characters in an swf file name. For example, Tomcat standalone does not support the use of NLS file names.