Axis RightFax 8.5 Guía de instalación Pagina 36

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 106
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 35
Copyright © 2001, 2015, Oracle and/or its affiliates. All rights reserved.
Installing Multiple Web Servers
Multiple web servers can be utilized to increase the performance of Oracle Transportation
Management. Generally, with more web servers you can maintain more simultaneous user connections
into the Oracle Transportation Management server’s web interface. You may also see increased
performance in integration, since incoming integration files are posted to a servlet on the web server
and are passed back to the application server.
Load Balancer
We recommend using a hardware load balancer to spread the incoming requests among multiple web
servers as efficiently as possible. The load balancer should be configured so that once a user logs into
a given web server, that same web server is always given back to that user within some configurable
time-period. After that time has elapsed, the web server given back to the user can once again be
determined by current load, after which the server returned should once again be fixed for a given
time-period. This is commonly referred to as a persistent or sticky session, and is usually
accomplished by inserting a cookie or other header into the request. It can also be done by IP
address, though this is a less desirable alternative. Exact configurations and options depend on the
load balancer in use.
Some load balancers can also be configured to dynamically remove a web server from the rotation if it
is down for whatever reason, and dynamically add it back in when it recovers. This is usually done by
having the load balancer attempt to connect to a specific URL on the web server every N seconds or
minutes, and there is a servlet provided to handle this specifically. Configure your load balancer to
load the glog.webserver.test.TestServlet servlet, e.g.:
http://www.company.com/GC3/glog.webserver.test.TestServlet
If the servlet loads properly and returns a response code of 200, then everything is fine. If any other
response code is given, or if a connection cannot be established, then that should be considered an
error condition and the server should be dropped out of rotation. Test out the URL manually with a
browser on a known-working system before using it to configure the load balancer; it should return
the word “OK” on the screen.
Diagnostic Screens
Oracle Transportation Management supports a number of diagnostic pages and processes that display
configuration information and monitor web-tier system health, including:
Log browsing
Properties management
Cache monitoring
JMS monitoring
Scalability balancing
If the installation is customized to support application-tier scalability
3
, diagnostic screens are aware of
all web servers. That is, from a single browser request, the screens retrieve data across all web
servers.
In an installation with multiple web servers but a single application server one without application-
tier scalability activated the diagnostic screens can still be configured to retrieve and report on data
across all web servers. To accomplish this, the installation must inform the application server and each
3
See the Application Scalability Guide for more information on this configuration.
Vista de pagina 35
1 2 ... 31 32 33 34 35 36 37 38 39 40 41 ... 105 106

Comentarios a estos manuales

Sin comentarios