bea.com | products | dev2dev | support | askBEA

Download Docs | Site Map | Glossary
Search

WebLogic Server 7.0 Upgrade Guide

Upgrading the Pet Store Application and the Examples Server

This appendix presents examples of the following processes:

- Upgrading the Pet Store Application From WebLogic 6.1 Service Pack 3 to WebLogic Server 7.0

- Upgrading the WebLogic 6.0 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

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.

Terms Used in This Document

Where all three versions are being discussed, the instructions use version-specific terms for WebLogic home directories. These conventions are used in this document to make explaining how to port your domain configurations easier.

In this document WL_HOME is defined to be the home of WebLogic Server 6.x and 7.0.

For 6.0 WL_HOME=D:\WLS_6.0\wlserver6.0

For 6.1 WL_HOME=D:\WLS_6.1\wlserver6.1

For 7.0 WL_HOME=D:\WLS_7.0\weblogic700

Upgrading the Pet Store Application From WebLogic 6.1 Service Pack 3 to 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:

1. Install WebLogic Server 7.0.

2. Set Up the WebLogic Server 7.0 Environment with Your 6.1 Service Pack 3 Domain Configuration.

3. Start the Pet Store Application on WebLogic Server 7.0.

Install WebLogic Server 7.0

Install WebLogic Server 7.0. See the Installation Guide.

Note: Installing the new version in the exact location of the old version is explicitly prohibited by the installer.

Set Up the WebLogic Server 7.0 Environment with Your 6.1 Service Pack 3 Domain Configuration

To upgrade the Pet Store application from WebLogic Server 6.1 Service Pack 3 to WebLogic Server 7.0:

1. Repair tag library errors in Pet Store that were accepted under WebLogic Server 6.x but are rejected by the parser in WebLogic Server 7.0.

2. Copy the WL_HOME/config/petstore directory from WebLogic Server 6.1 to a location in your WebLogic Server 7.0 installation. BEA recommends not copying the directory to WL_HOME in order to avoid having to move the domain the next 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 config.xml file to reflect a new directory location. If you copy Pet Store to a different directory location, you will need to find all of the fully qualified file and directory paths in your config.xml file and change them to relative paths.

1. Edit the startPetstore.cmd script to reflect the new WebLogic Server 7.0 installation as well as the new directory location (if you have one).

2. Edit the config.xml file to reflect the new WebLogic Server 7.0 installation as well as the new directory location (if you have one).

This section contains:

- Instructions for fixing the Pet Store errors: Fix JSP Parsing Errors" on page 4.

- An example of the startPetstore.cmd script used to boot WebLogic Server 6.1 Service Pack 3" on page 7.

- An example of the above-listed startPetstore.cmd script modified to boot WebLogic Server 7.0" on page 9.

- An example of the config.xml file used for WebLogic Server 6.1 Service Pack 3" on page 12.

- An example of the above-listed config.xml file used for WebLogic Server 7.0 which includes explanations for how to change this script to upgrade the 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 in Programming WebLogic Enterprise JavaBeans for information on WebLogic Server 7.0 DTDs

Fix JSP Parsing Errors

Minor errors that were parsable in earlier versions of WebLogic Server cause errors in WebLogic Server 8.1 because JDK 1.4 does not accept them. The errors corrected in this section are property settings for which the method and setter properties do not agree.

Correcting the errors requires making changes to these source files:

>     ListTag.java

>     CartListTag.java

>     MyListTag.java

>     ProductItemListTag.java

>     ProductListTag.java

>     SearchListTag.java

All of these files are located in the WL_HOME\samples\petStore\src\petstore\src\com\sun\j2ee\blueprints\petstore\taglib\list directory (where WL_HOME is the WebLogic Server installation directory)

Use these steps to make the replacement in ListTag.java:

1. In a command console, navigate to WL_HOME\samples\petStore\src\petstore\src\com\sun\j2ee\blueprints\petstore\taglib\list. For example:

   C:\> cd WL_HOME\samples\petStore\src\petstore\src\com\sun\j2ee\blueprints\petstore\taglib\list

2. Open ListTag.java in a text editor. For example:

   WL_HOME\samples\petStore\src\petstore\src\com\sun\j2ee\blueprints\petstore\taglib\list>notepad ListTag.java.

3. Change:

   >     public void setNumItems(String numItemsStr) {

   numItems = Integer.parseInt(numItemsStr);

   }

   to:

   >     public void setNumItems(int numItemsIn) {

   >     numItems = numItemsIn;

   >     }

4. Change:

   >     public void setStartIndex(String startIndexStr) {

   >     startIndex = Integer.parseInt(startIndexStr);

   >     }

   to:

   >     public void setStartIndex(int startIndexIn) {

   >     startIndex = startIndexIn;

   >     }

