websphere commerce server admin configuration

8,834 views

Published on

Published in: Technology
5 Comments
8 Likes
Statistics
Notes
No Downloads
Views
Total views
8,834
On SlideShare
0
From Embeds
0
Number of Embeds
12
Actions
Shares
0
Downloads
391
Comments
5
Likes
8
Embeds 0
No embeds

No notes for slide

websphere commerce server admin configuration

  1. 1. Course materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 20105.4.1Installing and configuringWebSphere Commerce
  2. 2. © Copyright IBM Corporation 2010Unit objectivesAfter completing this unit, you should be able to:• Install WebSphere Commerce• Configure WebSphere Commerce• Verify an installation of WebSphere Commerce• Explain the migration framework• Use the migration framework to migrate from a previous version• Install optional WebSphere Commerce components• Install fix packs and feature packs for WebSphere Commerce• Set up an instance of WebSphere Commerce• Use the configuration manager tool and instance creation wizard
  3. 3. © Copyright IBM Corporation 2010Hardware requirements: Linux on Intel or xSeries• Minimum requirements:– Dedicated Pentium III 733 MHz IBM-compatible personal computer– Minimum of 2 GB of memory per processor– Minimum of 4.5 GB of free disk space– Minimum of 1 GB of paging space per processor– Minimum of 6 GB of free disk space, if you install all of the required and optionalcomponents, with following recommended allocated file sizes:• /opt: 4.5 GB• /home: 1 GB• /tmp: 900 MB– DVD-ROM drive– Graphics-capable monitor with 256-color depth minimum– Mouse or other pointing device– Local area network (LAN) adapter that supports TCP/IP• Production requirements are greater.
  4. 4. © Copyright IBM Corporation 2010Software requirements: Linux• Red Hat Enterprise Linux AS/ES 4 Update 6• Red Hat Enterprise Linux 5 Update 1• SUSE Linux Enterprise Server 9 SP4• SUSE Linux Enterprise Server 10 Update 1• SUSE Linux Enterprise Server 11
  5. 5. © Copyright IBM Corporation 2010Commerce V7 package: Physical media• Commerce V7 DVDs:– Disk 1– Disk 2• WebSphere Application Server V7 Network Deployment:– Disk 1 contains IBM HTTP Server and WebSphere Application Server webserver plug-ins.– Disk 2 contains WebSphere Application Server custom installation package.• DB2 ESE:– Server– Administration client• WebSphere Commerce Express includes WebSphere ApplicationServer Express and DB2 Express.
  6. 6. © Copyright IBM Corporation 2010Commerce V7 package: Electronic media• WebSphere Commerce download image contains disk1 and disk2.• WebSphere Application Server V7 Network Deployment downloadimage contains disk1 and disk2.• DB2 ESE download image contains the Server and Administrationclient.• The WebSphere Commerce Express version can be downloaded.
  7. 7. © Copyright IBM Corporation 2010Preinstallation checklist: Linux (1 of 2)• Ensure your host name conforms to TCP/IP standards and can beresolved to an IP address.• If a component of WebSphere Commerce is already installed, stop allservices related to that component.• If you are running Lotus Notes or any other server on your machine,stop the server.• If you have a web server on your machine using ports 80, 443, 5432,5433, 8000, 8001, 8002, 8004, 8006, or 8007, disable it or change itsports.
  8. 8. © Copyright IBM Corporation 2010Preinstallation checklist: Linux (2 of 2)• Ensure that you have root authority.• Ensure that no other install programs are active.• Ensure that your firewall configuration is set to permissive.• Ensure that your operating system does not log your command line.• Review the WebSphere Commerce README file.• Create the user IDs and groups required by WebSphere Commerce onany machine on which you plan to install WebSphere Commerce.
  9. 9. © Copyright IBM Corporation 2010Commerce 7 installer• Installer is updated to support the software that is included inWebSphere Commerce V7.• Installer provides a soft stop warning if the detected preinstalledsoftware is not at the supported level.• Quick installation and custom installation are available.• WebSphere Commerce Payment instance is not available in the quickinstallation.
  10. 10. © Copyright IBM Corporation 2010Installation process: Linux (1 of 2)1. As root, insert and mount the WebSphere Commerce V7 disk 1.2. Ensure that X server is configured and working.3. Navigate to the location of the of the local WebSphere CommerceDVD image.4. Enter: mount_point/setup.sh5. Launch pad will start.6. Select the language for launch pad.7. Click Install Product.
  11. 11. © Copyright IBM Corporation 2010Installation process: Linux (2 of 2)8. Installation wizard steps through the installation:a. Verify prerequisites.b. Select installation type and components to install.c. Select database and web server products.d. View installation steps and begin installation.e. Install DB2, HTTP Server, WebSphere Application Server.f. Install WebSphere Commerce.g. Perform post-installation setup tasks.9. After installation of all components, if custom installation was used,you are asked to restart the system.
  12. 12. © Copyright IBM Corporation 2010Installation types
  13. 13. © Copyright IBM Corporation 2010Quick installation defaultsWebSphere Commerce instance demoWebSphere Commerce database mallWebSphere Application Server enterprise WC_demoWebSphere Application Server instance server1WebSphere Application Server profile demoIBM HTTP Server instance webserver1
  14. 14. © Copyright IBM Corporation 2010Custom installationA custom installation is required in the following scenarios:• You want to use software already installed as part of the WebSphereCommerce stack.• You want to do a distributed installation of WebSphere Commerce orits components.• You want to use anything other than the standard IBM components.• You want to use the old implementation of WebSphere CommercePayments.
  15. 15. © Copyright IBM Corporation 2010Installation directoriesDB2 /opt/IBM/db2/9.5HTTP Server /opt/IBMIHSWebSphere ApplicationServer/opt/IBM/WebSphere/AppServerWebSphere Commerce /opt/IBM/WebSphere/CommerceServer70
  16. 16. © Copyright IBM Corporation 2010Verify installation• Check the installation log files:– <WC_installdir>/logs/db2.setuplog– <WAS_installdir>/logs/install/log.txt– <WC_installdir>/logs/install.log– <WC_installdir>/instances/<instance_name>/logs– <WC_installdir>/logs/wctrace_date_time.log– <WC_installdir>/logs/wcinstall.log• Check that the non-root user starts DB2 correctly.
  17. 17. © Copyright IBM Corporation 2010Other installation considerations• Database– In a multi-tier environment, install the database server first.– If using Oracle, install and configure the database components first.• Web server– Ensure SSL is configured.– If using Microsoft IIS or Sun ONE, install and configure prior to WebSphereCommerce configuration.• Global security– Activated when WebSphere Application Server is installed– Can be deactivated using wsadmin– Should be enabled when site is in production– Requires user ID and password to execute commands or access consoleThese steps are outlined in the WebSphere Commerce installation guide. Manualconfiguration of components may also be required.
  18. 18. © Copyright IBM Corporation 2010Installing optional components• All optional software must be installed separately.• Refer to the Additional Software Guide for instructions for:– WebSphere Commerce Analyzer– IBM Tivoli Directory Server (or other LDAP server)– WebSphere Commerce Recommendation Engine• This also includes instructions for configuring WebSphere MQ andWebSphere InterChange Server.
  19. 19. © Copyright IBM Corporation 2010UninstallingUninstalling WebSphere Commerce is not trivial, and its componentsmust be uninstalled before WebSphere Application Server.1. Stop WebSphere Commerce, and if present, Payment instances.2. Stop any WebSphere Commerce, WebSphere Application Server, DB2processes.3. Delete any existing WebSphere Commerce instance.4. If present, delete any existing WebSphere Payment instance.5. Start the WebSphere Commerce uninstall process.6. Uninstall WebSphere Application Server; then IBM HTTP Server.7. Uninstall DB2• Cleanup of directories and configuration files may be needed afterWebSphere Commerce is uninstalled.• Follow the instructions in the Appendix of the Installation Guide carefully.
  20. 20. © Copyright IBM Corporation 2010The WebSphere Commerce instanceEach WebSphere Commerce instance has its own:• WebSphere Application Server profile (created by ConfigurationManager)• WebSphere Application Server Administration Console• IBM HTTP Server httpd.conf in<WC_installdir>/instances/inst/httpconf• IBM HTTP Server logs in<WC_installdir>/instances/inst/httplogs• IBM HTTP Server process• Database
  21. 21. © Copyright IBM Corporation 2010Configuration process• The WebSphere Commerce Configuration Manager is used to createthe instance• Instance creation requires a number of configuration steps:1. Create instance configuration files.2. Create database, tables, indexes, and so forth.3. Import bootstrap data.4. Configure web server including SSL, virtual hosts, path aliases.5. Configure WebSphere Application Server.• Virtual host aliases• JDBC driver and data source• Application server and application
  22. 22. © Copyright IBM Corporation 2010Start the Configuration Manager• Ensure that necessary services are started on the server.– Database server– IBM WebSphere Commerce 7.0 Configuration Manager• Start the Configuration Manager client.– Code to start the CM client• Log in to the ConfigurationManager using the user IDconfigadmin and thepassword specifiedduring installation.
  23. 23. © Copyright IBM Corporation 2010Create WebSphere Commerce instance
  24. 24. © Copyright IBM Corporation 2010Instance creation wizard (1 of 3)• Instance:– Enter instance name (must be unique).– Enter merchant key for data encryption.– Specify site administrator user ID and password.• Database:– Create new or use existing.– Enter database administrator name and password.– Enter database name (must be unique).– Choose database type (DB2 or Oracle).– Specify if remote database.• Schema:– Enter database user name.– Enter database password.
  25. 25. © Copyright IBM Corporation 2010Instance creation wizard (2 of 3)• WebSphere:– Enter cell and node name of WebSphere Application Server profile.– Enter data source name.– Enter JDBC driver location.• Specify languages for which to load translated data.• Web server:– Enter host name (must be unique).– Choose web server type.– Choose server ports.– Choose basic or X.509 authentication.• Staging:– Enable staging server.– Enable workspaces.
  26. 26. © Copyright IBM Corporation 2010Instance creation wizard (3 of 3)• Click Finish to begin instance creation:– Instance files are created in directory<WC_installdir>/instances/<instance_name>– Database is created and bootstrap data is loaded.– Web server definition is created.– WebSphere Application Server resources are imported.• Instance creation can take 30 minutes or longer.• After creation:– Start the web server for the WebSphere Commerce instance.– Start the WebSphere Commerce server.
  27. 27. © Copyright IBM Corporation 2010Commerce instance creationAnt targets divided into four logical groups:ConfigureDatabase • Database• Schema (tables, keys)• Bootstrap dataConfigureCommerceServer • Application server• Virtual hosts• Data source• EARConfigureWebServer • Web server configurationRegisterInstance • ConfigurationfilesDatabaseApplication ServerWeb Serverconfig
  28. 28. © Copyright IBM Corporation 2010Invoking an Ant target1. Depending which operating system you use, open a commandprompt, UNIX shell, and so forth.2. Since all Ant targets must be executed as the non-root user, switch tothat user.3. Navigate to the WC_installdir/bin directory.4. Run the command:config_ant[.sh] -DinstanceName=instanceName-Dparam1=value1 -Dparam2=value2 CreateInstance
  29. 29. © Copyright IBM Corporation 2010Instance settings
  30. 30. © Copyright IBM Corporation 2010Verify configurationCheck the instance creation log files to ensure successful databasecreation and WebSphere Application Server import.• Instance configuration file:– <WC_installdir>/instances/<instance_name>/xml/<instance_name>.xml• Instance creation logs:– <WC_installdir>/instances/<instance_name>/logs/createInstance*.log– <WC_installdir>/instances/<instance_name>/logs/createdb*.log• WebSphere Commerce Server log:– <WAS_installdir>/profiles/<instance_name>/logs/server1/SystemOut.log• Read the installation guide for more details on the available logs.
  31. 31. © Copyright IBM Corporation 2010WebSphere Application Server resources• WebSphere Application Server profile– <instance_name>• Application server– server1• Web server– webserver1• Enterprise application– WC_<instance_name>• Web modules• EJB modules• Connector modules• JDBC provider– <instance_name> — WebSphere Commerce JDBC provider• WebSphere Commerce DB2 data source <instance_name>• Virtual hosts
  32. 32. © Copyright IBM Corporation 2010Detailed configurationIBMHTTPServerWebSphereApplicationServerplug-inUsesPlugin-cfg.xmlWebSphereCommercevirtual hostsApplication Serverserver1WebSphere Commerce EARWebSphere Application Server cellBind toRun on Run onRun onWARs EJBsWeb serverdefinitionGenerate
  33. 33. © Copyright IBM Corporation 2010Configure an SSL certificate
  34. 34. © Copyright IBM Corporation 2010Testing instance creation• If you can log on to the WebSphere Commerce tools, the configurationwas most likely successful.• Before you launch the WebSphere Commerce tools, you must performthe following:– Make sure SSL is enabled in the web server.– Verify your browser settings.• Launch WebSphere Commerce Administration Console.– https://<hostname>:8002/adminconsole– Log in as site administrator specified in instance wizard.
  35. 35. © Copyright IBM Corporation 2010Starting and stopping an instance• WebSphere Application Server node agent• Execute the command from a profile:<WAS_installdir>/profiles/<profileName>/bin/• startServer.sh <server>• stopServer.sh <server>• serverStatus.sh –all
  36. 36. © Copyright IBM Corporation 2010WebSphere profiles• WebSphere files are split into two components:– Shared static files or product binaries– User customizable data files (profiles), which include WebSphere configuration,installed applications, resource adapters, properties, log files, and others
  37. 37. © Copyright IBM Corporation 2010Advantages of profiles• Stand-alone EAR• Ant targets for configuration• Clustering improves as WebSphere Application Server distributes theEAR to all cluster membersBenefits:• Follows the WebSphere Application Server administration model– Simplify migration to future releases of WebSphere Application Server– Better management using the WebSphere Application Server AdministrativeConsole• Manage the runtime state of the WebSphere Commerce applicationand WebSphere Administration Server– Set trace specification without restarting server– Start or stop WebSphere Commerce using the administrative console– Automatic propagation of plugin-cfg.xml file charges for IBM HTTP Server• Can start and stop the web server of each WebSphere Commerceinstance independently of the others
  38. 38. © Copyright IBM Corporation 2010Instance configuration file• <WC_installdir>/instances/<instance_name>/xml/<instance_name>.xml– This is the master configuration file for your instance.– This file is deployed to the EAR when changes occur.• <WC_eardir>/xml/config/wc-server.xml is the file used by theruntime.
  39. 39. © Copyright IBM Corporation 2010Deleting a WebSphere Commerce instance• As non-root user run the command:config_ant.sh –DinstanceName=value RemoveInstance• The following configurations are removed:– Instance-related configurations from WebSphere Application Server profile– Web server configuration (IBM HTTP Server only)– Unregister instance from Configuration Manager– <WC_installdir>/instances/<instance> directory• The following objects are not removed:– Database– WebSphere Application Server profile for the instance
  40. 40. © Copyright IBM Corporation 2010Advanced configurationDMZ: demilitarized zoneWAS: WebSphere Application ServerWC: WebSphere CommerceBrowserWebServerACustomerInternet DMZ IntranetWCServerAWCServerBWASserver1WASnodeagentWebserverDMgrDBServerADBServerBFirewallA FirewallBWASserver1WASnodeagentShareddiskWebSphereCommerceServerWebSphereCommerceServer2DatabaseserverWASdmgrDatabaseserverDatabaseclientDatabaseclientWCdatabaseWASplug-in
  41. 41. © Copyright IBM Corporation 2010Migration• Contact IBM for migration from a version before version 5.6.1.• Migration from the following versions is supported:– WebSphere Commerce Version 6.0 Feature Pack 1, 2, 3, 4, 5– WebSphere Commerce Version 5.6.1• Migration to higher editions is supported.• A GUI migration wizard is available.– Outlines best practice approaches– Provides default values– Hides complexity of underlying tools– Reduces probability of errorsPlanning and testing phases are mandatory.
  42. 42. © Copyright IBM Corporation 2010WebSphere Commerce V7 Feature Pack 1 installationUse the integrated installation wizard.• Download Feature Pack 1 from Passport Advantage site.• Store in a temporary location FeaturePack_tempdir.• As root, export the display and ensure access to the X server.• Navigate to FeaturePack_tempdir.• Enter: ./install• Follow the wizard accepting the defaults.• Enter WC_installdir for Product Installation Location.• When the Summary Page displays, click Finish.• Select and enable the fix pack feature or features desired.
  43. 43. © Copyright IBM Corporation 2010Install WebSphere Commerce V7 Fix Pack 1 (1 of 2)• Benefit:– Allows upgrade to DB2 V9.7– Allows migration from WebSphere Commerce V6 FP5– Support for WebSphere Application Server 64 bit– Fixes• Three-step process:– Install update installer– Install fix pack to WebSphere Commerce product installation directory– Install fix pack to all WebSphere Commerce instances• Downloads:– Latest installer– Latest fix pack– Check information center for relevant technotes
  44. 44. © Copyright IBM Corporation 2010Install WebSphere Commerce V7 Fix Pack 1 (2 of 2)Installation:• Update installer:– Expand the update installer.– Install the update installer.• Fix pack:– Save the fix pack to UPDI_installdir/maintenance– Run the GUI wizard installing the fix pack to WC_installdir– Rerun the GUI wizard installing the fix pack to a WebSphere Commerceinstance.– Silent installation is available.
  45. 45. © Copyright IBM Corporation 2010Unit summaryHaving completed this unit, you should be able to:• Install WebSphere Commerce• Configure WebSphere Commerce• Verify an installation of WebSphere Commerce• Explain the migration framework• Use the migration framework to migrate from a previous version• Install optional WebSphere Commerce components• Install fix packs and feature packs for WebSphere Commerce• Set up an instance of WebSphere Commerce• Use the configuration manager tool and instance creation wizard
  46. 46. © Copyright IBM Corporation 2010Checkpoint1. What is the default WebSphere Commerce administrator ID?A. ncadminB. wcsadminC. No default — defined during installationD. No default — defined during instance configuration2. Place the following components in the order in which they are created duringinstance configuration:A. Instance configuration fileB. WebSphere Application Server profileC. WebSphere Commerce database3. Which configuration screen allows you to change the ports used for WebSphereCommerce tools access?A. InstanceB. DatabaseC. WebSphereD. Web server4. According to the installation guide, what is the minimum amount of memoryneeded to install WebSphere Commerce?A. 1 GB B. 2 GB C. 4 GB D. 8 GB
  47. 47. © Copyright IBM Corporation 2010Checkpoint solution1. What is the default WebSphere Commerce administrator ID?A.B.C. No default — defined during installationD.2. Place the following components in the order in which they are created duringinstance configuration:A. Instance configuration fileC. WebSphere Commerce databaseB. WebSphere Application Server profile3. Which configuration screen allows you to change the ports used for WebSphereCommerce tools access?A.B.C.D. Web server4. According to the installation guide, what is the minimum amount of memoryneeded to install WebSphere Commerce?B. 2 GB

×