IBM Learning video, audio and pdf available for free

IBM Education Assistance

This is a free site, any body can access and go through the learning sessions provided by them.

For WebSphere Commerce Suite learning, please visit the following url

http://publib.boulder.ibm.com/infocenter/ieduasst/v1r1m0/index.jsp?topic=/com.ibm.iea.wcs/plugin_coverpage.html

In the left side menu items of the loaded page search for "WebSphere Commerce"

Converting special Characters in properties file to UTF8 using native2ascii

Eg: Converting poland special charectres to native language
1.  Rename the file provided by the customer (i.e., storetext.properties) to storetext.nta
2.  Run the following command:                                                 C:\WebSphere\IBM\SDP\runtimes\basev7\java\bin\native2ascii -encoding utf-8 <.nta-file locaiton> <target file name with path>
3.  Target properties file is your converted file.

Enabling cross-site scripting protection

http://publib.boulder.ibm.com/infocenter/wchelp/v7r0m0/index.jsp?topic=/com.ibm.commerce.admin.doc/tasks/tsecsssp.htm

Delete the Web server definition in a standalone application server

The uninstaller program for the Web server plug-ins for WebSphere Application Server does not delete Web server definitions. However, you can delete a Web server definition from admin console OR by using the following wsadmin commands:

$AdminTask deleteServer { -serverName webserver1 -nodeName WebserverHostName-node_node }
$AdminTask removeUnmanagedNode { -nodeName WebserverHostName-node_node }
$AdminConfig save

Ex:
$AdminTask deleteServer { -serverName webserver1 -nodeName webserver1_node}
$AdminTask removeUnmanagedNode { -nodeName webserver1_node}
$AdminConfig save

Enabling trace for WSAdmin Tool

