Re: HTTP listening ports and URL questions

I have asked this question before and do not remember an answer that dealt with the question.

Why not use the DNS on your iSeries? So, for example, an iSeries named Thor might have a section named ThorAR and resolve to 1.0.0.1:461 and another section named ThorAP could resolve to 1.0.0.1:6060. Then comes the fun of creating a logical naming scheme, but that gets to be fun.

Then your users and programmers do not need to concern themselves with port numbers, etc. That becomes an exercise for whomever handles the DNS.

Since no one suggested this solution there must be a reason not to do it. And yes, I understand I will undoubtedly be mortified when I read the answer. But in this case my curiosity outweighs my fear of humiliation.


On 11/2/2016 7:08 AM, Steinmetz, Paul wrote:

I have some questions related to HTTP listening ports and URLs.
I have a current instance listening on port 443, all IPS.

I have a new app going live that we prefer to listen on port 443. It can listen on a different port, but I've been told that if 443 is not used, then we must include the port number in the URL.
We would like to have the new app keep the same URL as the old current app, which is listening on port 80.

So my issue is that I will have two http apps listening on port 443.
Options.
1) Create one http instance for both, using virtual host. The problem with this option is that when one app needs to be shutdown, we don't wish to shut down the other app.
2) Have both apps listen on 443, two http instances, different IPs. I'm leaning towards this solution.
3) Are there others?



Thank You

_____

Paul Steinmetz

IBM i Systems Administrator



Pencor Services, Inc.

462 Delaware Ave

Palmerton Pa 18071



610-826-9117 work

610-826-9188 fax

610-349-0913 cell

610-377-6012 home



psteinmetz@xxxxxxxxxx<mailto:psteinmetz@xxxxxxxxxx>

http://www.pencor.com/