Develop > Presentation layer > Customize IBM Sales Center > Deploy customizations to the IBM Sales Center > Post deployment provisioning mechanisms > Other software distribution systems


Example: Creating and testing a WED4WL software package

This section explains the example of creating and testing a WED4WL software package.

Prerequisites


Procedure

  1. A Tivoli server and Gateway are installed and configured with at least the TCM Software Distribution, Inventory, Activity Planner, and Change Manager features.

  2. An Endpoint agent is running on the target client and successfully connecting with the Gateway. For production install by client imaging, the Endpoint agent should be installed in the prototype client and form part of the initial client image.

  3. A second Windows client, the development client, has an Endpoint agent and a copy of the Tivoli Configuration Manager Software Package Editor component installed. The Software Package Editor is part of the Software Distribution function of TCM.

  4. The Sales Center Client install CD image is available to the development client.


Results

the Endpoint agent must be configured to run with a Windows user identity, and not with the Local Server identity. Eclipse Update Site installations will fail if the agent runs as Local Server.

To create and test a WED4WL software package:

  1. On the development client, run the WED4WL installer with the option to generate a prototype response file setupwin32.exe -options-template c:\response.txt

  2. Use a text editor to customize the generated response file following instructions in the WED4WL System Administrator's Guide. Do not set the installLocation product bean property in the response file.

  3. Launch the Software Package Editor on the development client

  4. In the Software Package Editor Selector dialog, choose Generic Software Package and OK.

  5. In the editor that opens, right click on the Noname package icon in the left hand navigator and choose Properties.

  6. In the General tab set the package name to WMC and the version to 6.0.

  7. Click on the Condition button and in the Condition Editor window double-click on os_name, then click on the == button, then type 'Windows_NT' in the text window. It should look like the following image:

    In Tivoli Configuration Manager, "Windows_NT" is the name used to refer to all supported Windows operating systems. See the TCM Reference Manual for Software Distribution for information about condition variables.

  8. Click OK.

  9. Back in the Package Properties editor, choose the Variable list tab. In the variable editor type install_location in the Name field and $(program_files)\IBM\WED in the Value field, then click on the Set button. This creates a variable and its default value that we can use in the installation script to control where WED4WL will install. Also create a variable install_temp with value $(install_location)\temp. This directory will be used to temporarily hold the install image files. The window should now look like the following image:

  10. Click OK.

  11. Back in the Software Package Editor, right click on the package icon again and select Insert -> Program -> Execute program as in the image below. An Execute Program Properties editor will open.

  12. In the Install tab of the Execute Program Properties editor type cmd in the Path field. This is the program that will be executed, the Windows Command interpreter. Click on the Advanced button and complete the properties as follows

  13. Arguments /c start /w setupwin32.exe -silent -options "$(install_temp)/response.txt" -P installLocation="$(install_location)"
    Inhibit parsing check
    Work directory $(install_temp)/install
    Reporting stardard error file on server check

    Click on OK.

  14. Back in the Execute program properties window, select the Add button in the Corequisite Files section. Navigate to the local file system location where the WED4WL install images are and select the "install" directory then click Open. Select the directory icon just created and click on the Edit button.

  15. In the Add Directory Properties window, change the Destination Location to $(install_temp). The dialog should now look like the following image:

    This will temporarily copy the "install" directory and all files and subdirectories to the path $(install_temp)/install. Click OK.

  16. Ensure the directory icon is not selected and click on the Add button again. This time copy the "updates" directory to $(install_temp)/updates

  17. Deselect any icons again and click on Add one more time. Navigate to the response.txt file created in step 1. Edit the created file entry to again set the Destination location to $(install_temp). The editor should now look like the following image. Click OK.

  18. In the main editor window select from the menus File -> Save as. Choose the Software Package Block file type and provide the name wmc6 for the file. The resulting bundled package is approximately 200 MB in size.

  19. To test the package locally on the development client, open a command shell window with the Software Distribution command line environment established. Your Start menu should contain a shortcut named SWDIS ENV that will open this. Run the command wdinstsp -Dinstall_location=c:\WMC6 wmc6.spb

    where wmc6.spb is the software package block file created in step 15 and C:\WMC6 will override the default install location of C:\Program Files\IBM\WED. The package will install in the directory C:\WMC6.

Tip: Refer to the IBM Tivoli Configuration Manager: Reference Manual for Software Distribution for more information about disconnected command line interface commands and software package change management states.


Related concepts

Other software distribution systems

Deploy customizations to the IBM Sales Center


+

Search Tips   |   Advanced Search