Deploying the client application

Packaging your application

The procedure for deploying
a client application in a distributed computing environment is more
or less the same as the procedure for deploying any other PowerBuilder
application. You have two basic ways to package your client application:

• As one standalone
  executable (EXE) file that contains all the objects in the application
• As an executable file and one or more dynamic libraries

You might also need to provide some additional resources that
your application uses, such as bitmaps and icons. You can provide
resources in your executable and/or dynamic libraries,
or you can distribute them separately.

Remote object class definitions

Each remote object contained in a server application has a
corresponding class definition in the client application. The class
definitions on the client can contain the complete implementation
of the remote object, or just a representation of the remote object’s
interface.

For distributed processing, only the remote object’s
interface is required on the client. However, if you want to have
the option to instantiate these objects locally at execution time,
you need to deploy the complete implementation on the client.

For complete instructions on creating an executable
version of your application, see the PowerBuilder User’s
Guide
.

---