![For IBM i OS operating system](../com.ibm.commerce.base.doc/images/ngibmi.gif)
![](../../common/../com.ibm.commerce.base.doc/images/ngibmi.gif)
![Windows](../com.ibm.commerce.base.doc/images/ngwin.gif)
![](../../common/../com.ibm.commerce.base.doc/images/ngwin.gif)
![AIX](../com.ibm.commerce.base.doc/images/ngaix.gif)
![](../../common/../com.ibm.commerce.base.doc/images/ngaix.gif)
![Linux](../com.ibm.commerce.base.doc/images/nglinux.gif)
![](../../common/../com.ibm.commerce.base.doc/images/nglinux.gif)
![Solaris](../com.ibm.commerce.base.doc/images/ngsolaris.gif)
Verifying
instance creation
You can verify the creation of an
instance by confirming the creation of instance-specific XML files
and logs. Check these files to ensure that your instance was created
successfully.
Procedure
- Confirm that the instance was created.
- Check configuration information for the new WebSphere Commerce instance: WC_profiledir/installedApps/WC_instance_name_cell/WC_instance_name.ear/xml/config/wc-server.xml
- Check instance log files:
WC_installdir/instances/instance_name/logs
WC_userdir/instances/instance_name/logs
If you are using IBM HTTP Server Web server, the following log file is produced during instance creation:
WC_installdir/instances/instance_name/httplogs/error_log
WC_installdir/instances/instance_name/httplogs/error.log
- Ensure that there are no errors in the following log files:
- createInstanceANT.err.log
- createInstanceANT.log
createdb.db2.log
- messages.txt
- trace.txt
Schema.log
sec_check.log
Note: The sec_check.log file is created when the instance is started.
- Check that the following log file is created:
WC_installdir/logs/WCSconfig.log
WC_userdir/logs/WCSconfig.log
WC_installdir/logs/reorgdb2.err.log
Note: Errors in the trace.txt file like the following example can be safely ignored:
date time java.lang.Class resolveRecord IdResGen The element with key "<acaction ACACTION_ID=10043 ACTION=BuyOrderApprovalSummaryView>" already exists in the database therefore this record will not be updated.
- Optional:
The non-root user was assigned the DB2 instance owner privilege when you created your new instance. You can choose to remove it:
- Refer to the your operating system documentation to remove the privilege from the non-root user.
- Edit the following file: non-root
user home/.profileRemove the line below the following entry:
db_instance_owner_home/.profile
- Optional: To test multiple instances:
- Start the application server and web server of your instance.
- Test the following URLs:
Original instance New instance - http://host1.domain
- http://host1.domain:5432/webapp/PaymentManager
- https://host1.domain
- https://host1.domain:8000/accelerator
- https://host1.domain:8002/adminconsole
- https://host1.domain:8004/orgadminconsole
- http://host2.domain
- http://host2.domain:5432/webapp/ PaymentManager
- https://host2.domain
- https://host2.domain:8000/accelerator
- https://host2.domain:8002/adminconsole
- https://host2.domain:8004/orgadminconsole