WLS HttpClusterServlet 설정 (웹로직 proxy 플러그인)

[Luke]

http://e-docs.bea.com/wls/docs100/cluster/setup.html#wp684345

To use the HTTP cluster servlet, configure it as the default web application on your proxy server machine, as described in the steps below. For an introduction to web applications, see Overview of Web Applications in Developing Web Applications for WebLogic Server.

1. If you have not already done so, configure a separate, non-clustered Managed Server to host the HTTP Cluster Servlet.
2. Create the web.xml deployment descriptor file for the servlet. This file must reside in the \WEB-INF subdirectory of the web application directory. A sample deployment descriptor for the proxy servlet is provided in Sample web.xml. For more information on web.xml, see Understanding Web Applications, Servlets, and JSPs in Developing Web Applications, Servlets, and JSPs for WebLogic Server.
   1. Define the name and class for the servlet in the <servlet> element in web.xml. The servlet name is HttpClusterServlet. The servlet class is weblogic.servlet.proxy.HttpClusterServlet.
   2. Identify the clustered server instances to which the proxy servlet will direct requests in the <servlet> element in web.xml, by defining the WebLogicCluster parameter.
   3. Optionally, define the following <KeyStore> initialization parameters to use two-way SSL with your own identity certificate and key. If no <KeyStore> is specified in the deployment descriptor, the proxy will assume one-way SSL.
      • <KeyStore> - The key store location in your Web application.
      • <KeyStoreType> - The key store type. If it is not defined, the default type will be used instead.
      • <PrivateKeyAlias> - The private key alias.
      • <KeyStorePasswordProperties> - A property file in your Web application that defines encrypted passwords to access the key store and private key alias. The file contents looks like this:
        KeyStorePassword={3DES}i4+50LCKenQO8BBvlsXTrg\=\=
PrivateKeyPassword={3DES}a4TcG4mtVVBRKtZwH3p7yA\=\=

        You must use the weblogic.security.Encrypt command-line utility to encrypt the password. For more information on the Encrypt utility, as well as the CertGen, and der2pem utilities, see Using the WebLogic Server Java Utilities in the WebLogic Server Command Reference.
   4. Create <servlet-mapping> stanzas to specify the requests that the servlet will proxy to the cluster, using the <url-pattern> element to identify specific file extensions, for example *.jsp, or *.html. Define each pattern in a separate <servlet-mapping> stanza.

      You can set the <url-pattern> to "/" to proxy any request that cannot be resolved by WebLogic Server to the remote server instance. If you do so, you must also specifically map the following extensions: *.jsp, *.html, and *.html, to proxy files ending with those extensions. For an example, see Sample web.xml.

   5. Define, as appropriate, any additional parameters. See Table  for a list of key parameters. See Parameters for Web Server Plug-insin Using WebLogic Server with Plug-ins for a complete list. Follow the syntax instructions in Proxy Servlet Deployment Parameters.
3. Create the weblogic.xml deployment descriptor file for the servlet. This file must reside in the \WEB-INF subdirectory of the web application directory.

   Assign the proxy servlet as the default web application for the Managed Server on the proxy machine by setting the <context-root> element to a forward slash character (/) in the <weblogic-web-app> stanza. For an example, see Sample weblogic.xml.

4. In the Administration Console, deploy the servlet to the Managed Server on your proxy server machine. For instructions, see Deploying a New Web Application in Administration Console Online Help.

Sample web.xml

This section contains a sample deployment descriptor file (web.xml) for HttpClusterServlet.

web.xml defines parameters that specify the location and behavior of the proxy servlet: both versions of the servlet:

• The DOCTYPE stanza specifies the DTD used by WebLogic Server to validate web.xml.
• The servlet stanza:
  • Specifies the location of the proxy plug-in servlet class. The file is located in the weblogic.jar in your WL_HOME/server/lib directory. You do not have to specify the servlet's full directory path in web.xml because weblogic.jar is put in your CLASSPATH when you start WebLogic Server.
  • Identifies the host name(either DNS name or IP address) and listen port of each Managed Servers in the cluster, using the WebLogicCluster parameter.
  • Identifies the key store initialization parameters to use two-way SSL with your own identity certificate and key.
• The three servlet-mapping stanzas specify that the servlet will proxy URLs that end in '/', 'htm', 'html', or 'jsp' to the cluster.

For parameter definitions see Proxy Servlet Deployment Parameters.

<!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>hostname1:7736|hostname2:7736|hostname:7736</param-value>
  </init-param>

  <init-param>
    <param-name>KeyStore</param-name>
    <param-value>/mykeystore</param-value>
  </init-param>

  <init-param>
    <param-name>KeyStoreType</param-name>
    <param-value>jks</param-value>
  </init-param>

  <init-param>
    <param-name>PrivateKeyAlias</param-name>
    <param-value>passalias</param-value>
  </init-param>

  <init-param>
    <param-name>KeyStorePasswordProperties</param-name>
    <param-value>mykeystore.properties</param-value>
  </init-param>

