Using CORBA ORB implementations other than EAServer  Chapter 17: Creating PowerBuilder Clients

Chapter 16: Creating PowerBuilder Components

While PowerBuilder is not included with EAServer, the products are fully integrated and work well together. EAServer hosts the PowerBuilder virtual machine natively. This means that EAServer can communicate directly with PowerBuilder nonvisual user objects, and vice versa. EAServer components developed in PowerBuilder can take full advantage of the ease of use and flexibility of PowerScript® and the richness of PowerBuilder’s system objects.

The PowerBuilder IDE runs on Windows platforms, but you can deploy PowerBuilder components to EAServer on any platform for which a compatible PBVM is available, including most UNIX platforms. For more information, see the EAServer Release Bulletin for your platform.

The PowerBuilder IDE includes wizards to create EAServer components and deployment projects. While you can edit PowerBuilder component properties in EAServer Manager, you should use the PowerBuilder IDE instead. Changes you make outside of the IDE can be overwritten when you redeploy your project to EAServer from the IDE. For information on using the wizards, see the Application Techniques manual in the PowerBuilder documentation. If you must set additional component properties that cannot be set from the PowerBuilder IDE, consider creating a script or batch file that uses the jagtool set_props command to configure these additional settings. This allows you to maintain an automated deployment mechanism. For more information, see Chapter 12, “Using jagtool and jagant,” in the EAServer System Administration Guide.

PowerBuilder provides full-fledged support for EAServer component technologies, including:

For details on implementing components that use these features, see the Application Techniques manual in the PowerBuilder documentation.

Copyright © 2005. Sybase Inc. All rights reserved. Chapter 17: Creating PowerBuilder Clients