user manual

Additional Porting and Deployment Considerations
BEA WebLogic Server 7.0 Upgrade Guide 2-33
----------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. 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.
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
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.
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
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.