Guidelines for Java Database Connectivity
Java Database Connectivity (JDBC) provides an interface for Java application
programs to access relational data in a database by using dynamic SQL. DB2
supports this application programming interface. For complete information
about JDBC and DB2, see DB2 for OS/390 Application Programming Guide
and Reference for Java. This topic covers guidelines related to WebSphere
Application Server for z/OS's use of JDBC.
- You may use JDBC (dynamic SQL) in your server applications.
- Record the location of the run-time properties file, db2sqljjdbc.properties.
You will use the location during the WebSphere Application Server for z/OS
customization process. If you customize this file, you may want to keep the
customized version in a separate directory such as /etc and
record its location.
- All J2EE servers and the node must be granted EXECUTE authority on the
DSNJDBC plan. If your installation allows public access to the DSNJDBC plan,
all you need to do is issue:
GRANT EXECUTE ON PLAN DSNJDBC TO PUBLIC
If your installation does not allow public access to the DSNJDBC
plan, then you must grant EXECUTE authority to all J2EE servers and the node.
If you use DB2 secondary authorization IDs, then you can grant the authority
to the groups to which the server IDs belong.
- You must use the RRSAF attachment interface (not CAF).
For more information about setting up JDBC and the implications for application
programs, see DB2 for OS/390 Application Programming Guide and Reference
for Java.
Searchable topic ID:
cinsjavacon
Last updated: Jun 21, 2007 9:56:50 PM CDT
WebSphere Application Server for z/OS, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.websphere.zseries.doc/info/zseries/ae/cins_javacon.html