iii. 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.
a. Click Next.
b. 
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.
c. 
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.
i. 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
ii. Choose whether your startup type will be automatic or manual.
d. Click Next.
12. Specify a unique name for the web server definition, and click Next.
13. Select the configuration scenario.
. Choose the local scenario.
a. 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.
b. Click Next.
14. Select the profile to configure with the current web server plug-in, and click Next.
15. Review the summary information, and click Configure to begin configuring the web server, web server plug-in, and application server profile.
16. 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.
17. Domino Web Server only: Set the WAS_PLUGIN_CONFIG_FILE environment variable.
On platforms such as AIX® or Linux, sourcing a script to the parent shell allows child processes to inherit the exported variables. On Windows systems, run the script as you would run any other command. Sourcing is automatic on Windows systems.
. Open a command window.
a. Change directories to the plug-ins installation root directory.
b. Issue the appropriate command for the plugins_root/bin/setupPluginCfg.sh script:
. plugins_root/bin/setupPluginCfg.sh (Notice the space between the period and the installation root directory.)
source plugins_root/bin/setupPluginCfg.sh
The script is also in the lotus_root/notesdata directory on operating systems such as AIX or Linux.
Issue the appropriate command for the script before starting the Domino Web Server.
18. 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:
./startServer.sh server1
startServer server1
startServer server1
a. 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:
Access the apache and apachectl commands in the IBMHttpServer/bin directory.
./apachectl start
apache
b. 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.
c. Verify that Snoop is running.
Either web address should display the Snoop Servlet – Request/Client Information page.
Tip
In the event of a verification failure where an HTTP error code of 500 appears, go to IIS Manager > Default Web Site > sePlugins. Right click, and choose to edit permissions. Click on the sharing tab, and choose to share with everyone (permissions level: read/write).
d. Remote IBM HTTP Server only:
Verify that the automatic propagation function can work on a remote IBM HTTP Server by using the following steps. This procedure is not necessary for local web servers.
. Create a user=adminUser, password=adminPassword in the IHS_root /conf/admin.passwd file. For example: c:\ws\ihs80\bin\htpasswd -cb c:\ws\ihs80\conf\admin.passwd adminUser adminPassword
i. Use the administrative console of the deployment manager or the application server to enter the User ID and password information that you created for the administrative user of IBM HTTP Server. Go to Servers > Web server > web_server_definition > Remote web server administration. Set the following values: admin Port=8008, User Id=adminUser, Password=adminPassword.
ii. Set the correct read/write permissions for the httpd.conf file and the plugin-cfg.xml file. See the IHS_root /logs/admin_ERROR. LOG file for more information.
Automatic propagation of the plug-in configuration file requires the IBM HTTP administrative server to be up and running. If you are managing an IBM HTTP Server using the WebSphere Application Server administrative console, the following error might display:
"Could not connect to IHS Administration server error"
Perform the following procedure to correct the error:
iii. Verify that the IBM HTTP Server administration server is running.
iv. Verify that the web server host name and the port that is defined in the WebSphere Application Server administrative console matches the IBM HTTP Server administration host name and port.
v. Verify that the fire wall is not preventing you from accessing the IBM HTTP Server administration server from the WebSphere Application Server administrative console.
vi. Verify that the user ID and password that is specified in the WebSphere Application Server administrative console under remote managed, is created in the admin.passwd file, using the htpasswd command.
vii. If you are trying to connect securely, verify that you export the IBM HTTP Server administration server keydb personal certificate into the WebSphere Application Server key database as a signer certificate. This key database is specified by the com.ibm.ssl.trustStore directive in the sas.client.props file in the profile where your administrative console is running. This consideration is primarily for self-signed certificates.
viii. If you still have problems, check the IBM HTTP Server admin_ERROR. LOG file and the WebSphere Application Server logs (trace.log file) to determine the cause of the problem.
Configure an application server that is federated into a deployment manager cell.
Note
The following procedure describes installing the plug-ins on two machines. However, you could perform this procedure on a single machine.
The following topology is considered a local distributed topology because it involves a cell:
This part of the procedure assumes that you have already installed Installation Manager and the Network Deployment product on both machines. Also assumed is that you have already configured a deployment manager profile on Machine A and an application server profile on Machine B.
If you are planning to add the application server node into a deployment manager cell but have not done so yet, start the deployment manager and federate the node before configuring the plug-in. You cannot add an application server with a web server definition into the deployment manager cell.
A web server definition on a federated application server is installed on the same managed node as the application server. There is one node, but with two server processes, the application server and the web server definition.
If you are installing the plug-ins for use with a federated application server, start the deployment manager. Verify that the node agent process on the managed node is also running. Both the deployment manager and the node agent must be running to successfully configure a managed node.
1. Use Installation Manager to install the following on Machine B.
Web Server Plug-ins for WebSphere Application Server
Websphere Customization Toolbox
2. Use Installation Manager to install IBM HTTP Server on Machine B, or install another supported web server on Machine B.
3. Open the WebSphere Customization Toolbox and launch the Web Server Plug-ins Configuration Tool on Machine B.
4. 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.
a. Enter a name for the web server plug-in location.
b. Perform one of the following actions:
Enter the location.
Click Browse, find the location, and click OK.
5. Click Create.
6. Select the type of web server that you are configuring, and click Next.
7. Select the architecture of your installed target web server (64 bit or 32 bit), and click Next.
8. 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
以下文章点击率最高
Loading…