...
Item | Description | |||||
---|---|---|---|---|---|---|
Protocol | Enter the protocol type that you want the agent to use: Either TCP or UDP. For further information see Limitations - GTP' Transported Over TCP in 9.3637.5 GTP' Agent MZSH Commands, Events and Limitations. | |||||
Port | Enter the port through which the agent should await incoming data packages. This port must be located on the host where the EC is running. Default value is 3386.
| |||||
Accept any | Select this check box if you want the agent to accept any source endpoint (IP-address:port). | |||||
GSN IP Address | The IP addresses or hostnames of the GSN nodes that provide the data. | |||||
Server Port | Enter the server port number for each node. The agent will detect GGSN source port changes via the Node Alive Request or Echo Request messages. If a change is detected, it is is registered in the System Log. The agent's internal configuration is updated. |
...
The Miscellaneous tab includes collected format and storage settings of the data that is collected by the agent.
Item | Description | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Format | Must match the D | ||||||||||
Perform Format Version Check | When checked, the | ||||||||||
Format Version | Must match the D | ||||||||||
Directory | Enter either the relative pathname to the home directory of the user account, or an absolute pathname of the target directory in the file system on the local host, where the intermediate data for the collection is stored. The intermediate data includes:
| ||||||||||
Acknowledgement from APL | Check to enable acknowledgement from the APL module that follows the GTP' agent. This way the GTP' agent will expect a feedback route from the APL module, as well. No GTP packets will be acknowledged before all the data that is emitted into the workflow is routed back to the collector. Controlling acknowledgement from APL enables you to make sure that data is transmitted complete. Clear this check box if you want the agent to acknowledge incoming packets before any data is routed into the workflow. | ||||||||||
No Private Extension | Check to remove the private extension from any of the agent's output messages. | ||||||||||
Use seq num of Cancel/Release req | Check to change the type of the sequence numbers that are populated in a |
Advanced Tab
The GTP' agent configuration dialog - Advanced tab
...
Item | Description |
---|---|
Decoder | Click Browse and select a pre-defined decoder. These decoders are defined in the Ultra Format Editor, and are named according to the following syntax:
The option MZ Format Tagged UDRs indicate that the expected UDRs are stored in the the specific format. Select this option to make the Tagged UDR Type list accessible for configuration. |
Tagged UDR Type | Click Browse and select a pre-defined Tagged UDR Type. These UDR types are stored in the Ultra and Code servers. The naming format is:
If the decoder is intended to reprocess UDRs of an internal format, the Decoder MZ format tagged UDRs has to be selected enabling this list. Once enabled, the internal format must be selected. |
Full Decode | Select this check box to enable full decoding of the UDR, before it enters the workflow. This, in turn, might reduce performance rate. Leave this check box empty to minimize decoding work in the agent. By leaving this check-box empty, you postpone decoding, and discovery of corrupt data to a later phase in the workflow. |
Scroll ignore | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||