Running javaws.exe which is the client for JNLP applets the way i want depending on what i need, if i need to profile an application for streaming i will do:īoth the above cache the jnlp to system cache i pre-configured earlier Then I create the folder C:\Java_System_cache
#CITRIX XENAPP 6.5 BUILTIN LOAD EVALUATOR CODE#
In the code above i have 2 versions of JRE installed and it is found in every user’s profile.Īll i did was copy the file and appending it with these 2 parameters: We can do that by using the following JRE tools:ĭnfig – this file when placed in a certain location can pre-determine the configuration of the JRE environmentĭ=file\:C\:/WINDOWS/Sun/Java/Deployment/deployment.propertiesĭeployment.properties – this file when placed in a certain location can pre-determine the cache folder locationĭ=C:\\Java_System_Cacheĭ=360,189,720,360ĭ=C\:\\Program Files (x86)\\Internet Explorer\\iexplore.exeĭ.1.location=http\:///products/autodl/j2seĭ.0.path=C\:\\Program Files (x86)\\Java\\jre7\\bin\\javaw.exeĭ.1.path=C\:\\Program Files (x86)\\Java\\jre6\\bin\\javaw.exeĭ.0.location=http\:///products/autodl/j2se Let’s get on with it, what we want to do is instead of having the user go in to the application and have the JNLP cached to the user context we will want to either set rules for the caching in the JRE or pre-cache it for them on a SYSTEM context and have it available for all users on that machine. Please note: I will refer to Citrix Application Streaming version but the principles apply to other virtualization technologies.
This provides a huge advantage for us administrators to deliver an application on a System context on machines, such as XenApp Servers, Multi-User workstations and of course streamed environment. Part 1: JNLP Applets and Application streamingīeginning from the a certain JRE version options became available for the JNLP cache to be either in USER or SYSTEM context, After a long hiatus from this blog and being busy busy busy in other projects it’s time to complete this guide,