Thanks Joe!

Marcie Sirbaugh

One more question regarding this issue, I read the help test and it's

a bit confusing, perhaps you can clarify:

Prerequisites to Launch Topology Services

To access Campus Manager Topology Services, we recommend that you install Java Plug-in version 1.6.0_11. If the client machine is installed with the JRE Update version equal to or higher than the recommended version, then Topology Services is launched in the client machine.

If the client machine is installed with an Update version equal to or higher than the recommended JRE version (1.6.0_11), then Topology Services will be launched only if either one of two versions is selected.

If the user selects the recommended JRE as well as the higher Update version of JRE, Topology Services will be launched with the higher Update version of JRE.

For example, CM 5.2 requires JRE 1.6.0_11 to launch Topology Services. If the client machine is installed with an Update version higher than JRE 1.6.0_11, say 1.6.0_12, and user selects JRE 1.6.0_12, then Topology Services is launched with JRE 1.6.0_12.

My understanding is that if I have a version higher than update 11, topology services will open with that version.  I have update 17 loaded and selected in the control panel, however, when I try to open TS I get the Installation of Java.....window opening.  Do I need update 11 in addition to any other java loaded?  or should it load with update 17 only?

LMS 3.2 should launch with any JPI greater than or equal to 1.6.0_11.  This came about due to bug CSCsy29287.  Exactly what window are you seeing?  Post a screenshot.

Here is a screenshot:

Marcie Sirbaugh

You may need to reinstall JPI 1.6.0_17.  The code in LMS checks the browser's configured MIME types to see that Java Web Start is properly installed.  It's looking for the MIME type application/x-java-applet;version=1.6 or application/x-java-applet;version=1.6.0.  You should also check IE > Tools > Internet Options > Advanced to make sure you have checked the box to enable JPI 1.6.0_17 for tags.

I believe the JPI is installed correctly, there have been restrictions placed on the configuration in this environment. See below of specific configurations that have been put into place...do you see any that would affect the launching of java?

#deployment.properties

#Wed Dec 09 14:32:00 DST 2009

deployment.browser.path=C\:
Program Files
Internet Explorer
iexplore.exe

deployment.browser.vm.iexplorer = true

deployment.browser.vm.iexplorer.locked

deployment.browser.vm.mozilla = false

deployment.cache.jarcompression.locked

deployment.cache.jarcompression=3

deployment.cache.jarcompression=5

deployment.cache.max.size.locked

deployment.cache.max.size=500

deployment.cache.max.size=500

deployment.capture.mime.types=true

deployment.console.startup.mode=hide

deployment.console.startup.mode=hide

deployment.control.panel.log = True

deployment.control.panel.log=True

deployment.javapi.cache.update = false

deployment.javapi.cache.update=true

deployment.javapi.lifecycle.exception = false

deployment.javaws.associations.locked

deployment.javaws.associations=never

deployment.javaws.associations=never

deployment.javaws.autodownload.locked

deployment.javaws.autodownload=NEVER

deployment.javaws.autodownload=NEVER

deployment.javaws.cache.update=true

deployment.javaws.home.jnlp.url =

deployment.javaws.installURL.locked

"deployment.javaws.installURL="""""

"deployment.javaws.installURL="""""

deployment.javaws.jre.0.args=

deployment.javaws.jre.0.enabled=true

