Skip Headers
Oracle® Communications Order and Service Management Installation Guide
Release 7.2.2

E35412-06
Go to Documentation Home
Home
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

13 Uninstalling OSM

This chapter provides information about uninstalling the Oracle Communications Order and Service Management (OSM) product.

The OSM Uninstaller removes only the OSM program files. It does not remove the database schemas or the OSM application from the WebLogic server.

To completely remove OSM, you must perform the following steps:

  1. Back up all customized configuration files.

  2. Remove the OSM application from the WebLogic server. See the Oracle WebLogic documentation for more information.

    Note:

    Because the OSM installation scripts do not update the operating system's registry settings, you do not need to perform any manual clean-up operations on the registry.
  3. Remove the OSM database schemas. See the Oracle Database documentation for more information.

  4. Uninstall OSM components by running the OSM Uninstaller. See "Uninstalling OSM Components". If uninstalling in silent mode, see "Performing a Silent Uninstall".

  5. Remove the directory where OSM is installed.

Uninstalling OSM Components

The OSM Uninstaller removes the OSM program files. It does not uninstall any database or WebLogic domain information. This includes elements created by the OSM Installer. These must be uninstalled manually.

Note:

The uninstall operation does not have any dependency on the WebLogic server and the Oracle Database. You do not have to keep the servers in Running mode to uninstalling OSM.

To remove the OSM program files:

  1. Do one of the following:

    • On Linux:

      Run OSMUninstallLinux.bin.

    • On Solaris:

      Run OSMUninstallSparc.bin.

    • On AIX:

      Run OSMUninstallAix.bin.

    • On Windows:

      From the Start menu, select Programs, then Oracle Communications, then select Order and Service Management Uninstaller.

  2. In the Uninstaller's welcome dialog box, click Next.

    The Product Uninstallation dialog box is displayed.

  3. Do one of the following:

    • To remove all of the OSM files, click Next, which opens the confirmation dialog box.

    • To remove specific components, deselect the components you want to leave installed and click Next, which opens the confirmation dialog box.

  4. Click Next, which starts the uninstallation process.

    The uninstaller removes the OSM program files from the workstation.

OSM Uninstall: Additional Tasks

In addition to running the OSM software uninstall procedure, you need to perform additional tasks to completely remove the OSM software and related software elements.

You should perform an environment-specific analysis on each OSM system to create a customized list of uninstallation tasks. For example, you may want to remove customizations that you added after OSM was installed. These customizations might be part of a clustered environment or a multiproduct installation. You may also need to remove additional dependent WebLogic resources, such as messaging bridges, JMS Queues, automation plug-ins, and user accounts.

The specific steps for uninstalling all related elements will vary based on your particular environment.

The following procedure specifies the additional uninstallation tasks for a minimal OSM installation in a single server environment:

  1. Close the OSM applications running in the system, including:

    • Oracle Communications Design Studio

    • XML Import/Export application

    • XML API agents

  2. Stop the OSM WebLogic applications.

  3. Log in to the WebLogic Administration console.

  4. Click Deployments, and stop the OSM application oms and the cartridge management Web services application cartridge_management_ws.

    Note:

    Do not stop cartridge_management_ws in a suite or multiproduct environment because other applications may be dependent on it.
  5. Navigate to Services, then Messaging, then JMS Modules, and delete oms_jms_module.

  6. Navigate to Services, then Messaging, then JMS Servers, and delete oms_jms_server.

  7. Navigate to Services, then JDBC, then Data Sources, and delete oms_pool.

  8. Navigate to Services, then File T3, and delete oms_remote_file_system.

  9. Navigate to Security Realms, then myrealm, then Users and Groups, then Users and delete the following OSM users:

    • oms-automation

    • oms-internal

    • sceadmin

    • admin

      Note:

      admin is the default OSM Administrator user. However, you may have specified a different name for the default Administrator user during the OSM installation. In this case, you should remove the custom Administrator user.
  10. Navigate to Security Realms, then myrealm, then Users and Groups, then Groups, and delete the following OSM user groups:

    • Cartridge_Management_WebService

    • OMS_cache_manager

    • OMS_client

    • OMS_designer

    • OMS_log_manager

    • OMS_user_assigner

    • OMS_workgroup_manager

    • OMS_ws_api

    • OMS_xml_api

    • OSM_automation

    • OSM_user_manager

      Note:

      Do not delete Cartridge_Management_WebService in a suite or multiproduct environment because other applications may be dependent on it.
  11. Click Deployments, and delete the OSM application oms and the cartridge management Web services application cartridge_management_ws.

    Note:

    Do not delete cartridge_management_ws in a suite or multiproduct environment because other applications may be dependent on it.
  12. Delete the folder generated by the OSM WebLogic server during its installation.

  13. Close the WebLogic server.

  14. Navigate to the Domain directory, and delete the Attachments folder.

  15. Run the OSM uninstaller. See "Uninstalling OSM Components".

Performing a Silent Uninstall

Before you run a silent uninstall, you must configure the installOptions.txt file to reflect which OSM features you want to uninstall. You can use the sample file located in the OSM_home/SDK/Samples/installation directory and modify it accordingly.

Each feature in the installOptions.txt file has a selection state of either true or false to control whether that feature is to be uninstalled. The following sample shows the values for the Database Schema feature.

############################################################################
#
# "Database Schema" Feature
#
# The selection state of the "Database Schema" feature. Legal values are:
# 
#    true  - Indicates that the feature is selected for installation
#    false - Indicates that the feature is not selected for installation
# 
# For example, to select "Database Schema" for installation, use
# 
#    -P featureds.active=true
#
### -P featureds.active=<value>


#######
#
#    true  - Indicates that the feature is selected for uninstallation
#    false - Indicates that the feature is not selected for uninstallation
#
### -P featureds.activeForUninstall=<value>

############################################################################

To run a silent uninstall:

  1. Navigate to the directory where the installation executables are placed.

  2. Do one of the following:

    • On Oracle Linux and Red Hat Enterprise Linux, execute the command: OSMUninstallLinux.bin -silent -options installOptions.txt

    • On Oracle Solaris, execute the command: OSMUninstallSparc.bin -silent -options installOptions.txt

    • On IBM AIX, execute the command: OSMUninstallAix.bin -silent -options installOptions.txt

    • On Windows, execute the command: OSMUninstall.exe -silent -options installOptions.txt