Converting a resource file during import
To easily import resource files such as custom code lists into the SPE database, you can supply a custom map. The map runs during the import process to convert your resource file to XML format for use in SPE.
- If importing a WebSphere® Transformation
Extender map
to use for file conversion, you must copy these files and variables:
- Copy the WebSphere Transformation Extender JAR files dtxpi.jar, m4spe.jar and xds4j.jar from the WTX_install_dir/jars directory to the spe_install_dir/spe.war/WEB-INF/lib directory.
- Copy these WebSphere Transformation
Extender environment
variables to the server.env file:
- LD_LIBRARY_PATH
- LD_PRELOAD
- DTX_HOME_DIR
- DTX_TMP_DIR
- SPE_INSTALL_DIR
This must be done before SPE is started.
- Write or obtain a custom map that describes the import data. Test your map to ensure that it is valid (that is, a map that conforms to the SPE schema) and gives valid output. Compile the map and, if you anticipate converting your file through the SPE Trading Partner UI, import it into SPE.
You can use a custom map to convert a resource, such as
an imported code list, from an Excel spreadsheet, positional, comma-separated
(CSV) file, or subscription-based format (RSS feed) to the XML format
used by SPE. This allows resources from other sources to be
used easily in SPE. These map types can be used:
- WebSphere Transformation
Extender with one
input and output {out1, Card1}Note: SPE uses the convention in1 and out1.
- Sterling B2B Integrator
- XLST
Import and convert your file by using either of these methods:
| Option | Description |
|---|---|
| Through the SPE Trading Partner UI |
|
| From the command line | See the speimport command. Note: With this option, you
do not need to import the map file in advance. An option is available
to import the map file when the command is executed.
|