Conversion

 

If you have used an earlier version of Weblogic Server, you should convert your weblogic.properties files into a Domain. The resources defined in a single XML configuration file comprise a single domain.

This section describes the followingways to convert your .properties files:

• Conversion Using the Administration Console

Conversion Using the Administration Console

The first step in the conversion process is locating the root directory for your original WebLogic installation. All of the weblogic.properties files you convert must reside under this root, and these files must be located on the same machine that this server is running on.

Use the links to navigate the server's file system to find the weblogic root. When you have found it, click the icon next to it and move on to the next step.

The conversion utility provides a list of entities that have been identified as potential servers and clusters.

To use the Conversion Utility from the WebLogic Server Administration Console:

• Click Convert Weblogic Properties on the right pane.

• Select the Root directory (which is the location of the global weblogic.properties files)by navigating the tree using the icon on the left side of the pane.

• Select the Cluster and Server specific weblogic.properties directories.

• Click Convert

Continue to convert your weblogic.properties files until you have created the domains needed for your application.

SSL Security Files

SSL Security Files are set in the old properties file as

weblogic.security.certificate.server=democert.pem weblogic.security.key.server=demokey.pem weblogic.security.certificate.authority=ca1024.pem weblogic.security.clientRootCA=ca.pem

and will be copied into the config/<NewDomain>/<ServerName>(Server Specific Directory) where the config.xml file will reflect them as

<Server Name=....

<SSL ServerCertificateFileName="./config/<NewDomain>/democert.pem" ServerKeyFileName="./config/<NewDomain>/demokey.pem" TrustedCAFileName="./config/<NewDomain>/ca.pem" ServerCertificateChainFileName="./config/<NewDomain>/ca1024.pem" ....

>

</Server>

If the SSL security files specified in the weblogic.properties are not in the old server specific directory then they will not be set in the config.xml and will have to be copied into the config/<NewDomain>/<ServerName>(Server Specific Directory), and be set in the config.xml.

Servlets

All servlets registered in the weblogic.properties are converted into a single web application

The conversion tool creates the necessary files like web.xml and weblogic.xml in one of the following directorie

1. config/<NewDomain>/applications/DefaultWebApp_<ServerName>/WEB- INF directory and will be made as the default webapp, unless there is already a default web app declared in the properties file.

2. config/<NewDomain>/<Server_Name>/WEB-INF, if there is already a default web app declared.

All the Servlet Classes registered individually as weblogic.httpd.register in the old weblogic.properties except for the weblogic internal servlets have to be copied under the new weblogic(6.0) server tree structure as specified in the web.xml

For example if web.xml has

<servlet> <servlet-class>weblogic.hello.HelloworldServlet</servlet-class> </servlet>

The servlet class Hellowordlservlet.class should be copied into the corresponding WEB-INF/classes/weblogic/hello directory. The current directory signifies the directory from which the weblogic server(6.0) will be started with the new configuration.

EJB jar files and Web App war files

If the weblogic.properties has weblogic.ejb.deploy and weblogic.httpd.webApp.<webAppName> pointing to a relative directory then those jar and war files have to be copied under the new weblogic(6.0) server tree structure.

Example

weblogic.ejb.deploy=weblogic/ejb/HelloEJB.jar

Then the jar file has to be copied under ./weblogic/ejb/ directory.

The "." indicates the directory from which the server will be started with the new configuration.