Configuration Manager - Commerce - Web server
- Create a WebSphere Commerce instance.
- Update information in the Web server panel in Configuration Manager for an existing instance.
The sections that are changed in the configuration file are marked with the words IBM WebSphere Commerce (Do not edit this section). WebSphere Commerce does not support any customizations that are made to the restricted sections since the customizations might be overwritten at any time by WebSphere Commerce configuration tools such as Configuration Manager.
If you select Microsoft IIS, you must configure the Web servers manually. Complete the procedure in the following IBM Knowledge Center topic, Configuring Microsoft IIS.
Complete the fields as follows:
- Use Remote Web server
- Select this check box if you are installing your Web server on a separate machine from your
WebSphere Commerce machine.Note: If you installed your Web server on a different node from WebSphere Commerce (for example, if you are configuring a three-node environment), then you must select this check box.
- Hostname
- Enter the fully qualified host name of your Web server machine or Web server instance that
WebSphere Commerce will use. (
hostname.domainis fully qualified). Ensure that you do not enterwwwin the Hostname field.If you are using a remote Web server, this value is different from the hostname of the WebSphere Commerce machine.
- Web server Type
- Select the Web server to be used. The default is IBM HTTP Server.
- Server Port
- Enter the port number on which your Web server is running. The default value is 80.
- WebSphere Commerce Accelerator Port
- Enter the port number for accessing the WebSphere Commerce Accelerator.
The default is port 8000.
If you want to change this port after a WebSphere Commerce instance is created, refer to the IBM Knowledge Center.
- WebSphere Commerce Admin Port
- Enter the port number that is used for accessing the WebSphere Commerce Administration
Console.
The default port number is 8002.
If you want to change this port after a WebSphere Commerce instance is created, refer to the WebSphere Commerce Knowledge Center.
- WebSphere Commerce OrgAdmin Port
- Enter the port number that is used for accessing the WebSphere Commerce Organization
Administration Console.
The default port number is 8004.
If you want to change this port after a WebSphere Commerce instance is created, refer to the IBM Knowledge Center.
- Secure WebSphere Commerce Preview Port
- Enter the secure port number for accessing the WebSphere Commerce Preview. The default is port 8006.
- Non-secure WebSphere Commerce Preview Port
- Enter the non-secure port number for accessing the WebSphere Commerce Preview. The default is port 8007.
- SSL Port
- Enter the secure port number that your Web server is using. The default value is 443.
The following fields display if you select the Use Remote Web server check box and when you are using selected IBM HTTP Server as your Web server:
- Remote Server Install Path
- Enter the full path of the installation directory for the Web server on the remote Web server node. This path is the actual path on the Web server machine, not a network, or FTP path. This field is displayed only if IBM HTTP Server is selected as the Web server Type.
- Remote Plugin Install Directory
- Enter the Web server plug-in installation directory on the remote Web server machine. This directory is the actual path on the Web server machine, not a network, or FTP path.
- Remote Configuration Directory
- This field is only displayed if you are using an IBM HTTP Server as your Web server.
This directory on the remote Web server machine is dedicated to store the instance's Web server configuration files. This directory is the actual path on the Web server machine, not a network, or FTP path. This directory needs to be created manually on the remote Web server machine before you create your instance.
Remote Configuration- This check box is displayed if you select Use Remote Web server.
Select the Remote Configuration check box if the remote Web server is running on a UNIX or Linux system. This setting, along with the remote user name and remote configuration information, is used for sending files from the WebSphere Commerce node to the Web server node by using FTP.
Selecting Remote Configuration clears Mapped Network Drive Configuration.
Selecting the Remote Configuration check box might display the following fields, depending on the Web server type chosen:
- Remote Server Name
- Enter the fully qualified host name of the remote system.
- Remote Server Port
- Enter the FTP port number for the remote system. The default FTP port is 21.
- Remote User Name
- Enter a user ID with FTP access to the remote system. Ensure that the user has sufficient authority to create files on the remote system.
- Remote User Password
- Enter the password that is associated with the remote user name.
- Mapped Network Drive Configuration
- This check box is displayed if you select Use Remote Web server.
This setting along with the remote user name and password is used to send files from the WebSphere Commerce node to the Web server node by using a mapped network drive.
Selecting Mapped Network Drive Configuration clears Remote Configuration.
Selecting this check box might display the following fields, depending on the Web server type chosen:
- Mapped Configuration Directory
-
Enter the network path, including the mapped drive letter, of the remote plugin installation directory that is on the remote Web server machine. For example:
- Q:\WebSphere\HTTPServer\conf\remote\
- Generate properties file only
- This check box displays in the Instance Creation wizard only.
Select this check box if you do not want to create an instance but you want to populate a properties file. The properties file can be used with the CreateInstance Ant target to create a WebSphere Commerce instance.
The properties file is found in the following directory:
- WC_installdir/instances/instance_name/properties/createInstance.properties