WebSphere Commerce Developer

Overview of the IBM Packaging Utility

The IBM Packaging Utility is a publicly available packaging tool that combines the repositories of different IBM software packages into a common central repository. You can use the utility to move software packages between repositories or delete software packages from central repositories.

The IBM Packaging Utility can be used to copy software package repositories from various sources (such as, CDs, DVDs, the Internet) onto internal servers. In addition, you can also copy the latest fix packs and fixes of software packages onto the internal servers so not everyone in the enterprise needs to download it. By pointing the IBM Installation Manager to the internal servers, you can install the software from a common source.

The IBM WebSphere Commerce Developer product provides the development environment for WebSphere Commerce. In WebSphere Commerce V7.0, the development environment uses the Installation Manager as the installation technology. To set up the WebSphere Commerce development environment, the following IBM products must be installed:
  • Rational Application Developer Version 8.5.5.3, or a higher fix pack for Version 8.5.5
  • WebSphere Application Server Test Environment V7.0

WebSphere Commerce Developer V7.0 fix packs and feature packs are also applied using the Installation Manager.

Use the topics in this section to learn the following information:
  • How to use the IBM Packaging Utility to create a central repository for WebSphere Commerce Developer assets. This includes the following IBM software package repositories:
    • Rational Application Developer Version 8.5.5.3, or a higher fix pack for Version 8.5.5
    • WebSphere Application Server Test Environment V7.0
    • WebSphere Commerce Developer V7.0
    • WebSphere Commerce Developer V7.0 Fix Pack
    • WebSphere Commerce Developer V7.0 Feature Pack
  • How, if you want, you can make your central repository available on your intranet using HTTP, FTP, or a network shared drive.
  • How to use the IBM Packaging Utility to maintain your central repository.

Benefits of using a central repository

Without a central repository, you need to manually download and add each software package repository to the Installation Manager. In an enterprise, this becomes a time-consuming and tedious process as each developer needs to do this on their local machine. In some enterprises, the developers do not have Internet access so they must wait until the updates to these software packages are available on the intranet.

There are several benefits to having a central repository in your site. The following are just some of the benefits:
  • Only an administrator needs to download all the software packages and create the central repository.
  • When installing products, developers need to add only one repository to the Installation Manager for all products instead of one per product.
  • It is ideal for sites that have no Internet connection for developers, as the central repository is available over the local intranet.
  • Administrator can control the minimum and maximum level of software that can be installed by the developers.
  • When software updates are available, only one person needs to download and update the central repository. All other developers can refer to the central repository to apply updates to their environment.
  • Developers save time because they do not need to download each software package themselves and their latest fixes, which increase in size over time.
  • There is no need to order or create duplicate CD/DVDs for all developers in the site.
  • There is no need to fumble with all the CD/DVD packages.
  • To ensure that all developers are using software that is consistent with each other.