Configuring a remote web server

If the web server is installed on a different node from WebSphere Commerce, create a WebSphere Commerce instance, and then complete the configuration of the web server node.

Procedure

Ensure that you installed the WebSphere Application Server web server plug-in as described in the topic Installing the WebSphere Application Server web server plug-in.
Ensure that you enabled SSL on the web server node.
Change the user profile on your remote machine, so that the library of the remote instance is set to the current library. To complete these changes, run the following command:
```
CHGUSRPRF USRPRF(instance_name) CURLIB(instance_name)
```
Where:

instance_name

The name of the WebSphere Commerce instance.
Propagate the plug-in configuration file by following the steps in Copying the plugin-cfg.xml file to Web server.
If the plug-in configuration file does not exist, create directories on the web server node so that you have the following path available on the web server node:
- WC_profiledir/installedApps/cell_name
Ensure that the path for WC_profiledir is the same on the web server node and the WebSphere Commerce node.
Copy the following directory from the WebSphere Commerce node to the web server node:
- WC_profiledir/installedApps/cell_name/instance_name.ear
Ensure that the full paths on the web server node and the WebSphere Commerce node are the same.
Note:
Remove any JSP and JAR files from the WC_instance_name.ear directory on the web server. Ensure that only static-content files exist in this directory on the web server.
- Ensure that the web server read and execute permissions on all files and directories in the WC_profiledir/installedApps/ directory on the web server machine are correct.
  If the permissions on the files and directories are incorrect, you might not be able to access WebSphere Commerce.
- Remove any JSP and JAR files from the WC_instance_name.ear directory on the web server. Ensure that only static-content files exist in the WC_instance_name.ear directory on the web server.
Update the web server machine with a new Stores.war file every time that you perform an action that updates the static web content inside the application.
For example, update the web server machine when you publish a store. The Stores.war is in the following directory: WC_profiledir/installedApps/cell_name/WC_instance_name.ear/Stores.war. Ensure that the path to this file is the same on the web server node and the WebSphere Commerce node.
Note:
Remove any JSP and JAR files from the WC_instance_name.ear directory on the web server. Ensure that only static-content files exist in this directory on the web server.
- Ensure that the web server read and execute permissions on all files and directories in the WC_profiledir/installedApps/ directory on the web server machine are correct.
  If the permissions on the files and directories are incorrect, you might not be able to access WebSphere Commerce.
- Remove any JSP and JAR files from the WC_instance_name.ear directory on the web server. Ensure that only static-content files exist in the WC_instance_name.ear directory on the web server.
Add aliases if you are using Microsoft Internet Information Services (IIS) version 7.5 or 8.0.
1. On the WebSphere Commerce node, copy the WC_installdir/config/deployment/webserverconfig/IIS/addCommerceAliases.js file to any directory on the remote IIS node. This directory is denoted by IISdir.
2. On the remote IIS node, check the contents of file IISdir/addCommerceAliases.js. Ensure that all aliases and paths are correct.
3. On the remote IIS node, start a command prompt session and issue the following command:
```
cscript.exe IISdir/addCommerceAliases.js
```
  This command adds all the necessary aliases to the Microsoft Internet Information Services (IIS) version 7.5 or 8.0 web server configuration for WebSphere Commerce.
Note: If you receive the message Input Error: There is no script engine for file extension ".JS", then check the current association of the .JS extension on that Windows system by running the following command, ASSOC .JS
On a working system, ensure that the output resembles the following sample.
```
.js=JSFile
```
If it shows something else, note the output for safekeeping and then change by entering the following command:
```
ASSOC  .JS=JSFile
```
Then rerun the cscript file.
Open the WC_profiledir/properties/soap.client.props file in a text editor and change the property com.ibm.SOAP.requestTimeout from the default value of 180 to 6000.
If you need to create multiple instances of IBM HTTP Server, see Creating multiple instances of IBM HTTP Server on Windows operating systems.
Start your WebSphere Commerce server.
If your web server is configured to use only IPv6, change the custom properties for the WebSphere Commerce server JVM:
1. In the WebSphere Application Server Administrative Console for the WebSphere Commerce server, expand Servers > Server Types. Click WebSphere application servers. In the list of application servers, select your server.
2. On the Configuration tab, expand Java and Process Management and click Process definition > Java Virtual Machine > custom properties.
3. Click New. On the Configuration tab, enter the following name and value.
  
  Name Value
  java.net.preferIPv6Addresses true
4. Click Apply > Save directly to the master configuration.
Stop and restart the web server.

Note: For Microsoft Internet Information Services (IIS) version 7.5 or 8.0, you must stop and restart all Microsoft Internet Information Services (IIS) version 7.5 or 8.0 related services and applications. See Microsoft Internet Information Services (IIS) version 7.5 or 8.0 documentation for instructions on how to stop and start these services and servers.