Usage Considerations

Resolution of relative paths for some interfaces that use files as arguments

This version of the HCL Link resolves relative paths by appending the relative path to the directory of the currently running process. The following interfaces are affected:
  • Custom functions that use files as arguments
  • Adapter trace files in HCL Link for Integration Servers integrations
  • API implementations that open files after calling a map

For example, the following xmllib functions that can specify files as arguments are affected: 

xmllib->XSLTEX("ipo.in.xml", "ipo.xsl", "transform.log")
  • The first two arguments can be data or a file.
  • The third argument is always a file.
xmllib->XPATHEX("ipo.in.xml", "./order//item[1]/shipDate", "/ipo:purchaseOrders ", "xpathlog.txt")
  • The first argument can be data or a file.
  • The fourth argument is always a file.
xmllib-> VALIDATEEX(“ipo.in.xml”, " http://www.example.com/IPO  ipo.xsd", "numtotext.log"
  • The first argument can be data or a file.
  • The second argument is always a file (optionally prefixed by default name space).
  • The third argument is always a file.

In a multi-threaded environment relative paths are relative to the directory where the process was started.

For best results, use an absolute path for adapter trace files. You can use the GETDIRECTORY function to dynamically build an absolute path.

Native XML schemas with prologs must use XSD as the type of input card

When a native XML schema has a prolog, the Type setting of the main input card must be XSD (the root of the XML document). A parser error results when the XML schema has a prolog and the Type setting specifies a sub-element of the root.

As a general practice, use XSD as the Type setting in the main input card of all native XML schemas. The XSD setting parses correctly regardless of whether the schema includes a prolog.

For all Xerces type trees, use Doc XSD as the Type setting of the input card, regardless of whether the XML document has a prolog. Parsing errors can result if the XML document includes a prolog and you specify a sub-element of Doc XSD as the Type setting of the main input card.

Custom function memory allocation on Windows systems

Custom functions that run on Microsoft Windows systems must use the mpiMemMalloc and mpiMemRealloc memory management functions to allocate or reallocate the lpDataFromApp buffer.