Documentation Comments
Use this form to comment on this topic. You can also provide any general observations about the Online Documentation, or request that additional information be added in a future release.
Reality V15.0 ()
JReal (External Components Installation Guide) (M6859IG+JReal.htm)
JReal
JReal provides the Java programmer with the ability to access Remote
Basic subroutines (DataBasic subroutines that have been enabled for
remote access), and to write custom servlets to access a Reality
database via RealWeb. It comprises:
- DDA classes within the
com.northgateis.comms.dda package. These classes allow a Java program to
make a connection and access information in a Reality database by
sending DDA messages across a TCP/IP network.
- RSC classes within the
com.northgateis.reality.rsc package. These classes allow a Java program
to access a Remote Basic subroutine (a DataBasic subroutine that has
been enabled for use via remote access).
- Utility classes - including ItemView,
which allows a Reality item to be broken down into attributes, values
and subvalues.
- Servlet connection classes, which allow
you to write custom servlets to access a Reality database via RealWeb.
Prerequisites
Java Run Time Environment (JRE) version 1.2 or above. If this is not
available, it can be downloaded from Sun's Java web site (http://java.sun.com/j2se/).
Installation
Windows
- Start the installation program as
described for Windows in the section
Starting the Installation.
- Select JReal from the Core Reality
Software menu.
- The default location is c:\Program
Files\NorthgateIS\JReal-3.0; you can override this if required.
- You can select up to two components:
Program Files and Help Files. Highlight an item to display a description
of that component.
UNIX
- Start the installation program as described for UNIX in the section
Starting the Installation.
- Enter the root password when prompted. The following menu is
displayed:
Reality CD-ROM Component Installation Utility
The following components are available
JDBCdriver V1.0 RealSQL-JDBC driver interface to Reality
JReal V3.2 Java interface to Reality (DDA & RSC)
RealWeb V3.2 Web interface to Reality
Select component to install
Install JDBC driver y/n/q [n]:
Install JReal y/n/q [n]:
Install RealWeb y/n/q [n]:
- Enter y to select the required component.
- Enter the installation directory when prompted. The default
location is /usr/northgateis/Product-Version, but you can change this if
required.
Set-up After Installation
CLASSPATH
- Add the jreal.jar file to CLASSPATH. For example, on UNIX:
/usr/northgateis/JReal-3.1/class/jreal.jar
or on Windows:
C:\Program Files\NorthgateIS\JReal-3.1\jreal.jar
- Add the class directory to CLASSPATH.
On UNIX:
/usr/northgateis/JReal-3.1/class
On Windows:
C:\Program Files\NorthgateIS\JReal-3.1\class
This contains the reality.properties file.
For information on how to set
CLASSPATH, refer to Setting Environment Variables.
User-ids
To call a Remote Basic subroutine using JReal, you must establish a
connection to an account on a Reality database - you will need to use a
user-id that has been set up as follows.
Log on to the SYSMAN account and run SSM. Then do the following:
- Use SSM option 3 to create a security profile to be used with the
Remote Basic server. It is recommended that this profile should have
field 23 (Remote Basic) set to R (restricted); you must also specify a
file in which the subroutines that can be called remotely are listed.
For more information on security for external access, refer to the
Reality on-line documentation.
- Use SSM option 2 to set up a user-id that will be used to access
your Remote Basic subroutines. Set the status (field 13) to 'E'
(enabled) and the type (field 14) to 'S' or '*' (so that it can be used
as a server). Note that on a UNIX host a corresponding UNIX user-id must
also exist, and it is the password for the UNIX user-id that must be
used when establishing a connection.
- Use SSM option 3 to configure the security profile associated with
the user-id you have created, setting field 8 (Alt Server Profiles) to
specify that the Remote Basic server (RBSRVR) should use the security
profile you created in step 1.