Filter
Top Products
6320ax03.fm Draft Document for Review July 28, 2004 7:33 pm
252 Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide
File system
The directories where WebSphere Commerce resides along with any other user
defined directory needs to be backed up. For example, the default installation
directory, configuration files, and any customized files and directories (generally
defined for static content).
Default directories
The default directories are made up of the installation directory including all its
subdirectories and files. Backing up these directories and files will ensure that all
files related to WebSphere Commerce will be included in the backup. In case
your file system differs from the default installation directory, be sure that all
configuration files for WebSphere Commerce, WebSphere Application Server,
and IBM HTTP Server are included in your backup. Since you may need to refer
to these directories and files during the migration process, these directories and
files should be backed up to a location that is easily accessible.
The following section gives examples of directories and files that should be
backed up. These examples are based on the default install directories of
WebSphere Commerce Suite V5.1.
Your instance configuration file:
C:\WebSphere\WCS\instances\instance_name\instance_name.xml
where instance_name is the name of your instance.
Your store property files, jsps, images, and other store related data:
C:\WebSphere\WCS\stores\properties
C:\WebSphere\WCS\stores\web
The WebSphere Application Server configuration file:
C:\WebSphere\WAServer\bin\admin.config
The IBM HTTP Server configuration file:
C:\WebSphere\HTTPServer\conf\httpd.conf
Custom directories
Custom files and directories that have been created for use with WebSphere
Commerce should be also backed up. Any components that are associated with
WebSphere Commerce such as the database, WebSphere Application Server,
Note: you will also have to backup you SSL certificates files used for the
SSL configuration in the httpd.conf file