In the Adaptive Server plug-in, EJB Server packages allow you to group related EJB components as a logical unit. Typically, components in a package work together to provide a coherent service or function.
You can create JavaBeans from scratch or, more likely, import the JavaBeans to EJB Server using the Adaptive Server plug-in. When you import JavaBeans, they must be contained in a JAR file or Java class file. The Adaptive Server plug-in reads the JAR file or class file and creates an EJB Server package containing a component for each Bean in the file. See “Importing Enterprise JavaBeans”.
EJB Server packages serve the following purposes:
They are a unit of deployment Using the Adaptive Server plug-in, you can import and export archived copies of the components in a package and related application files.
They allow you to control which users can access the components Packages form one level in the EJB Server authorization hierarchy. A package is not available to the user unless it is deployed to the EJB Server’s Installed Packages folder. The Adaptive Server plug-in allows you to map roles through each package for methods within the package. See“Configuring package properties” for information about mapping roles.
When EJB Server is installed, the AseAuth default package is deployed automatically to EJB Server. You will see this package in the Installed Packages folder. AseAuth contains information you need to log in to EJB Server from the Adaptive Server plug-in. Do not alter or delete this package.
