ISW and Application Server Power Struggle!!!
I'm trying to install Identity Synchronization for Windows on a Solaris 10 machine that is already running Directory Server 5.2 and Application Server 8.2. I get this error message early in the ISW installation process:
"An existing Message Queue Broker, configured as a daemon, has been detected. Identity Synchronization for Windows requires the exclusive use of a Broker configured as a daemon. If you continue, the installer will stop the running Broker, uninstall it as a daemon, and replace it with its own daemon. If this is not acceptable, exit the installer."
If I finish installing ISW, the Application Server will not start, because it seems to require the use of a broker as well. Is there any way to get these two selfish kids to cooperate? Thanks.-G.
[784 byte] By [
GlennG] at [2007-11-26 10:46:49]
# 1
By default, Application Server will manage the starting and stopping of JMS (MQ broker). You can change this behaviour as follows :
Login to the Application Server Admin console
Expand Configuration and click on Java Message Service.
On the right pane, change the Type from LOCAL to REMOTE.
Restart the appserver. Now appserver will start independent of the MQ broker. But note that if any applications deployed on the appserver makes use of the MQ broker, it is your responsibility to start it since the appserver does not manage it any longer.
Hope this is what you are looking for.
Cheers,
Vasanth
# 2
Thank you, Vasanth, this does seem to work. The only application I'm running is Directory Editor, and I find no mention of the message queue in its documentation.Thanks again - you've made me happy today!-G.
