Changing JAS URL

[Starrjos]

Ok, I am feeling pretty stupid these days as I seem to be posting quite a bit for help.......but that is what ya'll are here for right?

OK, we finally have nearly everything working with our new JAS install and now I would like to change the http://server.company.com:81/jde/owhtml to an "alias" that doesn't have the port information or the long xxx.xxx.com stuff. Is this possible and if so, can someone guide me a white paper or web location with the steps to setting this up......

As always, thanks in advance!

 

[DeRay_Scholz]

There used to be a tech document titled "Proxy Server Configuration" which outlines the steps to do this. Maybe someone out there has it and can post it here.

DeRay Scholz
JDE CNC

 

[brother_of_karamazov]

See the attachment on this post and also this attachment:


http://www.jdelist.com/ubb/download.php?Number=93765

 

[morglum666]

If your feeling really lazy, google for "META REFRESH". Its an HTML command that will re-direct a browser automagically.
so you put in Http://servername.domain.com

index.html
default.htm (as appropriate, etc)
and use this command to re-direct to your real url.

 

[Starrjos]

Thanks to All.....I will take a look and see if any of these will help me out!

 

[Starrjos]

Ok, I applied the setups (as best I could) to my install.....just for PY as I don't plan to install any other environments for a few months. Having said this, I installed WAS50 and the document you refered me to looks like it is for WAS4.X. Anyway, I was able to relate most of the information other than the confusion I have with the ports. I am not a web expert as you can see....having said this, when I installed IBMHttp I believe it was installed on port 80 (?) and then my JAS install to port 81 (followed instructions provided by JDE). When I set up the alias in WebSphere, I used port 81. Is this the correct port to use? Second, I was not able to find Server Groups in WebSphere Admin. Has this been changed or replaced? Lastly, when I enter in http://jdeseapd.company.com I get the IBM Http Server page instead of the OW login. Any ideas here?

Thanks for you help so far......

 

[brother_of_karamazov]

Change the port for the WAS VirtualHost to port 80

Ex: jdeseapd.company.com:80


There are three major pieces to changing to name-based (as opposed to port-based) urls.

1- DNS entry
2- Apache Virtual Host in httpd.conf
3- WebSphere Virtual Host


Get all three right and you ditch port numbers in urls. Once you get this done you can fool with document root to ditch the four mile long path in the url.

 

[Starrjos]

When you say change the port for the WAS Virtual host....are you refering to the httpd.conf? I had everything set to use port 80 in httpd.conf and in the alias setup in WS ADmin but that didn't work. I got an error telling me the document was not found so I set everything back to 81. Currently if I type in http://jdeseapy:81 I will get the JDE login screen. If I type in http://jdeseapy (without the port) I get the IBM Http Server. I know I am close.....

Thanks for you help so far!

 

[brother_of_karamazov]

The WAS Virtual Host alias needs to have two parts.

1- The dns name you specifed in DNS (or hosts)
2- The port number that matches the port number you defined in httpd.conf (preferably 80)

Remove any default alias you have in WAS virtual hosts that says *:80

Post the relevant sections of your httpd.conf file. Also your plugin-cfg.xml file.



[ QUOTE ]
When you say change the port for the WAS Virtual host....are you refering to the httpd.conf? I had everything set to use port 80 in httpd.conf and in the alias setup in WS ADmin but that didn't work. I got an error telling me the document was not found so I set everything back to 81. Currently if I type in http://jdeseapy:81 I will get the JDE login screen. If I type in http://jdeseapy (without the port) I get the IBM Http Server. I know I am close.....

Thanks for you help so far!

[/ QUOTE ]

 

[brother_of_karamazov]

I may have forgotten to mention that in doing all this reconfiguration that you should follow best practices for configuring most anything. That includes stopping and restarting services, etc. when appropriate.

 

[AS400Guru]

I also get the same error. The login page is displayed only if we enter the port # 81.
Http://webdv - Does not work
Http://webdv:81 - Works.
We have added an entry in the DNS resolving the webdv to the JAS server and have made the changes relevant changes to the httpd.conf file.
Are we missing anything?.

Thanks for the help.

 

[brother_of_karamazov]

What does your httpd.conf Listen directive say?

It should say something like Listen *:80 or listen 10.0.0.10:80

Your web browser assumes a default port of 80. If your listen directive is set otherwise it is necessary to specify that port number in the url.



[ QUOTE ]
I also get the same error. The login page is displayed only if we enter the port # 81.
Http://webdv - Does not work
Http://webdv:81 - Works.
We have added an entry in the DNS resolving the webdv to the JAS server and have made the changes relevant changes to the httpd.conf file.
Are we missing anything?.

Thanks for the help.

[/ QUOTE ]

 

[gcarmody]

Don't know if this is any help:

We use http redirects to avoid using a port number. For instance, on my development (ISDEV) system I have installed several JAS instances, each listen on their own port, defined at install time, or by modifying the VH later DV(81), PY(82), ES(83), TR(84) TX(85) BI(91).

I run the APACHE server on port 80 which has aliases to redirect the request. So my users enter:

//isdev/dv
//isdev/py
//isdev/es

and so on..

Apache redirects them to the appropriate port. Takes about 2 minutes to set up. See screen print of the http configuration attached.

 

[AS400Guru]

I have Listen*:81 and also IP:81 in the httpd.conf file.

Thanks.

 

[AS400Guru]

We are running the http server on port 81. It is my understanding that if it was configured on port 80, we would not have to worry about putting the port # in the url.
Can the redirect still work if our http server is running on port #81.

Thanks.

 

[brother_of_karamazov]

That is why it is only working on port 81. Again, the web browser assumes port 80 unless specified otherwise. If you wish to eliminate port numbers you have to specify a Listen directive for port 80 in httpd.conf.

Put Listen ipaddress:80 where ipaddress is your server's ip address.



[ QUOTE ]
I have Listen*:81 and also IP:81 in the httpd.conf file.

Thanks.

[/ QUOTE ]

 

[brother_of_karamazov]

If you use the default port and virtual servers you don't need to do redirects. Redirects are not the appropriate solution for name-based virtual servers with port number-free urls.



[ QUOTE ]
We are running the http server on port 81. It is my understanding that if it was configured on port 80, we would not have to worry about putting the port # in the url.
Can the redirect still work if our http server is running on port #81.

Thanks.

[/ QUOTE ]

 

[AS400Guru]

I put a listen *:80 in the httpd.conf file and i get a 403 forbidden message. I ran the chmod -R 755 installedApps too.

However as you mentioned that redirects are not a good strategy for name based url, what would you suggest/advise in order to achieve a url without the port #.
The reason being eventually we plan to have seperate instances for each env on diff ports and we dont want our end users to enter the url along with the port #.

Appreciate your help.

 

[brother_of_karamazov]

Take a look at this paper I wrote when I was working for JD Edwards.



[ QUOTE ]
I put a listen *:80 in the httpd.conf file and i get a 403 forbidden message. I ran the chmod -R 755 installedApps too.

However as you mentioned that redirects are not a good strategy for name based url, what would you suggest/advise in order to achieve a url without the port #.
The reason being eventually we plan to have seperate instances for each env on diff ports and we dont want our end users to enter the url along with the port #.

Appreciate your help.

[/ QUOTE ]

 

[cdawes]

On the JAS installs for WAS 5.X you don't have the opportunity to specify the Virtual Hosts, Application Server names, etc. The installer also doesn't let you install on port 80. What's the easiest way to do the config for WAS 5.0? Obtain the WAR file? Modify the configs after the fact? Manual add the AS, EA and VH?

Thanks,

Colin