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.
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
