Deploy and explore the DB2 10.5 pureScale Feature with WebSphere Commerce V7

Improve capacity, transparency, and availability

The IBM® DB2® pureScale™ Feature for Advanced Enterprise Server Edition is designed for continuous availability and tolerance of both planned maintenance and unplanned accidental component failure. This article describes how to deploy the DB2 10.5 pureScale Feature with IBM WebSphere® Commerce V7 for both new and existing WebSphere Commerce applications, including the instance setup and application configuration from the Admin Console of WebSphere Application Server.

Yiying Zhang (yiyingz@ca.ibm.com), DB2 System Verification Test, IBM

Yiying ZhangYiying Zhang is an IBM certified Advanced Database Administrator. She has worked for IBM for eight years on the DB2 database, focusing on system verification testing. Yiying has over 10 years of experience in integrating DB2 with various WebSphere products.



Lydia Siu (lydias@ca.ibm.com), WebSphere Commerce System Integration Test and Performance, IBM

Lydia SiuLydia Siu is an IBM certified Database Administrator. She has worked in WebSphere Commerce System and Performance Testing for two years. Lydia has 10 years of experience in DB2 backup recovery testing.



Aslam Nomani (aslam@ca.ibm.com), STSM, DB2 Quality Assurance, IBM

Aslam NomaniAslam Nomani has spent most of his 14 years with IBM with the Quality Assurance team. His main area of focus has been high availability and disaster recovery solutions. Over the past several years, Aslam has been the quality assurance architect for the DB2 pureScale Feature.



17 July 2014

Introduction

Whenever possible, we all want continuous availability and workload balancing. In this article, learn how to deploy the DB2 pureScale Feature on WebSphere Commerce V7 to take advantage of workload balancing and other features of DB2 pureScale. Step-by-step instructions show how to deploy the DB2 pureScale Feature and how to enable a few necessary configuration parameters in WebSphere Application Server.


DB2 pureScale Feature

Based on the familiar and proven design features from DB2 for z/OS® database software, the IBM DB2 pureScale Feature for Enterprise Server Edition provides the highly competitive and demanding marketplace with the following key benefits.

Practically unlimited capacity

The DB2 pureScale Feature provides practically unlimited capacity by enabling the addition and removal of members on demand. The DB2 pureScale Feature can scale up to 128 members. It has a highly efficient, centralized management facility that allows for very efficient scale-out capabilities. The DB2 pureScale Feature also leverages a technology called Remote Direct Memory Access (RDMA) that provides an extremely efficient inter-node communication mechanism to augment its scaling capabilities.

Application transparency

An application that runs in a DB2 pureScale environment does not need any knowledge of the different members in the cluster. The DB2 pureScale Feature automatically routes applications to the members deemed most appropriate. The DB2 pureScale Feature also provides native support for syntax that other database vendors use, which enables those applications to run in a DB2 pureScale environment with minimal or no changes.

Continuous availability

The DB2 pureScale Feature provides a fully active-active configuration; if one member goes down, processing continues at the remaining active members. During a failure, only data being modified on the failing member is temporarily unavailable until database recovery completes for that set of data, which is very quick. This, complimented by other features such as online rolling updates, allows for superior availability.

Reduced total cost of ownership

The DB2 pureScale Feature interfaces can easily handle the deployment and maintenance of components.

Figure 1 shows an overview of the DB2 pureScale Feature topology and associated benefits.

Figure 1. DB2 pureScale Feature topology
Overview of DB2 pureScale topology. Includes Clients, a single database view of members, and cluster interconnect to shared storage access

Introduction to WebSphere Commerce

IBM WebSphere Commerce provides a powerful customer interaction platform for cross-channel commerce. It delivers a consistent and seamless shopping experience across mobile, social, and in-store channels. IBM WebSphere Commerce is built on a scalable platform designed for all sizes of companies in various business industries. It supports different business models such as direct to consumers (B2C), direct to businesses (B2B), and indirect through channel partners (indirect business models).

