AnsweredAssumed Answered

How to check the Provisioning Command Node Status Code?

Question asked by Lakshman Varadharajan on Nov 28, 2016
Latest reply on Jul 4, 2018 by Mostafa Helmy

Like • Show 0 Likes0
Comment • 8

How to check the Provisioning Command Node result?

Version 691 P18 I am trying to use the Provisioning Command Node and get the 'Status Code' .

I selected the 'Wait for Result' on the ProvisioningnCommand node but my workflow does not have gives me the status code.

I see below two job-level static variable that can be used to get the provisioning command status code but I don't see the below variables in the job runtime data on the job.

acm.provisioningCommandStatusCode
acm.provisioningCommandStatusMessage

Can anyone help me to use these 2 variable in the workflow and get the status code ?

No one else has this question

Outcomes

8 Replies

Boris Lekumovich Nov 28, 2016 12:47 AM
Mark Correct
Correct Answer
Try the following:

After the provisioning node, add a SQL Select node with the following query:
```
    select '${jobUserData_acm.provisioningCommandStatusCode}' as STATUS_CODE,
    '${jobUserData_acm.provisioningCommandStatusMessage}' as Message_TEXT
    from dual
```
1 person found this helpful
Like • Show 1 Like1
Actions
- Sandeep Sharma @ Boris Lekumovich on Dec 4, 2017 1:17 AM
  Mark Correct
  Correct Answer
  Hi Boris,
  As per my testing on v7.0 P02/03, this does NOT work for AD based provisioning command node! Regardless of whether AD capability i.e. Create Account etc. fails, the node turns Green! Any way to actually detect if the AD provisioning command was successful and if not, to be able to capture/ display the acm.provisioningCommandStatusMessage? This would help the administrator's/ users troubleshoot the root cause!
  
  I had opened a case with RSA Support some time back and RSA Support engineer confirmed this defect/ behavior. Wondering if P04/ P05 fixed this.
  
  Regards,
  Sandeep
  Like • Show 0 Likes0
  Actions
  - Boris Lekumovich @ Sandeep Sharma on Dec 4, 2017 3:59 AM
    Mark Correct
    Correct Answer
    Have you looked in RSA Via L&G 7.0.0.5 Release Notes ?
    Like • Show 0 Likes0
    Actions
Tahir Ahmed Nov 28, 2016 11:33 AM
Mark Correct
Correct Answer
Above solution suggested by Boris should solve your issue,
Just in case, take a look at this as well... Handling Provisioning Node Failures
1 person found this helpful
Like • Show 1 Like1
Actions
Lakshman Varadharajan Nov 29, 2016 6:37 PM
Mark Correct
Correct Answer
Thank you! that helped
Like • Show 0 Likes0
Actions
- Boris Lekumovich @ Lakshman Varadharajan on Dec 1, 2016 3:31 AM
  Mark Correct
  Correct Answer
  KB article is also available for that - 000034403 - Provisioning node CommandStatusCode and CommandStatusMessage in RSA Identity Governance & Lifecycle
  Like • Show 0 Likes0
  Actions
  - Jesvin Joseph @ Boris Lekumovich on Jul 4, 2018 2:27 AM
    Mark Correct
    Correct Answer
    Boris, how will this work if there are multiple provisioning command nodes in a workflow which executes one after the other.? are these variables expected to get updated after each node is executed.? Boris Lekumovich
    Like • Show 0 Likes0
    Actions
    - Mostafa Helmy @ Jesvin Joseph on Jul 4, 2018 3:28 AM
      Mark Correct
      Correct Answer
      Yes, after each Provisioning Command Node completes the value of these varaibles gets overwritten with the new status and code.
      
      However this is only valid if the Nodes are in series. If your workflow has multiple paths that execute in parallel, each containing different Provisioning Command Nodes, then the value of these variables in this case could be unexpected.
      Like • Show 0 Likes0
      Actions

How to check the Provisioning Command Node Status Code?

Outcomes

Related Content

Recommended Content