Briefly describe the automated deployment and configuration of the WebSphere Commerce Search Web Server

WebSphere Commerce Search WEB Server Automated Deployment Configuration Overview Features Overview

Prior to Version 7 Feature Pack 5, users had to manually perform some configuration steps to complete the deployment and configuration of the WebSphere Commerce Search Web Server after they started the foundation feature. With an IBM HTTP server (IHS) Web server, for example, users need to manually complete the following deployment configuration work on the Search Web server: Create a httpd.conf file for the search Web server, and add a virtual master to listen for the search application Machine port and configure the Search Web server plug-in correctly.

To reduce the amount of effort the user spends on the manual deployment configuration, WebSphere Commerce, starting with Version 7 Feature Pack 5, provides a user with the ability to automate the deployment and configuration of the Search Web server, allowing users to Foundation the feature to complete the automatic deployment and configuration of the Search Web server by passing additional parameters. It should be noted that this automation feature is currently available only for the IHS server, which is not available if the user is using a non-IHS Web server such as Iis,sunone.

Overview of how to use

Consistent with the WebSphere Commerce V7 Information Center, this article still uses [Search_server_config] to represent the collection of search Web server Automation configuration parameters that this new feature provides. The collection consists of 13 optional parameters:

Listing 1. [Search_server_config] Parameter collection

Autoconfigsearchwebserver 
issharewcwebserverproduct 
searchwebserverhostname 
Searchwebserveros 
Searchwebserverinstalllocation 
searchplugininstalllocation 
searchremoteconfigpath 
Searchisconfigviaftp 
searchftpserverport 
searchftpuserid 
searchftpuserpwd 
Searchisconfigvianfs 
Searchmappedconfigpath

Using this automated deployment Configuration feature, you only need to add the correct [search_server_config] parameter when running the Enable command for the Foundation feature. The main purpose of this article is to help users to quickly and accurately build the corresponding [Search_server_config] parameters for different scenarios.

The meaning of the tool of Flowchart Assistant tool

Each user's Commerce environment has its own unique topology and configuration. For example, some user environments use a local Web server, and some user environments use a remote Web server, while in some user environments the Commerce server shares a Web server with the search server, while in some user environments Commerce server and search services are configured with separate WEB servers, and in some user environments, FTP is used to complete file transfers between servers, while other user environments choose to use NFS, and so on. Using the WebSphere Commerce Search WEB Server Automation deployment and configuration features in these different scenarios requires different [search_server_config] parameters to be passed. which [Search_server_config] parameters are required for a particular scenario? And how should these parameters be assigned? These problems are the difficulties that users use when using this feature.

To better help users understand and use this automation feature, this article presents an Easy-to-use flowchart helper-"[Search_server_config] parameter build flowchart," as shown in Figure 1. This flowchart helps users to quickly select [Search_server_config] Parameters and assign values correctly to help users automate deployment and configuration of the WebSphere Commerce search Web server.

The [search_server_config] parameter constructs flowchart diagram 1. [Search_server_config] Parameter build flowchart

The main symbolic meanings in Figure 1 are as follows:

The only green hexagon labeled Start is the start step, which is the entrance to the entire flowchart.

Each yellow diamond represents a "decision step" that notes the question that needs to be answered when the step is reached. Each decision step has a unique digital ID, and different decision answers will determine the direction of the different paths.

Each bottom is a curved blue box that represents a "parameter recording step" that indicates the name of the parameter to be recorded when the step is reached. Each parameter logging step has a unique digital ID.

The blue line marked with an arrow represents the process "guide line", which indicates the direction in which the flowchart travels.

The orange Oval represents the stop step. Once you have reached stop step, you should exit the flowchart.

How do you get the [search_server_config] parameters and parameter values that are needed in the corresponding scene with the flowchart tool shown in Figure 1? The method is shown in Figure 2.

Figure 2. [Search_server_config] Parameter construction flowchart work diagram

Starting with the start step, go along the guide line to reach a step. If the "decision step" is reached, follow the instructions in the decision step analysis and the parameter assignment method to get the next step along the way according to the actual scenario. If you arrive at the parameter logging step, record each of the parameters shown in the step and assign values to these parameters as described in "decision step problem Analysis and parameter assignment methods." And so on, continue along the corresponding guide line and perform the appropriate action correctly in each step until you reach stop step. The arguments that are recorded and assigned in each parameter recording step are grouped together to get the [Search_server_config] parameter that applies to the scenario.

Analysis of decision step problem and method of parameter assignment

This section will elaborate on each of the parameter logging steps and decision steps shown in Figure 1, explaining how to make the right decisions in these steps and how to correctly assign values to the corresponding parameters.

Decision Steps (1): Do you intend to automate the deployment and configuration of the Commerce Search Web server while starting the feature components?

If you plan to configure new features using the WebSphere Commerce Search WEB Server Automation deployment, answer "yes" or "no".

Answer yes to the parameter logging step (1) Sets the value of the parameter "Autoconfigsearchwebserver" to "true". The next step is to reach the decision steps (2).

Answer No to the parameter logging Step (6) to set the value of parameter "Autoconfigsearchwebserver" to "false", or not to use this parameter, because the default value for the parameter is "false".

Next step to the stop step, exit the flowchart.