Provisioning Reference Guide › SPML Service › SPML Service Configuration › Retrying SPML Requests › Retry Configuration Files

Retry Configuration Files

Interface

Two operational attributes control the SPML retry capability:

• caIamRetry can be passed in with an asynchronous request, requesting that retry functionality is activated where supported by JIAM. caIamRetry is operational attribute and its value can be true or false.
• caIamRetryDetails is returned when an SPML status request targeting a retried request is received. It provides status information to the user.

For an example of a request flagged for retry, see the appendix “Sample SPML Requests.”

Hivemodule-plugin-deploy.xml

The file hivemodule-plugin-deploy.xml in the SPML deployment directory includes configuration items:

• A new database called db_spml_retry configured by the retryBasicDataSource service-point, and advertised to JIAM via the retryPersister service-point. This database (as well as the pre-existing db_qrtz and db_delegate) should not grow and shrink as requests are processed and time out.

  If a problem occurs in this area, the databases can be truncated by shutting down the SPML server and simply deleting their directories (the SPML server will automatically create new blank directories on start-up).

• The retryMaximumCount and retryDelayMinutes settings which control the JIAM retry behavior using the JIAMService class, which is also provided with the retryPersister.

  retryMaximumCount tells the SPML server the maximum number of times it should retry an operation before giving up and returning an error. When a retry is needed, the SPML server waits before doing the retry, to give the network or server failure a chance to correct itself. The time it waits before retrying is controlled by the retryDelayMinutes setting.

• The scheduledHoldingIntervalMinutes setting dictates the time that status requests targeting an asynchronous request can be submitted after its processing is completed, and consequently applies to retried requests too.

Any manual changes made to a hivemodule-plugin-deploy.xml file from a previous release will need to be reapplied to the file for this release.

To cancel a retried request, submit a SPML cancel request referring to its identifier. If a retry attempt has begun, it will continue, but no further retry attempts will be made.

Note: Retry functionality is not supported on SPML modify requests that change an object's Distinguished Name (DN).

Access Credentials

Access credentials for the databases used by the SPML server are stored in the spml_quartz.properties and hivemodule-plugin-deploy.xml configuration files. Each database supports two different styles of URLs in their datasources:

• jdbc:hsqldb:file:<dir>\<db>\<db> : databases can only be accessed by the SPML server process itself (the default).
• jdbc:hsqldb:hsql://localhost/<db> : allows SQL access to the database by other processes.