Figure 2 shows the WebSphere Commerce architecture. WebSphere commerce operates on top of WebSphere Application Server, which communicates with a web server to receive incoming requests and send outgoing responses. WebSphere Application Server also communicates with the database server to query and update product or customer data.

Figure 2. Architecture of WebSphere Commerce
Architecture of WebSphere Commerce

The configurable business processes:

  • Provide functions for creating and managing precision marketing campaigns, promotions, catalogs, and all merchandising sales channels, which meet various business requirements.
  • Support the management of customer profiles.
  • Manage member resources such as member groups.
  • Audit user security.

The business intelligence processes help businesses understand the site usage pattern and facilitate adapting the site to better suit the customer's needs.

The business context engine further facilitates commerce by incorporating analytics, personalization, globalization, and roles and relationships. WebSphere Commerce Analyzer helps businesses to better understand customer usage of the site in order to better meet customer needs. Personalization improves the customer’s experience by tailoring the site according to a certain criteria. Globalization controls how the site behaves according to the locale of the customer interacting with the store. Roles and relationships govern the customer’s access to various aspects of a store.

WebSphere Commerce also provides role-based tools for business users, administrators, and developers.


An integrated system

DB2 pureScale provides customers with many advanced capabilities and, when integrated with other IBM leading technologies, gives customers more value. Integrated systems mean lower initial purchase costs, easier deployment, single-number support, and optimized performance.

The integration of WebSphere Commerce and DB2 has been a solution for enterprise applications for many years. DB2 provides a reliable repository for WebSphere Commerce with highly efficient data access. The tight integration promotes IBM’s leadership in providing an end-to-end application and resource management system. With the DB2 pureScale capabilities of scale-out and continuous availability, customers can implement the enterprise systems with virtually no downtime.

Figure 3 shows an integrated WebSphere Commerce and DB2 pureScale system. There are multiple members (including a primary cluster cache facility (CF) and secondary CF) in the DB2 pureScale system, but there is still a single database view. WebSphere Commerce applications connect to any member of the pureScale system the same as connecting to a DB2 Enterprise Server Edition system.

Figure 3. Integrated WebSphere Commerce and DB2 pureScale system
Integrated WebSphere Commerce and DB2 pureScale system

Deploying the DB2 pureScale Feature with WebSphere Commerce V7

This section describes how to deploy the DB2 pureScale Feature on WebSphere Commerce. The example uses the following software, which you should install if you want to follow along with the example.

  • IBM WebSphere Commerce V7 FEP8 on AIX®
  • DB2 pureScale V10.5 on AIX. The example DB2 pureScale cluster has two members and two CF servers.

Installation instructions for the DB2 pureScale Feature and WebSphere Commerce are outside the scope of this article. See Resources for more information.

Database setup instructions for WebSphere Commerce are in the next section. To use DB2 pureScale as the database server, you would perform different procedures depending on whether you have new or existing WebSphere Commerce applications.

New WebSphere Commerce application deployment

Follow the steps in this section to deploy a new WebSphere Commerce application to use DB2 pureScale as the database server, including configuring the DB2 pureScale instance and creating the WebSphere Commerce instance from Configuration Manager.

WebSphere Commerce instance creation

When deploying WebSphere Commerce applications, you need to create a WebSphere Commerce instance from the Configuration Manager. During instance creation:

  • An enterprise edition archive (EAR) is deployed and run in WebSphere Application Server.
  • A relational database containing store data and metadata about the deployed EAR is created.
  • The web server configuration is generated.

You need to get information from the DB2 instance and adjust a couple of DB2 Configuration Manager parameters. With the data, you can create the WebSphere Commerce instance from Configuration Manager, which is a graphical tool to enable and configure WebSphere Commerce components.

