BEA WebLogic Server ™ BEA WebLogic Server 7.0 Upgrade Guide Release 7.
Copyright Copyright © 2002 BEA Systems, Inc. All Rights Reserved. Restricted Rights Legend This software and documentation is subject to and made available only pursuant to the terms of the BEA Systems License Agreement and may be used or copied only in accordance with the terms of that agreement. It is against the law to copy the software except as specifically allowed in the agreement.
Contents About This Document Audience.............................................................................................................. ix e-docs Web Site................................................................................................... ix How to Print the Document...................................................................................x Contact Us!............................................................................................................
Update Inbound RMI-IIOP Applications ................................................. 1-17 Authenticate Remote Users ...................................................................... 1-19 ACL Policy is LOCAL...................................................................... 1-19 ACL Policy is Global ........................................................................ 1-20 Set WebLogic Tuxedo Connector Properties ...........................................
2. Upgrading WebLogic Server 4.5 and 5.1 to Version 7.0 Upgrading Your WebLogic Server Configuration: Main Steps........................ 2-2 Upgrading WebLogic Server License Files ...................................................... 2-4 Converting a WebLogicLicense.class License........................................... 2-4 Converting a WebLogicLicense.XML License ......................................... 2-4 Converting the weblogic.properties File to XML Files.....................................
FileServlet................................................................................................. 2-28 Internationalization (I18N)....................................................................... 2-28 Java Transaction API (JTA) ..................................................................... 2-28 Java Database Connectivity (JDBC) ........................................................ 2-29 JSP ............................................................................................
.0 ................................................................................................B-9 config.xml file used for WebLogic Server 6.1 Service Pack 3.........B-12 above-listed config.xml file used for WebLogic Server 7.0 .............B-15 Start the Pet Store Application on WebLogic Server 7.0.........................B-19 Upgrading the WebLogic 6.0 Service Pack 2 Examples Server to WebLogic Server 7.0 ..............................................................................................
viii BEA WebLogic Server 7.
About This Document This document provides procedures and other information you need to upgrade earlier versions of BEA WebLogic Server to WebLogic 7.0. It also provides information about moving applications from an earlier version of WegLogic Server to 7.0. The document is organized as follows: Chapter 1, “Upgrading WebLogic Server 6.x to Version 7.0,” describes how to upgrade to WebLogic Server 7.0 from WebLogic Server 6.x. Chapter 2, “Upgrading WebLogic Server 4.5 and 5.1 to Version 7.
How to Print the Document You can print a copy of this document from a Web browser, one main topic at a time, by using the File→Print option on your Web browser. A PDF version of this document is available on the WebLogic Server documentation Home page on the e-docs Web site (and also on the documentation CD). You can open the PDF in Adobe Acrobat Reader and print the entire document (or a portion of it) in book format.
A description of the problem and the content of pertinent error messages Documentation Conventions The following documentation conventions are used throughout this document. Convention Usage Ctrl+Tab Keys you press simultaneously. italics Emphasis and book titles. monospace text Code samples, commands and their options, Java classes, data types, directories, and file names and their extensions. Monospace text also indicates text that you enter from the keyboard. Examples: import java.util.
Convention Usage [ ] Optional items in a syntax line. Example: java utils.MulticastTest -n name -a address [-p portnumber] [-t timeout] [-s send] | Separates mutually exclusive choices in a syntax line. Example: java weblogic.deploy [list|deploy|undeploy|update] password {application} {source} ... . . . xii Indicates one of the following in a command line: An argument can be repeated several times in the command line. The statement omits additional optional arguments.
C HAPTER 1 Upgrading WebLogic Server 6.x to Version 7.0 Upgrading WebLogic Server 6.x to version 7.0, under the simplest circumstances, involves changing your WebLogic Server start command scripts and environment settings. In some cases, it is necessary to move your domain directory. Sometimes, upgrading requires changes specific to the subsytem being upgraded. The following sections contain information necessary to upgrade your system from WebLogic Server 6.x to WebLogic Server 7.
1 Upgrading WebLogic Server 6.x to Version 7.0 For information on upgrading to WebLogic Platform 7.0 (7.0.0.1), see the Upgrading section of the WebLogic Server FAQs. Note: Throughout this document “upgrade” refers to upgrading to a later version of WebLogic Server and “port” refers to moving your applications from an earlier version of WebLogic Server to a later version. Upgrading Your WebLogic Server Configuration: Main Steps Take the following steps to upgrade from WebLogic Server 6.
Modifying Startup Scripts To upgrade a cluster of servers, follow the above steps for each server and then follow the steps outlined in Setting Up WebLogic Clusters in Using WebLogic Server Clusters. In cases where you invoke an application by using RMI/T3 or RMI/IIOP, WebLogic Server 6.1 and 7.0 are interoperable. Within a domain, however, all servers must be of the same version.
1 Upgrading WebLogic Server 6.x to Version 7.0 5. Modify or eliminate any WebLogic Server 6.x startup script directory structure tests. For example, if your script tries to verify a relative path, either fix the directory structure test or remove it. WebLogic Server 7.0 installs the JVM, JDK 1.3.1_02, with the server installation. The setenv.sh scripts provided with the server all point to the JVM. The latest information regarding certified JVMs is available at the Certifications Page.
Porting an Application from WebLogic Server 6.x to WebLogic Server 7.0 1. If you have not already installed WebLogic Server 7.0, do so now. See the Installation Guide for more information. Note: Installing the new version in the exact location of the old version is explicitly prohibited by the installer. 2. Each 6.x and 7.0 domain must have its own separate directory. It is not possible to have multiple config.xml files in the same directory. a. For each 6.
1 Upgrading WebLogic Server 6.x to Version 7.0 4. When you deploy applications to WebLogic Server 7.0, use the Administration Console or weblogic.Deployer utility to deploy using the new two-phase deployment protocol. The older, WebLogic Server 6.x deployment protocol, utilities, and API are deprecated in WebLogic Server 7.0 Note: WebLogic Server 7.0 will not deploy an application that has errors in its deployment descriptor.
Upgrading Security Note: The WebLogic Server 7.0 examples and PetStore are configured to use the default security configuration. It is not possible to run the WebLogic Server 7.0 examples and PetStore in Compatibility security. Booting WebLogic Server in Compatibility Security In previous releases of WebLogic Server, the File realm was configured by default. Therefore, WebLogic Server could use the File Realm to boot even if there was no security realm defined in the config.xml file.
1 Upgrading WebLogic Server 6.x to Version 7.0 Upgrading from Compatibility Security to WebLogic Server 7.0 Security If you want to leverage the new security features in WebLogic Server 7.0, you need to upgrade your existing security realm to a WebLogic Server 7.0 security realm. You upgrade by populating the security providers in WebLogic Server 7.0 with your existing user and group information and defining security policies on resources that reflect the ACLs.
Upgrading Security f. Click the Membership tab to add the user who can boot WebLogic Server to the Administrators group. g. Click the Apply button to save your changes. 5. Add the users and groups that you had configured in the 6.x security realm to an Authentication provider. 6. Optionally, define roles for your 6.x users and groups. See Securing WebLogic Resources. 7. Express 6.x ACLs as security policies. See Securing WebLogic Resources. 8. Set myrealm as the default security realm.
1 Upgrading WebLogic Server 6.x to Version 7.0 For information about using Compatibility security, see “Booting WebLogic Server in Compatibility Security” on page 1-7. 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.
Upgrading Security 9. Reboot WebLogic Server. 10. Expand the Domains-->Security nodes. 11. Select the General tab. 12. Set the security realm in which you configured the Realm Adapter Authentication provider as the default security realm. 13. Click Apply. Note: ACLs cannot be upgraded to WebLogic Server 7.0. Guest User The guest user is no longer supplied by default in WebLogic Server 7.0.
1 Upgrading WebLogic Server 6.x to Version 7.0 Creating a Boot Identity File in the Administration Guide. There is no direct upgrade of the old password.ini file because it contained a clear text password and no username. Upgrading the SSL Protocol This section contains information on how to upgrade the SSL protocol including instructions for creating a trusted CA Keystore, creating a private key Keystore, and using a CertAuthenticator in Compatibility security.
Upgrading Security keytool -import -trustcacerts -alias -file -keystore -storepass The trusted certificate authority shipped with WebLogic Server is located in WL_HOME/server/lib/cacerts.
1 Upgrading WebLogic Server 6.x to Version 7.0 Using a CertAuthenticator that needs to be changed may result in access being denied in WebLogic Server 7.0, but allowed in WebLogic Server 6.x. To change the CertAuthenticator, have it return NULL for unrecognized certs, or for all certs, if certs 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 config.
Upgrading WebLogic Tuxedo Connector Upgrading WebLogic Tuxedo Connector You must make the following application and configuration changes to use WebLogic Tuxedo Connector in WebLogic Server 7.
1 Upgrading WebLogic Server 6.x to Version 7.0 Convert WebLogic Tuxedo Connector XML Configuration Files WebLogic Tuxedo Connector is implemented as a service and no longer utilizes a separate XML configuration file. The WTCMigrateCF tool migrates XML configuration file information into the config.xml file of an active Administration server. Use the following steps to convert your WebLogic Tuxedo Connector XML configuration file: 1.
Upgrading WebLogic Tuxedo Connector Argument Description CONFIGWTC Fully qualified path and name of the WebLogic Tuxedo Connector XML configuration file to migrate to the config.xml file. Example: d:\bea\weblogic700\server\samples\examples\wtc \atmi\simpapp\bdmconfig.xml SERVERNAME Optional. The name of the administration or managed server that you want the new WTCServer MBean assigned to. Default: the current active administration server. DOMAIN Optional.
1 Upgrading WebLogic Server 6.x to Version 7.0 1. Modify the corbaloc:tgiop or corbaname:tgiop object reference in your ior.txt file. Example: corbaloc:tgiop:servername/NameService where servername is your server name 2. Register the WebLogic Server (WLS) Naming Service by entering the following command: cnsbind -o ior.txt your_bind_name where your_bind_name is the object name from your Tuxedo application. 3. Modify the *DM_REMOTE_SERVICES section of your Tuxedo domain configuration file.
Upgrading WebLogic Tuxedo Connector 4. Load your modified domain configuration file using dmloadcf. You are now ready to start your applications. Authenticate Remote Users For more information, see User Authentication at http://e-docs.bea.com/wls/docs70/wtc_admin/BDCONFIG.html#WTCuserAuth. WebLogic Tuxedo Connector uses Access Control Lists (ACLs) limit the access to local services within a local domain by restricting the remote domains that can execute these services.
1 Upgrading WebLogic Server 6.x to Version 7.0 ACL Policy is Global If the WebLogic Tuxedo Connector ACL Policy is GLOBAL, the user's security token is passed. No administration changes are required. Set WebLogic Tuxedo Connector Properties Note: For more information on how to set WebLogic Tuxedo Connector properties, see How to Set WebLogic Tuxedo Connector Properties at http://e-docs.bea.com/wls/docs70/wtc_admin/Install.html#WTCprops. TraceLevel and PasswordKey are now WebLogic Server properties.
Additional Upgrade Procedures and Information 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.
1 Upgrading WebLogic Server 6.x to Version 7.0 “Web Applications” on page 1-32 “WebLogic Server Clusters on Solaris” on page 1-33 “Web Services” on page 1-33 “Writable config.xml File” on page 1-33 “Deprecated APIs and Features” on page 1-34 “Removed APIs and Features” on page 1-36 ant.jar If you are going to develop new ant tasks, you must manually add the server/lib/ant.jar file to your classpath. Apache Xalan XML Transformer The built-in transformer in WebLogic Server 7.
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. WebLogic Server 7.
1 Upgrading WebLogic Server 6.x to Version 7.0 Deployment WebLogic Server 7.0 provides a new two-phase deployment model. For more information on this deployment model and other 7.0 deployment features, see WebLogic Server Deployment. By default, statically configured applications use the 6.x deployment model. Deployments initiated through the console or the new weblogic.Deployer command line utility use the new two-phase deployment model. WebLogic Server 7.
Additional Upgrade Procedures and Information EJB 2.0 The EJB 2.0 specification has changed substantially between WebLogic Server 6.0 and 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 at http://java.sun.com/products/ejb/2.0.html.
1 Upgrading WebLogic Server 6.x to Version 7.0 There were no local interfaces in 6.0, but they exist in 6.1 and 7.0. Remote relationships do not exist in 6.1 and 7.0. The new implementation of read-only beans in WebLogic 7.0 does not require NOT_SUPPORTED for a transaction attribute. It also doesn't do exclusive locking, but gives each transaction its own instance of the read-only bean to use. In pre-2.
Additional Upgrade Procedures and Information 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 ejb-ql elements in your ejb-jar.xml file or your weblogic-ql elements in your weblogic-cmp-jar.xml file. For example: WebLogic Server 6.
1 Upgrading WebLogic Server 6.x to Version 7.0 JMS WebLogic Server 7.0 supports the JavaSoft JMS specification version 1.0.2. All WebLogic JMS 6.x applications are supported in WebLogic JMS 7.0. However, if you want your applications to take advantage of the new highly available JMS features, you will need to configure your existing physical destinations (queues and topics) to be part of a single distributed destination set.
Additional Upgrade Procedures and Information JSP Due to a change in the JSP specification, null request attributes now return the string “null” instead of an empty string. WebLogic Server versions since 6.1 contain a new flag in weblogic.xml called printNulls which is true by default, meaning that "null" will be the default. Setting this to false ensures that expressions with "null" results are printed as an empty string, not the string “null.” An example of configuring the printNulls element in weblogic.
1 Upgrading WebLogic Server 6.x to Version 7.0 MBean API Change Previous versions of this document and various other sample documents erroneously described using weblogic.management.Admin.getInstance().getAdminMBeanHome() as a way to look up the MBeanHome interface on the Administration Server. However, the weblogic.management.Admin class is not public. Instead of using this non-public class, use JNDI to retrieve MBeanHome.
Additional Upgrade Procedures and Information about upgrading, see “Upgrading Security” in the Upgrade Guide for BEA WebLogic Server 7.0. Servlets Update your web.xml file so that it uses the following new classes: weblogic.servlet.proxy.HttpClusterServlet instead of weblogic.servlet.internal.HttpClusterServlet and weblogic.servlet.proxy.HttpProxyServlet instead of weblogic.t3.srvr.
1 Upgrading WebLogic Server 6.x to Version 7.0 ... /Server> Starting in WebLogic Server 7.0: /Server> To change the thread count value via the Console: 1. In the console, select Servers > myServer > Monitoring > . 2. Click on Monitor all Active Queues. 3. Click on "default" queue (a list of threads and what they are doing appears). 4. Click on Configure Execute Queues (at the top of the page). 5. Click on "default" queue. 6.
Additional Upgrade Procedures and Information WebLogic Server Clusters on Solaris Certain applications (heavy EJB apps) deployed in a WebLogic Server cluster on Solaris will perform better using the client JVM rather than the server JVM. This is especially true under heavy loads. Web Services Due to changes in the Web service runtime system and architecture between versions 6.1 and 7.0 of WebLogic Server, you must upgrade Web services created in version 6.1 to run on version 7.0.
1 Upgrading WebLogic Server 6.x to Version 7.0 Deprecated APIs and Features WebLogic Time Services is deprecated and should be replaced by JMX Timer Service. For documentation of JMX Timer Service, see Interface TimerMBean and Class Timer. WebLogic Workspaces Zero Administration Client (ZAC) is deprecated in this release of WebLogic Server 7.0. It is replaced by JavaWebStart. WebLogic Enterprise Connectivity (WLEC) is deprecated in this release of WebLogic Server 7.0.
Additional Upgrade Procedures and Information Instead, use the new two-phase deployment protocol APIs and tools described in the 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.
1 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.
C HAPTER 2 Upgrading WebLogic Server 4.5 and 5.1 to Version 7.0 Upgrading WebLogic Server 4.5 and 5.1 to version 7.0 is a multi-step process that involves defining Web applications and converting your weblogic.properties file(s) into a new XML file format. There are also several specification changes that affect the upgrade process. This chapter addresses the majority of upgrade issues, but may omit issues that are unique to a specific environment.
2 Upgrading WebLogic Server 4.5 and 5.1 to Version 7.
Upgrading Your WebLogic Server Configuration: Main Steps 3. Upgrade your server license files. For instructions on how to convert your licenses to the new format, see “Upgrading WebLogic Server License Files” on page 2-4. 4. Convert your weblogic.properties file. For instructions on how to convert your weblogic.properties file, see “Converting the weblogic.properties File to XML Files” on page 2-5 and the Console Help documentation. 5.
2 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. Upgrading WebLogic Server License Files The Java format license file (WebLogicLicense.class) and the XML-format license file (WebLogicLicense.XML) are no longer supported.
Converting the weblogic.properties File to XML Files 2. Click the link to update a WebLogic Server license. You may need to scroll down to see the link. 3. Browse and select the pathname for the directory containing the license file to be converted, or enter the pathname in the box provided. Then click Submit License. 4. You will receive the converted license_wlsxx.bea file through e-mail. To update the license.bea file on your system, see Updating Your license.
2 Upgrading WebLogic Server 4.5 and 5.1 to Version 7.0 The weblogic.xml file contains WebLogic-specific attributes for a Web application. You define the following attributes in this file: HTTP session parameters, HTTP cookie parameters, JSP parameters, resource references, security role assignments, character set mappings, and container attributes. The deployment descriptor web.xml file is defined by the servlet 2.3 specification from Sun Microsystems. The web.
Converting the weblogic.properties File to XML Files Note: The conversion utility described above specifies the Java home location in the weblogic.xml file. It reads this location using the System.getProperty(java.home), which means that it will specify the Java home location on which WebLogic Server was started for the conversion. It is strongly recommended that you not edit the config.xml file directly.
2 Upgrading WebLogic Server 4.5 and 5.1 to Version 7.0 Classloading in WebLogic Server 7.0 Earlier versions of WebLogic Server used the WebLogic classpath property (weblogic.class.path) to facilitate dynamic classloading. In WebLogic 6.0 and later, the weblogic.class.path is no longer needed. You can now load classes from the Java system classpath. To include the classes that were formerly specified in weblogic.class.
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.
2 Upgrading WebLogic Server 4.5 and 5.1 to Version 7.0 “XML Deployment Descriptors” on page 2-11 “WAR Files” on page 2-12 “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.
Converting and Porting Your Existing Applications into Web Applications When you convert your weblogic.properties file, the appropriate web.xml and weblogic.xml files are created for you under the directory domain\applications\DefaultWebApp_myserver\WEB-INF. Follow the preceding directory structure and place the XML files in the domain\applications\webAppName\WEB-INF directory that you create. For information on deploying web applications, see Developing WebLogic Server Applications.
2 Upgrading WebLogic Server 4.5 and 5.1 to Version 7.0 WAR Files A WAR file is a Web Application archive. If you have correctly followed the prescribed directory structure of a Web Application and created the appropriate web.xml and weblogic.xml files, it is strongly recommended that in production environments your applications be bundled together in a Web Application deployed as a WAR file.
Converting and Porting Your Existing Applications into Web Applications 8. Enter a name for the application or component in the provided field and click Create. 9. Enter the following information: Staging Mode—specify the staging mode. The options include server, nostage, and stage. Deployed—using the provided checkbox, indicate whether the .ear, .war, .jar, or .rar file should be deployed upon creation. 10. To configure components for the application, click the Configure Components in this Application. 11.
2 Upgrading WebLogic Server 4.5 and 5.1 to Version 7.0 See weblogic.xml Deployment Descriptor Elements in Assembling and Configuring Web Applications. JavaServer Pages (JSPs) and Servlets This section contains information specific to JSPs and servlets that may be pertinent to your applications. Some changes will be necessary in code (both Java and HTML) where the code refers to URLs that may be different when servlets and JSPs are deployed in a Web Application other than the default Web Application.
Converting and Porting Your Existing Applications into Web Applications Porting a Simple Servlet from WebLogic Server 5.1 to WebLogic Server 7.0 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.
2 Upgrading WebLogic Server 4.5 and 5.1 to Version 7.0 3. Move the web.xml file from domain\applications\DefaultWebApp_myserver\WEB-INF to C:\hello\WEB-INF\. 4. Set up your development environment (see Establishing a Development Environment in Developing WebLogic Server Applications for more information) and compile the HelloWorldServlet with a command like the following: C:\hello\WEB-INF\classes>javac -d . HelloWorldServlet.java This should compile the file and create the correct package structure. 5.
Porting and Converting Enterprise JavaBeans Applications EJB Porting Considerations Consider the following when porting Enterprise JavaBeans to WebLogic Server 7.0. WebLogic Server Version 7.0 supports the Enterprise JavaBeans 1.1 and 2.0 specifications. The XML parser is stricter with XML deployment descriptors in WebLogic 7.0 than it was in WebLogic 5.1. Some errors allowed in earlier versions are no longer permitted. This is described in Introducing WebLogic Server Enterprise Java Beans.
2 Upgrading WebLogic Server 4.5 and 5.1 to Version 7.0 for the WebLogic Server EJB container. This file must conform to the WebLogic Server 5.1 DTD or the WebLogic Server 7.0 DTD. 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. In WebLogic Server 7.
Porting and Converting Enterprise JavaBeans Applications For instance, WebLogic Server 7.0 ensures that a method exists if a transaction attribute is set for that method name. This helps identify a common set of errors where transaction attributes were mistakenly set on non-existent methods. Look at the WebLogic Server 7.0 examples The WebLogic Server distribution contains several EJB examples including their deployment descriptors.
2 Upgrading WebLogic Server 4.5 and 5.1 to Version 7.0 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. You can do this automatically using the DDCreator tool. 2.
Porting and Converting Enterprise JavaBeans Applications return null; // required by the EJB specification } In EJB 1.1 or 2.0, entity beans cannot use bean-managed transactions. Instead, they must run with a container-managed transaction attribute (for example, Required, Mandatory, etc.). Steps for Porting a 1.1 EJB from WebLogic Server 5.1 to WebLogic Server 7.0 The WebLogic Server 5.1 deployment descriptor only allows the exclusive or read-only concurrency options.
2 Upgrading WebLogic Server 4.5 and 5.1 to Version 7.0 java -classpath %CLIENTCLASSES%;%CLASSPATH% examples.ejb.basic.statelessSession.Client This command ensures that the EJB interfaces are referenced in your client’s classpath. Steps for Converting an EJB 1.1 to an EJB 2.0 To convert an EJB 1.1 bean to an EJB 2.0 bean, you can use the WebLogic Server DDConverter utility. BEA Systems recommends that you develop EJB 2.0 beans in conjunction with WebLogic Server 7.0. For 1.
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 weblogic-ejb-jar.xml deployment descriptor, and a CMP deployment descriptor if CMP entity beans are used.
2 Upgrading WebLogic Server 4.5 and 5.1 to Version 7.0 Developing WebLogic Server Applications. Note that if you are using JSPs and want them to compile at run time you must have the home and remote interfaces of the bean included in the classes directory of your WAR file. 3. Create the Enterprise Archive by executing a jar command like the following in the staging directory: jar cvf myApp.ear * 4.
Upgrading JMS Upgrading JMS WebLogic Server 7.0 supports the JavaSoft JMS specification version 1.0.2. Weblogic Server 4.5.1 — Porting is supported only for SP15. Customers running all service packs should contact BEA Support. Weblogic Server 5.1 — Customers running SP07 or SP08 should contact BEA Support before porting existing JDBC stores to version 7.0. z In order to port object messages, the object classes need to be in the Weblogic Server 7.0 server CLASSPATH.
2 Upgrading WebLogic Server 4.5 and 5.1 to Version 7.0 For supported platforms, as well as DBMS and client libraries, see the BEA Certifications Page. The most current certification information will always be posted on the Certifications page. Additional Porting and Deployment Considerations The following sections provide additional information that may be useful when you deploy applications on WebLogic Server 7.0.
Additional Porting and Deployment Considerations “Wireless Application Protocol Applications” on page 2-35 “Writable config.xml File” on page 2-35 “XML 7.0 Parser and Transformer” on page 2-36 “Deprecated APIs and Features” on page 2-36 “Removed APIs and Features” on page 2-37 Applications and Managed Servers By default, applications are deployed to the Administration Server. However, in most cases, this is not good practice.
2 Upgrading WebLogic Server 4.5 and 5.1 to Version 7.0 FileServlet In WebLogic Server 6.1 Service Pack 2 and later, the behavior of FileServlet, which is the default servlet for a Web Application, has changed. FileServlet now includes the SERVLET_PATH when determining the source filename. This means that it is possible to explicitly only serve files from specific directories by mapping the FileServlet to /dir/* etc. See Setting Up a Default Servlet.
Additional Porting and Deployment Considerations Based on the inclusion of support for JTA, the JTS JDBC driver (with properties in weblogic.jts.* and URL jdbc:weblogic:jts:..) has been replaced by a JTA JDBC/XA driver. Existing properties are available for backward compatibility, but you should change the class name and properties to reflect the JTS to JTA name change.
2 Upgrading WebLogic Server 4.5 and 5.1 to Version 7.0 Null Attributes Due to a change in the JSP specification, null request attributes now return the string "null" instead of an empty string. WebLogic Server versions since 6.1 contain a new flag in weblogic.xml called printNulls which is true by default, meaning that returning "null" is the default. Setting printNulls to false ensures that expressions with "null" results are printed as an empty string, not the string "null.
Additional Porting and Deployment Considerations Use JNDI instead of *.rmi.Naming. Use weblogic.rmic to generate dynamic proxies and bytecode; with the exception of RMI IIOP, stubs and skeletons classes are no longer generated. Note: For more information, see WebLogic RMI Fea tures and Guidelines in Programming WebLogic RMI. Use weblogic.rmi.server.UnicastRemoteObject.exportObject() to get a stub instance. The RMI examples have not currently been updated to use java.rmi.* and JNDI.
2 Upgrading WebLogic Server 4.5 and 5.1 to Version 7.0 Digital Certificates Generated by the Certificate Servlet Digital certificates obtained through a CSR created by the Certificate Request Generator servlet in WebLogic Server 5.1 cannot be used with this release of WebLogic Server. When creating a CSR using the Certificate Request Generator servlet in WebLogic Server 5.1, the servlet does not make you specify a password for the private key.
Additional Porting and Deployment Considerations ----------END CERTIFICATE---------- Remove any extra lines. If the existing private key is not password protected, you do not need to specify the weblogic.management.pkpassword argument when starting the server. When configuring the SSL protocol in the WebLogic Server Administration Console, note that the Key Encrypted attribute is not used to dictate whether or not the private key is password encrypted.
2 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. In a new installation of WebLogic Server, the server will configure a default Web Application. Customers upgrading to WebLogic Server 7.
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 web.xml file of the web application. In WebLogic Server 5.1, the default mime-type can be set using weblogic.httpd.defaultMimeType in weblogic.properties where its default value is "text/plain". WebLogic Server 6.0, WebLogic Server 6.1, and WebLogic Server 7.
2 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 parsers and transformers that were shipped in previous versions of WebLogic Server, and if you used classes, interfaces, or methods that have been deprecated, you might receive deprecation messages in your applications . WebLogic Server 7.
Additional Porting and Deployment Considerations Zero Administration Client (ZAC) is deprecated and should be replaced by JavaWebStart. -Dweblogic.management.host weblogic.deploy is deprecated in this release of WebLogic Server 7.0 and is replaced by weblogic.Deployer. For more information, see Deployment Tools and Procedures in Developing WebLogic Server Applications. weblogic.management.tools.WebAppComponentRefreshTool and weblogic.
2 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.
A PPENDIX A The weblogic.properties Mapping Table The weblogic.properties mapping table shows which config.xml, web.xml, or weblogic.xml attribute handles the function formerly performed by weblogic.properties properties. weblogic.properties file Property .xml Configuration Attribute weblogic.administrator.email config.xml: EmailAddress Console Label (Administrator element) weblogic.administrator.location config.xml: Notes (freeform, optional) (Administrator element) weblogic.administrator.
A The weblogic.properties Mapping Table weblogic.properties file Property .xml Configuration Attribute Console Label weblogic.cluster.defaultLoadAlgo rithm config.xml: DefaultLoadAlgorithm Clusters: clustername: Configuration: General: Default Load Algorithm (Cluster element) weblogic.cluster.multicastAddres s config.xml: MulticastAddress (Cluster element) weblogic.cluster.multicastTTL config.xml: MulticastTTL (Cluster element) weblogic.cluster.name config.
weblogic.properties file Property .xml Configuration Attribute weblogic.httpd.defaultServlet web.xml: Console Label define a servlet-mapping with the URL pattern of / element weblogic.httpd.defaultWebApp config.xml: DefaultWebApp (WebServer element) weblogic.httpd.enable config.xml: HttpdEnabled (Server element) weblogic.httpd.enableLogFile config.xml: LoggingEnabled (WebServer element) weblogic.httpd.http.keepAliveSec s config.xml: KeepAliveSecs (WebServer element) weblogic.
A The weblogic.properties Mapping Table weblogic.properties file Property .xml Configuration Attribute weblogic.httpd.logFileFlushSecs config.xml: LogFileFlushSecs Console Label (WebServer element) weblogic.httpd.logFileFormat config.xml: LogFileFormat Services: Virtual Host: Log File Format (WebServer element) weblogic.httpd.logFileName config.xml: LogFileName Services: Virtual Host: Log File Name (WebServer element) weblogic.httpd.logRotationPeriod Mins config.
weblogic.properties file Property .xml Configuration Attribute Console Label weblogic.httpd.servlet.extension CaseSensitive config.xml: ServletExtensionCaseSe nsitive Deployments: Web Applications: applicationname: Configuration: Files: Case Sensitive Extensions (WebAppComponent element) weblogic.httpd.servlet.reloadChe ckSecs config.xml: ServletReloadCheckSecs (WebAppComponent element) weblogic.httpd.servlet.SingleThr eadedModelPoolSize config.
A The weblogic.properties Mapping Table weblogic.properties file Property .xml Configuration Attribute weblogic.httpd.session.cookie.na me weblogic.xml: CookieName / element pair weblogic.httpd.session.cookie.pa th weblogic.xml: CookiePath / element pair weblogic.httpd.session.cookies.e nable weblogic.xml: CookiesEnabled / element pair weblogic.httpd.session.debug weblogic.
weblogic.properties file Property .xml Configuration Attribute weblogic.httpd.session.persisten tStoreDir weblogic.xml: PersistentStoreDir Console Label / element pair weblogic.httpd.session.persisten tStorePool weblogic.xml: PersistentStorePool / element pair weblogic.httpd.session.persisten tStoreShared weblogic.xml: SessionPersistentStore Shared / element pair weblogic.httpd.session.persisten tStoreType weblogic.
A The weblogic.properties Mapping Table weblogic.properties file Property .xml Configuration Attribute Console Label weblogic.httpd.tunneling.clientP ingSecs config.xml: TunnelingClientPingSec s Servers: servername: Configuration: Tuning: Tunneling Client Ping (Server element) weblogic.httpd.tunneling.clientT imeoutSecs config.xml: TunnelingClientTimeout Secs (Server element) weblogic.httpd.tunnelingenabled config.xml TunnelingEnabled (Server element) weblogic.httpd.
weblogic.properties file Property .xml Configuration Attribute Console Label weblogic.jdbc.
A The weblogic.properties Mapping Table weblogic.properties file Property .xml Configuration Attribute weblogic.jdbc.enableLogFile config.xml: JDBCLoggingEnabled (Server element) weblogic.jdbc.logFileName config.xml: JDBCLogFileName (Server element) weblogic.jms.ConnectionConsumer config.xml JMSConnectionConsumer element MessagesMaximum Selector Destination weblogic.jms.connectionFactoryAr gs.<> config.
weblogic.properties file Property .xml Configuration Attribute weblogic.jms.queueSessionPool config.xml: ConnectionConsumer ConnectionFactory ListenerClass AcknowledgeMode SessionsMaximum Transacted Console Label (JMSSessionPool element) weblogic.jms.tableNamePrefix config.xml: PrefixName weblogic.jms.topic config.xml JNDIName StoreEnabled Services: JMS: Connection Factories: JNDI Name (JMSDestination element) weblogic.jms.topicSessionPool config.
A The weblogic.properties Mapping Table weblogic.properties file Property .xml Configuration Attribute Console Label weblogic.security.certificate.au thority config.xml ServerCertificateChain FileName Servers: servername: Configuration: SSL: Server Certificate Chain File Name (SSL element) weblogic.security.certificate.se rver config.xml: ServerCertificateFileN ame (SSL element) weblogic.security.certificateCac heSize config.xml: CertificateCacheSize (SSL element) weblogic.security.
weblogic.properties file Property .xml Configuration Attribute weblogic.security.ldaprealm.cred ential config.xml: Credential Console Label (LDAPRealm element) weblogic.security.ldaprealm.fact ory config.xml LdapProvider (LDAPRealm element) weblogic.security.ldaprealm.grou pDN config.xml: GroupDN (LDAPRealm element) weblogic.security.ldaprealm.grou pIsContext config.xml: GroupIsContext (LDAPRealm element) weblogic.security.ldaprealm.grou pNameAttribute config.
A The weblogic.properties Mapping Table weblogic.properties file Property .xml Configuration Attribute weblogic.security.ldaprealm.user DN config.xml: UserDN (LDAPRealm element) weblogic.security.ldaprealm.user NameAttribute config.xml: UserNameAttribute (LDAPRealm element) weblogic.security.ldaprealm.user PasswordAttribute config.xml: UserPasswordAttribute (LDAPRealm element) weblogic.security.net.connection Filter config.xml: ConnectionFilter (Security element) weblogic.security.ntrealm.
weblogic.properties file Property .xml Configuration Attribute weblogic.security.realm.cache.au th.size config.xml: AuthenticationCacheSiz e Console Label (CachingRealm element) weblogic.security.realm.cache.au th.ttl.negative config.xml: AuthenticationCacheTTL Negative (CachingRealm element) weblogic.security.realm.cache.au th.ttl.positive config.xml: AuthenticationCacheTTL Positive (CachingRealm element) weblogic.security.realm.cache.ca seSensitive config.
A The weblogic.properties Mapping Table weblogic.properties file Property .xml Configuration Attribute weblogic.security.realm.cache.pe rm.size config.xml: PermissionCacheSize Console Label (CachingRealm element) weblogic.security.realm.cache.pe rm.ttl.negative config.xml: PermissionCacheTTLNega tive (CachingRealm element) weblogic.security.realm.cache.pe rm.ttl.positive config.xml: PermissionCacheTTLPosi tive (CachingRealm element) weblogic.security.realm.cache.us er.enable config.
weblogic.properties file Property .xml Configuration Attribute Console Label weblogic.security.ssl.enable config.xml: Enabled Servers: servername: Configuration: SSL: Enabled (SSL element) weblogic.security.SSL.hostnameVe rifier config.xml HostnameVerifier (SSL element) weblogic.security.SSL.ignoreHost nameVerification Servers: servername: Configuration: SSL: Hostname Verifier config.xml HostNameVerificationIg nored (SSL element) weblogic.security.SSLHandler.ena ble config.
A The weblogic.properties Mapping Table weblogic.properties file Property .xml Configuration Attribute Console Label weblogic.system.enableConsole config.xml: StdoutEnabled Servers: servername: Logging: General: Log to Stdout (Kernel element) weblogic.system.enableIIOP config.xml: IIOPEnabled (Server element) weblogic.system.enableReverseDNS Lookups config.xml: ReverseDNSAllowed (Server element) weblogic.system.enableSetGID, config.xml: PostBindGID weblogic.system.enableSetUID, config.
weblogic.properties file Property .xml Configuration Attribute weblogic.system.MagicThreadBackT oSocket config.xml: MagicThreadDumpBackToS ocket Console Label (ServerDebug element) weblogic.system.MagicThreadDumpF ile config.xml: MagicThreadDumpFile (ServerDebug element) weblogic.system.MagicThreadDumpH ost config.xml: MagicThreadDumpHost (ServerDebug element) weblogic.system.magicThreadDumps config.xml: MagicThreadDumpEnabled (ServerDebug element) weblogic.system.maxLogFileSize config.
A The weblogic.properties Mapping Table weblogic.properties file Property .xml Configuration Attribute Console Label weblogic.system.readTimeoutMilli s config.xml: LoginTimeoutMillis Servers: servername: (Server element) weblogic.system.SSL.useJava config.xml: UseJava (SSL element) weblogic.system.SSLListenPort config.xml: ListenPort (SSL element) weblogic.system.
A PPENDIX B 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.
B Upgrading the Pet Store Application and the Examples Server 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.
Upgrading the Pet Store Application From WebLogic 6.1 Service Pack 3 to WebLogic 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.
B Upgrading the Pet Store Application and the Examples Server 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.
Upgrading the Pet Store Application From WebLogic 6.1 Service Pack 3 to WebLogic 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.
B Upgrading the Pet Store Application and the Examples Server } 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.
Upgrading the Pet Store Application From WebLogic 6.1 Service Pack 3 to WebLogic 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.
B Upgrading the Pet Store Application and the Examples Server 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.
Upgrading the Pet Store Application From WebLogic 6.1 Service Pack 3 to WebLogic 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.pol icy" weblogic.
B Upgrading the Pet Store Application and the Examples Server 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.
Upgrading the Pet Store Application From WebLogic 6.1 Service Pack 3 to WebLogic @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;.
B Upgrading the Pet Store Application and the Examples Server :finish cd config\petStore ENDLOCAL config.xml file used for WebLogic Server 6.1 Service Pack 3 PAGE 119Upgrading the Pet Store Application From WebLogic 6.1 Service Pack 3 to WebLogic Targets="petstoreServer" URI="inventoryEjb.jar"/> PAGE 120B Upgrading the Pet Store Application and the Examples Server PAGE 121Upgrading the Pet Store Application From WebLogic 6.1 Service Pack 3 to WebLogic PAGE 122B Upgrading the Pet Store Application and the Examples Server Path="D:\WLS 6.1\wlserver6.1/config/petstore/applications/tour.war"> PAGE 123Upgrading the Pet Store Application From WebLogic 6.1 Service Pack 3 to WebLogic
2. Change the path to point to your petstoreAdmin.ear file. PAGE 124B Upgrading the Pet Store Application and the Examples Server 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"/>
PAGE 125Upgrading 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. 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.
B Upgrading the Pet Store Application and the Examples Server 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.
Upgrading the WebLogic 6.0 Service Pack 2 Examples Server to WebLogic Server 7.0 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.
B Upgrading the Pet Store Application and the Examples Server @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.
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.
B Upgrading the Pet Store Application and the Examples Server @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.
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. 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.
B Upgrading the Pet Store Application and the Examples Server @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=.
Upgrading the WebLogic 6.0 Service Pack 2 Examples Server to WebLogic Server 7.0 @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.
B Upgrading the Pet Store Application and the Examples Server @rem @rem @rem @rem @rem @rem @rem original: %JAVA_HOME%\bin\java -hotspot -ms64m -mx64m -classpath %CLASSPATH% -Dweblogic.Domain=examples -Dweblogic.Name=examplesServer -Dbea.home=C:\bea60sp2 -Dcloudscape.system.home =./samples/eval/cloudscape/data -Djava.security.policy==C:\bea60sp2\wlserver6.0 /lib/weblogic.policy weblogic.Server %JAVA_HOME%\bin\java -hotspot -ms64m -mx64m -classpath %CLASSPATH% -Dweblogic.Name=examplesServer -Dweblogic.
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 It is not necessary to upgrade the WebLogic 6.1 Examples Server to WebLogic Server 7.
B Upgrading the Pet Store Application and the Examples Server 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.
Upgrading the WebLogic 6.1 Service Pack 2 Examples Server to WebLogic Server 7.0 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.
B Upgrading the Pet Store Application and the Examples Server @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.
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.
B Upgrading the Pet Store Application and the Examples Server 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.
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. This script contains the following variable: @rem @rem JAVA_HOME - Determines the version of Java used to start @rem WebLogic Server.
B Upgrading the Pet Store Application and the Examples Server @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.
Upgrading the WebLogic 6.1 Service Pack 2 Examples Server to WebLogic Server 7.0 -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.
B Upgrading the Pet Store Application and the Examples Server :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 @rem @rem @rem @rem original: set CLASSPATH=.;.\lib\weblogic_sp.jar; .\lib\weblogic.jar;.\samples\eval\cloudscape\ lib\cloudscape. jar;.\config\examples\serverclasses set CLASSPATH=%WL_HOME%\lib\weblogic_sp.jar;%WL_HOME%\lib\weblogic.
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. 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.
B B-40 Upgrading the Pet Store Application and the Examples Server BEA WebLogic Server 7.