Activating the service activity monitoring facility

To activate the service activity monitoring facility, take the following steps:

Procedure

  1. Use the Configuration and Management module of InfoSphere® MDM to change the value of the /IBM/DWLCommonServices/Report/Broadcaster/enabled property to true.
    This configuration setting is dynamic, so when the value changes, the application server applies the change without requiring a restart. For information about using the Configuration and Management module, see Using the Configuration and Management components.
  2. To enable the service activity monitoring facility to capture the activity data in a log file, use the Configuration and Management module of InfoSphere MDM to change the value of the /IBM/DWLCommonServices/Report/KafkaListener/enabled property to true.
    When enabled, this configuration setting registers the listener with the MBean Server, providing the object name of the MBean that issued the notification. This configuration setting is static, so when the value changes, you must restart the application server to apply the change.
  3. To utilize the service activity monitoring facility at runtime, assign administrative IBM® WebSphere® Application Server roles such as Administrator or Operator. For more information, see Administrative roles. Complete the following steps if the user running InfoSphere MDM does not have the proper administrative IBM WebSphere Application Server roles:
    1. Add the following JVM properties:
      • MDM_SAM_USER specifies the username of the user with administrative roles to run service activity monitoring.
      • MDM_SAM_PASSWORD specifies the password of MDM_SAM_USER. This value can be encoded with IBM WebSphere Application Server. For more information, see Encrypting passwords with WebSphere Application Server.
      • MDM_SAM_REALM specifies the name of realm (user registry) where the MDM_SAM_USER is defined, for example, defaultWIMFileBasedRealm. If this property is not provided, InfoSphere MDM checks the above credentials in the current application realm.
      After you add the JVM properties, InfoSphere MDM attempts to run service activity monitoring with the credentials you provided.
    2. Configure the following properties to ensure a successful login:
      • Open Security > Global security > JAAS Configuration > Application logins and select WSLogin.
      • From the JAAS Login Modules, select com.ibm.ws.security.common.auth.module.WSLoginModuleImpl.
      • Set the value to true for the following custom properties:
        • use_realm_callback
        • use_appcontext_callback
      • Restart the application server.
  4. Start the Kafka server.
  5. Create the MDM SAM Kafka topic com-ibm-mdm-report-transactiondata if it is not yet created.
    1. Configure <MDM_INSTALL_HOME>/KafkaProcessor/bin/createTopics_Sample:
      • KAFKA_HOME=<KAFKA_HOME> is the Kafka installation directory
      • hostname=<KAFKA_HOST_NAME> is the Kafka host name
      • port=<KAFKA_PORT> is the Kafka port number
    2. Execute <MDM_INSTALL_HOME>/KafkaProcessor/bin/createTopics_Sample.(bat/sh).
  6. Start file connector.
    1. Configure <MDM_INSTALL_HOME>/KafkaProcessor/bin/runKafkaFileConnector.(bat/sh):
      • KAFKA_HOME=<KAFKA_HOME> is the Kafka installation directory
    2. Execute <MDM_INSTALL_HOME>/KafkaProcessor/bin/runKafkaFileConnector.(bat/sh).
  7. On the WebSphere Application Server Administrative Console, browse to Resources/Resource Environment/Resource Environment Providers/KafkaSAMResourceEnvironmentProvider/Custom properties, and set <KAFKA_HOSTNAME>:<KAFKA_PORT_NO> to the bootstrap.servers property to allow the MDM engine to send SAM messages.

    If security is enabled, configure an additional property such as:

    • a username and password
    • SSL trust store type/location/password

What to do next

See the Elements in the Configuration and Management component topic for details about these configurations.