Symptoms
The Client for Java fallback check box option is not available in Web Interface 4.6. This is due to the introduction of the client auto detection feature.
Resolution
The following configuration under client deployment in Web Interface 4.6 allows any user connecting to the site that does not have a client installed, but has JVM, to automatically use the Java Client to launch the application.
The Java Client deployment occurs without any user interaction and is similar to the feature called “Automatic fallback to the Client for Java” available in previously released versions of Web Interface.
Make sure that the users’ Internet browser is set to accept pop-up windows when accessing Web Interface.
1. Go to the Web Interface node and select the Web Interface site.
2. Under Common Tasks, select Manage Client Deployment.
3. From Manage Client Deployment, go to General > Client Detection and select the Perform client detection at logon check box.
4. Under the Display client detection notification options, select the Only if applications cannot be launched radio button.
5. Under Remote > Client Availability, select the following clients:
• Native client
• Embedded native client
• Client for Java
However, if you are using a Dual mode streaming site, under Default launch method, make sure that the Use remote client option is selected. Otherwise, Web Interface does not fallback to use Java and only uses the native client to launch remote applications which results in the client being prompted to save the ICA file when trying to launch the application.
