Shulou(Shulou.com)06/02 Report--

The content of this article mainly focuses on how to integrate Websphere Application Server 5.0and IIS 5.0. the content of the article is clear and clear. It is very suitable for beginners to learn and is worth reading. Interested friends can follow the editor to read together. I hope you can get something through this article!

IIS (Microsoft Internet Information Server) is a widely used Web Server at present, and in some cases, we need to use it instead of the IBM Http Server that comes with WAS as Web Server. At this point, we need to do some configuration work to make WAS and IIS work together. IIS (Microsoft Internet Information Server) is a widely used Web Server at present, and in some cases, we need to use it instead of the IBM Http Server that comes with WAS as Web Server. At this point, we need to do some configuration work to make WAS and IIS work together.

Since most of the materials are about the integration of IBM HTTP Server and WAS, the editor hopes to combine the recent integration experience to demonstrate step by step how to configure IIS and WAS distributed on the two servers, hoping to help you.

The system environment used in this paper is as follows: operating system installed software Web Server Win2000 Server (SP3) IIS 5.0 Application Server Win2000 Server (SP3) WebSphere 5.0.1 in order to save space and highlight the key points, we omitted the installation process of IIS and WebSphere. Both products can be installed by default. Go back to the top of the page

two。 Set up a test site to finally test our installation, we first set up a test site Test on IIS and configure port 80 for its use. Go back to the top of the page

3. To install WebSphere Web Server Plug-in for IIS so that client HTTP requests can be sent to WAS through IIS, we first need to install WebSphere Web Server Plug-in for IIS on Web Server's machine. What I want to point out here is that, as shown in this article, it is best to install IIS, set up the site, and then install the plug-in, otherwise you need to do some extra manual configuration work, which is not meaningful and will not be explained too much in this article. Using the WAS installation disk, follow the prompts to customize the installation. (omit the installation steps such as selecting a language and accepting the license agreement here. ) only select the IIS item under Web server plug-in in the product list, as shown in the figure: follow the prompts to complete the installation. At this point, we open the IIS administration interface and see that two virtual directories are automatically established under our test site, Test. They are: IBMWebAs-sePlugins mapped to the web directory of the WAS installation directory-mapped to the bin directory of the WAS installation directory, and the installation of WebSphere Web Server Plug-in for IIS is completed. Go back to the top of the page

4. Configure WAS and generate Web server plug-in configuration in order for WAS to properly handle HTTP requests sent by IIS, we need to configure the virtual host properties of WAS. Log in to the WAS management console, in the function menu on the left, select / environment / virtual host in the list on the right, and select the name of the virtual host that is ready to handle the IIS transfer request. In this example, we choose default_host. On the page you enter, click "Host Alias" in "other attributes", and add one: host name is 192.168.0.1 (IP address of Web Server, DNS host name with domain name suffix, or DNS host name only). Port 80. Save the configuration. Restart the WAS server. After startup, log in to the WAS management console and select / Environment / Update Web server plug-in from the function menu on the left. Click the OK button to update the Web server plug-in configuration. Go back to the top of the page

5. Copy the Web server plug-in configuration file to Web Server. In the previous step, we generated the Web server plug-in configuration file, which is stored in / config/cells/ under the WAS installation directory, named plugin-cfg.xml. We need to copy it to the same directory in Web Server, and the same directory structure is established when WebSphere Web Server Plug-in for IIS is installed.

At this point, all the configuration work has been completed. If all goes well, you can already access the application on WAS through IIS. Go back to the top of the page

6. Web server plug-in configuration file analysis although, under smooth circumstances, we may not have to analyze the Web server plug-in configuration file, but due to different environments and changes in requirements, such as the mapping of request forwarding, we often need to manually edit the Web server plug-in configuration file.

In this file, for clarity, we have deleted some applications that are installed by default in WAS, including the parts related to admin console. Due to the different applications deployed and the different configurations of virtual hosts, the configuration file you get may be different from this. Log: this defines the location of the log file and the level at which the log information is recorded. There are three levels: Trace, Warn, Error VirtualHostGroup: here the virtual host name that defines a specific set of HTTP host heads is a virtual host group. It is convenient for you to configure multiple virtual hosts that handle similar requests.

Here is the virtual host entry we added that marks the IIS request information. ServerCluster: configure a set of servers that handle the same type of requests. Here we have only one, that is, the server with WAS installed. UriGroup: a set of URI that defines a specific HTTP request. For the sake of simplicity, we define all requests "/ *" as a group. In the actual running environment, you may need to handle things like * .htm,*.jsp,*.do,/webapp/* and so on differently. Route: defines which ServerCluster handles requests that belong to one of the above UriGroup. 7. Trouble Shooting if you find that IIS and WAS are still not working properly through the above configuration, please check the location of the log file configured in plugin-cfg.xml.

In this example, when the C:Program FilesWebSphereAppServerlogshttp_plugin.log is normal, the plug-in should have the following information after loading: [Wed Aug 13 08:55:16 2003] 00000314 00000474-PLUGIN: Plugins loaded. [Wed Aug 13 08:55:16 2003] 00000314 00000474-PLUGIN:-System Information--- [Wed Aug 13 08:55:16 2003] 00000314 00000474-PLUGIN: Bld date: Nov 11 00000474 18:23:32 [Wed Aug 13 08:55:16 2003] 00000314 00000474-PLUGIN: Webserver: IIS [Wed Aug 13 08:55:16 2003] 00000314 00000474-PLUGIN: Hostname = SCOTTLEE [Wed Aug 13 08:55:16 2003] 00000314 00000474-PLUGIN: OS version, build 2195, & # 39 If the plug-in is not loaded successfully, there will be an error message, such as: ERROR: ws_common: websphereGetStream: Failed to connect to app server on host & # 39: Service Pack: 192.168.0.1 WAS does not start properly.

In addition, you may find that http_plugin.log does not have any information, it is possible that your Web Server plugin is not installed correctly, or there is something wrong with the content of plugin-cfg.xml. One solution is to install a WAS with the same configuration on the same machine with IIS. After there is no problem with configuration forwarding, manually change the corresponding Transport Hostname in the ServerCluster in the plugin-cfg.xml to the hostname or IP of the remote WAS.

Thank you for your reading. I believe you have some understanding of "how to integrate Websphere Application Server 5.0with IIS 5.0". Go ahead and practice it. If you want to know more about it, you can follow the website! The editor will continue to bring you better articles!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.