Setting up AquaLogic Commerce Services
12 BEA AquaLogic Commerce Services Deployment Guide
1. Open the WEB-INF\commerce-config.xml under your Storefront web application root folder
and change the "userId.mode" value to "2".
In this mode, the system will generate a unique user id for each customer. This user id will
not be changed when customers log into the Storefront to
change their email address.
2. Repeat last step for your Commerce Manager web application.
Change user maintenance mode
By default, the Commerce Manager does not support the maintenance of a password when using
WebLogic authentication. To change this, the user maintenance mode needs to be changed as
follows.
1. Open the WEB-INF\commerce-config.xml under your Commerce Manager web application
root folder and change the "user.maintain.mode" to "2".
In this mode the create/delete customer and edit password functions will be disabled.
Change the customer mapping
When using WebLogic authentication, the password should not be stored in a local database. You
will need to change the customer Hibernate mapping file settings with the following steps.
1. Open WEB-INF\conf\spring\dataaccess\hibernate\mapping\Customer.hbm.xml under your
Storefront web application root and remove or comment out following lines:
<many-to-one column="AUTHENTICATION_UID"
unique="true"
lazy="false"
cascade="all"
name="customerAuthentication"
class="com.elasticpath.domain.customer.CustomerAuthentication"
fetch="select"/>
2. Repeate last step for your Commerce Manager web application.
Single sign-on cookie
To ensure Single Sign-on works without problems with your WebLogic Server and WebLogic
Portal applications, ensure that the
weblogic.xml file for those applications contains the
following settings:
<session-descriptor>
<cookie-name>JSESSIONID</cookie-name>
<cookie-path>/</cookie-path>
</session-descriptor>
