Embed Size (px)
Citation preview
System i
3/30/2007
WebSphere Commerce 6.0
Installation and Configuration on iSeries
STG Lab Services – System i Rochester, MN
Visit STG Lab Services at http://ibm.com/servers/eserver/services/
System i
3/30/2007 2 of 63
Introduction......................................................................................................................... 3
Purpose of this Document............................................................................................... 3 Conventions .................................................................................................................... 3
Installing Commerce........................................................................................................... 4 Software Prerequisites .................................................................................................... 4
IBM Internal Software Download .............................................................................. 4 Network Prerequisites..................................................................................................... 4 User Profile Prerequisites ............................................................................................... 5 Installation Process Overview......................................................................................... 5
Prepare the System...................................................................................................... 5 Install WebSphere Application Server........................................................................ 6 Install WebSphere Commerce .................................................................................... 9 Install Remote WebSphere Commerce Management Utilities ................................. 17 Verify Product Installation........................................................................................ 23 Install Fixes............................................................................................................... 27 Verify Fixes .............................................................................................................. 33
Configuring a Commerce Instance ................................................................................... 34 Configuration Process Overview .................................................................................. 34
Information Required for the WC Instance Configuration ....................................... 34 Configure the WC Instance....................................................................................... 35 Verify the WC Instance Configuration ..................................................................... 44
Publishing a Store Archive ............................................................................................... 46 Publish a Composite (Sample) Store ............................................................................ 46 Publish a Component (Client-specific) Store ............................................................... 49 Verify Store Published.................................................................................................. 52
Pre-Compile JSPs...................................................................................................... 54 Troubleshooting ................................................................................................................ 55
Problem list ................................................................................................................... 55 Install......................................................................................................................... 55 Configuration ............................................................................................................ 55 Web Tools/Administration........................................................................................ 55 Publishing ................................................................................................................. 56 Storefront .................................................................................................................. 56
Appendix A – WC Instance URLs.................................................................................... 57 Appendix B - Web Resources........................................................................................... 58 Appendix C – Contacts ..................................................................................................... 59 Appendix D – WebSphere Commerce Parameters........................................................... 60
System i
3/30/2007 3 of 63
Introduction This document provides specific details related to the installation and configuration of WebSphere Commerce 6.0 on iSeries. It is meant to supplement product documentation already available. Most, if not all product documentation can be found at the WebSphere Commerce 6.0 Information Center (WCIC).
Purpose of this Document Using this document, along with product documentation, a working WC 6.0 environment on iSeries should be expected. It is highly recommended to use the product installation documentation as a guide and this document as a supplement to that guide. Online documentation is available to get the user through the process from start to finish. Unfortunately, that documentation is not located in one convenient location and does not provide step by step guidance through the process. This document attempts to highlight the key steps in the process to install and configure WC 6.0 on iSeries. Again, this guide is not intended to be used standalone.
Conventions Several conventions and wording schemes are used throughout the document. An explanation is provided here.
• WAS – WebSphere Application Server 6.0 for iSeries • WC - WebSphere Commerce 6.0 for iSeries • WAS admin console – WebSphere Application Server Administrative Console • WC admin console – WebSphere Commerce Administration Console • WCIC – WebSphere Commerce Information Center • WCIG – WebSphere Commerce Installation Guide (for iSeries) for the edition of
WC being installed • <edition> - as it applies to WAS (Express, Base, Network Deployment) and WC
(Express, Professional, Enterprise> • <instance> - your WebSphere Commerce instance name, i.e., MYCOWC • <was_profile> your WebSphere profile name, i.e., MYCO • <wc_app> your WebSphere Commerce enterprise application name, i.e.,
WC_myco • <user> - your user profile name on the iSeries, i.e., i5user • <i5_fqhn> - the fully qualified host name of the iSeries, i.e., myiseries.myco.com • <i5_ip_addr> - the IP address of the iSeries, i.e., 9.168.1.10 • <wc_fqhn> - the fully qualified host name for accessing the WC web server; this
can be different (or the same) than <i5_fqhn>, mycostore.myco.com • <wc_ip_addr> - the IP address of the WC web server, i.e., 9.168.1.20
System i
3/30/2007 4 of 63
Installing Commerce There are a couple of different ways to install the WebSphere Commerce product on iSeries. This document will highlight using the remote installation GUI (from a client windows PC). When referencing the WCIG, be sure it is for the edition of WC being installed. The WCIG can be obtained from the WCIC home page via the Technical Library links.
Software Prerequisites The software stack required to run WC is rather extensive. The customer is responsible for acquiring ALL required software, whether by download or media. Numerous fixes (PTFs, fix packs) will also be required. Service personnel MAY wish to have software in hand, just in case it’s needed in an ‘emergency’ situation. Take some time to identify
• the version (6.0) and edition (Express, Professional, Enterprise) of WC required • the version (6.0) and edition (Express, Base, Network Deployment) of WAS
required • iSeries group PTFs and product fix packs required. Some of the PTFs are very
large and problems have occurred when attempting to download and install these via Fix Central. It’s recommended to have any group PTFs on CDs. The customer should order these ahead of time so they are available. The CUM and HIPER group PTFs can be loaded and applied by the customer before any software is installed. The primary group PTFs are
o WAS o CUM and HIPER
IBM Internal Software Download IBM software can be downloaded internally using the Xtreme Leverage Software Download site. Visit http://w3-103.ibm.com/software/xl/portal/!ut/p/_s.7_0_A/7_0_LT?nb=all and look for the Software Downloads link. Use your IBM intranet user id and password to access the download area. To narrow down the search, use websphere commerce v6 iseries as the search text criteria.
Network Prerequisites There are several areas related to the network that need to be addressed.
• The system must have a resolvable fully qualified host name. To verify, issue the following command (nslookup ‘<i5_fqhn>’) from a either a DOS prompt or i5/OS command prompt. A correct IP address should be returned. Repeat, if necessary, for <wc_fqhn>. Note: If command nslookup is not found on the iSeries, issue command WRKOBJ OBJ(*ALL/NSLOOKUP) OBJTYPE(*CMD) to find its location.
System i
3/30/2007 5 of 63
• The IP address must resolve to a fully qualified host name. To verify, issue the following command (nslookup ‘<i5_ip_addr>’). The fully qualified host name should be returned. Repeat, if necessary, for <wc_ip_addr>.
• Ensure all the nodes on the system can be reached from external systems in the network. Ping each node using the fully qualified host name and short name.
• Ensure there are no port conflicts.
User Profile Prerequisites There are specifics related to the user profile used to install and configure WC that must be met. You will need access to either the QSECOFR profile, or an iSeries user profile that meets certain conditions. See the section titled ‘Preparing your systems…’ of the WCIG for details.
• USRCLS(*SECOFR) and SPCAUT(*USRCLS) • If you are using iSeries Access to create the profile, make sure that the following
localized settings are used: o CCSID – 37 o LangID – ENU o CountryID – US
• Make sure the created profile has an IFS home subdirectory (i.e., /home/<user>) with a SystemDefault.properties file
o tagged as 819 and containing ASCII data o file.encoding=ISO8859_1 property on one line
Installation Process Overview The following provides a high level task list for installing WC on iSeries.
1. Prepare the system 2. Install WebSphere Application Server 3. Install WebSphere Commerce 4. Install WebSphere Commerce Remote Management Utilities 5. Verify product installation 6. Install WAS fixes (including the latest WebSphere group PTF) 7. Install WC fixes
Prepare the System Refer to the section titled ‘Preparing your systems…’ in the WCIG for details. Basically, follow these steps.
1. Create the appropriate user profile 2. Obtain/download required software 3. Make sure the iSeries has the correct levels of CUM and non-WAS products
installed. (Do not install WAS, Java, DB2, HTTP or IBM Business Solutions group PTFs. They will be installed with the WAS group PTF later.)
System i
3/30/2007 6 of 63
4. Any related product group PTFs (CUM, HIPER, etc.) can be installed now if desired. To save an IPL, they can be installed at the same time the WAS group PTF is installed (after installing the WAS product).
Install WebSphere Application Server Depending on the edition of WebSphere Commerce 6.0, a choice needs to be made on which edition of WebSphere Application Server 6.0 will be used. If the system does not currently have any edition of WebSphere Application Server 6.0 installed, it will need to be installed first. When using the Quick Install mode for installing WebSphere Commerce 6.0, the installation wizard will install the edition of WAS 6.0 provided with the WC 6.0 media automatically. It’s not recommended to use the Quick Install mode. If the system already has an edition of WAS 6.0 installed, determine what it is and decide if it is the edition required. As an example, if WAS 6.0 Base is already installed, but WAS 6.0 ND is required, the custom installation process only recognizes that some edition of WAS 6.0 is installed, but does not let you choose. If a different edition is required, install the WAS 6.0 edition first. We’ll make the assumption that WAS 6.0 Base is installed, but we want WAS 6.0 ND, and walk through the steps to install WAS 6.0 ND for use with WC 6.0 Enterprise. The installation program is smart enough to determine the WAS is installed (or not). It will choose an edition of WAS in this order: ND, Base, Express, as applicable to the edition of WC being used. The process should be identical for all editions.
1. Launch the installation wizard for WAS 6.0 ND by double-clicking install.exe in the WAS directory of the WAS 6.0 ND CD. The first panel might look like this.
System i
3/30/2007 7 of 63
Enter the fully qualified host name of the iSeries, along with user name and password, and press OK. Make sure the user profile being used has the proper authorities.
2. Proceed through subsequent panels until reaching the panel prompting for an installation directory.
System i
3/30/2007 8 of 63
Accept the default value and press Next.
3. Accept defaults on any subsequent panels until reaching the summary panel.
System i
3/30/2007 9 of 63
Press Next to begin the installation on the iSeries. Depending on system resources, expect the installation to take around 30 minutes.
4. When the installation completes, the following panel is displayed.
Press Finish to complete the installation of WebSphere Application Server.
Install WebSphere Commerce It is recommended to use the Custom Install option. The Quick Install option automatically creates a WC instance. This prevents the permission.pak from installing properly. It will appear to install OK, but you will not be able to access the store at the end. This will not be fixed until the next release of WC, since it involves changing the install process, which is a significant piece of work. DO NOT use the Quick Install option.
1. Start the installation wizard (autorun.exe on disk 1). After selecting the language, the first panel displayed might look like this.
System i
3/30/2007 10 of 63
2. Select ‘Install Product on iSeries Machine’. Enter system related information
when prompted. 3. The following panel shows the various commerce components that can be
installed.
System i
3/30/2007 11 of 63
4. If prerequisite checking passes, the following panel will appear.
System i
3/30/2007 12 of 63
5. Select the Custom Installation option and press Next. 6. Install the components shown here. The ‘Remote WebSphere Commerce
Management Utilities’ will be installed at a later time.
System i
3/30/2007 13 of 63
7. Press Next to install the selected components. 8. Proceed through subsequent panels until reaching the summary display.
System i
3/30/2007 14 of 63
9. NOTE: If neither WebSphere Application Server Base or Network Deployment
are installed, the wizard will install the edition of WAS provided with WC. When installing WAS, watch for
a) the timeout message (see the Troubleshooting section of the installation guide)
b) the “can perform the same action” message. Cancel each. 10. Following the WAS install, the First Steps screen appears. Exit out of here. 11. Depending on system resources, the WC product installation will take around 30
minutes. When the installation is about complete, the following panel displays.
System i
3/30/2007 15 of 63
Press Next to continue.
12. The installation is now complete.
System i
3/30/2007 16 of 63
Press Next.
13. The First Steps panel appears.
System i
3/30/2007 17 of 63
As desired, select topics for more information. Select ‘Exit’ when finished.
Install Remote WebSphere Commerce Management Utilities The configuration manager tool is part of the Remote WebSphere Commerce Management Utilities. It is required to create WC instances and is installed on a system remote to the server, typically a Windows client. To install the ‘Remote WebSphere Commerce Management Utilities’, take the same steps as if you were installing the WC server as outlined above. This time only select to install the ‘Remote WebSphere Commerce Management Utilities’ component.
1. Launch the installation program as you did earlier to install the commerce product.
System i
3/30/2007 18 of 63
From the Launch Pad, select ‘Install Product’.
2. Proceed through the wizard panels until reaching the installation type panel.
System i
3/30/2007 19 of 63
Select ‘Custom Installation and press Next.
3. At the component selection panel, only select ‘Remote WebSphere Commerce Management Utilities’.
System i
3/30/2007 20 of 63
Press Next to continue.
4. Continue until reaching the panel prompting for install path.
System i
3/30/2007 21 of 63
Either accept default path or specify own path (as was done above). Press Next.
5. Proceed to the summary panel.
System i
3/30/2007 22 of 63
Press Next to start the install on the local client machine.
6. Once the installation has completed, the following panel appears.
System i
3/30/2007 23 of 63
Press Finish to complete the installation.
At this point, all of the required products should be installed.
Verify Product Installation As a sanity check, it’s a good idea to check now to make sure the products installed as expected. This can be done by viewing logs (probably the best) or by looking at the directory structure containing product files. For WebSphere on iSeries, look in IFS at the following location: /qibm/proddata/websphere/appserver/v6/<edition>. Using ND as an example, the directory structure will look something like this.
System i
3/30/2007 24 of 63
To further verify the product, look at the contents of /qibm/proddata/websphere/appserver/v6/<edition>/properties/version/WAS.product. The contents might look something like this.
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE product PUBLIC "productId" "product.dtd"> <product name="IBM WebSphere Application Server - ND"> <id>ND</id> <version>6.0.0.1</version> <build-info date="11/10/04" level="o0445.08"/> </product>
System i
3/30/2007 25 of 63
For WebSphere Commerce on iSeries, look in IFS at the following location: /qibm/proddata/CommerceServer60. Using Enterprise as an example, the directory structure will look something like this.
To further verify the product, look at the contents of /qibm/proddata/CommerceServer60/properties/version/COMMERCE.product. The contents might look something like this.
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE product PUBLIC "productId" "dtd/product.dtd"> <product name="IBM WebSphere Commerce">
System i
3/30/2007 26 of 63
<id>wc.server.be</id> <version>6.0.0.0</version> <build-info date="25/04/06" level="060420cdev"/> </product>
For the Remote WebSphere Commerce Management Utilities, look for the installation directory on the client. Using the example from above, that directory would be D:\WebSphere\CommerceServer60. Using Enterprise as an example, the directory structure will look something like this.
System i
3/30/2007 27 of 63
To further verify the product, look at the contents of D:\WebSphere\CommerceServer60\properties\version\COMMERCE.product. The contents might look something like this.
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE product PUBLIC "productId" "dtd/product.dtd"> <product name="IBM WebSphere Commerce"> <id>wc.server.be</id> <version>6.0.0.0</version> <build-info date="25/04/06" level="060420cdev"/> </product>
It’s important to note that both the VERSION and EDITION of the WebSphere Commerce product on the client and server need to match exactly. If they do not, there will be issues using the configuration manager.
Install Fixes There will be required system software maintenance (CUM, HIPER, other group PTFs), WebSphere Application Server maintenance, and WebSphere Commerce (client and server) maintenance.
WAS Fixes 1. Install the most recent PTFs for WAS required by WC 6.0. See http://www-
1.ibm.com/support/docview.wss?rs=494&uid=swg21239904 Note 1: The WebSphere group PTF will automatically install the HTTP, DB2, and Java group PTFs, so do NOT install these separately. Installing group PTFs will require an IPL.
2. Install the WAS <edition> product fix pack. The fix pack is provided as part of the WAS group PTF or it can be download. It requires the Update Installer. See the cover letter for the group PTF or visit http://www-03.ibm.com/servers/eserver/iseries/software/websphere/wsappserver/services/fixpack60.html
3. Install the permission pack: 6.0.2.5-WS-WAS-IFWC-file-permission.pak Note 1: This fix is found in WC_disk1/extra/ folder; where WC_disk1 is the WebSphere Commerce disk one CD image. Copy to /qibm/proddata/websphere/appserver/v6/<edition>/updateinstaller/maintenance Note 2: The permission.pak must be installed prior to creating any WC instances. If it is applied in an environment with existing instances, only the product will be updated, as well as any instances created after the pack is installed. The fix pack must be manually applied to any existing instances. Note 3: Install this from the directory /QIBM/ProdData/WebSphere/AppServer/V6/<edition>/updateinstaller. Use the following QSH command:
update –W product.location=”/QIBM/ProdData/WebSphere/AppServer/V6/<edition
System i
3/30/2007 28 of 63
>” –W maintenance.package=/QIBM/ProdData/WebSphere/ AppServer/V6/<edition>/updateinstaller/maintenance/6.0.2.5-WS-WAS-IFWC-file-permission.pak
WC Fixes There will likely be a WC fix pack and possibly enhancement packs that need to be identified and installed. Before installing any WC fixes, the WC Update Installer must be downloaded and installed on the appropriate platforms. In this case the Update Installer will be needed on both iSeries (server) and Windows (client).
Update Installer The WebSphere Commerce Update Installer must be used to install fixes to WebSphere Commerce.
1. Download the iSeries WC Update Installer to the client. There should be a link provided from the fix pack web page. As an example, see http://www-1.ibm.com/support/docview.wss?uid=swg24013502. This particular version of the Update Installer works with fix pack 6.0.0.1.
2. Unzip the Update Installer to a temporary directory. 3. Install the Update Installer on the iSeries
a. From the directory in which Update Installer was unzipped, locate ...\UpdateInstaller\install.exe and launch it.
Enter required information and press OK. b. Proceed to the installation directory panel.
System i
3/30/2007 29 of 63
Either keep the default (recommended) or specify another directory in IFS and press Next. c. The summary panel displays.
System i
3/30/2007 30 of 63
Press Next to begin the installation of the Update Installer on the iSeries. d. After a few minutes, the installation should complete.
System i
3/30/2007 31 of 63
e. Press Finish to complete the installation.
Repeat a similar process for getting the Update Installer installed on the windows client that has the Remote WebSphere Commerce Management Utilities installed. Be sure and download the Update Installer for the desired platform.
Install WC Fixes It’s highly recommended that you first read the Commerce Fix Pack Installation Guide for i5/OS before proceeding. Installing the fix pack to the product directories should take less than 30 minutes. Installing the fix pack to an already existing instance could take upwards of a couple of hours.
1. Install the most recent WC <edition> maintenance (fix pack). As of this writing, it is 6.0.0.1. See http://www-306.ibm.com/software/genservers/commerce/support/
a) Download (http://www-1.ibm.com/support/docview.wss?rs=3046&context=SSYSYL&context=SSYT2H&dc=D42G3&uid=swg24013056&loc=en_US&cs=utf-8&lang=en) and copy the WC fix pack to the Update Installer
System i
3/30/2007 32 of 63
maintenance directory, i.e., /qibm/proddata/websphere/UpdateInstaller/V61/WC.UPDI/maintenance
b) Be sure and use the SILENT install feature of the Update Installer to install the fix pack on the iSeries server. The ‘silent mode’ command to apply the WC fix pack to the product directories might look like this. It should be run from Qshell, directory /qibm/proddata/websphere/updateinstaller/v61/WC.UPDI/
update -devkit14 -options /qibm/proddata/websphere/updateinstaller/v61/WC.UPDI/responsefiles/install.txt where install.txt contains the following entries -W maintenance.package="/QIBM/ProdData/WebSphere/UpdateInstaller/V61/WC.UPDI/maintenance/6.0.0-WS-WCServer-FP001.pak" -W product.location="/QIBM/ProdData/CommerceServer60" If the fix pack must be applied to an already existing instance, the following will need to be added to the install.txt file. Remember that the fix pack must be applied to the product directories AND any WC instances that have already been created. -W update.instancename="<instance>" -W update.db="true"
2. Install any required enhancement packs. The process should be similar to fix pack installation. Be sure that any prerequisites are met before proceeding.
Configuration Manager Fixes Follow the process for installing WC (server) fixes with minor adjustments. For any fix packs to be installed on the Windows client, make sure you have downloaded the appropriate Update Installer version (usually from the same site from which you are getting the fix pack). The iSeries should already have the appropriate Update Installer as a result of the previous steps in this process. Follow the instructions in the readme file for using the Update Installer to install the fix pack. At this point, all of the required product fixes should be installed. The next step will be to configure a WC instance.
System i
3/30/2007 33 of 63
Verify Fixes As with verifying product installation, it will be a good idea to verify fix pack installation as well. If no errors were encountered during fix pack installation, that should be a good indication that all went well. It would still be a good idea to check logs and look at the WAS.product and COMMERCE.product files to make sure they reflect the current maintenance level as expected.
System i
3/30/2007 34 of 63
Configuring a Commerce Instance There are a couple of different ways to configure a WebSphere Commerce instance on iSeries.
• Quick Install (selectable option when installing the product) • Configuration Manager (recommended)
This document covers using the configuration manager tool (Remote WebSphere Commerce Management Utilities). The Quick Install option should not be used to configure a commerce instance as it precludes the execution of other required tasks which will cause later problems if not performed.
Configuration Process Overview The following provides a high level task list for configuring a WC instance on iSeries.
1. Assumption: product installed with fixes (see above) 2. Gather required information 3. Configure the instance 4. Verify the WC instance configuration
Information Required for the WC Instance Configuration There is a laundry list of required information when creating a WC instance. Most of which is needed when using the configuration manager.
• OS Information: o Local Certificate Authority (CA) password o *SYSTEM certificate store password o Is a new TCP/IP interface and host name required?
• WC information: o WC instance name and password (A WAS instance user profile will also
be created with this name. Max length = 10 chars.) o WC site administrator ID and password (used to access Accelerator, WC
admin console and WC org admin console). This is not an operating system id. Password:
Must be => 8 in length Must contain at least one numeric Must contain at least one alpha Can not contain 4 consecutive occurrences of a character Must not contain the same character more than 4 times
o Merchant key (used as an encryption key). It is a 16 digit hex number that:
Must contain at least one numeric Must contain at least one alpha Must not contain uppercase letters Can not contain 4 consecutive occurrences of a character
System i
3/30/2007 35 of 63
Must not contain the same character more than 4 times o Configuration Manager user name and password
• Store information o Store identifier (name of the store) o Store directory (usually the same name as the store identifier) o Organization (the org to which you wish to publish the store) o Sample data (the data assets to be published to the store) o Inventory Model (ATP, Non-ATP or No inventory)
• Topology information o Database remote or local? o Web server remote or local? o Staging or production server configuration? o New or existing WebSphere Application Server?
Configure the WC Instance The configuration manager is used to create WC instances. Refer to the WCIC for details on how to launch the configuration manager. On the server, from Qshell, issue command
/qibm/proddata/commerceserver60/bin/config_server.sh
It may take several minutes before the server is ready to accept requests. Once the following messages are seen, the configuration manager on the client can be started.
Registry created. CMServer bound in registry
On the client where the Remote WebSphere Commerce Management Utilities were installed, issue the command to start the configuration manager from a DOS prompt. As an example,
D:\WebSphere\CommerceServer60\bin\configClient –hostname <i5_fqhn>
Note that in this case, <i5_fqhn> is case sensitive and should match what is defined in the iSeries TCP/IP configuration. Typically <i5_fqhn> will be capitalized. Once the client side has connected to the server, a message similar to the following should be seen in the Qshell.
Configuration Manager Server ---------------------------- Edition: wc.server.be Version: 6.0.0.1 Build date: 26/09/06
System i
3/30/2007 36 of 63
Level: 060918dsup
1. Log into the configuration manager.
Specify the user id and password that was provided when WC was installed.
2. Once successfully logged in to the configuration manager, the following display should appear.
Select Action Create instance… to launch the wizard for creating a new WC instance.
System i
3/30/2007 37 of 63
3. Begin specifying parameters to create the WC instance, starting with instance related information. Note the all values provided are for example purposes only.
Fill in all required fields, making notes of their values. Press Next.
4. The Schema panel is displayed. This panel pertains to the database schema to be used by the WC instance.
System i
3/30/2007 38 of 63
The relational database name can be determined by issue iSeries command WRKRDBDIRE. It will typically be the physical name of the iSeries system. The instance logon password will be the password associated with the WC instance user profile (i.e., STGLS). This will be the iSeries user that owns the WC instance schema. Press Next to continue.
5. The WebSphere panel is displayed.
System i
3/30/2007 39 of 63
The WAS profile name is typically the same as the WC instance name, though it can be different. Normally defaults are taken here. If a remote iSeries database is used, the WebSphere JDBC Driver Type should be changed to use the Toolbox driver. Be sure that the starting port does not conflict with any other ports in use on the system. Press Next to continue.
6. The Languages panel is displayed.
System i
3/30/2007 40 of 63
Make changes here as necessary. Press Next to continue.
7. The Web server panel is displayed.
System i
3/30/2007 41 of 63
It’s possible the host name will be the same is <i5_fqhn>, but not necessarily. Often times another TCP/IP interface is created on the iSeries that uses a different IP address and thus host name than what is defined on the iSeries. This is typical of commerce because of its requirement to use default ports (80, 443). In this example, you can see that is the case and <wc_fqhn> is actually specified. If it’s decided to use a remote web server, be sure and understand the ramification to do so. Press Next to continue.
8. The Staging panel is displayed.
System i
3/30/2007 42 of 63
It should have been determined ahead of time whether or not this particular WC instance should be used as a staging server and if workspaces are to be enabled. More information on these topics can be found in the WCIC. Note that some of the parameters are associated with the production server. View the help for more information. Fill in parameters as required and press Finish to start WC instance creation.
9. WC instance creation begins. Monitor the console messages as creation processing continues.
System i
3/30/2007 43 of 63
The time it will take to configure the instance is dependent on system resources. Expect it to take at least a couple of hours.
10. When the configuration manager has finished creating the WC instance, the following panel is displayed.
System i
3/30/2007 44 of 63
Press OK to dismiss the information panel. Expand the newly created instance to view its properties. Close the configuration manager window when finished. Press OK to dismiss the information panel indicating the configuration manager server will be ended when exiting the configuration manager client.
Verify the WC Instance Configuration 1. Using the iSeries Digital Certificate Manager (DCM) which is accessible via the
iSeries Tasks web page, assign a valid certificate to the application, i.e., QIBM_HTTP_SERVER_STGLS. If this step is omitted, the web server will fail to start.
2. Start the web (HTTP) server, STRTCPSVR SERVER(*HTTP) HTTPSVR(STGLS) 3. Start the WC server
a) STRQSH b) Change directory to
/qibm/userdata/websphere/appserver/v6/<edition>/profiles/<was_profile>/bin
c) startServer server1 –profileName <was_profile> 4. Access the following URLs. For each page, log in using the WC site
administrator id and password. If you can not complete these steps, continue
System i
3/30/2007 45 of 63
verification using iSeries Navigator and the appropriate log files, as directed in the WCIG.
a) https://<wc_fqhn>:8000/accelerator b) https://<wc_fqhn>:8002/adminconsole c) https://<wc_fqhn>:8004/orgadminconsole
At this point, provided the environment is in working order, it’s time to publish a store.
System i
3/30/2007 46 of 63
Publishing a Store Archive Publishing a store archive to a WebSphere Commerce Server allows you to create a running store. Before publishing a store, it must be decided which business model (B2C, B2B, Extended sites, etc.) and corresponding type of store (Direct sales, Hub, etc.) is required. Once that is decide, the specific store archive to publish must be chosen. Publishing a store is well documented in the WCIC. An example publish scenario is provided below. Depending on system resources, expect a store publish to take around 60 minutes.
Publish a Composite (Sample) Store According to WCIC, a composite store must be published prior to publishing a component store. This will ensure that the organization structure, predefined user roles, etc., are in place before publishing any component store archives. Depending on the edition of WC being used will determine which store archives are available for publish. Make sure it’s understood how the WC instance will be used and which business model is required as there are a number of factors that will decide which store archive(s) are published. If it’s still not clear on which store to publish, first publish the composite store (AdvancedB2BDirect.sar) followed by the component store (AdvancedB2BDirectStore.sar). This will give the greatest amount of flexibility for future decisions. This example uses WC Enterprise and the advanced B2B store.
1. Make sure the required servers are started (web server, WC server) 2. Start the WC admin console and open to the Site option 3. From the Store Archives, select the Publish option 4. Select the (composite) AdvancedB2BDirect.sar initially. Publishing this store
archive provides all of the necessary resources to build a store, using default store values.
System i
3/30/2007 47 of 63
Press Next.
5. Decide if any sample data should be published and the store inventory model to use. Note that with the AdvancedB2BDirect.sar (Enterprise), neither the store identifier nor store directory parameters can be changed.
System i
3/30/2007 48 of 63
Press Next.
6. On the summary panel, verify selections made.
System i
3/30/2007 49 of 63
Press Finish to begin publishing the store.
7. Verify the store published successfully.
Publish a Component (Client-specific) Store Depending on requirements, it’s possible that using the (composite) AdvancedB2BDirect.sar may be sufficient. Typically a customer will want to change the store directory and store identifier to more closely reflect their company name and/or specific store. If that is the case, publish the (composite) SAR, followed by the (component) SAR. This will also allow for the option of publishing multiple stores for the business model selected. To publish a client-specific store, follow a process similar to above.
1. First publish the required composite store archive (Advanced B2BDirect.sar). 2. Publish the (component) AdvancedB2BDirectStore.sar
System i
3/30/2007 50 of 63
Press Next.
3. Change the parameters as appropriate for the store. In this example, ‘None’ was selected for Sample data, assuming that the customer will have their own data to load into the catalog.
System i
3/30/2007 51 of 63
Press Next.
4. Validate parameters on the summary panel.
System i
3/30/2007 52 of 63
5. Press Finish to start store publishing. 6. Very the store published successfully.
Verify Store Published Before accessing the published store, make sure it has published successfully.
1. Using the WC admin console, monitor store publishing by selecting Store Archives Publish status
2. Once the Publish Status is ‘Successful’, the store can be launched.
System i
3/30/2007 53 of 63
Select the appropriate Store Archive and press Details to continue.
3. The Publish Details panel appears.
System i
3/30/2007 54 of 63
Note the recommendation to batch compile the store JSPs (see below). Press Launch Store to access the published store.
Pre-Compile JSPs Here is what the command might look like to pre-compile the JSPs for a store. The command is run from the iSeries Qshell.
cd /qibm/proddata/websphere/appserver/v6/<edition>/bin JspBatchCompiler -enterpriseapp.name "WC_stgls" -webmodule.name "Stores.war" -cell.name "WC_stgls_cell" -node.name "WC_stgls_node" -server.name "server1" -profileName stgls
System i
3/30/2007 55 of 63
Troubleshooting There is a troubleshooting section in the WCIC. If problems are encountered, start there and use as a general resource. There are also numerous other resources to search when problems arise.
• WebSphere Commerce Zone http://www-128.ibm.com/developerworks/websphere/zones/commerce/
• IBM Home Page http://www.ibm.com/us/ • Google http://www.google.com/
Problem list The table below identifies some of the problems encountered when working with WebSphere Commerce on iSeries. This by all means is not an exhaustive list, but based on past experiences.
Install No problems encountered to date.
Configuration Problem Configuration manager won’t start Error Message Cannot connect to the Configuration Manager server. Check to make sure
that it is running or that the specified host name and port are correct. Cause There are numerous causes. Check the following.
• Is the configuration manager server started? • Does the host name case match that of the TCP/IP configuration? • Does the port specified on the client match the port used on the
server? • Is a firewall blocking access? • Is a network configuration blocking access? • Are client and server at the same level?
Solution Will depend on the identified cause. Log File/Messages See the DOS prompt and iSeries Qshell consoles. Notes/References Typically this will be network related.
Web Tools/Administration Problem Tool web page (i.e., accelerator) can’t be found Error Message Typically will see a ‘page not found’ message in the browser window
System i
3/30/2007 56 of 63
Cause There are numerous causes. Check the following. • Did the WC instance configure correctly? • Is the WC server started? • Is the web server started? • Has a valid certificate been assigned to the web server application
using DCM? Solution Will depend on the identified cause. Log File/Messages Notes/References Issue iSeries command “wrklnk
’/qibm/userdata/websphere/appserver/v6/<edition>/profiles’” and display the contents of the directory to view all of the WAS servers that have been created.
Problem Not authorized to view page Error Message Typically will see a ‘You are not authorized to view this page’ message in
the browser window. Cause This is permission related and is most likely caused by not applying fix pack
6.0.2.5-WS-WAS-IFWC-file-permission.pak (the permission pack). Solution See http://www-1.ibm.com/support/docview.wss?uid=swg21240016,
http://www-1.ibm.com/support/docview.wss?uid=swg21237099 Log File/Messages Look in the latest web server basic_error_log file, found at,
/QIBM/UserData/CommerceServer60/instances/<instance>/httplogs Notes/References Another way to determine if there might be permission problems is to check
authorization on a store resource, such as SiteAdministration.war. It should look like this
drwxr-sr-x 7 QEJBSVR 0 12288 Jan 24 21:55 SiteAdministration.war
not this
drwxr-s--- 7 QEJBSVR 0 12288 Jan 24 16:52 SiteAdministration.war
Publishing No problems encountered to date.
Storefront No problems encountered to date.
System i
3/30/2007 57 of 63
Appendix A – WC Instance URLs WebSphere Commerce Administration Console Logon https://<wc_fqhn>:8002/adminconsole or https://<wc_fqhn>:8002/webapp/wcs/admin/servlet/ToolsLogon?XMLFile=adminconsole.AdminConsoleLogon WebSphere Commerce Accelerator Logon https://<wc_fqhn>:8000/accelerator or https://<wc_fqhn>:8000/webapp/wcs/tools/servlet/ToolsLogon?XMLFile=common.mcLogon WebSphere Commerce Organization Administration Console Logon https://<wc_fqhn>:8004/orgadminconsole or https://<wc_fqhn>:8004/webapp/wcs/orgadmin/servlet/ToolsLogon?XMLFile=buyerconsole.BuyAdminConsoleLogon&storeId=0 WC Store Home Page http:// <wc_fqhn>/webapp/wcs/stores/servlet/TopCategoriesDisplay?langId=-1&storeId=10051&catalogId=10051
System i
3/30/2007 58 of 63
Appendix B - Web Resources WebSphere Commerce 6.0 Information Center http://publib.boulder.ibm.com/infocenter/wchelp/v6r0m0/index.jsp WebSphere Commerce Zone http://www-128.ibm.com/developerworks/websphere/zones/commerce/ WebSphere Commerce Support http://www-306.ibm.com/software/genservers/commerce/support/ iSeries Information Center http://publib.boulder.ibm.com/iseries/ Digital Certificate Manager http://publib.boulder.ibm.com/infocenter/iseries/v5r4/index.jsp?topic=/rzahu/rzahurazhudigitalcertmngmnt.htm
System i
3/30/2007 59 of 63
Appendix C – Contacts IBM STG Lab Services
• Mark Shade, [email protected] – System i Services • Rich Macrafic, [email protected] – System i Services
System i
3/30/2007 60 of 63
Appendix D – WebSphere Commerce Parameters The following table is a reference for key parameters required from installation through publishing of a store.
Parameter Value Description Install - General System fully qualified host name (FQHN)
The fully qualified host name of the system on which the product is installed, i.e., myiseries.mycompany.com
System short host name This is found by removing the domain portion from the FQHN. Often referred to as the host name, i.e., myiseries
Physical system name The physical name of the system (DSPNETA).
Install user profile The iSeries user profile used for the install. It must have proper authorities.
DCM *SYSTEM certificate store password
DCM Local CA certificate store password
Install - WebSphere Application Server WebSphere Application Server version and edition
Version and edition of WAS, i.e., WAS 6.0 ND
WAS product installation directory
WAS <edition> install directory
Update Installer version UPDI installation path Fix pack level Install - WebSphere Commerce Server WebSphere Commerce version and edition
Version and edition of WC, i.e., WC 6.0 Enterprise
WC product installation directory
WC install directory
WC install type Choices are Quick or Custom (recommended is Custom)
Configuration manager user Needed to access the client
System i
3/30/2007 61 of 63
id and password configuration manager Update Installer version UPDI installation path Fix pack level Install - WebSphere Commerce Client Remote WebSphere Commerce Management Utilities client name
Most likely installed on a windows client.
Remote WebSphere Commerce Management Utilities installation path
Install path of the configuration manager
Update Installer version UPDI installation path Fix pack level Configuration - General Configuration manager user id and password
See above
Configuration - Instance Instance name Instance admin user id and password
Merchant key Configuration - Schema Relational database name Likely to be the physical
system name (WRKRDBDIRE)
Instance (user profile) password
Database owner password
DB local or remote If remote, provide location. Configuration - WebSphere Profile name Cell Node Starting port JDBC driver type Configuration - Languages Default Selected Configuration - Web server Local or remote Recommend local for
iSeries. Can use proxy server in DMX for ‘remote’
Host name This could be different than
System i
3/30/2007 62 of 63
system host name Type Port Most likely 80 Accelerator port Admin console port Org Admin port Secure preview port Non-secure preview port Authentication mode Configuration - Staging Staging checked Yes or No Workspaces checked Yes or No Read schema prefix Write schema prefix Number of workspaces Production application name
Probably the same name as on staging
Prod data source Prod DB name Prod DB user and pwd Store Archive Publish - 1 Business model SAR name Store Directory Store Identifier Organization Sample Data Inventory model Store URL The URL used to access the
storefront Store Archive Publish – 2 Business model SAR name Store Directory Store Identifier Organization Sample Data Inventory model Store URL The URL used to access the
storefront Miscellaneous
System i
3/30/2007 63 of 63
