Accessing Applications Via the Proxy Server Ensure that applications clients will

Setting up WebLogic Clusters 10-17

10.2.9.1.4 Accessing Applications Via the Proxy Server Ensure that applications clients will

access via the proxy server are deployed to your cluster. Address client requests to the listen address and listen port of the proxy server. If you have problems: ■ Make sure all servers instances have unique addressport combinations Each of the server instances in the configuration must have a unique combination of listen address and listen port. ■ Make sure that the proxy servlet is the default application for the proxy server If you get a page not found error when you try to your application, make sure that weblogic.xml is in \WEB-INF for the application and that it sets the context-root deployment parameter to . ■ When all else fails, restart If you are having problems try rebooting all your servers, some of the changes you made while configuring your setup may not have been persisted to the configuration file. ■ Verify Your Configuration To verify the configuration of the HttpClusterServlet: clientCertProxy Specifies to trust client certificates in the WL-Proxy-Client-Cert header. Valid values are true and false. The default value is false. This setting is useful if user authentication is performed on the proxy server—setting clientCertProxy to true causes the proxy server to pass on the certs to the cluster in a special header, WL-Proxy-Client-Cert. The WL-Proxy-Client-Cert header can be used by any client with direct access to WebLogic Server. WebLogic Server takes the certificate information from that header, trusting that is came from a secure source the plug-in and uses that information to authenticate the user. For this reason, if you set clientCertProxy to true, use a connection filter to ensure that WebLogic Server accepts connections only from the machine on which the plug-in is running. See Using Network Connection Filters in Programming Security for Oracle WebLogic Server. PathPrepend String that the servlet prepends to the original URL, after PathTrim is trimmed, before forwarding the URL to the cluster. init-param param-namePathPrependparam-name param-valueParameterValueparam-value init-param RoutingHandlerCl assName Extends the proxy servlet to support Web service cluster routing. For more information, see Managing Web Services in a Cluster in Programming Advanced Features of JAX-WS Web Services for Oracle WebLogic Server. init-param param-nameRoutingHandlerClassNameparam-name param-value weblogic.wsee.jaxws.cluster.proxy.SOAPRoutingHandler param-value init-param Table 10–1 Cont. Proxy Servlet Deployment Parameter Parameter Usage 10-18 Using Clusters for Oracle WebLogic Server 1. Set the DebugConfigInfo parameter in web.xml to ON. 2. Use a Web browser to access the following URL: http:myServer:portplaceholder.jsp?__WebLogicBridgeConfig Where: myServer is the Managed Server on the proxy machine where HttpClusterServlet runs, port is the port number on that server that is listening for HTTP requests, and placeholder.jsp is a file that does not exist on the server. The plug-in gathers configuration information and run-time statistics and returns the information to the browser. For more information, see Parameters for Web Server Plug-ins in Using Web Server Plug-ins With WebLogic Server.

10.2.10 Configure Replication Groups