Changing priority of job steps

Hello,


Our business is complaining that a specific process (EH_UNSAccountB_Insert_OADM Retrieve Contact Information) is taking too much time (around 4-5 minutes). When creating a customer account in the OIM web interface, they assign a contact identifier (OADM Id) and this process is triggered to retrieve contact information from another system (OADM). Information are retrieved by a web service call to OADM.


We changed the specific code of this process: the code linked to a log was activated for every process run. It is not the case anymore. This code is now activated only if a configuration parameter is set to True (just in case of debugging).


Another idea is to increase the priority of process steps related to this process. The priority of those process steps has been changed from 3 to 2.


You can see below an example of test carried out after having changed the code and the priority of process steps:

GenProcID JobChainName Queue Priority TaskName StartAt EndedAt Time Processing
eff5889c-c694-4361-8270-75c3f29e6d0f Created by QBMDBQueueProcess:PersonInAERole \D1JUFRDTC01 5 FireGenEvent 28/11/2019 17:07:04 28/11/2019 17:08:07 00:01:03
eff5889c-c694-4361-8270-75c3f29e6d0f Created by QBMDBQueueProcess:PersonInAERole \D1JUFRDTC01 5 FireGenEvent 28/11/2019 17:07:04 28/11/2019 17:08:07 00:01:03
eff5889c-c694-4361-8270-75c3f29e6d0f Created by QBMDBQueueProcess:PersonHasTSBAccountDef \D1JUFRDTC01 5 FireGenEvent 28/11/2019 17:11:24 28/11/2019 17:12:38 00:01:13
eff5889c-c694-4361-8270-75c3f29e6d0f TSB_PersonHasTSBAccountDef_Autocreate_UNSAccountB \D1JUFRDTC01 3 Exists 28/11/2019 17:12:38 28/11/2019 17:14:07 00:01:29
eff5889c-c694-4361-8270-75c3f29e6d0f TSB_PersonHasTSBAccountDef_Autocreate_UNSAccountB \D1JUFRDTC01 3 Exists 28/11/2019 17:12:38 28/11/2019 17:14:08 00:01:29
eff5889c-c694-4361-8270-75c3f29e6d0f TSB_PersonHasTSBAccountDef_Autocreate_UNSAccountB \D1JUFRDTC01 3 ScriptExecSingle 28/11/2019 17:12:38 28/11/2019 17:14:11 00:01:33
eff5889c-c694-4361-8270-75c3f29e6d0f TSB_PersonHasTSBAccountDef_Autocreate_UNSAccountB \D1JUFRDTC01 3 Insert 28/11/2019 17:12:38 28/11/2019 17:14:11 00:01:33
eff5889c-c694-4361-8270-75c3f29e6d0f EH_UNSAccountB_Insert_Calculate Permissions \D1JUFRDTC02 3 Update 28/11/2019 17:14:11 28/11/2019 17:15:12 00:01:01
eff5889c-c694-4361-8270-75c3f29e6d0f EH_UNSAccountB_Insert_OADM Retrieve Contact Information \D1JUFRDTC01 2 ScriptExec 28/11/2019 17:14:11 28/11/2019 17:14:24 00:00:12
eff5889c-c694-4361-8270-75c3f29e6d0f EH_UNSAccountB_Insert_OADM Retrieve Contact Information \D1JUFRDTC01 2 Execute SQL 28/11/2019 17:14:11 28/11/2019 17:14:23 00:00:11
eff5889c-c694-4361-8270-75c3f29e6d0f EH_Person_Insert_Update_Push data for IRP Distribution Plan \D1JUFRDTC01 3 ScriptExec 28/11/2019 17:14:24 28/11/2019 17:15:40 00:01:15
eff5889c-c694-4361-8270-75c3f29e6d0f EH_PersonHasTSBAccountDef_Update_Synchronize Permissions \D1JUFRDTC01 3 ScriptExec 28/11/2019 17:15:12 28/11/2019 17:15:39 00:00:27
eff5889c-c694-4361-8270-75c3f29e6d0f EH_PersonHasTSBAccountDef_Update_Synchronize Permissions \D1JUFRDTC01 3 Not Exists 28/11/2019 17:15:12 28/11/2019 17:15:38 00:00:25

We could also change the priority of process steps of the standard process TSB_PersonHasTSBAccountDef_Autocreate_UNSAccountB but this is not allowed in the Designer: the priority is greyed (Priority.CanEdit is False on Extended tab of process step properties).

Do you advise to change the priorities of process steps of such a standard process? If yes, directly by SQL?

Do you see any other options that we could use to improve the time processing of this specific process?


Kind regards,


P. Vittadello


Euler Hermes IAM Competenicy Centre

Parents
  • The processing speed for a single job seems to be very low in general in your environment and all the times are summing up.

    In regards to changing the priority of a process step please tell us the version of OneIM you are using.

  • Hello Markus,

    Processing times in the table above were taken after changes in a testing environment (UAT-R) whose performance is really slow indeed.

    We are using a 7.0.2 version of OIM (no more supported since 31/12/2018) but we are currently in contact with Quest Professional Services (C. Rudd & I. Sadique) to have a PS consultant from 19/12 to work with us on a technical prerequiste (History DataBase), needed before being able to upgrade to a supported version.

    Pascal

Reply
  • Hello Markus,

    Processing times in the table above were taken after changes in a testing environment (UAT-R) whose performance is really slow indeed.

    We are using a 7.0.2 version of OIM (no more supported since 31/12/2018) but we are currently in contact with Quest Professional Services (C. Rudd & I. Sadique) to have a PS consultant from 19/12 to work with us on a technical prerequiste (History DataBase), needed before being able to upgrade to a supported version.

    Pascal

Children