Filter
Top Products
Appendix B. Backup WebSphere Commerce Suite V5.1 253
Draft Document for Review July 28, 2004 7:33 pm 6320ax03.fm
WebSphere Commerce Payments (formerly WebSphere Payment Manager), the
Web server, and the IBM Developer Kit Java 2 Technology Edition.
For example, you may have changed the IBM HTTP Server document root to a
directory outside the default WebSphere Commerce install directory. This
directory would need to be included in the backup. If you have any custom code
or jar files located outside of the default WebSphere Commerce install directory,
these directories and file would also need to be included in the backup.
Database
The WebSphere Commerce Suite V5.1 database, along with any additional
databases that your system requires needs to be backed up. For example, an
additional database that would need to be backed up would be the WebSphere
Commerce Payments database. Most likely, a database backup process has
been implemented for your system. You can use your normal procedures for your
site.
Database backup
Based on your configuration, a DB2 database backup can be performed from the
database server machine. The following are instructions on how to perform a
DB2 backup.
1. Logon to your Windows system as the Windows user ID that created the DB2
database, or that owns the DB2 database.
2. Complete all database transactions by shutting down your WebSphere
Commerce Suite V5.1 system.
3. Start a DB2 command window, by typing the following in a command window:
db2cmd
4. Ensure that all applications are disconnected from each database. To view a
list of all the applications that are connected to a database, run the following
command:
db2 list applications
If no applications are connected to your database, the following message
displays:
SQL1611W No data was returned by the Database System Monitor.
SQLSTATE=00000
If any applications are listed as being connected to your database, you will
need to locate the source of the application and shut it down. After you have