6320ch_install_56.fm Draft Document for Review July 28, 2004 7:33 pm
174 Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide
4. The database window appears. Ensure that the Create a new DB2 database
or Oracle tablespace option is selected and that the Remote and Advanced
Options check boxes are not checked. Enter the following values and click
Next:
– Database administ rator name: <userid>
– Database administ rator password: <password>
– Confirm Datab ase administrator password: <password>
– Database name: test
– Database type: DB2
Where <userid> and <password> are the user ID and password for the
existing administrative user, which was used during the installation in 9.2,
“Installation” on page 165.
5. The Schema window appears. Enter the same user ID and password used in
the previous page and ensure that Use staging server is not checked and
that Set as active database is checked. Click Next.
6. It is not necessary to change the default values for the remaining pages. Keep
clicking Next until the Auction page appears. Then click Finish.
The Commerce Instance Creation Wizard will now begin the instance creation.
The progress can be monitored on the main Configuration Manager window
which may be hidden behind the Commerce Instance Creation Wizard.
The Commerce Instance Creation Wizard may prompt you to restart the Web
server as seen in Figure 9-1. Click OK to dismiss the dialog.
Figure 9-1 Web server restart prompt for commerce instance creation
If this happens, click OK to close the window and follow the directions in
Appendix A, “Managing WebSphere Commerce components” on page 239 to
restart the Web server.
Note: It is recommended to use a different non-administrative user ID for a
production system. For test purposes, we choose to reuse the
administrative user ID for the schema owner.