From the DB2 pureScale instance

  1. Get the user id (instance name) and the password from the db2 instance. For example, a user id (instance name) is db2inst1 and password passwdA.
  2. Get the TCPIP service name that is being used by the DB2 pureScale instance:
    1. Run the following command:
      db2 get dbm cfg |grep –i svcename

      The output of the command is similar to:
      TCP/IP Service name (SVCENAME) = db2inst1 SSL service name (SSL_SVCENAME) =

    2. Run the following command:
      grep "db2inst1" /etc/services

      The output of the command is similar to:
      db2inst1 32512/tcp
      db2inst1_int 32513/tcp

    The TCPIP port number is 32512.

  3. Configure the DB2 pureScale instance if it is not already set, as follows:
    1. Set the DB2 registry variable DB2COMM to TCPIP by running the following command:
      db2set DB2COMM=TCPIP
    2. Set the default database creation path to the existing GPFS file system where the store database is created by running the following command:
      db2 update dbm cfg using DFTDBPATH <GPFS file system path>
    3. Restart the DB2 instance:
      db2stop
      db2start

From WebSphere Commerce Configuration Manager

  1. Start Configuration Manager, as follows:
    1. Open a terminal window and log on as wasuser_ID, where wasuser_ID is the non-root user ID created before installing WebSphere Commerce.

      The default WebSphere Application Server user name is wasuser. Enter:

      cd <wc_install_dir>/bin
      ./config_server.sh
    2. Open a terminal window, log on as wasuser_ID, and enter:
      export DISPLAY=<hostname>:0.0

      where <hostname> is the fully qualified hostname of the system from which you will access the configuration manager graphically. Then enter:
      cd <WC_install_dir>/bin
      ./config_client.sh
    3. Enter the Configuration Manager user id and password, which were set up when installing WebSphere Commerce, and click OK, as in Figure 4.
      Figure 4. Start Configuration Manager client
      Start Configuration Manager Client
  2. Create a WebSphere Commerce instance from the Configuration Manager:
    1. Select WebSphere Commerce -> WC machine host name (wcsp708) -> Commerce -> Instance List, as in Figure 5.
      Figure 5. Create WebSphere Commerce instance
      Create WC instance
    2. Right-click Action and then select Create Instance, and the Commerce Instance Creation Wizard appears.
    3. Enter the instance data as shown in Figure 6.
      Figure 6. Enter instance data
      Input the instance data
    4. Enter the database data in Figure 7 with the information retrieved from the DB2 pureScale instance. The Database name can be your preference; it is used to contain the Commerce application data. The Database server host name can be any member node in the DB2 pureScale instance. You can specify any name for Database node name, which is used by WebSphere Commerce to catalog the database in DB2. Select the pureScale database box to enter the data in the Alternate hosts and Alternate ports fields, which are used to enable the enableAlternateServerListFirstConnect feature. This feature is explained in WebSphere Application Server configuration.
      Figure 7. Enter the database data
      Input the database data
    5. Enter the WebSphere Commerce Schema data as shown in Figure 8. The Database user name is the user id that is used to access the database.
      Figure 8. Enter the schema data
      Input the schema data
    6. Keep the data in the WebSphere Application Server window, as in Figure 9.
      Figure 9. WebSphere Application Server window
      WebSphere Application Server Panel
    7. Choose all the available languages in the Language window, as shown in Figure 10.
      Figure 10. Language selection
      Language Panel
    8. Enter the web server data in Figure 11. You can use the default values or choose different values according to your needs.
      Figure 11. Enter web server data
      Enter the web server data
    9. Choose the following options in the Staging window, as in Figure 12.
      • Runtime server: Clear all the options
      • Authoring server: Select the box for Use staging server
      • Enable workspace in Authoring server: Select the boxes for Use staging server and Enable workspaces
      Figure 12. Staging
      Staging Panel
    10. Click Finish.

Post instance-creation setup

Perform the following setup, which is not specific to DB2 pureScale, as needed and in the usual way. See Resources for related information.

  • Feature enablement
  • Data loading
  • Search server deployment
  • Cache configuration

