Introduction

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 utility is often used to copy software package repositories from various sources (for example, CDs, DVDs, Internet, and so on) 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 perform the installation of 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 leverages the Installation Manager as the install technology. To set up the WebSphere Commerce development environment, the following IBM products must be installed:

• Rational® Application Developer V7.5.4 or Rational Software Architect V7.5.4
• WebSphere Application Server Test Environment V7.0

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

This article demonstrates how you can use the utility to create a central repository for WebSphere Commerce Developer assets. This includes the following IBM software package repositories:

• Rational Application Developer V7.5.4
• 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

You can optionally make your central repository available on your intranet via HTTP, FTP, or a network shared drive. Finally, you will learn how to maintain your central repository using the utility.

Benefits

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 have to wait until the updates to these software packages are available on the intranet.

There are several benefits for having a central repository in your site, including but not limited to the following:

• Only an administrator needs to download all the software packages and create the central repository.
• When installing products, developers only need to add 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 also 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 just refer to the central repository to apply updates to their environment.
• Developers save time by not having to download each software package themselves and their latest fixes that keep increasing 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.
• All developers are using software that is consistent with each other.

Objectives

Learn how to:

• Use the utility to create a central repository for WebSphere Commerce assets.
• Make your central repository available over the local intranet.
• Use the utility to maintain your central repository.

Back to top

Creating a central repository

In this section, you will download and install the utility and then use it to create a central repository to include all WebSphere Commerce assets.

Installing the IBM Packaging Utility

Follow the steps to download and install the utility:

1. Choose a server where you want to host the central repository.
2. Download the IBM Packaging Utility installation files for your platform.
3. Browse to the downloaded image location and run install.exe from the InstallImage_Platform folder. Follow the prompts in the installation wizard to complete the installation.

Now that you have installed the utility on your server, we can move on to demonstrate how to use the utility to create a central repository that will contain all the WebSphere Commerce Developer assets. Since WebSphere Commerce Developer V7.0 and its supporting software are available in two different formats, one as eAssemblies from Passport Advantage and one as physical media (CD/DVDs), there are two different ways of doing this according to which media source you wish to use:

• If you want to use the eAssemblies, then follow the instructions in the Using eAssemblies to create a central repository section
• If you want to use physical media, then follow the instructions in the Using physical media to create a central repository section.

Note: Make sure you follow only one set of instructions according to the source format you want to use, not both.

Back to top

Using eAssemblies to create a central repository (recommended)

If you want to use eAssemblies of the WebSphere Commerce assets, then follow the procedure below to create a central repository.

Before you begin

1. Download the following product eAssemblies to the server:
   1. Rational Application Developer Version V7.5.4.
   2. WebSphere Application Server Test Environment (WTE) V7.0.
   3. WebSphere Commerce Developer Version V7.0.
   4. The most recent WebSphere Commerce Developer fix pack desired at your site.
   5. The most recent WebSphere Commerce Developer feature pack desired at your site.
2. Extract each package to a temporary location. For example:
   1. RAD_WTE_image_location
   2. WCDE_image_location
   3. FP_image_location
   4. FEP_image_location
3. Download the latest version of IBM Installation Manager and extract it to a temporary location. For example: IM_image_location.

Procedure

1. Run the IBM Packaging Utility.
2. Click Copy Packages.
3. Click Open Repository.
4. Add the latest version of the Installation Manager to the central repository:
   1. Browse to the IM_image_location and select repository.config.
   2. Optional: Enter a name in the Repository Name to replace the default.
   3. Click OK.
      
5. Add the Rational Application Developer V7.5.4 and WebSphere Application Server Test Environment (WTE) V7.0 repositories to the central repository:
   1. Browse to the RAD_WTE_image_location\RAD_SETUP and select diskTag.inf.
   2. Optional: Enter a name in the Repository Name to replace the default.
   3. Click OK.
6. Add the WebSphere Commerce Developer V7.0 repository to the central repository:
   1. Browse to the WCDE_image_location and select repository.config.
   2. Optional: Enter a name in the Repository Name to replace the default.
   3. Click OK.
7. Add the most recent WebSphere Commerce Developer V7.0 fix pack repository desired at your site to the central repository:
   1. Browse to the FP_image_location and select repository.config.
   2. Optional: Enter a name in the Repository Name to replace the default.
   3. Click OK.
