INSTALLATION INSTRUCTIONS ObjectSpace Voyager 3.1 ====================================================================== CONTENTS ====================================================================== Voyager Installation Installation Installation Troubleshooting Running Voyager Tools Compiling Voyager Examples ====================================================================== VOYAGER INSTALLATION ====================================================================== IMPORTANT: Please make sure you understand the Copyright and License information (in the files named COPYRIGHT.TXT and LICENSE.TXT) before installing this release. This section provides instructions on installing and configuring Voyager. INSTALLATION ---------------------------------------------------------------------- The following sections describe the installation and initial setup of Voyager. The installation directory is subsequently referred to as $(INSTALL_ROOT). Windows 9x and Windows NT InstallShield Distribution ---------------------------------------------------- Execute the InstallShield executable which will perform the installation and unpack the distribution. It will query for needed information such as the installation root directory. Generic .ZIP Distribution ------------------------- Unzip the .ZIP distribution using any .ZIP capable utility. The .ZIP distribution contains only two files, a .class file and a small readme. From the directory where you unzipped the distribution run "java voyager3_1" to launch the generic InstallShield installation program. Unix .tar.Z and .tar.gz Distribution ------------------------------------ Uncompress and untar the Unix distributions using compress and tar for the .Z version and gunzip and tar for the .gz version. The Unix distributions contain only two files, a shell script and a small readme. Follow the instructions in the readme to correctly set the permissions on the shell script and run it to launch the Unix InstallShield installation program. NOTE: If you experience problems with 'gunzip', try using 'gzip -d'. Manually Setting the PATH and CLASSPATH --------------------------------------- The PATH and CLASSPATH environment variables must be modified manually after installation. If you are using Windows 95/98 , you must edit C:\AUTOEXEC.BAT. If you are using Windows NT, open Control Panel->System and select the Environment tab. If you are using a Unix system, the particular file to be modified is dependent on the particular version of Unix and command shell you are using. Please contact your system administrator if you are unsure how to modify the environment correctly. InstallShield generates a file called environment.txt that is placed in the install root. This file contains the CLASSPATH and PATH entries that must be added to your environment. NOTE: The Dynamic XML feature included in this release requires the IBM XML parser, XML4J. This product may be downloaded free from the IBM website at http://www.alphaworks.ibm.com/tech/xml4j. INSTALLATION TROUBLESHOOTING ---------------------------------------------------------------------- Voyager will run properly on an isolated Windows host. Localhost will resolve properly to the localhost address. However, Windows network settings must be set properly for the TCP stack. If a DNS entry for a host is incorrect, localhost might not always resolve to the correct IP number of the host. In this case, a Voyager program might seem to be started correctly but is unavailable to clients. Check the IP number printed by the Voyager program after Voyager is started from the commandline with the -l verbose switch. For example, at the command prompt, type voyager -l verbose 8000 If it differs from the correct IP number of the localhost, then the DNS entry needs to be corrected. If the Voyager server can not load class files from the directory in which it was started, add the current directory to the CLASSPATH environment variable. By default the Voyager server is only able to locally load classes which the Java virtual machine can find through the CLASSPATH. Files which exist in no specific package (the default package) in the directory the Voyager server is started in require the "." CLASSPATH entry which refers to the current directory. See the User Guide for examples on how to extend the Voyager server class search path. RUNNING VOYAGER TOOLS ---------------------------------------------------------------------- The Voyager tools and runtime may be run from the command line. Note that there are executable binaries for Microsoft Windows, and shell scripts for Unix platforms. Brief descriptions of the Voyager tools follow. For complete documentation, please refer to the appropriate developer guide. Interface Generator (igen) -------------------------- The Interface Generator is invoked with the command igen. This utility creates interfaces from .class or .java files. Proxy Generator (pgen) ---------------------- The Proxy Generator is invoked with the command pgen. It generates proxy class files from .class or .java files. Code Generator (cgen) --------------------- The Code Generator is invoked with the command cgen. It converts between CORBA .idl files and Java .class and .java files. Voyager ------- A Voyager server may be started with the voyager command. It provides a simple, non-programmatic way to start a Voyager server. Dynamic XML Interface Generator (xgen) -------------------------------------- The Dynamic XML Interface Generator is invoked with the command xgen. It generates Java interface files from DTD files. The generated interfaces correspond to the constructs in the DTD. The interfaces are used by the developer to access XML documents. ACL Installation Utility (aclinst) ---------------------------------- The ACL Installation tool is used to install a BasicPolicy ACL into a directory server.