This section contains troubleshooting tips for problems that occur when using the Corda® Embedder.
Corda Embedder Does Not Work with ColdFusion* MX on Windows*
Having Trouble Knowing What Values to Assign externalServerAddress and internalCommPortAddress
Microsoft VBScript Compilation: Cannot Use Parentheses When Calling a Sub
Characters Not Displaying Properly in Strings Passed to Javascript* Function Through Drilldown
You may receive this error for one of two reasons:
You're assigning the wrong address for the Corda Embedder internalCommPortAddress. For more information, see Comm Port Address in the Corda 7 Developer Reference.
The Corda Server has not been started or failed to start correctly. For more information, see Starting Corda Server.
If you receive a File not found error after clicking on a Highwire™ link, it is most likely because you're assigning the wrong address for the Corda Embedder externalServerAddress. For more information, see Server Address in the Corda 7 Developer Reference.
If the Web application you created returns a server error instead of the Web page you were expecting, first make sure that the Web application works without the code you inserted for the Corda image.
If the Web application works without the Corda Embedder code, you may have a syntax error in the Corda Embedder code. Review the code carefully to make sure it contains no syntax error. The error log and/or documentation for the Java* Application Server can help you locate syntax errors.
If there are no syntax errors, it is possible that you are not properly importing the Corda Embedder library into the Web application or that you have not installed the Corda Embedder at all. For instructions on importing and installing Corda Embedder, review the section in Using Corda Embedder that corresponds to your Web environment.
If you are using ColdFusion MX on Windows, be sure you have updated the server to the latest version using the ColdFusion MX Updater Release 1. This is available at http://www.macromedia.com/support/coldfusion/releasenotes/mx/releasenotes_mx_updater.html. Apply this update to fix a bug in ColdFusion MX that prevents it from accessing Window's Component Object Model (COM).
Setting the height and width attributes when using ColdFusion MX with the COM Corda Embedder causes an error because of a bug in ColdFusion MX that does not allow the passing of integers to a COM object. To work around this, Corda Technologies has added two string attributes, height4MX and width4MX, in the COM Object to use instead. For example:
myImage.height4MX = "350";
For more information, see Identifying Server Addresses in the Corda 7 Developer Reference.
This problem occurs when you accidentally use a semi-colon at the end of a line in VBScript. You may run into this problem when using the Corda Embedder with Active Server Pages (ASPs).
Active Server Pages use VBScript, whose syntax requires that you do not have a semi-colon at the end of a line of code. Since other languages either require a semi-colon or are indifferent, most of the example code in this documentation uses a semi-colon at the end of each line of code. Remove any semi-colons from example code if you use it in ASP.
For example, this line of code is invalid in ASP:
myImage.imageTemplate="bar.itxml";
This line of code is valid:
myImage.imageTemplate="bar.itxml"
This problem occurs when you accidentally use incorrect VBScript syntax for a method that does not return a value. You may run into this problem when using the Corda Embedder with Active Server Pages (ASPs).
VBScript syntax requires any functions that do not return a value (void methods) to not have parenthesis around the parameters.
For example, the addHTMLTable syntax is:
myImage.addHTMLTable("graph","title");
This syntax is perfectly valid in every language except VBScript. In ASPs, use the following syntax:
myImage.addHTMLTable "graph", "title"
For experienced ASP developers, this is an obvious conversion process.
This error can occur for one of two reasons:
The Corda Server has not been started or has failed to start correctly. For more information, see Starting Corda Server.
The HTML code does not properly reference the Corda Embedder library. Make sure that you load Corda Embedder through a script tag.
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 cannot load that data.
By default, Corda Server URL-encodes all drilldown effects so that Web browsers can properly interpret the intended drilldown destination.
Unfortunately, this creates a problem when the intended target of a 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, Corda Server assumes that it should encode the Javascript function as a URL.
Anytime a drilldown effect passes a string containing a character higher than 127 (0x7E) 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 is not displayed 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
You don't want to use this macro if the string is to be interpreted as a URL, as in the string below. This is because Group ™ needs to be interpreted as Group %e2%84%a2 in order for the browser to properly recognize it.
javascript:window.open("http://test.com/?cat=Group ™")
Make sure that you are targeting map layers by the correct layer name. Also, make sure that you have defined ranges for the map.
To save to a path on the computer running the Web application server, use saveToAppServer. Make sure that the path specified in the first parameter is an absolute path. Also, make sure that the directory actually exists and that write permissions are granted to the user running the application.
Note: This command is not related to path.xml settings.
Try setting Corda Embedder's isPostRequest attribute to true.