EAServer 6.0 has a new property for packages and two new properties for components:
com.sybase.jaguar.package.java.package com.sybase.jaguar.component.roles com.sybase.jaguar.component.webservice
The EAServer wizards and the Project painter Properties dialog box have new fields where you can set these properties. If you are using an earlier version of EAServer, the values you specify in these fields are ignored.
You can deploy components as EAServer 5.x Web services, as in previous releases, or as EJB 2.1 Web services. For use with EAServer 6.0, select EJB 2.1 Web services.
For a package named mypkg, the default Java package name is mypkg.ejb. To specify a different package name, enter it on the Specify Package Name page in the wizard or the General page in the Project painter. You must specify a Java package name if you plan to deploy the component as an EJB 2.1 Web service.
You can specify one or more security roles for a component in the wizards. You can specify security roles for all the components in a project on the Components page in the Properties dialog box in the Project painter.
In EAServer 6.0, PowerBuilder® components are wrapped as EJBs. For a table mapping PowerBuilder datatypes to EJB datatypes, and for more information about building PowerBuilder components and clients for EAServer 6.0, see the CORBA Components Guide in the EAServer 6.0 core documentation set on the Sybase Product Manuals Web site.
Changes have been made in the user interface to extend features originally used only with EAServer for use with other application servers. The EAServer Profiles dialog box has been renamed “Application Server Profiles” and can now be used to specify profiles for other servers. The Application Servers folder on the Components page in the System Tree displays all the application server profiles you have created.
Building EJB client applications for EJBs running in EAServer 6.0 requires you to take some additional steps when you create the EJB client proxy and when you create the client.
To generate a proxy for an EJB deployed to EAServer
6.0:
Copy the packagename directory from the %DJC_HOME%\deploy\ejbjars\ directory on the server to the client computer, where packagename is the package that contains the EJB you want to use.
Add this directory to the Classpath on the Select EJB Component dialog box in the EJB Proxy Project painter.
Generate the proxy.
To create an EJB client application for an EJB
deployed to EAServer 6.0:
Copy the eas-server-14.jar file (or eas-server-15.jar if you are using JDK 1.5.x) from the %DJC_HOME%\lib directory to the client computer and include its full path in the client’s classpath.
Copy the stub files from %DJC_HOME%\genfiles\java\classes\ directory to the client computer and include this path in the client’s classpath.
Copy the packagename directory from the %DJC_HOME%\deploy\ejbjars\ directory on the server to the client computer, where packagename is the package that contains the EJB you want to use, and include this path in the client’s classpath.
If you copied these files and directories to a directory on the client called EAServer6, and you want to use an EJB in the datamapping package, the client classpath setting might look like this:
Classpath=D:\EAServer6\lib\eas-server-14.jar;D:\EAServer6\genfiles\java\classes;D:\EAServer6\deploy\ejbjars\datamapping
