Test remediation efforts for MID Server user connectivity issues

After attempting to resolve a user connectivity issue that appears in the MID Server Issue [ecc_agent_issue] table, you can test your remediation efforts without having to wait until the next scheduled reporting period by shortening the sampling interval.

Before you begin

Role required: admin

About this task

Reconfigure the sampling interval using this procedure and then examine the results in the MID Server Issue [ecc_agent_issue] table. You can set any time span for the sample, but the best practice is to define a window of not less than 5 minutes, since this is the default interval of the MID Server heartbeat that reports its status. The recommended method for configuring a shorter sampling interval is to copy and modify the code from the MIDUserConnectivity scheduled job, and then run it manually in the background script utility.
Caution: Avoid editing the script in the MIDUserConnectivity schedule record. If you make any change to this record, it will not be updated when you upgrade the instance.

Procedure

  1. Navigate to System Definition > Scheduled Jobs.
  2. Open the MIDUserConnectivity scheduled job.
  3. Copy this line from the Run this script field:
    MIDUserConnectivity(0).checkConnectivity(4 * (60 * 60 *1000));

    This code sets the 4 hour sampling interval in milliseconds and turns debugging off with the MIDUserConnectivity(0) value.

  4. Navigate to System Maintenance > Scripts - Background.
  5. Paste the code from the scheduled job into the Run script field.
  6. Set the sampling interval to 5 minutes by changing the time calculation to (5 * 60 *1000).
    The modified command looks like this: MIDUserConnectivity(0).checkConnectivity (5 * 60 *1000);
  7. Click Run script.
  8. Open the record of the MID Server that had the issue and select the MID Server Issues related list.
    The issue is updated as follows:
    • If the issue persists, the Count column is incremented, and the Last detected column shows the current date and time.
    • If the issue no longer exists, the system changes the State to Resolved.
  9. Optionally, you can enable debugging by selecting a level, and then run the script again to see the breakdown for each condition evaluated.
    Use these settings to select a debugging level:
    • For a summary view, enter MIDUserConnectivity(1).
    • For a detailed view, enter MIDUserConnectivity(2).

    For details about the type of debugging information provided, see Interpreting MID Server user debugging output.