|
 |
| e-docs > WebLogic Server > WebLogic Server 7.0 Upgrade Guide > Upgrading WebLogic Server 4.5 and 5.1 to Version 7.0 |
|
WebLogic Server 7.0 Upgrade Guide
|
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.
The following sections provide procedures and other information you need to upgrade your system from WebLogic Server 4.5 or 5.1 to WebLogic Server 7.0; to port your applications from WebLogic Server 4.5 or 5.1 to WebLogic Server 7.0; and deploy these applications. Instructions apply to upgrades from both WebLogic Server 4.5 and 5.1 to WebLogic Server 7.0.
Note: Throughout this document the word, upgrade, is used to refer to upgrading to a later version of WebLogic Server and the word, port, is used to refer 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 4.5 or 5.1 to WebLogic Server 7.0:
Prior to WebLogic Server 6.0, a separate download was required if you wanted to get 128-bit encryption instead of 56-bit encryption. WebLogic Server 7.0 has a single download for both 56-bit encryption and 128-bit encryption. For details of how to enable 128-bit encryption see Enabling 128-Bit Encryption in the Installation Guide.
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 Clusters. All servers in the cluster should be running 7.0 since there is no interoperability between 4.5 and 7.0 or between 5.1 and 7.0.
To upgrade from WebLogic Server 7.0 to WebLogic Server 7.0.0.1, see Updating WebLogic Server 7.0 GA (7.0.0.0) to 7.0.0.1 in the Installation Guide.
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. These files were used with earlier releases of WebLogic Server and must be converted to a new format. The new license file is called license.bea.
Converting a WebLogicLicense.class License
If a WebLogicLicense.class license file is used in your existing WebLogic Server installation, perform the following tasks before you install WebLogic Server 7.x:
Converting a WebLogicLicense.XML License
To convert a WebLogicLicense.XML file to a license.bea file (compatible with WebLogic Server 6.x and 7.x), complete the following steps. Be sure the WebLogicLicense.XML license file is available on the machine on which you perform this procedure.
Converting the weblogic.properties File to XML Files
Note: Throughout this document, the WebLogic Server 7.0 directory domain that you create is referred to as domain.
Prior to WebLogic Server 6.0, WebLogic Server releases used a weblogic.properties file to configure applications. In WebLogic Server 7.0, configuration of applications is handled through XML descriptor files and the Administration Console. Converting a weblogic.properties file to the config.xml file creates a new domain for your applications and adds XML files that define how your applications are set up. BEA Systems recommends that you change the name of the default domain name that is created during the conversion so that the name is relevant to your work.
The config.xml file is an XML document that describes the configuration of an entire Weblogic Server domain. The config.xml file consists of a series of XML elements. The domain element is the top-level element, and all elements in the domain are children of the domain element. The domain element includes child elements, such as the server, cluster, and application elements. These child elements may have children themselves. Each element has one or more configurable attributes.
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.xml file defines each servlet and JSP page and enumerates enterprise beans referenced in the Web application. This deployment descriptor can be used to deploy a Web Application on any J2EE-compliant application server.
Convert your existing weblogic.properties file to the appropriate XML file by following these steps:
When you convert your properties file, the web.xml and weblogic.xml files for the default web application are created for you and placed inside a domain\applications\DefaultWebApp_myserver\WEB-INF directory. The process of converting your weblogic.properties file also creates the config.xml file located in domain. This file contains configuration information specific to your domain.
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.
For more procedures for converting your weblogic.properties file, see the Console Help documentation.
For a list of which config.xml, web.xml, or weblogic.xml attribute handles the function formerly performed by weblogic.properties properties, see The weblogic.properties Mapping Table.
The startup scripts, which are generated when a weblogic.properties file is converted, are named:
where domainName is the name of your domain directory.
These scripts exist under the domain directory in your WebLogic Server 7.0 distribution and start the administration server in the new domain.
See Starting and Stopping WebLogic Servers in the Administration Guide for more information on scripts and starting servers.
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.path in the standard Java system classpath, set the CLASSPATH environment variable, or use the -classpath option on the command line as in the following example:
java -classpath %CLASSPATH%;%MyOldClassspath% weblogic.Server
where %MyOldClasspath% contains only the directories that point to your old applications.
If you used WebLogic Server startup scripts with a previous version of the product, modify them to work with 7.0.
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. For more information on J2EE deployment units, see Deploying Web Applications as Part of an Enterprise Application in Assembling and Configuring Web Applications. Web Applications are usually a collection of servlets, JSPs, and HTML files, packaged as WAR files. Enterprise JavaBeans (packaged as JAR files) are server-side Java components written according to the EJB specification. Enterprise Archives (EAR files) contain all of the JAR and WAR component archive files for an application and an XML descriptor that describes the bundled components. Client Applications are Java classes that connect to WebLogic Server through Remote Method Invocation (RMI). Later sections discuss the aforementioned J2EE deployment units in greater detail.
Converting and Porting Your Existing Applications into Web Applications
In order to convert an application to a Web Application and then port it into a Web Application deployed on WebLogic Server 7.0, the application's files must be placed within a directory structure that follows a specific pattern. For development, these files can be left in an exploded directory format. However, for production situations, it is highly recommended that you bundle your applications into a WAR file as a single Web Application. For more information on Web Applications see Understanding WebLogic Server J2EE Applications and Assembling and Configuring Web Applications.
The following sections provide information you need to know about porting and deploying Web Applications, including a procedure for porting a simple servlet from WebLogic Server 5.1 to WebLogic Server 7.0:
Web Applications Directory Structure
Web Applications are organized in a specified directory structure so that they can be archived and deployed on WebLogic Server. All servlets, classes, static files, and other resources belonging to a Web Application are organized under a directory hierarchy. The root of this hierarchy defines the document root of your Web Application. All files under this root directory can be served to the client, except for files under the special directories WEB-INF and META-INF located in the root directory. The root directory should be named with the name of your Web Application.
The following diagram illustrates the directory structure of any Web Application.
WebApplicationRoot\(Publically available files such as
| .jsp, .html, .jpg, .gif)
|
+WEB-INF\-+
|
+ classes\(directory containing
| Java classes including
| servlets used by the
| Web Application)
|
+ lib\(directory containing
| JAR files used by the
| Web Application)
|
+ web.xml
|
+ weblogic.xml
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.
The Web Application Deployment Descriptor (web.xml) file is a standard J2EE descriptor used to register your servlets, define servlet initialization parameters, register JSP tag libraries, define security constraints, and define other Web Application parameters. For detailed instructions on creating the deployment descriptor, see Writing the web.xml Deployment Descriptor in Assembling and Configuring Web Applications.
There is also a WebLogic-specific Deployment Descriptor (weblogic.xml). In this file you define JSP properties, JNDI mappings, security role mappings, and HTTP session parameters. The WebLogic-specific deployment descriptor also defines how named resources in the web.xml file are mapped to resources residing elsewhere in WebLogic Server. For detailed instructions on creating the WebLogic-specific deployment descriptor, see Writing the WebLogic-Specific Deployment Descriptor. This file may not be required if you do not need the preceding properties, mappings, or parameters.
Use the web.xml and weblogic.xml files, in conjunction with the Administration console, to configure your applications. The XML files can be viewed through any text editor. To edit them, simply make your changes and save the file as web.xml or weblogic.xml with the appropriate path as specified by the prescribed directory structure under Web Applications Directory Structure. See Assembling and Configuring Web Applications for more information. If you do not want to deploy your applications together as a single Web Application, you need to split up the XML files that have been created for you, creating the appropriate XML files specific to each Web Application. Each Web Application needs a weblogic.xml file and a web.xml file as well as whichever files you choose to put in it.
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. Once you have bundled your applications into a WAR file, it is important to remove the previously existing directory structure so that WebLogic Server only has one instance of each application.
Use the following command line from the root directory containing your Web Application to create a WAR file, replacing `webAppName' with the specific name you have chosen for your Web Application:
jar cvf webAppName.war *
You now have created a WAR file that contains all the files and configuration information for your Web Application.
To configure and deploy a web application using the WebLogic Server Administration Console:
Configuration—Edit the staging mode and enter the deployment order.
Targets—Indicate the Targets-Server for this configured application by moving the application from the Available list to the Chosen list.
Deploy—Deploy the application to all of the selected targets or undeploy it from all targets.
Monitoring—View monitoring information related to the application.
For more information on setting attributes in the console, see the Web Applications section of the Console Help.
WebLogic Server 7.0 does not recognize cookies from previous versions because cookie format changed with WebLogic Server 6.0. WebLogic Server will ignore cookies with the old format and create new sessions. Be aware that new sessions are created automatically.
The default name for cookies has changed from 5.1, when it was WebLogicSession. In WebLogic Server 7.0, cookies are named JSESSIONID by default.
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.
weblogic.servlet.proxy.HttpClusterServlet
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.
<!DOCTYPE web-app (View Source for full doctype...)>
- <web-app>
- <servlet>
<servlet-name>HelloWorldServlet</servlet-name>
<servlet-class>examples.servlets.HelloWorldServlet</servlet-class>
</servlet>
- <servlet-mapping>
<servlet-name>HelloWorldServlet</servlet-name>
<url-pattern>/hello/*</url-pattern>
</servlet-mapping>
</web-app>
For more information on web.xml files, see Writing Web Application Deployment Descriptors in Assembling and Configuring Web Applications. A weblogic.xml file is not necessary with such a simple, stand-alone servlet as HelloWorld.
For more information on weblogic.xml files, see Writing the WebLogic-Specific Deployment Descriptor in Assembling and Configuring Web Applications.
C:\hello\WEB-INF\classes>javac -d . HelloWorldServlet.java
jar cvf hello.war *
In this case /hello/ is the context path of the servlet. This is determined by the naming of the WAR file, in this case hello.war. The second /hello was mapped in the servlet mapping tags inside the web.xml file.
Porting and Converting Enterprise JavaBeans Applications
The following sections describe Enterprise Java Beans porting and conversion procedures.
Consider the following when porting Enterprise JavaBeans to WebLogic Server 7.0.
EJBs should always get their database connections from a TxDataSource. This allows the EJB container's transaction management to interface with the JDBC connection, and it also supports XA transactions.
The WebLogic Server 7.0 CMP Deployment Descriptor supports TxDataSources and should be used instead of the WebLogic Server 5.1 CMP Deployment Descriptor which only specifies a connection pool.
The WebLogic Server EJB compiler (weblogic.ejbc) generates Java code that is then compiled by the Java compiler. By default, WebLogic Server uses the javac compiler included with the bundled JDK. The EJB compiler runs much faster when a faster Java compiler is used. Use the -compiler option to specify an alternate compiler as in the following example:
java weblogic.ejbc -compiler sj pre_AccountEJB.jar AccountEJB.jar
The WebLogic Server 7.0 EJB compiler (ejbc) includes additional verification that was missing from earlier WebLogic Server releases. It is possible that an EJB deployed in a previous WebLogic Server version without error, but WebLogic Server 7.0 finds and complains about the error. These errors must be corrected before the EJB is deployed in WebLogic Server 7.0.
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.
The WebLogic Server distribution contains several EJB examples including their deployment descriptors. The EJB examples can be found in the samples\server\src\examples\ejb11 and samples\server\src\examples\ejb20 directories of the WebLogic Server 7.0 distribution.
The following table shows the descriptor combinations supported by WebLogic Server 7.0.
For more information on Enterprise JavaBeans, see Enterprise JavaBean Components and Programming WebLogic Enterprise Java Beans.
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:
To ensure EJB 1.1 or 2.0 compliance, make the following changes to the EJB 1.0 beans:
private transient SessionContext ctx;
public void ejbCreate (String name) {
firstName = name;
}
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. The database concurrency option is available when upgrading to the WebLogic Server 7.0 weblogic-ejb-jar.xml file. For more information about this option, see information on database concurrency in weblogic-ejb-jar.xml Document Type Definitions in Programming WebLogic Enterprise JavaBeans.
The WebLogic Server 7.0 CMP deployment descriptor allows multiple EJBs to be specified and it supports using a TxDataSource instead of a connection pool. Using a TxDataSource is required when XA is being used with EJB 1.1 CMP.
To port a 1.1 EJB from WebLogic Server 5.1 to WebLogic Server 7.0:
javac -d %CLIENTCLASSES% Trader.java TraderHome.java TradeResult.java Client.java
java -classpath %CLIENTCLASSES%;%CLASSPATH% examples.ejb.basic.statelessSession.Client
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.1 beans already used in production, it is not necessary to convert them to 2.0 beans. EJB 1.1 beans are deployable with WebLogic Server 7.0. If you do wish to convert 1.1 beans to 2.0 beans, see the DDConverter documentation in Programming WebLogic Enterprise JavaBeans for information on how to do this conversion.
The basic steps required to convert a simple CMP 1.1 bean to a 2.0 bean are as follows:
public Enumeration findAllBeans()
Throws FinderException, RemoteException;
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. The WebLogic Server EJB examples located in samples\examples\ejb11 and samples\examples\ejb20 of the WebLogic Server distribution include sample weblogic deployment descriptors.
Creating an Enterprise Application
An Enterprise Application is a JAR file with an EAR extension. An EAR file contains all of the JAR and WAR component archive files for an application and an XML descriptor that describes the bundled components. The META-INF\application.xml deployment descriptor contains an entry for each Web and EJB module, and additional entries to describe security roles and application resources such as databases.
EnterpriseApplicationStagingDirectory\
|
+ .jar files
|
+ .war files
|
+META-INF\-+
|
+ application.xml
The application.xml file contains a descriptor for each component in the application, using a DTD supplied by Sun Microsystems. For more information on the application.xml file, see Application Deployment Descriptor Elements in 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.
jar cvf myApp.ear *
Understanding J2EE Client Applications
WebLogic Server supports J2EE client applications, packaged in a JAR file with a standard XML deployment descriptor. Client applications in this context are clients that are not Web browsers. They are Java classes that connect to WebLogic Server using Remote Method Invocation (RMI). A Java client can access Enterprise JavaBeans, JDBC connections, messaging, and other services using RMI. Client applications range from simple command line utilities that use standard I/O to highly interactive GUI applications built using the Java Swing/AWT classes.
To execute a WebLogic Server Java client, the client computer needs the weblogic_sp.jar file, the weblogic.jar file, the remote interfaces for any RMI classes and Enterprise Beans that are on WebLogic Server, as well as the client application classes. To simplify maintenance and deployment, it is a good idea to package a client-side application in a JAR file that can be added to the client's classpath along with the weblogic.jar and weblogic_sp.jar files. The weblogic.ClientDeployer command line utility is executed on the client computer to run a client application packaged to this specification. For more information about J2EE client applications, see Packaging Client Applications in Developing WebLogic Server Applications.
WebLogic Server 7.0 supports the JavaSoft JMS specification version 1.0.2.
For more information on porting your WebLogic JMS applications, see Porting WebLogic JMS Applications in Programming WebLogic JMS. Note that WebLogic Events are deprecated and are replaced by JMS messages with NO_ACKNOWLEDGE or MULTICAST_NO_ACKNOWLEDGE delivery modes. Each of these delivery modes is described in WebLogic JMS Fundamentals in Programming WebLogic JMS.
BEA Systems, mirroring Oracle's support policy, supports the Oracle releases listed in the Platform Support for WebLogic jDriver JDBC Drivers on the WebLogic Server Certifications page. BEA no longer supports the following Oracle client versions: 7.3.4, 8.0.4, 8.0.5, and 8.1.5.
To use the Oracle Client Version 7.3.4, use the backward compatible oci816_7 shared library. As stated above, BEA no longer supports this configuration.
To upgrade to Oracle Client Version 9i, or read detailed documentation on the WebLogic jDriver and Oracle databases, see Configuring WebLogic jDriver for Oracle in Installing and Using WebLogic jDriver for Oracle.
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. Deprecated features, upgrades, and the important changes that have been made in WebLogic Server 7.0 are noted.
Note: WebLogic Server 7.0 uses PointBase 4.2 as a sample database and does not bundle the Cloudscape database.
Applications and Managed Servers
By default, applications are deployed to the Administration Server. However, in most cases, this is not good practice. You should use the Administration Server only for administrative purposes. Use the Administration Console to define new managed servers and associate the applications with those servers. For more information, see Using WebLogic Server Clusters and Overview of WebLogic System Administration in the Administration Guide.
By default, WebLogic Server version 7.0 uses the two-phase deployment model. For more information on this deployment model and other 7.0 deployment features, see WebLogic Server Deployment in Developing WebLogic Server Applications. Therefore, if you deploy a 4.5 or 5.1 application in your 7.0 server, the deployment model is unspecified and, thus, uses a two-phase deployment. For more information, see the Release Notes.
The communication between the plug-in and WebLogic Server 4.5 and 5.1 is clear text. The plug-ins in WebLogic Server 7.0 support SSL communication between the plug-in and the back-end WebLogic Server.
To upgrade the plug-in, copy the new plug-in over the old one and restart the IIS, Apache, or iPlanet web server.
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.
Several internationalization and localization changes have been made in this version:
For details on internationalization in this version, see the Internationalization Guide.
Java Database Connectivity (JDBC)
The following changes have been made to JDBC:
The behavior of the JSP include directive has changed between WebLogic Server 5.1 and the current version. In versions through WebLogic Server 5.1, the JSP include directive logged a Warning-level message if it included a non-existent page. In WebLogic Server 6.0 and later, it reports 500 Internal Server Error in that case.You can avert the error by placing an empty file at the referenced location.
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."
An example of configuring the printNulls element in weblogic.xml:
<param-name>printNulls</param-name>
<param-value>false</param-value>
WebLogic Server 7.0 installs the Java Virtual Machine (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.
The following tips are for users porting to WebLogic Server 7.0 who used RMI in their previous version of WebLogic Server:
Note: For more information, see WebLogic RMI Fea tures and Guidelines in Programming WebLogic RMI.
Upgrading to the New Security Architecture
WebLogic Server 7.0 has a new security architecture. Upgrading WebLogic Server 4.5 or 5.1 to the security functionality in WebLogic Server 7.0 is a two-step process.
For instructions on how to upgrade security configurations from WebLogic Server 4.5 or 5.1 to WebLogic Server 6.x see the Security section under Additional Migration and Deployment Considerations in Migrating WebLogic Server 4.5 and 5.1 Applications to 6.x.
See Upgrading Security in Upgrading WebLogic Server 6.x to Version 7.0 for details.
For specific information about the new security architecture in WebLogic Server 7.0, see the Security section of the WebLogic Server 7.0 documentation.
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. The password is required in order to use the private key and associated digital certificate with this release of WebLogic Server.
Use the JDK keytool utility to define a password for the digital certificate's private key. The digital certificate can then be used with this release of WebLogic Server. Before using keytool to define the password for the private key, you may need to delete extra characters at the end of each line in the private key.
Private Keys and Digital Certificates
In this release of WebLogic Server, more stringent checks are performed on private keys and digital certificates. In order to use an existing private key and digital certificate, you must perform the following upgrade steps:
----------BEGIN ENCRYPTED PRIVATE KEY----------
...
-----------END RSA PRIVATE KEY---------------------
If the private key is not in PEM format, you receive the following exception:
java.lang.Exception:Cannot read private key from file
C:\bea700sp5\user_proects\mydomain\privatkey.der
Make sure password specified in environnment property weblogic.management.pkpassword is valid.
If the private key is unencrypted, use the java utils der.2pem command and modify the header as follows:
----------BEGIN RSA PRIVATE KEY----------
...
----------END RSA PRIVATE KEY----------
----------END CERTIFICATE----------
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. The attribute is irrelevant if a password is not used for the private key passphrase.
If you want to import the converted private key and digital certificate into a keytore, use java utils.ImportPrivateKey.
WebLogic Server 6.0 and later does not recognize cookies from previous versions because cookie format changed with 6.0. WebLogic Server ignores cookies with the old format, and creates new sessions.
The default name for cookies has changed from 5.1, when it was WebLogicSession. Beginning in WebLogic 6.0, cookies are named JSESSIONID by default.
See weblogic.xml Deployment Descriptor Elements in Assembling and Configuring Web Applications for more information.
In the original domain provided with WebLogic Server 7.0, as well as in any domains that have been created using the weblogic.properties file converter, domain\applications\DefaultWebApp_myserver directory is created. This directory contains files made available by your Web server. You can place HTML and JSP files here and make them available, separate from any applications you install. If necessary, you can create subdirectories within the DefaultWebApp_myserver directory to handle relative links, such as image files.
The following tips are for users porting to WebLogic Server 7.0 who used Web components in their previous version of WebLogic Server:
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.0 do not have a default mime-type. You must explicitly specify mime-type for each extension in the web.xml file.. For information on required MIME types see Programming WebLogic Server for Wireless Services. For information on creating and editing a web.xml file, see Writing Web Application Deployment Descriptors in Assembling and Configuring Web Applications.
An example configuration of the mime-types in the web.xml file:
<mime-type>image/tiff</extension>
<mime-type>image/tiff</extension>
WebLogic Server 7.0 automatically updates configuration information read from the 6.x config.xml file to include version 7.0 information. In order for these changes to be retained between invocations of the server, the config.xml file must be writable. To allow the file to be writable, make a back-up copy of your config.xml file from your 6.x configuration and change the file attributes.
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.0 also includes the WebLogic FastParser, a high-performance XML parser specifically designed for processing small to medium size documents, such as SOAP and WSDL files associated with WebLogic Web services. Configure WebLogic Server to use FastParser if your application handles mostly small to medium size (up to 10,000 elements) XML documents.
The WebLogic Server 7.0 distribution no longer includes the unmodified Xerces parser and Xalan transformer in the WL_HOME\server\ext\xmlx.zip file.
The following APIs and features are deprecated in anticipation of future removal from the product:
WebLogic Events are deprecated and should be replaced by JMS messages with NO_ACKNOWLEDGE or MULTICAST_NO_ACKNOWLEDGE delivery modes. See Non-transacted session in Programming WebLogic JMS for more information.
The following APIs and features have been removed:
|
|
|
|
||
 |
|
|
 |
 |
 |
|
||
