After the File Field Description has been created, use the Journal Monitors tab in the Configuration Tool to define the journal monitors that will collect the performance data from each file in the journal.
You can click the Create button to create a new Journal Monitor Group or click Edit to add new monitors to an existing Journal Monitor Group.
Figure 20: Define Journal Monitors
In the Journal Monitor Group, click the Add Monitor button to create an entry for a performance data file journal.
Figure 21: Create Performance Data File Journal
Enter the Journal Name and Journal Library of the journal that was created in the section Step 3: Start Journaling the Collection Services Data above.
Specify the Object Type as *FILE.
Enter the Object Name and Object Library of the Collection Services table that you have added to the Journal, for example QAPMDISK in library QPFRDATA. These need to match the names defined in.
Set the Frequency for checking the journal for new data.
Note: It is recommended that this is the same as the interval that was chosen for the data collection interval.
Assign the File Field Description created in section Step 4: Create the File Field Descriptions
above to this journal entry.
Leave the Entry Code empty.
Set the entry Type field to PT. This ensures that Ironstream only collects records that are being added to the file (not any housekeeping entries).
Note: On some machines the Journal records are created in the journal with a Type of PX not PT. If no journal records are being sent to the destination, after all the steps in this section have been taken, then check whether the records are being added to the Journal with a Type of PX instead of PT. If so, change the Type field to PX and re-distribute the Journal Monitor.
Fill in the Assigned systems field, at the top, to assign the completed Journal Monitor Group to one or more systems. If you have the same performance collection files configured on multiple systems that are running the same IBM i OS version and PTF level, you can assign the same group to multiple IBM i LPARs.
Note: Because different OS versions or even PTF levels may have different field layouts for performance data files, you may need to create multiple Journal Monitor Groups with different File Field Descriptions for different versions. In this case it is recommended that the File Field Definition groups should be named using the performance data file name followed by either the LPAR name or IBM i OS version number, for example QAPMDISK_BLUEBOX or QAPMDISK_V7R2.
Click on the Add Monitor button, to repeat this step for each performance data file that you want to collect data from in this Journal Monitor Group.
Click Save button to save the Journal Monitor Group definition.
Note: Make sure the steps in the section Age Limit for Journal Monitoring have been taken for each LPAR before distributing the Journal Monitoring Group.
Click the Distribute button to send the Journal Monitor Group 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 System affected by the changes to ensure that the Proxy Server is using the new configuration details when processing journal entries.
Your chosen Collection Services data should now start being sent by the Agent on the IBM i LPAR to the Proxy Server.