Enabling Store
Enhancement feature for WCS v7
Table of Contents
Note: This document only summarizes the steps of
configuration for more details do select the selected URL with CTRL+Click from
keyboard.
After you
install the feature pack, you must enable the starter store enhancements
feature to take advantage of the store features.
After you
enable the starter store enhancements feature, the following store archive (.sar) files are available for publishing:
- MayUJoy starter store (MayUJoy.sar)
Provides all the pages and features necessary for a functioning
consumer direct online store for the Chinese market.
- Brazil starter store (Brazil.sar)
Provides all the pages and features necessary for a functioning
consumer direct online store for the Brazilian market.
- Madisons starter store
enhancements (MadisonsEnhancements.sar):
Remote widgets store enhancements- Digital wallet functionality
Coshopping functionality- Search integration
- Subscriptions and recurring
orders
- Support for Management Center
price lists and price rules
Store pages that are tagged with
the latest set of WebSphere Commerce analytics tags for IBM Digital
Analytics, formerly known as Coremetrics Analytics- e-Marketing Spots that support
dynamic recommendations from IBM Product Recommendations, formerly
known as Coremetrics Intelligent Offer
- Dynamic kit integration with
Sterling Configurator
Facebook integration- Elite starter store enhancements (EliteEnhancements.sar and EliteStorefrontAssetStore-FEP.sar):
- Search integration
- Store pages that are tagged with
the latest set of WebSphere Commerce analytics tags for IBM Digital
Analytics, formerly known as Coremetrics Analytics
- e-Marketing Spots that support
dynamic recommendations from IBM Product Recommendations, formerly
known as Coremetrics Intelligent Offer
- Dynamic kit integration with
Sterling Configurator
- Madisons mobile enhancements (MadisonsMobileEnhancements.sar):
- Mobile starter stores for
smartphone and tablet devices:
- Mobile web starter stores
- Mobile applications for Android
and iOS
Aurora starter store (Aurora.sar):
IBM Tealeaf Customer Experience
integration- e-Marketing
Spot and wish list feeds
- Click-to-edit
function
- Advanced
Search page
- Support
for Dojo 1.8
- Hebrew
language translation
- Tolerance
for tablet devices
- Product-specific
swatch images
Note: There are
no enhancement store archive (.sar) files for the Aurora
starter store. To obtain the latest Aurora store features for a specific
feature pack, republish the Aurora.sar file
after you install the feature pack and enable starter store enhancements.
[VT1]
[VT1] - Aurora mobile enhancements (AuroraMobile.sar):
- Mobile starter stores for
smartphone and tablet devices:
- Mobile web starter stores
- Mobile applications that use IBM
Worklight
2.0
Before you begin
1)
Ensure that you are logged on as the WebSphere Commerce non-root
user.
2)
Ensure that you are logged on as a user that has *SECOFR
authority.
3)
Review the prerequisite steps in Enabling features.
|
2.1 Enabling features
After you install a WebSphere Commerce feature pack, you can
enable any of the included features to enhance your WebSphere Commerce
instance.
Before you begin
 There are issues
