Đang chuẩn bị nút TẢI XUỐNG, xin hãy chờ
Tải xuống
172 Chapter 8 Database Access Databases Supported in WebSphere sMash Before we begin, we need to cover the database vendors supported in WebSphere sMash. Vendors not listed will probably work as long as they support JDBC, and you can acquire the necessary driver files required to connect to the database server. The database vendors that are supported and known to work with WebSphere sMash are as follows: • Apache Derby • MySQL • IBM® DB2® • Informix • Microsoft® SQL Server® • Oracle Configuration Settings As with most things in WebSphere sMash, we need to start by configuring our application dependencies. To use database accesses in. | 172 Chapter 8 Database Access Databases Supported in WebSphere sMash Before we begin we need to cover the database vendors supported in WebSphere sMash. Vendors not listed will probably work as long as they support JDBC and you can acquire the necessary driver files required to connect to the database server. The database vendors that are supported and known to work with WebSphere sMash are as follows Apache Derby MySQL IBM DB2 Informix Microsoft SQL Server Oracle Configuration Settings As with most things in WebSphere sMash we need to start by configuring our application dependencies. To use database accesses in the application you need to first add the zero.data dependency as shown here dependency name zero.data org zero rev 2.0.0.0 3.0.0.0 The next step is to define the database connections. There are only a couple items to be concerned about here such as defining the database driver and the connection details. If you are impatient skip ahead to the ZRM discussion because WebSphere sMash will work automatically with the embedded Apache Derby database with no configuration requirements. All database connection information is placed inside config db stanzas in the config zero.config file. For each database connection configuration there needs to be a named database section that is used to access the manager associated with that connection. The name should be symbolic of the data accessed more than any particular connection specifics. For the samples used in this chapter we use the name bookmark because we ll be accessing a database of URL references that may be shared among several users. Within the configuration stanza a driver name must be defined that indicates the actual JDBC class to be used to access the data. It is preferred to use a normal JDBC Type 4 driver. These are pure Java solutions and do not require any special operating system configuration. Just place the appropriate JAR file inside the environment CLASSPATH or preferably add it to the .
