1
Upgrading WebLogic Server 6.x to Version 7.0
JMS
WebLogic Server 7.0 supports the
All WebLogic JMS 6.x applications are supported in WebLogic JMS 7.0. However, if
you want your applications to take advantage of the new highly available JMS features,
you will need to configure your existing physical destinations (queues and topics) to
be part of a single distributed destination set. For more information on using JMS
distributed destinations, see
WebLogic JMS.
For more information on porting your WebLogic JMS applications, see
WebLogic JMS Applications
JMX
All public WebLogic Server 6.x MBeans and attributes are supported in WebLogic
Server 7.0. However, if you are employing internal MBeans or attributes, you may
encounter porting issues.
See
MBean attributes and operations.
Jolt Java Client
Jolt users will need to upgrade to Jolt Java Client 8.0.1 to enable BEA Tuxedo services
for the Web using BEA WebLogic Server 7.0. The Jolt Java Client 8.0.1 is available
from the
http://commerce.bea.com/downloads/products.jsp. Follow the link to BEA WebLogic
Server 7.0 and select the Jolt Java Client 8.0.1 from the Modules for WebLogic Server
list.
1-28
BEA WebLogic Server 7.0 Upgrade Guide
"Deprecated APIs and Features" on page 1-34
BEA Product Download Center at
JavaSoft JMS specification version
Using Distributed Destinations
in Programming WebLogic JMS.
1.0.2.
in Programming
Porting
for information on deprecated
Need help?
Do you have a question about the WebLogic Server 7 and is the answer not in the manual?