Uninstalling OSM

14 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:

Back up all customized configuration files.
Remove the OSM application from the WebLogic server. See "OSM Uninstall: Additional Tasks" for minimal instructions, and see the Oracle WebLogic Server 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.
Remove the OSM database schemas. See Oracle Database documentation for more information.
Uninstall OSM components by running the OSM Uninstaller. See "Uninstalling OSM Components." If uninstalling using silent uninstall, see "Performing a Silent Uninstall."
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:

To run the OSM Uninstaller using the procedure in this section, you must have the Info-ZIP project utility installed. If it is not already installed on your system, you can download it from the following location:

http://sourceforge.net/projects/infozip/

If you do not install the Info-ZIP project utility, you must modify the OSM uninstall script to use a different unzip utility.

Always run the Uninstaller to remove the OSM program files. If you simply delete the program files without running the Uninstaller, you may receive errors in future OSM installations.

Note:

The uninstallation 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 uninstall OSM.

To uninstall the OSM program files:

Go to the installation directory, OSM_home/_uninst.
Do one of the following:
- On Oracle Linux or Red Hat Enterprise Linux, Solaris, or IBM AIX, execute the command:
```
OSMUninstall.sh
```
- On Microsoft Windows, execute the command:
```
OSMUninstall.bat
```
  Or, from the Start menu, select Programs, then Oracle Communications, then select Order and Service Management Uninstaller.
In the Uninstaller's welcome dialog box, click Next.

The Product Uninstallation dialog box is displayed.
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.
Click Next, which starts the uninstallation process.

The uninstaller removes the OSM program files from the workstation.
Do one of the following:
- Click Yes to remove an existing file.
- Click Yes to All to remove all existing files.
- Click No to keep an existing file.
- Click No to All to keep all existing files.
Click Finish.

OSM Uninstall: Additional Tasks

In addition to running the OSM software uninstall procedure, you must 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:

Close the OSM applications running in the system, including:
- Oracle Communications Design Studio
- XML Import/Export application
- XML API agents
Stop the OSM WebLogic applications.
Log in to the WebLogic Administration console.
Click Deployments, and stop the OSM application oms, the cartridge management web services application cartridge_management_ws, and the shared Java EE library comms-platform-webapp.

Note:

Do not stop cartridge_management_ws and comms-platform-webapp in a suite or multiproduct environment because other applications may be dependent on them.
Click the OSM application oms, then select the Configuration tab, then the Workload tab, and delete all of the application-scoped work managers.
Navigate to Services, then Messaging, then JMS Modules, and delete oms_jms_module.
Navigate to Services, then Messaging, then JMS Servers, and delete oms_jms_server.
Navigate to Services, then JDBC, then Data Sources, and delete oms_pool.
Navigate to Services, then File T3, and delete oms_remote_file_system.
Navigate to Security Realms, then myrealm, then Users and Groups, then Users and delete the following OSM users:
- oms-automation
- oms-internal
- deployAdmin
- admin
  
  Note:
  
  admin is the default OSM Administrator user and deployAdmin is the default Design Studio administrator user. If you specified different names during the OSM installation, remove the custom users.
Navigate to Security Realms, then myrealm, then Users and Groups, then Groups, and delete the following OSM user groups if present:
- Cartridge_Management_WebService
  
  Note:
  
  Do not delete Cartridge_Management_WebService in a suite or multiproduct environment because other applications may be dependent on it.
- OMS_cache_manager
- OMS_client
- OMS_log_manager
- OMS_user_assigner
- OMS_workgroup_manager
- OMS_ws_api
- OMS_ws_diag
- OMS_xml_api
- OSM_automation
- osmRestApiGroup
- osmEntityClientGroup
Click Deployments, and delete the OSM application oms, the cartridge management web services application cartridge_management_ws, and the shared Java EE library comms-platform-webapp.

Note:

Do not delete cartridge_management_ws and comms-platform-webapp in a suite or multiproduct environment because other applications may be dependent on them.
Delete the directory generated by the OSM WebLogic server during its installation.
Close the WebLogic server.
Navigate to the Domain directory, and delete the Attachments directory.

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:

Navigate to the directory where the installation executables are placed.

Do one of the following:

On Linux, execute the command:

OSMUninstallLinux.bin -silent -options installOptions.txt

On Solaris, execute the command:

OSMUninstallSparc.bin -silent -options installOptions.txt

On AIX, execute the command:

OSMUninstallAix.bin -silent -options installOptions.txt

On Windows, execute the command:

OSMUninstall.exe -silent -options installOptions.txt