web server - Borland Technical Publications
web server - Borland Technical Publications web server - Borland Technical Publications
Configuring JDBC Datasources The Main tab in the content pane captures the essential properties needed to define the chosen database. If the database is known to the DDEditor, it will automatically complete these properties. The Driver Properties and Pool Properties tabs capture some of the information from the Main tab, but also allow you to set any less common properties that do not appear in the Main tab. Chapter 22: Using JDBC 197
Configuring JDBC Datasources To add pool properties, click the Add button and select the property you want to add from the drop-down list under “Name.” Pool Properties are described in “Defining the Connection Pool Properties for a JDBC Datasource” on page 199. The same procedure is used for adding Driver Properties. Consult your database documentation for any properties you need to define. Once you're finished, save the module and dismiss the final modal window. The JNDI Definitions Module is automatically re-deployed to the Partition. Deploying Driver Libraries If a deployed application component contains a JNDI lookup of third party JDBC datasource, vendor libraries are required and must be deployed to the target Partition as a library archive before the lookup is performed. Note that these steps are not necessary if you are using the native all-Java database, JDataStore. When trying to connect to another database like Oracle or Sybase the respective JDBC driver must first be deployed to the target Partition. To deploy a library to multiple partitions do the following: 1 From the Console, select Wizard->Deployment Wizard. This will open the Deployment Wizard. 2 Click on the Add button and navigate to the library file in the resulting window and click OK. The library name should now appear in the selection box in the Deployment Wizard. 3 Click on the Next button. The names of the partitions will appear in the Deployment Wizard window. 4 Select the partitions to which you want to deploy the library and click on the Finish button. The deployment status will appear in a separate window. 5 Click the Close button to close this window. You can verify that the libraries are deployed correctly by checking the partition's Deployed Modules node in the BES Console navigation pane. The name of the library should appear under the Deployed Modules node. 198 BES Developer’s Guide
- Page 157 and 158: Setting Properties Figure 16.2 Edit
- Page 159 and 160: Setting Properties Table 16.1 ejb.m
- Page 161 and 162: Setting Properties Table 16.3 Table
- Page 163 and 164: Setting Properties Security Propert
- Page 165 and 166: Aggregate Functions in EJB-QL Selec
- Page 167 and 168: Support for ORDER BY Support for OR
- Page 169 and 170: Overriding SQL generated from EJB-Q
- Page 171 and 172: Container-managed data access suppo
- Page 173 and 174: 162 BES Developer’s Guide
- Page 175 and 176: Generating primary keys from a cust
- Page 177 and 178: Implementing primary key generation
- Page 179 and 180: Transaction manager services Consis
- Page 181 and 182: Transaction manager services When t
- Page 183 and 184: Transaction manager services Follow
- Page 185 and 186: Declarative transaction management
- Page 187 and 188: Declarative transaction management
- Page 189 and 190: JDBC API Modifications JDBC API Mod
- Page 191 and 192: Handling of EJB exceptions Applicat
- Page 193 and 194: 182 BES Developer’s Guide
- Page 195 and 196: Client View of an MDB Client View o
- Page 197 and 198: Clustering of MDBs This is yet anot
- Page 199 and 200: Error Recovery Redelivered messages
- Page 201 and 202: 190 BES Developer’s Guide
- Page 203 and 204: JNDI Definitions Module Important s
- Page 205 and 206: Disabling and Enabling a Deployed D
- Page 207: Configuring JDBC Datasources In the
- Page 211 and 212: Defining the Connection Pool Proper
- Page 213 and 214: Defining the Connection Pool Proper
- Page 215 and 216: Descriptions of Borland Enterprise
- Page 217 and 218: Advanced Topics for Defining JDBC D
- Page 219 and 220: Connecting to JDBC Resources from J
- Page 221 and 222: Configuring JMS Connection Factorie
- Page 223 and 224: Defining Connection Pool Properties
- Page 225 and 226: Obtaining JMS Connection Factories
- Page 227 and 228: JMS and Transactions and its accomp
- Page 229 and 230: JMS and Transactions For instance:
- Page 231 and 232: 220 BES Developer’s Guide
- Page 233 and 234: Configuring JMS administered object
- Page 235 and 236: Tibco Creating Clustered JMS Servic
- Page 237 and 238: Sonic serverUrl String localhost:72
- Page 239 and 240: Sonic Creating Clustered JMS Servic
- Page 241 and 242: OpenJMS Even though OpenJMS can be
- Page 243 and 244: OpenJMS Important If you use OpenJM
- Page 245 and 246: OpenJMS openjms.clean_messages_on_s
- Page 247 and 248: OpenJMS Table 24.1 Property Name De
- Page 249 and 250: Other JMS providers The following a
- Page 251 and 252: 240 BES Developer’s Guide
- Page 253 and 254: Creating the Interceptor Class For
- Page 255 and 256: Creating the JAR file Creating the
- Page 257 and 258: Components Components The Connector
Configuring JDBC Datasources<br />
The Main tab in the content pane captures the essential properties needed to define<br />
the chosen database. If the database is known to the DDEditor, it will automatically<br />
complete these properties.<br />
The Driver Properties and Pool Properties tabs capture some of the information from<br />
the Main tab, but also allow you to set any less common properties that do not appear<br />
in the Main tab.<br />
Chapter 22: Using JDBC 197
Change language