WebSphere Commerce Suite, WebSphere Application server, IBM HTTP Server and Oracle
Monday, March 22, 2010
Enabling cross-site scripting protection
Wednesday, December 2, 2009
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
$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
Tuesday, December 1, 2009
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.
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.
Thursday, November 12, 2009
Changing ORACLE LISTENER port number
Stop Listener
Change the port number in the following path:
D:\oracle\product\10.1.0\Db_1\NETWORK\ADMIN\listener.ora
Change the port number to desired port number and save.
Start the listener.
Run the following statement in the SQL prompt as sys dba.
ALTER SYSTEM SET LOCAL_LISTENER='(ADDRESS = (PROTOCOL = TCP)(HOST = host-name)(PORT = 1522))';
Check the status of listener, it should pick up your service name.
Change the port number in the following path:
D:\oracle\product\10.1.0\Db_1\NETWORK\ADMIN\listener.ora
Change the port number to desired port number and save.
Start the listener.
Run the following statement in the SQL prompt as sys dba.
ALTER SYSTEM SET LOCAL_LISTENER='(ADDRESS = (PROTOCOL = TCP)(HOST = host-name)(PORT = 1522))';
Check the status of listener, it should pick up your service name.
Monday, November 2, 2009
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
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
2. Change
$WCSHelper exportApplication $AppName $AppPath
to
$AdminApp export $AppName $AppPath
3. Launch UPDI and retry the APAR deployment
Friday, September 25, 2009
Prepare url dynamically in Javascript
Wednesday, September 23, 2009
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:
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);
}
Tuesday, September 22, 2009
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
Monday, September 21, 2009
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
Subscribe to:
Posts (Atom)