Previous     Contents     Index     DocHome     Next     
iPlanet Messaging Server 5.0 Installation Guide



Appendix C       Un-Installing the Software


This appendix contains instructions for un-installing the Messaging Server software. It includes the following sections:



Why Un-Install?

You might remove the Messaging Server software from a machine if you need to free up some disk space, or if you want to re-install the product.

Note In order to remove Messaging Server, you must be logged in as root. All procedures in this chapter, unless otherwise noted, require that you access the system as root.





Uninstalling Messaging Server Components



This section describes how to remove an existing instance of the Messaging Server from a machine.

Note The uninstall program will not attempt to remove any Message Store or Message Access components; if you want to remove these, you must do so manually.

Additionally, the uninstall program does not remove any high availability components. See Un-Installing High Availability for instructions on removing the high availability components.



In the directory in which you installed the Messaging Server files, you will find the uninstall program. To run uninstall, use the following steps:

  1. Login as root.

  2. Halt the Messaging Server instance.

    To halt the server instance, run the stop-msg utility. This utility is stored in the server-root/msg-instance directory. For example:

    cd /usr/iplanet/server5/msg-budgie
    ./stop-msg

    Status messages are displayed as the various daemons and services are stopped.

  3. Change to the server-root directory.

  4. Halt the Administration Server instance.

    If you have an Administration Server running, run the stop-admin utility to halt this server instance. This utility is stored in the server-root directory. For example:

    cd /usr/iplanet/server5
    ./stop-admin

    Note Do not manually stop the Directory Server; the uninstall program requires the Directory Server to be up and running and it will handle the shutting down of the Directory Server.



  5. Run the uninstall program:

    ./uninstall

    Note The screens you see here may vary depending on which components you have installed. This example assumes you have all components installed.



  6. Select which components you want to remove:

    The following are the SuiteSpot components currently installed on your machine:

    Components with a number in () contain additional subcomponents which you can select using subsequent screens.

       1. Netscape Server Products Core Components (3)
       2. Netscape Directory Suite (2)
       3. Administration Services (2)
       4. iPlanet Messaging Applications (5)

    Select the components you wish to uninstall (default: all) [All]:

  7. Select which Serer Core Product components you want to remove:

    The following are the Netscape Server Products Core Components components currently installed on your machine:

    Components with a number in () contain additional subcomponents which you can select using subsequent screens.

       1. Netscape Server Products Core Components
       2. Netscape Core Java classes
       3. Java Runtime Environment

    Specify the components you wish to uninstall [1, 2, 3]:

  8. Select which Directory Suite components you want to remove.

    The following are the Netscape Directory Suite components currently installed on your machine:

    Components with a number in () contain additional subcomponents which you can select using subsequent screens.

       1. Netscape Directory Server
       2. Netscape Directory Server Console

    Specify the components you wish to uninstall [1, 2]:

  9. Select which Administration Services components you want to remove:

    The following are the Administration Services components currently installed on your machine:

    Components with a number in () contain additional subcomponents which you can select using subsequent screens.

       1. Netscape Administration Server
       2. Administration Server Console

    Specify the components you wish to uninstall [1, 2]:

  10. Select which iPlanet Messaging Applications components you want to remove.

    The following are the iPlanet Messaging Suite components currently installed on your machine:

    Components with a number in () contain additional subcomponents which you can select using subsequent screens.

       1. iPlanet Message Store and Message Access
       2. iPlanet Internet Message Transport Agent
       3. iPlanet Messaging Multiplexor
       4. High Availability for iPlanet Messaging Server
       5. iPlanet Delegated Administrator Command Line Utilities

    Specify the components you wish to uninstall [1, 2, 5]:

    Caution

    If you installed any high availability components, you must manually remove them (See Un-Installing High Availability.). Although it is presented as an option, the automatic un-install of high availability components is not supported at this time; do not select this option.



  11. Enter the login ID and password of the Configuration Administrator:

    Enter the User ID or Distinguished Name of the administrator who is authorized to access the Configuration Directory at

       ldap://budgie.siroe.com:389/

    Configuration Admin ID or DN: [admin]:

    At this point, the uninstall program should begin removing the various components you specified from your system.

Your un-install is now complete.

In some cases, uninstall might have been unable to remove some of your installation files. Please check for any remaining files and remove them manually.


Note The uninstall script does not reinstate the original sendmail link. You must manually restore this link if you want receive mail on the server via Solaris sendmail.



Additionally, if you want to remove any Message Store and Message Access components not removed by uninstall, you may now do so.



Un-Installing High Availability



To uninstall the high availability components:

  1. Perform the normal uninstall procedures as described in the previous section ("Uninstalling Messaging Server Components").

  2. Remove the instance entry from the /etc/msgregistry.inf file if multiple instances are installed; otherwise, remove the /etc/msgregistry.inf file on both nodes.

At this point, uninstall instructions differ depending on whether you installed Veritas Cluster Server or SunCluster. Read whichever one of the following subsections is appropriate.


Un-Installing High Availability for Veritas Cluster Server

To un-install the high availability components for Veritas Cluster Server:

  1. Remove the dirsync entries from cron job table on both nodes.

  2. Delete all of the Veritas Cluster Server resources created during installation.

  3. Stop the Veritas Cluster Server and remove following files on both nodes if no more instances exist:

    /etc/VRTSvcs/conf/config/MsgSrvTypes.cf
    /opt/VRTSvcs/bin/MsgSrv/online
    /opt/VRTSvcs/bin/MsgSrv/offline
    /opt/VRTSvcs/bin/MsgSrv/clean
    /opt/VRTSvcs/bin/MsgSrv/monitor
    /opt/VRTSvcs/bin/MsgSrv/sub.pl

  4. Remove the Messaging Server entries from the /etc/VRTSvcs/conf/config/main.cf file on both nodes.


Un-Installing High Availability for SunCluster

To un-install the high availability components for SunCluster:

  1. Run the following command:

    hareg -u ims50

  2. Remove the following:

    /opt/SUNWcluster/ha/msg/ims_common
    /opt/SUNWcluster/ha/msg/ims_fm_probe
    /opt/SUNWcluster/ha/msg/ims_start_net
    /opt/SUNWcluster/ha/msg/ims_stop_net

  3. Remove the ims_ha.cnf file from your shared disk mount point directory (for example, /mnt if your shared disk is mounted under the /mnt directory.


Previous     Contents     Index     DocHome     Next     
Copyright © 2000 Sun Microsystems, Inc. Some preexisting portions Copyright © 2000 Netscape Communications Corp. All rights reserved.

Last Updated October 05, 2000