Deploying the WebSphere Commerce Developer search server remotely
The search server is deployed in the development environment in an embedded configuration by default. If you prefer to run the search server outside of the WebSphere Commerce application, for example, to reduce the memory footprint of the development environment, you can change it to a remote deployment.
The development environment remote deployment includes running search as a Java EE application server in WebSphere Application Server, on a remote machine from the developer's development environment machine. That is, the search server is deployed on the remote WebSphere Application Server machine.
Before you begin
- Enable WebSphere Commerce Developer Feature Pack 2, 3, 4, 5, or 6 using either a DB2 or Oracle database.
- Published a search-supported WebSphere Commerce starter store, such as the Madisons, Elite, or Aurora starter store.
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.