Summary of the content on the page No. 1
BEA WebLogic
™
Server
BEA WebLogic Server 7.0
Upgrade Guide
Release 7.0
Document Date: June 2002
Revised: June 28, 2002
Summary of the content on the page No. 2
Copyright Copyright © 2002 BEA Systems, Inc. All Rights Reserved. Restricted Rights Legend This software and documentation is subject to and made available only pursuant to the terms of the BEA Systems License Agreement and may be used or copied only in accordance with the terms of that agreement. It is against the law to copy the software except as specifically allowed in the agreement. This document may not, in whole or in part, be copied photocopied, reproduced, translated, or reduced to a
Summary of the content on the page No. 3
Contents About This Document Audience.............................................................................................................. ix e-docs Web Site................................................................................................... ix How to Print the Document...................................................................................x Contact Us!............................................................................................................x
Summary of the content on the page No. 4
Update Inbound RMI-IIOP Applications ................................................. 1-17 Authenticate Remote Users ...................................................................... 1-19 ACL Policy is LOCAL...................................................................... 1-19 ACL Policy is Global ........................................................................ 1-20 Set WebLogic Tuxedo Connector Properties........................................... 1-20 Additional Upgrade Proc
Summary of the content on the page No. 5
2. Upgrading WebLogic Server 4.5 and 5.1 to Version 7.0 Upgrading Your WebLogic Server Configuration: Main Steps........................ 2-2 Upgrading WebLogic Server License Files ...................................................... 2-4 Converting a WebLogicLicense.class License........................................... 2-4 Converting a WebLogicLicense.XML License ......................................... 2-4 Converting the weblogic.properties File to XML Files...............................
Summary of the content on the page No. 6
FileServlet................................................................................................. 2-28 Internationalization (I18N)....................................................................... 2-28 Java Transaction API (JTA) ..................................................................... 2-28 Java Database Connectivity (JDBC) ........................................................ 2-29 JSP ................................................................................
Summary of the content on the page No. 7
7.0 ................................................................................................B-9 config.xml file used for WebLogic Server 6.1 Service Pack 3.........B-12 above-listed config.xml file used for WebLogic Server 7.0 .............B-15 Start the Pet Store Application on WebLogic Server 7.0.........................B-19 Upgrading the WebLogic 6.0 Service Pack 2 Examples Server to WebLogic Server 7.0 .................................................................................
Summary of the content on the page No. 8
viii BEA WebLogic Server 7.0 Upgrade Guide
Summary of the content on the page No. 9
About This Document This document provides procedures and other information you need to upgrade earlier versions of BEA WebLogic Server to WebLogic 7.0. It also provides information about moving applications from an earlier version of WegLogic Server to 7.0. The document is organized as follows: Chapter 1, “Upgrading WebLogic Server 6.x to Version 7.0,” describes how to upgrade to WebLogic Server 7.0 from WebLogic Server 6.x. Chapter 2, “Upgrading WebLogic Server 4.5 and 5.1 to Version 7.0,
Summary of the content on the page No. 10
How to Print the Document You can print a copy of this document from a Web browser, one main topic at a time, → Print option on your Web browser. by using the File A PDF version of this document is available on the WebLogic Server documentation Home page on the e-docs Web site (and also on the documentation CD). You can open the PDF in Adobe Acrobat Reader and print the entire document (or a portion of it) in book format. To access the PDFs, open the WebLogic Server documentation Home page,
Summary of the content on the page No. 11
A description of the problem and the content of pertinent error messages Documentation Conventions The following documentation conventions are used throughout this document. Convention Usage Ctrl+Tab Keys you press simultaneously. italics Emphasis and book titles. monospace Code samples, commands and their options, Java classes, data types, text directories, and file names and their extensions. Monospace text also indicates text that you enter from the keyboard. Examples: import java.util.Enu
Summary of the content on the page No. 12
Convention Usage [ ] Optional items in a syntax line. Example: java utils.MulticastTest -n name -a address [-p portnumber] [-t timeout] [-s send] | Separates mutually exclusive choices in a syntax line. Example: java weblogic.deploy [list|deploy|undeploy|update] password {application} {source} ... Indicates one of the following in a command line: An argument can be repeated several times in the command line. The statement omits additional optional arguments. You can enter additional para
Summary of the content on the page No. 13
CHAPTER 1 Upgrading WebLogic Server 6.x to Version 7.0 Upgrading WebLogic Server 6.x to version 7.0, under the simplest circumstances, involves changing your WebLogic Server start command scripts and environment settings. In some cases, it is necessary to move your domain directory. Sometimes, upgrading requires changes specific to the subsytem being upgraded. The following sections contain information necessary to upgrade your system from WebLogic Server 6.x to WebLogic Server 7.0: “Upgr
Summary of the content on the page No. 14
1 Upgrading WebLogic Server 6.x to Version 7.0 For information on upgrading to WebLogic Platform 7.0 (7.0.0.1), see the Upgrading section of the WebLogic Server FAQs. Note: Throughout this document “upgrade” refers to upgrading to a later version of WebLogic Server and “port” refers to moving your applications from an earlier version of WebLogic Server to a later version. Upgrading Your WebLogic Server Configuration: Main Steps Take the following steps to upgrade from WebLogic Server 6.x to
Summary of the content on the page No. 15
Modifying Startup Scripts To upgrade a cluster of servers, follow the above steps for each server and then follow the steps outlined in Setting Up WebLogic Clusters in Using WebLogic Server Clusters. In cases where you invoke an application by using RMI/T3 or RMI/IIOP, WebLogic Server 6.1 and 7.0 are interoperable. Within a domain, however, all servers must be of the same version. For information on upgrading WebLogic Server license files, see Upgrading Licenses from Previous WebLogic Serve
Summary of the content on the page No. 16
1 Upgrading WebLogic Server 6.x to Version 7.0 5. Modify or eliminate any WebLogic Server 6.x startup script directory structure tests. For example, if your script tries to verify a relative path, either fix the directory structure test or remove it. WebLogic Server 7.0 installs the JVM, JDK 1.3.1_02, with the server installation. The setenv.sh scripts provided with the server all point to the JVM. The latest information regarding certified JVMs is available at the Certifications Page. Under
Summary of the content on the page No. 17
Porting an Application from WebLogic Server 6.x to WebLogic Server 7.0 1. If you have not already installed WebLogic Server 7.0, do so now. See the Installation Guide for more information. Note: Installing the new version in the exact location of the old version is explicitly prohibited by the installer. 2. Each 6.x and 7.0 domain must have its own separate directory. It is not possible to have multiple config.xml files in the same directory. a. For each 6.x configuration domain that you wish
Summary of the content on the page No. 18
1 Upgrading WebLogic Server 6.x to Version 7.0 4. When you deploy applications to WebLogic Server 7.0, use the Administration Console or weblogic.Deployer utility to deploy using the new two-phase deployment protocol. The older, WebLogic Server 6.x deployment protocol, utilities, and API are deprecated in WebLogic Server 7.0 Note: WebLogic Server 7.0 will not deploy an application that has errors in its deployment descriptor. Previous versions of WebLogic Server would deploy an application
Summary of the content on the page No. 19
Upgrading Security Note: The WebLogic Server 7.0 examples and PetStore are configured to use the default security configuration. It is not possible to run the WebLogic Server 7.0 examples and PetStore in Compatibility security. Booting WebLogic Server in Compatibility Security In previous releases of WebLogic Server, the File realm was configured by default. Therefore, WebLogic Server could use the File Realm to boot even if there was no security realm defined in the config.xml file. However
Summary of the content on the page No. 20
1 Upgrading WebLogic Server 6.x to Version 7.0 Upgrading from Compatibility Security to WebLogic Server 7.0 Security If you want to leverage the new security features in WebLogic Server 7.0, you need to upgrade your existing security realm to a WebLogic Server 7.0 security realm. You upgrade by populating the security providers in WebLogic Server 7.0 with your existing user and group information and defining security policies on resources that reflect the ACLs. During successful booting of
