Appendix A: Using EJB 1.0 JAR Support
Importing an EJB 1.0 JAR file
This feature is provided for backward compatibility with previous EAServer versions and any EJB 1.0 servers. To import the JAR file:
Start EAServer Manager if it is not already running, and connect to the server where you want to install the component.
Highlight the top-level Packages folder. Choose File | Deploy | EJB 1.0 JAR.
Enter the path to the JAR file, and optionally enter a package name. If you do not specify a package name, EAServer installs the components into a package with the same name as the base JAR file name. For example, components imported from EmploymentAuth.jar are installed to package EmploymentAuth.
EAServer Manager displays the beans that are defined in the JAR file. Select and configure beans for deployment as follows:
In the left column, select the check boxes for each bean that you want to deploy, or click Select All to deploy all beans.
Highlight each selected bean, then click Configure. Verify the deployment descriptor properties described in “EJB 1.0 deployment descriptor properties”.
When all selected beans have been configured, click Deploy.
Map role names that were read from the deployment descriptor to role names that exist in EAServer Manager. Names in the left column are used in the deployment descriptor; these may not match existing roles in EAServer Manager, or may match roles that do not agree with the access control requirements intended for the bean. For each name in the left column, assign a role name using the drop-down list in the right column.
Map run-as identity names that were read from the deployment descriptor to identity names that exist in EAServer Manager. You can configure these mappings now or later. To configure now, for each name in the left column, assign an identity name using the drop-down list in the right column. To configure after deployment completes, use the Run-As Mode tab in the Component Properties or Method Properties dialog.
Optionally generate stubs and skeletons for the bean. You must generate stubs and skeletons before the bean can run, but you can do so after deployment completes. If generating now, specify a code base for the generated files. Sybase recommends the EAServer java/classes subdirectory, which is the default.
Exporting an EJB 1.0 JAR file
Highlight the EAServer package to export and choose File | Export, then choose EJB 1.0 JAR.
Enter the path and file name for the new JAR file and click Next.
EAServer Manager creates the JAR file, displaying status messages in the Export wizard.
|Copyright © 2005. Sybase Inc. All rights reserved.|