CAFE

WebLogic

Apache Plug-in 설정법

작성자Luke|작성시간07.08.30|조회수1,986 목록 댓글 0

Apache HTTP Server Plug-In 설정방법

Apache HTTP 서버에 Plug-in 을 설치한 후에는 해당 플러그인을 사용할 수 있도록 구성을 해주어야 합니다.After installing the plug-in in the Apache HTTP Server, configure the WebLogic Server Apache Plug-In and configure the server to use the plug-in. This section explains how to edit the Apache httpd.conf file to instruct the Apache server to load the WebLogic Server library for the plug-in as an Apache module, and to specify the application requests that should be handled by the module.

Editing the httpd.conf File

Edit the httpd.conf file in your Apache HTTP server installation to configure the Apache HTTP Server Plug-In.

This section explains how to locate and edit the httpd.conf file, to configure the server to use the WebLogic Server Apache Plug-In, to proxy requests by path or by MIME type, to enable HTTP tunneling, and to use other WebLogic Server plug-in parameters.

  1. httpd.conf 파일 열기

    파일 위치 =>  APACHE_HOME\conf\httpd.conf
    (where APACHE_HOME is the root directory of your Apache HTTP server installation). See a sample httpd.conf file at Setting Up Perimeter Authentication.

  2. Ensure that the WebLogic Server modules are included for Apache 2.0.x, manually add the following line to the httpd.conf file:
    LoadModule weblogic_module   modules\mod_wl_20.so
  3. Add an IfModule block that defines one of the following:

    For a non-clustered WebLogic Server:

    The WebLogicHost and WebLogicPort parameters.

    For a cluster of WebLogic Servers:

    The WebLogicCluster parameter.

    For example:

    <IfModule mod_weblogic.c>
      WebLogicHost myweblogic.server.com
      WebLogicPort 7001
    </IfModule>
  4. To proxy requests by MIME type, add a MatchExpression‎ line to the IfModule block. Note that if both MIME type and proxying by path are enabled, proxying by path takes precedence over proxying by MIME type.

    For example, the following IfModule block for a non-clustered WebLogic Server specifies that all files with MIME type .jsp are proxied:

    <IfModule mod_weblogic.c>
      WebLogicHost myweblogic.server.com
      WebLogicPort 7001
      MatchExpression‎ *.jsp
    </IfModule>

    You can also use multiple MatchExpressions, for example:

    <IfModule mod_weblogic.c>
      WebLogicHost myweblogic.server.com
      WebLogicPort 7001
      MatchExpression‎ *.jsp
      MatchExpression‎ *.xyz
    </IfModule>

    If you are proxying requests by MIME type to a cluster of WebLogic Servers, use the WebLogicCluster parameter instead of the WebLogicHost and WebLogicPort parameters. For example:

    <IfModule mod_weblogic.c>
      WebLogicCluster w1s1.com:7001,w1s2.com:7001,w1s3.com:7001
      MatchExpression‎ *.jsp
      MatchExpression‎ *.xyz
    </IfModule>
  5. To proxy requests by path, use the Location block and the SetHandler statement. SetHandler specifies the handler for the Apache HTTP Server Plug-In module. For example the following Location block proxies all requests containing /weblogic in the URL:
    <Location /weblogic>
    SetHandler weblogic-handler
    PathTrim /weblogic
    </Location>

    The PathTrim parameter specifies a string trimmed from the beginning of the URL before the request is passed to the WebLogic Server instance (see General Parameters for Web Server Plug-Ins).

  6. Optionally, enable HTTP tunneling for t3 or IIOP.
    1. To enable HTTP tunneling if you are using the t3 protocol and weblogic.jar, add the following Location block to the httpd.conf file:
      <Location /HTTPClnt>
      SetHandler weblogic-handler
      </Location>
    2. To enable HTTP tunneling if you are using the IIOP, the only protocol used by the WebLogic Server thin client, wlclient.jar, add the following Location block to the httpd.conf file:
      <Location /iiop>
      SetHandler weblogic-handler
      </Location>
  7. Define any additional parameters for the Apache HTTP Server Plug-In.

    The Apache HTTP Server Plug-In recognizes the parameters listed in General Parameters for Web Server Plug-Ins . To modify the behavior of your Apache HTTP Server Plug-In, define these parameters either:

    • In a Location block, for parameters that apply to proxying by path, or
    • In an IfModule block, for parameters that apply to proxying by MIME type.

 

 

[httpd.conf Sample]


LoadModule weblogic_module modules/mod_wl_20.so
<IfModule mod_weblogic.c>
  WebLogicHost myweblogic.server.com
  WebLogicPort 7001
  DebugConfigInfo ON

  CookieName JSESSIONID

  KeepAliveEnabled ON

  KeepAliveSecs 20

  DynamicServerList OFF

  Idempotent OFF
  MatchExpression‎ *.jsp

  WLExcludePathOrMimeType "*.gif, *.css, *.js"

#Debug Option 설정

  Debug ALL
  WLLogFile D:\Temp\wlproxy.log

#SSL 연동 설정
  SecureProxy ON
  EnforceBasicConstraints off
  TrustedCAFile D:\temp\test.pem
  RequireSSLHostMatch false
</IfModule>

<Location /weblogic>

 SetHandler weblogic-handler

 PathTrim /weblogic

</Location>

or

 

LoadModule weblogic_module modules/mod_wl_20.so
<IfModule mod_weblogic.c>
WebLogicCluster agarwalp02: 8005, agarwalp02: 8006
Debug ON
WLLogFile c: /tmp/global_proxy.log
WLTempDir "c: /myTemp"
DebugConfigInfo On
KeepAliveEnabled ON
KeepAliveSecs 15
</IfModule>

 

 

http://webServer/index.jsp?__WebLogicBridgeConfig

 

 

[Virtual Host 설정]

LoadModule weblogic_module modules/mod_wl_22.so

NameVirtualHost *:80

<VirtualHost *:80>

DocumentRoot C:\Apache\htdocs
ServerName fis.domain.com:80
<IfModule mod_weblogic.c>
  WebLogicHost xxx.xxx.xxx.xx
  WebLogicPort 7003
  MatchExpression‎ *
</IfModule>
</VirtualHost>

<VirtualHost *:80>
ServerName account.domain.com:80
<IfModule mod_weblogic.c>
  WebLogicHost xxx.xxx.xxx.xx
  WebLogicPort 7005
  MatchExpression‎ *
</IfModule>
</VirtualHost>

<VirtualHost *:80>
ServerName pda.domain.com:80
<IfModule mod_weblogic.c>
  WebLogicHost xxx.xxx.xxx.xx

  WebLogicPort 7007
  MatchExpression‎ *
</IfModule>
</VirtualHost>

 

 

▶ WLS Plug-in 로그분석

첨부파일 WLS_Plugin_log분석.pdf

 

다음검색
현재 게시글 추가 기능 열기

댓글

댓글 리스트
맨위로

카페 검색

카페 검색어 입력폼