Applies to:

Oracle Trading Community - Version: 12.0 to 12.1.0 - Release: 12 to 12
Information in this document applies to any platform.

Goal

How does the DQM Real Time (Automatic) Synchronization work for R12?

Solution

In Release 12, the DQM Synchronization can be set to:
Automatic
Batch
Disabled

Navigation Path: (R)
Customers Online Data Librarian Super User or Trading Community Manager
Administration Tab > DQM tab >
DQM Synchronization Method

Release 12 no longer uses the Real Time Work flow business events.
The real time is now called automatic.

IF DQM automatic sync is enabled a concurrent program is submitted whenever a party is created/updated.
This concurrent program is called DQM Serial Sync Index Program (ARHDQMSS).

Once a new party/account is added or updated, the DQM Serial Sync Index Program is kicked off and once the concurrent process is complete you can search and find the party/account that was updated or added.

You might not be able to search for the newly created party/account immediately after creation. After a few minutes you can search for them, this depends on the completion of the concurrent request.

As an optimization to make sure, we don't have too many of these concurrent requests running, when there is a lot of activity, we seeded these programs to have the property "No Pending Requests" enabled. In other words,when one sync concurrent request is in pending status, no other sync concurrent request would even be submitted. If a party is created while a concurrent program is already running, the DQM Serial Sync Index Program was not run for the newly created party.
.
To overcome this , you can set the profile option:
HZ: Ignore Concurrent Request Limits for DQM Synchronization
If it is set to yes,it will run the DQM Serial Sync Index Program irrespective of the other concurrent programs. [@more@]

ITPub博客

How does the DQM Real Time (Automatic) Synchronization work for R12? [ID 465993.1]

Applies to:

Goal

Solution

最新文章