Skip to main content

Websphere Commerce Struts-Config.xml Properties

 

authenticate: specifies whether the view requires that the user is authenticated, i.e. that the user has to be a registered user (not guest or generic user).

<action path="/RequisitionListDisplayView" type="com.ibm.commerce.struts.BaseAction">
<set-property property="authenticate" value="10001:1"/>
</action>

credentialsAccepted: is used when you have partially authenticed users, i.e. users that have been remembered via the Remember Me function. If a user has not specifically authenticated (i.e. logged on via the Logon command), but has been remembered via the Remember Me persistent cookie, that user is considered partially authenticated my Commerce.

<action path="/LogonCmd" parameter="com.ibm.commerce.catalog.commands.LogonCmd" type="com.ibm.commerce.struts.BaseAction">
set-property property="credentialsAccepted" value="0:P" />
</action>

https: specifies whether the resource in question needs to be presented via HTTPS. If you try to access the resources via HTTP, Commerce will redirect you to an HTTPS version of the page.

<action path="/OrderItemDisplayView" type="com.ibm.commerce.struts.BaseAction">
<set-property property="https" value="0:1"/>
</action>

The value before the colon (:) is the store id. So you can have different https values for different stores, e.g. 10001:1, 10102:1


“0 “means it applies to all stores(site level). It does not make sense to have more than one 0:1. 

Comments

Popular posts from this blog

Dataload Utility

Data can be loaded into WCS tables using data load utility. WCS Data Load utility performs the following functions in a single operation: 1.                Reads the data from the input source file. 2.                Transforms the source data to Web Sphere Commerce business objects. 3.                Allocates and resolves Web Sphere Commerce business objects to physical data. 4.                Loads the physical data into the database. There are three configurations files and a input source file required to complete the data loader setup. WCS supports only CSV File Reader for other input source you have to write your own Reader Class. This means that if you are using OOB CSV Reader then your input file must be...

Issues While Starting WAS Server

This happens when there is other application which is also using the same port 8880. To resolve the issue, we need to find which application is using the port 8880 through 'netstat' command in command prompt or update our WAS server to not use 8880. We can update the WAS server through these steps: 1) Stop  WAS. 2) Browse to or search for the serverIndex.xml, for example, at "C:\WAS\AppServer\config\yourNode\nodes\yourNode\serverindex.xml" 3) Open the file and locate the following lines:               endPointName="SOAP_CONNECTOR_ADDRESS"> 4) Change "port 8880" to an available port 5) Save the serverindex.xml and restart WAS

ERROR HANDLING IN WCS

ECApplicationException : This exception is thrown if the error is related to user input and will always fail. For example, when a user enters an invalid parameter, an ECApplicationException is thrown. When this exception is thrown, the solution controller does not retry the command, even if it is specified as a retriable command. ECSystemException: This exception is thrown if a runtime exception or a Websphere Commerce configuration error is detected. Examples of this type of exception include create exceptions, remote exceptions, and other EJB exceptions. When this type of exception is thrown, the solution controller retries the command if the command is retriable and the exception was caused by either a database deadlock or database rollback. Both of the exception types are classes that extend from the ECException class, which is found in the com.ibm.commerce.exception package. In order to throw one of these exceptions, the following information must be specified...