Product Requirements for Using Active Technologies

In this section:

Reference:

In some cases, additional products are required in order to use Active Technologies.

Some product requirements and device support depend on the Active Technologies chart engine that you are using. The chart engine is set with the WebFOCUS StyleSheet ARGRAPHENGINE attribute in an active report procedure, or in the SECTION declaration of a compound layout report. For more information on the ARGRAPHENGINE syntax and settings for the chart engine, see Switching the Chart Engine.


Top of page

x
Reference: Active Technologies for Adobe Flash Player Installation Requirements

The following additional installations are required:


Top of page

x
Reference: Active Technologies for PDF Installation Requirements

In order to run an active report for PDF (APDF output format), Adobe Reader® 9.4.5 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.

For details on enabling Adobe Reader for Google Chrome™, Mozilla® Firefox®, and Safari® on Mac OS® so that you can view active reports for PDF in those browsers, see Viewing an Active Technologies Report for PDF in Adobe Reader.


Top of page

x
Mobile and Tablet Device Support Information

The following apply to Active Technologies.


Top of page

x
UNC Path Considerations

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. The Adobe Flex compiler does not support the use of a UNC (Universal Naming Convention or Uniform Naming Convention) path.

If the WebFOCUS Reporting Server is installed on a network share using a UNC path name, you must set the CLASSPATH to flex-compiler-oem.jar and mxmlc.jar on a mapped drive before starting the server.

For example, before calling edastart on a user PC, issue the following commands:

net use E: \\mypc\C$\ibi
set CLASSPATH=E:\srv77\home\etc\flex\lib\flex-compiler-oem.jar;
    E:\srv77\home\etc\flex\lib\mxmlc.jar


Top of page

x
Traditional MVS Considerations

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.


Top of page

x
Language Requirements

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 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.


WebFOCUS