Windows NT Installation instructions for SOMobjects Java Client

Initial Setup

Since you are reading this, you have unzipped som30jcl.zip. For this discussion, it will be assumed that you unzipped it in a directory by the name of x:\www\html\sjclient. If you chose a different name, modify these steps accordingly.

To use the IDL-to-Java compiler, you must add the directory x:\www\html\sjclient to the CLASSPATH environment variable on the machine on which you will be using the compiler. If you place the Java .class files in a different directory, modify the above directory accordingly. (Note: this step is not necessary for running the Checkers demo.)

Product Documentation

Documentation for this product is in HTML format. To view the index, point your web browser at the file "packages.html" in the DOCS directory. Instructions for compiling IDL into Java client proxies are in the file COM.ibm.idl.toJava.Compile.html, and a summary is contained in the Setup.html file.

Server-side Checkers Setup (Windows NT Server)

  1. Make sure your %SOMBASE%\etc\somenv.ini file is configured as follows: Note: Changing these somenv.ini variables requires that you rerun the som_cfg -i command. Before doing this, erase all files in the directory $SOMBASE/etc/dsom, and edit the somenv.ini file to remove the SOMNMOBJREF and HOSTKIND stanzas.

  2. Next, build the Checkers server implementation:
    From a Command Prompt window:

    1. If you haven't already, generate the C++ language bindings using the somxh command.

    2. cd x:\www\html\sjclient\COM\ibm\samples\servers\nt

    3. Start the SOM Daemon in the background: start somdd
        (Wait until you see the SOMDD - Ready message)

    4. Kick off the build by typing buildit
      This should:
      • create the necessary libraries
      • populate the Implementation Repository (via regimpl)
      • create the IR file (som.ir)
      Note: There is also a cleanit command that will delete all files generated by the build. Use this command if you need to restart the build from scratch.

    5. The reason you started somdd in step 2 is because it is required for the regimpl to run.

  3. Add the following directory to your PATH registry record in the same way as you did when you installed the SOM 3.0 product:

  4. Insert the following file as the second-to-last entry in your SOMIR registry record (make sure it is the second-to-last entry):

  5. Reboot the server machine to pick up the registry changes.

  6. Restart the SOM Daemon in the background by typing start somdd in a Command Prompt window. You may want to create a desktop icon for SOMDD and place it in the Startup folder to make this occur each time the system is rebooted.

  7. The server-side should now be ready for action from the Java Client...

© 1996 IBM Corp. All rights reserved. All trademarks are the property of their respective owners.