Follow the steps to collect the IFS Log Files that are being journaled with the Configuration Tool:
- Create a Journal Monitor.
Object Type as *STMF Type.
Note: The Raw option will be checked automatically when you choose *STMF.
In the Path name field, specify the path to the IFS log(s) you want to collect. The restrictions are as follow:
- It MUST start with a forward slash ‘/’.
It MUST include the full path to the folder where the logs are stored.
Note: Do not use wildcards in the folder text.
- The name of the log file can include wildcards. Use a ‘*’ to collect all the log files in the folder, or add a wildcard to the name to collect some of the log files in the folder.
For example, you can use: /home/users/*, /home/users/log*, or /home/users/log.text.
- Fill in the rest of the Journal Monitor details as required. For more details about other fields, see Choose Journals to Monitor section.
- Fill in the Assigned systems field to assign the completed Journal Monitor Group to one or more IBM i LPARs.
- Click the Save button.
- Click the Distribute button for the new Journal Monitor Group, to send the details to the Ironstream Agent for IBM i for the Assigned systems.
- On the Systems tab, restart each System that is in the Assigned systems list of the newly created Journal Monitor Group.
Note: After creating or changing a journal monitor, you MUST restart each Source affected by the changes to ensure that Hub is using the new configuration details when processing journal entries.
Only IFS Log records from files that meet the Journal Monitor options are sent to Hub. These records are always sent as 'raw' unformatted records. Then, Hub Server processes these raw records and creates JSON formatted records to send them to the target.
For more details of the fields, see Table: Fields of a Journal Monitor definition.