Loading the ENU sample data

ENU Sample data is installed as part of the IBM® Predictive Maintenance and Quality server artifact installation. The data covers examples for substations, distribution transformers, and poles and cables.

The sample data is provided in different languages. If you want to change the language of the data, you must ensure that the Predictive Maintenance and Quality data store content is deleted, and that you restart your brokers.

Tip: You can verify that the data was loaded by using commands to check the Predictive Maintenance and Quality queues. You can check the queues by running the following commands: 
runmqsc pmqmanager
Display q(PMQ.*) WHERE(CURDEPTH NE 0)

Procedure

  1. Log in to the Integration Bus node computer as the mqm user.
    Important: The user must be the mqm user or a member of the mqm group. If you copy the files as another user, they might not be processed by the Integration Bus node components.
  2. Load the data.
    1. Go to the /var/PMQ/MQSIFileInput/PMQSampleData/Set6-EventData_ENU directory.
    2. Copy the following files, in sequence, to the /var/PMQ/MQSIFileInput/eventdatain directory one file at a time.
      1. event_observation_parameter*.csv—Loads parameter data.
      2. event_observation_*_training.csv—Loads training data.
      3. event_observation_pole_inspection.csv—Loads pole data.
  3. Set the appropriate time triggers in the PMQ_orchestration_definition_batch.xml file.
    1. Go to the /var/PMQ/MQSIFileInput/properties directory.
    2. Open PMQ_orchestration_definition_batch.xml in a text editor.
    3. Locate each of the following sections, and set the <scheduled_time> value to an appropriate time.
      Table 1. Predictive Maintenance and Quality feature and identifier value
      Feature <Identifer> value
      Distribution transformer Current ageing DTCA
      Distribution transformer Projected ageing DTPA

      Feature Based Analytics Training

      		 FHSTrigger
      Integrated Analytics Training IHSTrigger
      Feature Based Analytics for Poles POLEFBA
    4. Use the following command to stop AutoTrigger.msgflow in the PMQBatchIntegration application:

      mqsistopmsgflow pmqbroker -e pmqgroup1 -k PMQBatchIntegration -m AutoTrigger

    5. Use the following command to restart AutoTrigger.msgflow in the PMQBatchIntegration application:

      mqsistartmsgflow pmqbroker -e pmqgroup1 -k PMQBatchIntegration -m AutoTrigger

  4. Load the event data for scoring.
    1. Go to the /var/PMQ/MQSIFileInput/PMQSampleData/Set6-EventData_ENU directory.
    2. Copy the contents of that directory to the /var/PMQ/MQSIFileInput/eventdatain directory one file at a time. For example, copy event_observation_feature_*_scoring.csv.
  5. Reset the time triggers in the PMQ_orchestration_definition_batch.xml file.
    1. Go to the /var/PMQ/MQSIFileInput directory.
    2. Open PMQ_orchestration_definition_batch.xml in a text editor.
    3. Locate each of the following sections, and set the <sequence_time> value to an appropriate time.
      Table 2. Predictive Maintenance and Quality feature and identifier value
      Feature <Identifer> value

      Distribution transformer Current aging

      DTCA

      Distribution transformer Projected aging

      DTPA
      Note: If you are resetting the scheduler of any batch feature that is set to run for a duration_in_days that is greater than 1 day, then you must restart AutoTrigger.msgflow in the PMQBatchIntegration application to see the changes immediately.
    4. Use the following command to stop AutoTrigger.msgflow in the PMQBatchIntegration application:

      mqsistopmsgflow pmqbroker -e pmqgroup1 -k PMQBatchIntegration -m AutoTrigger

    5. Use the following command to restart AutoTrigger.msgflow in the PMQBatchIntegration application:

      mqsistartmsgflow pmqbroker -e pmqgroup1 -k PMQBatchIntegration -m AutoTrigger

Parent topic: Samples