Virtualization

Hello,

It can use anything else laid down in the operating system - such as File type associations or shortcuts - to reference other packages

But it does not run without that but during capturing it was running smoothly. Actually while capturing the application used java 5.11 but when the application package is accessed from the app-v client it calls for J2RE 4.2 and installs all the files from the server. Now this J2RE is a old App-V package which resides in the server package list. The application calls the J2RE 4.2 in place of Java 5.11.

Is it possible to install both client and sequencer in the same machine. I am using APP-V 4.5 sp1.

Client and sequencer on the same machine never worked in the past - not good for your capture in any case.
For your problem, have you tried to assess the behaviour with a manual insall on a clean machine with no java and see what it requires and then install that version as a pre-req. Examine runtime behaviour and finally sequence the app with the version of java in the bubble on a machine with no previous install of java.
S

Baneerji just wanted to know why you would want to install both of them in the same machines??? any client specific requirement is there?

guys,
the thing is that. The application requires Java. So in the package I have put java 5.22 and it works fine. There is a child application which is used with this. while sequencing the child application runs using the java 5.22 and runs fine. So i capture and put it in the management console as usual. now when i run the application from a client it used the 5.22 java residing inside the package but when the child application is launched it calls in Java 4.2 which happens to be another App-V package residing in the management console. Though during packaging it launches using 5.22 but during testing from client it calls in 4.2. The obvious solution to this would be to make the Java 4.2 unavailable to the client by revoking permission but if I do that the child application fails to launch from client.

I am confused as during packaging I have never touched or mentioned or did anything at all with the 4.2 java, rather the first time I was not aware that that kind of java 4.2 exist in the App-V management console. Its after a failure in testing I found out from logs that the child application is trying to fetch 4.2 java and as it does not have access it is failing.

Thanks
Arun

i believe that the old java package (4.2 java) is an app v package and hence open the OSD of this application and copy the package Guid and search for the same in your new application and are there instances of "Merge with Local" and "Local Interaction=TRUE" if soo please remove them.....this may not work too!!

One more question how your application is calling another app V package(java 4.2) still remains a mystery to me....unless thers a DSC...

Cheers
Aj

Baneerji...could do one thing,,,use a pre launch script and access the virtual bubble and then check the version of javaw.exe which you have captures