Provisioning Retry Behavior

[AJGibson76 (Andrew Gibson)]

Which IIQ version are you inquiring about?

8.4

As part of a project I must implement some custom retry logic when the provisioning fails. We are using the Provisioning object inside a beanshell rule to perform provisioning via Provisioner.execute(ProjectPlan). My question is: if an error occurs during provisioning, will an exception be thrown? Does Provisioner.execute block? What is the correct way to implement retry behavior?

[enistriminsait (Emanuele Nistri)]

Hi @AJGibson76,

@AJGibson76

if an error occurs during provisioning, will an exception be thrown?

depends on the error. If the error is “in the code” like nullPointer will be generate an exception and you can manage it. If the error is on the application you can find the error into the response. For example, 403/404 like a response code for a API call you dont an exception. In the first case the provisioning will be interrupted, in the second it will not.

To retry a plan, you can use the keys in the connector, where you can define the number of retries, the retry frequency, and the errors that should be triggered.

<entry key="provisioningMaxRetries" value="4"/> 
<entry key="provisioningRetryThreshold" value="2"/> 
<entry key="retryableErrors">
  <value>
    <List>
      <String>Timeout occurred</String>
    </List>
  </value>
</entry>

Additionally, you can manage directly in your rule, with a “while” you can retry as long as you want.

I don’t know how useful it is to use “retry” if an exception or error occurs.

[fratelesca (Francesca Telesca)]

Hi @AJGibson76

maybe you can implement your custom retry logic in the Post Provisioning Rule of your connector, you should have the status of the provisioning there (i.e. if it was successful or if it failed)

[AJGibson76 (Andrew Gibson)]

@fratelesca

Post Provisioning Rule

Is it possible to supply a Rule as part of Provisioner. execute action? I need to do this from my beanshell script.

[AJGibson76 (Andrew Gibson)]

I’ve been looking more into this, and it looks like a good solution, since all my interactions are with one service. Does the post provisioning rule get called once the instructions are sent to the external connected service, or after some sort of response? I’ve been reading that the ProvisioningResult is sometimes null?

[fratelesca (Francesca Telesca)]

@AJGibson76 Sorry, I realized I called it ‘post provisioning rule’ but it’s actually called After Provisioning Rule. Anyway, I found here this definition:

“An application’s AfterProvisioning rule is executed immediately after the connector’s provisioning method is called, but only if the provisioning result is in a committed or queued state. This gives customers the ability to customize or react to anything in the ProvisioningPlan that has been sent out to specific applications after the
provisioning request has been processed. This rule is not connector-specific; it runs for all applications regardless of connector type.”

Hope this helps

[AJGibson76 (Andrew Gibson)]

Is there a way to create a rule that gets triggered after the provisioning is complete? I need to send an email notification in the event of a provisioning failure, but it’s not a simple email, some scripting is involved.

[AJGibson76 (Andrew Gibson)]

I’ve trying to do this via an after provision rule, but the provisioning plan has a null as it’s status when I do this. Is there another approach that might work? There is no task visible under task results either, but I can see exceptions get through by the connector when I used the service.