0
Not a bug

Only One Schedule runs when multiple schedules executing at same time

Matthew Woolnough 3 years ago in UNIFYBroker/Aurion • updated by anonymous 3 years ago 7

5 Connectors all have Import All Schedule to run at midnight. An exclusion group exists to ensure they do not all run at once. Only one connector runs, resulting in incomplete data being imported.




Affected Versions:
Fixed by Version:

Answer

Answer
Not a bug

Hi Matthew,


Please reconfigure the connectors and enable the Queue when Blocked setting.

This is what is shown on main page after execution



All Schedules were to start at 9:25 for testing. Only the Aurion Person Connector ran.


20160901,23:25:00,UNIFY Identity Broker,Change detection engine,Information,"Change detection engine import all items started.Change detection engine import all items for connector Aurion Person Connector started.",Normal
20160901,23:25:00,UNIFY Identity Broker,Connector,Information,"Request to import all entities from connector.
Request to import all entities from connector Aurion Person Connector.",Normal
20160901,23:25:09,UNIFY Identity Broker,Connector Processor,Information,"Connector Processing started.
Connector Processing started for connector Aurion Person Connector (page 1)",Normal
20160901,23:25:09,UNIFY Identity Broker,Connector,Information,"Import all entities from connector completed.
Import all entities from connector Aurion Person Connector return 1048 entities. Duration: 00:00:08.7968910",Normal
20160901,23:25:09,UNIFY Identity Broker,Connector Processor,Information,"Connector processing success.
0 entities in cumulative total. Current processing of page 1 for connector Aurion Person Connector processed 1000 entities, finding 0 differences. Duration: 00:00:00.7031358. ",Normal
20160901,23:25:09,UNIFY Identity Broker,Connector Processor,Information,"Connector Processing started.
Connector Processing started for connector Aurion Person Connector (page 2)",Normal
20160901,23:25:10,UNIFY Identity Broker,Connector Processor,Information,"Connector processing success.
1000 entities in cumulative total. Current processing of page 2 for connector Aurion Person Connector processed 48 entities, finding 0 differences. Duration: 00:00:00.2031390. ",Normal
20160901,23:25:10,UNIFY Identity Broker,Change detection engine,Information,"Change detection engine import all items completed.
Change detection engine import all items for connector Aurion Person Connector completed. Duration: 00:00:09.8598919",Normal

Answer
Not a bug

Hi Matthew,


Please reconfigure the connectors and enable the Queue when Blocked setting.

I'm curious to know what function the grouping provides other facilitating queue when blocked?

It assists deployments with large number of connected systems find the connector or adapter based on group, or allows for logical groupings so that an operation can be performed against the group.

I don't see a configuration item for Queue when Blocked on the Aurion Connector. How do I edit this?

What version of Identity Broker for Aurion are you running? This setting has been available since v4.1.2 and v5.0.1.