Over a million developers have joined DZone.

How to Change the Listening Port for the Axway/Vordel API Server

DZone's Guide to

How to Change the Listening Port for the Axway/Vordel API Server

· Integration Zone
Free Resource

Discover how Microservices are a type of software architecture where large applications are made up of small, self-contained units working together through APIs that are not dependent on a specific language. Brought to you in partnership with AppDynamics.

A common question about the Axway/Vordel API Server is "How do you change its listening port?". The key to answering this question is to understand what are the "Services" groups under Policy Studio for the API Server:

What are the "Services" groups?

If you look under "Listeners" in Policy Studio, you will see the various "Services" groups. In the screenshot below we see "Default Services", "OAuth 2.0 Services" and "Sample Services". These are a way to group different paths under different ports. So, for example, the sample services are only available under the port which is defined under "Sample Services". And, the sample services can be disabled en masse, without affecting other listeners. You could also setup a new Services group, call it "SSL Only", then put an SSL listener in that group. Then, paths exposed under "SSL Only" could only be accessed using SSL.

Parameterized Ports
If you look at the circled item in the screenshot above, you see that the port number is not visible. Instead, we see an environmentalized parameter. So where is the port number? Notice that the variable starts with "env". This is a clue. It is in the Environmental Properties file.

So, if you look under /conf for the particular API Server instance, you can find the envSettings.props file, which is where this variable is defined. Here we see it below:

Notice the highlighted text. This is where the port is defined, and it's port 8080 at the moment. You can change this value here. And, in fact, you can add other variables here and then reference them in policies, providing environmental customization of the API Server [e.g. on another machine, we may use 8888 instead].

Discover the six challenges and best practices in managing microservice performance, brought to you in partnership with AppDynamics.


Published at DZone with permission of Mark O'Neill, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.


Dev Resources & Solutions Straight to Your Inbox

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.


{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}