10.02.2013 Views

Progress Sonic 8.5 Installation and Upgrade Guide - Product ...

Progress Sonic 8.5 Installation and Upgrade Guide - Product ...

Progress Sonic 8.5 Installation and Upgrade Guide - Product ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 5: Using Response Files with Installers<br />

Creating Scripted Launcher <strong>Installation</strong>s for Host Managers<br />

Centralized installation provides many strategies that remove the burden of distributed<br />

installation <strong>and</strong> upgrade of widely dispersed machines:<br />

● The Domain Manager is the central repository of licensed components, provisioning<br />

remote machines with required libraries without any intervention at remote sites.<br />

● The <strong>Sonic</strong> Deployment Manager acts on the Domain Manager system to map<br />

configurations in its models to machines in the distributed topology through Host<br />

Manager objects running on the remote machines.<br />

● The <strong>Sonic</strong> Launcher provides easy installation of <strong>Sonic</strong> container resources <strong>and</strong> can<br />

setup a container that connects to its assigned domain.<br />

That last step can still be error prone. Until the container is given a name that will be<br />

unique in the domain <strong>and</strong> the configuration is set up <strong>and</strong> running, remote administrators<br />

cannot perform any maintenance functions.<br />

The following techniques describe how, on Windows systems, a simple script <strong>and</strong> a<br />

properties file installed on a machine can set up <strong>Sonic</strong> resources, configure a container<br />

that uses the host’s name, start it, <strong>and</strong> connect it to its assigned domain, silently, with no<br />

user input whatsoever.<br />

Consider the following scenario for this example:<br />

1. One or more Domain Managers are installed at various locations in the enterprise.<br />

2. In some domains, the containers are grouped on management lines, perhaps as<br />

regions.<br />

3. The network identity of machines that will cooperate in a domain are defined with<br />

unique names by the systems <strong>and</strong> network teams.<br />

4. The optimal setup on a distributed machine would be a container that contains a Host<br />

Manager, <strong>and</strong> that is setup as a Windows Service. The container would always be<br />

running <strong>and</strong> would be accessible to administrators for deploying additional containers<br />

<strong>and</strong> assets on the remote system.<br />

The following properties file was created as a response file from a Container Launcher<br />

installation, then edited to:<br />

● Specify a st<strong>and</strong>ard installation location <strong>and</strong> to use the installed JRE.<br />

● Specify connection information for the assigned domain.<br />

● Stub the container name <strong>and</strong> path, <strong>and</strong> the Windows Service name.<br />

158 <strong>Progress</strong> <strong>Sonic</strong> <strong>Installation</strong> <strong>and</strong> <strong>Upgrade</strong> <strong>Guide</strong> <strong>8.5</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!