When importing beans from an EJB-JAR file, EAServer Manager displays the settings from each bean’s deployment descriptor and allows you to make changes before the information is recorded in EAServer’s configuration repository.
The information is displayed in the Verify Enterprise Bean Settings dialog box, which contains the tabs listed below. Changes that you make in the Verify Enterprise Bean Settings dialog box do not affect the settings recorded in the EJB-JAR file, only the settings to be recorded in EAServer’s configuration repository.
After deploying an EJB component into EAServer, you can change these properties using the controls in the Component Properties dialog box.
The leftmost tab defines the general settings for the bean. The bean’s implementation is dependent on the bean type and the Java class names specified here. You may change the EJB Home Name if you wish. Do not change other settings unless the deployment descriptor was prepared incorrectly.
EJB Class The Java class that implements the bean, specified in dot notation.
Home Interface Class The Java home interface name, specified in dot notation.
Remote Interface Class The Java remote interface name, specified in dot notation.
EJB Home Name The name suffix used by client applications to look up the bean’s home interface in the EAServer naming service. The full name consists of the server’s initial naming context followed by a slash (/) and the bean’s home name.
EJB Session Type Session beans only. Whether the session bean is stateful or stateless.
EJB Primary Key Entity beans only. The Java class that specifies primary key values for the entity bean, in Java dot notation.
Reentrant Entity beans only. Whether the bean is reentrant. A reentrant bean can participate in loopback call sequences, which are call sequences where one of the bean’s methods calls another component which in turn calls a method in the calling bean instance. Most beans are not implemented to support reentrancy. Do not enable this option unless the bean developer has verified that the implementation allows it.
Changing general properties after deployment
After deployment completes, use the General tab in the Component
Properties dialog to view or modify these properties. The Reentrant
property for an entity bean is specified with a check box on the
Instances tab.
This tab configures the users that can call the bean’s methods. If roles are listed for a method name, only users in that role can execute the method. The displayed role names are those listed in the bean’s deployment descriptor. The displayed roles may not exist in EAServer Manager. If they do not, the Deployment Wizard prompts you to map these role names to existing EAServer Manager roles after all selected beans have been configured.
Changing Access Control properties after
deployment completes
After deployment completes, you can configure access control
for the EJB component and its methods in EAServer Manager. To change
access control for the component, use the Role Membership folder
below the component’s icon. To change access control for
a method, expand the Interfaces folder below the component icon,
then expand the icon for the interface that contains the method.
Add or remove roles using the Role Membership folder.
Use this tab to configures settings that control how EAServer executes the bean’s methods:
Tx Attribute Determines how the bean participates in transactions managed by EAServer. For more information, see the online help or Chapter 4, “Defining Components,” in the EAServer Programmer’s Guide.
Tx Isolation If the bean participates in transactions, determines the transaction isolation level. For more information, see the online help or Chapter 4, “Defining Components,” in the EAServer Programmer’s Guide.
Run-as Mode Determines the user name and password used when the bean calls other EAServer components installed in the same server or server cluster. The choices are:
Option |
Description |
---|---|
Client |
Use the client’s username and password. |
System |
Use the system user name and password. The system account effectively belongs to any role, and can execute any method on any component that is installed in the same server or cluster. |
Specified |
Use the user name and password associated with the identity name specified in the Run-as Identity column. |
Run-as Identity If the run-as mode is set to Specified, Run As Identity must specify an identity name to authenticate calls to components that are installed on the same server or server cluster. The identity name read from a bean may not exist in EAServer. If it does not, the Deployment wizard asks you to map this identity name to an identity listed in the EAServer Manager Identities folder after all selected beans have been configured.
Changing Control Descriptor properties
after deployment completes
After deployment completes, you can configure transactional properties
on the Transactions tab in the Component Properties dialog box.
Use the Run-As Mode tab to view and edit the run-as mode and run-as
identity settings.
Use this tab to specify bean properties required by the implementation. For example, there might be a property specifying a JDBC database URL for queries to a remote database. At runtime, the bean accesses these properties using the EJBContext.getEnvironment() method. The tab initially displays the properties and values defined in the bean’s deployment descriptor. You can modify, add, and delete properties as follows:
To do this |
Do this |
---|---|
Modify a property |
Edit the value in the right column. |
Add a property |
Click Add. A blank row appears. Type a property name and a value for the property. Property names beginning with com.sybase are reserved for Sybase internal use. |
Delete a property |
Highlight the property name or value column, then click Delete. |
Changing Environment properties after deployment
completes
After deployment completes, you can configure environment
properties using the Advanced tab in the Component Properties dialog
box. The environment properties are listed in addition to the com.sybase.jaguar.component properties used
internally by EAServer.
Copyright © 2005. Sybase Inc. All rights reserved. |
![]() |