ITX pack deployment scenario 1a: Deploy all pack files from a design system

This scenario is the most common approach to deploying ITX industry packs on ITXA from a design system.

By installing the design components on a Windows system, you can use the type trees, sample maps, and other design components to create and customize maps for use in ITXA. You can also create the resource bundle (jar file) from the design system, and deploy it to the ITXA run-time system.

Important: The IBM generated pack resource bundle is currently only available with the Financial Pack version 9.0.2. For other ITX packs, creating the resource bundle from a design system is the only way to deploy the pack. Creating the resource bundle from a design system also allows you to create platform-specific compiled maps, which are smaller than the multiplatform compiled maps that are included in the IBM-generated pack resource bundle.

This procedure assumes that you have installed the following:

On each design system (Windows platform only):
- SPE server and design components
- One or more industry packs (server and design components)
On each SPE runtime server:
- WebSphere® Transformation Extender
- SPE server components

Note: You do not need to install the pack on the SPE runtime server for this scenario.

This scenario applies in these situations:

You want to use WebSphere Transformation Extender maps for HIPAA, EDI, or SWIFT/SEPA compliance checking.
You prefer to install SPE packs on a single design system, and deploy all files from there.
You plan to use the same system for both design and runtime functions, such as for a Windows test or demonstration system.
You are running SPE on a z/OS® platform.

On your design system, perform these steps:

Generate an resource bundle file for each pack. Enter this command:
```
speresource-packedi|packhc|packfsp -platform=platform -bits=31|64 -resource=pack
```
Example:
```
speresource-packhc -platform=windows -bits=64 -resource=pack
```
See the speresource-pack* command topic for details, including available platforms and other parameter values.
Result:
- The script compiles pack resources and generates a resource bundle file for each pack.
- A message such as the following is displayed:
  Please transfer the C:\IBM\Standards Processing Engine version\spe_hc_pack_for_windows_WTX_64bit.jar to the target SPE server and execute the spedeploy-packs script.

On each runtime server, perform these steps:

Use FTP or another file transfer method to copy the resource bundle file from your source system to the target runtime system.

Note: Omit this step if the same Windows system is used for both design and runtime.
Start the SPE database.
On each runtime system, deploy one or more pack bundles with this command:
(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_linux_WTX_64bit.jar -d /IBM/wtx900 
```
(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 "C:\IBM\WebSphere Transformation Extender 9.0.0"
```
-j

Full path to the SPE resource bundle file

pack

File name for the resource bundle file. Format: spe_packname_platform_bitversion.jar
Example: spe_edi_pack_for_windows_WTX_64bit.jar

-d

Full path to the target directory ( WebSphere Transformation Extender installation)

-t

Indicates the tenant ID under which resources should be imported. If not specified, it defaults to the DEFAULT tenant. Optional.

This command extracts the files, loads the database, and updates the configuration.
When the script completes successfully:
- The database is initialized and SPE and pack configuration files and resources (code lists, generic acknowledgment envelopes, and so on) are loaded.
- A message is displayed. Example:
```
Pack files were deployed, configured, and loaded successfully.
```
Stop and restart any applications that use SPE, including the SPE console window. This allows the application or console window to detect the updated environment.