5. Save and close ListTag.java.

Make the replacements in the rest of the files as follows:

1. In the command console, navigate to WL_HOME\samples\petStore\src\petstore\src\com\sun\j2ee\blueprints\petstore\taglib\list. For example:

   C:\>cd WL_HOME\samples\petStore\src\petstore\src\com\sun\j2ee\blueprints\petstore\taglib\list

2. Open CartListTag.java in a text editor. For example:

   WL_HOME\samples\petStore\src\petstore\src\com\sun\j2ee\blueprints\petstore\taglib\list>notepad CartListTag.java.

3. Remove the following lines from CartListTag.java:

   >     public void setNumItems(String numItemsStr) {

   >     super.setNumItems(numItemsStr);

   >     }

   >       public void setStartIndex(String startIndexStr) {

   >     super.setNumItems(startIndexStr);

   >     }

4. Replace with the following:

   >     public void setNumItems(int numItems) {

   >     super.setNumItems(numItems);

   >     }

   >     public void setStartIndex(int startIndex) {

   >     super.setNumItems(startIndex);

   >     }

5. Save and close ProductListTag.java.

6. Repeat steps 1 through 5 for the remaining files:

   >     MyListTag.java

   >     ProductItemListTag.java

   >     ProductListTag.java

   >     SearchListTag.java

Rebuild Pet Store

After making the corrections to Pet Store, rebuild the application.

1. In a command console, change to theWebLogic Server 6.x WL_HOME\config\examples directory, and set your environment:

   WL_HOME\config\examples> setexamplesenv.cmd (or .sh)

2. In the same console, change to the WL_HOME\samples\petStore\src\petstore\src directory and rebuild:

   WL_HOME\samples\petStore\src\petstore\src> build

   The script builds petstore.ear to WL_HOME\samples\petStore\src\petstore\build.

startPetstore.cmd script used to boot WebLogic Server 6.1 Service Pack 3

>     @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 the server is started
>     @rem using the config.xml file found in this directory and that the CLASSPATH
>     @rem is set appropriately. This script contains the following variables:
>     @rem
>     @rem JAVA_HOME      - Determines the version of Java used to start
>     @rem                  WebLogic Server. This variable must point to the
>     @rem                  root directory of a JDK installation. and will be set
>     @rem                  for you by the WebLogic Server installer. Note that
>     @rem                  this script uses the hotspot VM to run WebLogic Server.
>     @rem                  If you choose to use a JDK other than the one
>     @rem                  included in the disribution, make sure that the JDK
>     @rem                  includes the hotspot VM. See the WebLogic platform
>     @rem                  support page (http://e-docs.bea.com/wls/platforms/index.html)
>     @rem                  for an up-to-date list of supported JVMs on Windows NT.
>     @rem
>     @rem When setting these variables below, please use short file names (8.3).
>     @rem To display short (MS-DOS) filenames, use "dir /x". File names with
>     @rem spaces will break this script.
>     @rem
>     @rem jDriver for Oracle users: This script assumes that native libraries
>     @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).

>     SETLOCAL

>     cd ..\..

>     @rem Set user-defined variables.
>     set JAVA_HOME=d:\610sp2\jdk131

>     @rem Check that script is being run from the appropriate directory
>     if not exist lib\weblogic.jar goto wrongplace
>     goto checkJDK

>     @rem :wrongplace
>     @rem echo startPetStore.cmd must be run from the config\petStore directory. 1>&2
>     @rem goto finish

>     :checkJDK
>     if exist "%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

>     :runWebLogic
>     echo on
>     set PATH=.\bin;"%JAVA_HOME%\bin";%PATH%

>     set CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar;.\
>     samples\eval\cloudscape\lib\cloudscape.jar;.\config\petStore\serverclasses
>     echo off

>     echo.
>     echo ***************************************************
>     echo *  To start WebLogic Server, use the password     *
>     echo *  assigned to the system user.  The system       *
>     echo *  username and password must also be used to     *
>     echo *  access the WebLogic Server console from a web  *
>     echo *  browser.                                       *
>     echo ***************************************************

>     @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.  The default is false.
>     set STARTMODE=true

>     echo on
>     "%JAVA_HOME%\bin\java" -hotspot -ms64m -mx64m -classpath "%CLASSPATH%"
>     -Dweblogic.Domain=petstore -Dweblogic.Name=petstoreServer
>     -Dbea.home="d:\610sp2" -Dweblogic.management.password=%WLS_PW%
>     -Dweblogic.ProductionModeEnabled=%STARTMODE%
>     -Dcloudscape.system.home=./samples/eval/cloudscape/data
>     -Djava.security.policy=="d:\610sp2\wlserver6.1/lib/weblogic.policy" weblogic.Server
>     goto finish

