Oracle Lite Performance Testing

Question

Hi All,
Is there a way to sync more than one client from the same PC/Laptop to simulate a concurrent sync for performance testing purposes? Greg Rekuonas did mention, some script available by Oracle Support for the same. Oracle (on raising an SR) unfortunately says that they cannot make that available to customers.
I have found a way out, but it involves changing one of olite's dll's and was wondering if anyone else knew a better solution.(Other than finding 50-100 different laptop's/handhelds and make them all synchronize one by one).
Cheers,
Vikrant

Answer 1

Hi Greg,
Thanks for the reply. I will try and re-raise it with them, though they have closed my SR with a "Not Entitled" status.
In case anyone is interested I finally, got the trick done by using the following:-
1) Open ocapi.dll in your $MOBILE_HOME/bin folder. (Right where the msync_java.dll is there)
2) Open the above file in a text editor like EditPlus(Note this is a binary file)
3) Search for the string OracleLiteSync.
4) Change the string to something else(Do not add any characters, just change any one alphabet).
5) Save this file as ocapi.dll in a different directory.
I wrote a standard java program, to programatically trigger a synchronization. To, handle concurrent synchronizations, I create multiple copies of ocapi.dll with different strings for OracleLiteSync.
Each of my simulation "Clients"(Basically Java Threads) were invoked with a different path each pointing to a different ocapi.dll. This seemed to work, and the "Mutex" error went away.
The exaplanation is that basically OracleLite uses the Kernel32 API CreateMutexA to create a mutex to ensure that two synchroninzations cannot happen on the same machine. The mutex name is OracleLiteSync and the code is in ocapi.dll.
By changing the mutex name and using a different version of ocapi.dll (Oracle Lite uses JNI which reads DLL from the PATH environment variable) you can fool Oracle Lite into doing different synchronizations.
This did give me some errors when it tried to apply the downloaded changes simultaneously in different ODB's, but allowed me to load the mobile server concurrently with syncrhonization sessions.
Cheers,
Vikrant