BEA WebLogic Server 7 ユーザーズマニュアル

ページ / 146
1
Upgrading WebLogic Server 6.x to Version 7.0
1-34
BEA WebLogic Server 7.0 Upgrade Guide
Deprecated APIs and Features
„
WebLogic Time Services is deprecated and should be replaced by JMX Timer 
Service. For documentation of JMX Timer Service, see 
and 
„
WebLogic Workspaces
„
Zero Administration Client (ZAC) is deprecated in this release of WebLogic 
Server 7.0. It is replaced by JavaWebStart.
„
WebLogic Enterprise Connectivity (WLEC) is deprecated in this release of 
WebLogic Server 7.0. Tuxedo CORBA applications using WLEC should migrate 
to WebLogic Tuxedo Connector. For more information, see 
„
weblogic.deploy
 is deprecated in this release of WebLogic Server 7.0 and has 
been replaced by 
weblogic.Deployer
. For more information, see 
in WebLogic Server Deployment.
„
This version of WebLogic Server deprecates deploying multiple J2EE modules 
without an 
application.xml
 file. If you select a directory for deployment, the 
directory must contain either one standalone J2EE module (an EJB, Web 
Application, or Resource Adapter), or multiple modules with an associated 
application.xml
 file (an Enterprise Application).
„
This release provides a standard method for resource adapter deployers to plug 
in their specified authorization/authentication mechanism through secure 
password credential storage. This WebLogic Server storage mechanism has 
replaced the Security Principal Mapping mechanism provided with the 
weblogic-ra.xml
 deployment descriptor within the resource adapter archive. 
As a result, the element has been deprecated. 
„
The Password Converter Tool provided with the previous release of WebLogic 
Server has been deprecated. 
„
The 
<connection-cleanup-frequency>
 and 
<connection-duration-time>
 
elements in the 
weblogic-ra.xml
 deployment descriptor have been deprecated in 
favor of a new connection leak detection mechanism. 
„
WebLogic Server 7.0 deprecates the single-phase deployment model used in 
WebLogic Server 6.x. All WebLogic 6.x deployment protocol APIs and tools are 
now deprecated and should not be used for deploying production applications.