I have changed the port that the DX Netops Performance Center console/sso servers run on but I still see the default ports in the process listing

book

Article ID: 196915

calendar_today

Updated On:

Products

CA Infrastructure Management CA Performance Management - Usage and Administration DX NetOps

Issue/Introduction

I have changed the port that the DX Netops Performance Center console/sso servers run on but I still see the default ports in the process listing.

The console and single sign on (sso) are accessible on the ports I configured and login and other functions are working properly.

Environment

Release : 3.7

Component : IM Reporting / Admin / Configuration

Resolution


The other configuration steps you have done specify the port that the PC/sso services listen on and those ports in the process listing for the console and sso can be ignored.

The following should show the ports jetty is listening on for each of the four services:

netstat -npl | grep "$(ps -ef | awk '/[j]etty\.http/ {print $2}')"

Example:

# netstat -npl | grep "$(ps -ef | awk '/[j]etty\.http/ {print $2}')"
tcp 0 0 127.0.0.1:32000 0.0.0.0:* LISTEN 141035/java
tcp 0 0 127.0.0.1:32001 0.0.0.0:* LISTEN 40510/java
tcp 0 0 127.0.0.1:32002 0.0.0.0:* LISTEN 141036/java
tcp 0 0 127.0.0.1:32003 0.0.0.0:* LISTEN 40652/java
tcp6 0 0 :::8182 :::* LISTEN 40510/java       <------PC console
tcp6 0 0 :::8281 :::* LISTEN 141035/java
tcp6 0 0 :::8382 :::* LISTEN 40652/java       <------SSO
tcp6 0 0 :::8481 :::* LISTEN 141036/java


The example system is configured for https with the console on 8182 and sso on 8382 and is working properly.


Additional Information


Note that you will see some entries in the 3200x range, these are for communicating between the wrapper process and jetty.