Shulou(Shulou.com)05/31 Report--

In this issue, the editor will bring you about how to analyze IHS problems. The article is rich in content and analyzes and narrates it from a professional point of view. I hope you can get something after reading this article.

Generally speaking, IBM Http Server (referred to as IHS) and Websphere Application Server (referred to as WAS) are used together, that is, through port 80 of IHS to indirectly access WAS's dynamic web (jsp,servlet,javabean) and EJB (Enterprise Javabean). The default application port used by WAS is 9080. In actual projects, it is often encountered that 80% of IHS is not available, and you must add 9080 to make the application accessed normally. Some friends stay up late to fight and almost freak out, but it's not so scary. After many battles with this issue, I have gained a little experience, hoping to give some reference to other friends who have just come into contact with WAS and IHS. Without saying much about the principle, let's take a look at a few questions.

The reasons for the unavailability of port 80 or the inability of IHS to deliver requests to port 9080 of was are generally as follows:

1. Plug-in question:

After you install IHS, be sure to generate and distribute plug-ins in the WAS console. If you do not do this, you will not be able to use IHS 80 port properly.

Without this item, there is no way to combine was and ihs. When you have done this, you will find that these two sentences will be automatically added at the end of the httpd.conf file of IHS.

LoadModule was_ap22_module / usr/IBM/HTTPServer/Plugins/bin/32bits/mod_was_ap22_http.so

WebSpherePluginConfig / usr/IBM/HTTPServer/Plugins/config/webserver1/plugin-cfg.xml

Of course, sometimes you click on the generate and propagate plug-ins, but these two sentences are not available in httpd.conf. Please check the write permission of httpd.conf or add these two sentences manually.

2. Do not modify httpd.conf easily:

Don't change IHS's httpd.conf at will if you don't understand how to modify it.

After installing was, install ihs. Start the was management console, after entering, stop uninstalling the default application DefaultApplication, and then deploy your application (such as the WAR package with wsad or AAT). After startup, test whether the access to port 9080 is normal, and then under the management console: environment-update the web server plug-in-make sure, restart ihs, and you will naturally be in the httpd.conf of ihs.

You see these two lines at the end of the file (automatically added, no need to add manually at all):

LoadModule was_ap22_module / usr/IBM/HTTPServer/Plugins/bin/32bits/mod_was_ap22_http.so

WebSpherePluginConfig / usr/IBM/HTTPServer/Plugins/config/webserver1/plugin-cfg.xml

Without the above two lines? Then think about whether it is the version, otherwise the slightest error will easily cause ihs not to start up or no port 80 after startup.

3. Authority issues

It is important to pay special attention to the fact that the mod_was_ap22_http.so and plugin-cfg.xml files must be consistent with the users and groups used at the time of installation, and that these two files need read and execute permissions.

For example, you will sometimes encounter IHS process and port normal, but access reported a 404 error, prompting "URL / microblog/mb/findMblogIdsOrderbyTime.action was not found on this server." If you can't find the problem, when you adjust the owner and permission of these two files correctly, you won't report it wrong.

4. What problems do you need to pay attention to when packing?

IBM packaging tools wsad and ATT are very easy to use, and there are no special settings, basically it works on tomcat, but there is no problem on was. In addition, be sure to set the environment variable, enter the was management console-Resources-jdbc provider-the SQLServer I use, and enter C:/j2sdk/lib/msbase.jar in the classpath.

C:/j2sdk/lib/mssqlserver.jar

C:/j2sdk/lib/msutil.jar

This is done, if you set up data sources and connection pooling here, it is more concise to use. When packing, the settings are generally very flexible, as long as you can, if you want to hit an ear, you can hit a war. When deploying in was, the context root is also very casual, if the fill / representative points directly to your application folder (perhaps your website root directory), of course, you can also point to your application name.

5. Reinstall IHS

Sometimes the IHS is abnormal or there is no port 80 started, so that the application must be added 9080 to be accessed. At this point, you can only check the IHS process with 1-3 processes (normally there are 6 IHS processes), and you can't restart IHS several times. Usually you can choose to reinstall IHS, but you need to generate and propagate plug-ins.

The above is the editor for you to share how to analyze the IHS problem, if you happen to have similar doubts, you might as well refer to the above analysis to understand. If you want to know more about it, you are welcome to follow the industry information channel.

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.