Existing WebSphere Commerce applications

You need to upgrade your existing WebSphere Commerce applications to V7 FP8 first in order to benefit from DB2 pureScale. Use the following steps to move the database from the Enterprise Edition environment to the pureScale environment. Because of the specific hardware used by DB2 pureScale, many customers typically deploy DB2 pureScale on new hardware. It is not a requirement to have DB2 pureScale deployed on the same operating system (OS) as the Enterprise Server Edition being used. Using a different OS would lead to different alternatives for moving data.

DB2 pureScale using the same operating system as the original ESE environment

You can use restore migration to move the database to the pureScale system. The DB2 migration paths are:

  • V9.5 ESE -> V10.1 ESE -> V10.5 ESE -> V10.5 pureScale
  • V9.7 ESE -> V10.5 ESE -> V10.5 pureScale

To simplify the process, please have the same userid and password set up in the DB2 pureScale system as the original DB2 Enterprise Server Edition system.

First, in the original DB2 V9.5 or V9.7 system, using the DB2 instance id, perform an offline database backup.

In the new DB2 pureScale system, you need to perform the following steps before the database can be used.

  1. If the database backup image is from DB2 V9.5:
    1. Using the user id with root access, install DB2 V10.1.
    2. Using the user id with root access, create an Enterprise Server Edition instance:
      < DB2 V10.1 Install Path>/instance/db2icrt <db2 instance ID> -u <db2 fenced ID>
    3. Using the user id with the DB2 instance id, restore the database backup image you made at the beginning of this section.
    4. Using the user id with root access, install DB2 V10.5 (with pureScale features).
    5. Using the user id with root access, upgrade the instance to V10.5 Enterprise Server Edition:
      < DB2 V10.5 Install Path>/instance/db2iupdt <db2 instance ID> -u <db2 fenced ID>
    6. Using the DB2 instance id, upgrade the database:
      db2 upgrade db <dbname>
  2. If the database backup image is from DB2 V9.7:
    1. Using the user id with root access, install DB2 V10.5 (with pureScale features).
    2. Using the user id with root access, create an Enterprise Server Edition instance:
      < DB2 V10.5 Install Path>/instance/db2icrt -s ese <db2 instance ID> -u <db2 fenced ID>
    3. Using the DB2 instance id, restore the database backup image you made at the beginning of this section.
  3. Before upgrading to a DB2 pureScale instance:
    1. Using the DB2 instance id, check whether the database is pureScale compatible:
      <DB2 V10.5 instance sqllib path>/bin/db2checkSD <dbname> -l <output file>

      Correct any problems reported in the previous output file before proceeding to the next step.

    2. Using the DB2 instance id, perform an offline database backup.
    3. Using the DB2 instance id, drop the database.
    4. Ensure that the DB2 registry DB2COMM is set to TCPIP and that the DBM CFG SVCENAME is set properly. If not, see New WebSphere Commerce application deployment for details on how to set these parameters.
  4. Upgrade Enterprise Server Edition to a pureScale instance. You need to use the user id with root access:
    1. cd <DB2 V10.5 install path>/instance
    2. Run the following command to add one member and one CF:
      /db2iupdt -cf <hostname> -cfnet <netname-list> -m <hostname> -mnet
      <netname-list> -mid <member-id>-instance_shared_dev <device> -tbdev
      <device> -u <db2 fenced ID> <db2 instance ID>
    3. Run the following command to add one more member:
      /db2iupdt -add -m <hostname> -mnet <netname-list> -mid <member-id> <db2 instance ID>
    4. Run the following command to add one more CF:
       /db2iupdt -add -cf <hostname> -mnet <netname-list> <db2 instance ID>
    5. You can add more members and CFs as needed.
  5. Create GPFS file systems for storing data and logs:
    1. Using the user id with root access, run the command to create GPFS file system:
      db2cluster -cfs -create -filesystem <filesystem_name> -disk <disk-list> -mount <directory_name>

      Repeat the previous step if multiple GPFS file systems are required.

    2. Using the user id with root access:
      1. Create a subdirectory with the same name as the db2 instance id under the path of the GPFS file system.
      2. Change the ownership of the subdirectory to the DB2 instance id.
    3. Using the DB2 instance id, restore the database backup from "Step 3, Before upgrading to pureScale instance" to the GPFS file system created in the previous step.
    4. Using the DB2 instance id, enter:
      db2 activate db <dbname>

