Download Adobe PDF - Lymeware Corporation

Transcript
IAgent3 User’s Guide
Administration
CHAPTER 26 – IAGENT3 MAINTENANCE ISSUES
Log Rolling
The output log files (iagent.log, iagent.err, and iagent.alert) and transaction log files
(*_trans.log) can be safely "rolled" by performing the following actions:
1. Move all the log files to a new location/name with the mv command,
2. Send a SIGHUP to the IAgent3 process or process group identified by the iagent.pid
file.
This last step will signal all IAgent3 processes to close then re-open all the log files and will in
effect, complete the prior move command. It is recommended that a cron job performing the
above steps be scheduled on a daily basis to insure minimal log size and allow log archiving.
Log File Details
The IAgent3 system generates a single transaction log file per major process. These process
specific transaction logs (one per major process) log the final status of a transaction (either inbound,
to the server(s) or outbound, from the client(s). These logs are called: client_trans.log,
receipt_trans.log, server_trans.log, and hipri_trans.log. The log files consist
of a transaction per line in the following format:
date time: message type: ISA segment of the message: source or destination IP address and
port: message priority: and numeric transaction status
The date time is the time the entry was logged, in local time.
The message type may be any of the following:
Message Type
UNSUPPORTED
BASIC_EDI
INTEGRITY_EDI
SIGNED_EDI
BASIC_RECEIPT
INTEGRITY_RECEIPT
SIGNED_RECEIPT
IA_STATUS
Type Number
0
1
2
3
4
5
6
9
Table 9 Transaction Log Message Type Numbers
The ISA segment of the message should be the first 105 bytes of a raw EDI or Receipt
message. For IA Status messages this field is populated with the status bit string in four
hexadecimal numbers.
The source or destination IP address and port will reflect the other side of the exchange. In
the server(s) it should be the transaction’s source IP address. In clients(s) it should reflect
the destination IP address of the transaction.
November 2004
Page 72
version 3.1.1