1. CLASS PATHS and JARS : Add all jars used by the application in classpath (A better approach is to look at the RunMe.bat you guys have and ensure all classpaths, and options are set on VUGEN as well). Eg: the -Xmx and -Xms arguments should be passed as JVM arguments if these were part of your original batch file.
2. JAVA SECURITY : Ensure that java security policy grants all permission for all applications. Lookup in support portal or on the web on how to do it. It invloves editing of the java.policy file under the JDK folder>jre>lib>security.
3. JDK : Use the correct JDK. Note that JRE is not supported. You need a JDK for VUGEN classpath.
4. CLASS PATH ORDER : The order in which the classpath listings are done is important in VUGEN. It has to be JDK first, and then application classes. Please refer to the user guide for exact details. If the LR / JDK classes are not loaded first, the interactions may not be listed.
5. CLASS DUMPING : Under the logs option, use the class dump feature. Save the script, and check the folder to see if the classes are being dumped. If the dumped classes are not included in the USER.HOOKS, they may not be recorded. Although I suspect that this is only a problem you will need to deal with later. If there are no events, then the issue is up in the steps above than here. Coz, if the JDKs IIOP and CORBA classes are being called, you should be able to see scripts, even when using your own custom JARS, provided they are implementing the standard Java IIOP provisions.
6. MORE OFTEN than not, its the JARS, CLASSPath and BATCH file which is causing your problems. Also please check if the JDK you are using is supported by the VUGEN version.
Regards,
AJ