NonStop Servlets for JSP System Administrator's Guide
Configuring NSJSP
NonStop Servlets for JavaServer Pages (NSJSP) System Administrator’s Guide—525644-001
3-24
JDBCRealm
Or you may run the NonStop SQL Commands directly through the NonStop Command 
Interpreter (SQLCI) after replacing the =T1222DBDIR string with the Guardian 
Location of the JDBCRealm catalog (of the form $Volume.SubVolume). This 
subvolume (disk) should be an HP NonStop Transaction Management Facility (TMF) 
audited data volume. 
JDBCRealm Element Attributes
To configure JDBCRealm, create a <Realm> element and nest it in your 
iTPWS_INSTALL_DIR/servlet_jsp/conf/iTP_server.xml file, as described in 
Example 3-18. The following attributes are supported for JDBCRealm:
className
Specify the value org.apache.catalina.realm.JDBCRealm here.
connectionURL
The database URL used to establish a JDBC connection. 
For SQL/MP, specify the value jdbc:sqlmp:
For SQL/MX, specify the value jdbc:sqlmx:
debug
The level of debugging detail logged by this realm to the associated <Logger>. 
Higher numbers generate more detailed output. If not specified, the default 
debugging detail level is zero (0).
digest
The digest algorithm used to store passwords in non-plaintext formats. Valid values 
are those accepted for the algorithm name by the 
java.security.MessageDigest class. See Digested Passwords on page 3-31 
for more information. If not specified, passwords are stored in clear text.
Example 3-21. SQLCI Commands to Create and Load the JDBCRealm
osh> gtacl -p sqlci < iTP_JDBCRealm.create.sample
osh> gtacl -p sqlci < iTP_JDBCRealm.load.sample
Note. Example 3-20 uses a varchar(15) field for the user_name column in the users table. If 
you configure a web application with the client-certificate based authentication method, this 
column size (variable length characters with a maximum size of 15 characters) is not large 
enough because the value stored in the user_name column is the subject (subject 
distinguished name field) from the client-certificate. The subject may even exceed the NonStop 
SQL maximum allowable primary key limit of 256 characters. In such a case, you need to alter 
the user_name field to the appropriate size and also define a new primary key that conforms to 
the NonStop SQL limits.










