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

Chapter 2: Using Progress Sonic Installer
Creating a Runtime Infrastructure
A runtime infrastructure is comprised of one or more Domain Managers, distributed
installations of runtime components, administration tools, and clients to support
applications.
A runtime infrastructure includes:
● Sonic Domain Manager — The central point of component provisioning, upgrades,
and updates. The license keys entered for a Domain Manager enable it to configure
and manage distributed components. They also enable the Domain Manager to deploy
a component by simply adding the component’s configuration to a management
container. Upgrades and updates simply added to the Directory Service store
propagate to the appropriate components dynamically.
● Sonic Administration Tools — The toolset for all the products can be on every
administrator’s system so that they can authenticate and connect on multiple domains.
● Through a separate installer, the Sonic Container Launcher provides all the local
resources on distributed systems that enable them to setup and launch containers. The
Container Launcher also can setup a management container configuration during
installation, and then launch the container to record its configuration in the domain’s
Directory Service. You can choose to add an activation daemon and a host manager,
and—on Windows— a Windows Service.
Important JMS Clients — Java applications running on remote systems require a Java runtime
environment and Sonic client libraries. While JMS client was an installation type in Sonic
releases before 8.5, in practice, SonicMQ applications are typically packaged with their
supporting Sonic client libraries and, often, the appropriate JVM. Every installation type
created by the Sonic Installer includes the complete SonicMQ client libraries.
86 Progress Sonic Installation and Upgrade Guide 8.5