Business Integration Solutions documentation
How to: Use the job queue handler
Use this task when you want to process several BC BIS connections automatically using the job queue functionality, without configuring each job queue entry separately.
The job queue handler lets users configure one job queue entry for several NAV BIS connections. For example, with only one job queue entry, you can process all subscription connections for Replication Management.
When importing the BIS objects, the job queue handlers are created automatically. To add a job queue handler manually, follow this task.
When a connection processes using the job queue handler, two requirements apply:
- The connection is published.
- The connection does not have Process with Job Queue enabled for events, the Splitter activity, and the reading endpoints.
To use the job queue handler:
- Go to the Job Queue Entries list and select New to create a new job queue entry.
- Fill in the following fields (optional, you can also define Earliest Start Date and recurrence settings if needed):
| Field | Description |
|---|---|
| Object Type to Run | Codeunit |
| Object ID to Run | Codeunit object ID |
| Object Name to Run | Codeunit name |
| Description | Job queue handler |
To configure the job queue handler for other BC BIS solutions, use the following codeunits:
| Codeunit ID | Name | BC BIS solution |
|---|---|---|
| 11068925 | N111 Job Queue Handler | Connectivity Studio |
| 11032204 | N116 Job Queue Handler | Notification Management |
| 11069189 | N128 Job Queue Handler | EDI Studio |
| 11069209 | N130 Publ. Job Queue Handler | Replication Management |
| 11069219 | N130 Subscr. Job Queue Handler | Replication Management |
- Select the Set Status to Ready action to start the job queue.
In the Job Queue Entries list, a new job queue entry is created for the subscription connections. From this list, you can see whether the job queue entry is still running and what the earliest start date is.