Jmeeting Beta Site

From Jmeeting Wiki
Jump to: navigation, search

Contents

General Beta Info

To use the beta site, simply go to http://beta.jmeeting.com

Needless to say, being BETA it will be constantly in a state of change, but still we figure many will enjoy the chance to check out the beta site to see some of the up and coming features, and best of all, the enhanced cam speeds.

That said, to use the new beta site, you will need to be running the Java 7 runtime, unlike the old site that would run under Java 6.

So trying to get everything going, I ran into the issue of wanting to be able to use the new beta jmeeting standalone messenger, but also wanting to keep Java 6 compatibility with the old Jmeeting site, as well as a few other Java applications I used that don't seem to work under 7. I am personally running all of this on a Windows 7 x64 machine (granted everyone should load the i586 32-bit version of Java), so my instructions will be from this PC, but should in general be applicable to others as well.

The one big difference between a 64-bit machine, and a 32-bit machine is the programs directory, where on a 32-bit machine programs normally go into C:\Program Files on a 64-bit machine 32-bit software ends up in C:\Program Files (x86) as the 64-bit stuff goes in the normal program files directory.

Loading Java 7

You can choose to just remove Java 6, and load Java 7 if desired, and you don't have any reason for actually needing Java 6 any longer. At least here, I ran into the issue of having some applications that don't run correctly under Java 7, so needed to also keep a copy of Java 6 loaded as well. Now Java does support this, and they seem to imply it's simple to do, but between trying to do this, and using a little google-fu, I have found this is not the case.

So let's take a more detailed look at what I did to load Java on my machine, and how I handled the end configuration. First I went out and picked up the latest java at the time, which can always be found at http://java.sun.com , where you can get the latest Java SE for your computer. As I said I am running under Windows 7, so at the time the two files I acquired were jre-6u32-windows-i586.exe for Java 6, and then I picked up jre-7u3-windows-i586.exe for Java 7.

I then double clicked on the Java 6 executable and installed it on my system, verified Java 6 was loaded and available, and all was OK. Next I double clicked on the Java 7 executable, and installed it on my PC as well, again trying to start something that revealed Java 7 was being called. So both installs were good, but anything I tried to run that required Java ended up being run by Java 7.

If you want to verify both Java's are enabled, you can go into your Control Panel, then click on Java (32-bit), and click on the tab that says Java, and you should see:

Jcontrol-1.png

Now click on the View button in that window, and you will see:

Jcontrol-2.png

Note that in the window there is a check mark in both the 1.7 (Java7) and 1.6 (Java6) boxes. If you see both, then you will know both are installed and available on your system.

You can then click OK, and exit out of things as you now know your Java's are correctly installed.

Getting the beta Jmeeting Messenger (Standalone)

To get the Jmeeting Messenger, just go to http://beta.jmeeting.com and you should see the following on the left side of your screen:

Jbeta-1.png

As you can see from the above image, you can download the beta messenger, or even download Java 7, as links are provided.

When you download the messenger, it should save to a file called jmeeting-beta.jar it's important to save this to a place you will remember on your system, on mine I put it in C:\Programs\Jmeeting, but you can put it anyplace you desire.

So now that we have this saved, you should be able to right click on the jar file, and drag it out to your desktop. As you right clicked to drag it, when you drop it on the desktop, one of your options should be to create a shortcut to the file, select this.

Now you should have a shortcut pointing to jmeeting-beta.jar on your desktop, so now let's make sure it's setup to point to Java 7. So right click on the shortcut, and select Properties. Make sure you're on the Shortcut tab in properties, which it should be by default, but if not click on shortcut. You should get a screen that looks like this:

Jshortcut-1.png

If you look back at the Java installs as described earlier, you will see the paths available to Java 6 and Java 7, for the beta messenger we are concerned about Java 7. So per the image above, you need to make sure that you set the correct target path to run the program. On my system that path is "C:\Program Files (x86)\Java\jre7\bin\javaw.exe" -jar jmeeting-beta.jar Here is a second image showing the second half of the path to make things more clear.

Jshortcut-2.png

Also make sure the Start in: path points to wherever you saved (or moved) the jmeeting-beta.jar file to after you downloaded it from the site.

Now click OK, and save the changes to your shortcut, and after that you should be able to double click on the Jmeeting Beta Messenger and it should launch and run OK, or it did for me.

I want to have Java 6 as my default Java, so other apps I have can run

So after all of the above, the Beta Messenger should be running OK, but many will say, but now my Java 6 programs fail to run, and I want to do more than just run Jmeeting Beta.

This seems to be one of the biggest issues, or at least this was for me. Once I loaded Java 7, it didn't matter what I did, everything started under Java 7, and some apps break badly. I even went as far as to go into the control panel, and disable Java 7, but still no change. A little more research showed, that when Java 7 was installed, it took and copied out it's executables into the Windows system files area as the default Java programs. As Windows by default looks in the windows core files area for programs first, no matter what happened, it always used 7.

So how to fix this problem, well it took a little digging, but I found something that at least appears to work for me on my Windows 7 PC, and if you need this, hopefully it will for you as well.

The solution to this was to take and set a couple environment variables so they point to Java 6 by default, and then if I want to run Java 7, I can specify it like I did in the last section for the beta messenger.

OK, so let's setup the path to allow Java 6 to be your default for things, if you're running a java app. First go to Control Panel, System, and then click on Advanced System Settings. Once in the Advanced Settings, you should see the following:

Jadvance-1.png

Then you will want to click on the Environment Variables button to enter that section. Once in that section your screen should look something like this:

Jenv-1.png

Now by default you will not have a JAVA_HOME variable, but you will want to click on New under the system variables area, and add JAVA_HOME, and you will want it to point to wheverever your Java 6 is installed. In the case of my system, it was installed into the C:\Program Files (x86)\Java\jre6 folder, and I suspect your install will be close. As mentioned above if you're not on a 64bit machine, yours will probably just say Program Files without the x86 part added in the path.

Once you have set the JAVA_HOME variable, we have one more thing to do, and that is make sure that when windows searches for programs it looks for Java 6 before everything else. To do this, we need to edit the Path variable, which should exist in your system variables list. So scroll down in your variables listing till you find PATH, and then highlight it, and click Edit. In edit, you now want to go to the very start of the path statement (left arrow back to the start, and then add the following %JAVA_HOME%\bin; make sure you do it just like this, as messing up your path line may break trying to run all kinds of things. When done, it should look like this:

Jenv-2.png

Once that is complete, just click OK, and save your changes, and you should now have Java 6 as your default choice unless you specify it specifically.

I hope this helps some get things running as desired, as the beta is looking good, and hopefully will become the new and improved Jmeeting in the near future. As always, if you get stuck on something, you can always stop into #TechSupport if your on Jmeeting, or drop an email to Jmeeting Support


Click here to let us know if this wasn't helpful

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox