The high level CORBA development and deployment process for EAServer is:
If you are using C++ or Java, define the component interfaces in CORBA IDL and deploy the IDL to the EAServer repository. Chapter 3, “Using CORBA IDL,” describes how to do this.
If you are using PowerBuilder, you can define interfaces with the PowerBuilder IDE. PowerBuilder generates IDL when you deploy to EAServer.
Create EAServer entities to define the CORBA packages and components. The package and component properties specify the component interfaces and control interaction between EAServer and your implementation. Chapter 4, “Managing CORBA Packages and Components,” describes how to define and configure CORBA packages and components.
Develop the component implementation classes and deploy them to EAServer. For more information, see:
The PowerBuilder IDE documentation and online help
Run the jaguar-compiler command on the CORBA packages to generate the code and EJB wrapper components required to run the components in EAServer. You can do this several ways:
From the PowerBuilder IDE, if using PowerBuilder.
From the Management Console as described in “Refreshing CORBA packages in the Management Console”.
Using a configuration script, as described in “Managing CORBA packages with configuration scripts”.
Using the jaguar-compiler command-line tool, as described in Chapter 12, “Command Line Tools,” in the System Administration Guide.
Create the client code to invoke the component methods. You can call CORBA components from any other client model, including EJB clients and Web components. For details on CORBA client models, see:
