Summary
How to create an offline connection to a Sonic domain with the Sonic Management Console
Question/Problem Description
How to create an offline connection to a Sonic domain with the Sonic Management Console
How can I connect to the Sonic domain with the Sonic Management Console if the Domain Manager will not start?
How to configure a Sonic installation when the management container is down
How do I connect to a Sonic domain that is offline?
Environment
SonicMQ All Supported Operating Systems
Resolution
Ensure that the management container is not running (even in a 'limbo' state with the broker down). Shut down or kill the process if necessary.
If using a version prior to 7.5, remove the 'lock' file from the <Domain>/data/_MFSystem directory if it exists.
In 7.6, look for a 'lock' file in the <Domain>/data.odb/ directory and remove it if it exists.
Start the Sonic Management Console.
Fill in the Create Connection parameters as follows:
Connection Name : enter a name of your choice, e.g. 'MyDomain (offline)'
Domain Name : the name of the Sonic domain
Connection URL : enter the path to the ds.xml file. For example, instead of the usual management broker URL (e.g. tcp://localhost:2506), the field might contain: C:\SonicMQ\ds.xml
Username : not required - can be left blank
Password : must be left blank, unless the domain storage has been encrypted using the PBE tool (pbetool), in which case the encryption password must be entered - note this only works with SonicMQ 7.x and later, in earlier versions the domain storage must be unencrypted manually using pbetool prior to creating the offline connection
Uncheck the 'Default Connection' checkbox
Click 'OK' to complete the connection.
Before restarting the management container, close the Sonic Management Console connection so that it releases its lock on the domain.
After the broker has been restarted, subsequent connections with the Sonic Management Console must use the broker URL , not the ds.xml file.
This solution must not be used for normal management connections/configuration when the management broker is running.
<supportagent>
Disclaimer
The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information. Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.
Internal Comments
SonicMQ Category: Sonic Management ConsoleInternal Notes
If it is not possible to run the Sonic Management Console on the machine where the domain storage is located, see Solution S559, "How to create an offline Sonic Management Console connection to remote domain storage" .References to Written Documentation:
SonicMQ Configuration and Management Guide, "Configuring Framework Components", "Directory Service", "Connecting Off Line" </supportagent>