Axis RightFax 8.5 Installationsanleitung Seite 37

  • Herunterladen
  • Zu meinen Handbüchern hinzufügen
  • Drucken
  • Seite
    / 106
  • Inhaltsverzeichnis
  • LESEZEICHEN
  • Bewertet. / 5. Basierend auf Kundenbewertungen
Seitenansicht 36
Copyright © 2001, 2015, Oracle and/or its affiliates. All rights reserved.
web server of all potential web servers. To do this you will need to add properties to inform each web
server of the existence of other web servers. To do this directly in the “glog.properties” file:
1. Back up the existing glog.properties file.
$ cd <otm_install_dir>/glog/config
$ cp glog.properties glog.properties_20130417_2156
2. Edit the “glog.properties” file.
3. Locate the section that looks like this:
!remove glog.scalability.web.topologyMachineURL
glog.scalability.web.topologyMachineURL=<HTTP URL for webserver #1>
and add a property for each Web server:
!remove glog.scalability.web.topologyMachineURL
glog.scalability.web.topologyMachineURL=<HTTP URL for webserver #1>
glog.scalability.web.topologyMachineURL=<HTTP URL for webserver #2>
glog.scalability.web.topologyMachineURL=<HTTP URL for webserver #n>
4. Restart OTM.
Note: In the case where a Web server has more than one URL (e.g. an internal URL and an
external URL), the URL listed should be one that is accessible from the machine whose
“glog.properties" file is being edited.
Alternatively, this can be done by modifying the WEB_CUSTOM property set, setting the
glog.scalability.web.topologyMachineURL property for each web server.
Preventing Double-Login Issue
If a load-balancer is used, the Tomcat configuration file will need to be adjusted to prevent an issue
where a user has to login twice. This can also happen in some reverse proxy configurations. The
problem presents itself as:
The user logs in via the load balancer URL.
After successful login, the user is redirected to another login page, this time with the URL of a
specific web server (not the load balancer).
After the second successful login, the user may use the system, but only by hitting the web
server directly, not through the load balancer.
The solution is to use the load balancer’s information in the Tomcat “server.xml” configuration file.
To do that, follow these steps:
1. Back up the existing “server.xml” file.
$ cd <otm_install_dir>/tomcat/conf
$ cp server.xml server.xml_20130417_2156
2. Edit the “server.xml” file.
3. Locate the <Connector> element and change the proxyName and proxyPort attributes:
Before
<Connector address="localhost" port="8009" protocol="HTTP/1.1"
connectionTimeout="3600000"
proxyName="otmweb.company.com" proxyPort="80"
URIEncoding="UTF-8" />
Seitenansicht 36
1 2 ... 32 33 34 35 36 37 38 39 40 41 42 ... 105 106

Kommentare zu diesen Handbüchern

Keine Kommentare