Navigation:  Programming Cookbook > Deploying Applications >

Deployment Strategy

Previous pageReturn to chapter overviewNext page

The first step is to create a new RuntimeSessionManager subclass that instantiates the application as part of its start-up processing. This is done by overriding the #main method.

When deploying the application the package is simply selected in the Package Browser and the Deployment can wizard is invoked by right-clicking on the desired package and clicking on the Deployment/Deploy Executable command. One of the steps in configuring the ImageStripper allows the selection of the session manager that will be installed during deployment and it is here that the new RuntimeSessionManager subclass is specified.

Tip: the deployment process saves the development image just before it starts. This ensures that when you restart it, it is in the same state as it was before image stripping.

When creating a new RuntimeSessionManager note that:

Using the #getCommandLine method of SessionManager can be useful in to configure how an application will behave depending on parameters supplied on the command line.
It is also possible to override the #onUnhandledError:, #onUnhandledWarning: and #onUnhandledNotification: methods in any RuntimeSessionManager subclass that you create. This will give control over how such events are dealt with.