>     :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
>     @rem this directory and that the CLASSPATH is set appropriately.
>     @rem This script contains the following variables:
>     @rem
>     @rem JAVA_HOME      - Determines the version of Java used to start
>     @rem                  WebLogic Server. This variable must point to the
>     @rem                  root directory of a JDK installation. and will be set
>     @rem                  for you by the WebLogic Server installer. Note that
>     @rem                  this script uses the hotspot VM to run WebLogic Server.
>     @rem                  If you choose to use a JDK other than the one
>     @rem                  included in the disribution, make sure that the JDK
>     @rem                  includes the hotspot VM. See the WebLogic platform
>     @rem                  support page (http://e-docs.bea.com/wls/platforms/index.html)
>     @rem                  for an up-to-date list of supported JVMs on Windows NT.
>     @rem
>     @rem When setting these variables below, please use short file names (8.3).
>     @rem To display short (MS-DOS) filenames, use "dir /x". File names with
>     @rem spaces will break this script.
>     @rem
>     @rem jDriver for Oracle users: This script assumes that native libraries
>     @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).

>     SETLOCAL

>     cd ..\..

>     @rem Set user-defined variables.
>     @rem 1.  SET THE NEW JAVA HOME APPROPRIATELY
>     set JAVA_HOME=D:\70bea\jdk131

>     @rem 2.  FOR SIMPLICITY, CREATE AND SET BEA_HOME AND WL_HOME70
>     set BEA_HOME=d:\wls70
>     set WL_HOME70=%BEA_HOME%\weblogic700

>     @rem 3.  REMOVE THIS ENTIRE CHECK AND ITS TAG SINCE
>     @rem NEITHER IS RELEVANT ANY LONGER
>     @rem Check that script is being run from the appropriate directory
>     @rem if not exist lib\weblogic.jar goto wrongplace
>     @rem goto checkJDK

>     @rem :wrongplace
>     @rem echo startPetStore.cmd must be run from the config\petStore directory. 1>&2
>     @rem goto finish

>     :checkJDK
>     if exist "%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

>     @rem 4.  SET THE PATH VARIABLE APPROPRIATELY USING WL_HOME70 YOU DEFINED IN STEP 2 ABOVE
>     :runWebLogic
>     echo on
>     set PATH=%WL_HOME70%\server\bin;"%JAVA_HOME%\bin";%PATH%

>     @rem 5.  SET YOUR CLASSPATH SO THE NEW WLS70 CLASSES ARE USED WHILE RETAINING ALL CLASS LOCATIONS
>     @rem RELEVANT TO YOUR APPLICATION.  TO DO THIS, USE WL_HOME70 YOU SET IN STEP 2.
>     set CLASSPATH=.;%WL_HOME70%\server\lib\weblogic.jar;.\samples\
>     eval\cloudscape\lib\cloudscape.jar;.\config\petStore\serverclasses
>     echo off

>     echo.
>     echo ***************************************************
>     echo *  To start WebLogic Server, use the password     *
>     echo *  assigned to the system user.  The system       *
>     echo *  username and password must also be used to     *
>     echo *  access the WebLogic Server console from a web  *
>     echo *  browser.                                       *
>     echo ***************************************************

>     @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.  The default is false.
>     set STARTMODE=true

>     @rem 6.  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.policy" weblogic.Server
>     goto finish

>     :finish
>     cd config\petStore
>     ENDLOCAL

config.xml file used for WebLogic Server 6.1 Service Pack 3

>     <Domain
>     Name="petstore">
>     <JDBCTxDataSource
>     JNDIName="jdbc.EstoreDB"
>     Name="EstoreDB"
>     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"
>     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"/>

>     </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>

>     <Server
>     JavaCompiler="D:\WLS 6.1\jdk131/bin/javac"
>     ListenPort="7001"
>     Name="petstoreServer"
>     RootDirectory="D:\WLS 6.1\wlserver6.1"
>     ThreadPoolSize="15"
>     TransactionLogFilePrefix="config/petstore/logs/"
>     IIOPEnabled="false">

>     <WebServer
>     DefaultWebApp="tour"
>     LogFileName="./config/petstore/logs/access.log"
>     LoggingEnabled="true"
>     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_CBC_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"/>

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

above-listed config.xml file used for WebLogic Server 7.0

1. Change the path to point to your 7.0 petstore.ear file.

   >     <Domain ConfigurationVersion="7.0.0.0"
   >     Name="petstore" Path="D:\700sp0\weblogic700\samples\server\config\petstore\applications\
   >     petstore.ear" StagedTargets="" TwoPhase="false">

   >     <JDBCTxDataSource
   >     JNDIName="jdbc.EstoreDB"
   >     Name="EstoreDB"
   >     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"
   >     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"/>

   >     </Application>

