ROS Client msi packaging

ROS Client msi deployment

(revised 11/01/05)

The ROS client msi file is sent to EDS for ITG/IOT testing upon notification from Release
Manager. This process only applies to final version (1.3) of the client installer. If any spot
builds are made to final version (i.e. 1.3.1) this process needs to be applied to spot build.

This documentation is intended for people who have a working knowledge of Windows
operating systems.

The msi installer has four major steps applied to it. First, the msi is copied from the build
area and renamed to a format consistent with the requirements of the ITG. Second, there
are several data tables within the msi that need manual editing/updating. Third, it is
published to the ‘dropbox’ ftp location. Fourth, it is placed on the deployment web site.

These procedures take place on server 90.136.104.5 which is a Windows server. Remote
access software and administrator login are required. Contact appropriate people to
install/configure remote access software and obtain administrator login password.

Client msi installer is created in the build directory structure and copied to the level build
directory H:\IIS WEBS\PC GUI WEB\releases\level. For this documentation, the format of
the original msi name is ROSInstaller-2005.0B.Feb.Client.1.3.msi. Where examples are
shown using this name or variations of it, substitute the actual name of the build you are
working with.

Copy and Rename

Copy installer msi from 'level' location:

H:\IIS WEBS\PC GUI WEB\releases\level\ROSInstaller-2005.0B.Feb.Client.1.3.msi
to C:\ROS_Client and rename msi to format of ROS_Client_20050BFeb_1_3.msi
C:\ROS_Client is setup as ROS_Client_for_ITG shortcut on desktop.

Edit msi Tables

Perform all edits for this process on msi located in C:\ROS_Client directory.
Right Mouse Click (RMC) current installer msi and select “Edit with Orca”.

Select Property table and add rows for ROOTDRIVE and ALLUSERS.
Row for ROOTDRIVE should have Property of ROOTDRIVE, Value of C:\.
Row for ALLUSERS should have Property of ALLUSERS, Value of 1. (number one).
Edit property items starting with VSD (6 items) and remove any reference to obtaining
products or downloading products. Messages should just state message, not include
prompts to download other software items.

Select _Validation table. Select TOOLS from top menu, Select VALIDATE command.
On Validation Output, select Go. When validation is complete, select OK box on
Validations Complete screen. Close Validation Output screen.

Expand error description area at bottom of _Validation table screen. Sort description area
by Type if needed. Error messages of the following formats and ICE number are normal
and expected. Error messages other than these need to be resolved. Quantity of Error
messages will change from build to build, but only these three errors are normal. Not all
errors messages will occur.

ICE08 Component: C_ {guid number} has a duplicate GUID: {guid number}

ICE30 The target file '{filename} is installed in '[TARGETDIR}\’ by two different

components on an LFN system: C_...

ICE61 Upgrade.ActionProperty PREVIOUSVERSIONINSTALLED may be used in only

one record of the Upgrade table.

Close Windows Installer 2.0 Table Editor and SAVE changes to the msi.

Publish to Dropbox

Current msi is now ready to be published to the drop box. Open WinFTP.exe shortcut on
desktop and select ITG profile. Profile is configured to connect to dropbox location and
login. Select msi is left pane (local directory) and copy to remote directory using arrow icon
pointing to right pane. Refresh right pane to confirm msi has been copied.
Should problems occur, login information is: username/password = ispgbu/ispgB5BU.
Select remote directory of ‘ROS for Wholesale’. Select local directory C:\ROS_Client.

Send notice that msi (specify msi name) has been published to the dropbox and is in 'ROS
for Wholesale' folder. Ipage notification goes to Release Manager, Kim Megahee and
Chester Harris. Email notification goes to packaging.requests@bellsouth.com, Rick
Milliken, Dean Debois, Kenneth L. Wright and Chester Harris.

Deployment

Notification will be received some time after shipping msi installer to dropbox that msi is
ready for deployment. This notice is sometimes two weeks after msi is published to
dropbox. When notice is received, login to 90.136.104.5 server using remote access
software and Administrator user account. Copy msi from C:\ROS_Client to H:\IIS
WEBS\PC GUI Deployment Web\releases\level. From a separate PC, open Internet
Explorer and enter URL http://90.136.104.5:8090. Go to LEVEL section and select msi for
download. Download and start installation process to confirm msi is accessible. Cancel
installation at first screen. Notify by reply email or reply ipage, depending on notification
method, that msi is on deployment web site.