DB2 pureScale instance using a different operating system from the original ESE environment

If using a different OS than the original Enterprise Server Edition environment, you need to use other alternatives to move the database. This section explains how to use db2look to capture the object definitions for database creation and export/load utilities to move data. You can also use other methods, such as db2move, to accomplish the same task.

  1. In the original Enterprise Server Edition database environment:
    1. Using the DB2 instance id, capture all the object definitions (for example, tablespaces, buffer pools, tables, indexes, and so forth) to get the database recreated in the pureScale environment.
      db2look -d <dbname> -td@ -e -l -o <output file>

      where the output file is, for example, db2look.out.

      FTP the output db2look.out to the pureScale system.

    2. Using the DB2 instance id, export the data out from all the WebSphere Commerce tables.
      1. Retrieve the list of tables whose data are to be exported using:
        db2 list tables for schema <schema>

        The schema is the one that was used during WebSphere Commerce instance creation.
      2. Export data for each table returned in the previous list tables command:
        db2 export to <data file> of del select * from <schema>.<tablename>

        If the table contains a large object (LOB) column, you might need to add the option lobs to <lobpath>.

      3. FTP the data files to the pureScale system.
  2. In the DB2 pureScale instance, using the DB2 instance id:
    1. Ensure the DB2 registry DB2COMM is set to TCPIP and the DBM CFG SVCENAME is set properly. If they are not, see New WebSphere Commerce application deployment for details on setting these parameters.
    2. Create the database and associated objects:
      1. db2 create database <dbname> using codeset UTF-8 territory US

        using codeset UTF-8 territory US. WebSphere Commerce stores data with the settings of codeset UTF-8 and territory US, so you need to create the database by using the specific codeset and territory.
      2. db2 -td@ -f db2look.out
    3. Populate data
      1. Load data for each table in Step 1, as follows.
        db2 load from <exported data file e.g. data.del> of del insert into <schema>.<tablename>

        If the table contains a LOB column or generated column, you might need to add the lobs from <lobpath> or modified by generatedoverride options.

      2. Set the integrity for those pending tables, as follows.
        • Retrieve the list of tables in set integrity pending state:
          db2 “select tabschema, tabname from syscat.tables where status=’C’”
        • Set integrity for the list of tables returned above:
          db2 “set integrity <schema>.<table1>,
          <schema>.<table2>, ….,
          <schema>.<tableN> 
          immediate checked"
    4. Perform a database backup for recovery purposes.

WebSphere Commerce configuration after database setup

The following information applies for both scenarios (with the same and with different operating systems).

  1. Update the datasource in WebSphere Commerce:
    1. Log on to the WebSphere Application Server Admin Console and:
      • Select Resources -> JDBC -> Data sources -> WebSphere Commerce DB2 DataSource demo, then enter the Server name and Port number (at the bottom of the window).
      • Select Resources -> JDBC -> Data sources -> WebSphere Commerce DB2 Publish DataSource demo, then enter the Server name and Port number (at the bottom of the window).
      • Select Apply -> Save.
    2. Log on to Solr WebSphere Application Server Admin Console and:
      • Select Resources -> JDBC -> Data sources -> WebSphere Commerce Search DB2 DataSource demo, then enter the Server name and Port number (at the bottom of the window).
      • Select Apply -> Save.
  2. Update configuration files:
    1. Update DBHost and DBServerPort in the file:
      <WAS_install_dir>/profiles/<profile >/installedApps/WC_<profile>_cell/WC_demo.ear/xml/config/wc-server. xml
    2. Update DBHost and DBServerPort in the file: <WCS>/instances/<profile>/xml/<profile>.xml
  3. Restart WebSphere Commerce and Solr servers.

