Manual

NOTE: By default, the petclinic_tables_script.sql file creates the database catalog
name as petcliniccat and schema name as petclinicsch. If these names conflict with
any of the existing catalog and schema names, modify the database catalog and schema
names in the petclinic_tables_script.sql script file.
If you modify the database catalog and schema names, edit the jdbc.properties file
present in the <My SASH Home>\spring\samples\petclinic\src directory, present
in SAMPLES.zip file.
6. Load the sample data in the PetClinic sample application database tables using the SQL/MX
command:
mxci>> obey petclinic_dataload_script.sql;
The PetClinic database is setup on your NonStop system.
Deploying PetClinic on NonStop
Before deploying PetClinic, ensure that you have WRITE permissions to the lib directory in
your <NSJSP deployment directory>. You can confirm this by using the OSS command:
OSS> ls –l <NSJSP deployment directory>
For example: ls –l at /home/sash_usr/webserver/servlet_jsp must display WRITE
permissions to the lib directory.
If this directory does not have WRITE permissions set, run the following command:
OSS> chmod +w <NSJSP deployment directory>/lib
For example:
OSS> chmod +w /home/sash_usr/webserver/servlet_jsp/lib
After verifying the permissions, copy the class loader file spring-tomcat-weaver.jar file
from the OSS directory <NonStop Spring Home>/dist/weaving to <NSJSP deployment
directory>/lib using the command:
OSS> cp <NonStop Spring Home>/dist/weaving/spring-tomcat-weaver.jar
<NSJSP deployment directory>/lib
For example:
OSS> cp /usr/tandem/sash/spring_2.5.5/dist/weaving/spring-tomcat-weaver.jar
/home/sash_usr/webserver/servlet_jsp/lib
To deploy PetClinic on your NonStop system, complete the following steps:
1. Go to http://<IP Address of the iTP WebServer>:<port#>/servlet_jsp /manager/html.
The NSJSP Web Application Manager Login screen appears.
Figure 3-1 shows the NSJSP Web Application Manager Login screen.
Deploying and Running Sample Spring Applications on NonStop 51