Table of Contents
Advertisement
WebLogic Server Clusters on Solaris
Certain applications (heavy EJB apps) deployed in a WebLogic Server cluster on
Solaris will perform better using the client JVM rather than the server JVM. This is
especially true under heavy loads.
Web Services
Due to changes in the Web service runtime system and architecture between versions
6.1 and 7.0 of WebLogic Server, you must upgrade Web services created in version
6.1 to run on version 7.0.
The WebLogic Web services client API included in WebLogic Server 6.1 of has been
deprecated and you cannot use it to invoke 7.0 Web services. WebLogic Server 7.0
includes a new client API, based on the Java API for XML-based RPC (JAX-RPC).
For detailed information on upgrading a 6.1 WebLogic Web service to 7.0, see
Upgrading 6.1 WebLogic Web Services to 7.0 at
http://e-docs.bea.com/wls/docs70/webServices/migrate.html.
For examples of using JAX-RPC to invoke WebLogic Web services, see
Services at
For general information on the differences between 6.1 and 7.0 Web services, see
Overview of WebLogic Web Services at
http://e-docs.bea.com/wls/docs70/webServices/overview.html.
Writable config.xml File
WebLogic Server 7.0 automatically updates configuration information read from the
6.x
config.xml
changes to be retained between invocations of the server, the
writable. To allow the file to be writable, make a backup copy of your
file from your 6.x configuration and change the file attributes.
Additional Upgrade Procedures and Information
http://e-docs.bea.com/wls/docs70/webServices/client.html.
file to include WebLogic Server 7.0 information. In order for these
BEA WebLogic Server 7.0 Upgrade Guide
Invoking Web
file must be
config.xml
config.xml
1-33
Advertisement
Table of Contents
Need help?
Do you have a question about the WebLogic Server 7 and is the answer not in the manual?