WebSphere Commerce search server: Standard configuration
The WebSphere Commerce search server
can be deployed on your WebSphere Commerce or WebSphere Commerce Developer
machine in the standard configuration. The standard configuration
mode creates and deploys a separate search profile and Web module
on the same machine as the WebSphere Commerce profile.
The following diagram illustrates deploying WebSphere
Commerce search in the standard configuration, where the WebSphere
Commerce Server and WebSphere Commerce search are running on separate
JVMs:
Where WebSphere Commerce server and WebSphere Commerce search is deployed on a single machine.
Where WebSphere Commerce server and WebSphere Commerce search is deployed on a single machine.
Note: 2 GB of additional memory is required for
the WebSphere Commerce search server.
The
following list summarizes the WebSphere Commerce search deployment
in the standard configuration:- It contains a dual WebSphere Application Server profile, with WebSphere Commerce and WebSphere Commerce search, on the same (non-managed) node.
- It uses a separate JDBC datasource and separate JVM heap space.
- It uses a common database. DB2, Oracle, or IBMi.
- Indexes are created locally and synchronized between two WebSphere Application Server profiles.
- WebSphere Application Server security is enabled:
- Administrative security is enabled on the WebSphere Commerce server.
- A self-signed certificated is imported by default. You must import your own CA-signed certificate in production environments.
- DRS cannot be used.
- A dispatcher is optional.
- The same maintenance mechanism applies to both the WebSphere Commerce and WebSphere Commerce search applications.