Skip to main content
Announcements
Have questions about Qlik Connect? Join us live on April 10th, at 11 AM ET: SIGN UP NOW
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Qlikview Service- Listening Ports

Hi guys,

I want to check services status( running, stopped,..) by NLB , thus i need services listening ports.. How can i get them?

Labels (1)
1 Solution

Accepted Solutions
mls
Former Employee
Former Employee

The QlikView Server Reference manual covers the ports in the "Service by Service" chapter.

For example:

QlikView Server: Listens to QVP: 4747; QVP (tunneling): 4774; Broadcast: 14747; SNMP: 161

QlikView Distribution Service: Listens to HTTP: 4720; SNMP: 4721

QlikView Web Server: Listens to HTTP: 80; HTTP: 4750; SNMP: 4751

QlikView Management Service Listens to HTTP: 4780 (Web); HTTP: 4799 (API); SNMP: 4781

View solution in original post

4 Replies
mls
Former Employee
Former Employee

The QlikView Server Reference manual covers the ports in the "Service by Service" chapter.

For example:

QlikView Server: Listens to QVP: 4747; QVP (tunneling): 4774; Broadcast: 14747; SNMP: 161

QlikView Distribution Service: Listens to HTTP: 4720; SNMP: 4721

QlikView Web Server: Listens to HTTP: 80; HTTP: 4750; SNMP: 4751

QlikView Management Service Listens to HTTP: 4780 (Web); HTTP: 4799 (API); SNMP: 4781

Not applicable
Author

Thank's.

I wanted to ckeck this with netstat -o -n -a, and this is what i got:

For Qlikview Server: TCP     0.0.0.0 :4747     0.0.0.0     Listening --> This means QVP?


For Qlikview web server: TCP     x.y.z.w:57032     x.y.z.w:4747     Listening--> i'm not seeing the port number 4750

I'm a little bit confused

Not applicable
Author

For more details, this is what i didi:

To check QVS: netstat -o -n -a\findstr:4747

25364 is the PID of QVS.


To check QVWS: netstat -o -n -a\findstr:4750

but 4 is not the PID of QVWS but the PID of SYSTEM.

mls
Former Employee
Former Employee

this looks correct.
Some ports are run as a system process and then you will see pid 4 instead of the real pid. This makes it more difficult to be sure what process is actually behind it. To be sure you could stop QVWS momentarily and run netstat again, to verify that it stops listening on that port.