Category: Build


DB2 Clients

So there are a few topics I wanted to cover relating to DB2 clients and how Commerce uses them. Type 2 vs. Type 4 drivers So strictly speaking, this is referring to the JDBC driver being used. Type 2 JDBC drivers are the traditional kind that require having a DB2 client installed, and the databases properly cataloged within that DB2...


How to catalog a DB2 database

So I’m doing a lot of posts in the DB2 Basics area this week. That’s because they are quick for me to write, and they’re questions I get all the time. So bear with me if you read for the more detailed Commerce topics – I’m not abandoning them. DB2 Client DB2 databases can be cataloged on DB2 servers or...


How to completely stop DB2

On Linux and Unix anyway. This is actually a common request during build when OS-level patches are applied or other OS-level work needs to be done, especially any related to disks. Stop Commerce (and/or any other applications) I’m not going to go into detail on this one – it is not my area of expertise. If I end up doing...



What is HADR? HADR is DB2’s implementation of log shipping. Which means it’s a shared-nothing kind of product. But it is log shipping at the Log Buffer level instead of the Log File level, so it can be extremely up to date. It even has a Synchronous mode that would guarantee that committed transactions on one server would also be...


DB2 for Commerce IDs

So the easy thing to do on Commerce build is to use your DB2 instance owner for everything related to the database. But that’s not really the best choice. It’s almost always the choice I see when a DBA was not involved with the architecture or build of a Commerce system. You’ll notice in the instance XML that there is an option...


Build Tip – DB2 Backups

Schedule DB2 backups starting immediately after instance creation – the most common time that restores are needed is during the build process. Of course the most common cause for needing a restore is human error, but that’s something that is important to protect against during build.


Build Tip – Database Naming

Just a quick tip. When building Commerce environments, select a different database name for each environment (Stage, Prod, etc), even if they are on different database servers. This will help you ensure that you(or developers or whoever else accesses the databases) never do something in the wrong environment. It adds a bit of complexity when you restore between different environments, but nothing that...


The role of the DBA in supporting WebSphere Commerce

I have generally been a bit disappointed on the information coming out of IBM on supporting Commerce databases. I also meet clients who don’t believe they need a dba or that they can hire someone out of college or with minimal database experience to fill such a role. In my opinion, any reasonably sized Commerce implementation needs a DBA, and unless...


Data Movement Options for Commerce Databases – Synchronizing Data Between Commerce Environments

So one of the most common questions I get is about moving data between homogenous Commerce databases. Our standard setup includes 4 environments – Dev, QA, Stage, and Prod. Dev/QA are a stagingprop pair, Stage/Prod are a stagingprop pair, and Prod usually has HADR. So with 4 environments, they can get out of sync. For the most part, business users are making...