Features

  Configuration

  • Configure 20+ Protocols
  • Cross-Connections of Protocols
  • Groups of Destination Devices
  • Data Transformation
  • View Activity Logs
  • Can run on virtual instance or hardware
  • Configure Network Parameters
  • Manage Logins

  Connections

  • One-to-One Cross Connection
  • Many-to-One Cross Connections
  • One-to-Many Cross Connections
  • Many-to-Many Cross Connections
  • Protocol Pass-Thru
  • External Processing

  Data Transformation

  • Filter Data
  • Convert Data
  • Route Data
  • Template Based Reformatting
  • Protocol Field Mapping
  • Remote Processing

  Interfaces

  • Web Pages Interface
  • Streaming Output Events
  • Wizards can be networked
  • API - Application Program Interface
  • Traffic Metrics Dashboard
  • Big Data (Hadoop) Interface
  • Virtual Keypad


Connectivity Diagrams


One-to-One routing:

Input is a single connection via any of the protocols. Output is a single connection via any of the protocols.




One-to-Many routing:

Input is a single connection via any of the protocols. Output will be routed to multiple connections via any of the protocols.




Many-to-One routing:

Input can be via multiple connections using any of the protocols. Output is consolidated onto a single connection of one protocol.




Many-to-Many routing:

Input can be via multiple connections using any of the protocols. Output will be routed to multiple connections via any of the protocols.




Pass-thru routing:

An Input can simply be passed through without any changes to a similar Output protocol. The output can be split out to another connection for other uses.




External Processing:

The Data Mediation Gateway has the ability to accept input data, then send this data to a waiting process on an external Processing System , then passing results back for routing. This allows custom processing to occur if/when necessary.


Optional Processing Gateway Interface (PGI)
One of the mediation options that is available is the ability to accept input data, then send this data to a waiting process on an external Processing System. This option would be using the Processing Gateway Interface (PGI). The Processing System can be any machine defined by an IP Address and Port. The communication would be via a tcp socket connection. The Processing System would have a process waiting for a connection on this Port. The process will receive, then process this data any way it wants. The response would then be sent back, to be further processed by the Wizard, according to its meditation and routing rules.
This connection to the Processing System can be Synchronous or Asynchronous.
Synchronous - The Wizard connects to the Processing System and sends data, then waits on this same tcp connection until a response comes back to be further processed. A timeout will be configured for this PGI connection.
Asynchronous - The Wizard connects to the Processing System and sends data. After receiving data, the connection drops. The Processing System, upon its internal logic can process and send the response data back at any time via any of the input protocols. (E.G. posted form, tcp connection,..etc). Some applications may not require response data to be sent back to the Wizard.