Setting up imagedb database on nonstop – HP Integrity NonStop H-Series User Manual
Page 61
NOTE:
Because JDBC Type 2 driver resides on the NonStop system, you need
not mention the username and password in the
jdbc.username
and
jdbc.password
fields.
•
If you plan to use the JDBC/MX Type 4 driver, uncomment the SQL/MX settings
for the JDBC Type 4 driver in the
jdbc.properties
file and enter the values of
the JDBC URL (NonStop system IP Address and port number of JDBC data source),
NonStop system username, and password. The SQL/MX settings for the JDBC Type
4 driver in the
jdbc.properties
file appear as:
#---------------------------------------------------
-------------------
#common settings
#
imageDatabase.lobHandler=defaultLobHandler
jdbc.blobTableName=imagedbcat.imagedbsch.blobTableName
jdbc.catalog=imagedbcat
jdbc.schema=imagedbsch
#------------------------------------------------------
----------------------
# SQL/MX Settings for JDBC Type 4 Driver
jdbc.driverClassName=com.tandem.t4jdbc.SQLMXDriver
jdbc.url=jdbc:t4sqlmx://
jdbc.username=
jdbc.password=
4.
Build the ImageDB
WAR
file (
imagedb.war).
1.
Go to the
directory from the command
prompt using the command:
Command Prompt> cd
2.
Build the ImageDB web archive.
•
If you plan to use JDBC Type 2 driver, build the ImageDB web archive using the
command:
Command Prompt> ant –buildfile build_jdbct2.xml all
•
If you plan to use JDBC Type 4 driver, build the ImageDB web archive using the
command:
Command Prompt> ant –buildfile build_jdbct4.xml all
After successful build, a new directory named
dist
is created in the
samples\imagedb
directory. The application WAR file (
imagedb.war
) is created in the
dist
directory on your Windows system.
Setting up ImageDB Database on NonStop
To set up the ImageDB deployment environment on your NonStop system, complete the following
steps:
1.
Edit the
imagedb_tables_script.sql
file to add the following:
•
<$datavol>
: specify the Guardian volume for the primary partition of the table. For
example:
$data01
•
: specify the owner of the schema. For example:
super.sashusr
•
: specify the location of the metadata tables for the catalog. For example:
\NSK01.$data01
•
: specify the designated subvolume name for the schema. For
example:
SASH3
Deploying and Running Sample Spring Applications on NonStop
61