I'll go one better and say the best way is to open up a command prompt and type:

xppversion

This will output the XPP version and also validate that the XPP environment (as well as the %PATH% variable) are set properly for a actual command to work.

Steve,

But wouldn't that also work on a machine that is installed as an XPP client?
(while the software is really installed on anther machine)

You are correct, the command would also work on a client. The XYV_ADVP_NODE on the server will point to the XPP server, so the client version of the variable will show the real name of the server. Perhaps your way is better. I just took the question to mean, is XPP installed on a machine at all, and not specifically am I on a XPP server or XPP client.

Hi Steve,

I also found the Env variable with the needed value. Thanks to you as well. Can you point me to the XPP server architectural documentation? I need to create at least two optional performance benchmarks.

Are we talking Windows or Linux here?

Not that it really matters as the choices are basically the same:
1. Central server with client machines.
Client machines are machines that run the XPP server locally but get all the executables over the network from the server. Client machines are typically used as workstations while the server does all the background services

2. Central server acting as terminal server
In a windows environment that would mean using RDP connections for your workstations. Everything is run on the central machine: foreground and background tasks

You might want to describe a little your working environment (how many workstations, servers, what industry you are working in, will you use webservices or the REST API or will you mainly use autoproc hot folders). The more we know about your environment the better advice we can give you regarding your setup.

Are we talking Windows or Linux here?

Not that it really matters as the choices are basically the same:
1. Central server with client machines.
Client machines are machines that run the XPP server locally but get all the executables over the network from the server. Client machines are typically used as workstations while the server does all the background services

2. Central server acting as terminal server
In a windows environment that would mean using RDP connections for your workstations. Everything is run on the central machine: foreground and background tasks

You might want to describe a little your working environment (how many workstations, servers, what industry you are working in, will you use webservices or the REST API or will you mainly use autoproc hot folders). The more we know about your environment the better advice we can give you regarding your setup.