Relationship Management Application (RMA) task
This Services Framework task is used to load the relationship management application data from Swift.
After the RMA task is complete, a tactical activation message is sent to the Business Rules Manager to reload the data. For more information about tactical activation, see Tactical activation.
Register the task
Use the task registry page in the Services Framework user interface. For more information, see Register a task. The following table shows the fields that are needed to register this task.
| Field | Description | Value |
|---|---|---|
| Task classname | Enter the Java class name for the task. | com.ibm.fxh.swiftref.tasks.RMATask |
| Characteristic | Setting | Description |
|---|---|---|
| Manual Run | Allowed | This task can be run manually. |
| Scheduled Run | Allowed | This task can be scheduled to run by using the Services Framework timed interface. |
| Concurrent Run | Not allowed | This task cannot run concurrently. |
This task can be run manually but no manual run configuration is available.
Configure the task
Services Framework tasks need to be configured before they can be used. The following list
describes the configuration that the RMA task needs.
- Set the appropriate configuration parameters for the task. The parameters for this task are shown in the following tables.
- The file is delivered to a configured target directory. This directory is normally configured as the source directory for an outbound Gateway.
Use the Services Framework task configuration page to provide the configuration parameters for
the task. For more information, see Configure a task. The following
table shows the common parameters for the Services Framework tasks.
| Parameter | Description | Example |
|---|---|---|
| Task | The name of the registered task. | RMA task |
| Configuration | The descriptive name for the configuration. | RMA task configuration |
| Description | A detailed description that explains what the configuration does. This parameter is not mandatory. If entered, it must be 512 characters or less. | |
| Activate task | This parameter identifies if the configuration is active. | Yes, No |
| Process end of day | This parameter indicates whether the task is to be called during end of day processing. Set this value to yes to call the task | Yes |
| Process cleanup | Set this value to no because the task does not need to process cleanup. | No |
| Delete on complete | This parameter indicates whether the activity for this task is deleted when it is complete. If set to yes, the activity for this task is deleted when it successfully completes and is not deleted when it has errors or warnings. If set to no, the activity for this task is not deleted when it completes. Deleted task activities do not appear on the task activity page | Yes, No |
| Allow Monitor | This parameter indicates whether Services Framework collects performance data for the task configuration. | Yes, No |
The following table shows the parameters for the RMA task.
| Parameter | Description |
|---|---|
| Source directory | This parameter specifies the directory where the RMA file is delivered. |
| Error directory | This parameter specifies the error directory that the RMA task use to store the failed RMA file. |
| Processed directory | This parameter specifies the processed directory that the RMA task use to store the completed RMA file. |
Information displayed by the task
Depending on the various stages of the data loading processing, you can see the following information.
- Whether the task execution is a manual run or a regular scheduled run.
- Task execution messages that are appropriate for the stage of processing.
- Task error messages.
- The total number of records read from the source file.
- The total number of records that are inserted to the database.
- The total number of records that are updated in the database.
- The total number of records that are bypassed in the database.
- The total number of records that are deleted in the database.
- The total time used by the task.