This section contains troubleshooting tips for problems that occur with graph or map image generation.
Trouble Displaying International Characters in Helvetica, Times, or Courier Fonts
Drilldown / Hover / Roll-Over Data Label Problems with PNG or JPEG Images
No Drilldown / Hover / Roll-Over Data Labels in PDF, EPS, and TIFF Images
Characters Not Displaying Properly in Strings Passed to Javascript* Function Through Drilldown
Drilldown, Hover, or Notes Not Appearing in Correct Place for X-Y, Time, or Pareto Graphs
Graph or Map Animations Slow and Choppy with Auto-Updating Turned On
To load or read a file or data source of any kind, Corda Server must be given permission to read data from the specified path or domain. By default, Corda Server has permission to read from <document_root>\image_templates; Corda Server can also read anything running on the localhost.
For more information on adding access permissions, see Setting Path Permissions.
Corda Server cannot load data (screen-scraping, HTML Tables, CSV files, etc.) through a proxy server. If you are loading data from a URL, but have to go through a proxy server to access that URL, Corda Server is unable to load that data.
Data that you send to Corda Server can differ dramatically from the sample data that was in an Image Template file. To compensate for this, Corda Server may need to resize objects and/or the Image Template file to prevent overlap. If you want to make sure that an object stays anchored to the same place that you put it in Corda Builder, use Corda Builder’s anchoring feature (see Anchoring Objects in the Corda Builder User Guide).
The following attributes of the ITXML Chart property control Corda Server’s automatic resizing of Image Template files: AutoResize, FitInBounds, and CollisionProtection. For example, the following Chart property disables all of Corda Server’s resizing capabilities:
<Chart Version='4.0' AutoResize='No' FitInBounds='No' CollisionProtection='No'>
Corda Builder also lets you disable automatic resizing in an Image Template file. For more information, see Object Resizing and Repositioning in the Corda Builder User Guide.
Corda® 7 supports international characters only through the pre-installed Lucida font set, or through imported custom fonts. The Times, Helvetica, and Courier font sets do not provide international character support.
For information about custom fonts, see Fonts and Languages.
Some fonts are unable to display certain characters. Helvetica, for example, is limited in the number of characters beyond 255. Change the font that is selected for that text to another font, such as Lucida Sans. With international characters, you may need to create a custom font for Corda 7 by using the Corda Font Converter. This also helps with double-byte characters.
For information about custom fonts, see Fonts and Languages.
If this problem is occurring in images generated by Corda Server, make sure that you have installed the custom font on the computer running Corda Server. Designers sometimes create custom fonts on their own systems, but forget to upload them to the server. Although the font may be available to a designer in Corda Builder, Corda Server doesn't know anything about the font and reverts to the default font instead.
If this problem is occurring in an Image Template file you are working on in Corda Builder, it probably means that the person who created the Image Template file was using fonts that you don’t have. Please contact the person who created the Image Template file and obtain those fonts.
For more information about uploading or installing fonts, see Installing Custom Fonts.
These features are not supported in PNG or JPEG images without using the Corda Embedder.
Certain browsers, including browsers older than Netscape* 4, Internet Explorer 4, or Opera 7, are unable to display any interactive features such as hover text and drilldown effects in PNG or JPEG images. Some browsers, including Netscape 4.x, provide only limited interactivity via image maps.
By default, these features are supported in PNG and JPEG images via Javascript. If Javascript is disabled on the Web browser, these features are supported by image maps. If you have disabled Javascript hover in the Image Type section of Corda Server Administrator, these features are also supported by image maps.
When these features are supported by image maps, feedback (i.e., response time between mousing over a data item and seeing the associated hover/rollover text) is slow, and you cannot customize the appearance of rollover data labels and hover text. In Netscape browsers, you may be unable to get hover text without also enabling a drilldown effect for the specified data item.
These features are not supported in PDF, EPS, and TIFF images.
HTML data table output is only supported in Corda 7 Enterprise.
HTML data table output is not supported using the HTTP request method.
Corda Server cannot load data (screen-scraping, HTML tables, CSV files, etc.) through a proxy server. If you are loading data from a URL, but have to go through a proxy server to access that URL, Corda Server is unable to load that data.
By default, Corda Server URL-encodes all drilldown effects. In other words, drilldown strings are encoded in such a manner that browsers can properly interpret the intended drilldown destination.
Unfortunately, this creates a problem when the intended target of the drilldown effect is a Javascript function instead of a URL. Corda Server may URL-encode characters that should be Javascript-encoded instead. Since Javascript functions do not recognize URL encoding, the characters display improperly.
This situation is further complicated by occasions when strings in Javascript functions should be URL encoded, because the string is eventually interpreted by a browser as a URL. Because this is often the case, Corda Server cannot simply attempt to detect whether the target is a URL or a Javascript function. Therefore, it just assumes that it should encode it as a URL.
Anytime a drilldown effect passes a string containing a character higher than 128 (0x7F) through a Javascript function and this string is not supposed to be interpreted as a URL, the string is not interpreted properly. To get around this, use the %_JS_ENCODE macro. This macro instructs Corda Server to Javascript-encode the drilldown effect rather than URL encode it. It should be included at the end of any drilldown effect that needs to be Javascript-encoded.
For example, the following drilldown effect does not display correctly. Instead of Group ™, you see Group %e2%84%a2.
javascript:alert("Category: Group ™")
However, by adding the %_JS_ENCODE macro to the end of the drilldown effect, you can correct the problem:
javascript:alert("Category: Group ™")%_JS_ENCODE
Note that you would not want to use this macro if your string was to be interpreted as a URL, as in the string below, because Group ™ needs to be interpreted as Group %e2%84%a2 so the browser can properly recognize it.
javascript:window.open("http://test.com/?cat=Group ™")
In graphs where data is sorted (Pareto, or X-Y and Time graphs where the Graph Settings > Sort attribute is enabled in Object Properties), the target “category” for hover text, drilldown, and notes is enumerated by sort order rather than list order. Because of this, you may experience unexpected behavior when using these features with the specified graph types.
At present, there is no workaround for this problem when producing static graphs in Corda Builder. The only option is to disable sorting in X-Y and Time graphs by unchecking the Sort Data option.
Work around this problem by targeting data items by sorted order. Furthermore, when using Pareto graphs, identify target categories by name instead of number.
The automatically updated image feature in FLASH is not compatible with animations.
On some browsers you may experience caching problems with auto-updating FLASH images. To get around these problems, be sure to set the Content Expiration header for each FLASH image you load to expire immediately. For more information, see Solving Caching Issues with Auto Updated FLASH Images in the Corda 7 Developer Reference.
Corda Server requires access to a Java* AWT, X Server, or Virtual Frame Buffer to handle bitmap-based images (including JPEG, PNG, and TIFF). See Corda Server and the Java AWT for details.
For the Corda Server Servlet to render bitmap-based images (jpeg, png, or tiff), the Web application server on which it is installed must have an enabled AWT rendering environment.
Unfortunately, this environment may not be enabled or installed for some application servers. If the application server is running with Java 1.4 and later, activate it by modifying the Java startup parameters so that Java is run in Headless AWT mode. For example, to enable this in WebLogic, modify the script or program that launches WebLogic so that the java process it runs has the command line parameter:
-Djava.awt.headless=true
With other versions of Java, install an AWT rendering environment, such as ETek’s Pure Java AWT (see Corda Server and the Java AWT).
Consult the Web application server’s documentation for further detail about enabling an AWT rendering environment.