Configuring the IONOutbox Queue for Multi-threading
By default, the IONOutbox queue is single-threaded for the requests that it processes, such as those for BODs and data replication through IMS. This can negatively impact performance if you have requests from more than one of the IMS message types (replication, BOD, data, and unknown). To help performance, you can configure your system so that this queue is multi-threaded and thus devotes a thread to each of the IMS message types.
- In your Landmark user interface, access the data area for which you want to configure the IONOutbox queue. Be sure that the actor logging in to perform these steps has permission to run the IMSWriter Sweep action.
- Navigate to 5. , select the IONOutbox queue, and change the maximum active actions setting for the queue to
-
Disable the original request that uses the IONOutbox queue.
- Navigate to and select the request to disable (Hint: filter the list using the class of IMSWriter). Be sure to select the request that is defined for the current data area. If you have multiple data areas that use the IONOutbox queue, you must log into the other data areas and repeat this step for each data area.
- Change the System Request setting to Yes and make sure the Pending Scheduling check box is not selected.
- Save your changes.
-
For each IMS message type, create a new request. (Be sure to
create a request for all of the types: replication, BOD, data, and unknown.
Also, if you have multiple data areas that use the IONOutbox queue, you must log
into the other data areas and repeat this step for each data area.)
- Set up scheduling for the request according to your business needs.
- On the Action Request form, select .