JSPWiki/Glassfish Install (Part 6 of 18: Preliminary Directory)

Some of the packages downloaded in an earlier step do not have installers. We will have to manually copy (drop and drag) some of the files contained there in to their proper locations. Some of the packages will need to be decompressed and perhaps even renamed.

Some of these packages will have installers but the installers will have pre-established default locations. Where this happens we will likely override the default install locations.

As we progress I will write a “part” that pertains to installing each of the packages we will be using. Ultimately, each of these packages will end or be installed into a sub-directory of C:\java [all lower case]. For the most part any new sub-directory (a.k.a sub-folder) we create will be in LOWERCASE letters and will contain NO SPACES.

My desire is to have all the software we will install in one location with a clean and easy to understand directory structure. The benefit I anticipate from taking a little extra time during the install is that when we attempt to troubleshoot or expand the use of our Glassfish installation at a later time we’ll quickly be able to navigate to any location of interest.

When completed our install directory will look something like:

C: java
\–ant-version
\–glassfish-version
\–jdk-version
\–jre-version
\–jspwiki-storage
\–other-stuff-version
\–and-so-on-version

Go ahead and create the initial “java” directory now.

  1. Double click on the “My Computer” icon
  2. Double click on the “C:” drive icon
  3. Right click in the “C:” drive window and choose New –> Folder
  4. Name this folder: “java” — all lower case

As we install packages you will want to adjust your path/folder names to compensate for the specific versions you are actually installing. However, I wouldn’t recommend installing any versions of the packages discussed here if they are older than the versions I’m using for this walk through. Sun, and Apache for that matter, seems to put a lot of effort into ensuring backward compatibility so chances are you’ll be OK with newer versions of these packages as they are released.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s