Limitations of DataPower SOA appliances

DataPower SOA appliances do not support all of the features of Map Designer. Some features are not available and the ability to use map and card settings is limited. The limitations on DataPower maps are listed here. For limitations on DataPower SOA appliances, see the DataPower release notes.
Map settings
DataPower SOA appliances support all map settings except MapTrace. For the WorkSpace setting, they support only the Memory value.

The mapping process sets the Switch setting for MapTrace to OFF, and the WorkSpace setting to Memory, and then runs the map by using those values. It also overrides the MapAudit and Warnings settings that are based on the settings on the WebSphere DataPower SOA Appliance.

If the TX Audit Log map audit setting is enabled on the WebSphere DataPower SOA Appliance, that setting overrides the Switch setting for MapAudit to ON and the AuditLocation setting to Memory. If the map audit setting is not enabled on the Appliance, the mapping process sets the Switch setting for MapAudit to OFF. The mapping process generates the map audit log based on the map audit setting on the Appliance.

If the Support TX Warnings map warning option is selected on the WebSphere DataPower SOA Appliance, the mapping process uses the values that you set for the Warnings property in the map settings. If the warning setting is not selected on the Appliance, the mapping process on the Appliance handles all map warnings as failures, unless the Warnings > Return setting is specified as Ignore. When you specify Warning > Custom, the mapping process on the Appliance handles those map warnings that are set as Warn or Fail as failures, while those map warnings set as Ignore, are ignored. To be able to use the Restart attribute and the REJECT function, the map warnings setting must be specified as Ignore. At run time, when the map detects invalid objects, it ignores them and continues processing.

To read about how to enable or disable map audit and warning settings on DataPower SOA appliances, see the DataPower documentation. For information about how to run a DataPower map locally, see Running locally.

Card settings
DataPower SOA appliances support all card settings except the Backup setting. The mapping process sets the Switch setting for Backup to OFF for all of the input and output cards of a map. Then, the mapping process runs the map with that setting turned off. For information about how to run a DataPower map locally, see Running locally.

The mapping process sets the DocumentVerification setting to Well Formed for all input cards of the map and then runs the map with that setting. It calls the external parser for document verification only for the well-formed document. So there is no external schema validation for DataPower maps.

Map Designer features
The following Map Designer features are not available for use with DataPower maps:

For information about how to run a DataPower map locally, see Running locally.

Functions
Custom functions cannot be used in DataPower maps. In addition, DataPower SOA appliances do not support the following functions:
  • DBLOOKUP
  • DBQUERY
  • DDEQUERY
  • EXIT
  • GET
  • GETANDSET
  • GETDIRECTORY
  • GETFILENAME
  • GETRESOURCENAME
  • JEXIT
  • PUT

The unsupported functions that are listed previously are applicable to both map and component rules.

XML functions
DataPower SOA appliances appliances support the use of the following XML functions in map rules in DataPower maps:
  • XPATH
  • XSLT
  • XVALIDATE

The above XML functions may need access to resources located either on the appliance or that are remotely accessible to the appliance. The resources referenced in the functions include XML, XSL, or XSD files. DataPower SOA appliances use their own methods to process these functions in the map rules.

Absolute resource paths can have only Uniform Resource Locators (URLs) that start with local:///, store://, http://, or https://. Resources that are on the DataPower SOA appliances can be accessed by the appliances through URL paths that start with local:/// or store://. Resources that are located remotely can be accessed through URL paths that start with http:// or https://.

Relative resource paths are resolved by the mapping process, which appends the relative path to the absolute path of its parent map. Relative resource paths of the top-level map are resolved based on the working directory that is set by the DataPower SOA appliance for the top-level map. If you specify relative paths that contain the parent directory (..) notation, which is not valid for DataPower SOA appliances, the mapping process returns an error.

DataPower maps also support paths that start with current://. Resource paths starting with current:// are run like the relative resource paths defined above. Therefore, current:// equates to the . (current directory) notation in relative paths and is substituted with the parent map path during transformation. DataPower maps do not support file:// URL paths in the XML functions.

Since DataPower SOA Appliances use their own methods to process these XML functions, map runtime behavior differences may occur when running DataPower maps on an appliance against running them locally on the system. Errors reported with the LASTERRORMSG function may differ for appliance and local runs of DataPower maps.

For information about how to run a DataPower map locally, see Running locally. To read about the functions, see the related topics in the Functions and Expressions documentation.

Resource adapters
DataPower SOA appliances support the following IBM Transformation Extender resource adapters:
  • ECHO
  • FILE
  • SINK
  • STATIC FILE

The FILE and SINK adapters are the only target options available for output. The ECHO, FILE, and STATIC FILE adapters are the only source options available for input. IBM DataPower SOA Appliances do not support the other IBM Transformation Extender resource adapters.

RUN maps
DataPower SOA appliances support the use of the RUN function in map and component rules in DataPower maps, but with specific limitations.
All of the limitations that are described in this Limitations topic apply as well to RUN maps. Here are more limitations that apply only to RUN maps.
  • If the map input source and output target cards specify adapters other than ECHO, SINK, or STATIC FILE, you must use the -IE, -OE, or -OASINK command-line options to override the adapters. You can use the ECHOIN or HANDLEIN functions to override the adapters in the map input source cards. If you do not override the input source or output target adapters that are not supported for RUN maps, for example, the FILE adapter, the mapping process returns Source not available (12) or Target not available (9) errors.
  • The following commands and command options are ignored:
    • -T (MapTrace) command
    • -W (WorkSpace) command
    • K (Backup) option with -OASINK command
    • EN, EA, EF, ES (DocumentVerification) options with -IE, -OE, or -OASINK commands
    • U, +, !+, ={file|dir} options with -A (MapAudit) command
  • The map audit log is generated only when both of the following settings are specified:
    • The MapAudit setting is set to ON, either with the MapAudit > Switch map setting that is set to ON or with the -A (MapAudit) command line that is specified along with options.
    • The TX Audit Log map audit setting is set on the DataPower SOA appliances.
  • Absolute map paths can have only Uniform Resource Locators (URLs) that start with local:///, store://, http://, or https://. Maps that are on the DataPower SOA appliances can be accessed by the appliances through URL paths that start with local:/// or store://. Maps that are located remotely can be accessed through URL paths that start with http:// or https://.
  • Relative map paths are resolved by the mapping process, which appends the relative path to the absolute path of its parent map. Relative RUN map paths of the top-level map are resolved based on the working directory that is set by the DataPower SOA appliances for the top-level map. If you specify relative paths that contain the parent directory (..) notation, which is not valid on DataPower SOA appliances, the mapping process returns Could not open map(3) error.

For information about how to run a DataPower map locally, see Running locally. To read about the execution commands, and the command availability, which lists the commands that are valid with the RUN function, see the related topics in the Execution Commands documentation.

Database Interface Designer
The Database Interface Designer is only available for use with IBM Transformation Extender maps. DataPower SOA appliances do not support IBM Transformation Extender database adapters.

Integration Flow Designer
The Integration Flow Designer is only available for use with IBM Transformation Extender maps. DataPower maps within a map source file are not visible in the Integration Flow Designer.

Resource Registry
The Resource Registry is only available for use with IBM Transformation Extender maps. DataPower maps do not support resource aliases in map settings, card settings, and map rules. Resource configuration (.mrc) files and Resource name (.mrn) files created by using the Resource Registry are not supported on DataPower SOA appliances.

Enterprise Application Packs and Industry Packs
DataPower SOA appliances do not support the IBM Transformation Extender Enterprise Application Packs.

For the latest information, see DataPower SOA appliances support of IBM Transformation Extender Industry Packs.

For information about a specific release of the Industry Packs, see the IBM Transformation Extender release notes.

WSDL Importer
DataPower SOA appliances do not support the HCL Transformation Extender Web Services Description Language (WSDL) Importer.

Map runtime behavior differences
Maps that are run on a WebSphere DataPower SOA Appliance behave differently from maps that are run on other platforms on which IBM Transformation Extender maps run. The mapping process behaves differently in the following ways:
  • Processes the NULL value in a character text item for XML types, which are specified in the type tree with the Intent property set to XML, as an invalid character.
  • Processes the year 0000 value in the Date & Time item as an invalid date.
  • Overrides map and card settings before it runs the WebSphere DataPower maps. See Map settings and Card settings.
  • Processes some of the XML functions with its own methods. For more information, see XML functions.
Tip: If you abide by these limitations, you can initially create your maps by using the standard IBM Transformation Extender run time to take advantage of features such as the Map Debugger and Profiler. When your map unit testing is successful, you can then change the runtime setting to WebSphere DataPower and proceed to build and run the maps. For information about how to run a DataPower map locally, see Running locally.