Australian Personal Computer 2000 October

home *** CD-ROM | disk | FTP | other *** search

/ Australian Personal Computer 2000 October / tst.iso / programs / sun / install < prev next >

Wrap

Text File | 2000-05-26 | 33.9 KB | 833 lines

Forte(tm) for Java(tm) Community Edition Installation ----------------------------------------------------- To see the installation FAQ, which includes troubleshooting questions, and any installation note updates, check the Forte for Java web site at http://www.sun.com/forte/ffj/ce/index.html. ------------------------------------------------------------------ System Requirements To run successfully, the installation procedures require a Java(tm) 2-compatible virtual machine (JVM) installed on your system. If you do not yet have a Java 2-compatible (Java 2 SDK, Standard Edition) JVM, you should install one prior to running the Forte for Java installation. Intel x86/Microsoft Windows Platform Hardware Minimum configuration: Microsoft Windows 95, 98, 2000, or NT with a P133 processor, 64 megabytes of RAM, and 30 megabytes of free disk space. Recommended configuration: Microsoft Windows 95, 98, 2000, or NT with a P300 processor and 128 Mbytes of RAM. Optimal configuration: Microsoft Windows 95, 98, 2000, or NT with a P300 processor and 192 Mbytes of RAM. Note: If you are running on a Microsoft Windows system with 64 Mbtytes of memory, it is recommended that you set the maximum Java heap size to 48 Mbytes to prevent disk swapping. Set the configuration file (forte4j.cfg) startup flag to -Xmx48m. Software Forte for Java, Community Edition, requires a Java 2-compatible JVM, version 1.2.2. Preliminary testing shows that it also runs well with the JDK 1.3 Beta version. The JavaTM 2 SDK, Standard Edition, for the Windows environment is available for download from http://java.sun.com/products/jdk/1.2/ (v. 1.2) and http://java.sun.com/products/jdk/1.3/ (v. 1.3 release candidate). SPARC/Solaris Platform Hardware When running on the Solaris platform, you should have at least 30 Mbytes of free disk space. Minimum configuration: SparcStation 5: 170 Mhz, 128 Mbytes of RAM. Recommended configuration: UltraSPARC 5: 333 Mhz, 256 Mbytes of RAM. Optimal configuration: UltraSPARC 10: 440 Mhz, 512 Mbytes of RAM. Software Forte for Java, Community Edition requires the JavaTM 2 SDK, v. 1.2.1 for the Solaris environment. The latest SDK is available for download from http://www.sun.com/solaris/java/. Linux Platform The Linux JVM is more resource-intensive than the Windows JVM, so Linux users may want to have a higher memory configuration. The latest SDK is available for download from http://java.sun.com/products/jdk/1.2/download-linux.html. ------------------------------------------------------------------ Installation Procedures There are several installation formats of Forte for Java, Community Edition. The software in each of these formats is identical; it is merely bundled in different installation formats for ease of use on different platforms. Use the format provided for your platform, or use the Java class installation, which runs on all platforms. Before you begin, the Java 2 SDK, Standard Edition, v1.2 must be installed on your system. If you do not have it, you will need to download and install this software before you can run the Forte for Java installation routine. The software can be found at http://java.sun.com/products/jdk/1.2/. NOTE: If you are installing Forte for Java in a multi-user environment, see the instructions provided in the Shared Installation section. Microsoft Windows Platform 1. Double-click the forte_ce_1_0.exe file to launch the InstallShield routine. The install routine will attempt to locate a Java 2 virtual machine on your system; if it fails to locate one, you must browse to locate one before continuing. 2. Follow the InstallShield dialogs as normal. Once installation is complete, you will have a shortcut to Forte for Java on your desktop. On your Start menu, you'll also have a Forte for Java entry containing shortcuts to the Community Edition README file and the Forte for Java web site. Four EXE files will be available in the bin folder for launching Forte for Java: * forte4jw.exe - launches Forte for Java without a console window. This launcher is used when you launch the IDE from the shortcut on the Desktop or Start menu. * forte4j.exe - launches Forte for Java with a console window that includes standard error and standard output from the IDE. On the console, you can press CTRL+BREAK to get a thread dump or CTRL+C to immediately terminate the program. * forte4jw_multiuser.exe - launches a multi-user version of Forte for Java without a console window. When you first run this executable, you are prompted to enter a directory where your files will be stored. This information will be placed in your Windows registry, so that the directory you specify in the prompt will be used whenever you launch the IDE in the future. * forte4j_multiuser.exe - launches a multi-user version of Forte for Java with a console window. UNIX/Solaris Platform 1. Change your working directory to the location where you've saved the forte_ce_1_0.sh file. 2. Launch the installation by typing the command: $ sh forte_ce_1_0.sh The installation program will attempt to locate a Java 2 virtual machine on your system. The software displays a menu listing any JVM found and gives you the option to specify another virtual machine. 3. Follow the InstallShield dialogs as normal. Specify a location within your home directory as the installation directory. 4. Once the installation is complete, launch Forte for Java using the forte4j.sh script in the bin subdirectory of your installation directory: $ sh forte4j.sh Linux Platform The Linux installation is an RPM (Red Hat Package Manager) format. If RPM is not supported by your Linux distribution or you have problems using RPM, use forte_ce_1_0.class (the Java class installer) or forte_ce_1_0.sh (the UNIX/Solaris installer) instead. 1. Become root. 2. Open a command prompt and change the working directory to the location of the ForteCE-FCS-1_0.noarch.rpm installation file. 3. Launch the installation: rpm -i ForteCE-FCS-1_0.noarch.rpm 4. When the RPM file is installed, you can run Forte for Java by typing forte4j on the command line. Class Install for All Platforms 1. Change your working directory to the location where you have saved the forte_ce_1_0.class file. 2. If you have a CLASSPATH set, and it does not include the current directory, add the current directory to your existing CLASSPATH. If you do not have a CLASSPATH set, skip to the next step. (To check whether you have a CLASSPATH currently set, type set at a command prompt. If you see CLASSPATH listed, you have a CLASSPATH setting.) o To add the current directory to your CLASSPATH on a Windows machine, type: set CLASSPATH=.;%CLASSPATH% o On a UNIX machine with a Bourne-type shell (which typically gives a $ prompt), type: CLASSPATH=.:$CLASSPATH;export CLASSPATH o On a UNIX machine with a C-type shell (which typically gives a % or > prompt), type: setenv CLASSPATH .:$CLASSPATH 3. Type the following command to launch the InstallShield installation routine (do not include the .class extension): java forte_ce_1_0 This assumes you have a Java 2 virtual machine in your path. If not, you must specify the full path to the java interpreter executable. For example: C:\TEMP>C:\jdk1.2\bin\java.exe forte_ce_1_0 4. Follow the InstallShield dialogs as normal. 5. Once the installation is complete, use the launch script in your installation directory to launch Forte for Java. If you installed the software on a Microsoft Windows machine, you will have shortcuts for launching Forte for Java on your desktop and under the Start menu. Shared Installation This type of installation requires a user who can act as the administrator and who is responsible for maintaining, upgrading, and installing new modules. Module upgrades and installation of new modules should be performed by the administrator entirely within Forte for Java, using the Update Center. If a user who is not the administrator upgrades modules or installs new modules, the updates will be made only to that user's local installation directory, where personal settings and configuration files are stored. Other users will not be able to see or use the updated modules. Local modules are given preference to those in the shared installation, so if the administrator subsequently upgrades the same module to a newer version, the user will still have the older, local version. UNIX/Solaris Platform 1. As root user, install as described above in the UNIX/Solaris Platform section or the Class Install section. Install the software in a shared location, such as /usr/local/forte4j. 2. Change ownership of the forte4j directory tree to the administrator. If you have defined a user group, change ownership to also include that group: # chown -R f4jadmin.f4jusers /usr/local/forte4j 3. Set the permissions on the install directory: # chmod 750 forte4j 4. The installation routine generates a file called forte4j_multiuser.sh in the installation directory. Create a symbolic link to this file from /usr/local/bin/ (or anywhere in the $PATH): # ln -s ./forte4j_multiuser.sh /usr/local/bin/forte4j 5. Assuming users have /usr/local/bin in their $PATH, they can launch Forte for Java by typing forte4j on the command line. The first time a user launches the application on a multiuser installation, the launch script copies and creates configuration files under the user's $HOME/forte4j_user directory. Thereafter, each user keeps their settings and preferences files, and saves development files locally. Note: When initially starting Forte for Java, the administrator should start the application with the command in the bin directory. Users other than the administrator can then run Forte for Java as directed in Step 5. Windows NT Platform 1. Install the software on a Windows NT machine that will act as the server. Use the instructions in the Windows Platform section or the Class Install section. The installation directory should be write protected to normal users, but this is not mandatory. 2. Create a shared directory on the machine where you installed the product and map this onto the user's local machine as a network drive. 3. When the installation is complete, users should launch Forte for Java using forte4jw_multiuser.exe. The first time this is run, each user is prompted to enter a directory where their files will be stored. Note: When initially starting Forte for Java, the administrator should start the application with the forte4jw.exe command in the bin directory. Users other than the administrator can then run Forte for Java using the command forte4jw_multiuser.exe. Administrators who want to update modules in the central installation should use forte4jw.exe. ------------------------------------------------------------------ Command Line Switches On Windows machines, you can set options when running the IDE on the command line or by modifying the forte4j.cfg file that is in the bin folder of your installation directory. If you use the forte4j.cfg file, you can break the options into multiple lines. The loader tries to read this file before it starts parsing the command line options. This means that even Java applications options can be put in this file. On UNIX machines, you can modify the forte4j.sh file in the bin subdirectory of the installation directory, or you can create your own shell script that calls forte4j.sh with options. The following is a list of switches that you can use (either in a shell script or the forte4j.cfg file) when loading Forte for Java: * -jdkhome jdk_home_dir - use the Java 2 SDK specified in the jdk_home_dir argument instead of the default SDK. * -hotspot * -classic - use the classic JVM. By default, the HotSpot JVM is used. * -cp:p additional classpath - add the class path specified in the additional classpath parameter to the beginning of the Forte for Java class path. * -cp:a additional classpath - add the class path specified in the additional classpath parameter to the end of the Forte for Java class path. * -Jjvm_flags - pass the flag specified by the jvm_flags parameter directly to the JVM. There is no space between -J and the argument. * -ui com.sun.java.swing.plaf.windows.WindowsLookAndFeel - run the IDE with the Windows look and feel. * -ui com.sun.java.swing.plaf.motif.MotifLookAndFeel - run the IDE with the Motif look and feel. * -fontsize fontsize - set the font size used in the IDE's graphical user interface. ------------------------------------------------------------------ Installation Directories When you install Forte for Java on your machine, the following subdirectories are included in your installation directory: * beans - contains JavaBeans components installed in the IDE * bin - includes the IDE launchers (as well as the forte4j.cfg file on Windows installations); and addtopath.bat, which is used by the batch file startup. * Development - the directory mounted by default in Filesystems. Objects you create in the IDE will be saved here unless you mount other directories in the IDE and use them instead. * docs - contains the HTML files for the User's Guide, QuickStart Guide, and Tutorials. * javadoc - the directory mounted by default in the IDE's Javadoc repository. Javadoc documentation that you create in the IDE will be stored here. * lib - contains JAR files that comprise the IDE's core implementation and the open APIs. * lib/ext - contains extensions to the IDE for things such as JavaHelp, Absolute Layout, javac, and regular expressions. * lib/patch - any JAR or ZIP file included in this folder will be automatically included at the beginning of the IDE's startup class path. That is, it will be a patch against the core. * modules - any JAR file in this folder is an IDE module. The ext subdirectory contains libraries used by modules. * sources - sources for libraries which may be redistributed with user applications. * system - includes files and directories used by the IDE for special purposes. It includes forte4j.log, which provides information useful when seeking technical support, and project.basic and project.last, which contain information on Forte for Java projects. It is mounted in the IDE as a hidden file system. Subdirectories include system/parserDB, which holds databases that are used for Java code completion and other Editor functions, Startup (holds classes that are run at IDE startup), Actions (IDE actions which appear in Global Options under Actions), applet (policy file for debugging applets), and Bookmarks (web bookmarks). --Volery_of_Birds_100_000-- Forte(tm) for Java(tm) Community Edition Installation ----------------------------------------------------- To see the installation FAQ, which includes troubleshooting questions, and any installation note updates, check the Forte for Java web site at http://www.sun.com/forte/ffj/ce/index.html. ------------------------------------------------------------------ System Requirements To run successfully, the installation procedures require a Java(tm) 2-compatible virtual machine (JVM) installed on your system. If you do not yet have a Java 2-compatible (Java 2 SDK, Standard Edition) JVM, you should install one prior to running the Forte for Java installation. Intel x86/Microsoft Windows Platform Hardware Minimum configuration: Microsoft Windows 95, 98, 2000, or NT with a P133 processor, 64 megabytes of RAM, and 30 megabytes of free disk space. Recommended configuration: Microsoft Windows 95, 98, 2000, or NT with a P300 processor and 128 Mbytes of RAM. Optimal configuration: Microsoft Windows 95, 98, 2000, or NT with a P300 processor and 192 Mbytes of RAM. Note: If you are running on a Microsoft Windows system with 64 Mbtytes of memory, it is recommended that you set the maximum Java heap size to 48 Mbytes to prevent disk swapping. Set the configuration file (forte4j.cfg) startup flag to -Xmx48m. Software Forte for Java, Community Edition, requires a Java 2-compatible JVM, version 1.2.2. Preliminary testing shows that it also runs well with the JDK 1.3 Beta version. The JavaTM 2 SDK, Standard Edition, for the Windows environment is available for download from http://java.sun.com/products/jdk/1.2/ (v. 1.2) and http://java.sun.com/products/jdk/1.3/ (v. 1.3 release candidate). SPARC/Solaris Platform Hardware When running on the Solaris platform, you should have at least 30 Mbytes of free disk space. Minimum configuration: SparcStation 5: 170 Mhz, 128 Mbytes of RAM. Recommended configuration: UltraSPARC 5: 333 Mhz, 256 Mbytes of RAM. Optimal configuration: UltraSPARC 10: 440 Mhz, 512 Mbytes of RAM. Software Forte for Java, Community Edition requires the JavaTM 2 SDK, v. 1.2.1 for the Solaris environment. The latest SDK is available for download from http://www.sun.com/solaris/java/. Linux Platform The Linux JVM is more resource-intensive than the Windows JVM, so Linux users may want to have a higher memory configuration. The latest SDK is available for download from http://java.sun.com/products/jdk/1.2/download-linux.html. ------------------------------------------------------------------ Installation Procedures There are several installation formats of Forte for Java, Community Edition. The software in each of these formats is identical; it is merely bundled in different installation formats for ease of use on different platforms. Use the format provided for your platform, or use the Java class installation, which runs on all platforms. Before you begin, the Java 2 SDK, Standard Edition, v1.2 must be installed on your system. If you do not have it, you will need to download and install this software before you can run the Forte for Java installation routine. The software can be found at http://java.sun.com/products/jdk/1.2/. NOTE: If you are installing Forte for Java in a multi-user environment, see the instructions provided in the Shared Installation section. Microsoft Windows Platform 1. Double-click the forte_ce_1_0.exe file to launch the InstallShield routine. The install routine will attempt to locate a Java 2 virtual machine on your system; if it fails to locate one, you must browse to locate one before continuing. 2. Follow the InstallShield dialogs as normal. Once installation is complete, you will have a shortcut to Forte for Java on your desktop. On your Start menu, you'll also have a Forte for Java entry containing shortcuts to the Community Edition README file and the Forte for Java web site. Four EXE files will be available in the bin folder for launching Forte for Java: * forte4jw.exe - launches Forte for Java without a console window. This launcher is used when you launch the IDE from the shortcut on the Desktop or Start menu. * forte4j.exe - launches Forte for Java with a console window that includes standard error and standard output from the IDE. On the console, you can press CTRL+BREAK to get a thread dump or CTRL+C to immediately terminate the program. * forte4jw_multiuser.exe - launches a multi-user version of Forte for Java without a console window. When you first run this executable, you are prompted to enter a directory where your files will be stored. This information will be placed in your Windows registry, so that the directory you specify in the prompt will be used whenever you launch the IDE in the future. * forte4j_multiuser.exe - launches a multi-user version of Forte for Java with a console window. UNIX/Solaris Platform 1. Change your working directory to the location where you've saved the forte_ce_1_0.sh file. 2. Launch the installation by typing the command: $ sh forte_ce_1_0.sh The installation program will attempt to locate a Java 2 virtual machine on your system. The software displays a menu listing any JVM found and gives you the option to specify another virtual machine. 3. Follow the InstallShield dialogs as normal. Specify a location within your home directory as the installation directory. 4. Once the installation is complete, launch Forte for Java using the forte4j.sh script in the bin subdirectory of your installation directory: $ sh forte4j.sh Linux Platform The Linux installation is an RPM (Red Hat Package Manager) format. If RPM is not supported by your Linux distribution or you have problems using RPM, use forte_ce_1_0.class (the Java class installer) or forte_ce_1_0.sh (the UNIX/Solaris installer) instead. 1. Become root. 2. Open a command prompt and change the working directory to the location of the ForteCE-FCS-1_0.noarch.rpm installation file. 3. Launch the installation: rpm -i ForteCE-FCS-1_0.noarch.rpm 4. When the RPM file is installed, you can run Forte for Java by typing forte4j on the command line. Class Install for All Platforms 1. Change your working directory to the location where you have saved the forte_ce_1_0.class file. 2. If you have a CLASSPATH set, and it does not include the current directory, add the current directory to your existing CLASSPATH. If you do not have a CLASSPATH set, skip to the next step. (To check whether you have a CLASSPATH currently set, type set at a command prompt. If you see CLASSPATH listed, you have a CLASSPATH setting.) o To add the current directory to your CLASSPATH on a Windows machine, type: set CLASSPATH=.;%CLASSPATH% o On a UNIX machine with a Bourne-type shell (which typically gives a $ prompt), type: CLASSPATH=.:$CLASSPATH;export CLASSPATH o On a UNIX machine with a C-type shell (which typically gives a % or > prompt), type: setenv CLASSPATH .:$CLASSPATH 3. Type the following command to launch the InstallShield installation routine (do not include the .class extension): java forte_ce_1_0 This assumes you have a Java 2 virtual machine in your path. If not, you must specify the full path to the java interpreter executable. For example: C:\TEMP>C:\jdk1.2\bin\java.exe forte_ce_1_0 4. Follow the InstallShield dialogs as normal. 5. Once the installation is complete, use the launch script in your installation directory to launch Forte for Java. If you installed the software on a Microsoft Windows machine, you will have shortcuts for launching Forte for Java on your desktop and under the Start menu. Shared Installation This type of installation requires a user who can act as the administrator and who is responsible for maintaining, upgrading, and installing new modules. Module upgrades and installation of new modules should be performed by the administrator entirely within Forte for Java, using the Update Center. If a user who is not the administrator upgrades modules or installs new modules, the updates will be made only to that user's local installation directory, where personal settings and configuration files are stored. Other users will not be able to see or use the updated modules. Local modules are given preference to those in the shared installation, so if the administrator subsequently upgrades the same module to a newer version, the user will still have the older, local version. UNIX/Solaris Platform 1. As root user, install as described above in the UNIX/Solaris Platform section or the Class Install section. Install the software in a shared location, such as /usr/local/forte4j. 2. Change ownership of the forte4j directory tree to the administrator. If you have defined a user group, change ownership to also include that group: # chown -R f4jadmin.f4jusers /usr/local/forte4j 3. Set the permissions on the install directory: # chmod 750 forte4j 4. The installation routine generates a file called forte4j_multiuser.sh in the installation directory. Create a symbolic link to this file from /usr/local/bin/ (or anywhere in the $PATH): # ln -s ./forte4j_multiuser.sh /usr/local/bin/forte4j 5. Assuming users have /usr/local/bin in their $PATH, they can launch Forte for Java by typing forte4j on the command line. The first time a user launches the application on a multiuser installation, the launch script copies and creates configuration files under the user's $HOME/forte4j_user directory. Thereafter, each user keeps their settings and preferences files, and saves development files locally. Note: When initially starting Forte for Java, the administrator should start the application with the command in the bin directory. Users other than the administrator can then run Forte for Java as directed in Step 5. Windows NT Platform 1. Install the software on a Windows NT machine that will act as the server. Use the instructions in the Windows Platform section or the Class Install section. The installation directory should be write protected to normal users, but this is not mandatory. 2. Create a shared directory on the machine where you installed the product and map this onto the user's local machine as a network drive. 3. When the installation is complete, users should launch Forte for Java using forte4jw_multiuser.exe. The first time this is run, each user is prompted to enter a directory where their files will be stored. Note: When initially starting Forte for Java, the administrator should start the application with the forte4jw.exe command in the bin directory. Users other than the administrator can then run Forte for Java using the command forte4jw_multiuser.exe. Administrators who want to update modules in the central installation should use forte4jw.exe. ------------------------------------------------------------------ Command Line Switches On Windows machines, you can set options when running the IDE on the command line or by modifying the forte4j.cfg file that is in the bin folder of your installation directory. If you use the forte4j.cfg file, you can break the options into multiple lines. The loader tries to read this file before it starts parsing the command line options. This means that even Java applications options can be put in this file. On UNIX machines, you can modify the forte4j.sh file in the bin subdirectory of the installation directory, or you can create your own shell script that calls forte4j.sh with options. The following is a list of switches that you can use (either in a shell script or the forte4j.cfg file) when loading Forte for Java: * -jdkhome jdk_home_dir - use the Java 2 SDK specified in the jdk_home_dir argument instead of the default SDK. * -hotspot * -classic - use the classic JVM. By default, the HotSpot JVM is used. * -cp:p additional classpath - add the class path specified in the additional classpath parameter to the beginning of the Forte for Java class path. * -cp:a additional classpath - add the class path specified in the additional classpath parameter to the end of the Forte for Java class path. * -Jjvm_flags - pass the flag specified by the jvm_flags parameter directly to the JVM. There is no space between -J and the argument. * -ui com.sun.java.swing.plaf.windows.WindowsLookAndFeel - run the IDE with the Windows look and feel. * -ui com.sun.java.swing.plaf.motif.MotifLookAndFeel - run the IDE with the Motif look and feel. * -fontsize fontsize - set the font size used in the IDE's graphical user interface. ------------------------------------------------------------------ Installation Directories When you install Forte for Java on your machine, the following subdirectories are included in your installation directory: * beans - contains JavaBeans components installed in the IDE * bin - includes the IDE launchers (as well as the forte4j.cfg file on Windows installations); and addtopath.bat, which is used by the batch file startup. * Development - the directory mounted by default in Filesystems. Objects you create in the IDE will be saved here unless you mount other directories in the IDE and use them instead. * docs - contains the HTML files for the User's Guide, QuickStart Guide, and Tutorials. * javadoc - the directory mounted by default in the IDE's Javadoc repository. Javadoc documentation that you create in the IDE will be stored here. * lib - contains JAR files that comprise the IDE's core implementation and the open APIs. * lib/ext - contains extensions to the IDE for things such as JavaHelp, Absolute Layout, javac, and regular expressions. * lib/patch - any JAR or ZIP file included in this folder will be automatically included at the beginning of the IDE's startup class path. That is, it will be a patch against the core. * modules - any JAR file in this folder is an IDE module. The ext subdirectory contains libraries used by modules. * sources - sources for libraries which may be redistributed with user applications. * system - includes files and directories used by the IDE for special purposes. It includes forte4j.log, which provides information useful when seeking technical support, and project.basic and project.last, which contain information on Forte for Java projects. It is mounted in the IDE as a hidden file system. Subdirectories include system/parserDB, which holds databases that are used for Java code completion and other Editor functions, Startup (holds classes that are run at IDE startup), Actions (IDE actions which appear in Global Options under Actions), applet (policy file for debugging applets), and Bookmarks (web bookmarks).