that are related to database schema creation when you use DB2 V9.7 Fix Pack 5
or later. See: Database
schema creation might fail on DB2 V9.7 Fix Pack 5 (or later) when you install
or upgrade from a WebSphere Commerce version older than V7.0.0.6 Important: If
you plan to use DB2 Version 9.7 database, you must change the development database type before
you enable features.
Depending on the feature pack level you have installed, modify
one or more of the following files:
In each applicable SQL file, you must change any table space
references so that they point to your custom table spaces. Feature packs are
cumulative, so if you are on a later feature pack, files for lower-level
feature packs will already be present on your system and will need to be
modified.
About
this task
If you
enable a high-level feature, lower-level features are enabled automatically.
The following table shows the dependencies between the features.
Procedure
Enable
one or more features (FP 4 onwards):
NOTE: For more details follow the Hyperlink by CTRL+Click on
eeach link above
|
4) Ensure that the test server
is stopped and that Rational Application Developer is not running.
5) Ensure that your
administrative server is started. For example:
o
If WebSphere Commerce is managed by WebSphere Application Server
Deployment Manager (dmgr), start the deployment manager and all node agents.
Your cluster can also be started.
o
If WebSphere Commerce is not managed by dmgr, start the WebSphere
Application Server server1.
6) Determine how you are going
to deploy the WebSphere Commerce search server:
Deploys the search server
locally on a separate application server profile. This method enables the
WebSphere Commerce server to statically bind to the local dedicated search
server and avoid outgoing network communications to a remote machine.
Deploys the search server
remotely, depending on your environment. It prepares the deployment package to
copy and run the deployment scripts on a remote search machine, where a search
profile and web module is deployed.
Note:
To support personalization in remote widgets and feeds,
persistent sessions and personalization ID must be enabled. When you run the
enablement script, the script checks the WebSphere Commerce configuration file
for the current settings:
|
|
Enabled
|
Disabled
|
|
Persistent sessions
|
The script does not
change the setting.
|
The script enables
persistent sessions.
The
script sets the Cookie expiry (days) value to -1. As a result, sessions do not
persist because the number of days is a negative number.
To
persist sessions, change the Cookie expiry (days) value to a positive number of
days.
|
|
Personalization ID
|
The script does not
change the setting.
|
The script enables
personalization ID.
|
- Complete
one of the following tasks:
Log on as a WebSphere Commerce
non-root user.
Log on with a user ID that is a
member of the Windows Administration group.
Log on with a user profile that
has *SECOFR authority.- Go
to the following directory:
- WC_installdir/bin
- WCDE_installdir\bin
- As
the WebSphere Commerce non-root user, increase the file handle limit.
- Increase the file handle limit
with the command: ulimit -n 8192
- As the root user grant USE
authority to the non-root user. Switch to the non-root user and issue the
command: ulimit -n 8192.
You can also issue the command as the root user, then switch to the
non-root user.
- Run
the enablement script. Running the starter store enhancements
enablement script also enables the Management Center feature. That
is, if the Management Center feature is disabled, it is enabled after you
run the starter store enhancements enablement script.
- config_ant.bat
-buildfile WC_installdir/components/common/xml/enableFeature.xml
-DinstanceName=instance_name -DfeatureName=store-enhancements
-DdbUserPassword=db_password [-DdbaPassword=dba_password] [-DSolrWASAdminUser
= solr_wasadminuser] [-DSolrWASAdminPassword =solr_wasadminpassword]
[-Dscchost=HostForScheduledJobs] [search_server_config] [-DsearchPort=searchPort] - ./config_ant.sh
-buildfile WC_installdir/components/common/xml/enableFeature.xml
-DinstanceName=instance_name -DfeatureName=store-enhancements
-DdbUserPassword=db_password [-DSolrWASAdminUser = solr_wasadminuser]
[-DSolrWASAdminPassword = solr_wasadminpassword] [-Dscchost=HostForScheduledJobs] [search_server_config] [-DsearchPort=searchPort]
- ./config_ant.sh
-buildfile WC_installdir/components/common/xml/enableFeature.xml
-DinstanceName=instance_name -DfeatureName=store-enhancements
-DdbUserPassword=db_password [-DdbaPassword=dba_password] [-DSolrWASAdminUser
= solr_wasadminuser] [-DSolrWASAdminPassword =solr_wasadminpassword] [-Dscchost=HostForScheduledJobs] [search_server_config] [-DsearchPort=searchPort]
- enableFeature.bat
-DfeatureName=store-enhancements
Where:
instanceName
The name of the WebSphere
Commerce instance with which you are working (for example, demo).
featureName
The name of the WebSphere
Commerce feature to enable (for example, store-enhancements).
dbUserPassword
The password for the user
who is connecting to the database.
dbaPassword
The dbaPassword is
required when you are enabling the feature on an Authoring server.
SolrWASAdminUser
The WebSphere Application
Server administrator user ID for the Solr cell. This parameter is required only
if all three of the following conditions are met:
- You
enabled a previous version of Search from an earlier WebSphere Commerce
feature pack
- You
enabled WebSphere Administration Server administrative security on the
Search server
- You
are not specifying remoteSearchEngine=true
SolrWASAdminPassword
The WebSphere Application
Server administrator password for the Solr cell. This parameter is required
only if all three of the following conditions are met:
- You
enabled a previous version of Search from an earlier WebSphere Commerce
feature pack
- You
enabled WebSphere Administration Server administrative security on the
Search server
- You
are not specifying remoteSearchEngine=true
scchostThe name of the host
(server) on which the scheduled job runs. Use this parameter if your
organization chooses to schedule jobs to run only on a specific host.
The WebSphere Commerce scheduler runs the RefreshRegistry command to ensure that the latest data from the CMDREGtable is used by the WebSphere
Commerce CommandRegistry. The job runs only if
the CMDREG table was modified. It runs only
once, shortly after enablement is completed. By default, this scheduled job run
is set to run on any host. If you want to run on a specific host, use this
parameter to define the specific host.
Note: The search server is
deployed when the foundation feature is enabled.
remoteSearchEngineUse this parameter with a
value of true when you are deploying Solr search server on a remote
machine.The search_server_config options
help automate updating the web server configuration for IBM HTTP Server. If you
do not use this option, you must manually configure your web server after you
run the enablement script, as described in the next step. When thesearch_server_config options
are used, WebSphere Commerce search helps automate creating the web server
configuration. This automation is achieved by passing in more configuration
parameters when you run the enablement scripts.
Important: The automated web
server configuration supports IBM HTTP Server (IHS) only. That is, it does not
support or include steps for configuring non-IHS web servers such as IIS and
SunOne. For other types of web servers, consult the documentation that is provided
by the web server vendor to update the configuration.
This approach includes the
following considerations:
- The
WebSphere Commerce search web server's httpd.conf file is automatically
created.
- You
can set up a valid configuration where the WebSphere Commerce search and
WebSphere Commerce web servers have separate configuration files. That
is, you do not need to manually update the plugin-cfg.xml files.
- If
preferred, you do not need to install another copy of IBM HTTP Server.
The same installation can be shared with the WebSphere Commerce web
server.
A second IHS process is launched to handle
search HTTP requests that use the same IHS installation. A second process
ensures that the configurations do not collide, while easing configuration and
maintenance.
Important: You can skip updating
the web server configuration if you previously enabled the feature foundation
and passed in thesearch_server_config parameters during the
enablement. you can also skip the update if your Solr web server is already
configured.
The following list shows
the available parameters with brief explanations of each. Examples can be seen
in the following task, along with more-detailed descriptions of each parameter
and when it is needed and not needed:
The scripts validate the
values that are provided for any required parameters. If values for required
parameters are blank, the scripts do not proceed. The error message indicates
which values must be specified. An example of such an error can be viewed in
the following troubleshooting reference:
Where search_server_config includes
the following parameters that help automate updating the web server
configuration for IBM HTTP Server:
autoConfigSearchWebserver
The flag that turns on or
off the automation. It indicates whether to automatically configure the IHS web
server. The default value is false.
If set to false, or if not
specified in the script, you must manually configure your search web server.
isShareWCWebserverProduct
Indicates whether the IHS
server is shared with WebSphere Commerce. The default value is false.
If set to true, the
parameter values listed below are automatically retrieved. However, you must
specify the FTP password, as it is not typically stored on disk for security
purposes.
searchWebserverHostname
The fully qualified host
name for the WebSphere Commerce Search web server.
searchWebserverOS
Indicates which operating
system is used on the search web server host.
searchWebserverInstallLocation
The WebSphere Commerce
search installation location.
searchPluginInstallLocation
The WebSphere Commerce
search plug-in installation location. This parameter is required when you use a
separate IHS installation.
searchRemoteConfigPath
The path on the remote IHS
machine where the WebSphere Commerce Search web server's file is stored.
searchIsConfigViaFTP
Indicates whether to
transfer the configuration files using FTP.
The FTP
parameters include:
searchFtpServerPort
The WebSphere Commerce
search FTP server port.
searchFtpUserId
The WebSphere Commerce
search FTP user ID.
searchFtpUserPwd
The WebSphere Commerce
search FTP user password.
searchIsConfigViaNFS
Indicates whether to
transfer the configuration files using a locally mapped or mounted drive.
The
mapped parameters are:
searchMappedConfigPath
The directory to which the
search web server configuration files are copied.
Files and directories are
created under the searchMappedConfigPath/instance_name_solr
directory.
Examples
The following examples
outline the typical scenarios when configuring the WebSphere Commerce search web
server:
Replace [search_server_config] in the command line with the following parameter if you are:
- Not
using the automated IHS web server configuration.
-DautoConfigSearchWebserver=false
Replace [search_server_config] in the command line with the following parameters if you
are:
- Using
the automated IHS web server configuration,
- Sharing
the IHS from your WebSphere Commerce instance, and
- Your
IHS is local.
-DautoConfigSearchWebserver=true
-DisShareWCWebserverProduct=true
Replace [search_server_config] in the command line with the following parameters if you
are:
- Using
the automated IHS web server configuration,
- Sharing
the IHS from your WebSphere Commerce instance,
- Your
IHS is remote, and
- Your
WebSphere Commerce web server does not use FTP or NFS for remote
configuration. Or your WebSphere Commerce web server uses NFS for remote
configuration and the NFS mount is in place.
-DautoConfigSearchWebserver=true
-DisShareWCWebserverProduct=true
Or, if your WebSphere
Commerce web server uses FTP for remote configuration:
-DautoConfigSearchWebserver=true
-DisShareWCWebserverProduct=true -DsearchFtpUserPwd=your_FTP_password
Where your_FTP_password is
the password for the FTP server running on your IHS web server host.
Or, when you want to ensure
that FTP or NFS is not used for remote configuration:
-DautoConfigSearchWebserver=true
-DisShareWCWebserverProduct=true -DsearchIsConfigViaFTP=false
-DsearchIsConfigViaNFS=false
Replace [search_server_config] in the command line with the following parameters if you
are:
- Using
the automated IHS web server configuration,
- Using
a separate IHS,
- Your
IHS is remote, and
- You
are not automatically transferring the files to the remote machine.
-DautoConfigSearchWebserver=true
-DisShareWCWebserverProduct=false
-DsearchWebserverHostname=yourSearchIHSHostName
-DsearchWebserverInstallLocation=thePathToIHSInstallDirOnYourSearchIHSHost
-DsearchPluginInstallLocation=thePathToPluginInstallDirOnYourSearchIHSHost
-DsearchRemoteConfigPath=pathWhereSearchIHSConfigFilesWillReside
For example:
-DautoConfigSearchWebserver=true
-DisShareWCWebserverProduct=false
-DsearchWebserverHostname=search.example.com
-DsearchWebserverInstallLocation=/usr/IBM/WebSphere/HTTPServer
-DsearchPluginInstallLocation=/usr/IBM/WebSphere/HTTPServer/Plugins
-DsearchRemoteConfigPath=/usr/IBM/WebSphere/HTTPServer/solrHttpConf1
The WebSphere Application
Server virtual host port number to listen on for the WebSphere Commerce search
application.
The value must be a valid
and available TCP port.
The default value is 3737.
If the script runs successfully in the runtime
environment, a BUILD SUCCESSFUL message appears in the command window
where you ran the script and in the WC_installdir/instances/instance_name/logs/enablestore-enhancements_timestamp.log file. For enablement
details, see theWC_installdir/instances/instance_name/logs/enablestore-enhancements_timestamp.log log file.
If the script runs successfully, the
message enableFeature.bat completed is displayed in the
command window. For enablement details, see the WCDE_installdir\logs\enableFeature.log file.
The following configuration
options are available, depending on your web server and WebSphere Commerce
Feature Pack version:
- WebSphere
Commerce search deployment tasks include steps to manually update the web
server configuration for IBM HTTP Server (IHS).
This approach includes the following
considerations:
- You
created the WebSphere Commerce search web server httpd.conf file.
- A
directive to listen on the search virtual host port is added.
- The
web server plug-in is installed on the web server host.
- WebSphere Commerce search
deployment tasks include steps to help automate updating the web server
configuration when using IBM HTTP Server (IHS). This automation is
achieved by optionally passing in more configuration parameters when you
are running the enablement scripts during the previous step. For more
information, see the previous step.
- For
configuring non-IHS web servers such as IIS and SunOne, consult the
provided documentation to update the configuration.
- Republish the application:
- Open WebSphere Commerce Developer and
switch to the Enterprise Explorer view.
- Right click LOBTools and
select OpenLaszlo Migration > Compare
Customizations.
- Rebuild any projects that are
required to be rebuilt in the workspace. For example:
- Rebuild LOBTools.
Right-click LOBTools, then select Build OpenLazlo
Project
- Start the WebSphere
Commerce Test Server. Some errors are displayed in the console.
These errors can be safely ignored.
- In the Servers view, right-click
the test server then click Publish.
- Wait for the application to
finish publishing and to restart. Ensure that no errors are displayed.
g.
If you customized a previous version of Management Center,
see Migrating Management Center to migrate
those customizations to the latest Management Center version.
- Ensure
that you publish the Madisons store archive after you install Feature Pack
1 or later. You might see a different store name for Madison starter
store, depending on your version of the installed Feature Pack. If Feature
Pack 1 is installed, the store name isMadisons.sar. If Feature Pack 2 or later is
installed, the store name is Madisons-FEP.sar. When you install Fix Pack 1 or
later, a new version of Madisons.sar is installed, containing the
latest fixes and necessary extension points. The Brazil starter
store, MayUJoy starter store, and Madisons starter store enhancements
store archives do not function correctly with earlier versions of the
Madisons starter store.
- If
you are enabling starter store enhancements in the WebSphere Commerce
development environment, the default configuration includes a Derby
database with all base, non-feature pack, starter stores, including the
Madisons starter store, pre-published. If you require a feature pack
version of a starter store, publish the feature pack version by using a
different store name. You can create a database without the pre-published
stores or restore to a clean bootstrap Derby database. Then, you can
publish the feature pack version of the starter store. Also, when you
configure the WebSphere Commerce development environment you can select to
a new bootstrap Derby database without the prepublished starter stores.
- See: First steps after enabling features.
If you
encounter problems while installing a WebSphere Commerce feature pack or
enabling a feature on a WebSphere Commerce instance, review this section for
common issues.
- Troubleshooting: WebSphere Commerce feature pack
install or uninstall failed
Review this information if the installation or uninstallation of a WebSphere Commerce feature pack fails. - Troubleshooting: Checking that the WebSphere
Commerce feature pack is installed on your machine
After installing a WebSphere Commerce feature pack, you want to ensure that the feature pack is installed correctly. - Troubleshooting: Checking that a WebSphere Commerce
feature is enabled on your instance
After installing a feature pack, you can enable one or more features. You enable a feature on a WebSphere Commerce instance. After enabling the feature you should verify the enablement is successful. 
Troubleshooting: Errors ORA-01017, SQL30082N occur
during feature enablement
When you are enabling a feature on your WebSphere Commerce instance, a BUILD FAILED message is displayed.- Troubleshooting: Errors WASX7023E, WASX7213I,
WASX8011W, WASX7206W occur during feature enablement
During a configuration or administration task, such as feature enablement, you receive errors similar to the following:" 
Troubleshooting: Database connectivity
You can encounter database connectivity issues when you are creating instances, applying fix packs, enabling features, or running many WebSphere Commerce utilities. You can use the database connection validation utility to determine whether any configured database parameters that required to establish a database connection is invalid.- Troubleshooting: web.xml was not found error after
enabling features
After enabling all features, the application server starts successfully, but the Management Center cannot be accessed. An error in the logs states that "web.xml was not found". - Troubleshooting: java.net.SocketTimeoutException
error logged
A java.net.SocketTimeoutException is met while performing a WebSphere Application Server operation over SOAP. - Troubleshooting: ConnectorNotAvailableException
while executing wsadmin script
Feature enablement or disablement fails while executing a wsadmin script, such as a jacl script. - Troubleshooting: WebSphere Commerce feature
enablement fails with a NullPointerException or OutOfMemoryError
When you attempt to enable a feature, the operation fails with a NullPointerException or an OutOfMemoryError. - Troubleshooting: Unable to use the unzip command to
decompress downloaded e-images
After transferring an e-image to a Linux or Solaris system, you are unable to use the unzip command to unzip the e-image zip file. 
Troubleshooting: CMDREG data not properly restored
during foundation feature disablement
In WebSphere Commerce Version 7 Feature Packs 1, 2 and 3, when foundation is enabled, component specific rows are extracted from the existing CMDREG table and saved to a file. This occurs during enablement immediately before updates are applied to the CMDREG table. When foundation is disabled, the data is restored from that backup file so that the table is restored to its pre-enablement state.
Troubleshooting: Massload error when using DB2
When using DB2 v9.5 Fix Pack 4 or Fix Pack 5, or DB2 v9.7 Fix Pack 1, if you perform an operation that uses the massload utility, such as creating an instance, installing a fix pack, or issuing a setdbtype command, the operation might fail.- Troubleshooting: Ant properties error occurs during
feature enablement
When you try to enable a feature, you receive an error that states that values must be given for required Ant properties. - Troubleshooting: IllegalArgumentException after
feature enablement
Receive IllegalArgumentException in SystemOut.log after you upgrade or migrate from a lower feature pack to a higher feature pack and enable a feature. - Troubleshooting: DB2 SQL Error: SQLCODE=-552,
SQLSTATE=42502 during feature enablement
When you attempt to enable a feature on Microsoft Windows 2008, you receive the following error: DB2 SQL Error: SQLCODE=-552, SQLSTATE=42502.
No comments:
Post a Comment