Download PDF:
Eliminating Port Numbers in E1 JAS/HTTP
Executive Summary
To meet high availability needs and to optimize performance in an ERP/Websphere environment, J.D. Edwards recommends creating multiple Java Application Server (JAS) instances in WebSphere Application Server (WAS). Also, in order to address the Path Code caching issue (Refer to “Implement a Single Path Code per Virtual Machine” appendix in JAS Install Guide), it is recommended that multiple JAS instances be created. To support these needs, an elaborate addressing structure must be created. The choices for creating this addressing structure are either port-based or name-based addresses. This paper presents name-based addressing as an alternative to port-based addressing.
Abstract
The purpose of this paper is to describe the methods used to create an EnterpriseOne Web-based system without the use of port numbers.
The use of aliasing and Virtual Hosting techniques in DNS, IBM HTTP Server (Apache), and WebSphere 4 allows JAS instances to be referenced by name instead of by TCP Port Number. DNS mappings, Apache VirtualHosts, and WAS Host Aliases are created to enable this solution.
You create multiple HTTP servers by the use of Apache Named Virtual Hosts. Each named Virtual Host is on the same physical web server but appears to be a different URL and can have a different setting.
Total Pages - 10
