Ensure 1 Active Sync process runs against the change log before all others?

Question

He folks,
We have a lot of LDAP active sync thread. We have a primary on that correlates to an individuals account. Then we have several that represent affiliations at our organization. The affiliations are represented in LDAP as subordinates of the main persons entry. These sets of data were set up as different resource adapters because the they are different object types in LDAP.
Now we are running into a problem where the active sync threads for subordinates are running before the thread for the main entry. What this means, is that an affiliation thread might run, see a new person was added and ignore it (since that isn't it's resource) but find the affiliation subordinate entry and want to process it. However, the thread can't find an associated account in IDM yet, so no processing takes place on that change, ever..
If the main account active sync thread had already run, it would see the main entry, and then make a correisponding IDM entry. If the IDM entry has been made, and the affiliation resource active sync adapter runs, it will then find the IDM entry and update that.
So.. We are experience problems when the affiliation processes a new account before the main account sync process.
Can we ensure somehow that the main account active sync process always runs first? These are all LDAP resources. If we could ensure the main account resource / sync happens before any other affiliation resource, then we would never ignore data, and would not have anyproblems.
Does anyone know of a good clean way to do this?
Thanks!

Answer 1

I had a similar issue, and solved it by using post process workflows and starting and stopping resource adapters manually. This will allow you to start the first resource, and any others you want can be started/stopped manually via the workflow. You can effectively "chain" resource adapters to run in any order you'd like.
On the first resource that you want to run before anything else, this will run as a post-process workflow:
     <Activity id='0' name='stopFirstResource'>
        <Action id='0' name='stop'>
          <expression>
            <block name='stop'>
              <invoke name='stopActiveSyncOnResource' class='com.waveset.session.SessionUtil'>
                <ref>displaySession</ref>
                <s>%%FIRSTRESOURCENAME%%</s>
              </invoke>
            </block>
          </expression>
        </Action>
        <Transition to='Process Errors'>
          <ref>WF_ACTION_ERROR</ref>
        </Transition>
        <Transition to='startSecondResource'/>
      </Activity>
      <Activity id='1' name='startSecondResource'>
        <Action id='0' name='start'>
          <expression>
            <invoke name='startActiveSyncOnResource' class='com.waveset.session.SessionUtil'>
              <ref>displaySession</ref>
              <s>%%SECONDRESOURCENAME%%</s>
            </invoke>
          </expression>
        </Action>
        <Transition to='Process Errors'>
          <ref>WF_ACTION_ERROR</ref>
        </Transition>
        <Transition to='end'/>
      </Activity>
This will stop the first one (after it has run) and start the second one.
Then, on the post process workflow of the second resource:
      <Activity id='1' name='stopSecondResource'>
        <Action id='0' name='stop'>
          <expression>
            <block name='start'>
              <invoke name='stopActiveSyncOnResource' class='com.waveset.session.SessionUtil'>
                <ref>displaySession</ref>
                <s>%%SECONDRESOURCENAME%%</s>
              </invoke>
            </block>
          </expression>
        </Action>
        <Transition to='Process Errors'>
          <ref>WF_ACTION_ERROR</ref>
        </Transition>
        <Transition to='end'/>
      </Activity>This stops the second one.