Packaging Runtime Applications
Use the following guidelines when packaging a client Smalltalk application that uses GemBuilder to access GemStone.
A.1 Prerequisites
In addition to code required by your application, the packaged image must contain the application or parcel GbsRuntime, which contains the system code modified for GemBuilder.
In order to ensure that your image initializes correctly, your application must specify GbsRuntime as a prerequisite.
Do not include the application or parcel GbsTools. These are subclasses of classes that will be deleted during the packaging process.
Names
Ensure that your image is packaged to include class pool dictionaries and instance variable names and does not remove them.
Replicating Blocks
To ensure that your application is able to replicate Smalltalk blocks in the same manner as it did in the development environment, we recommend that you include the compiler.
Defunct Stubs and Forwarders
Defunct stubs and forwarders cause problems during packaging. To avoid these problems, start with new client image as shipped from your client Smalltalk vendor.
Shared Libraries
A deployed runtime application that uses GemBuilder needs to contain all the server-specific shared libraries.
With 32-Bit GemStone/S, it must also include the error file english.err or englisxx.err (where xx is the release number).
The Installation Guide for the GemStone server product and version you are using will provide the specific names of the required library files.
If you are logging in only remote sessions, set the GemBuilder configuration parameter libraryName to the RPC version of the GemStone client libraries. Again, see the appropriate Installation Guide for the specific library names.