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 an Eclipse update site software package
This section explains the example of creating and testing an Eclipse update site software package.
Prerequisites
Procedure
- A Tivoli server and Gateway are installed and configured with at least the TCM Software Distribution, Inventory, Activity Planner, and Change Manager features.
- 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.
- 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.
- 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.
The following steps will create a Software Package from an Eclipse Update Site. The Sales Center update site is used for purposes of illustration, but the same procedure can be used to distribute Update Sites built with the customizations:
- Launch the Software Package Editor on the development client
- In the Software Package Editor Selector dialog, choose Generic Software Package and OK.
- In the editor that opens, right Click the Noname package icon in the left hand navigator and choose Properties.
- Enter the name Sales Center and the version 1.0.
- Click the Condition button and in the Condition Editor window double-Click os_name, then Click the == button, then type 'Windows_NT' in the text window.
- Click OK.
- 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 the Set button. When the distribution is installed, this variable must be set to the path where WED4WL has already been installed. Also create a variable install_temp with value $(install_location)\temp. This directory will be used to temporarily hold the install image files.
- Click OK.
- Back in the Software Package Editor, right Click the package icon again and select Insert -> Program -> Execute. An Execute Program Properties editor opens.
- In the Install tab of the Execute Program Properties editor type installfeature.bat in the Path field. This is the name of the Windows batch file that will run. Click the Advanced button and complete the properties as follows, including the quotes where given
Arguments "$(install_location)" Inhibit parsing Not checked Work directory $(install_temp) Reporting stardard error file on server Check
- Click OK.
- Copy the following text into a file named installfeature.bat located somewhere on the development client
setlocal enableextensions set WED_HOME=%1 set CUR_DIR=%~dp0 %WED_HOME%\rcp\rcplauncher -application org.eclipse.update.core.standaloneUpdate -nosplash -os win32 -arch x86 -command install -featureId FEATUREID -version VERSION -from "file:/%CUR_DIR%/" -to %WED_HOME%\sc\eclipse -rcpLauncherWait -consolelog -data "%CUR_DIR%/data" set rc=%ERRORLEVEL% if errorlevel 1 goto :error rem replicate previous lines to add other features :error rem endlocal is implied by end of script exit %rc%
Edit this file replacing the text FEATUREID with the name of a feature to install and VERSION with its version number.
To install Sales Center, replace FEATUREID with the name of the primary feature com.ibm.commerce.telesales.impl.feature and VERSION with 1.1.0. Any nested features in the update site will also be installed. If the site has more than one primary feature, replicate those lines and replace FEATUREID and VERSION with the corresponding values for the other features, as many times as necessary.
Note that this script takes one command line argument, that is the path where an instance of WED4WL is already installed. The script assumes that it will be in the same directory where the update site's site.xml file is located.
It implicitly creates an install site named "sc". You may encounter errors if you attempt to use an existing install site instead. In particular, the site at %WED_HOME%\shared\eclipse cannot be installed into using this mechanism.
- Back in the Execute program properties window, select the Add button in the Corequisite Files section. Navigate to the local file system location of the Eclipse update site and select its directory then click Open.
- Select the directory icon just created and Click the Edit button.
- In the Add Directory Properties window, change the Destination Location to $(install_temp)and the Destination Name to ".", and check the Descend directories option. The dialog should now look like the following image:
This maps the update site directory and all files and subdirectories it contains to the path $(install_temp).
- Click OK.
- Back in the Execute program properties window, deselect all icons and Click Add.
- Navigate to the customized installfeature.bat file and select Open. Click the Edit button and set the Destination Location to $(install_temp). The properties editor should now look like the following image:
- Click OK.
- Now configure the actions to uninstall. Select the Remove tab and type uninstallfeature.bat in the Path field.
- Click the Advanced button and set the fields identically to how they were set for the Install action.
- Copy the following text into a file named uninstallfeature.bat
setlocal enableextensions set WED_HOME=%1 set CUR_DIR=%~dp0 %WED_HOME%\rcp\rcplauncher -application org.eclipse.update.core.standaloneUpdate -nosplash -os win32 -arch x86 -command disable -featureId FEATUREID -version VERSION -to %WED_HOME%/sc/eclipse -rcpLauncherWait -consolelog -data "%CUR_DIR%/data" set rc=%errorlevel% if errorlevel 1 goto :error %WED_HOME%\rcp\rcplauncher -application org.eclipse.update.core.standaloneUpdate -nosplash -os win32 -arch x86 -command uninstall -featureId FEATUREID -version VERSION -to %WED_HOME%/sc/eclipse -rcpLauncherWait -consolelog -data "%CUR_DIR%/data" set rc=%errorlevel% if errorlevel 1 goto :error :error rem endlocal implied by end of script exit %rc%
Again customize with FEATUREID and VERSION and the install site location. Duplicate the text if more than one feature must be uninstalled.
Note that since features must be disabled before they can be uninstalled, this script performs two actions for each feature.
- Select Add in the Execute Program Properties editor and map the customized uninstallfeature.bat file to the directory $(install_temp).
- Click OK.
- Save in Sofware Package Block format as in the previous example. Test using the wdinstsp command on the development client to install into a previously installed WED4WL. Note that the install will succeed whether the client is running or not, but installed features will only become accessible after the client is restarted.
- Test the uninstall action on the development client using the Software Distribution disconnected command
wdrmvsp "Sales Center^1.0" Note: If the features are removed while the client is running the results are unpredictable, so uninstalls should normally be scheduled when the client is not in use.
The Tivoli Desktop can now be used to import the Software Distribution packages built in this section into a Profile Manager in the management region, and activities scheduled to distribute them to endpoints. There are other variations on the distribution mechanics where, for example, the corequisite files are served from a file server instead of being copied to each endpoint, or the package is served from a repeater depot.
Related concepts
Other software distribution systems
Deploy customizations to the IBM Sales Center