Business Integration Solutions Documentation
How to: Use Job Queue Handler
Use this task when you want to process many BC BIS Connections automatically, using the Job Queue functionality, without configuring each Job Queue Entry separately.
The Job Queue Handler allows users to configure 1 Job Queue Entry, for multiple NAV BIS Connections. For example: with only 1 Job Queue Entry, you can process all the Subscription Connections for Replication Management.
When importing the BIS Objects, the Job Queue Handlers will automatically be created. To add a Job Queue Handler manually, please read this topic.
When a connection is processed using the Job Queue Handler, there are two requirements for the connection:
- The connection is published.
- The connection does not have the Process with Job Queue setting enabled for Events, the Splitter Activity and the Reading Endpoints.
To use the job queue handler:
- Go to the Job Queue Entries list and click New to create a new Job Queue Entry.
- Fill in the following fields (not required, but if desired you can define the Earliest Start Date and Recurrence settings):
Field | Description |
---|---|
Object Type to Run | Codeunit |
Object ID to Run | Codeunit object id |
Object Name to Run | Codeunit name |
Description | Job queue handler |
When you want to configure the Job Queue Handler for the other BC BIS Solutions, use these Codeunits:
Codenit 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 3. Click Set Status to Ready action to activate the Job Queue.
In the Job Queue Entries list [Job Queue/Job Queue Entries] a new Job Queue Entry is created for the Subscription Connections. From the Job Queue Entries list you are able to see if the Job Queue Entry is still running and what the earliest start date is for the Job Queue Entry.