Install > Installing WebSphere Commerce > Installing WebSphere Commerce using the custom installation > Create a WCS instance > Mandatory post-instance creation tasks
Microsoft IIS tasks
WebSphere Commerce supports Microsoft IIS v6.0 and Microsoft IIS v7.0
To download the appropriate security patch, refer to the Microsoft Web site.
Your Web server provides a secure environment for the business transactions by using encryption technology. Encryption is the scrambling of information transactions on the Internet so that they cannot be read until they are unscrambled by the receiver. The sender uses an algorithmic pattern or key to scramble (encrypt) a transaction, and the receiver uses a decryption key. These keys are used by the SSL protocol.
Your Web server uses an authentication process to verify the identity of the person with whom you are conducting business (that is, to make sure they are whom they say they are). This involves obtaining a certificate signed by a trusted third party called a certification authority (CA), such as Equifax or VeriSign Inc. Other CAs are available as well.
To create a production key file...
- Request a secure certificate from a certifying authority.
- Set the production key file as the current key file.
- Receive the certificate and test the production key file.
- If you are already using a production key file signed by a certifying authority, you may be able to skip these steps.
- As you perform these steps, the browser may display security messages. Review the information in each message carefully and decide how to proceed.
Procedure
- Log in to the WebSphere Application Server Administration Console.
- Select Servers then Web servers.
- Select webserver1.
- Review the settings recorded in the Administration Console, and correct them based on the configuration. Apply the changes.
- Select Servers then Web servers.
- Select webserver1 then Additional Properties.
- Review the settings recorded in the Administration Console, and correct them based on the configuration. Apply the changes.
- Update the Microsoft IIS installation with the latest security patches available from Microsoft.
- Enable SSL. For instructions on enabling SSL, refer to the Microsoft IIS product documentation.
- Add the following SSL ports to the Web server:
- SSL communication port 8000
- SSL communication port 8002
- SSL communication port 8004
- SSL communication port 8006
The port numbers must be the same as those entered during the WCS instance creation.
- Add the following non-SSL port to the Web server:
- Non-SSL communication port 8007
The port number must be the same as those entered during the WCS instance creation.
- Test the installation and configuration of the Microsoft IIS Web server by opening a Web browser and accessing the following Web pages:
- http://IISWebServer_hostname
- http://IISWebServer_hostname:8007
- https://IISWebServer_hostname
- https://IISWebServer_hostname:8000
- https://IISWebServer_hostname:8002
- https://IISWebServer_hostname:8004
- https://IISWebServer_hostname:8006
where IISWebServer_hostname is the fully qualified hostname of the Microsoft IIS machine.
- Review the Configure Microsoft Internet Information Services (IIS) topic in the WebSphere Application Server Information Center to ensure that the Web server settings are correct.
- Navigate to the following location: WC_INSTALL/config/deployment/webserverconfig/IIS
- Open the addCommerceAliases.js file in a text editor. Review the file and update the ServerNumber and Commerce Web alias paths.
- If the Web server is located on a separate machine, copy the addCommerceAliases.js script to that machine.
- On the Microsoft IIS machine, open a Windows command window, and run the following command: cscript.exe WC_INSTALL/config/deployment/webserverconfig/IIS/addCommerceAliases.js
If you receive an Input Error: There is no script engine for file extension ".js". error, refer to the Error "Input Error: There is no script engine for file extension ".JS" when trying to debug a Resource Model Technote #1172559. Once you complete the steps outlined in the technote, attempt to run the command again.
- If the Web server is on a separate machine, refer to Remote Web server post-instance creation tasks.
- Enable detailed errors:
- Start the IIS Manager
- Select Default Web Site > Error Pages > Edit feature setting
- Click Detailed errors and click OK.
- Restart the Microsoft IIS Admin Service from the Windows Services panel.
- Start the Web site.