WebLogic specific configuration for use with cluster

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 the 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. 3. 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 [http:e-docs.bea.comwlsdocs81secmanage ssl.html1185171] in BEAs WebLogic product documentation. 4. Prepare a registry deployment package REGISTRY_HOME\conf\porting\weblogic\registry.war as described in Section Oracle WebLogic deployment details . In our case, the http port is 7101 , the https port is 7102 , and the application server context is wasp . 5. Check that the paths for log4j.appender.eventLog.File, log4j.appender.errorLog.File, and registry.war\conf\log4j.config are valid on all cluster nodes. 6. Deploy registry.war into all WebLogic cluster nodes You must also prepare the package for the balancer which will only be deployed to the cluster manager server. To do so: 1. Create a balancer directory, in, for example, REGISTRY_HOME. This directory is referenced in this section as PACKAGE_HOME . 2. Create a subdirectory of PACKAGE_HOME named WEB-INF. 3. 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 looks like: ?xml version=1.0 encoding=UTF-8? DOCTYPE web-app PUBLIC -Sun Microsystems, Inc.DTD Web Application 2.3EN http:java.sun.comdtdweb-app_2_3.dtd web-app servlet servlet-nameHttpClusterServletservlet-name servlet-classweblogic.servlet.proxy.HttpClusterServletservlet-class init-param param-nameWebLogicClusterparam-name param-valuekila:7101|fido:7101param-value init-param servlet servlet servlet-nameFileServletservlet-name servlet-classweblogic.servlet.FileServletservlet-class servlet Page 128

7.4. WebLogic specific configuration for use with cluster

servlet-mapping servlet-nameFileServletservlet-name url-patternuddiwebdataurl-pattern servlet-mapping servlet-mapping servlet-nameHttpClusterServletservlet-name url-patternurl-pattern servlet-mapping servlet-mapping servlet-nameFileServletservlet-name url-patternuddibscwebdataurl-pattern servlet-mapping web-app 4. In the WEB-INF subdirectory, create the file weblogic.xml containing the following text, where wasp is the context of Oracle Service Registry deployed 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.1EN http:www.bea.comserverswls810dtdweblogic810-web-jar.dtd weblogic-web-app context-rootwaspcontext-root weblogic-web-app 5. Create the directory PACKAGE_HOME\uddi\webdata. 6. Unjar REGISTRY_HOME\app\uddi\bsc.jar and copy the content of the webroot subdirectory from the jar to PACKAGE_HOME\uddi\bsc\webdata 7. Unjar REGISTRY_HOME\app\uddi\web.jar and copy the content of the webroot subdirectory from the jar to PACKAGE_HOME\uddi\webdata . 8. Package the content of PACKAGE_HOME into the file balancer.war using jar or some other compression utility. 9. Deploy balancer.war into the cluster manager server.

8. Authentication Configuration

This section explains how to change the Oracle Service Registry configuration to allow the following authentication options: • HTTP Basic • Netegrity SiteMinder • SSL Client authentication with Embedded HTTPHTTPS Server • SSL Client Authentication in Oracle WebLogic • J2EE Server Authentication • Internal SSL Client Authentication Mapping in J2EE Page 129

8. Authentication Configuration

• Disabling Normal Authentication • Outgoing Connections Protected with SSL Client Authentication

8.1. HTTP Basic

Important In the case where Registry is deployed to an Oracle WebLogic Server • Add the enforce-valid-basic-auth-credentialsfalseenforce-valid-basic-auth-credentials element to config.xml in the directory [domain]\config within the security-configuration element. • The enforce-valid-basic-auth-credentials flag effects the entire domain. Client requests that use HTTP BASIC authentication will be ignored by WebLogic Server authentication. To allow HTTP Basic authentication: 1. Modify REGISTRY_HOMEappuddiservicesWasp-infpackage.xml to enable HTTP basic authentication as follows: a. Under processing name=UDDIv1v2v3PublishingProcessing , uncomment use ref=tns:HttpBasicInterceptor . This enables the HTTP Basic authentication for UDDI Publishing API v1, v2, v3. b. Under processing name=UDDIv1v2v3InquiryProcessing , add use ref=tns:HttpBasicInterceptor . This enables the HTTP Basic authentication for all three versions of the UDDI Inquiry API. c. Under processing name=wsdl2uddiProcessing, add use ref=tns:HttpBasicInterceptor . This enables the HTTP Basic authentication for versions 2 and 3 of the WSDL2UDDI API. d. Add the attribute accepting-security-providers=HttpBasic to other service-endpoints except UDDI publishing and Inquiry endpoint you wish to access via HTTP Basic authentication. A fragment of the package.xml is shown in Example 2, package.xml - HTTP Basic Enabled 2. Shutdown Oracle Service Registry, delete the REGISTRY_HOMEwork directory, and restart the registry. Page 130

8.1. HTTP Basic