When deciding what type of application profile to setup it is important to determine if the application communicates with the Java runtime at TCP/IP level or uses Java RMI. Java at RMI If your Java application uses Java RMI please setup an application profile as shown in the image below: The main feature to be concerned when setting up a Java RMI application profile is the list of Java protocol selections and hooking option that are made available to successfully hook and record your Java application. Java Virtual Machine hooking - This option is used when you need to hook into a JVM. This option should be the default when you need to record Oracle Forms on Socket level. Network only - This option is used to only hook (catch) class and jar files that are downloaded via HTTP. This option was the default used in early versions of Silk Performer when recording against Jacada applications. Manual - This option should only be selected if you have manually prepared a startup script to record your Java application. Note: To record at Java RMI level a separate protocol license is needed. Java at TCP/IP If the application uses TCP/IP please use the application profile shown below. To set up an application profile open Silk Performer and go to: SETTINGS| SYSTEM | RECORDER | APPLICATION PROFILE Select the Add new button Give an application name for reference purposes In the application path field browse to your Java.exe or Javaw.exe* The application type will be CUSTOM and the Protocol API selection will be Web Click the Web Settings button and ensure ws2_32.dll is chosen Your application profile should be similar to this: After you have set up the application profile you should launch the Silk Performer recorder from the toolbar instead of using the Model Script button. To do this choose: RECORD | RECORDER This action will launch the recorder without automatically launching the application. After doing this you should start your application manually (i.e. from a shortcut, start menu entry etc..). Java Web Start at TCP/IP level If the application uses Java Web Start please use the application profile as shown above, but please change the application path to point to the javaw.exe instead of the java.exe. The reason for this is that Java Web Start applications send the traffic via the javaw.exe Note: When using task manager to check which executable the application uses, you may notice that the javaws.exe process appears to launch. Please DO NOT hook this process. The javaws.exe is just a launcher process which is responsible for automatic updates, determines which JVM to use etc .... When recording a Java Web Start application, please hook the javaw.exe process. Java application that requires batch file or command line input If the application you are testing requires batch file or input cmd line parameters then you should be aware that you should not launch the application profile from the work flow bar option "Model Script" but instead you should use the menu Record | Recorder and then start the application manually. The reason for this is that when passing in parameters to the application you need to set these in the application profile and the "Model Script" launch of the application does not set these options. *For full details on whether to choose Java.exe or Javaw.exe refer to Which executable should I hook to record my Java application, Java.exe or Javaw.exe? . Old KB# 18076
↧