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
--------------------------------------------------------------------------------
Thursday, June 23, 2011
Thursday, June 9, 2011
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.
- Use the Assets tool in Management Center to work with attachments, managed files, and managed directories.
- The stagingcheck utility has been discontinued.
- 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.
Subscribe to:
Posts (Atom)