The Application Server Options page of the New / Edit J2EE Session EJB Wizard is application server and state management mode specific. The configuration options change depending on the type of application server you are using and the whether your EJBs are maintaining state.
These options, along with the application server options for the J2EE connector, are needed by your application server and are included in the packaging of your enterprise application.
|These are WebLogic application server specific options that are set in
WebLogic Application Server Options for Stateful EJBs
Every stateful EJB that you use keeps a connector allocated (until the EJB is removed). This ensures that the same number of connectors are available. Connector options are set on the next panel of the wizard.
Maximum Beans in Cache: Maximum number of objects of this class that are allowed in memory. Objects are kept in an LRU (Least Recently Used) chain and the objects dropped from the end of the chain are deactivated. The default value is 1000.
Idle Timeout (seconds): Number of seconds of inactivity after which a bean is deactivated. The default value is 600 seconds.
The J2EE connector that is bundled in the enterprise application when the session EJB is created cannot be serialized, therefore deactivation is not supported. Increase this value to accommodate the time between tasks when running stateful client applications.
Cache Type: The order in which stateful session beans are removed from the cache. The default value is NRU (Not recently used).
Persistent Store Directory: Specifies the directory in the application server's file system where the state of deactivated stateful session beans is to be stored.
Replication Type: The replication-type element describes how to replicate stateful session beans in a cluster.
This value Does this In Memory The bean will be replicated in memory across the cluster. None The bean will not be replicated.
Allow Concurrent Calls: Choose Allow concurrent calls to specify whether a stateful session bean will support concurrent method calls.
When a stateful session bean is currently in a method call and another (concurrent) method call arrives on the server, with Allow Concurrent Calls cleared (or set to false), a server error will occur. Allow Concurrent Calls is cleared by default. When this value is selected, the concurrent method call will be blocked and then allowed to proceed when the previous call has completed. The value of this element is either "True" or "False" and the default value is false.
WebLogic Application Server Options for Stateless EJBs
Each stateless EJB that you use only allocates a connector while the task is being executed. Thus, depending on how long an execution takes, you may actually require fewer connectors.
Maximum beans in free pool: A free pool of beans is maintained for each bean class. This setting specifies the maximum size of the pool. The default value is 1000.
Initial beans in free pool: A free pool of beans is maintained for each bean class. This setting specifies the initial size of the pool. The default value is 0.
Stateless bean is clusterable: Values are true or false. The default value is true. If selected (set to true), the bean can be deployed from multiple servers in a cluster.
Stateless bean load algorithm: The stateless bean load algorithm specifies the algorithm to use for load-balancing between replicas of the bean. If this property is not specified, the algorithm specified by the server property,
weblogic.cluster.defaultLoadAlgorithmwill be used. The possible values are: Random, RoundRobin, or WeightBased.
Stateless bean call router class name: Specify a custom class to be used for routing bean method calls. This class must implement
The task file and application server names are the names selected on the Task File and Application Server page of the J2EE Session EJB Wizard.
|Packaging J2EE Session EJBs|
|Configuring J2EE Session EJBs, Overview|
|MCS for Screens Help Links|