This documentation supports the 18.08 version of Remedy IT Service Management Suite.

To view the latest version, select the version from the Product version menu.

Configuring the ARID plug-in and BMC Remedy ITSM Process Designer runtime settings

Set or review the BMC Remedy ITSM Process Designer configuration for:

  • All fresh installs of the Process Designer server on Linux or UNIX.
  • All fresh installs where you configured an RPC queue.

Note

 This procedure is optional for Windows, because the installer generates a default entry. Verify that the configuration entry is correct after installing.

To configure the ARID plug-in and BMC Remedy ITSM Process Designer runtime settings

  1. Log on to BMC Remedy Mid Tier on your AR System server as a member of the Process Designer Administrator group.
    You can use the ARID user credentials.
  2. From the Home Page, select Process Designer Configuration from the Process Designer menu.
  3. Click the Configuration tab.

    The following table describes the purpose of each of the field values:

    Field

    Description

    ARID Configuration Path

    Full path on your BMC Remedy AR System server where the Process Designer plug-in and other server configuration files are installed. Use the Default button to select the default location for a Windows server.

    Pause Between Job Initiation (ms)

    Wait period for the manager thread between assigning a job and checking for more jobs (the default is 100 ms).

    Job Timeout (secs)

    Timeout period for a worker thread to complete a job default is 60 seconds.

    Number of Worker Threads

    Maximum number of worker threads.
    For servers using a private queue for processing this should be set to one less than the number of threads assigned to the Private RPC Queue configured on your AR System server.

    Delete Successful Jobs (Yes/No)

    Set to Yes to delete all jobs that complete successfully. (This setting is recommended unless you are troubleshooting.)

    Logging Type (Form / File)

    Select Form if you want the process runtime logging information to be written to an AR System form so that it can be viewed from the Logging tab under Process Designer Configuration.

    Logging Level (None, Error, Milestone, Detail, Debug)

    Set to the required level for viewing log information.
    Each log level includes logging from the previous level, so Detail logging includes Errors and Milestones. Debug level logging is only visible to Administrators. It is recommended to use File based logging at Error level for normal operations.

    Log File

    Full path of the log file, including file name for recording events from the Process Designer plug-in. Use the Windows Server Default button to select the default location on your server.

    Auto-Release Tasks

    This option is now redundant.

    Cancel Redundant Tasks

    Set to Yes to set redundant process tasks to a cancelled state at run time (the default is No).

  4. If the user or password has been updated, click Update Password File to update this setting.

    Note

     This step is not applicable to Process Designer versions 8.3.04 and 9.0.

  5. Click Apply to confirm all changes.

Best Practices

  • In a production environment, assign the ARID plug-in its own private thread pool to avoid conflict with other users and processes when performing operations on the AR System server. On the development or other low-volume servers, this step is not required and the Process Designer server will use the general thread pools.

    The server queue must have a minimum of two threads available. The maximum number of threads depends on how many worker threads you need to perform the server-side operations. The higher this value, the faster the process designer server can complete its operations in a high-load environment. However, assigning too many threads to this function can result in slowing down other areas of your AR System server. BMC recommends a server queue to have a minimum of two threads and a maximum of eight threads. This allows up to 7 operations to be performed concurrently, if required.

    By enabling the audit for a process or a task, you can track the individual changes to processes and tasks, SLAs, OLAs, and assignment rules. The details include the user who made the change and the timestamp when the change was performed.

  • Click the Yes option of Delete Successful Jobs in the Configuration tab of Process Designer. Click No only for debugging.

Was this page helpful? Yes No Submitting... Thank you

Comments