Deploying the WebSphere Commerce search server locally in the standard configuration
You can deploy the search server
on your WebSphere Commerce server by running the feature enablement
scripts. This script deploys the search server locally on a separate
application server profile. This enables the WebSphere Commerce server
to statically bind to the local dedicated search server and avoid
outgoing network communications to a remote machine.
Before you begin
- Ensure that you are logged on as the WebSphere Commerce non-root user.
- Ensure that you are logged on as a user that has *SECOFR authority.
- Ensure that the test server is stopped and that Rational Application Developer is not running.
- Ensure that your administrative server is started. For example:
- 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.
- If WebSphere Commerce is not managed by WebSphere Application Server Deployment Manager (dmgr), start the WebSphere Application Server server1.
- Ensure that WebSphere Commerce search is being deployed on a separate Web server. WebSphere Commerce search cannot share a Web server with a WebSphere Commerce instance. If you previously configured a Web server to be shared by a WebSphere Commerce instance and WebSphere Commerce search, you can follow the support document link in tsdsearchwebserver.html to get instructions for changing your configuration.
- Determine how you will configure the Web server for the Solr application.