AIX Installation instructions for SOMobjects Java Client

Initial Setup

Since you are reading this, you have untarred som30jcl.tar.Z. For this discussion, it will be assumed that you untarred it in a directory by the name of /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 /www/html/sjclient to the CLASSPATH environment variable on the machine on which you will be using the compiler.

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 (AIX Server)

Add the following directory to your LIBPATH environment variable:
Add the following file to the end of your SOMIR environment variable:
(Note: Make sure it is the last entry of the environment variable)
Make sure your $SOMBASE/etc/somenv.ini file is configured as follows:
- HOSTNAME should include the fully-qualified domain name.
  For example, machinename.xxx.yyy.zzz, not just machinename.
  (There are several instances of this variable in somenv.ini.)
- SOMDPROTOCOLS must include the SOMD_TCPIP protocol.
  (The default only includes SOMD_IPC.)
- SOMD_JCLIENT stanza must include the SERVICES_FILE_TARGET= variable.
  When you run som_cfg -i on the SOM server it will use this variable to determine where to put the services file. The services file contains a stringified Object Reference for the NameService.
  The Java client ORB will access this file to resolve the root naming context to be used by the client. The html for the Java applet will pass this variable to the Java ORB via the param tag.
  
  For this demo, the Checkers.html file expects SERVICES_FILE_TARGET to be one directory above the directory containing Checkers.html. If you do not put the services file here, you must edit the param tag within the Checkers.html file. Its value can be either relative to the current directory (as the default one is) or a full URL path.
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.
Building the Checkers sample server is the next step:
From an aixterm window:
1. If you haven't already, generate the C-language bindings using the somstars command. This will generate the variant of the bindings that assumes use of the dereference operator (*) when referencing object instances.
2. cd /www/html/sjclient/COM/ibm/samples/servers/aix
3. Start the SOM Daemon in the background: somdd &
4. Kick off the build by typing buildit
  This should:
  - create the necessary libraries
  - populate the Implementation Repository (via regimpl)
  - create the IR file (Checkers.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. But the build also created the Checkers.ir file. Now somdd needs to be restarted so it will pick up the Checkers.ir information (somdd caches this on startup).
  So, to stop the somdd process:
  - Type ps -ef |grep somdd to get the id number for the process.
    (It will be the first number after the owner's userid).
  - Type kill process id number to stop the process.
6. Now restart somdd & in the background.
The server-side should now be ready for action from the Java Client...