JacORB 1.2.2

		Installing and Building JacORB

_____________________________________________________________________

Required: 

	- JDK 1.1 or later

	- if your are using JDK 1.1 and want to use any GUI features
	  at all, you need to install the swing classes (aka Java 
	  Foundations Classes JFC) downloadable from http://java.sun.com

	- for IIOP over SSL:
	  IAIK crytography provider and SSL implementation

	- for rebuilding JacORB or compling the demos:
	  the Jakarta Ant make tool available from
	  http://jakarta.apache.org/ant

	[ This release was tested on Linux (JDK 1.2.2), Solaris 
	(JDK 1.2.2 and JDK 1.1.8) and WinNT 4Sp6 (JDK1.3, JDK 1.1.8). ]

Installation:
=============

(0. Download "Ant" and install it as described in its documentation
    if you want to rebuild)

1.  For rebuilding, extend your CLASSPATH environment variable to 
    include the following paths, where <jacorb_home> denotes your 
    JacORB installation directory and <ant_home> the Ant installation 
    directory.:

	1) <jacorb>/classes
	2) <ant_home>/lib/ant.jar

2. Extend your search path to include the <jacorb>/bin subdirectory
   of the installation directory so that the JacORB utilities can be
   found. (For rebuilding, ant's /bin directory must also be included.)

3. Copy orb.properties to JAVA_HOME/lib or edit the existing
   orb.properties file.

4. Edit jacorb.properties and copy them to your "home" directory:
   Most options need no configuration, but you must adjust the  
   URL strings

	jacorb.NameServerURL=http://www.inf.fu-berlin.de/~brose/NS_Ref
	jacorb.TradingServiceURL=http://www.inf.fu-berlin.de/~brose/TS_Ref
	jacorb.ImplementationRepositoryURL=http://www.inf.fu-berlin.de/~brose/ImR_Ref
        jacorb.ProxyServerURL=http://www.inf.fu-berlin.de/~brose/Appligator_Ref

   to match your domain's web server or local file system structure.
   Please consult the programming guide's section on  setting up the
   name server for details. The trader and the Appligator are located 
   using the same mechanism.

   Also, you can configure how much diagnostic information JacORB
   emits by setting the jacorb.verbosity property. A value of 0
   means no output,  level 1 emits basic connection information, 
   and levels 2 and above are debug levels.

5. Generate or edit the start script jaco and jaco.bat:
   If you are not building JacORB entirely you need to adapt
   the jaco script in bin/ by either editing it yourself
   or by calling "ant jaco" to update the classpath. (The 
   latter obviously requires an installation of ant.) If
   you are rebuilding, the script will be automatically
   generated.


Building JacORB (Optional)
==========================

   To build JacORB you need to call "ant" in 
   the installation directory as shown below.

	$> ant 
 
   NOTE: 

   The build process may bail out, claiming that javac 
   does not have enough memory. This can happen when trying to
   compile a large number or files at one time. To avoid this
   on Unix, copy the file "ANT-RC" to your home directory. ant will
   consult this file and use a larger Java maximum heap size. If 
   this is not applicable in your setting or if you are building on 
   a Windows platform, you need to edit ANT_HOME/bin/ant(.bat) such
   that the java interpreter is passed the -mx48m (or whatever)
   switch.


Upgrading from 1.0 beta 15
===========================

1. JDK 1.2 only:

   The only thing requiring source code changes is using the name
   service: since 1.1, our libraries coexist more or less peace-
   fully with the CORBA classes in the JDK. The only conflict 
   occurs when you use the org.omg.CosNaming.NamingContext interface,
   since Sun included broken stub code for this interface.

   This is no problem if you upgrade to using the Interoperable
   Naming Service (INS), which is a straight extension. All that
   is needed is to change any reference to CosNaming.NamingContext
   to CosNaming.NamingContextExt in your code. 

   You should always narrow to NamingContextExt any NamingContext 
   reference obtained as a result from other NamingContext operations 
   before invoking operations, otherwise the broken Sun JDK stubs
   may throw null pointer exceptions.

   The easiest way out is top delete any NamingContext classes from
   rt.jar...

2. Scripts (jaco, javaco, ..)

   Basically, you don't need these anymore, calling java or javac
   directly is enough - if you are using JDK 1.1 or, for JDK 1.2,
   installed the orb.properties file correctly. If this was not
   possible, you need to set and pass the system properties 
   org.omg.CORBA.ORBClass and org.omg.CORBA.ORBSingletonClass on 
   the command line. For convenience, you can use the jaco script
   in bin/


_____________________________________________________________________
Gerald Brose, October 2000
