Troubleshoot WebSphere Application Server port conflicts with Profile Port checker

Introduction

This problem may occur when the customer is using WebSphere application server, one server on the same physical host is functioning correctly, and the other server does not start properly, possibly due to multiple Server port conflicts. Profile Port Checker is a free tool provided by IBM to provide service for conflict port detection. This article will detail the installation process of the profile port Checker, as well as the capabilities of each command, and use the example to show how to use the profile port Checker to detect port conflicts in the actual environment.

IBM serviceability Tools Overview

In addition to providing high-quality products, in order to further improve the product's customer experience, and to provide better customer support services, IBM also launched a series of tools to facilitate the simple monitoring and rapid resolution of customers in the use of IBM products encountered in the process of the various problems. These tools are collectively known as IBM serviceability tools that provide technical support for the product from all angles, such as IBM Visual Configuration Explorer (VCE) [1], which focuses on the configuration aspects of the product, IBM Databa Se Connection Pool Analyzer for WebSphere Application Server [2] focused on Java in the WebSphere Application server product? Database Connectivity (JDBC) connection pools related issues, and the profile Port Checker we're going to look at is focused on installing WebSphere application Server Products Problem with port conflicts.

Part of the IBM Serviceability tool is integrated into the IBM Support Assistant [3] products as a plug-in, and part of it needs to be downloaded, installed, and run independently. As of the IBM Support Assistant 4.1 version, profile Port Checker has not been integrated into the IBM Support Assistant tool, but runs independently.

In this article, we will demonstrate the use of profile port Checker on an experimental host that contains multiple WebSphere application server profiles, showing how to easily get multiple application server-occupied ports on multiple profiles List and locate the ports that conflict between the application servers.

Installation Preparation

Before starting an instance demo, you first need to download profile Port Checker and see what it does.

Download Profile Port Checker

Profile Port Checker is a free IBM serviceability tool that allows you to download the profile Port Checker package in reference resources [4]. After decompression, you can run it directly from the command line without installing.

Applicable situation

Profile Port Checker is suitable for the same physical host, contains profiles for multiple WebSphere application servers, and multiple application server scenarios. This tool scans the physical host for the ports used by each application server on each WebSphere application Server profile and consolidates the reporting information. In addition to listing each occupied port in detail in the report, if a conflict is found, the conflicting application server and the conflicting port are also indicated.

Profile Port Checker searches the installation path for all WebSphere application Server profiles on the machine, primarily based on profile registration files, such as on Windows systems, located in c:\w Indows\.nifregistry. Alternatively, the path information for this file can be found in the Nifregistry.properties file in the installation directory of WebSphere application Server, for example, on a Windows system that is located in C:\Program files \ibm\websphere\appserver7\properties\nifregistry.properties.

The profile Port Checker applies as shown in table 1:

The following two points need to be noted:

In addition to detecting the stand-alone installed WebSphere Application Server, Profile Port Checker can detect the profile of WebSphere Application server that is installed with other products, such as Bm? The Rational? Software Delivery the profile corresponding to the WebSphere application Server installed at Platform installation, which is typically located under the Rational product installation directory Runtimes folder.

Profile Port Checker can be used to scan and detect profiles for different versions of WebSphere Application server on the same machine, but currently does not support simultaneous scanning of WebSphere application server V 8.0 and other versions of WebSphere application Server corresponding to the profile. For example, both the WebSphere Application Server V6.1,websphere Application Server V7.0 and the WebSphere Application Server V8.0 are installed on the experimental machine. If we run Profile Port Checker on the installation directory of the WebSphere Application Server V8.0, only the profile of the WebSphere Application server V8.0 can be scanned, not Can scan profiles for WebSphere Application Server V6.1 and WebSphere Application Server V7.0. As shown in Figure 1, figure 1 intercepts the profile Port Checker Scan report, please refer to the download resource [1] for the complete scan report.

Figure 1. Profile Port Checker Scan was V8 report

If you run profile Port Checker on the installation directory of the WebSphere Application Server V7.0 or on the WebSphere application Server V6.1, you can scan only the WebSphere Application Server V7.0 and WebSphere Application Server V6.1 profile, and cannot scan out and WebSphere Application Server V8.0 E. As shown in Figure 2, Figure 2 intercepts the profile Port Checker Scan report, please refer to the download resource [2] for the complete scan report.

Figure 2. Profile Port Checker Scan was V7.0 and was V6.1 reports