Keeping Track With The Catalog

Keeping track of large numbers of things can be difficult. By its nature, ZXTM will be expected to deal with many back-end nodes, services, TrafficScript™ rules and SSL certificates. ZXTM makes your life easy by keeping everything in the Catalog, a ordered collection of all the things that it manages.

Quick Links

How can I reuse TrafficScript™ rules rather than duplicate them? 

When you create a virtual server, which corresponds to a service you are managing, e.g. HTTP on port 80, you can associate one or more TrafficScript™ rules with it. If your TrafficScript™ rules are generic, e.g. "if the source IP address is A.B.C.D, send the request to this pool of servers", you don't need to duplicate this rule for each virtual server that uses it. Instead you can define the one rule in the Catalog and associate the same rule with each virtual server. This also means that if you change the rule, it will take effect across all associated virtual servers.

How can I find out which pools of nodes are used by which TrafficScript™ rules? 

A pool is a group of back-end servers or nodes which are all running a particular clustered service (such as an email server cluster). Traffic is accepted and processed by a virtual server on ZXTM, then passed on to a pool. The TrafficScript™ rules which you define and associate with a virtual server may send traffic to a different pool of nodes depending on specific information (e.g. the source IP address). The Catalog makes your life easy by examining the TrafficScript™ rules associated with a virtual server and telling you which pools will be used.

How can I manage my SSL private and public keys? 

If you are decrypting and / or re-encrypting traffic on ZXTM, you may end up with several sets of private and public keys. The Catalog makes it easy to import your SSL keys and can tell you which virtual servers are using which sets of keys.

© Zeus Technology Ltd