2. Change the path to point to your petstoreAdmin.ear file.

   >     <Application
   >     Deployed="true"
   >     Name="petstoreAdmin"
   >     Path="D:\700sp0\weblogic700\samples\server\config\petstore\applications\
   >     petstoreAdmin.ear" 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"
   >     LogFileName="./config/petstore/logs/access.log"
   >     LoggingEnabled="true"
   >     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_CBC_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"/>

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

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. Click Enter the Store.

Upgrading the WebLogic 6.0 Service Pack 2 Examples Server to WebLogic Server 7.0

It is not necessary to upgrade the WebLogic 6.0 Examples Server to WebLogic Server 7.0; this section just provides the steps to do so as an example of how to upgrade a server from 6.0 to 7.0. To upgrade the WebLogic 6.0 Examples Server domain configuration for use on WebLogic Server 7.0:

- Install WebLogic Server 7.0

- Set Up the WebLogic Server 7.0 Environment with Your 6.0 Service Pack 2 Domain Configuration

- Start the Examples Server on WebLogic Server 7.0

Install WebLogic Server 7.0

Install WebLogic Server 7.0. See the Installation Guide.

Note: Installing the new version in the exact location of the old version is explicitly prohibited by the installer.

Set Up the WebLogic Server 7.0 Environment with Your 6.0 Service Pack 2 Domain Configuration

It is important to keep the examples domain directory within the config directory when you copy your 6.0 WL_HOME/config/examples directory to your 7.0 directory. For 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, .cmd and .sh, respectively.

The setExamplesEnv script at SAMPLES_HOME\server\config\examples sets certain environment variables in your development shell, the command window from which you build and run the examples.

setExamplesEnv sets these variables:

- CLASSPATH

  contains all of the classes needed to build and run the examples

- CLIENT_CLASSES

  points to the directory that stores client classes

- SERVER_CLASSES

  points to the directory that stores server-side classes

- EX_WEBAPP_CLASSES

  points to the directory that stores classes used by the Examples Web Application

- PATH

  contains your system path, appended with the JDK and WebLogic Server bin directories

The java and javac commands use the CLASSPATH variable to locate the Java classes that are required to compile source files and run examples. CLASSPATH must contain the appropriate classes for compiling and running the example.

To upgrade the Examples Server from WebLogic Server 6.0 to WebLogic Server 7.0, you must edit the WebLogic Server 7.0 setExamplesEnv.cmd script so that you can access your 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.

This section contains:

- An example of the setExamplesEnv.cmd script used to boot a WebLogic 6.0 Service Pack 2 Examples Server.

- An example of the above-listed setExamplesEnv.cmd script modified to boot a WebLogic 7.0 Examples Server which includes explanations for how to change this script to upgrade the Examples Server toWebLogic Server 7.0.

- An example of the startExamplesServer.cmd script used to boot a WebLogic 6.0 Service Pack 2 Examples Server.

- An example of the above-listed startExamplesServer.cmd script modified to boot a WebLogic 7.0 Examples Server which includes explanations for how to change this script to upgrade the Examples Server toWebLogic Server 7.0.

setExamplesEnv.cmd script used to boot a WebLogic 6.0 Service Pack 2 Examples Server