"deployment.javaws.jre.0.location="""""

deployment.javaws.jre.0.osarch=x86

deployment.javaws.jre.0.osname=Windows

deployment.javaws.jre.0.path=C\:
Program Files
Java
jre6
bin
javaw.exe

deployment.javaws.jre.0.platform=1.6

deployment.javaws.jre.0.product=1.6.0_17

deployment.javaws.jre.0.registered=true

deployment.javaws.muffin.max = 256

deployment.javaws.shortcut.locked

deployment.javaws.shortcut=NEVER

deployment.javaws.shortcut=NEVER

deployment.javaws.ssv.enabled = False

deployment.javaws.ssv.enabled=False

deployment.javaws.uninstall.shortcut = false

deployment.jpi.mode.new=false

deployment.proxy.bypass.list.locked

deployment.proxy.override.hosts.locked

deployment.proxy.type.locked

deployment.proxy.type=3

deployment.repository.askdownloaddialog.show = false

deployment.repository.askdownloaddialog.show = False

deployment.repository.askdownloaddialog.show=False

deployment.repository.enabled = false

deployment.repository.enabled=false

deployment.security.askgrantdialog.notinca.locked

deployment.security.askgrantdialog.notinca=false

deployment.security.askgrantdialog.notinca=false

deployment.security.askgrantdialog.show.locked

deployment.security.askgrantdialog.show=false

deployment.security.askgrantdialog.show=false

deployment.security.authenticator = true

deployment.security.browser.keystore.use = true

deployment.security.browser.keystore.use.locked

deployment.security.clientauth.keystore.auto = true

deployment.security.clientauth.keystore.auto.locked

deployment.security.expired.warning.locked

deployment.security.expired.warning=True

deployment.security.expired.warning=True

deployment.security.https.warning.show = true

deployment.security.https.warning.show.locked

deployment.security.https.warning.show=true

deployment.security.jsse.hostmismatch.warning = true

deployment.security.jsse.hostmismatch.warning.locked

deployment.security.notinca.warning = true

deployment.security.notinca.warning.locked

deployment.security.password.cache.locked

deployment.security.password.cache=false

deployment.security.password.cache=false

deployment.security.pretrust.list = true

deployment.security.pretrust.list.locked

deployment.security.pretrust.list=true

deployment.security.sandbox.awtwarningwindow = true

deployment.security.sandbox.awtwarningwindow.locked

deployment.security.sandbox.jnlp.enhanced = False

deployment.security.sandbox.jnlp.enhanced.locked

deployment.security.sandbox.jnlp.enhanced=False

deployment.security.SSLv2Hello = false

deployment.security.SSLv2Hello.locked

deployment.security.SSLv3 = true

deployment.security.SSLv3.locked

deployment.security.TLSv1 = true

deployment.security.TLSv1.locked

deployment.security.trusted.policy =

deployment.security.validation.crl = True

deployment.security.validation.crl.locked

deployment.security.validation.crl=True

deployment.security.validation.ocsp = True

deployment.security.validation.ocsp.locked

deployment.security.validation.ocsp=True

deployment.system.tray.icon.locked

deployment.system.tray.icon=false

deployment.update.mime.types = true

deployment.version=6.0

Marcie Sirbaugh

I don't think that these settings would prevent the JavaScript code from detecting the JPI.  Do you have the box checked under IE > Tools > Internet Options > Advanced to use JPI 1.6.0_17 for tags?  You could also try installing Firefox 3.0, and see if it can launch topology.

Yes, I have the applet tag selected in the browser and unfortunately Firefox has not been approved to work in our environment....anything else you can think of to check?

Marcie Sirbaugh

You could try setting your security level to low in IE for your LMS server's zone.  As I said, the Campus code must be able to read the installed MIME types in the browser (using JavaScript), and the "application/x-java-applet;version=1.6" must exist.

As for Firefox, simply testing to see if it works would let you know if you have a plug-in problem vs. a browser problem.  Note: you may need to reinstall JPI 1.6.0_17 before trying.

Hi Joe,

This is still a very big issue for us, we are completly unable to work with Topology Services at this point.  We are narrowing the issue down, I believe it must have something to do with LMS not being able to read the installed MIME types in the browser (using JavaScript), and the "application/x-java-applet;version=1.6".  Is there a registry entry on the Windows PC where it reads this?  I have done a workaround that seems to work, but not going to proceed in production environment with it, but it might help in troubleshooting.  I changed the following file:

topoServices.jsp

This seems to tell LMS that java is there and then it proceeds to using it....otherwise it can't find it.  I'm wondering when update 17 was installed, if when it uninstalled the previous version of 1.6, it corrupted something and it wasn't completely removed, causing conflict somewhere.

Any thought?  thanks, Marcie

Try creating a virgin user account on this machine.  Then see if the problem persists.  If it does, try another machine with JPI 1.6.0_17 to rule out problems with the plug-in.  I have a feeling the problem will be localized to one account or one machine at the most.