1. Enable tracing on the wsadmin tool. To do this, edit the WC_profiledir /properties/wsadmin.properties file. You must set the com.ibm.ws.scripting.traceString property to the correct trace specification. By default this line is commented out; be sure to remove the comment character (#) when you set the desired trace specification. The wsadmin client's trace file is WC_profiledir /logs/wsadmin.traceout.
2. Restart server1
3. Try to use wsadmin tool to manually export the EAR.
4. After the exception was thrown, collect the trace WC_profiledir/logs/wsadmin.traceout.

SOAP request Timeout

In wsadmin.traceout, the exception was thrown:org.apache.soap.SOAPException: [SOAPException: faultCode=SOAP-ENV:Client; msg=Read timed out; targetException=java.net.SocketTimeoutException: Read timed out]"
follows:
---------------------------
com.ibm.websphere.management.exception.ConnectorException: ADMC0009E: The system failed to make the SOAP RPC call: invokeat com.ibm.ws.management.connector.soap.SOAPConnectorClient.invokeTemplate(SOAPConnectorClient.java:642)at com.ibm.ws.management.connector.soap.SOAPConnectorClient.invoke(SOAPConnectorClient.java:512)at com.ibm.ws.management.connector.soap.SOAPConnectorClient.invoke(SOAPConnectorClient.java:332)
----------------------------
SocketTimeoutException was possibly thrown because the SOAP timeout was not be long enough, if the exporting of the ear takes longer than the value specified by the SOAP timeout, it would fail.The SOAP timeout parameter was specified in \opt\IBM\WebSphere\AppServer\profiles\FairPrice\properties\soap.client.props, as following in your environment:
#------------------------------------------------------------------------------
# SOAP Request Timeout #
# - timeout (specified in seconds [default 180], 0 implies no timeout)#
#------------------------------------------------------------------------------
com.ibm.SOAP.requestTimeout=180
#------------------------------------------------------------------------------
So I have following suggestion to resolve the problem:
1. Chanage com.ibm.SOAP.requestTimeout to 0 or a larger value (e.g. 3600)
2. Restart server1

Export fix while Applying APAR

Find exportEar.jacl under $Commerce_installDIR/config/deployment/scripts. Make a backup.
2. Change
$WCSHelper exportApplication $AppName $AppPath
to
$AdminApp export $AppName $AppPath
3. Launch UPDI and retry the APAR deployment

Prepare url dynamically in Javascript

<% String sWebAppPath=UIUtil.getWebappPath(request); %>string url = window.location.protocol + "://" + window.location.hostname + "/" + <%=sWebAppPath%> + "/" + ViewName

Creating Cookie in a Session

The ViewCommandContext offers the getResponse() method which can be used to gain access to the HttpServletResponse, from where you can add the cookies.

http://publib.boulder.ibm.com/infocenter/wchelp/v6r0m0/index.jsp?topic=/com.ibm.commerce.api.doc/com/ibm/commerce/command/ViewCommandContext.html

For example:

if ( commandContext instanceof com.ibm.commerce.command.ViewCommandContext ) {
 com.ibm.commerce.command.ViewCommandContext v = (com.ibm.commerce.command.ViewCommandContext)commandContext;
 javax.servlet.http.HttpServletResponse response = (javax.servlet.http.HttpServletResponse)v.getResponse();
 javax.servlet.http.Cookie myCookie = new javax.servlet.http.Cookie("name","value");
 response.addCookie(myCookie);
} 

Home Page - Getting Admin Console in Store Front

https://localhost:8004/webapp/wcs/orgadmin/servlet/BuyAdminConsoleView?

XMLFile=buyerconsole.BuySiteAdminConsole&

customFrameset=common.MerchantCenterFramesetRHS&

webPathToUse=/webapp/wcs/stores/servlet&

sidebarViewName=SidebarDisplayView&

headerViewName=HeaderDisplayView&

footerViewName=FooterDisplayView&

actionName=organization&langId=-1&

storeIdToUse=10051&

buyer=true

Create DB Schema (When Instance exists)

Command For Create Schema (When Instace exists):

/opt/IBM/WebSphere/CommerceServer60/bin/createdb.oracle.sh /opt/IBM/WebSphere/CommerceServer60/instances/instance-name/properties/createInstance.properties

Check the log for Errors:

/opt/IBM/WebSphere/CommerceServer60/logs/populateDB_oracle.log

Start and Stop Servers

Start Commerce Server:
/opt/IBM/WebSphere/AppServer/profiles/instance-name/bin/startServer.sh server1

Stop Commerce Server:
/opt/IBM/WebSphere/AppServer/profiles/instance-name/bin/stopServer.sh server1

Start WebServer:
/opt/IBMIHS/bin/apachectl -f /opt/IBM/WebSphere/CommerceServer60/instances/instance-name/httpconf/httpd.conf -k start

Stop WebServer:
/opt/IBMIHS/bin/apachectl -f /opt/IBM/WebSphere/CommerceServer60/instances/instance-name/httpconf/httpd.conf -k stop

HTTP Conf Syntax Check:
/opt/IBMIHS/bin/apachectl -f /opt/IBM/WebSphere/CommerceServer60/instances/instance-name/httpconf/httpd.conf -t

Commerce Product Updates Installation Check

/opt/IBM/WebSphere/CommerceServer60/properties/version/update/backup/NIFStack.xml

/opt/IBM/WebSphere/CommerceServer60/instances/instance-name/properties/version/update/backup/NIFStack.xml

SAR Publish Guide

Place your Store file under the following path:
/opt/IBM/WebSphere/CommerceServer60/starterstores

Folder structure should be:
SureshStore/samplecatalogs/SureshStoreCatalogData.sar
SureshStore/SureshStore.sar

/opt/IBM/WebSphere/AppServer/profiles/instance-name/installedApps/WC_instance-name_cell/WC_instance-name.ear/xml/tools/devtools/SARRegistry.xml

Connect to Commerce Admin Console as site level
Store Archives -> Publish
Select the appropriate Store and click on Publish.

WAS Deployment Scripts

cd /opt/IBM/WebSphere/AppServer/bin
./wsadmin.sh

$AdminApp update WC_instance-name partialapp {-contents /home/wcuser/temp/Packaging.zip}

$AdminConfig save

$AdminApp update WC_instancename modulefile {-operation addupdate -contents /home/wcuser/temp/WebSphereCommerceServerExtensionsData.jar -contenturi WebSphereCommerceServerExtensionsData.jar -nodeployejb -usedefaultbindings -defaultbinding.datasource.jndi "jdbc/WebSphere Commerce Oracle Datasource demo" -defaultbinding.cf.jndi "jdbc/WebSphere Commerce Oracle Datasource demo" -defaultbinding.cf.resauth Per_Connection_Factory}

$AdminConfig save