user manual

1 Upgrading WebLogic Server 6.x to Version 7.0
1-26 BEA WebLogic Server 7.0 Upgrade Guide
 There were no local interfaces in 6.0, but they exist in 6.1 and 7.0.
 Remote relationships do not exist in 6.1 and 7.0.
 The new implementation of read-only beans in WebLogic 7.0 does not require
NOT_SUPPORTED for a transaction attribute. It also doesn't do exclusive locking,
but gives each transaction its own instance of the read-only bean to use.
 In pre-2.0 final versions of our EJB implementation you could refer to a CMP or
CMR field in a
EJB QL query without using a qualified path. However, as of the
final specification, all
EJB QL queries must have a qualified path.
 The new implementation of read-only beans in WebLogic 7.0 does not require
NOT_SUPPORTED for a transaction attribute. The new implementation also does
not do exclusive locking, but gives each transaction its own instance of the
read-only bean to use.
If you have trouble with a servlet within the scope of application deployment see
“Deployment” on page 1-24.
weblogic.management.configuration.EJBComponentMBean Changes
Beginning in Weblogic Server 6.1 and continuing in WebLogic Server 7.0, the
interface
weblogic.management.configuration.EJBComponentMBean changed
so that it extends both
ComponentMBean and EJBContainerMBean. Any methods
that implement
EJBComponentMBean (for example,
getVerboseEJBDeploymentEnabled) must be changed to support
EJBContainerMBean when you port from WebLogic Server 6.0 to 7.0.
max-beans-in-cache Parameter
In WebLogic Server 7.0 the max-beans-in-cache parameter controls the maximum
number of beans in the cache for Database concurrency. In earlier WebLogic Server
versions,
max-beans-in-cache was ignored; the size of the cache was unlimited.
You may need to increase the size of this parameter.