Tuesday, August 27, 2013

List of WCS site

B2C:

www.thenorthface.com
www.llbean.com
www.iconfitness.com
www.edwinwattsgolf.com
www.arcadiagroup.co.uk
www.sears.com
www.nokiausa.com/buy-online                        
www.ikea.com
www.argos.co.uk
www.moosejaw.com
www.sonystyle.com
www.panasonic.com
www.usa.canon.com
www.darty.com

B2B

Endorsia                        www.endorsia.com
Staples                          www.staples.com
Seagate Technolog         www.seagate.com
Roche Diagnostics         www.Roche-Diagnostics.com

How to clear the WebSphere class caches

IBM Support, may ask you to clear the class cache. There are several reasons for this. After an upgrade, it is possible that the class cache's are still holding onto previous versions of classes. It is also possible that the caches became corrupted.
Please remember there are two caches that will need to be cleared, the JVM's cache and the OSGi cache. The server has to be stopped before clearing the cache.

 To clear the OSGi class cache:
For UNIX platforms, run the following script in each profile:
<WebSphere_HOME>/profiles/profile_name/bin/osgiCfgInit.sh

 To clear the JVM's class cache (Windows, Linux and AIX only) :
For UNIX platforms, run the following script:
<WebSphere_HOME>/bin/clearClassCache.sh

How to enable Oracle JDBC Driver tracing with WebSphere Application Server v7

This document describes how to enable Oracle JDBC driver trace when using a datasource in WebSphere Application Server v7

Symptom

When debugging WAS + Oracle connection problems, it sometimes becomes necessary to enable Oracle JDBC driver tracing.

Resolving the problem

-Doracle.jdbc.Trace=true -Djava.util.logging.configureByLoggingPropertiesFile=true -Djava.util.logging.config.file=C:\WAS70\AppServer\profiles\AppSrvXML\logs\server1\OracleTrace\OracleTracing.properties

Forgot websphere admin console password

When you enable the security on WebSphere Application Server [WAS], it will prompt you for authentication when you access admin console, stop server and wsadmin prompt. As we discussed earlier in other blog post about WebSphere Security, all the security related settings are stored in config file under Profile_root/config/cells/cell_name.  File name is security.xml. The workaround when the administrator forgot the password is to change the security settings by manually modifying the security.xml file
  1. Locate the security.xml file and take a backup of it.
  2. open security.xml file for editing and search for enabled=”true
  3. modify it to enabled=”false” [you need to do this only for the very first occurrence of enabled=”true” ]
  4. Restart the servers
    1. Note: since you do not have the password you cannot stop the servers, so use KILL command
  5. Log into admin console
  6. Enable Security again
  7. Restart the servers.

Tips of Command context

At run time, each requested JSPs includes the EnvironmentSetup.jsp or EnvironmentSetup.jspf file. The command context is retrieved from this file.

some more soon.............

Do not want to restart WAS every time a properties file is changed

Nice feature available in WAS

We normally change properties files during development time, so need to restart server to impact the changes, how to properties file changes effect without restart server.

appropriate properties file location under the following directory.

stores\properties\com\ibm\commerce\tools\

1. Open wc-server.xml file
2. Change the value of developmentMode to "true". the default value is "false".
2. Restart WAS.