>     @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. It contains the following variables:
>     @rem
>     @rem WL_HOME   - This must point to the root directory of your WebLogic
>     @rem             installation.
>     @rem JAVA_HOME - Determines the version of Java used to compile
>     @rem             and run examples. This variable must point to the
>     @rem             root directory of a complete JDK installation. See
>     @rem             the WebLogic platform support page
>     @rem             (http://e-docs.bea.com/wls/platforms/index.html)
>     @rem             for an up-to-date list of supported JVMs on
>     @rem 	 				Windows NT.
>     @rem
>     @rem When setting these variables below, please use short file names(8.3).
>     @rem To display short (MS-DOS) filenames, use "dir /x". File
>     @rem names with
>     @rem spaces will break this script.
>     @rem
>     @rem jDriver for Oracle users: This script assumes that native libraries
>     @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 (/install/index.html in your local documentation set or on the
>     @rem Internet at
>     @rem http://e-docs.bea.com/wls/docs60/install/index.html).

>     @rem Set user-defined variables.
>     set WL_HOME=D:\WLS_6.0\wlserver6.0
>     set JAVA_HOME=D:\WLS_6.0\jdk130

>     @if exist %WL_HOME%\lib\weblogic.jar goto checkJava
>     @echo.
>     @echo The WebLogic Server wasn't found in directory %WL_HOME%.
>     @echo Please edit the setExamplesEnv.cmd script so that the
>     @echo WL_HOME
>     @echo variable points to the WebLogic Server installation
>     @echo directory.
>     @echo Your environment has not been set.
>     @goto finish

>     :checkJava

>     @if exist %JAVA_HOME%\bin\java.exe goto setEnv
>     @echo.
>     @echo The JDK wasn't found in directory %JAVA_HOME%.
>     @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
>     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.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
>     @rem This script should be used to set up your environment for
>     @rem compiling and running the examples included with WebLogic
>     @rem Server. It contains the following variables:
>     @rem
>     @rem WL_HOME   - This must point to the root directory of your WebLogic
>     @rem             installation.
>     @rem JAVA_HOME - Determines the version of Java used to compile
>     @rem             and run examples. This variable must point to the
>     @rem             root directory of a complete JDK installation. See
>     @rem             the WebLogic platform support page
>     @rem             (http://e-docs.bea.com/wls/platforms/index.html)
>     @rem             for an up-to-date list of supported JVMs on Windows NT.
>     @rem
>     @rem When setting these variables below, please use short file @rem names(8.3).
>     @rem To display short (MS-DOS) filenames, use "dir /x". File
>     @rem names with
>     @rem spaces will break this script.
>     @rem
>     @rem jDriver for Oracle users: This script assumes that native libraries
>     @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 (/install/index.html in your local documentation set or on the
>     @rem Internet at
>     @rem http://e-docs.bea.com/wls/docs60/install/index.html).

>     @rem Set user-defined variables.
>     @rem changed: set WL_HOME=C:\bea60sp2\wlserver6.0

1. Set the WL60_HOME variable so that you can access your WebLogic Server 6.0 classes.

   >     set WL60_HOME=C:\bea60sp2\wlserver6.0

2. Set the WL_HOME variable so that you can access your WebLogic Server 7.0 classes.

   >     set WL_HOME=C:\bea700\weblogic700

   >     @rem changed: set JAVA_HOME=C:\bea60sp2\jdk130

3. Point to the JDK on WebLogic Server 7.0.

   >     set JAVA_HOME=c:\bea700\jdk131

4. Point to application archives created when you build the examples.

   >     set APPLICATIONS=%WL60_HOME%\config\examples\applications

5. Point to the directory used to store client classes.

   >     set CLIENT_CLASSES=%WL60_HOME%\config\examples\clientclasses

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.

   >     set EX_WEBAPP_CLASSES=%WL60_HOME%\config\examples\applications\examplesWebApp\WEB-INF\classes

8. Point to the WebLogic Server 6.0 and WebLogic Server 7.0 classes.

   >     set 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 %WL_HOME% 7.0 home.

   >     set PATH=%WL_HOME%\bin;%JAVA_HOME%\bin;%PATH%

   >     @echo.
   >     @echo Your environment has been set.

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. 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. This script contains the following
>     @rem variable:
>     @rem
>     @rem JAVA_HOME      - Determines the version of Java used to start
>     @rem                  WebLogic Server. This variable must point to the
>     @rem                  root directory of a JDK installation and will be set
>     @rem                  for you by the WebLogic Server installer. Note that
>     @rem                  this script uses the hotspot VM to run WebLogic Server.
>     @rem                  If you choose to use a JDK other than the one
>     @rem                  included in the disribution, make sure that the JDK
>     @rem                  includes the hotspot VM. See the WebLogic platform
>     @rem                  support page
>     @rem (http://e-docs.bea.com/wls/platforms/index.html)
>     @rem                  for an up-to-date list of supported JVMs @rem on Windows NT.
>     @rem
>     @rem When setting the variable below, please use short file names (8.3).
>     @rem To display short (MS-DOS) filenames, use "dir /x". File
>     @rem names with
>     @rem spaces will break this script.
>     @rem
>     @rem jDriver for Oracle users: This script assumes that native
>     @rem libraries
>     @rem required for jDriver for Oracle have been installed in the
>     @rem proper
>     @rem location and that your system PATH variable has been set
>     @rem appropriately.
>     @rem For additional information, refer to Installing and Setting up WebLogic
>     @rem Server
>     @rem (http://e-docs.bea.com/wls/docs60/install/index.html).

>     SETLOCAL

>     cd ..\..

>     @rem Set user-defined variables.
>     set JAVA_HOME=D:\WLS 6.0\jdk130

>     if exist %JAVA_HOME%\lib\nul goto runWebLogic
>     echo.
>     echo The JRE wasn't found in directory %JAVA_HOME%.
>     echo Please edit the startExamplesServer.cmd script so that the JAVA_HOME
>     echo variable points to the root directory of your Java installation.
>     goto finish

>     :runWebLogic
>     echo on
>     set PATH=.\bin;%PATH%

>     set CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar;.\samples
>     \eval\cloudscape\lib\cloudscape.jar;.\config\examples\server
>     classes

>     %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

>     @rem Set user-defined variables.
>     @rem original:set JAVA_HOME=C:\bea60sp2\jdk130

1. Set your JAVA_HOME to your new JDK in WebLogic 7.0.

   >     set JAVA_HOME=C:\bea700\jdk131

   >     @rem added:

2. Set WL60_HOME in order to be able to access your WebLogic Server 6.0 classes.

   >     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.
   >     echo The JRE wasn't found in directory %JAVA_HOME%.
   >     echo Please edit the startExamplesServer.cmd script so that the JAVA_HOME
   >     echo variable points to the root directory of your Java installation.
   >     goto finish

   >     :runWebLogic
   >     echo on
   >     @rem original: set PATH=.\bin;%PATH%

4. Set the PATH to look in your %WL_HOME% 7.0 home. If this is not set, the server won't boot.

   >     set PATH=%WL_HOME%\bin;%PATH%

   >     @rem original: set
   >     @rem CLASSPATH=.;.\lib\weblogic_sp.jar;
   >     @rem .\lib\weblogic.jar;.\samples\eval\cloudscape\
   >     @rem lib\cloudscape.
   >     @rem jar;.\config\examples\serverclasses

5. Set the CLASSPATH to point to old classes and to new classes that you need.

   >     set CLASSPATH=%WL_HOME%\lib\weblogic_sp.jar;%WL_HOME%\lib\weblogic.jar;
   >     %WL60_HOME%\samples\eval\cloudscape\lib\
   >     cloudscape.jar;%WL60_HOME%\config\examples\serverclasses

   >     echo CLASSPATH=%CLASSPATH%

   >     @rem original: %JAVA_HOME%\bin\java -hotspot -ms64m -mx64m
   >     @rem -classpath %CLASSPATH% -Dweblogic.Domain=examples
   >     @rem -Dweblogic.Name=examplesServer -Dbea.home=C:\bea60sp2
   >     @rem -Dcloudscape.system.home
   >     @rem =./samples/eval/cloudscape/data
   >     @rem -Djava.security.policy==C:\bea60sp2\wlserver6.0
   >     @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=%WL60_HOME%/
   >     samples/eval/cloudscape/data -Djava.security.policy==%WL60_HOME%/lib/weblogic.policy weblogic.Server

   >     goto finish

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

5. Choose Examples.

6. Choose Start Examples Server.

7. Watch for the Out-of-the-Box Examples Index Page.

Or ...

1. In Windows Explorer, go to the SAMPLES_HOME\server\config\examples directory.

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

It is not necessary to upgrade the WebLogic 6.1 Examples Server to WebLogic Server 7.0; this section just provides the steps to do so as an example of how to upgrade a server from 6.1 to 7.0. To upgrade the WebLogic 6.1 Examples Server domain configuration for use on WebLogic Server 7.0:

- Install WebLogic Server 7.0

- Set Up the WebLogic Server 7.0 Environment with Your 6.1 Service Pack 2 Domain Configuration

- Start the Examples Server on WebLogic Server 7.0

Install WebLogic Server 7.0

Install WebLogic Server 7.0. See the Installation Guide.

Note: Installing the new version in the exact location of the old version is explicitly prohibited by the installer.

Set Up the WebLogic Server 7.0 Environment with Your 6.1 Service Pack 2 Domain Configuration

It is important to keep the examples domain directory within the config directory when you copy your 6.1 WL_HOME/config/examples directory to a new location. For 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, .cmd and .sh, respectively.

The setExamplesEnv script at SAMPLES_HOME\server\config\examples sets certain environment variables in your development shell, the command window from which you build and run the examples.

setExamplesEnv sets these variables:

- CLASSPATH

  contains all of the classes needed to build and run the examples

- CLIENT_CLASSES

  points to the directory that stores client classes

- SERVER_CLASSES

  points to the directory that stores server-side classes

- EX_WEBAPP_CLASSES

  points to the directory that stores classes used by the Examples Web Application

- PATH

  contains your system path, appended with the JDK and WebLogic Server bin directories

The java and javac commands use the CLASSPATH variable to locate the Java classes that are required to compile source files and run examples. CLASSPATH must contain the appropriate classes for compiling and running the example.

To upgrade the Examples Server from WebLogic Server 6.1 to WebLogic Server 7.0, you must edit the WebLogic Server 7.0 setExamplesEnv.cmd script so that you can access your 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.

This section contains:

- An example of the setExamplesEnv.cmd script used to boot a WebLogic 6.1 Service Pack 2 Examples Server.

- An example of the above-listed setExamplesEnv.cmd script modified to boot WebLogic Server 7.0 which includes explanations for how to change this script to upgrade the Examples Server toWebLogic Server 7.0.

- An example of the startExamplesServer.cmd script used to boot a WebLogic 6.1 Service Pack 2 Examples Server.

- An example of the above-listed startExamplesServer.cmd script modified to boot WebLogic Server 7.0 which includes explanations for how to change this script to upgrade the Examples Server toWebLogic Server 7.0.

setExamplesEnv.cmd script used to boot a WebLogic 6.1 Service Pack 2 Examples Server

>     @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. It contains the following variables:
>     @rem
>     @rem WL_HOME   - This must point to the root directory of your WebLogic
>     @rem             installation.
>     @rem JAVA_HOME - Determines the version of Java used to compile
>     @rem             and run examples. This variable must point to the
>     @rem             root directory of a complete JDK installation. See
>     @rem             the WebLogic platform support page
>     @rem             (http://e-docs.bea.com/wls/platforms/index.html)
>     @rem             for an up-to-date list of supported JVMs on Windows NT.
>     @rem When setting these variables below, please use short file names(8.3).
>     @rem To display short (MS-DOS) filenames, use "dir /x". File
>     @rem names with spaces will break this script.
>     @rem
>     @rem jDriver for Oracle users: This script assumes that native libraries
>     @rem required for jDriver for Oracle have been installed in the @rem proper location and that your system PATH variable
>     @rem has been set appropriately.
>     @rem For additional information, refer to Installing and Setting up WebLogic
>     @rem Server (/install/index.html in your local documentation set or on the Internet at
>     @rem http://e-docs.bea.com/wls/docs61/install/index.html).

>     @rem Set user-defined variables.
>     set WL_HOME=D:\WLS 6.1\wlserver6.1
>     set JAVA_HOME=D:\WLS 6.1\jdk131

>     @dir %WL_HOME%\lib > nul
>     if errorlevel 0 goto checkJava
>     @echo.
>     @echo The WebLogic Server wasn't found in directory %WL_HOME%.
>     @echo Please edit the setExamplesEnv.cmd script so that the
>     @echo WL_HOME variable points to the WebLogic Server installation @echo directory.
>     @echo Your environment has not been set.
>     @goto finish

>     :checkJava
>     @dir %JAVA_HOME%\jre\bin\java.exe > nul
>     if errorlevel 0 goto setEnv
>     @echo.
>     @echo The JDK wasn't found in directory %JAVA_HOME%.
>     @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
>     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

>     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. It contains the following variables:
>     @rem
>     @rem WL_HOME   - This must point to the root directory of your WebLogic
>     @rem             installation.
>     @rem JAVA_HOME - Determines the version of Java used to compile
>     @rem             and run examples. This variable must point to the
>     @rem             root directory of a complete JDK installation. See
>     @rem             the WebLogic platform support page
>     @rem             (http://e-docs.bea.com/wls/platforms/index.html)
>     @rem             for an up-to-date list of supported JVMs on Windows NT.
>     @rem
>     @rem When setting these variables below, please use short file @rem names(8.3).
>     @rem To display short (MS-DOS) filenames, use "dir /x". File
>     @rem names with spaces will break this script.
>     @rem
>     @rem jDriver for Oracle users: This script assumes that native libraries
>     @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 (/install/index.html in your local documentation set or on the
>     @rem Internet at http://e-docs.bea.com/wls/docs61/install/index.html).

>     @rem Set user-defined variables.
>     @rem changed: set WL_HOME=C:\bea61sp2\wlserver6.1

1. Set the WL61_HOME variable so that you can access your WebLogic Server 6.1 classes.

   >     set WL61_HOME=C:\bea61sp2\wlserver6.1

2. Set the WL_HOME variable so that you can access your WebLogic Server 7.0 classes.

   >     set WL_HOME=C:\bea700\weblogic700

3. Point to the JDK on WebLogic Server 7.0.

   >     @rem changed: set JAVA_HOME=C:\bea61sp2\jdk130
   >     set JAVA_HOME=c:\bea700\jdk131

4. Point to application archives created when you build the examples.

   >     set APPLICATIONS=%WL61_HOME%\config\examples\applications

5. Point to the directory used to store client classes.

   >     set CLIENT_CLASSES=%WL61_HOME%\config\examples\clientclasses

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.

   >     set EX_WEBAPP_CLASSES=%WL61_HOME%\config\examples\applications\examplesWebApp\WEB-INF\classes

8. Point to the WebLogic Server 6.1 and WebLogic Server 7.0 classes.

   >     set 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 %WL_HOME% 7.0 home.

   >     set PATH=%WL_HOME%\bin;%JAVA_HOME%\bin;%PATH%

   >     @echo.
   >     @echo Your environment has been set.

startExamplesServer.cmd script used to boot a WebLogic 6.1 Service Pack 2 Examples Server

>     @echo off

>     @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. This script contains the following variable:
>     @rem
>     @rem JAVA_HOME      - Determines the version of Java used to start
>     @rem                  WebLogic Server. This variable must point to the
>     @rem                  root directory of a JDK installation and will be set
>     @rem                  for you by the WebLogic Server installer. Note that
>     @rem                  this script uses the hotspot VM to run WebLogic Server.
>     @rem                  If you choose to use a JDK other than the one
>     @rem                  included in the disribution, make sure that the JDK
>     @rem                  includes the hotspot VM. See the WebLogic platform
>     @rem                  support page (http://e-docs.bea.com/wls/platforms/index.html)
>     @rem                  for an up-to-date list of supported JVMs on Windows NT.
>     @rem

>     @rem When setting the variable below, please use short file names (8.3).
>     @rem To display short (MS-DOS) filenames, use "dir /x". File names with
>     @rem spaces will break this script.
>     @rem
>     @rem jDriver for Oracle users: This script assumes that native libraries
>     @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).

>     SETLOCAL

>     cd ..\..

>     @rem Set user-defined variables.
>     set JAVA_HOME=D:\WLS 6.1\jdk131

>     @rem Check that script is being run from the appropriate directory
>     if not exist lib\weblogic.jar goto wrongplace
>     goto checkJDK

>     :wrongplace

>     echo startExamplesServer.cmd must be run from the config\examples directory. 1>&2
>     goto finish

>     :checkJDK
>     if exist %JAVA_HOME%/bin/javac.exe goto runWebLogic
>     echo.
>     echo Javac wasn't found in directory %JAVA_HOME%/bin.
>     echo Please edit the startExamplesServer.cmd script so that the JAVA_HOME
>     echo variable points to the root directory of your JDK installation.
>     goto finish

>     :runWebLogic
>     echo on
>     set PATH=.\bin;%PATH%

>     set CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar;.\samples
>     eval\cloudscape\lib\cloudscape.jar;.\config\examples\serverclasses
>     echo off

>     echo.
>     echo ***************************************************
>     echo *  To start WebLogic Server, use the password     *
>     echo *  assigned to the system user.  The system       *
>     echo *  username and password must also be used to     *
>     echo *  access the WebLogic Server console from a web  *
>     echo *  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"
>     -Dcloudscape.system.home=./samples/eval/cloudscape/data
>     -Djava.security.policy=="D:\WLS
>     6.1\wlserver6.1/lib/weblogic.policy" weblogic.Server
>     goto finish

>     :finish
>     cd config\examples
>     ENDLOCAL

above-listed startExamplesServer.cmd script modified to boot WebLogic Server 7.0

>     @echo off

>     SETLOCAL

>     @rem Set user-defined variables.
>     @rem original:set JAVA_HOME=C:\bea61sp2\jdk130

1. Set your JAVA_HOME to your new JDK in WebLogic 7.0.

   >     set JAVA_HOME=C:\bea700\jdk131

   >     @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.
   >     echo The JRE wasn't found in directory %JAVA_HOME%.
   >     echo Please edit the startExamplesServer.cmd script so that the JAVA_HOME
   >     echo variable points to the root directory of your Java installation.
   >     goto finish

   >     :runWebLogic
   >     echo on
   >     @rem original: set PATH=.\bin;%PATH%

4. Set the PATH to look in your %WL_HOME% 7.0 home. If this is not set, the server won't boot.

   >     set PATH=%WL_HOME%\bin;%PATH%

   >     @rem original: set
   >     @rem CLASSPATH=.;.\lib\weblogic_sp.jar;
   >     @rem .\lib\weblogic.jar;.\samples\eval\cloudscape\
   >     @rem lib\cloudscape.
   >     @rem jar;.\config\examples\serverclasses

   >     set CLASSPATH=%WL_HOME%\lib\weblogic_sp.jar;%WL_HOME%\lib\weblogic.jar;
   >     %WL61_HOME%\samples\eval\cloudscape\lib\cloudscape.jar;
   >     %WL61_HOME%\config\examples\serverclasses

5. Set the CLASSPATH to point to old classes and to new classes that you need.

   >     echo CLASSPATH=%CLASSPATH%

   >     @rem original: %JAVA_HOME%\bin\java -hotspot -ms64m -mx64m
   >     @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

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.

5. Choose Examples.

6. Choose Start Examples Server.

7. Watch for the Out-of-the-Box Examples Index Page.

Or ...

1. In Windows Explorer, go to the SAMPLES_HOME\server\config\examples directory.

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