spedeploy-packs
The spedeploy-packs command is used to deploy SPE pack configuration files and resources from the Windows machine where they were installed to a target runtime system.
It can also be used to deploy configuration files only, or to redeploy packs after a database change.
(Linux™ and UNIX™)
spedeploy-packs.sh -j /source_filepath/pack_filename.jar -d /wtx_target_filepath [-t=tenant_ID]Example:
spedeploy-packs -j spe_edi_pack_for_windows_WTX_64bit.jar -d "/IBM/WebSphere Transformation Extender 8.4.1 64bit"(Windows™)
spedeploy-packs -j \source_filepath\pack.jar -d \wtx_target_filepath [-t=tenant_ID]Example:
spedeploy-packs -j spe_edi_pack_for_windows_WTX_64bit.jar -d "/IBM/WebSphere Transformation Extender 8.4.1 64bit"- -j
- Full path to the SPE resource bundle file. Valid values: pack, nojar
- pack
- File name for the resource bundle file. Format: spe_packname_platform_bit.jar
Example: spe_edi_pack_for_windows_WTX_64bit.jar
- nojar
- Indicates that only pack server components are deployed. Other resources are not deployed.
- -d
- Full path to the target directory ( WebSphere® Transformation Extender installation). Valid values: pathname, nowtx
- nowtx
- Indicates that WebSphere Transformation Extender is not installed, or, if installed, WebSphere Transformation Extender validation maps are not being used. Less commonly, WebSphere Transformation Extender is installed but used for transformation operations only.
- -t
- Indicates the tenant ID under which resources should be imported. If not specified, it defaults to the DEFAULT tenant. Optional.
Results
When the script completes successfully:
- The database is initialized.
- Depending on the options selected, SPE and pack configuration files and resources such as business rules, code lists, envelopes, maps, schemas and XSLT files are loaded and updated.
- A message is displayed. Example:
Pack files were deployed, configured, and loaded successfully.