Server Guide : Packaging server applications : Packaging a Smalltalk image : Packaging into image components : Packaging a dependent or leaf module
Packaging a dependent or leaf module
The procedure below describes how to package: a dependent module that uses a base module to run in a native server environment or under CICS Transaction Server, or a leaf module that uses a reusable module to run in a native server environment.
The starting point for the procedure is a clean image loaded with the ‘ST: Server Workbench, Base’ feature.
The procedure
•Creates a passive image in the development image
•Loads the project into the passive image
•Launches the packager control panel from the passive image
•Uses the packager to
•Create the packaging instructions and save them in a Smalltalk class in an ENVY Application.
•Create a reduced runtime image
 
Step 3: Making the passive image the current image
If you do not already have a passive image, add one by following these steps.
Make the passive image which you wish to use in packaging current by following this step.
Step 4: Loading your project into the passive image
To load your project into the passive image, click here
Tip icon
If you are packaging a CICS application that accesses IMS databases, ensure that the prerequisite IMS applications are loaded into the passive image.
Step 5: Producing the packaged dependent or leaf image
Note
If you are going to create new or alter existing packaging instructions, you should make sure the ENVY Application containing those instructions is an open edition in the developoment image BEFORE opening the packager in the passive image.
 
1. Open a Packager Control Panel.
2. Create a packaged image from a packaging instruction.
3. Add project to be packaged.
4. Specify how your project is launched.
5. Perform Reduce step to find unused components.
6. Examine packaging problems.
7. Fix packaging problems and reduce again, if necessary.
8. Optionally, alter the contents of the image using the Image Contents Browser.
9. Save your packaging instructions in memory or as Smalltalk code in the library.
10. Perform Output Image to produce the output image.
11. Version your new packaging instructions.
 
Last modified date: 05/11/2020