WebSphere Extended Deployment, Version 6.0.x
             Operating Systems: AIX, HP-UX, Linux, Solaris, Windows


Configuring database sources

Under typical circumstances, the JDBC connections should not need to be recreated. The dynamic cluster clones the JDBC connector template from the WC_demo application server.

About this task

Do the following to configure dynamic operations:

Procedure

  1. Launch the Deployment Manager Administration Console.
  2. Select Resources > JDBC Providers.
  3. Delete any targets in the Node, Cluster or Server box and click Apply. The scope is now set to the Cell level.
  4. Create a new JDBC provider. The information will match what the provider already created for the single application server, but at the Cell level:
    1. Database Type: DB2
    2. Provider Type: DB2 Universal JDBC Driver Provider
    3. Implementation Type: Connection pool data source
    4. Name: demo - WebSphere Commerce JDBC Provider
    5. Description: demo - WebSphere Commerce JDBC Provider
    6. Class Path: C:/WebSphere/SQLLIB/java/db2java.zip, for example
    7. Native Library Path: *blank
    8. Implementation class name: COM.ibm.db2.jdbc.DB2ConnectionPoolDataSource
    9. Click Apply Changes.
  5. Create a data source:
    1. Name: WebSphere Commerce DB2 DataSource demo
    2. JNDI Name:jdbc/WebSphere Commerce DB2 DataSource demo
    3. Use this Data Source in container managed persistence (CMP): Select this check box.
    4. Description: WebSphere Commerce DB2 DataSource demo
    5. Data store helper class name: Click this button.
    6. Component managed authentication alias: WC_demo - authDataAlias
    7. Container managed authentication alias: WC_demo - authDataAlias
    8. Mapping configuration alias: DefaultPrincipalMapping
    9. Database name: mall
  6. Connection Pool properties:
    1. Connection timeout: 180
    2. Maximum connections: 65
    3. Minimum connections: 5
    4. Reap time: 180
    5. Unused timeout: 1800
    6. Aged timeout: 1800
    7. Purge policy: Entire Pool
  7. Data Source properties:
    1. Statement cache size: 50
    2. Enable multithreaded access detection: Deselect.
    3. Enable database reauthentication: Deselect.
    4. Enable JMS one-phase optimization support: Deselect.
    5. Manage cached handles: Deselect.
    6. Log missing transaction context: Deselect.
    7. Pretest connections: Deselect.
  8. Custom Properties:
    1. Name: URL
    2. Value: jdbc:db2:mall
    3. Type: java.lang.String
  9. Save changes to the master repository.
  10. Use the Test Connection function to ensure that the database configuration is correct.



Related tasks
Installing and configuring the product
Related information
IBM WebSphere Commerce Business Edition documentation
Task topic    

Terms of Use | Feedback

Last updated: Nov 30, 2007 3:58:31 PM EST
http://publib.boulder.ibm.com/infocenter/wxdinfo/v6r0/index.jsp?topic=/com.ibm.websphere.xd.doc/info/odoe_task/tcommercedatabase.html