8. Add the most recent WebSphere Commerce Developer V7.0 repository feature pack desired at your site to the central repository:
   1. Browse to FEP_image_location\developer and select repository.config.
   2. Optional: Enter a name in the Repository Name to replace the default.
   3. Click OK.
9. Select all the required products to be copied to the central repository as shown in Figure 1.
   
   Figure 1. Products to be copied to the central repository
   
   
   
10. Click Next.
11. Review the license agreements and click Accept.
12. Select a location on the server where you want to create the central repository. This location will be referred to as "common_repo" throughout the rest of this article. Click Next.
13. Review the summary page and click Copy to begin creating the central repository.
14. Once successful, click Finish and close the IBM Packaging Utility.

Your central repository is now created under common_repo that you specified in Step 13 above on the server.

Back to top

Using physical media to create a central repository

If you want to use the physical media (CD/DVDs) of the WebSphere Commerce assets, then follow the procedure below to create a central repository.

Before you begin

1. Ensure that you have the following product CD/DVDs available:
   1. Rational Application Developer Version V7.5.4.
   2. WebSphere Application Server Test Environment (WTE) V7.0.
   3. WebSphere Commerce Developer Version V7.0.
   4. The most recent WebSphere Commerce Developer feature pack desired at your site.
2. Since WebSphere Commerce Developer V7.0 Fix Packs are not available in physical media format, you must download them from Passport Advantage. Download the most recent WebSphere Commerce Developer V7.0 fix pack supported at your site and extract it to a temporary location. For example, FP_image_location.
3. Download the latest version of IBM Installation Manager and extract it to a temporary location. For example: IM_image_location.

Procedure

1. Insert the CD labeled IBM WebSphere Commerce V7.0 - WebSphere Commerce Rational Application Developer V7.5.4 Set Up Multilingual into the CD/DVD drive of the server.
2. Run the IBM Packaging Utility.
3. Click Copy Packages.
4. Click Open Repository.
5. Add the latest version of the Installation Manager to the central repository:
   1. Browse to IM_image_location and select repository.config.
   2. Optional: Enter a name in the Repository Name to replace the default.
   3. Click OK.
6. Add the Rational Application Developer V7.5.4 and WebSphere Application Server Test Environment (WTE) V7.0 repositories to the central repository:
   1. Browse to the CD/DVD drive and select diskTag.inf.
   2. Optional: Enter a name in the Repository Name to replace the default.
   3. Click OK.
7. Select all the required products to be copied to the central repository as shown in Figure 2.
   
   Figure 2. IBM Installation Manager and Rational products to be copied to the central repository
   
   
   
8. Click Next.
9. Review the license agreements and click Accept.
10. Select a location on the server where you want to create the central repository. This location will be referred to as common_repo throughout the rest of this article. Click Next.
11. Review the summary page and click Copy to begin creating the central repository. Insert appropriate disks as prompted by the utility.
12. Once successful, click Finish.
13. Insert the DVD for WebSphere Commerce Developer V7.0 into the DVD drive.
14. Click Copy Packages.
15. The source window will include repositories that you have opened previously. You can optionally close them or leave them unchecked. Click Open Repository.
16. Add the WebSphere Commerce Developer V7.0 repository into the central repository:
    1. Browse to the DVD drive and select repository.config.
    2. Optional: Enter a name in the Repository Name to replace the default.
    3. Click OK.
17. Add the most recent WebSphere Commerce Developer V7.0 fix pack repository desired at your site to the central repository:
    1. Browse to the FP_image_location and select repository.config.
    2. Optional: Enter a name in the Repository Name to replace the default.
    3. Click OK.
18. Select all the required products to be copied to the central repository as shown in Figure 3.
    
    Figure 3. Fix pack to be copied to the central repository
    
    
    
19. Click Next.
20. Review the license agreements and click Accept.
21. Browse to the common_repo directory and click Next.
22. Review the summary page and click Copy to begin creating the central repository.
23. Once successful, click Finish.
24. Insert the DVD for the most recent desired WebSphere Commerce V7.0 feature pack into the DVD drive.
25. Click Copy Packages.
26. Click Open Repository.
27. Add the WebSphere Commerce Developer V7.0 feature pack repository desired at your site into the central repository:
    1. Browse to <DVD drive>/developer and select repository.config.
    2. Optional: Enter a name in the Repository Name to replace the default.
    3. Click OK.
