STRUTS Action-mapping Properties - WCS Tips

Popular Posts

• Extending an SOI service with UserData C ustomization of the Order noun by using the UserData field. This involves extending the Order noun of the Web services archite...
• Persistent Sessions in WCS WebSphere Commerce can be configured to enable persistent sessions. This enables some session-related information of the registered or gues...
• WCS Data Cache Data that is cached by the WebSphere Commerce data cache can be configured by using either the command caching or DistributedMap objects c...
• WCS Calculation Framework WCS need to calculate monetary amounts and apply them to business objects. Business rules and legal requirements specify how and when thes...
• WCS Commands in Catalog Subsystem The Catalog Subsystem contains all logic and data relevant to an online catalog, including catalog groups (or categories), catalog entries...
• Store with Multiple Languages and Multiple Currencies What if a store has to support multiple currencies to sell based on the language/country ? Here is a smal POC done to make it work. PFB...
• WCS Order Management Commnds The Order Management subsystem includes all logic and data relevant to placing, processing, and managing orders.  This is done using variou...
• WCS Subsystems WCS framework is majorly used fo E-Commerce Sites development on basis of many subsystems, which helps in developing and integrating diffe...
• WCS Promotions Promotions provide the ability to offer customers incentives to purchase. WebSphere Commerce supports numerous types of promotions. For e...
• WCS Payment Subsystem The Payments subsystem helps us manage the payment information. It connects to Payment Service Providers by using payment plug-ins. Paymen...

STRUTS action-mapping properties

Action-mappings elements associate a URL with a controller command. The syntax of the value attribute of the nested set-property element: a comma-separated list of storeID : propertyValue URL: The URL name. Store ID: The store reference number for this URI or 0 to mean any store. HTTPS: The value of 1 indicates that the request was expected to be received on a secure channel (HTTPS) and a redirect to the SSL port is done if it is received on an insecure channel (HTTP). The HTTPS setting for an ajax request does not take effect. The scheme that is used by the parent page takes effect. E.g., AjaxOrderItemAdd(Even if HTTPS setting is there, it goes as HTTP) on a Product display page (HTTP) E.g., In the below example, SampleCmd can be accessed over an in secure channel for any store other than 10161 <action-mappings type="com.ibm.commerce.struts.ECActionMapping"> <action path="/SampleCmd"parameter="com.xxx.xxx.xxx.xxx.SampleCmd" type="com.ibm.commerce.struts.BaseAction"> <set-property property="https" value="0:0,10161:1" /> </action> </action-mappings> Authenticate: The value of 1 indicates that user logon is required for this URI. Only non-guest, non-generic users (registered users) are allowed to access pages with Authenticate=1. If the user is requesting the page as an authenticated user, such as a registered user, then the request will continue. If the user is not authenticated, then it redirects the user to LogonForm, where they must authenticate before the initial request continues. E.g., In the below example, SampleCmd requires user to be logged in for the store 10161 <action-mappings type="com.ibm.commerce.struts.ECActionMapping"> <action path="/SampleCmd"parameter="com.xxx.xxx.xxx.xxx.SampleCmd" type="com.ibm.commerce.struts.BaseAction"> <set-property property="authenticate" value="10161:1" /> </action> </action-mappings> Credentials Accepted: When the authenticate property is set 1, the request requires an authenticated user, which means partial credentials. Partial credentials are provided when persistent sessions are enabled for a store and the user has selected "Remember Me". This creates a persistent cookie (WC_PERSISTENT) keeping their user ID. Upon return to the store in a new browser session, the detection of the persistent cookie allows WebSphere Commerce to partially authenticate the remembered user. If the authenticate property is set to 1, it requires authentication, but you can add an additional property called "credentialsAccepted". This indicates whether or not partial credentials are accepted. A partially authenticated user is a "Remembered" user. Setting the value to "P" means partial credentials are accepted. Partially authenticated users are those users that are logged off, but in a remembered user state. That is, when rememberMe is set to true for the Logoff command. Any other value (or the absence of the property means that partial credentials are not accepted. The user must be fully authenticated (or logged in within the browser session) to access a view or command. E.g., <action-mappings type="com.ibm.commerce.struts.ECActionMapping"> <action path="/SampleCmd"parameter="com.xxx.xxx.xxx.xxx.SampleCmd" type="com.ibm.commerce.struts.BaseAction"> <set-property property="credentialsAccepted" value="10161:P" /> </action> </action-mappings> Email ThisBlogThis!Share to XShare to FacebookShare to Pinterest

2 comments:

1. Unknown21 April 2017 at 22:59

   Valuable information! Thank You. Keep Sharing.Website Development services in Bangalore | website development company Bangalore | Ecommerce website development Bangalore | ecommerce development Bangalore

   ReplyDeleteReplies
   Reply
2. Unknown8 June 2017 at 01:21

   good info Uma! Thanks a lot.

   ReplyDeleteReplies
   Reply

Add commentLoad more... Home Subscribe to: Comments (Atom)

• Home
• WCS Subsystems
• Catalog Subsystem
• Order Management Subsystem
• Payment Subsystem
• Member Subsystem
• Marketing Subsystem
• Promotion Engine
• Promotions
• Calculation framework
• Calculation of Shipping Charge
• Payment Processing Flow
• Creating a new Payment Method
• Business Tools
• How to evaluate promotion without user adding the ...
• Redirect vs Forward
• WCS Persistence Layer
• Inventory Systems
• ATP vs Non-ATP Inventory
• Commands in the Order Flow
• Classification of Catalog Entries
• Design Patterns in WCS
• Caching
• How to install Cache Monitor ?
• Cache Invalidation
• How to import certificate file and its private key...
• Dynamic Kits Data model and Order flow
• Enabling Persistent Sessions in WCS
• STRUTS action-mapping properties

Blog Archive

• ▼  2017 (2)
  • ▼  October (1)
    • WCS Data Cache
  • ►  July (1)

• ►  2016 (12)
  • ►  October (12)

About Me

Uma Govindaraj A WCS developer View my complete profile

Total Pageviews