WebSphere Commerce Developer

Installing WebSphere Commerce Developer by using the IBM Installation Manager

You can install WebSphere Commerce Developer by using the graphical installation program, Installation Manager.

Note: WebSphere Commerce Developer supports the use of versions 7.5.5.x, 8.0.4.x, and 8.5.5.x. But since versions 7.5.5.x and 8.0.4.x are deprecated, the following topic teaches you how to install the latest supported version, Version 8.5.5.

Before you begin

Ensure that you completed the following tasks:
  • Install Rational Application Developer Version 8.5.5.3, or a higher fix pack for Version 8.5.5 with the WebSphere Application Server Test Environment on the machine.
  • Stop any applications that are running on your machine.
  • Disable any Web server that is configured on your machine.
  • Log on as a user with Administrator privileges.
  • WebSphere Commerce EnterpriseWebSphere Commerce ProfessionalIf you plan to use the IBM Sales Center development environment, you must preinstall the IBM Sales Center client. See Installing IBM Sales Center for WebSphere Commerce for details.
    Note: If you want to install the IBM Sales Center client, ensure that your system meets all the prerequisites described in the installation topic.
  • If you are using physical media, insert the WebSphere Commerce Developer DVD in the DVD-ROM of the Rational Application Developer machine.

Procedure

  1. Open Installation Manager.
  2. Add the WebSphere Commerce repository location to the Installation Manager:
    1. On the Start page of Installation Manager, click File > Preferences, and then click Repositories.
      The Repositories page opens, showing any available repositories, their locations, and whether they are connected.
    2. On the Repositories page, click Add Repository.
    3. In the Add Repository dialog box, click Browse. Navigate to the location of your WebSphere Commerce Developer DVD or eAssembly and select the repository.config file, and then click OK.
      The new repository location is listed.
    4. Click Test Connections to ensure that the Repository URL is available.
  3. Download the following fixes and add the repository locations to the Installation Manager.
    You need WebSphere Commerce Developer Fix Pack 9, Feature Pack 8, iFix JR55273, and iFix JR55296 to support Rational Application Developer Version 8.5.5.
    1. Download Fix Pack 9 and Feature Pack 8 for WebSphere Commerce Developer.
    2. Download the following interim fixes.
      Note: The following fixes are also included in cumulative interim fix package JR56287, but the package does not contain the necessary repository.config file so you need to download these fixes individually.
      • JR55273.fp (for Fix Pack 9 - 7.0.0.9-WS-WCDeveloperEdition-IFJR55273)
      • JR55273.fep (for Feature Pack 8 - 7.0.0.0-WS-WC70Fep8DeveloperEdition-IFJR55273)
      • JR55296.fp (for Fix Pack 9 - 7.0.0.9-WS-WCDeveloperEdition-IFJR55296)
      • JR55296.fep (for Feature Pack 8 - 7.0.0.0-WS-WC70Fep8DeveloperEdition-IFJR55296)
    3. On the Start page of Installation Manager, click File > Preferences, and then click Repositories.
      The Repositories page opens, showing any available repositories, their locations, and whether they are connected.
    4. On the Repositories page, click Add Repository.
    5. In the Add Repository dialog box, click Browse. Go to the location of your WebSphere Commerce Developer Fix Pack 9 repository and select the repository.config file, and then click OK.
      The new repository location is listed.
    6. In the Add Repository dialog box, click Browse. Go to the location of your WebSphere Commerce Developer Feature Pack 8 repository and select the repository.config file, and then click OK.
      The new repository location is listed.
    7. Repeat the steps to add the repository location to the interim fixes JR55273.fp. and JR55273.fep
    8. Click Test Connections to ensure that the repositories are available.
  4. From the Start page, click Install.
    The Installation Manager searches its defined repositories for available packages.
  5. Select the following package to install WebSphere Commerce Developer Version 7 Fix Pack 9 and then click Next:
    • IBM WebSphere Commerce Developer edition
      • Version 7.0.0.9
  6. Select the following fix to install.
    • IBM WebSphere Commerce Developer edition 7.0.0.9
      • JR55273.fp for WebSphere Commerce Version 7 Fix Pack 9 1.0.0.0
  7. View the License panel carefully, and select I accept the terms in the license agreements, then click Next.
  8. Select Create a new package group. Click Next.
  9. Select the languages that you want to install.
    The default is English. Click Next.
  10. Under the IBM WebSphere Commerce Developer edition name feature, select the WebSphere Commerce toolkit feature.
  11. Optional: WebSphere Commerce EnterpriseWebSphere Commerce Professional If you plan to use the IBM Sales Center toolkit, under the IBM WebSphere Commerce Developer edition name feature, select the IBM Sales Center toolkit feature.
    The IBM Sales Center toolkit is installed to the same location as the WebSphere Commerce toolkit.
  12. Click Next.
  13. Confirm all information and click Install.
    After the installation completes, a Summary page is displayed. In the success message, a link to the Installation Manager log is provided.
  14. Click Finish.
  15. Install Feature Pack 8 and the necessary interim fixes.
    1. Click Install.
    2. Select the following package to install WebSphere Commerce Developer Version 7 Feature Pack 8 and then click Next:
      • IBM WebSphere Commerce Developer Feature Pack
        • Version 8.0.0.0
    3. Select the following fix to install.
      • IBM WebSphere Commerce Developer Feature Pack 8.0.0.0
        • JR55273.fep for WebSphere Commerce Version 7 Feature Pack 8 1.0.0.0
    4. Select the WebSphere Commerce Developer package group and click Next.
    5. Skip the configuration enablement Features panel. Do not enable features now.
    6. Review the installation summary and click Install to begin the installation process.
      After the installation completes, a Summary page is displayed. In the success message, a link to the Installation Manager log is provided.
    7. Click Finish.
  16. Install interim fixes JR55296.fp and JR55296.fep by using the WebSphere Commerce Update Installer (UPDI).
    For information about how to install WebSphere Commerce Developer interim fixes, see one of the following topics:
  17. Ensure that all installations completed successfully.
    1. Examine the contents of WCDE_installdir/logs/setup.log.
      If setup.log is empty or has errors, run WCDE_installdir/bin/restoreDefault.bat from the command line, then run setup.bat.
    2. Check that the installation was able to properly detect Rational Application Developer on your system by ensuring that WCDE_installdir/bin/setenv.bat sets the RAD_HOME environment variable to RAD_installdir correctly.
    3. WebSphere Commerce EnterpriseWebSphere Commerce Professional If you installed the IBM Sales Center development environment component, examine the contents of the WCDE_installdir/logs/setupmsc.log for errors.
      If errors appear in the setupmsc.log, examine the WCDE_installdir/bin/setenv.bat file. Ensure that the RAD_HOME environment variable points to the correct Rational Application Developer installation location, and that the WED_HOME environment variable points to the correct IBM Sales Center for WebSphere Commerce location.

What to do next

  • Start WebSphere Commerce Developer.
    Feature Pack 8WebSphere Commerce Version 7.0.0.9Note: If you installed interim fix JR55273, you might notice guava.jar errors in the enableFeature.log file or in the WebSphere Commerce Developer Problems window. You can ignore errors messages that are related to guava.jar. For example,
    [workspaceBuild] org.eclipse.jst.jee.archive.ArchiveOpenFailureException:
    java.io.FileNotFoundException: \WC\lib\guava.jar (The system cannot find the path specified)  
    [workspaceBuild] Caused by: java.io.FileNotFoundException: \WC\lib\guava.jar (The system cannot find
    the path specified) 
  • If needed, you can change the development database type.