To write and test code for your ActiveX client, you must be connected to a server (or have the server running on your machine) and have the ActiveX runtime files installed on your machine. To install the ActiveX runtime files, see “Deploy the ActiveX client”; if you install EAServer on your machine, you have the option to install the ActiveX runtime files as well. For more information, see the EAServer Installation Guide.
Before invoking methods on component instances, the client must connect to a server and instantiate the components. There are two techniques for proxy instantiation:
Instantiating proxies using CORBA-style interfaces – This technique follows the CORBA client model. This technique is recommended for new development.
Instantiating stub instances using the EAServer 1.1 interface – This technique uses interfaces that introduced in EAServer version 1.1. These interfaces are provided for backward compatibility with existing clients.
If you currently have ActiveX proxy automation server clients, Sybase recommends that you migrate you current ActiveX clients to use the CORBA-style so that you can take advantage of the new benefits. The following features are available to CORBA style clients and not to EAServer 1.1 style clients:
Use the ORB, Session, Factory, and Manager objects and methods.
Configure ORB level properties.
Use high availability/load balancing features.
Use most SSL features.
Invoke Enterprise JavaBean components.
The ORB, SessionManager, and other CORBA-style interfaces are documented in Chapter 4, “ActiveX Client Interfaces,” in the EAServer API Reference.
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
