Log on or use telnet to connect to your UNIX based JDBC server and start a terminal session.
Use your favorite UNIX editor (Emacs, for example) to create a shell script from the following text:
# begin CONNX startup script CNXDIR=<path to CONNX JDBC server> PATH=<basic system path for shell programs> export CNXDIR PATH case "$1" in start) su <connx user> -c "$CNXDIR/jdbcserver START";; stop) su <connx user> -c "$CNXDIR/jdbcserver STOP";; restart|reload) su <connx user> -c "$CNXDIR/jdbcserver START";; esac exit 0 #end CONNX startup script
Supply the correct values for <path to CONNX JDBC server>, <basic system path for shell programs> and <connx user>. The value for <path to CONNX JDBC server> will be the path to the CONNX installation directory. The value for <basic system path for shell programs> should contain the path for basic shell utilities such as cd and ls. The value for <connx user> will be the user that has been designated to start the CONNX processes. It is not recommended that any of the CONNX server processes be started with the root account.
Save the document in the appropriate UNIX flavor. The following table contains some example of file names:
UNIX Flavor |
File Name |
---|---|
HP-UX |
/sbin/rc2.d/S999connx |
LINUX |
/etc/rc.d/rc5.d/S99connx |
SCO |
/etc/rc2.d/S99connx |
SUN |
/sbin/rc2.d/S99connx |
SOLARIS |
/sbin/rc2.d/S99connx |
TRU-64 |
/sbin/rc2.d/S99connx |
AIX |
If you do not have rc#.d directories, where
# is the run level number and generally 2 for multi-user, then
you can put the following lines toward the bottom of the /etc/rc
script. For example: export CNXDIR sh$CNXDIR/connxserver START [port number]
|
If an example of the file name to use for your UNIX flavor does not appear in the above table, contact CONNX Technical Support for details.
The CONNX JDBC server automatically starts when you restart the system. To verify that it has started, type the following UNIX command after a command prompt in your UNIX system:
$CNXDIR/jdbcserver STATUS
Check the log file in the CNXDIR directory to verify the start procedure.
Note: Since the startup procedures vary between operating systems as well as UNIX flavors, the above examples should be used as a rough guide. Consult your operating system's system administration guide for the exact location of startup scripts and directories. You should be logged in as root to complete the script configuration and set the proper permissions on the script.