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

More documents

Recommendations

Info

Chapter 5: Using Response Files with Installers Creating Scripted Launcher Installations for Host Managers Centralized installation provides many strategies that remove the burden of distributed installation and upgrade of widely dispersed machines: ● The Domain Manager is the central repository of licensed components, provisioning remote machines with required libraries without any intervention at remote sites. ● The Sonic Deployment Manager acts on the Domain Manager system to map configurations in its models to machines in the distributed topology through Host Manager objects running on the remote machines. ● The Sonic Launcher provides easy installation of Sonic container resources and can setup a container that connects to its assigned domain. That last step can still be error prone. Until the container is given a name that will be unique in the domain and the configuration is set up and running, remote administrators cannot perform any maintenance functions. The following techniques describe how, on Windows systems, a simple script and a properties file installed on a machine can set up Sonic resources, configure a container that uses the host’s name, start it, and connect it to its assigned domain, silently, with no user input whatsoever. Consider the following scenario for this example: 1. One or more Domain Managers are installed at various locations in the enterprise. 2. In some domains, the containers are grouped on management lines, perhaps as regions. 3. The network identity of machines that will cooperate in a domain are defined with unique names by the systems and network teams. 4. The optimal setup on a distributed machine would be a container that contains a Host Manager, and that is setup as a Windows Service. The container would always be running and would be accessible to administrators for deploying additional containers and assets on the remote system. The following properties file was created as a response file from a Container Launcher installation, then edited to: ● Specify a standard installation location and to use the installed JRE. ● Specify connection information for the assigned domain. ● Stub the container name and path, and the Windows Service name. 158 Progress Sonic Installation and Upgrade Guide 8.5
Sonic Container Launcher Parameters and Procedures The properties file is as shown using the defaults and the Domain Manager’s dmhostname: Code Sample 9. Properties for a silent launcher installation with a container #Choose Install Folder #--------------------- INSTALL_LOCATION=C:\\Program Files\\Progress\\SonicLauncher #Configure Container #------------------- CONFIGURE_CONTAINER=true #Domain Manager Connection Properties #------------------------------------ DOMAIN_NAME=Domain1 CONNECTION_URLS=tcp://dmhostname:2506 SECURITY_USER=Administrator SECURITY_PASSWORD=Administrator #The name of the container to configure #-------------------------------------- CONTAINER_NAME=scripted #The path for the configured container #------------------------------------- CONTAINER_PATH=/scripted/scripted #Determine if the container configuration should be created if it does not exist #----------------------------------------------------------------------------- CREATE_CONTAINER_CONFIG=true #The path for the host manager #----------------------------- HOST_MANAGER_PATH=/Framework Components/HOST MANAGER #Should the host manager be configured? #-------------------------------------- HOST_MANAGER_ENABLED=true #The name of the Windows Service #------------------------------- WINDOWS_SERVICE_NAME=scripted #Should the Windows Service be created? #-------------------------------------- WINDOWS_SERVICE_ENABLED=true #Chosen JVM Home directory #------------------------- CHOSEN_JVM_HOME=C:\\Program Files\\Progress\\SonicLauncher\\jre #Launch Container Process #------------------------ LAUNCH_CONTAINER=true #------------------------ ACCEPT_LICENSE_AGREEMENT=true INI_ENCRYPT_PASSWORD=secret Progress Sonic Installation and Upgrade Guide 8.5 159
Page 1 and 2:
® ® PROGRESS® SONIC® Installati
Page 3 and 4:
the redistribution, if any, must in
Page 5 and 6:
the relevant code modules. All Righ
Page 7 and 8:
OF USE, DATA, OR PROFITS; OR BUSINE
Page 9:
products derived from this software
Page 12 and 13:
Contents Chapter 2: Using Progress
Page 14 and 15:
Contents Chapter 7: Upgrading Versi
Page 16 and 17:
Contents 16 Progress Sonic Installa
Page 18 and 19:
Preface About This Guide This guide
Page 20 and 21:
Preface Progress Sonic Documentatio
Page 22 and 23:
Preface ● Progress SonicMQ C++ Cl
Page 24 and 25:
Preface 24 Progress Sonic Installat
Page 26 and 27:
Chapter 1: Overview of Installation
Page 28 and 29:
Page 30 and 31:
Page 32 and 33:
Page 34 and 35:
Page 36 and 37:
Page 38 and 39:
Page 40 and 41:
Page 42 and 43:
Page 44 and 45:
Page 46 and 47:
Page 48 and 49:
Page 50 and 51:
Page 52 and 53:
Page 54 and 55:
Page 56 and 57:
Page 58 and 59:
Page 60 and 61:
Chapter 2: Using Progress Sonic Ins
Page 62 and 63:
Page 64 and 65:
Page 66 and 67:
Page 68 and 69:
Page 70 and 71:
Page 72 and 73:
Page 74 and 75:
Page 76 and 77:
Page 78 and 79:
Page 80 and 81:
Page 82 and 83:
Page 84 and 85:
Page 86 and 87:
Page 88 and 89:
Page 90 and 91:
Page 92 and 93:
Page 94 and 95:
Page 96 and 97:
Page 98 and 99:
Page 100 and 101:
Page 102 and 103:
Page 104 and 105:
Page 106 and 107:
Page 108 and 109: Chapter 3: Using Progress Sonic Lau
Page 122 and 123: Chapter 4: Setting Up Containers Ab
Page 124 and 125: Chapter 4: Setting Up Containers Us
Page 126 and 127: Chapter 4: Setting Up Containers Co
Page 128 and 129: Chapter 4: Setting Up Containers Pr
Page 130 and 131: Chapter 4: Setting Up Containers No
Page 132 and 133: Chapter 4: Setting Up Containers 2.
Page 134 and 135: Chapter 4: Setting Up Containers 13
Page 136 and 137: Chapter 5: Using Response Files wit
Page 164 and 165: Chapter 6: Upgrade Planning Introdu
Page 166 and 167: Chapter 6: Upgrade Planning Version
Page 168 and 169: Chapter 6: Upgrade Planning Compati
Page 170 and 171: Chapter 6: Upgrade Planning Compati
Page 172 and 173: Chapter 6: Upgrade Planning 172 Pro
Page 174 and 175: Chapter 7: Upgrading Version 8 Doma
Page 188 and 189: Chapter 8: Upgrading from 7.5 or 7.
Page 208 and 209:
Chapter 8: Upgrading from 7.5 or 7.
Page 210 and 211:
Page 212 and 213:
Page 214 and 215:
Page 216 and 217:
Page 218 and 219:
Page 220 and 221:
Page 222 and 223:
Chapter 9: Updating Sonic Installat
Page 224 and 225:
Chapter 9: Updating Sonic Installat
Page 226 and 227:
Chapter 10: Uninstalling Progress S
Page 228 and 229:
Appendix A: Characters in Progress
Page 230 and 231:
Appendix A: Characters in Progress
Page 232:
Appendix B: Troubleshooting Install
show all

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

Create successful ePaper yourself

Delete template?

Save as template?