E1: JAS: How To Redirect An URL To Another Website
(Doc ID 1101426.1)
Last updated on MAY 30, 2017
JD Edwards EnterpriseOne Tools - Version 8.98 and later Information in this document applies to any platform.
1. How To Redirect The Server URL to EntepriseOne Login Web Page
How can a shortened URL be used to redirect users to EnterpriseOne JAS environment? For example: there are some ports setup for JPD900 and JDV900 and web server is E1WEB900 and the URLs should be redirected as follows:
2. How to redirect the Data Browser to Another JAS Instance using HTTP Redirection (Websphere and OAS only)
Some EnterpriseOne installations have a dedicated E1 HTML Server configured to handle large data loads being requested through Data Browser. In such setups, it can be desirable to automatically redirect Data Browser requests to another E1 HTML Server instance. This solution provides the steps to configure this for Oracle Application Server and IBM WebSphere J2EE servers. The solution described below require an Apache-based J2EE application server.
Given that E1 Data Browser requests are handled by the resource in relative path /jde/DataBrowser.mafService, it is possible to setup URL redirection in the HTTP Server such that requests from one web site are handled by another web site. This is achieved by inserting URL redirection settings inside the VirtualHost declaration for the E1 HTML Server contained in httpd.conf.
A benefit of setting up URL redirection at the HTTP Server level is that it does not affect the Data Browser request parameters embedded in the URL. When Data Browser is loaded from an E1 application from the original E1 HTML Server, the request to open the corresponding view can be handled by the other E1 HTML Server because the parameters of the request were not affected by the URL redirection.
The following steps are valid for WebSphere 7.0 and Oracle Application Server 10.1.3.x. It is not applicable to Weblogic 10.3.x because Weblogic's embedded HTTP Server is not Apache-based. Weblogic uses an embedded HTTP server and it does not have the Apache httpd.conf file.
For more details, refer to Apache documentation for mod_alias (Redirect) and mod_rewrite (RewriteRule).
Disclaimer: Information in this document is provided as-is. Any further inquiries regarding Oracle HTTP Server or IBM HTTP Server configuration should be directed to the appropriate product vendor support.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!