Tunning WCS Developer toolkit

In addition to increasing the JVM heap size, you can perform few more tuning to developer toolkit to improve the performance of development toolkit.

Tuning Apache Derby Database

Derby is a filesystem based database, there are few minor configuration changes that can be
performed on the toolkit Derby properties to improve overall performance of the WCS Developer Toolkit.

The file is located in following location for WCS V7:
IBM\SDP\runtimes\base_v7\derby\derby.properties


With this Derby will be able to access data from cache instead of filesystem, this will reduce overall I/O as data will be read from the cache.

derby.storage.pageCacheSize = 10000
derby.storage.pageSize = 8192

How do enable web service(Webservices over HTTP) in Websphere commerce?

1. Open the Administration Console and select Site or Store.
2. Click Configuration > Transports.
3. The Webservices over HTTP transports should appear in the list and as inactive.

If the transport want to configure is active

1. Select the check box next to the inactive transport.
2. Click Change Status.
3. The transport status should change from Inactive to active.

Enable database SQL statement trace log on Dev

1. Logon WebSphere Administrative console.
2. From left panel select Troubleshooting-->logs and trace->server1->change log details levels
3. Expand com.ibm.ejs.*
4. Expand sub element com.ibm.ejs.persistences.*
5. Enable all Messages and traces for com.ibm.ejs.persistence.EJSDBCFinder and com.ibm.ejs.persistence.EJSJDBCPersister.



6. Click OK and Save.
7. Restart App Server.

Listing enabled WebSphere Commerce features in development environment

we can list the features that have been enabled on WCS 7.

1. Run the check enablement status: WCDE_installdir\bin\checkEnablementStatus.bat
2. The status message appears in the log file. WCDE_installdir\logs\enableFeature.log

Create new Websphere Commerce Database schema using developer machine

Steps to follow

1. Create a user (schema) with DBA privileges in oracle 11g.
2. Go to command prompt where WCS Installed
Ex: D:\WCDE_ENT70\bin>
3. Prepare setdbtype.bat statement.
Ex: setdbtype oracle D:\app\testuser\product\11.2.0\client_1 UATDB wcs7 wcs7 wcs7 wcs7 192.168.140.2 1521 createdb

4. Execute the setdbtype.bat file as mentioned above.


5. setdbtype.bat command will open one more window


6. Verify the createdb.oracle.log file.
7. WCS schema created.

How do you find installed product in Websphere commerce?

if it's windows:

<WCS_INSTALLER>\bin>versionInfo.bat

WVER0010I: Copyright (c) IBM Corporation 2002, 2005; All rights reserved.
WVER0012I: VersionInfo reporter version 1.15.1.13, dated 3/29/06

--------------------------------------------------------------------------------
IBM WebSphere Application Server Product Installation Status Report
--------------------------------------------------------------------------------

Report at date and time June 23, 2011 5:45:22 PM IST

Installation
--------------------------------------------------------------------------------
Product Directory D:\WCDE_E~1
Version Directory D:\WCDE_E~1\properties\version
DTD Directory D:\WCDE_E~1\properties\version\dtd
Log Directory D:\WCDE_E~1\logs
Backup Directory D:\WCDE_E~1\properties\version\update\backup
TMP Directory C:\DOCUME~1\testuser\LOCALS~1\Temp

Product List
--------------------------------------------------------------------------------
Installed Product
--------------------------------------------------------------------------------

Name IBM WebSphere Commerce
Version 7.0.0.2
ID wc.toolkit.be
Build Level 101129asup
Build Date 30/11/10

Installed Product
--------------------------------------------------------------------------------
Name IBM WebSphere Commerce
Version 2.0.0.0
ID wc.fep2
Build Level 101126dev
Build Date 26/11/10

--------------------------------------------------------------------------------
End Installation Status Report
--------------------------------------------------------------------------------

Deprecated functionality in Authoring Server in WCS 7

1. Managed Files

• The Manage Files feature in WebSphere Commerce Accelerator is deprecated for WebSphere Commerce Version 7 Feature Pack 2. This feature was used to upload new catalog files, such as images of products for your store, or to reorganize existing files.

Rcommanded Action:

• Use the Assets tool in Management Center to work with attachments, managed files, and managed directories.

2. stagingcheck utility

• The stagingcheck utility has been discontinued.

Rcommanded Action:

• As an alternative, run the stagingprop utility with the transaction parameter set to one (the default value) and the batchsize parameter set to 0. If an error is encountered during the stagingprop transaction, then the entire process is rolled back without any changes to staging or production servers.