sun-ejb-jar.xml Visual Editor: Session Bean Configuration Tabs
See Also
The following configuration tabs in the sun-ejb-jar.xml Visual Editor: Session Bean pane
enable you to further modify sun-ejb-jar.xml elements for EJB session beans:
IOR Security Config tab
The IOR security configuration tab allows you to specify the following security information values for the Interoperable Object Reference (IOR).
- Transport Configuration
The Transport Configuration section has the following configurable fields:
- The Integrity field specifies if the target supports integrity-protected messages for transport.
- The Confidentiality field specifies if the target supports privacy-protected messages for transport.
- The Establish Trust in Target field specifies if the target is capable of authenticating to a client for transport.
- The Establish Trust in Client field specifies if the target is capable of authenticating a client for transport.
In each of these fields, you can select whether the item is supported, required, or none (not activated).
- As Context
The As Context section has the following configurable fields:
- Use the Required drop-down list to identify if the authentication method specified is required to be used for client authentication. Setting this field to True indicates that the authentication method specified is required; False indicates the method authentication is not required.
- Use the Authorization Method drop-down list to authenticate the client. The only supported value is USERNAME_PASSWORD.
- Use the Realm field to identify the realm in which the user is authenticated.
- Sas Context
The Sas Context section has the following configurable fields:
- Use the Caller Propagation drop-down list to identify if the target will accept propagated caller identities.
Bean Pool tab
The Bean Pool tab allows you to specify the pool properties of stateless session beans.
You can modify the following settings:
- Steady Pool Size specifies the initial and minimum number of
bean instances that should be maintained in the pool.
- Resize Quantity specifies the number of beans to be
created or deleted when the pool is being serviced by the server. The possible values
are 0 to MAX_INTEGER.
- Max Pool Size specifies the maximum number of bean instances
that can be created to satisfy client requests. The possible values are
from 0 to MAX_INTEGER.
- Pool Idle Timeout In Seconds specifies the maximum time, in
seconds, that the bean instance is allowed to remain idle in the pool.
When this timeout expires, the bean instance in a pool becomes a candidate
for passivation or deletion.
Bean Cache tab
The Bean Cache tab allows you to specify the pool properties of stateless session beans.
- Max Cache Size specifies the maximum number of beans allowable in the cache.
- Resize Quantity specifies the number of beans to be
created or deleted when the pool is being serviced by the server. The possible values
are 0 to MAX_INTEGER.
- Cache Idle Timeout In Seconds specifies the maximum time that a stateful session
bean or entity bean is allowed to be idle in cache. When this timeout expires, the bean
instance in a pool becomes a candidate for passivation or deletion.
- Removal Timeout In Seconds specifies the amount of time a bean instance can
remain passivated. If the bean is not accessed before this timeout expires, the
passivated bean is removed and is no longer accessible to the client.
- Is Cache Overflow Allowed specifies if the Max Cache Size value is a hard limit or not.
Sometimes many entity beans are needed to be added to a cache, exceeding the
max-cache-size. When this element is set to true, occasionally the size of the
cache can be exceeded. The size will reduce gradually when beans are
passivated or removed programmatically. If this element is set to false, and if
the cache size exceeds the Max Cache Size limit, then a CacheOverFlowException is thrown.
- Victim Selection Policy specifies the algorithm to use for picking victims when a pool
needs to shrink. Victims are generally passivated into a backup store
(typically a file system or database) that is cleaned during startup.
The following implementation choices are possible:
- The victims are removed from the cache.
- The victims are converted into soft references. This way, the objects stay in memory
but do not prevent the garbage collector from picking these objects, if memory runs very low.
The backup store is monitored by a background thread (or sweeper thread) to remove unwanted entries.
If no victims could be selected, then the value in the Is Cache Overflow Allowed field
will determine if a CacheOverFlowException is thrown or not.
The possible values are:
- First In, First Out (fifo)
- Least Recently Used (lru)
- Not Recently Used (nru)
- See Also
- sun-ejb-jar.xml Visual Editor
Session Bean
Sun Configuration
Entity Bean
Message Bean
Web Service Descriptor
- About Session Beans
- Configuring EJB Deployment Descriptors
Legal Notices