WebSphere Application Server application server configuration

To exploit the following DB2 pureScale features, you need to enable some configuration parameters from the WebSphere Application Server Admin Console:

  • Seamless automatic client reroute
  • Workload balancing
  • Alternate server list for first connect failure

Workload balancing and Alternate server list for first connect failure are enabled automatically if a WebSphere Commerce instance is created in V7 FP8 with the pureScale database option selected, as in Figure 7. For the migrated applications, follow the steps in this section.

To get started, log on to WebSphere Application Server Admin Console using:
https://<host_name>:<secure_port_number>/ibm/con sole/logon.jsp, where:

  • <host_name> is the machine where WebSphere Commerce is installed.
  • <secure_port_number> is the Administrative Console secure port specified in the file

    <WAS_install_dir>/profiles/<instance>/logs/AboutThisProfile.txt

Enabling seamless automatic client reroute

  1. Select Resources -> JDBC -> JDBC Providers -> “<profile> - WebSphere Commerce JDBC Provider” -> Data sources, as in Figure 13, where <profile> is the WebSphere Application Server Profile Name defined in WebSphere Commerce instance creation (see Figure 9). Our example uses demo2.
    Figure 13. Choose WebSphere Commerce data source
    Choose WebSphere Commerce data source
  2. Select WebSphere Commerce DB2 DataSource <profile> -> Connection Pool Properties, as in Figure 14.
    Figure 14. Choose Connection pool properties to modify
    Choose Connection pool properties to modify
  3. Click FailingConnectionOnly in the drop-down list below Purge policy, then select Apply -> Save to save the change, as in Figure 15.
    Figure 15. Modify Purge policy
    Modify the Purge policy

    For Java client applications, failover for automatic client reroute can be seamless or non-seamless. With non-seamless failover, when the client application reconnects to another server an error is always returned to the application to indicate that failover (connection to the alternate server) occurred. With seamless failover, the driver does not return an error if a connection fails and successful reconnection to an alternate server occurs during execution of the first SQL statement in a transaction.

    The Purge policy property specifies how to purge connections when a stale connection or fatal error is detected. The default is EntirePool, which means all connections in the pool are marked stale. FailingConnectionOnly means only the connection that caused the StaleConnectionExeption is closed. To enable WebSphere Application Server to support the seamless automatic client reroute (ACR), you should set the Purge policy with FailingConnectionOnly.

Enabling workload balancing

The DB2 pureScale environment provides applications with transaction-level or connection-level workload balancing (WLB) functions. When the first connection is made to the pureScale server, a list of all members and their capacity (priority or weight) is passed back to the client in a server list. The capacity values indicate the current load on a DB2 pureScale member. WLB relies on the server list to distribute application requests among the available DB2 pureScale members. To avoid overloading particular members when the client processing begins, the client automatically and transparently sends the transaction to a member that has a higher capacity value, which means a lower workload on it.

The configuration enableSysplexWLB=true is mandatory to enable WebSphere Application Server applications to take advantage of the transaction level WLB. The requests are distributed among the members according to the capacity of each member.

  1. Select Resources -> JDBC -> Data sources -> WebSphere Commerce DB2 DataSource <profile>, as in Figure 16.
    Figure 16. Choose WebSphere Commerce data source
    Choose the WebSphere Commerce data source
  2. Click Custom properties, as in Figure 17.
    Figure 17. Modify custom properties of the WebSphere Commerce data source
    Modify the custom properties of the WebSphere Commerce data source
  3. Click New, as in Figure 18.
    Figure 18. Create a new property for WebSphere Commerce data source
    Create a new property for the WebSphere Commerce data source

    Enter the following values:

    • Name: enableSysplexWLB
    • Value: true
  4. Select Apply -> Save, as in Figure 19.
    Figure 19. Add new property to enable WLB
    Add new property to enable workload balancing

