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

Chapter 4: Setting Up Containers
2. Change to the appropriate version’s directory, such as, 8.5.0.392
3. Change to the container_setup directory
4. Enter setup.sh with the appropriate parameters in the form:
setup.sh -c propertiesFile -u user -p userPassword -e encryptionPwd
The container is setup.
Running Setup Again for a Container
Once you have setup and launched a container, the domain will maintain the Launcher
versioning, and update the caches and container.ini file automatically. If you performed
significant changes that would impact a container’s container.ini (such as the
authentication credentials) when the container was not running, run setup again on the
same host through a host manager or a setup file generated since the changes occurred.
Note Do not edit a Container’s container.ini File — A container.ini file is not intended for
edits. The naming conventions and sequence of parameters are not intended for user
interface. There are very few circumstances where a minor edit might be required; in such
cases, documentation will guide you to the specific changes needed.
Windows Services in a Container’s Working Directory
Every container working directory includes a winservice script to assist in managing the
container as a Windows Services. The preset name of the Windows service is Sonic
container_name Service.
◆ To use a container’s winservice script:
1. Open a console window in a container’s working directory.
2. Enter winservice and one of the following parameters:
■ /install
■ /start
■ /wait_for_stop
■ /stop
■ /remove
The requested Windows Service action occurs.
132 Progress Sonic Installation and Upgrade Guide 8.5