12.11.2014 Views

web server - Borland Technical Publications

web server - Borland Technical Publications

web server - Borland Technical Publications

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.

Sonic<br />

Creating Clustered JMS Service for Sonic<br />

Use the Sonic Wizard to create a Managed Sonic Messaging Service. For details on<br />

the specifics of your Sonic Messaging Service, refer to the Sonic documentation.<br />

For clustering Sonic, you have two choices:<br />

■<br />

If you have already used the Sonic Wizard to create a managed Sonic service,<br />

check the box and choose the appropriate instance from the drop down list.<br />

■<br />

You can create a new managed Sonic service by clicking the Launch Sonic Wizard<br />

button. When you've finished, click Refresh and select your new Sonic service from<br />

the drop-down list.<br />

Enabling security for Sonic<br />

To enable and disable security for Sonic, you must ensure db.ini file is updated before<br />

initialization of the database. There are two levels at which security must be applied,<br />

the backend database and the Sonic Broker. Use the Management Console to<br />

configure Sonic Broker and you can use a dbtool command to take care of the<br />

database. Most importantly, the database and Sonic broker must be in sync.<br />

1 Start the Sonic Broker. To do so, right-click on it in the left pane and select Start<br />

from the dropdown menu.<br />

2 Start the Sonic Management Console by selecting Tools->Sonic Management<br />

Console and establish a connection to the <strong>server</strong>'s domain.<br />

3 On the Configure tab, right-click on the Sonic broker that is being security enabled<br />

and choose Properties.<br />

4 Under the General tab of the 'Edit Broker Properties', check Security box. Set<br />

appropriate values for Authorization Domain and Authorization Policy properties,<br />

and click OK to persist the changes.<br />

5 Shut down the Sonic Management Console.<br />

6 Stop the Sonic JMS Broker. To do so, right-click on it in the left pane and select<br />

Stop from the menu.<br />

7 Under the SonicMQ installation root directory, /jms/sonic, edit<br />

database configuration file db.ini. Set property ENABLE_SECURITY to true and click on<br />

the Save button.<br />

8 Open a Command Prompt window and navigate to the /jms/sonic/bin<br />

directory, and issue the command dbtool/r all to reinitialize the database. For<br />

UNIX use the command dbtool -r all<br />

9 The SonicMQ JMS <strong>server</strong> can now be restarted. The Broker will now run with<br />

security enabled. To establish a connection in the Sonic Management console<br />

should now requires user/password authentication.<br />

Disabling security for Sonic<br />

1 Start the secure Sonic JMS Server<br />

2 Start the Sonic Management console and establish a connection to the <strong>server</strong>'s<br />

domain. Use username Administrator and password Administrator.<br />

3 On the Configure tab, right-click on the appropriate Broker and choose Properties.<br />

4 Under the General tab of the Edit Broker Properties, uncheck Security box. This<br />

completes configuration of the Broker and it should now be shutdown.<br />

5 Shutdown the Sonic Management Console.<br />

228 BES Developer’s Guide

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

Saved successfully!

Ooh no, something went wrong!