WLB is not mandatory when using the DB2 pureScale feature. Client affinity is also supported. See Performance tuning for more information.

Enabling the enablealternateServerListFirstConnect feature

When a data source is created, the server name can be any member node in the pureScale cluster. When the first connection is made, a server list is returned from the pureScale server to the client to indicate that WLB (if enabled) will happen for the nodes contained in the returned server list, and that the nodes will be used for client reroute in case of ACR. However, it is possible that the member is not up yet when the first connection is made. For example, there might be a hardware failure on the member node to which the data source is configured to connect. In this case, the client cannot make the first connection to retrieve the server list from the server.

To resolve this issue, the enableAlternateServerListFirstConnect feature was introduced by DB2 in V9.7 FP1. Together with the clientRerouteAlternateServerName and clientRerouteAlternatePortNumber properties, it enables loading of the preconfigured alternate server list into memory when the application tries to open the first connection. It will try to connect to a different member in the pureScale cluster (specified in the list of clientRerouteAlternateServerName) on the first connection failure.

  1. Select Resources -> JDBC -> Data sources, then double click WebSphere Commerce DB2 DataSource <profile> -> Custom Properties.
  2. Click New, then enter the following values:
    • Name: enableAlternateServerListFirstConnect
    • Value: true
  3. Select Apply -> Save, as in Figure 20.
    Figure 20. Enable first connect failure
    Enable First connect failure
  4. Click New, then enter the following values:
    • Name: clientRerouteAlternateServerName
    • Value: <hostName>[, <hostName2>]
  5. Select Apply -> Save, as in Figure 21.
    Figure 21. Specify alternate server list for first connect failure
    Specify alternate server list for first connect failure
  6. Click New, then enter the following values:
    • Name: clientRerouteAlernatePortNumer
    • Value: <port number>[, <port number>]

      The port number is the same as the database manager configuration parameter SVCENAME.

  7. Select Apply -> Save, as in Figure 22.
    Figure 22. Specify the port number of the alternate server
    Specify the port number of the alternate server

Performance tuning

For optimal performance with pureScale DB2, use the guidelines described in Database performance tuning for WebSphere Commerce and pureScale.


Conclusion

In this article, you learned how to deploy DB2 pureScale Feature V10.5 on WebSphere Commerce V7 and how to enable WebSphere Commerce applications to take advantage of workload balancing and enableAlternateServerListFirstConnect features. The enablement procedures are as simple as adding and modifying a few custom properties of the WebSphere Application Server data sources from the WebSphere Application Server Admin Console. From the application perspective, there is only one single database view provided by the DB2 pureScale server.

Resources

Learn

Get products and technologies

  • Evaluate IBM products in the way that suits you best: Download a product trial, try a product online, or use a product in a cloud environment.

Discuss

Comments

developerWorks: Sign in

Required fields are indicated with an asterisk (*).


Need an IBM ID?
Forgot your IBM ID?


Forgot your password?
Change your password

By clicking Submit, you agree to the developerWorks terms of use.

 


The first time you sign into developerWorks, a profile is created for you. Information in your profile (your name, country/region, and company name) is displayed to the public and will accompany any content you post, unless you opt to hide your company name. You may update your IBM account at any time.

All information submitted is secure.

Choose your display name



The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerWorks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

Required fields are indicated with an asterisk (*).

(Must be between 3 – 31 characters.)

By clicking Submit, you agree to the developerWorks terms of use.

 


All information submitted is secure.

Dig deeper into Information management on developerWorks


static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=Information Management
ArticleID=977984
ArticleTitle=Deploy and explore the DB2 10.5 pureScale Feature with WebSphere Commerce V7
publish-date=07172014