BEA WebLogic Server 7 Upgrade Manual
  1. Manuals
  2. Brands
  3. BEA Manuals
  4. Server
  5. WebLogic Server 7
  6. Upgrade manual
BEA WebLogic Server 7 Upgrade Manual

BEA WebLogic Server 7 Upgrade Manual

Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
WebLogic
BEA
Server
™
BEA WebLogic Server 7.0
Upgrade Guide
Release 7.0
Document Date: June 2002
Revised: June 28, 2002

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the WebLogic Server 7 and is the answer not in the manual?

Questions and answers

Related Manuals for BEA WebLogic Server 7

Summary of Contents for BEA WebLogic Server 7

  • Page 1 WebLogic Server ™ BEA WebLogic Server 7.0 Upgrade Guide Release 7.0 Document Date: June 2002 Revised: June 28, 2002...

  • Page 2: Software Version

    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.

  • Page 3: Table Of Contents

    Upgrading Your WebLogic Server Configuration: Main Steps......1-2 Modifying Startup Scripts ................. 1-3 Understanding the WebLogic Server 7.0 Directory Structure ......1-4 Porting an Application from WebLogic Server 6.x to WebLogic Server 7.0 ... 1-4 Upgrading Security.................... 1-6 Booting WebLogic Server in Compatibility Security ........ 1-7 ACLs on MBeans ..................
  • Page 4 Thread Pool Size..................1-31 Web Applications ..................1-32 WebLogic Server Clusters on Solaris............1-33 Web Services .................... 1-33 Writable config.xml File ................1-33 Deprecated APIs and Features..............1-34 Removed APIs and Features ..............1-36 BEA WebLogic Server 7.0 Upgrade Guide...
  • Page 5 Deploying Web Applications ..............2-12 Session Porting..................2-13 JavaServer Pages (JSPs) and Servlets ............2-14 Porting a Simple Servlet from WebLogic Server 5.1 to WebLogic Server 7.0 2-15 Porting and Converting Enterprise JavaBeans Applications......2-16 EJB Porting Considerations ..............2-17 EJB Porting Recommendations..............
  • Page 6 Upgrading the Pet Store Application From WebLogic 6.1 Service Pack 3 to WebLogic Server 7.0................. B-2 Install WebLogic Server 7.0..............B-2 Set Up the WebLogic Server 7.0 Environment with Your 6.1 Service Pack 3 Domain Configuration................ B-3 Fix JSP Parsing Errors................ B-4 Rebuild Pet Store................
  • Page 7 Upgrading the WebLogic 6.0 Service Pack 2 Examples Server to WebLogic Server 7.0 ....................B-19 Install WebLogic Server 7.0..............B-19 Set Up the WebLogic Server 7.0 Environment with Your 6.0 Service Pack 2 Domain Configuration ..............B-20 setExamplesEnv.cmd script used to boot a WebLogic 6.0 Service Pack 2 Examples Server ................B-21...
  • Page 8 BEA WebLogic Server 7.0 Upgrade Guide...

  • Page 9: About This Document

    WebLogic Server 7.0 from WebLogic Server 6.x. Chapter 2, “Upgrading WebLogic Server 4.5 and 5.1 to Version 7.0,” describes how to upgrade to WebLogic Server 7.0 from WebLogic Server 4.5 or 5.1. Appendix A, “The weblogic.properties Mapping Table,” shows which attribute handles the function config.xml, web.xml, or weblogic.xml...

  • Page 10: How To Print The Document

    If you have any questions about this version of BEA WebLogic Server, or if you have problems installing and running BEA WebLogic Server, contact BEA Customer Support through BEA WebSupport at http://www.bea.com.

  • Page 11: Documentation Conventions

    * config/examples/applications .java config.xml float Variables in code. monospace italic Example: text String CustomerName; UPPERCASE Device names, environment variables, and logical operators. TEXT Examples: LPT1 BEA_HOME A set of choices in a syntax line. BEA WebLogic Server 7.0 Upgrade Guide...
  • Page 12 An argument can be repeated several times in the command line. The statement omits additional optional arguments. You can enter additional parameters, values, or other information Indicates the omission of items from a code example or from a syntax line. BEA WebLogic Server 7.0 Upgrade Guide...

  • Page 13: Upgrading Weblogic Server 6.X To Version

    “Additional Upgrade Procedures and Information” on page 1-21 For instructions on how to upgrade the Pet Store application from WebLogic Server 6.1 to WebLogic Server 7.0 and how to upgrade the WebLogic 6.0 and 6.1 Examples Servers to WebLogic Server 7.0, see “Upgrading the Pet Store Application and the...

  • Page 14: Upgrading Your Weblogic Server Configuration: Main Steps

    Note: The installer will prevent you from installing the new version directly over the old version. You must select a new directory location. 3. Modify your 6.x startup scripts to work with WebLogic Server 7.0. See “Modifying Startup Scripts” on page 1-3.

  • Page 15: Modifying Startup Scripts

    WebLogic Server 7.0 installation directory. For example: WL_HOME=c:\bea700\weblogic700 3. Modify PATH so that it includes your 7.0 home. For example: %WL_HOME% PATH=%WL_HOME%\bin;%PATH% 4. Modify CLASSPATH so that it points to the WebLogic Server 7.0 classes. For example: CLASSPATH=%WL_HOME%\lib\weblogic_sp.jar;%WL_HOME%\lib\weblog ic.jar BEA WebLogic Server 7.0 Upgrade Guide...

  • Page 16: Understanding The Weblogic Server 7.0 Directory Structure

    Certifications Page. Understanding the WebLogic Server 7.0 Directory Structure The directory structure in WebLogic Server 7.0 is different from that of 6.x. For complete information on the updated directory structure see Understanding the WebLogic Server Directory Structure in Performing Post-Installation Tasks in the Installation Guide.
  • Page 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.

  • Page 18: Upgrading Security

    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 that had errors in its deployment descriptor.

  • Page 19: Booting Weblogic Server In Compatibility Security

    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.

  • Page 20: Upgrading From Compatibility Security To Weblogic Server 7.0 Security

    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.

  • Page 21: Security Realms

    Security Realms The scope of security realms changed in WebLogic Server 7.0. In WebLogic Server 6.x, security realms provided authentication and authorization services. You chose from the File realm or a set of alternative security realms including the Lightweight Data Access Protocol (LDAP), Windows NT, UNIX or RDBMS realms.
  • Page 22 Use the Realm Adapter Authentication provider with the WebLogic Server 7.0 security providers. This option allows you to use the roles and security policies available in WebLogic Server 7.0 while accessing users and groups stored in an LDAP, Windows NT, UNIX or RDBMS security realm. You also have the option of configuring multiple Authentication providers so you can use your existing 6.x security realm while upgrading users and groups to an Authentication...

  • Page 23: Guest User

    13. Click Apply. Note: ACLs cannot be upgraded to WebLogic Server 7.0. Guest User user is no longer supplied by default in WebLogic Server 7.0. To use the guest user, you must run in Compatibility security or define the user as a user...

  • Page 24: Upgrading The Ssl Protocol

    CertAuthenticator in Compatibility security. Creating a Trusted CA Keystore By default in WebLogic Server 7.0, clients check the server’s trusted certificate authority. This check is done whenever a client and server connect using SSL, including when WebLogic Server is acting an a client. For example, when a client is using the SSL protocol to connect to an Apache HTTP Server, the client checks the trusted certificate authorities presented by the server.

  • Page 25: Using Certauthenticator In Compatibility Security

    Using CertAuthenticator in Compatibility Security In WebLogic Server 7.0, the CertAuthenticator is called first, before any username/password authentication. Because this is a change in behavior from WebLogic Server 6.x, a CertAuthenticator written for WebLogic Server 6.x may need to change if clients used both two-way SSL and they supplied a username and password for security credentials.

  • Page 26: Cipher Suites

    NULL are only being used to make an SSL connection. In WebLogic Server 7.0, X.509 Identity Assertion is turned off by default. If your WebLogic Server 6.x file used a CertAuthenticator you need to manually config.xml...

  • Page 27: Upgrading Weblogic Tuxedo Connector

    Previous releases of the connector used a WebLogic Server Startup class to start a WebLogic Tuxedo Connector session and a WebLogic Server Shutdown class to end a session. In WebLogic Server 7.0, WebLogic Tuxedo Connector does not use a Startup or a Shutdown class. WebLogic Tuxedo Connector sessions are managed using a WTCServer MBean.

  • Page 28: Convert Weblogic Tuxedo Connector Xml Configuration Files

    WebLogic property used to turn on -Dweblogic.wtc. wtc.migrateDebug migrateDebug mode. URL passed to your server. Example: \\myServer:7001 User Name passed to your server. USERNAME Example: system Password passed to your server. PASSWORD Example: mypasswd 1-16 BEA WebLogic Server 7.0 Upgrade Guide...

  • Page 29: Update Inbound Rmi-Iiop Applications

    If you use inbound RMI-IIOP, you must modify the reference object that connects WebLogic Tuxedo Connector instances to Tuxedo CORBA applications. Tuxedo CORBA objects now use the server name to reference remote WebLogic Tuxedo Connector objects. Earlier releases used the DOMAINID BEA WebLogic Server 7.0 Upgrade Guide 1-17...
  • Page 30 TYPE=TDOMAIN DOMAINID="TDOM1" BLOCKTIME=20 MAXDATALEN=56 MAXRDOM=89 *DM_REMOTE_DOMAINS TDOM2 TYPE=TDOMAIN DOMAINID="TDOM2" *DM_TDOMAIN TDOM1 NWADDR="<network address of Tuxedo domain:port>" TDOM2 NWADDR="<network address of WTC domain:port>" *DM_REMOTE_SERVICES "//servername" where is the name of your WebLogic Server. servername 1-18 BEA WebLogic Server 7.0 Upgrade Guide...

  • Page 31: Authenticate Remote Users

    5. Click the Configure a new User text link. 6. Click DefaultAuthenticator 7. In the General tab, do the following: a. Add the Tuxedo in the Name field. DOMAINID b. Enter and validate a password. c. Click Apply. BEA WebLogic Server 7.0 Upgrade Guide 1-19...

  • Page 32: Acl Policy Is Global

    To generate passwords using the weblogic.wtc.gwt.genpasswd utility, you must set a password key using the WebLogic Server PasswordKey property. For more information on how to generate passwords, see Configuring a WTCPassword MBean http://e-docs.bea.com/wls/docs70/wtc_admin/BDCONFIG.html#1111404. mykey -Dweblogic.wtc.PasswordKey= where mykey is the key value. 1-20 BEA WebLogic Server 7.0 Upgrade Guide...

  • Page 33: Additional Upgrade Procedures And Information

    The following sections provide additional information that may be useful about deprecated features, upgrades, and the important changes that have been made in WebLogic Server 7.0. Note: WebLogic Server 7.0 uses PointBase 4.2 as a sample database and does not bundle the Cloudscape database. “ant.jar” on page 1-22 “Apache Xalan XML Transformer”...

  • Page 34: Ant.jar

    Apache Xalan XML Transformer The built-in transformer in WebLogic Server 7.0 is based on the Apache Xalan 2.2 transformer. Use of the Xalan APIs directly has been deprecated. If you are still using those APIs and encounter difficulties, you should use the Java API for XML Processing (JAXP) to use XSLT.

  • Page 35: Apache Xerces Xml Parser

    Additional Upgrade Procedures and Information Apache Xerces XML Parser The built-in XML parser for WebLogic Server 7.0 is based on the Apache Xerces 1.4.4 parser. The parser implements version 2 of the SAX and DOM interfaces. Users who used older parsers that were shipped in previous versions may receive deprecation messages.

  • Page 36: Deployment

    WebLogic Server 7.0 will not deploy an application that has any errors in its deployment descriptor. Previous versions of WebLogic Server would deploy an application that had errors in its deployment descriptor. For example, if your 6.x application was missing a reference description stanza in the deployment descriptor, the application will not deploy in the 7.0 server until you add that stanza.

  • Page 37: Ejb 2.0

    WebLogic Server 7.0, and somewhat between WebLogic Server 6.1 and WebLogic Server 7.0. Some of the prominent changes are listed here. To see a complete listing of the specification changes from WebLogic Server 6.0 to WebLogic Server 7.0, you can view and download the EJB 2.0 final specification http://java.sun.com/products/ejb/2.0.html.

  • Page 38: Weblogic.management.configuration.ejbcomponentmbean Changes

    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 changed weblogic.management.configuration.EJBComponentMBean so that it extends both .

  • Page 39: Fully Qualified Path Expressions

    In an EJB QL Query on WebLogic Server 7.0, all path-expressions must be fully qualified. This is a change from WebLogic Server 6.x. If you see an ejbc error while running ejbc on WebLogic Server 7.0 using a 6.x EJB, you need to correct either your elements in your...

  • Page 40: Jms

    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 BEA Product Download Center at http://commerce.bea.com/downloads/products.jsp.

  • Page 41: Jsp

    EJBs. Managed Servers A Managed Server running WebLogic Server 6.x cannot obtain its configuration and boot using an Administration Server running WebLogic Server 7.0. Make sure that you do not copy the file from your WebLogic Server running-managed-servers.xml 6.x installation directory to your WebLogic Server 7.0 installation directory.

  • Page 42: Mbean Api Change

    Caution: This argument was added to assist existing WebLogic Server customers to upgrade their security functionality. You should take great caution when using the user in a production environment. For more information guest 1-30 BEA WebLogic Server 7.0 Upgrade Guide...

  • Page 43: Servlets

    Server MBean. ExecuteQueue WebLogic Server 7.0 provides a porting path for this parameter, so that if it is specified in the file, or if it is passed to the client or server on the command line config.xml...

  • Page 44: Web Applications

    Servlet Request and Response objects. If you did this in WebLogic Server 6.0, you were probably relying on the undocumented, internal implementations of these objects. WebLogic Server 7.0 supports Servlet 2.3, so you should be able to take advantage of the new ServletRequest/ResponseWrapper objects.

  • Page 45: Weblogic Server Clusters On Solaris

    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).

  • Page 46: Deprecated Apis And Features

    WebLogic Server 7.0. Tuxedo CORBA applications using WLEC should migrate to WebLogic Tuxedo Connector. For more information, see WebLogic Tuxedo Connector. is deprecated in this release of WebLogic Server 7.0 and has weblogic.deploy been replaced by . For more information, see Deployment weblogic.Deployer...
  • Page 47 WebLogic Server 7.0 documentation. The WebLogic jDriver for Microsoft SQL Server is deprecated and will be removed from a future release of WebLogic Server. BEA recommends that you use the JDBC driver available from Microsoft to connect to a Microsoft SQL Server database.

  • Page 48: Removed Apis And Features

    Upgrading WebLogic Server 6.x to Version 7.0 Removed APIs and Features WebLogic Enterprise Connectivity (WLEC) examples have been removed. 1-36 BEA WebLogic Server 7.0 Upgrade Guide...

  • Page 49: Upgrading Weblogic Server 4.5 And 5.1 To Version

    The following sections provide procedures and other information you need to upgrade your system from WebLogic Server 4.5 or 5.1 to WebLogic Server 7.0; to port your applications from WebLogic Server 4.5 or 5.1 to WebLogic Server 7.0; and deploy these applications.

  • Page 50: Upgrading Your Weblogic Server Configuration: Main Steps

    Server 7.0: 1. Make a back-up copy of your 4.5 or 5.1 domain before you begin the upgrade procedure. After you start the server using WebLogic Server 7.0 classes, you will be unable to downgrade to a previous version. 2. Install WebLogic Server 7.0. See the Installation Guide.
  • Page 51 7.0 since there is no interoperability between 4.5 and 7.0 or between 5.1 and 7.0. To upgrade from WebLogic Server 7.0 to WebLogic Server 7.0.0.1, see Updating WebLogic Server 7.0 GA (7.0.0.0) to 7.0.0.1 in the Installation Guide.

  • Page 52: Upgrading Weblogic Server License Files

    Upgrading WebLogic Server 4.5 and 5.1 to Version 7.0 Note: The directory structure in WebLogic Server 7.0 is different from that of 4.5 and 5.1. For complete information on the updated directory structure see Understanding the WebLogic Server Directory Structure in Performing Post-Installation Tasks.

  • Page 53: Converting The Weblogic.properties File To Xml Files

    XML files that config.xml define how your applications are set up. BEA Systems recommends that you change the name of the default domain name that is created during the conversion so that the name is relevant to your work.
  • Page 54 Convert your existing file to the appropriate XML file by weblogic.properties following these steps: 1. Start the WebLogic Server 7.0 examples server. For information on starting the WebLogic Server 7.0 examples server, see Starting the Examples, Pet Store, and Workshop Examples Servers in Performing Post-Installation Tasks.
  • Page 55 Server Web Components in the Administration Guide. Security properties are stored in the file located in fileRealm.properties . For information about using a security realms in WebLogic Server 7.0, domain Customizing the Default Security Configuration. API, which provided methods to weblogic.common.ConfigServicesDef...

  • Page 56: Classloading In Weblogic Server 7.0

    WebLogic Server 7.0” on page 2-8. WebLogic Server 7.0 is started from the domain directory. Make sure that your startup script starts the server from the domain directory. It is no longer necessary to include the license file in the classpath.

  • Page 57: Weblogic Server 7.0 J2Ee Application Types

    WebLogic Server 7.0 J2EE Application Types WebLogic Server 7.0 J2EE Application Types Applications on J2EE-compliant servers such as WebLogic Server 7.0 are created and deployed as one of the following four types: Web Applications, Enterprise JavaBeans, Enterprise Archives, and client applications. To port your existing components to WebLogic Server 7.0, create the appropriate J2EE deployment units.

  • Page 58: Web Applications Directory Structure

    “Deploying Web Applications” on page 2-12 “Session Porting” on page 2-13 “JavaServer Pages (JSPs) and Servlets” on page 2-14 “Porting a Simple Servlet from WebLogic Server 5.1 to WebLogic Server 7.0” on page 2-15 Web Applications Directory Structure Web Applications are organized in a specified directory structure so that they can be archived and deployed on WebLogic Server.

  • Page 59: Xml Deployment Descriptors

    XML files specific to each Web Application. Each Web Application needs a file and a weblogic.xml web.xml file as well as whichever files you choose to put in it. BEA WebLogic Server 7.0 Upgrade Guide 2-11...

  • Page 60: War Files

    Note that WebLogic Server will deploy all components it finds in and below the specified directory. 7. Click the icon to the left of a directory or file to choose it and proceed to the next step. 2-12 BEA WebLogic Server 7.0 Upgrade Guide...

  • Page 61: Session Porting

    Help. Session Porting WebLogic Server 7.0 does not recognize cookies from previous versions because cookie format changed with WebLogic Server 6.0. WebLogic Server will ignore cookies with the old format and create new sessions. Be aware that new sessions are created automatically.

  • Page 62: Javaserver Pages (Jsps) And Servlets

    Server-side-includes are not supported. You must use JSP to achieve this functionality. WebLogic Server 7.0 is fully compliant with the Servlet 2.3 specification. Update your web.xml file so that it uses the following new classes: weblogic.servlet.proxy.HttpClusterServlet instead of weblogic.servlet.internal.HttpClusterServlet...

  • Page 63: Porting A Simple Servlet From Weblogic Server 5.1 To Weblogic Server

    The following procedure ports the simple Hello World Servlet that was provided with WebLogic 5.1 Server to WebLogic Server 7.0. 1. In WebLogic Server 7.0, create the correct directory structure, as described in Administration and Configuration in Programming WebLogic Server HTTP Servlets.

  • Page 64: Porting And Converting Enterprise Javabeans Applications

    . The second was mapped in hello.war /hello the servlet mapping tags inside the file. web.xml Porting and Converting Enterprise JavaBeans Applications The following sections describe Enterprise Java Beans porting and conversion procedures. 2-16 BEA WebLogic Server 7.0 Upgrade Guide...

  • Page 65: Ejb Porting Considerations

    Java Beans. EJB 1.1 beans are deployable in WebLogic Server 7.0. However, if you are developing new beans, it is recommended that you use EJB 2.0. EJB 1.1 beans can be converted to 2.0 using the DDConverter utility. For more information, see...

  • Page 66: Ejb Porting Recommendations

    In order to specify the mappings to the database, container-managed persistence entity beans require a CMP deployment descriptor that conforms to either the WebLogic Server 5.1 CMP DTD, the WebLogic Server 7.0 EJB 1.1 DTD, or the WebLogic Server 7.0 EJB 2.0 DTD.
  • Page 67 WebLogic Server 7.0. The below combinations include a WebLogic Server 7.0 CMP deployment descriptor. The WebLogic Server 7.0 EJB 1.1 CMP deployment descriptor allows multiple EJBs to be specified within a single EJB JAR file, and it supports using a TxDataSource which is required when an EJB is enlisted in a two-phase /XA transaction.

  • Page 68: Steps For Porting A 1.0 Ejb From Weblogic Server 4.5.X To Weblogic Server 7.0

    WebLogic Server 3.1.x, 4.0.x, and 4.5.x supported the EJB 1.0 specification. To port a 1.0 EJB from WebLogic Server 4.5 to WebLogic Server 7.0: 1. Convert the EJB 1.0 deployment descriptor to either the EJB 1.1 or the EJB 2.0 XML deployment descriptor.

  • Page 69: Steps For Porting A 1.1 Ejb From Weblogic Server 5.1 To Weblogic Server 7.0

    XA is being used with EJB 1.1 CMP. TxDataSource To port a 1.1 EJB from WebLogic Server 5.1 to WebLogic Server 7.0: 1. Open the Administration Console. From the home page, click on Install Applications under the Getting Started heading.

  • Page 70: Steps For Converting An Ejb 1.1 To An Ejb 2.0

    BEA Systems recommends that you develop EJB 2.0 beans in conjunction with WebLogic Server 7.0. For 1.1 beans already used in production, it is not necessary to convert them to 2.0 beans. EJB 1.1 beans are deployable with WebLogic Server 7.0. If you do wish to convert 1.1 beans to 2.0 beans, see the...

  • Page 71: Porting Ejbs From Other J2Ee Application Servers

    Creating an Enterprise Application Porting EJBs from Other J2EE Application Servers Any EJB that complies with the EJB 1.1 or EJB 2.0 specifications may be deployed in the WebLogic Server 7.0 EJB container. Each EJB JAR file requires an ejb-jar.xml file, a deployment descriptor, and a CMP deployment weblogic-ejb-jar.xml...

  • Page 72: Understanding J2Ee Client Applications

    For more information about J2EE client applications, see Packaging Client Applications in Developing WebLogic Server Applications. 2-24 BEA WebLogic Server 7.0 Upgrade Guide...

  • Page 73: Upgrading Jms

    In order to port object messages, the object classes need to be in the Weblogic Server 7.0 server CLASSPATH. For destinations that are not configured in Weblogic Server 7.0, the ported messages will be dropped and the event will be logged.

  • Page 74: Additional Porting And Deployment Considerations

    WebLogic Server 7.0. Deprecated features, upgrades, and the important changes that have been made in WebLogic Server 7.0 are noted. Note: WebLogic Server 7.0 uses PointBase 4.2 as a sample database and does not bundle the Cloudscape database.

  • Page 75: Applications And Managed Servers

    Plug-ins The communication between the plug-in and WebLogic Server 4.5 and 5.1 is clear text. The plug-ins in WebLogic Server 7.0 support SSL communication between the plug-in and the back-end WebLogic Server. To upgrade the plug-in, copy the new plug-in over the old one and restart the IIS, Apache, or iPlanet web server.

  • Page 76: Fileservlet

    For details on internationalization in this version, see the Internationalization Guide. Java Transaction API (JTA) JTA has changed as follows: WebLogic Server 7.0 supports the JTA 1.0.1 specification. Updated JTA documentation is provided in Programming WebLogic JTA. 2-28 BEA WebLogic Server 7.0 Upgrade Guide...

  • Page 77: Java Database Connectivity (Jdbc)

    Warning-level message if it included a non-existent page. In WebLogic Server 6.0 and later, it reports 500 Internal Server Error in that case.You can avert the error by placing an empty file at the referenced location. BEA WebLogic Server 7.0 Upgrade Guide 2-29...

  • Page 78: Null Attributes

    JVM. The latest information regarding certified JVMs is available at the Certifications Page. The following tips are for users porting to WebLogic Server 7.0 who used RMI in their previous version of WebLogic Server: Re-run the WebLogic RMI compiler, , on any existing code to weblogic.rmic...

  • Page 79: Security

    Upgrading to the New Security Architecture WebLogic Server 7.0 has a new security architecture. Upgrading WebLogic Server 4.5 or 5.1 to the security functionality in WebLogic Server 7.0 is a two-step process. 1. Upgrade your security configuration to WebLogic Server 6.x.

  • Page 80: Digital Certificates Generated By The Certificate Servlet

    ----------END RSA PRIVATE KEY---------- 2. Check to see if the digital certificate has an extra line at the end of the file. The following should be the last line of the certificate file: 2-32 BEA WebLogic Server 7.0 Upgrade Guide...

  • Page 81: Session Porting

    Deployment Descriptor Elements in Assembling and Configuring Web Applications for more information. Standalone HTML and JSPs In the original domain provided with WebLogic Server 7.0, as well as in any domains that have been created using the file converter, weblogic.properties directory is created.

  • Page 82: Web Components

    Upgrading WebLogic Server 4.5 and 5.1 to Version 7.0 Web Components The following tips are for users porting to WebLogic Server 7.0 who used Web components in their previous version of WebLogic Server: All Web components in WebLogic Server now use Web Applications as the mechanism for defining how WebLogic Server serves up JSPs, servlets, and static HTML pages.

  • Page 83: Wireless Application Protocol Applications

    Additional Porting and Deployment Considerations Wireless Application Protocol Applications To run a Wireless Application Protocol (WAP) application on WebLogic Server 7.0, you must now specify the MIME types associated with WAP in the file of web.xml the web application. In WebLogic Server 5.1, the default mime-type can be set using where its default weblogic.httpd.defaultMimeType...

  • Page 84: Xml 7.0 Parser And Transformer

    Upgrading WebLogic Server 4.5 and 5.1 to Version 7.0 XML 7.0 Parser and Transformer The built-in parser and transformer in WebLogic Server 7.0 have been updated to Xerces 1.4.4 and Xalan 2.2, respectively. If you used the APIs that correspond to older...

  • Page 85: Removed Apis And Features

    Additional Porting and Deployment Considerations Zero Administration Client (ZAC) is deprecated and should be replaced by JavaWebStart. -Dweblogic.management.host is deprecated in this release of WebLogic Server 7.0 and is weblogic.deploy replaced by . For more information, see Deployment Tools weblogic.Deployer and Procedures in Developing WebLogic Server Applications.
  • Page 86 Upgrading WebLogic Server 4.5 and 5.1 to Version 7.0 This feature relied on the Microsoft JVM (Jview), which is no longer supported. 2-38 BEA WebLogic Server 7.0 Upgrade Guide...
  • Page 87 Property .xml Configuration Console Label Attribute weblogic.administrator.email config.xml: EmailAddress (Administrator element ) weblogic.administrator.location config.xml: Notes (freeform, optional) (Administrator element ) weblogic.administrator.name config.xml: Name (Administrator element ) weblogic.administrator.phone config.xml: PhoneNumber (Administrator element ) BEA WebLogic Server 7.0 Upgrade Guide...

  • Page 88: The Weblogic.properties Mapping Table

    ( WebAppComponent element) applicationname: Configuration: Other: Auth Realm Name weblogic.httpd.charsets config.xml: Charsets ( WebServer element) weblogic.httpd.clustering.enable config.xml: ClusteringEnabled ( WebServer element) Servers: servername: weblogic.httpd.defaultServerName config.xml DefaultServerName Configuration: HTTP: Default Server Name ( WebServer element) BEA WebLogic Server 7.0 Upgrade Guide...
  • Page 89 ( WebServer element) Deployments: Web weblogic.httpd.indexDirectories config.xml: Applications: IndexDirectoryEnabled ( WebAppComponent element) applicationname: Configuration: Files: Index Directories Servers: servername: weblogic.httpd.keepAlive.enable config.xml: Configuration: HTTP: KeepAliveEnabled Enable Keep Alives ( WebServer element) weblogic.httpd.logFileBufferKByt config.xml: LogFileBufferKBytes ( WebServer element) BEA WebLogic Server 7.0 Upgrade Guide...
  • Page 90 Servers: servername: weblogic.httpd.maxLogFileSizeKBy config.xml: MaxLogFileSizeKBytes Logging: HTTP: Max Log File Size Kbytes ( WebServer element) weblogic.httpd.mimeType web.xml: mime-type ( <mime-mapping> element) Servers: servername: weblogic.httpd.postTimeoutSecs config.xml: Configuration: HTTP: PostTimeoutSecs Post Timeout Secs ( WebServer element) BEA WebLogic Server 7.0 Upgrade Guide...
  • Page 91 CacheSize Configuration: SSL: Certificate Cache Size <param-name>/<param-va lue> element pair weblogic.httpd.session.cookie.co weblogic.xml: mment CookieComment <param-name>/<param-va lue> element pair weblogic.httpd.session.cookie.do weblogic.xml: main CookieDomain <param-name>/<param-va lue> element pair weblogic.httpd.session.cookie.ma weblogic.xml: xAgeSecs CookieMaxAgeSecs <param-name>/<param-va lue> element pair BEA WebLogic Server 7.0 Upgrade Guide...
  • Page 92 <param-name>/<param-va lue> element pair weblogic.httpd.session.debug weblogic.xml: SessionDebuggable <param-name>/<param-va lue> element pair weblogic.httpd.session.enable weblogic.xml: TrackingEnabled <param-name>/<param-va lue> element pair weblogic.httpd.session.invalidat weblogic.xml: ionintervalSecs InvalidationIntervalSe <param-name>/<param-va lue> element pair weblogic.httpd.session.jdbc.conn weblogic.xml: TimeoutSecs JDBCConnectionTimeoutS <param-name>/<param-va lue> element pair BEA WebLogic Server 7.0 Upgrade Guide...
  • Page 93 <param-name>/<param-va lue> element pair weblogic.httpd.session.swapinter weblogic.xml: valSecs SwapIntervalSecs <param-name>/<param-va lue> element pair Servers: servername: weblogic.httpd.session.timeoutSe weblogic.xml: TimeoutSecs Configuration: HTTP: Post Timeout Secs <param-name>/<param-va lue> element pair weblogic.httpd.session.URLRewrit weblogic.xml: ing.enable URLRewritingEnabled <param-name>/<param-va lue> element pair BEA WebLogic Server 7.0 Upgrade Guide...
  • Page 94 Enable Tunneling weblogic.httpd.URLResource config.xml: URLResource ( WebServer element) Servers: weblogic.iiop.password config.xml: DefaultIIOPPassword servername: Configuration: ( Server element) Protocols: Default IIOP Password Servers: weblogic.iiop.user config.xml: DefaultIIOPUser servername: Configuration: ( Server element) Protocols: Default IIOP User BEA WebLogic Server 7.0 Upgrade Guide...
  • Page 95 RefreshMinutes autorefresh test testConnsOnReserve =true to test TestConnectionsOnReser connection at reserve testConnsOnRelease =true to test TestConnectionsOnRelea connection at release props =props for JDBC connection Properties JDBCConnectionPool Element ConnLeakProfilingEnabl ACLName CapacityEnabled SupportsLocalTransacti KeepLogicalConnOpenOnR elease Password BEA WebLogic Server 7.0 Upgrade Guide...
  • Page 96 MessagesMaximum Selector Destination weblogic.jms.connectionFactoryAr config.xml: gs.<<factoryName>> JMSConnectionFactory element ClientID ClientID DeliveryMode DefaultDeliveryMode TransactionTimeou t TransactionTimeout UserTransactionsEnable AllowCloseInOnMessage weblogic.jms.connectionFactoryNa config.xml: JMSConnectionFactory element JNDIName weblogic.jms.connectionPool ConnectionPool (JMSJDBCStore element) weblogic.jms.queue config.xml: JNDIName StoreEnabled ( JMSDestination element) A-10 BEA WebLogic Server 7.0 Upgrade Guide...
  • Page 97 Transacted ( JMSSessionPool element) Servers: weblogic.jndi.transportableObjec config.xml: tFactories JNDITransportableObjec servername: tFactoryList ( Server element) Servers: weblogic.login.readTimeoutMillis config.xml LoginTimeoutMillis servername: ( SSL element) Security: General: Audit weblogic.security.audit.provider config.xml Provider Class AuditProviderClassName ( Security element) BEA WebLogic Server 7.0 Upgrade Guide A-11...
  • Page 98 ExportKeyLifespan espan Configuration: SSL: Export Key Lifespan ( SSL element) Servers: servername: weblogic.security.key.server config.xml: Configuration: SSL: ServerKeyFileName Server Key File Name ( SSL element) weblogic.security.ldaprealm.auth config.xml: entication AuthProtocol ( LDAPRealm element) A-12 BEA WebLogic Server 7.0 Upgrade Guide...
  • Page 99 GroupUsernameAttribute ( LDAPRealm element) weblogic.security.ldaprealm.prin config.xml: cipal Principal ( LDAPRealm element) weblogic.security.ldaprealm.ssl config.xml: SSLEnable ( LDAPRealm element) weblogic.security.ldaprealm.url config.xml: LDAPURL ( LDAPRealm element) weblogic.security.ldaprealm.user config.xml: Authentication UserAuthentication ( LDAPRealm element) BEA WebLogic Server 7.0 Upgrade Guide A-13...
  • Page 100 ACLCacheEnable ( CachingRealm element) weblogic.security.realm.cache.ac config.xml: l.size ACLCacheSize ( CachingRealm element) weblogic.security.realm.cache.ac config.xml: l.ttl.negative ACLCacheTTLNegative ( CachingRealm element) weblogic.security.realm.cache.ac config.xml: l.ttl.positive ACLCacheTTLPositive ( CachingRealm element) weblogic.security.realm.cache.au config.xml: th.enable AuthenticationCacheEna ( CachingRealm element) A-14 BEA WebLogic Server 7.0 Upgrade Guide...
  • Page 101 GroupCacheEnable ( CachingRealm element) weblogic.security.realm.cache.gr config.xml: oup.size GroupCacheSize ( CachingRealm element) weblogic.security.realm.cache.gr config.xml: oup.ttl.negative GroupCacheTTLNegative ( CachingRealm element) weblogic.security.realm.cache.gr config.xml: oup.ttl.positive GroupCacheTTLPositive ( CachingRealm element) weblogic.security.realm.cache.pe config.xml: rm.enable PermissionCacheEnable ( CachingRealm element) BEA WebLogic Server 7.0 Upgrade Guide A-15...
  • Page 102 UserCacheTTLNegative ( CachingRealm element) weblogic.security.realm.cache.us config.xml: er.ttl.positive UserCacheTTLPositive ( CachingRealm element) Servers: servername: weblogic.security.realm.certAuth config.xml: enticator CertAuthenticator Configuration: SSL: Cert Authenticator ( SSL element) weblogic.security.SSL.ciphersuit config.xml Ciphersuites ( SSL element) A-16 BEA WebLogic Server 7.0 Upgrade Guide...
  • Page 103 Administration Port weblogic.system.bindAddr config.xml: ListenAddress ( Server element) Servers: weblogic.system.defaultProtocol config.xml: DefaultProtocol servername: Configuration: ( Server element) Protocols: Default Protocol Servers: weblogic.system.defaultSecurePro config.xml: tocol DefaultSecureProtocol servername: Configuration: ( Server element) Protocols: Default Secure Protocol BEA WebLogic Server 7.0 Upgrade Guide A-17...
  • Page 104 ( Server element) Servers: weblogic.system.helpPageURL config.xml HelpPageURL servername: ( Server element) weblogic.system.home config.xml: RootDirectory ( Server element) Servers: servername: weblogic.system.ListenPort config.xml Configuration: SSL: ListenPort Listen Port ( Server element) weblogic.system.logFile config.xml: FileName ( Log element) A-18 BEA WebLogic Server 7.0 Upgrade Guide...
  • Page 105 Configuration: Tuning: ( Server element) Enable Native IO weblogic.system.nonPrivGroup config.xml PostBindGID ( UnixMachine element) weblogic.system.nonPrivUser config.xml PostBindUID ( UnixMachine element) Servers: weblogic.system.percentSocketRea config.xml: ders ThreadPoolPercentSocke servername: tReaders Configuration: Tuning: Socket Readers ( Kernel element) BEA WebLogic Server 7.0 Upgrade Guide A-19...
  • Page 106 Configuration: SSL: ListenPort Listen Port ( SSL element) weblogic.system.startupFailureIs config.xml Fatal FailureIsFatal ( StartupClass element) weblogic.system.user config.xml: SystemUser ( Security element) Servers: weblogic.system.weight config.xml ClusterWeight servername: Configuration: Cluster: ( Server element) Cluster Weight A-20 BEA WebLogic Server 7.0 Upgrade Guide...

  • Page 107: Upgrading The Pet Store Application And The Examples Server

    Upgrading the WebLogic 6.1 Service Pack 2 Examples Server to WebLogic Server 7.0 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.

  • Page 108: Install Weblogic Server 7.0

    It is not necessary to upgrade the WebLogic 6.1 Service Pack 3 Pet Store application to WebLogic Server 7.0; this section just provides the steps to do so as an example of how to upgrade an application from 6.1 to 7.0. To upgrade the WebLogic 6.1 Service Pack 3 Pet Store application for use on WebLogic Server 7.0:...
  • Page 109 WL_HOME time you upgrade. Note: If the directory in WebLogic Server 7.0 to which you copy Pet Store is the same as Pet Store’s directory location in WebLogic Server 6.1, you will not need to edit the file to reflect a new directory location.

  • Page 110: Fix Jsp Parsing Errors

    Examples Server toWebLogic Server 7.0. Note: To upgrade the Pet Store application to WebLogic Server 7.0, it is not necessary to update the DTDs in the weblogic.xml and web.xml files. See weblogic-ejb-jar.xml Document Type Definitions...
  • Page 111 1. In the command console, navigate to WL_HOME\samples\petStore\src\petstore\src\com\sun\j2ee\blueprin . For example: ts\petstore\taglib\list C:\>cd WL_HOME\samples\petStore\src\petstore\src\com\sun\j2ee\blueprin ts\petstore\taglib\list 2. Open in a text editor. For example: CartListTag.java WL_HOME\samples\petStore\src\petstore\src\com\sun\j2ee\blueprin ts\petstore\taglib\list>notepad CartListTag.java. 3. Remove the following lines from CartListTag.java public void setNumItems(String numItemsStr) { super.setNumItems(numItemsStr); BEA WebLogic Server 7.0 Upgrade Guide...

  • Page 112: Rebuild Pet Store

    1. In a command console, change to theWebLogic Server 6.x directory, and set your environment: WL_HOME\config\examples WL_HOME\config\examples> setexamplesenv.cmd 2. In the same console, change to the directory and rebuild: WL_HOME\samples\petStore\src\petstore\src WL_HOME\samples\petStore\src\petstore\src> build The script builds petstore.ear WL_HOME\samples\petStore\src\petstore\build BEA WebLogic Server 7.0 Upgrade Guide...

  • Page 113: Startpetstore.cmd Script Used To Boot Weblogic Server 6.1 Service Pack 3

    @rem required for jDriver for Oracle have been installed in the proper @rem location and that your system PATH variable has been set appropriately. @rem For additional information, refer to Installing and Setting up WebLogic @rem Server (http://e-docs.bea.com/wls/docs61/install/index.html). BEA WebLogic Server 7.0 Upgrade Guide...
  • Page 114 @rem Set WLS_PW equal to your system password for no password prompt server startup. set WLS_PW= @rem Set Production Mode. When set to true, the server starts up in production mode. @rem When set to false, the server starts up in development mode. BEA WebLogic Server 7.0 Upgrade Guide...

  • Page 115: Above-Listed Startpetstore.cmd Script Modified To Boot Weblogic Server 7.0

    :finish cd config\petStore ENDLOCAL above-listed startPetstore.cmd script modified to boot WebLogic Server 7.0 @echo off @rem This script can be used to start WebLogic Server for the purpose @rem of running the PetStore application. This script ensures that @rem the server is started using the config.xml file found in...
  • Page 116 "%JAVA_HOME%/bin/javac.exe" goto runWebLogic echo. echo Javac wasn't found in directory %JAVA_HOME%/bin. echo Please edit the startPetStoreServer.cmd script so that the JAVA_HOME echo variable points to the root directory of your JDK installation. goto finish B-10 BEA WebLogic Server 7.0 Upgrade Guide...
  • Page 117 SET THE -Dbea.home COMMAND LINE OPTION USING THE BEA_HOME VARIABLE YOU SET IN STEP 2. echo on "%JAVA_HOME%\bin\java" -hotspot -ms64m -mx64m -classpath "%CLASSPATH%" -Dweblogic.Domain=petstore -Dweblogic.Name=petstoreServer -Dbea.home="%BEA_HOME%" -Dweblogic.management.password=%WLS_PW% -Dweblogic.ProductionModeEnabled=%STARTMODE% -Dcloudscape.system.home=./samples/eval/cloudscape/data -Djava.security.policy=="d:\610sp2\wlserver6.1/lib/weblogic.pol icy" weblogic.Server goto finish BEA WebLogic Server 7.0 Upgrade Guide B-11...

  • Page 118: Config.xml File Used For Weblogic Server 6.1 Service Pack 3

    PoolName="petstorePool" Targets="petstoreServer"/> <JDBCTxDataSource JNDIName="jdbc.InventoryDB" Name="InventoryDB" PoolName="petstorePool" Targets="petstoreServer"/> <JDBCTxDataSource JNDIName="jdbc.SignOnDB" Name="SignOnDB" PoolName="petstorePool" Targets="petstoreServer"/> <Application Deployed="true" Name="tour" Path="D:\WLS 6.1\wlserver6.1/config/petstore/applications/tour.war"> <WebAppComponent Name="tour" Targets="petstoreServer" URI="tour.war"/> </Application> <Application Deployed="true" Name="petstore" Path="D:\WLS 6.1\wlserver6.1/config/petstore/applications/petstore.ear"> <EJBComponent Name="customerEjb" Targets="petstoreServer" URI="customerEjb.jar"/> <EJBComponent Name="inventoryEjb" B-12 BEA WebLogic Server 7.0 Upgrade Guide...
  • Page 119 Targets="petstoreServer" URI="personalizationEjb.jar"/> <EJBComponent Name="signonEjb" Targets="petstoreServer" URI="signonEjb.jar"/> <EJBComponent Name="shoppingcartEjb" Targets="petstoreServer" URI="shoppingcartEjb.jar"/> <EJBComponent Name="petstoreEjb" Targets="petstoreServer" URI="petstoreEjb.jar"/> <WebAppComponent Name="petstore" Targets="petstoreServer" URI="petstore.war"/> </Application> <Application Deployed="true" Name="petstoreAdmin" Path="D:\WLS 6.1\wlserver6.1/config/petstore/applications/petstoreAdmin.ear> <EJBComponent Name="petstoreAdminEjb" Targets="petstoreServer" URI="petstoreadminEjb.jar"/> <WebAppComponent Name="petstoreadmin" Targets="petstoreServer" URI="petstoreadmin.war"/> </Application> BEA WebLogic Server 7.0 Upgrade Guide B-13...
  • Page 120 Name="petstoreServer"/> <SSL CertificateCacheSize="3" Enabled="true" ListenPort="7002" ServerCertificateChainFileName="./config/petstore/ca.pem" ServerCertificateFileName="./config/petstore/democert.pem" ServerKeyFileName="./config/petstore/demokey.pem" TrustedCAFileName="./config/petstore/ca.pem" Ciphersuites="SSL_RSA_EXPORT_WITH_RC4_40_MD5,SSL_RSA_WITH_DES_C BC_SHA, SSL_RSA_EXPORT_WITH_DES_40_CBC_SHA,SSL_NULL_WITH_NULL_NULL"/> <Log FileName="./config/petstore/logs/weblogic.log"/> </Server> <Log FileName="./config/petstore/logs/wl-domain.log"/> <JDBCConnectionPool CapacityIncrement="1" DriverName="COM.cloudscape.core.JDBCDriver" InitialCapacity="1" MaxCapacity="1" Name="petstorePool" Properties="user=none;password=none;server=none" Targets="petstoreServer" URL="jdbc:cloudscape:petStore"/> <FileRealm Name="myFileRealm"/> <Security Realm="myRealm"/> <Realm FileRealm="myFileRealm" Name="myRealm"/> B-14 BEA WebLogic Server 7.0 Upgrade Guide...

  • Page 121: Above-Listed Config.xml File Used For Weblogic Server 7.0

    FailureIsFatal="false" Name="StartBrowser" Targets="petstoreServer" Notes="On Windows, this class automatically starts a browser after the server has finished booting."/> </Domain> above-listed config.xml file used for WebLogic Server 7.0 1. Change the path to point to your 7.0 file. petstore.ear <Domain ConfigurationVersion="7.0.0.0" Name="petstore"...
  • Page 122 6.1\wlserver6.1/config/petstore/applications/petstore.ear"> <EJBComponent Name="customerEjb" Targets="petstoreServer" URI="customerEjb.jar"/> <EJBComponent Name="inventoryEjb" Targets="petstoreServer" URI="inventoryEjb.jar"/> <EJBComponent Name="mailerEjb" Targets="petstoreServer" URI="mailerEjb.jar"/> <EJBComponent Name="personalizationEjb" Targets="petstoreServer" URI="personalizationEjb.jar"/> <EJBComponent Name="signonEjb" Targets="petstoreServer" URI="signonEjb.jar"/> <EJBComponent Name="shoppingcartEjb" Targets="petstoreServer" URI="shoppingcartEjb.jar"/> <EJBComponent Name="petstoreEjb" Targets="petstoreServer" URI="petstoreEjb.jar"/> <WebAppComponent Name="petstore" Targets="petstoreServer" URI="petstore.war"/> B-16 BEA WebLogic Server 7.0 Upgrade Guide...
  • Page 123 StagedTargets="" TwoPhase="false"> <EJBComponent Name="petstoreAdminEjb" Targets="petstoreServer" URI="petstoreadminEjb.jar"/> <WebAppComponent Name="petstoreadmin" Targets="petstoreServer" URI="petstoreadmin.war"/> </Application> 3. Change the path so that it points to the location of your WebLogic Server 7.0 Java compiler. <Server JavaCompiler="D:\700sp0\jdk131_02/bin/javac" ListenPort="7001" Name="petstoreServer" RootDirectory="D:\700sp0" ThreadPoolSize="15" TransactionLogFilePrefix="config/petstore/logs/" IIOPEnabled="false"> <WebServer DefaultWebApp="tour"...
  • Page 124 Name="myFileRealm"/> <Security Realm="myRealm"/> <Realm FileRealm="myFileRealm" Name="myRealm"/> <MailSession Name="mailSession" Targets="petstoreServer" JNDIName="mail.Session" Properties="mail.from=orders@javapetstoredemo.com;mail.host=san -francisco.beasys.com"/> <StartupClass Arguments="port=7001" ClassName="com.bea.estore.startup.StartBrowser" FailureIsFatal="false" Name="StartBrowser" Targets="petstoreServer" Notes="On Windows, this class automatically starts a browser after the server has finished booting."/> </Domain> B-18 BEA WebLogic Server 7.0 Upgrade Guide...

  • Page 125: Start The Pet Store Application On Weblogic Server 7.0

    Upgrading the WebLogic 6.0 Service Pack 2 Examples Server to WebLogic Server 7.0 Start the Pet Store Application on WebLogic Server 7.0 To start the Pet Store application on WebLogic Server 7.0: 1. Open a new web browser window. 2. Go to http://localhost:7001/estore/index.html 3.
  • Page 126 7.0 directory. For WL_HOME/config/examples example, you could use the following directory structure: c:\my_application_domains\config\examples To upgrade the WebLogic 6.0 Examples Server to WebLogic Server 7.0, you need to edit the following two scripts: setExamplesEnv.cmd startExamplesServer.cmd These scripts are provided in both DOS and Unix versions, , respectively.

  • Page 127: Setexamplesenv.cmd Script Used To Boot A Weblogic 6.0 Service Pack 2

    WebLogic Server 6.0 classes, your WebLogic Server 7.0 classes, and any native libraries that you want to use in WebLogic Server 7.0. The steps used to boot WebLogic Server 7.0 are no different from those used to boot WebLogic Server 6.0.
  • Page 128 @echo Please edit the setEnv.cmd script so that the JAVA_HOME @echo variable points to the location of your JDK. @echo Your environment has not been set. @goto finish :setEnv set APPLICATIONS=%WL_HOME%\config\examples\applications set CLIENT_CLASSES=%WL_HOME%\config\examples\clientclasses set SERVER_CLASSES=%WL_HOME%\config\examples\serverclasses EX_WEBAPP_CLASSES=%WL_HOME%\config\examples\applications\exampl esWebApp\WEB-INF\classes CLASSPATH=%JAVA_HOME%\lib\tools.jar;%WL_HOME%\lib\weblogic_sp. B-22 BEA WebLogic Server 7.0 Upgrade Guide...

  • Page 129: Above-Listed Setexamplesenv.cmd Script Modified To Boot A Weblogic 7.0 Examples Server

    Upgrading the WebLogic 6.0 Service Pack 2 Examples Server to WebLogic Server 7.0 jar;%WL_HOME%\lib\weblogic.jar;%WL_HOME%\lib\xmlx.jar;%WL_HOME% \samples\eval\cloudscape\lib\cloudscape.jar;%CLIENT_CLASSES%; %SERVER_CLASSES%;%EX_WEBAPP_CLASSES%;D:\WLS 6.0 set PATH=%WL_HOME%\bin;%JAVA_HOME%\bin;%PATH% @echo. @echo Your environment has been set. :finish above-listed setExamplesEnv.cmd script modified to boot a WebLogic 7.0 Examples Server @echo on...
  • Page 130 6. Point to the directory used to store server-side classes. set SERVER_CLASSES=%WL60_HOME%\config\examples\serverclasses 7. Point to the directory used to store classes used by the Examples Web Application. EX_WEBAPP_CLASSES=%WL60_HOME%\config\examples\applications\exam plesWebApp\WEB-INF\classes 8. Point to the WebLogic Server 6.0 and WebLogic Server 7.0 classes. CLASSPATH=%JAVA_HOME%\lib\tools.jar;%WL_HOME%\lib\weblogic_sp. jar;%WL_HOME%\lib\weblogic.jar;%WL_HOME%\lib\xmlx.jar;%WL60_ HOME%\samples\eval\cloudscape\lib\cloudscape.jar;%CLIENT_ CLASSES%;%SERVER_CLASSES%;%EX_WEBAPP_CLASSES% 9. Point to your 7.0 home.

  • Page 131: Startexamplesserver.cmd Script Used To Boot A Weblogic 6.0 Service Pack 2 Examples Server

    Upgrading the WebLogic 6.0 Service Pack 2 Examples Server to WebLogic Server 7.0 startExamplesServer.cmd script used to boot a WebLogic 6.0 Service Pack 2 Examples Server @echo off @rem This script can be used to start WebLogic Server for the @rem purpose @rem of running the examples.

  • Page 132: Above-Listed Startexamplesserver.cmd Script Modified To Boot A Weblogic 7.0 Examples Server

    %JAVA_HOME%\bin\java -hotspot -ms64m -mx64m -classpath %CLASSPATH% -Dweblogic.Domain=examples -Dweblogic. Name=examplesServer -Dbea.home=D:\WLS 6.0 -Dcloudscape.system.home=./samples/eval/cloudscape/ data -Djava.security.policy==D:\WLS 6.0\wlserver6.0/lib/weblogic.policy weblogic.Server goto finish :finish cd config\examples ENDLOCAL above-listed startExamplesServer.cmd script modified to boot a WebLogic 7.0 Examples Server @echo off SETLOCAL B-26 BEA WebLogic Server 7.0 Upgrade Guide...
  • Page 133 2. Set in order to be able to access your WebLogic Server 6.0 classes. WL60_HOME set WL60_HOME=c:\bea60sp2\wlserver6.0 3. Set this in order to be able to access your WebLogic Server 7.0 classes. set WL_HOME=c:\bea700\weblogic700 :checkJRE if exist %JAVA_HOME%\lib\nul goto runWebLogic echo.
  • Page 134 :finish ENDLOCAL Start the Examples Server on WebLogic Server 7.0 To start the Examples Server on WebLogic Server 7.0: On Windows: 1. On the taskbar, click Start. 2. Choose Programs. 3. Choose BEA WebLogic E-Business Platform. 4. Choose WebLogic Server 7.0.

  • Page 135: Upgrading The Weblogic 6.1 Service Pack 2 Examples Server To Weblogic Server 7.0

    Upgrading the WebLogic 6.1 Service Pack 2 Examples Server to WebLogic Server 7.0 2. Double-click the startExamplesServer icon. 3. Watch for the Out-of-the-Box Examples Index Page. On UNIX Bourne shell: 1. cd $SAMPLES_HOME/server/config/examples 2. sh startExamplesServer.sh Upgrading the WebLogic 6.1 Service Pack 2 Examples Server to WebLogic Server 7.0...
  • Page 136 For WL_HOME/config/examples example, you could use the following directory structure: c:\my_application_domains\config\examples To upgrade the WebLogic 6.1 Examples Server to WebLogic Server 7.0, you need to edit the following two scripts: setExamplesEnv.cmd startExamplesServer.cmd These scripts are provided in both DOS and Unix versions, , respectively.
  • Page 137 WebLogic Server 6.1 classes, your WebLogic Server 7.0 classes, and any native libraries that you want to use in WebLogic Server 7.0. The steps used to boot WebLogic Server 7.0 are no different from those used to boot WebLogic Server 6.1.
  • Page 138 @echo variable points to the location of your JDK. @echo Your environment has not been set. @goto finish :setEnv set APPLICATIONS=%WL_HOME%\config\examples\applications set CLIENT_CLASSES=%WL_HOME%\config\examples\clientclasses set SERVER_CLASSES=%WL_HOME%\config\examples\serverclasses set EX_WEBAPP_CLASSES=%WL_HOME%\config\examples\applications\ examplesWebApp\WEB-INF\classes set CLASSPATH=%JAVA_HOME%\lib\tools.jar;%WL_HOME%\lib\ weblogic_sp.jar;%WL_HOME%\lib\weblogic.jar;%WL_HOME%\lib\ xmlx.jar;%WL_HOME%\samples\eval\cloudscape\lib\cloudscape.jar; %CLIENT_CLASSES%;%SERVER_CLASSES%;%EX_WEBAPP_CLASSES%; D:\WLS 6.1 B-32 BEA WebLogic Server 7.0 Upgrade Guide...

  • Page 139: Above-Listed Setexamplesenv.cmd Script Modified To Boot Weblogic Server 7.0

    Upgrading the WebLogic 6.1 Service Pack 2 Examples Server to WebLogic Server 7.0 set PATH=%WL_HOME%\bin;%JAVA_HOME%\bin;%PATH% @echo. @echo Your environment has been set. :finish above-listed setExamplesEnv.cmd script modified to boot WebLogic Server 7.0 @echo on @rem This script should be used to set up your environment for @rem compiling and running the examples included with WebLogic @rem Server.

  • Page 140: Startexamplesserver.cmd Script Used To Boot A Weblogic 6.1 Service Pack 2 Examples Server

    6. Point to the directory used to store server-side classes. set SERVER_CLASSES=%WL61_HOME%\config\examples\serverclasses 7. Point to the directory used to store classes used by the Examples Web Application. EX_WEBAPP_CLASSES=%WL61_HOME%\config\examples\applications\exam plesWebApp\WEB-INF\classes 8. Point to the WebLogic Server 6.1 and WebLogic Server 7.0 classes. CLASSPATH=%JAVA_HOME%\lib\tools.jar;%WL_HOME%\lib\weblogic_sp. jar;%WL_HOME%\lib\weblogic.jar;%WL_HOME%\lib\xmlx.jar;%WL61_ HOME%\samples\eval\cloudscape\lib\cloudscape.jar;%CLIENT_ CLASSES%;%SERVER_CLASSES%;%EX_WEBAPP_CLASSES% 9. Point to your 7.0 home.
  • Page 141 Upgrading the WebLogic 6.1 Service Pack 2 Examples Server to WebLogic Server 7.0 @rem This script can be used to start WebLogic Server for the purpose @rem of running the examples. This script ensures that the server is started @rem using the config.xml file found in this directory and that the CLASSPATH @rem is set appropriately.
  • Page 142 * browser. echo *************************************************** @rem Set WLS_PW equal to your system password for no password prompt server startup. set WLS_PW= echo on "%JAVA_HOME%\bin\java" -hotspot -ms64m -mx64m -classpath "%CLASSPATH%" -Dweblogic.Domain=examples -Dweblogic.Name=examplesServer -Dweblogic.management.password=%WLS_PW% -Dbea.home="D:\WLS 6.1" B-36 BEA WebLogic Server 7.0 Upgrade Guide...

  • Page 143: Above-Listed Startexamplesserver.cmd Script Modified To Boot Weblogic Server 7.0

    @rem added: 2. Set this in order to be able to access your WebLogic Server 6.1 classes. set WL61_HOME=c:\bea61sp2\wlserver6.1 3. Set this in order to be able to access your WebLogic Server 7.0 classes. set WL_HOME=c:\bea700\weblogic700 :checkJRE if exist %JAVA_HOME%\lib\nul goto runWebLogic echo.
  • Page 144 @rem -classpath %CLASSPATH% -Dweblogic.Domain=examples @rem -Dweblogic.Name=examplesServer -Dbea.home=C:\bea61sp2 @rem -Dcloudscape.system.home @rem =./samples/eval/cloudscape/data @rem -Djava.security.policy==C:\bea61sp2\wlserver6.1 @rem /lib/weblogic.policy weblogic.Server %JAVA_HOME%\bin\java -hotspot -ms64m -mx64m -classpath %CLASSPATH% -Dweblogic.Name=examplesServer -Dweblogic.ProductionModeEnabled=true -Dbea.home=C:\bea700 -Dcloudscape.system.home=%WL61_HOME%/ samples/eval/cloudscape/data -Djava.security.policy==%WL61_HOME%/lib/weblogic.policy weblogic.Server goto finish :finish ENDLOCAL B-38 BEA WebLogic Server 7.0 Upgrade Guide...

  • Page 145: Start The Examples Server On Weblogic Server 7.0

    Upgrading the WebLogic 6.1 Service Pack 2 Examples Server to WebLogic Server 7.0 Start the Examples Server on WebLogic Server 7.0 To start the Examples Server on WebLogic Server 7.0: On Windows: 1. On the taskbar, click Start. 2. Choose Programs.
  • Page 146 Upgrading the Pet Store Application and the Examples Server B-40 BEA WebLogic Server 7.0 Upgrade Guide...

This manual is also suitable for:

Weblogic server 7.0

Table of Contents