28. Select all the required products to be copied to the central repository as shown in Figure 4.
    
    Figure 4. Feature pack to be copied to the central repository
    
    
    
29. Click Next.
30. Review the license agreements and click Accept.
31. Browse to the common_repo directory and click Next.
32. Review the summary page and click Copy to begin creating the central repository.
33. Once successful, click Finish.

Your central repository is now created under common_repo. You can also create a central repository by using a mixture of physical media and eAssemblies.

Back to top

Making your central repository available over the local intranet

Currently, the central repository that you created can only be used on the server. To make the most use of it, we recommend that you make this central repository available over your local intranet. This can be done several ways. Here, we outline three common methods:

• HTTP
• FTP
• Network Share

Making the central repository available over HTTP

To make your central repository available over HTTP, you need to install and set up a web server (for example: IBM HTTP server, Microsoft® IIS, and so on) on your server. Configure your web server to make the common_repo visible on the local server through HTTP. If you configured your web server to be password protected, the Installation Manager prompts you for user credentials when adding this repository.

Making the central repository available over FTP

To make your central repository available over FTP, you need to install and set up a FTP server (for example, Filezilla Server, Mozilla fireFTP, and so on) on your server. Configure your FTP server to make common_repo visible on the local server through FTP.

Making the central repository available via Network Share

To share your central repository over the network, use the Microsoft Windows® Sharing feature to make the common_repo directory shared onto your network. You can also configure your Samba server to share common_repo over the network. Developer workstations can map to the drive where common_repo is located.

Back to top

Maintaining your central repository

You can also use the utility to maintain your central repository. The maintenance of central repository includes the following actions:

• Add new software packages.
• Remove software packages.
• Update software packages.

Add new software packages to the central repository

If there are other products at your site that are installed via the Installation Manager, you can also add them to the custom central repository. Follow the steps in the next section.

Before you begin

• If the software is packaged as a CD/DVD, ensure you have the CD/DVD available and inserted in the CD/DVD driver of the system where your central repository is hosted.
• If the software is packaged as a zip file, then extract the package to a temporary location on the system where your central repository is hosted.

Procedure

1. Run the IBM Packaging Utility.
2. Click Copy Packages.
3. Click Open Repository.
4. Add your software package to the repository:
   1. Browse to the CD/DVD drive or to the location where your software is extracted and select diskTag.inf if it exists, else select repository.config.
   2. Optional: Enter a name in the Repository Name to replace the default.
   3. Click OK.
5. Ensure the correct version of the product you want to install is checked. Click Next.
6. Review any license agreements and click Accept.
7. Browse to the location of your central repository.
8. Click Next.
9. Review the summary page and click Copy to begin creating the repository. Insert appropriate disks if prompted by the utility.
10. Once successful, click Finish and exit the utility.

You have now successfully added your software package to the central repository.

Removing software packages from the central repository

You can use the utility to remove any software packages you wish from the repository. To do this, follow the steps in the next section.

Procedure

1. Run the IBM Packaging Utility.
2. Click Delete Packages.
3. Click Open Repository.
4. Browse to the location of your central repository and select repository.config, click OK.
5. The source window now shows all the products that are included in the repository. Select one or more software packages that you wish to delete and click Next.
6. Review the summary panel and click Delete to start the deletion process.
7. Once successful, click Finish and close the utility.

You have now successfully removed the software packages from the central repository.

Add updates for software packages to the central repository

If there are updates available to one or more software in the central repository, you can use the utility to add those updates to the repository.

The utility provides two methods of doing this:

1. Download the update package and follow the instructions in the Add new software packages to the central repository section to add it to the central repository.
2. Use the utility's built-in feature to download and add update packages to the central repository by following the procedure below.

Note: In the context of WebSphere Commerce assets, the second method can only be used to add updates for Rational Application Developer V7.5.4 and WebSphere Application Server Test Environment V7.0. Updates to WebSphere Commerce Developer V7.0 fix packs and feature packs must be added using the first method.

Before you begin

Ensure your server has access to the Internet.

Procedure

