This procedure describes installing a web server and its
plug-in on a machine that contains a deployment manager and a managed
node.
Before you begin
다중 프로파일이 존재하면 웹 서버 플러그인 구성 도구가
구성하는 플러그인을 선택할 수 있습니다.
구성할 프로파일을 선택하는 방법을 판별하는 논리 플로우에 대한 설명은
Plug-ins configuration의
내용을 참조하십시오.
다중 프로파일이 존재하면 웹 서버 플러그인 구성 도구가
구성하는 플러그인을 선택할 수 있습니다.
구성할 프로파일을 선택하는 방법을 판별하는 논리 플로우에 대한 설명은
Plug-ins configuration의
내용을 참조하십시오.
This procedure configures the deployment manager profile
on the machine. A managed node must exist to define a web server definition,
which is always on a managed node.
Start
the deployment manager and the node agent for the managed node. The
deployment manager and the node must be running to successfully change
its configuration.
About this task
지원된 구성: 이 도구는 AIX®,
Linux 및 Windows에서만
지원됩니다. As an alternative to
using the Web Server Plug-ins Configuration Tool, you can use the pct command-line tool with a
response file to configure a web server. Read
pct 도구를 사용하여 웹 서버 플러그인 구성 for
more information.
sptcfg
Use
this procedure to install the web server plug-in, configure the web
server, and create a web server definition.
Procedure
- 운영 체제에 로그온하십시오.
루트가 아닌
사용자 또는 관리자가 아닌 사용자로 설치하는 경우 몇 가지
제한사항이 있습니다.
![[Windows]](../images/windows.gif)
Windows
운영 체제에 관리 사용자로 설치할 때 Windows
서비스를 자동으로 작성하여 애플리케이션 서버를
자동으로 시작합니다. 설치 프로그램
사용자 계정에는 다음과 같은 고급 사용자 권한이 있어야 합니다.
예를 들어, 일부 Windows 운영 체제에서는
제어판 > 관리 도구 > 로컬 보안 정책 > 로컬 정책 > 사용자 권한 지정을 클릭하여
고급 옵션을 설정하십시오. 자세한 정보는 Windows
운영 체제 문서를 참조하십시오.
Windows 서비스로 애플리케이션 서버를 실행하려는 경우
공백이 포함된 사용자 ID로는
설치하지 마십시오. 공백이 있는 사용자 ID는 유효성 검증할 수 없습니다.
이러한
사용자 ID로는 설치를 계속할 수 없습니다. 이 제한사항을 해결하려면 공백이 없는 사용자 ID로 설치하십시오.
- Install IBM® Installation
Manager.
- Use Installation Manager to install the WebSphere® Application Server
Network Deployment product.
- Create a deployment manager profile as the first profile
on the machine.
- Create a standalone application server or custom profile,
and federate the node.
- Use Installation Manager to install the following:
- Web Server Plug-ins for WebSphere Application
Server
- WebSphere Customization Toolbox
- Use Installation Manager to install IBM HTTP Server, or install another supported
web server.
- Open the WebSphere Customization
Toolbox and launch the Web Server Plug-ins Configuration Tool.
- Select a web server plug-in runtime location.
If
the location of a previously installed web server plug-in that you
want to use is not in the list, perform the following actions to add
the location to your working set:
- Click Add.
- Enter a name for the web server plug-in location.
- Perform one of the following actions:
- Enter the location.
- Click Browse, find the location, and click OK.
- Click Create.
- Select the type of web server that you are configuring,
and click Next.
- Select the architecture of your installed target web server
(64 bit or 32 bit) and click Next if you are
asked.
- Click Browse to select the configuration
file or files for your web server, verify that the web server port
is correct, and then click Next when you are
finished.
Select the file and not just the directory
of the file. Some web servers have two configuration files and require
you to browse for each file.
The following list shows configuration
files for supported web servers:
- Apache HTTP Server
- apache_root/config/httpd.conf
- Domino® Web Server
- names.nsf and Notes.jar
The
wizard prompts for the notes.jar file. The actual
name is Notes.jar.
The Web
Server Plug-ins Configuration Tool verifies that the files exist but
the tool does not validate either file.
- IBM HTTP Server
IHS_root/conf/httpd.conf
IHS_profile_root/conf/httpd.conf
- Microsoft Internet
Information Services (IIS)
- The Web Server Plug-ins Configuration Tool can determine the correct
files to edit.
- Sun Java™ System Web Server
(formerly Sun ONE Web Server and iPlanet Web Server) Version 6.0 and
later
- obj.conf and magnus.conf
- If you are configuring an IBM HTTP
web server plug-in, perform the following actions.
- Optionally, set up the administration server configuration to
administer the web server.
Attention: When using the Web
Server Plug-ins Configuration Tool to configure the IBM HTTP Server Administration Server, the Websphere
Customization Toolbox must be run as a "local" account with administrator/root privileges.
- Select Setup IBM HTTP
Server Administration Server.
- Specify a port number on which the IBM HTTP
administration server will communicate.
- Optionally, select Create a user ID for IBM Server Administration Server authentication and
enter a user ID and password to authenticate to the IBM HTTP Server administrative server from the
administrative console.
- Click Next.
![[AIX]](../images/aixlogo.gif)
Specify the system user ID
and group to have write permission to IBM HTTP
Server, the IBM HTTP Server
administrative server, and the web server plug-in configuration files.Select Create
a new unique system user ID and group using the credentials if
necessary.
Restriction: The
configuration might fail if you specify a new user ID or group name
that exceeds the platform limit, which is commonly 8 characters and
is sometimes configurable.
Optionally, set up the IBM HTTP Server Administration Server to run
as a Window service.- Select Run IBM HTTP Server
Administration Server as a Windows Service.
- Perform one of the following actions:
- Select Log on as a local system account.
- Select Log on as a specified user account, and enter the
user ID and password for that account.
The user ID requires the
following advanced user rights:
- Act as part of the operating system
- Log on as a service
- Choose whether your startup type will be automatic or manual.
- Click Next.
- Specify a unique name for the web server definition, and
click Next.
- Select the configuration scenario.
- Choose the local scenario.
- Perform one of the following actions:
- Enter the installation location of WebSphere Application Server (app_server_root).
- Click Browse, find the installation location of WebSphere Application Server
(app_server_root), and click OK.
- Click Next.
- Select the profile to configure with the current web server
plug-in, and click Next.
- Review the summary information, and click Configure to
begin configuring the web server, web server plug-in, and profile.
- Verify the success of the installation on the summary panel,
and click Finish.
If a problem
occurs and the installation is unsuccessful, examine the logs in the plugins_root/logs directory.
Correct any problems and re-configure.
Domino 웹 서버 전용: WAS_PLUGIN_CONFIG_FILE
환경 변수를 설정하십시오. AIX 또는 Linux 같은 플랫폼에서,
스크립트를 상위 쉘로 소스 지정하면 하위 프로세스가 내보낸 변수를 상속할 수 있습니다.
Windows 시스템에서
다른 명령을 실행하는 것처럼 스크립트를 실행하십시오. 소스 지정은
Windows 시스템에서 자동입니다.
- 명령 창을 여십시오.
- 플러그인 설치 루트 디렉토리로 디렉토리를 변경하십시오.
- plugins_root/bin/setupPluginCfg.sh
스크립트에 대해 적합한 명령을 실행하십시오.
![[AIX]](../images/aixlogo.gif)
![[HP-UX]](../images/hpux.gif)
. plugins_root/bin/setupPluginCfg.sh (마침표와
설치 루트 디렉토리 사이에 공간이 있음에 유의하십시오.)
source plugins_root/bin/setupPluginCfg.sh
스크립트는 AIX 또는 Linux 같은 운영 체제의
lotus_root/notesdata 디렉토리에도 있습니다.
Domino 웹 서버를 시작하기 전에
스크립트에 맞는 적절한 명령을 실행하십시오.
- 배치 관리자의 관리 콘솔에서 시스템 관리 >
마스터 저장소에 변경사항 저장 > 노드에서 변경사항 동기화 > 저장을
클릭하십시오.
- Start the Snoop servlet to verify the ability
of the web server to retrieve an application from the application
server.
Test your environment by starting your application
server, your web server, and using the Snoop servlet with an IP address.
- Start the application server. In a Network Deployment environment, the Snoop servlet
is available in the cell only if you included the DefaultApplication
when adding the application server to the cell. The -includeapps option
for the addNode command migrates the DefaultApplication
to the cell. If the application is not present, skip this step.
Change
directories to the
profile_root/bin directory
and run the
startServer command:
![[AIX]](../images/aixlogo.gif)
./startServer.sh
server1
startServer server1
startServer server1
- Start the IBM HTTP
Server or the web server that you are using.
Use either the 2001 page or use the STRTCPSVR
SERVER(*HTTP) HTTPSVR(instance_name ) command to
start the IBM HTTP Server.
Use a command window to change the directory to the IBM HTTP Server installed image,
or to the installed image of your web server. Issue the appropriate
command to start the web server, such as these commands for IBM HTTP Server:
To
start the IBM HTTP Server from
the command line:
![[AIX Solaris HP-UX Linux Windows]](../images/dist.gif)
Access the
apache and
apachectl commands
in the
IBMHttpServer/bin directory.
- Point your browser to http://localhost:9080/snoop to
test the internal HTTP transport provided by the application server.
Point your browser to http://Host_name_of_Web_server_machine/snoop to
test the web server plug-in.
The HTTP Transport port
is 9080 by default and must be unique for every profile. The port
is associated with a virtual host named default_host, which is configured
to host the installed DefaultApplication. The Snoop servlet is part
of the DefaultApplication. Change the port to match your actual HTTP
Transport port.
- Verify that Snoop is running.
Either Web
address should display the Snoop Servlet - Request/Client Information
page.
Results
웹 서버 플러그인을 설치하면
Plugins 디렉토리와 여러 서브디렉토리가
작성됩니다. 다음은 Linux
시스템에서 작성된 디렉토리로, 예를 들면 다음과 같습니다.
- plugins_root/bin/32bits 또는 plugins_root/bin/64bits에는
지원되는 모든 웹 서버에 대한 2진 플러그인이 포함되어 있습니다.
- plugins_root/logs에는
로그 파일이 들어 있음
- plugins_root/properties에는
버전 정보가 들어 있음
The
Installation Manager configures the web server to use the plugins_root/plugin-cfg.xml file.
What to do next
After installing the binary plug-in for the local Web
server, you must create a managed node before you can successfully
run the configuration script and use the web server.
See Plug-ins configuration for an overview
of the installation procedure.
See Web server configuration for
more information about the files involved in configuring a web server.
See Editing web server configuration files for information
about how the Web Server Plug-ins Configuration Tool configures supported
web servers.
See 웹 서버 플러그인 구성 for
information about other installation scenarios for installing Web
server plug-ins.