Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 20 Next »

On This Page:

Note: ServiceGANTT for Web Start is a value-added module available within ServiceManager.

 

ServiceGANTT for Web Start is provided as a compressed (ZIP) archive and also as an MSI installer for Windows platforms.

Pre-requisites

ServiceGANTT for Web Start must be installed with a compatible version of ServiceManager.  The pre-requisites for ServiceManager are listed in ServiceManager Pre-Requisites

A predefined port must be set up as the client connection port within the ServicePower database (see ServiceOptimizer Install Guide)

  • In order for client workstations to run ServiceGANTT for Web Start Java Runtime Environment version 1.6 must be installed. This can be installed automatically the first time ServiceGANTT for Web Start is launched if required.
  • Client workstations should also be set up to have a default executable for .jnlp files of javaws.exe.

Components

ServiceGANTT for Web Start is a module of ServiceManager, which allows the standard ServiceGANTT application to be downloaded and installed on a workstation using Sun’s Java Web Start technology. ServiceGANTT for Web Start uses the ServiceManager application server to host the files required for ServiceGANTT to be launched.

Integrating with ServiceManager

Whenever a ServiceManager module is installed, upgraded or uninstalled, the appropriate process must be followed as described in the following sections. The ServiceManager application will then need to be redeployed and restarted twice to ensure that the correct ServiceManager modules are fully installed and initialised.

Installers and Licensing

ServiceGANTT for Web Start may only be installed into an existing ServiceManager installation - see ServiceManager Install Guide for instructions on this if not yet covered.

Deploying ServiceGANTT for Web Start

The directory structure opposite shows how this installs on the target machine.  This structure is identical regardless of the installation method used (MSI, or ZIP). 

The top directory must be the ServiceManager <modules> directory.
<MODULES_DIR>/SERVICEGantt/Gantt
		SERVICEGantt.jnlp
<MODULES_DIR>/SERVICEGantt/Gantt/images
		GanttClient_380x285.png
		GanttSplash.gif
		ganttsystem.gif
<MODULES_DIR>/SERVICEGantt/Gantt/jars
		*.jar
		version.xml
<MODULES_DIR>/SERVICEGantt/Gantt/jre
		jinstall-6-windows-i586.cab
<MODULES_DIR>/SERVICEGantt/WEB-INF/lib
		sp-ganttjnlpservlet.jar

Windows MSI Deployment

When the MSI installer is run it will automatically detect the location of the ServiceManager modules directory by reading a value from the registry.

HKEY_LOCAL_MACHINE\SOFTWARE\ServicePower\

SERVICEManager\svm_modules

If the key doesn’t exist the installer will display an ‘Installer Information’ message and exist from the installer.  ServiceManager will need to be reinstalled to establish the modules directory correctly before re-running the ServiceGANTT for Web Start installer. 

When the modules registry key is found the installer displays a welcome screen and invites the user to press next to continue. On doing this the screen shows the destination folder settings which are automatically populated with the location of the ServiceManager modules directory - the user cannot change these settings.  Selecting the next button will ask for confirmation before installing the required files.

 

 

 

ZIP-Based Manual Deployment

The ServiceGANTT for Web Start release bundle is a compressed zip archive that contains all the files required to install the ServiceGANTT for Web Start into ServiceManager.  The release bundle should be used to install ServiceGANTT for Web Start where MSI deployment is not appropriate, e.g. non-windows based platforms.

To install ServiceGANTT for Web Start the zip file should be extracted into the ServiceManager modules directory, preserving the directory hierarchy of the zip file.

Once the installation has finished, ServiceManager’s application server needs to be restarted so that the ServiceGANTT for Web Start files are picked up by ServiceManager.  In order for the new files to be properly detected by ServiceManager the application will need to be redeployed and restarted twice as described in Section 5.3..

 

Uninstalling and Upgrading ServiceGANTT for Web Start

To upgrade an older version of ServiceGANTT for Web Start when a new version is released, the older version needs to be uninstalled first. Having done this, then the new version may be installed exactly as described above. The client workstations will automatically pickup the new version of ServiceGANTT the next time ServiceGANTT is launched from within ServiceManager.

Remember

After uninstalling, OR after installing the new version, ServiceManager’s application server needs to be restarted so that the change to configuration is recognised. The application will need to be redeployed and restarted twice.

To uninstall...

Windows MSI Deployment

ZIP-Based Manual Deployment

The un-installation of ServiceGANTT for Web Start can be launched from the Add/Remove programs option from the control panel.

The un-install removes the ServiceGANTT for Web Start installed files from the ServiceManager modules directory

To uninstall ServiceGANTT for Web Start remove the ServiceGANTT directory and all its contents from the ServiceManager modules directory.

ServiceGANTT for Web Start – Client first run.

Once the ServiceGANTT for Web Start module has successfully been installed a new menu tab will be visible in the menu list to the left of the screen. The user is able to navigate to the Download & Launch ServiceGANTT page.  Selecting this may result in one of a number of different messages, depending upon whether Java is installed on the client workstation.  If a version of Java cannot be found on the client workstation the user has the option to install Java and then launch ServiceGANTT.  The screen shots below show the Java installation process and the loading of ServiceGANTT via Web Start. 

Dependent upon network capabilities, the whole Java and application installation takes less than 3 minutes the first time the application is launched, less than 10 seconds on subsequent launches. 

ServiceManager displaying the SERVICEGantt Download and Launch Page - Java is not installed. 

 

Java Runtime Installation

 

Downloading the SERVICEGantt Application.  This only occurs the first time the application is launched or there are any application updates.

 

  • No labels