PStoreTool copy -alias authTokenIdentity -keyPassword SSL_CERTIFICATE_PASSWORD -config REGISTRY_HOME\conf\pstore.xml -config2 TARGET_REGISTRY_HOME\conf\pstore.xml

PStoreTool export -alias authTokenIdentity -certFile authTokenIdentity.crt -config REGISTRY_HOME\conf\pstore.xml

PStoreTool add -certFile authTokenIdentity.crt -config TARGET_REGISTRY_HOME\conf\pstore.xml

Install WebLogic, then configure it by adding machines to the cluster. In our case, cluster is named cluster, and the configuration manager, named myserver, is running on 10.0.0.79. The nodes in the WebLogic cluster are named:

Generate the certificates of all cluster nodes: Let's create proper certificates for our two nodes. It will be done via the CertGen tool provided by WebLogic. Go to the directory %WEB_LOGIC_HOME%\weblogic81\server\lib. CertGen is located in weblogic.jar's utils package. Invoke it with the command:

java -cp weblogic.jar utils.CertGen changeit kilacert kilakey export kila.mycompany.com

The output resembles the following:

kilacert kilakey export kila.mycompany.com 
        ...... Will generate certificate signed by CA from CertGenCA.der file
        ...... With Export Key Strength 
        ...... Common Name will have Host name kila.mycompany.com
        ...... Issuer CA name is
        CN=CertGenCAB,OU=FOR TESTING ONLY,O=MyOrganization,L=MyTown,ST=MyState,C=US 

Use the password changeit for starting particular UDDI node servers. The output file with the certificate is kilacert, and kilakey is the output file containing the private key. Generate certificates for all remaining nodes from their CertGen tools. (In our case, the other node is fido.mycompany.com.)

Once you have certificates from all nodes (in our case files kilacert.der and fidocert.der), import them to pstore.xml using the PstoreTool. Also include CertGenCA.der (from the directory %WEB_LOGIC_HOME%\weblogic81\server\lib). The pstore.xml file is now ready. For more info about WebLogic certificates and SSL settings, please see Configuring SSL in BEA's WebLogic product documentation.

	Note
	If you want to use both a standalone server and a ported application server, make a backup copy of pstore.xml. When you have performed the following steps, replace pstore.xml with the backup copy.

Edit configurator.xml as described above (where the application server context is wasp).

	Note
	If you want to use both a standalone server and a ported application server, make a backup copy of configurator.xml. When you have perfumed the following steps, replace configurator.xml with the backup copy.

<?xml version="1.0" encoding="UTF-8"?>
<config name="configurator" savingPeriod="5000" local="true">

    <configManagerUrls>
        <url>https://kila.mycompany.com:7102</url>
        <managerServiceUrlPath>/wasp/uddi/configuratorManager</managerServiceUrlPath>
        <managerConfiguratorUrlPath>/wasp/uddi/configurator</managerConfiguratorUrlPath>
    </configManagerUrls>

    <IPFilter name="configuratorFilter">
        <subnet IPAddress="10.0.0.79" subnetMask="255.255.255.255"/>
        <subnet IPAddress="10.0.0.134" subnetMask="255.255.255.255"/>
    </IPFilter>

    <configManager cluster="true">
        <configuratorListeners>        
            <configuratorListener>
              https://fido.mycompany.com:7102/wasp/uddi/configuratorListener
            </configuratorListener>
        </configuratorListeners>
    </configManager>

    <UDDIInterceptorChain name="configuratorApiChain">
    </UDDIInterceptorChain>

    <UDDIInterceptorMapping>
        <mapping UDDIInterceptorChainName="configuratorApiChain" 
	      UDDIServiceInterface="org.systinet.uddi.configurator.ConfiguratorApi"/>
    </UDDIInterceptorMapping>

</config>

Prepare the ported distribution (REGISTRY_HOME/conf/porting/weblogic/wasp.war) as described in Porting to Application Server.

In our case, the http port is 7101, the https port is 7102, and the application server context is wasp.

Check that the paths for log4j.appender.eventLog.File, log4j.appender.errorLog.File, and wasp.war\conf\log4j.config are valid on all cluster nodes.

Deploy wasp.war into all WebLogic cluster nodes

Create a balancer directory, in, for example, REGISTRY_HOME. This directory is referenced in this section as PACKAGE_HOME.

Create a subdirectory of PACKAGE_HOME named WEB-INF.

In this subdirectory, create the file web.xml containing the following text. Under WebLogicCluster specify the names and ports of your cluster nodes separated by a pipe (|). In our case, the file looked like:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" 
                                        "http://java.sun.com/dtd/web-app_2_3.dtd">
<web-app>
  <servlet>
     <servlet-name>HttpClusterServlet</servlet-name>
     <servlet-class>weblogic.servlet.proxy.HttpClusterServlet</servlet-class>
     <init-param>
        <param-name>WebLogicCluster</param-name>
        <param-value>kila:7101|fido:7101</param-value>
     </init-param>
  </servlet>

  <servlet>
      <servlet-name>FileServlet</servlet-name>
      <servlet-class>weblogic.servlet.FileServlet</servlet-class>
  </servlet>

  <servlet-mapping>
     <servlet-name>FileServlet</servlet-name>
     <url-pattern>/uddi/webdata/*</url-pattern>
  </servlet-mapping>

  <servlet-mapping>
    <servlet-name>FileServlet</servlet-name>
    <url-pattern>/uddi/bsc/webdata/*</url-pattern>
  </servlet-mapping>
  
  <servlet-mapping>
     <servlet-name>FileServlet</servlet-name>
     <url-pattern>/uddi/doc/*</url-pattern>
  </servlet-mapping>
  
  <servlet-mapping>
     <servlet-name>HttpClusterServlet</servlet-name>
     <url-pattern>/</url-pattern>
  </servlet-mapping> 
</web-app>

In the WEB-INF subdirectory, create the file weblogic.xml containing the following text, where /wasp is the context of BEA AquaLogic Service Registry ported to this application server. Your text must be customized for your own installation.

<!DOCTYPE weblogic-web-app PUBLIC "-//BEA Systems, Inc.//DTD Web Application 8.1//EN" 
"http://www.bea.com/servers/wls810/dtd/weblogic810-web-jar.dtd">
<weblogic-web-app>
  <context-root>/wasp</context-root>
</weblogic-web-app>

Create the directory %PACKAGE_HOME%\uddi\webdata and %PACKAGE_HOME%\uddi\bsc\webdata.

Unjar REGISTRY_HOME\app\uddi\bsc.jar and copy the content of the webroot subdirectory from the jar to %PACKAGE_HOME%\uddi\bsc\webdata

Unjar REGISTRY_HOME\app\uddi\web.jar and copy the content of the webroot subdirectory from the jar to %PACKAGE_HOME%\uddi\webdata.

Copy directory REGISTRY_HOME\doc to %PACKAGE_HOME%\uddi.

Package the content of %PACKAGE_HOME% into the file balancer.war using jar or some other compression utility.

Deploy balancer.war into the cluster manager server.