Sun Java Enterprise System 5 Installation Guide for Microsoft Windows

Uninstallation Behavior of Message Queue

Table 7–5 Uninstallation Details for Message Queue

Topic 

Details 

Configuration data 

Instance-specific configuration data, user repository and access control file remains after uninstallation, and can be reused upon subsequent reinstallation. 

Other installations this component requires 

Directory Server (optional) 

Products requiring this installation 

Application Server (must reside on same host as Message Queue) 

Pre-uninstallation tasks 

  • Stop any running brokers. You will be prompted for user name (admin) and password:imqcmd shutdown bkr [-b hostName:port]

  • If you are not planning to reinstall Message Queue and therefore want to delete dynamic data, the flat-file user repository, and the access control file associated with each broker instance, remove this data by using the following command. imqbrokerd -name instanceName -remove instance

  • If you upgrade Message Queue by using the Message Queue upgrade script, make a note of your process. The upgrade script does not write installation information to the Java ES registry.

Post-uninstallation tasks 

If you are not planning to reinstall Message Queue, use the commands in the Java ES component documentation to clean up your system.