1. Run the IBM Packaging Utility.
2. Click Copy Packages.
3. Click Open Repository.
4. Browse to the location of your central repository, select repository.config, and click OK.
5. The source window now shows all the products that are included in the central repository. Select the software package that you wish to update and click Check for Updates.
6. The utility will display the latest version available for the selected product. If you wish to see all versions available, select the Show All radio button. An example of this for Rational Application Developer V7.5 is shown in Figure 5.
   
   Figure 5. Available updates for Rational Application Developer
   
   
   
7. Select the version you want to add to the central repository and click Next.
8. Review any license agreements and click Accept.
9. Browse to the location of your central repository.
10. Click Next.
11. Review the summary page and click Copy to begin creating the central repository. Insert appropriate disks if prompted by the utility.
12. Once successful, click Finish and exit the utility.

You have now successfully added updates for software packages to the central repository.

Back to top

Next steps

Now that your central repository is created and available over the local intranet, you can now use it to install software on a developer's environment. There are two ways of doing this:

• Using the IBM Installation Manager
• Using the Enterprise Deployment Utility

Using the IBM Installation Manager

Developers can use the Installation Manager to install software on their environment by following the procedure below.

Before you begin

Ensure that you have the Installation Manager installed on your system. Also, make sure you know the correct URL for the central repository. The URL format depends on how you made the central repository available over the local intranet.

• Via HTTP: http://<hostname of the server>/common_repo
• Via FTP: ftp://<hostname of the server>/common_repo/repository.config
• Via Network Share: Map a drive letter to the common_repo drive, such as Y. The URL is: Y:\common_repo\repository.config.

Procedure

1. Launch the Installation Manager.
2. From the Menu, select File > Preferences.
3. Click Add Repository, enter the correct URL to the central repository, and click OK. An example is shown in Figure 6.
   
   Figure 6. Central repository added to IBM Installation Manager
   
   
   
4. Ensure that the repository you just added is selected and click OK.
5. Click Install and you can now see all the products that are included in the central repository. An example is shown in Figure 7.
   
   Figure 7. Available products to install
   
   
   
6. Select the products you wish to install and follow the wizard to complete the installation.

Using the Enterprise Deployment Utility

If all developers are required to have identical development environment at your site, then you can use the Enterprise Deployment Utility to mass deploy WebSphere Commerce Developer V7 to all of the developers' workstations. Follow the instructions in the Using the Enterprise Deployment Utility in WebSphere Commerce V7 article to set up all of the developers' workstations.

If you want to further mass deploy a customized WebSphere Commerce development environment, you can follow the instructions in the Customizing the Enterprise Deployment Utility to deploy WebSphere Commerce environments article.

Back to top

Conclusion

From this article, you learned how to use the IBM Packaging Utility to create and manage a common central repository that contains all of the WebSphere Commerce Developer V7.0 assets and to make this repository available over the local intranet. You also learned how to use the repository to set up all the developers' workstations.

Acknowledgements

The author would like to thank Brian Lima and Keith Chan for reviewing this article.

Resources

Learn

• WebSphere Commerce Information Center: WebSphere Commerce development environment
  
  
• IBM Installation Manager Information Center: IBM Packaging Utility IBM Installation Manager Information Center: IBM Installation Manager
  
  
• Using the Enterprise Deployment Utility in WebSphere Commerce V7
  
  
• Customizing the Enterprise Deployment Utility to deploy WebSphere Commerce environments
  
  
• developerWorks WebSphere Commerce zone
  
  

Discuss

• WebSphere Commerce discussion forum
  
  

About the author

Jitendra Gupta is a Staff Software Developer on the WebSphere Commerce Deployment team at the IBM Toronto Lab, Canada. He is responsible for designing and implementing WebSphere Commerce installers, and is the Scrum Master for the Deployment team.

Rate this article

Comments

Back to top

Table of contents

• Introduction
• Creating a central repository
• Using eAssemblies to create a central repository (recommended)
• Using physical media to create a central repository
• Making your central repository available over the local intranet
• Maintaining your central repository
• Next steps
• Conclusion
• Resources
• About the author
• Comments

Local resources

• IBM Innovation Center - Austin, TX
• IBM Innovation Center - Chicago, IL
• IBM Innovation Center - Dallas, TX
• IBM Innovation Center - San Mateo, CA
• IBM Innovation Center - Waltham, MA
• Technical Briefings in North America

Dig deeper into WebSphere on developerWorks

Try IBM PureSystems. No charge.

Experience today!

---

Get started with the cloud-based trial and pattern development kit.

Special offers