Session Porting; Standalone Html And Jsps - BEA WebLogic Server 7 Upgrade Manual

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

Session Porting

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
Beginning in WebLogic 6.0, cookies are named
See
Web Applications for more information.

Standalone HTML and JSPs

In the original domain provided with WebLogic Server 7.0, as well as in any domains
that have been created using the
domain\applications\DefaultWebApp_myserver
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
directory to handle relative links, such as image files.
Additional Porting and Deployment Considerations
java utils.ImportPrivateKey
weblogic.xml Deployment Descriptor Elements
argument when starting the server.
.
JSESSIONID
in Assembling and Configuring
weblogic.properties
DefaultWebApp_myserver
BEA WebLogic Server 7.0 Upgrade Guide
WebLogicSession
by default.
file converter,
directory is created. This
.
2-33