IBM(R) WebSphere(R) Commerce Web Server Configurator, Version 1.0.0
Last Updated: July 19, 2002
During instance creation, WebSphere Commerce V5.4 configures the following:
A number of manual steps are documented in the WebSphere Commerce Installation Guide. These steps are performed by the user to configure:
Most of these manual steps are done by this GUI-based Web server Configurator.
NOTE: This tool does not perform the basic Web server configuration. The Web server and its ports must be functioning prior to using this tool.
Try to view http://webserver_hostname to check that your Web server is functioning.
,where "webserver_hostname" is the fully qualified host name of the machine on which your Web server runs.
Windows Executable Installation
- Download win-dbconfig-setup.exe file, save it to the destination directory.
- Navigate to the destination directory, and run win-dbconfig-setup.exe to launch the installation.
AIX Native Executable Installation
- Download aix-wsconfig-setup.jar file, save it to the destination directory.
- Change file permission to make it executable: chmod +x aix-wsconfig-setup.jar
- Run the jar file as an executable: ./aix-wsconfig-setup.jar to launch the installation.
Solaris Native Executable Installation
- Download aix-wsconfig-setup.jar file, save it to the destination directory.
- Change file permission to make it executable: chmod +x sun-wsconfig-setup.jar
- Run the .jar file as an executable: ./sun-wsconfig-setup.jar to launch the installation.
Please download and install Microsoft MetaEdit 2.2 Utility from http://www.microsoft.com/
Skip the steps in Pre-configuration steps: Configuring Microsoft IIS and perform the following steps.
If you are working with 1 or 2 tier configuration:
If you are working with 3-tier configuration:
- From a command prompt, navigate to the Web_Server_ Configurator_install_ directory\bin directory.
- Run the IISpreconfig.js script.
cscript IISpreconfig.js "WAS_install_dir"
(i.e. cscript IISpreconfig.js "C:\Program Files\WebSphere\AppServer")
where WAS_install_dir is the WebSphere Application Server install directory. The path must be the full path. (i.e. 'C:\Program Files' instead of 'C:\Progra~1')
- From a command prompt, navigate to the Web_Server_ Configurator_install_ directory\bin directory.
- Run the IISpreconfig.js script.
cscript IISpreconfig.js "plugin_dir"
(i.e. cscript IISpreconfig.js "C:\Program Files\WebSphere\AppServer")
where plugin_dir is the directory where you installed the WebSphere Application Server Web server plug-in. (Please see "Installing WebSphere Commerce: A 3-tier installation: A 3-tier installation - Web server"). The path must be the full path. (i.e. 'C:\Program Files' instead of 'C:\Progra~1')
NOTES:IMPORTANT:
- This tool adds the Web aliases required for WebSphere Commerce. (i.e. You have to make sure your Web server is functional on the secure port and the tools port if applicable.)
- Run this tool immediately after you have created your WebSphere Commerce instance.
- You must restart your Web server after running this tool.
If you are working with 3-tier configuration, you must perform Copying assets to your Web server in Post-configuration Steps: 3-tier post-configuration steps.
If you use this tool after the instance creation, you can skip the following steps in the installation guide.
- From Step 5 to Step 13 in Chapter 3:Installing your Web Server:Installing and Configuring Domino Web Server
- All steps in Chapter 6:Pre-configuration steps:Configuring Microsoft IIS
- All steps in Chapter 8:Post-configuration Steps:3-tier post-configuration steps:Configuring your IBM HTTP Server in a 3-tier environment
- Step 2 in Chapter 8:Post-configuration Steps:One and two tier post-configuration steps:Completing your Microsoft IIS configuration
- Step 2 in Chapter 8:Post-configuration Steps:3-tier post-configuration steps:Completing your Microsoft IIS configuration
- All steps in Chapter 8:Post-configuration Steps:Completing your iPlanet Web Server installation:Remote iPlanet Web Server configuration
If you use this tool after the instance creation, you can skip the following steps in the installation guide.
- All steps in Chapter 11:Post-configuration Steps:Post-configuration steps for a local Web server:Completing your Domino Web Server configuration
- Step 2 in Chapter 11:Post-configuration Steps:Post-configuration steps for a remote Web server:Enabling SSL for testing
- All steps in Chapter 11:Post-configuration Steps:Post-configuration steps for a remote Web server:Completing the IBM HTTP Server installation
- All steps in Chapter 11:Post-configuration Steps:Post-configuration steps for a remote Web server:Completing your Domino Web Server configuration
If you use this tool after the instance creation, you can skip the following steps in the installation guide.
- All steps in Chapter 12:Post-configuration Steps:Post-configuration steps for a local Web server:Completing your Domino Web Server configuration
- Step 2 in Chapter 12:Post-configuration Steps:Post-configuration steps for a remote Web server:Enabling SSL for testing
- All steps in Chapter 12:Post-configuration Steps:Post-configuration steps for a remote Web server:Completing the IBM HTTP Server installation
- All steps in Chapter 12:Post-configuration Steps:Post-configuration steps for a remote Web server:Completing your Domino Web Server configuration
Launching the tool
Run WebConfig.bat in WebServer_Configurator_install_dir\bin directory.
Enter ./WebConfig.sh in WebServer_Configurator_install_dir/bin directory.
Enter ./WebConfig.sh in WebServer_Configurator_install_dir/bin directory.
Instance Name
This is the your WebSphere Commerce instance name.
Host Name
This is the fully qualified host name of your Web server machine.
Web Server Type
From the drop-down list, select the Web server that you intend to configure and use.
Web Site Number
(IIS only.) Open the MetaEdit 2.2 Utility. Expand LM and then W3SVC. Each Web site is indicated by a number shown as a folder name under W3SVC.
Enter the Web site number that you want to configure in this input field. You can determine which Web site it is by looking at the ServerComment attribute.
Primary Document Root
(HTTP Server only.) This is the primary document directory of your HTTP Server. (i.e. C:\WebSphere\HTTPServer\htdocs)
Authentication Mode
Select the authentication mode that you would like to use for this WebSphere Commerce instance. The choices are as follows:
Basic: Authentication will be performed using a custom certificate.
X.509: Authentication will be performed using the X.509 certificate standard.
Secure Server Configuration Path
(iPlanet only.) Enter the directory path to the obj.conf file for your secure Web server (port 443).
Non-secure Server Configuration Path
(iPlanet only.) Enter the directory path to the obj.conf file for your non-secure Web server (port 80).
Secure Tools Server Configuration Path
(iPlanet only.) Enter the directory path to the obj.conf file for your secure tools Web server (port 8000).
Domino Server Name
This is the Domino Web server name for this WebSphere Commerce instance. The format of this name should be like CN=name/O=domain. (i.e. CN=bob/O=ibm)
Domino Administrator Password
This is the Domino Administrator Client password, the password to log into Lotus Domino Administrator, for your Domino Web server
WebSphere Commerce Directory
For 1 or 2 tier configuration, this is the WebSphere Commerce install directory on the WebSphere Commerce machine.
For 3-tier configuration, this is the directory, on the Web server machine, that you copied the WebSphere Commerce asset files into. (i.e. C:\WebSphere\CommerceServer)
WebSphere Application Server Directory
For 1 or 2 tier configuration, this is the WebSphere Application Server install directory on the WebSphere Application Server machine.
For 3-tier configuration, this is the directory, on the Web server machine, that you copied the WebSphere Application Server asset files into. (i.e. C:\WebSphere\AppServer)
Web Server Directory
This is your Web server installation directory. (i.e. C:\lotus\Domino)
Tools Port Number
(HTTP Server only) The port number used for accessing WebSphere Commerce administration tools. The default port number is 8000.
Refer to WebSphere Application Server to find out which port it is using for accessing administration tools.
Uninstall from Program Folder:
- Select Start --> Program Files --> {IBM WebSphere Commerce Server Folder} --> System Tools --> Web Server Configurator.
- Select Uninstall Web Server Configuator.
- Follow the uninstallation process to remove the program.
Uninstalling from Command line:
- From a command prompt, navigate to the directory where the Web Server Configurator is installed. For example, C:/Program Files/WebServer Configurator/_uninst/
- Enter the following command:
java -jar uninstall.jar- Remove the installation file structure, since there a few files left on the file system after the uninstall process. For example,
cd C:\Program files\
rm -r WebServerConfigurator
Uninstallation
- From a command prompt, navigate to the installation directory:
cd /usr/WebServerConfigurator- Enter the following command:
cd _uninst
./uninstall-ws.sh
- Follow the steps to uninstall the program
Uninstallation
- From a command prompt, navigate to the installation directory:
cd /opt/WebServerConfigurator- Enter the following command:
cd _uninst
./uninstall-ws.sh
- Follow the steps to uninstall the program
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user’s responsibility to evaluate and verify the operation of any non-IBM product, program, or service.
Any reference to an IBM licensed program in this publication is not intended to state or imply that only IBM’s licensed program may be used. Any functionally equivalent product, program, or service that does not infringe any of IBM’s intellectual property rights may be used instead of the IBM product, program, or service. Evaluation and verification of operation in conjunction with other products, except those expressly designated by IBM, is the user’s responsibility.
IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504–1785
U.S.A.
For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:
IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, Japan
The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION
″AS IS″.WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:
IBM Canada Ltd.
Office of the Lab Director
8200 Warden Avenue
Markham, Ontario
L6G 1C7
Canada
Such information may be available, subject to appropriate terms and conditions, including in some cases payment of a fee.
The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer
Agreement, IBM International Program License Agreement or any equivalent agreement between us.
Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurement may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.
Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.
All statements regarding IBM’s future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.
This information is for planning purposes only. The information herein is subject to change before the products described become available.
This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.
Credit card images, trademarks and trade names provided in this product should be used only by merchants authorized by the credit card mark’s owner to accept payment via that credit card.
The following are trademarks of IBM Corporation in the United States and other countries:
WebSphere Commerce WebSphere Application Server IBM HTTP Server
Domino is a trademark of Lotus Development Corporation.
JDK, Java and iPlanet is a trademark of Sun Microsystems, Inc..
Internet Information Server, IIS, Microsoft, Windows, and Windows NT are trademarks of Microsoft Corporation in the United States, other countries, or both.
Netscape is a registered trademark of Netscape Communications Corporation in the United States and other countries.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Other company, product, or service names may be trademarks or service marks of others.
************************************************************************** ** © COPYRIGHT INTERNATIONAL BUSINESS MACHINES CORPORATION 2001 ** ALL RIGHTS RESERVED. **************************************************************************
Note to US Government Users -- Documentation related to restricted rights -- Use, duplication, or disclosure is subject to restriction set forth in GSA ADP Schedule Contract with IBM Corp.
End of Web Server Configurator README File