</servlet>

<servlet-mapping>
  <servlet-name>HttpClusterServlet</servlet-name>
  <url-pattern>/</url-pattern>
</servlet-mapping>

<servlet-mapping>
  <servlet-name>HttpClusterServlet</servlet-name>
  <url-pattern>*.jsp</url-pattern>
</servlet-mapping>

<servlet-mapping>
  <servlet-name>HttpClusterServlet</servlet-name>
  <url-pattern>*.htm</url-pattern>
</servlet-mapping>

<servlet-mapping>
  <servlet-name>HttpClusterServlet</servlet-name>
  <url-pattern>*.html</url-pattern>
</servlet-mapping>

</web-app>

Sample weblogic.xml

This section contains a sample weblogic.xml file. The <context-root> deployment parameter is set to "/". This makes the proxy servlet the default web application for the proxy server.

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

Proxy Servlet Deployment Parameters

Key parameters for configuring the behavior of the proxy servlet in web.xml are listed in Table 10-1.

The parameters for the proxy servlet are the same as those used to configure WebLogic Server plug-ins for Apache, Microsoft, and Netscape web servers. For a complete list of parameters for configuring the proxy servlet and the plug-ins for third-part web servers see Parameters for Web Server Plug-insin Using WebLogic Server with Plug-ins.

The syntax for specifying the parameters, and the file where they are specified, is different for the proxy servlet and for each of the plug-ins.

For the proxy servlet, specify the parameters in web.xml, each in its own <init-param> stanza within the <servlet> stanza of web.xml. For example:

<init-param>
<param-name>ParameterName</param-name>
<param-value>ParameterValue</param-value>
</init-param>

Table 10-1 Proxy Servlet Deployment Parameter

Parameter	Usage
WebLogicCluster	<init-param> <param-name>WebLogicCluster</param-name> <param-value>WLS1.com:port|WLS2.com:port </param-value> Where WLS1.com and WLS2.com are the host names of servers in the cluster, and port is a port where the host is listening for HTTP requests. If you are using SSL between the plug-in and WebLogic Server, set the port number to the SSL listen port (see Configuring the Listen Port) and set the SecureProxy parameter to ON.
SecureProxy	<init-param> <param-name>SecureProxy</param-name> <param-value>ParameterValue</param-value> </init-param> Valid values are ON and OFF. If you are using SSL between the plug-in and WebLogic Server, set the port number to the SSL listen port (see Configuring the Listen Port) and set the SecureProxy parameter to ON.
DebugConfigInfo	<init-param> <param-name>DebugConfigInfo</param-name> <param-value>ParameterValue</param-value> </init-param> Valid values are ON and OFF. If set to ON, you can query the HttpClusterServlet for debugging information by adding a request parameter of ?__WebLogicBridgeConfig to any request. (Note: There are two underscore ( _ ) characters after the ?.) For security reasons, it is recommended that you set the DebugConfigInfo parameter to OFF in a production environment.
ConnectRetry Secs	Interval in seconds that the servlet will sleep between attempts to connect to a server instance. Assign a value less than ConnectTimeoutSecs. The number of connection attempts the servlet makes before returning an HTTP 503/Service Unavailable response to the client is ConnectTimeoutSecs divided by ConnectRetrySecs. Syntax: <init-param> <param-name>ConnectRetrySecs</param-name> <param-value>ParameterValue</param-value> </init-param>
ConnectTimeout Secs	Maximum time in seconds that the servlet will attempt to connect to a server instance. Assign a value greater than ConnectRetrySecs. If ConnectTimeoutSecs expires before a successful connection, an HTTP 503/Service Unavailable response is sent to the client. Syntax: <init-param> <param-name>ConnectTimeoutSecs</param-name> <param-value>ParameterValue</param-value> </init-param>
PathTrim	String trimmed by the plug-in from the beginning of the original URL, before the request is forwarded to the cluster. Syntax: <init-param> <param-name>PathTrim</param-name> <param-value>ParameterValue</param-value> </init-param> Example: If the URL http://myWeb.server.com/weblogic/foo is passed to the plug-in for parsing and if PathTrim has been set to /weblogic the URL forwarded to WebLogic Server is: http://myWeb.server.com:7001/foo
TrimExt	The file extension to be trimmed from the end of the URL. Syntax: <init-param> <param-name>TrimExt</param-name> <param-value>ParameterValue</param-value> </init-param>
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 WebLogic Security.
PathPrepend	String that the servlet prepends to the original URL, after PathTrim is trimmed, before forwarding the URL to the cluster. <init-param> <param-name>PathPrepend</param-name> <param-value>ParameterValue</param-value> </init-param>

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 address/port 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:

  1. Set the DebugConfigInfo parameter in web.xml to ON.
  2. Use a Web browser to access the following URL:

     http://myServer:port/placeholder.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-insin Using WebLogic Server with Plug-ins.

httpClusterServlet.zip