WebSphere Commerce search server: Advanced configuration
The advanced configuration deploys
the search server on local and remote machines by running the enablement
scripts on the machines you want to deploy WebSphere Commerce search.
The following diagram describes the overall advanced configuration
topology:
The
following diagram illustrates deploying WebSphere Commerce search
in the advanced configuration, where the WebSphere Commerce Server
and WebSphere Commerce search are running on separate machines where
a WebSphere Application Server cluster with multiple WebSphere Commerce
server and WebSphere Commerce search nodes (machine) is deployed for
scalability and failover support:
Where the following
cluster deployment configuration exists in the production environment:
- Code is installed on the primary node. The WebSphere Commerce application on the primary node can be added to the WebSphere Commerce cluster to handle live traffic.
- The search cluster can be manually created and the Solr.war file can be manually federated to the cluster to become the search subordinate server.
- The master search server or repeater can be a standalone server that is not managed by the deployment manager.
- Fixes and maintenance must be manually applied to each search subordinate and repeater server.
- The replication configuration on each subordinate server points to the repeater web server. For example, IBM HTTP Server (IHS).