The TCP/IP Format

When the configuration settings Allow Multiple Connections and Send Response are enabled, the collector expects UDRs as replies from the APL agent. To support this, your internal format must extend the built-in TCPIPUDR class, and your mappings must reflect this structure.

See https://infozone.atlassian.net/wiki/spaces/MD92/pages/680427779 for a different example.

Example - APL structure to extend the TCP/IP format

The following example demonstrates the required structure when both Allow Multiple Connections and Send Response are enabled. It shows how to extend your internal format with the built-in TCP/IP format (TCPIPUDR), and how to set up the mapping and decoder.

external my_ext sequential {
  // field definitions
  int type : static_size(1);
  ascii Anum : static_size(8);
  ascii Bnum : terminated_by(0xA);
};


internal TCP_Int : 
   extends_class( "com.digitalroute.wfc.tcpipcoll.TCPIPUDR" ) {
};


in_map TCP_InMap :
    external( my_ext ),
    internal( TCP_Int ),
    target_internal( my_TCP_TI ) {
    automatic;
};


decoder myDecoder : in_map( TCP_InMap );