No, it's not a new piece of equipment for your World of Warcraft character, it's an obscure reference to an underappreciated setting to aide your troubleshooting of advanced rules extensions in your MIIS implementation. Let's see what the MSDN Library says about this option:
A rules extension is loaded into memory when Microsoft Identity Integration Server 2003 first uses a synchronization rule configured for a rules extension. The rules extension is unloaded from memory under the following conditions:
- When Identity Integration Server does not call the rules extension within five minutes of the first call.
- When Unload extension if the duration of a single operation exceeds in Global rules Extension Settings of Configure Rules Extension in the Identity Manager is selected and Identity Integration Server calls the rules extension and does not receive a response from the rules extension after the specified time. If Identity Integration Server does not receive a response by the specified time, Identity Integration Server returns a synchronization error with the value extension-dll-timeout.
If the rules extension is unloaded from memory because of one of the previous conditions, then the rules extension will be loaded into memory the next time Identity Integration Server uses a synchronization rule configured for a rules extension.
I think most of us are familiar with the 5 minute reload requirement - if not from training then you've learned it the hard way from much trial, error and frustration. However, this additional setting allows you to determine how long before the extension is terminated due to inactivity of the code to progress beyond a single action; luckily for us this includes infinite loops.
I recently made some changes to an already implemented code base and began to see MIIS "stall" on certain records when running synchronizations. My first thought was that a SQL query had gotten past me somewhere and someone was locking one of the metaverse tables, but a quick check in SQL Enterprise manager and a more lengthy check in SQL Reporting Services reports didn't reveal anything so I set about trying to find the offending record. When I was going in to disable Provisioning I noticed the rules extension timeout setting. After checking the option I was able to locate an offending record quickly by running a Full Synchronization. With the new setting in place the code terminated with an extension-dll-timeout error after 60 seconds and I was able to locate the offending record and loop.