Go to the conf path of IHS. By default it will be under /opt/IBM/HTTPServer/conf
Take a backup of httpd.conf file
Add following two lines
LoadModule was_app22_module /opt/IBM/WebSphere/Plugins/bin/64bits/mod_was_ap22_http.so
WebSpherePluginConfig /opt/IBM/WebSphere/Plugins/config/WebServer-1/plugin-cfg.xml
Tip: if you are not sure the file location of mod_was_ap22_http.so then you can use find command.
Restart HTTP server
This concludes you have successfully integrated IBM HTTP Server with IBM WebSphere Application Server.
Note: In order to have context root accessible through a web server, you must select Web Server as the target during deployment.
Whenever you add new application or changes in context root, you must generate and propagate plug-in.
So that was all for today. Hope you like this.
Configuring a web server and an application server profile on the same machine
WebSphere® Application Server provides web server plug-ins that you can configure to communicate with a particular brand of web server. Learn how to install the web server, its web server plug-in for WebSphere Application Server, and the application server on the same machine.
Before you begin
When multiple profiles exist, you can select the profile that the Web Server Plug-ins Configuration Tool configures. See Plug-ins configuration for a description of the flow of logic that determines how to select the profile to configure.
When multiple profiles exist, you can select the profile that the Web Server Plug-ins Configuration Tool configures. See Plug-ins configuration for a description of the flow of logic that determines how to select the profile to configure.
If the WebSphere Application Server product family supports a particular brand of web server, such as IBM® HTTP Server or Microsoft Internet Information Services (IIS), your WebSphere Application Server product provides a binary plug-in for the web server that you must install.
If the WebSphere Application Server product family does not provide a binary plug-in for a particular brand of web server, then the web server is not supported. The purpose of the binary plug-in is to provide the communication protocol between the web server and the application server.
Suppose that you create a new profile and you also want to use a web server. You must install a new web server for the new profile, install the Web Server Plug-ins, and use the Web Server Plug-ins Configuration Tool to configure both the web server and the application server.
If the web server is not already installed, you can still install the Web Server Plug-ins for future use.
This procedure configures the application server profile that is the default profile on the machine. A one-to-one relationship exists between a web server and the application server.
However, a standalone application server profile and a managed profile can each have multiple web servers defined, each in a separate web server definition.
This article describes how to create the following topology:
Note
Nonroot installation for the plug-in component is only supported if the application server was also installed by the same nonroot user. Otherwise, the web server configuration scripts will fail to run against the application server installation.
About this task
Note
This topic references one or more of the application server log files. As a recommended alternative, you can configure the server to use the High Performance Extensible Logging (HPEL) log and trace infrastructure instead of using SystemOut.log , SystemErr.log, trace.log, and activity.log files on distributed and IBM i systems. You can also use HPEL in conjunction with your native z/OS® logging facilities. If you are using HPEL, you can access all of your log and trace information using the LogViewer command-line tool from your server profile bin directory. See the information about using HPEL to troubleshoot applications for more information on using HPEL.
The Web Server Plug-ins Configuration Tool configures the plug-in for the supported web server after collecting the following information:
Type of web server to configure
Architecture of your installed target web server (64 bit or 32 bit)
Location of the configuration file or files for the web server to be configured
Web server port
For IBM HTTP Server, the following information:
o Port number for optional IBM HTTP Server administrative server setup
o User ID and password to authenticate to the optional IBM HTTP Server administrative server from the administrative console
o 
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
o 
User ID and password if you choose to run the IBM HTTP Server administrative server as a Window service
Name of the web server definition
Configuration scenario to be used
o If it is a remote scenario, the tool collects the host name or IP address of the application server.
o If it is a local scenario, the tool collects the installation root directory of the WebSphere Application Server product.
Profile to be configured with the web server plug-in
The Web Server Plug-ins Configuration Tool edits the configuration file or files for a web server by creating directives that point to the location of the binary plug-in module and the plug-in configuration file.
The name of the binary plug-in module varies per web server type. The plug-in configuration file is always the plugin-cfg.xml file.
The Web Server Plug-ins Configuration Tool creates a web server definition in the configuration of the application server unless one already exists.
You can use the administrative console to manage the web server configuration. For example, when you install an application on the application server, you can also choose to install it on the web server definition. If so, the updated plugin-cfg.xml file shows that the new application is available. When the web server reads the updated plug-in configuration file, the web server becomes aware of the new application that it can serve to web clients.
If you choose not to install the new application on the web server definition, the application is not added to the plug-in configuration file. The web server is not aware of the application and cannot serve it to web clients.
Tip
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 Configuring a web server plug-in using the pct tool for more information.
Use this procedure to install the web server plug-in, configure the web server, and create a web server definition in the default application server profile.
Procedure
Configure a standalone application server.
1. Log on to the operating system.
If you are installing as a nonroot or non-administrative user, then there are certain limitations.
In addition, select a umask that allows the owner to read/write to the files, and allows others to access them according to the prevailing system policy. For root, a umask of 022 is recommended. For nonroot users, a umask of 002 or 022 could be used, depending on whether or not the users share the group. To verify the umask setting, issue the following command:
umask
To set the umask setting to 022, issue the following command:
umask 022
When installing as an administrative user on a Windows operating system, a Windows service is automatically created to autostart the application server. The installer user account must have the following advanced user rights:
Act as part of the operating system
Log on as a service
For example, on some Windows operating systems, click Control Panel > Administrative Tools > Local Security Policy > Local Policies > User Rights Assignments to set the advanced options. See your Windows operating system documentation for more information.
If you plan to run the application server as a Windows service, do not install from a user ID that contains spaces. A user ID with spaces cannot be validated. Such a user ID is not allowed to continue the installation. To work around this restriction, install with a user ID that does not contain spaces.
2. Install Installation Manager.
3. Use Installation Manager to install the following:
WebSphere Application Server Network Deployment
Web Server Plug-ins for WebSphere Application Server
Websphere Customization Toolbox
4. Use Installation Manager to install the IBM HTTP Server, or install another supported web server.
5. Open the Websphere Customization Toolbox, and launch the Web Server Plug-ins Configuration Tool.
6. Select a Web Server Plug-ins 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:
a. Click Add.
b. Enter a name for the web server plug-in location.
c. Perform one of the following actions:
Enter the location.
Click Browse, find the location, and click OK.
7. Click Create.
8. Select the type of web server that you are configuring, and click Next.
9. Select the architecture of your installed target web server (64 bit or 32 bit) and click Next if you are asked.
10. 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
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
11. 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.
i. Select Setup IBM HTTP Server Administration Server.
ii. Specify a port number on which the IBM HTTP administration server will communicate.
以下文章點擊率最高
Loading…