Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The configuration values can be stored for either the invidual individual gateway server itself, or it can be inherited (and shared between multiple gateway instances) by placing this configuration in a server entry which the individual gateways extends from.

...

  • gateway
    Gateway global settings, such as number of threads, max POST size, cluster IDs and accesslog access log configuration. 
  • session
    Session related configuration, such as session resolvers, cookie names, scripts etc. 
  • listen
    Listener configuration, TCP port numbers, SSL settings and protocols - allows you to setup set up listeners on vairous various ports and protocols. 
  • locations
    Locations and their settings - you can potentially have hundreds or even thousands of locations - bear in mind though that each location is processed sequentially and its conditions are checked for a match - so there is a (low, but existing) performance cost of chaining hundreds of checks - especially if conditions include regular expressions and not simple string matching. Consider nesting locations to reduce the number of check required and group locations e.g. by virual virtual server.
  • destinations
    Contains the destination clusters of target servers that requests can be proxied to. 
  • pipelines
    Pipelines and tasks, which enable ESB or API Gateway functionality.
  • cannedreplies
    Define "canned" replies, reusable from within various locations.
  • ipranges
    Create IP ranges, which contain IP ranges defined locally, loaded from files, or from Online IP Reputation Databases.

...