It is customary for users at my organization to access web services simply by entering the name of the service they want using a host name in their browser. (ie. http://imanager or http://eguide) The access gateway in Access Manager requires that you use fully qualified names when accessing resources and will give you a 403 FORBIDDEN error message if you don't use the FQDN. I am running AM 3.0.4 and initially was using the following article as a guide (and you should continue to do so if you're using AM 3.0.2 or less)... Redirecting the Access Gateway to the Full Domain Name
However, according to the AM documentation here... http://www.novell.com/documentation/novellaccessmanager/adminguide/index.html?page=/documentation/novellaccessmanager/adminguide/data/b5512be.html
...the page for error messages has been transitioned from the error.jsp to an HTML template in AM 3.0.3 and above. I will describe how I modified the template to properly redirect users of host name to the FQDN on the gateway itself.
This configuration assumes that you have only one domain suffix that your access gateway is handling since we hard code the config in the HTML (not the best way but certainly the easiest way to do it). You'll need to locate and edit the error page template on each LAG where you want to enable this functionality.
Make a backup of...
mystatusCode = "<ERROR_STATUS>";
myhost = "";
if (document.URL.indexOf("mydomain.com") == -1)
myhost = "http://" + location.host + ".mydomain.com/";
Save the file and then restart the AM Virtualization Controller to activate the change.
Test by accessing a proxied web site with just the host name. The code above should detect that the error coming back from the LAG is a 403 Forbidden error and attempt to access the site again using the fully qualified domain name.
Also, I would suggest reading the documentation link above about how the templates are managed during a product upgrade.
Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).
It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.