Uninstalling manually on UNIX™ operating systems

Steps to take when uninstalling IBM Workload Scheduler master domain manager manually on UNIX™ operating systems.

To manually remove an IBM Workload Scheduler master domain manager complete the following steps.

Note: If your RDBMS is based on Oracle, browse to the TWA_DATA_DIR/usr/servers/engineServer/configDropins/overrides path and check in the datasource.xml configuration file the net service name used for your database before uninstalling the master domain manager.

1. Shut down all IBM Workload Scheduler operations and processes

On a system prompt, go to the IBM Workload Scheduler installation path.
Set the environment by running the twa_env.sh command.
Stop the dynamic agent by running the ShutDownLwa command.
Stop the event processor by running the conman stopmon command.
Stop the application server process by running the conman stopappservman command.
Stop netman, conman, and their child processes by running the conman “shut;wait” command.
To verify that the following processes are inactive, run the command ps -ef | grep process_name.
```
netman 
appservman 
java 
mailman 
monman
```

2. Delete the IBM Workload Scheduler files

Delete all the files under the TWS_install_dir directory.

Note: The TWS_install_dir directory is not the IBM Workload Automation directory, as that might also contain a Dynamic Workload Console installation.

3. Drop the IBM Workload Scheduler tables into the RDBMS

On DB2:

Complete the following steps:

From the program menu, open the DB2 command-line processor (CLP)
Look for the database name by running the command:
```
list db directory
```
If you see an entry named your_db_name associated to the IBM Workload Scheduler instance, run the command:
```
drop db your_db_name
```
If you see an entry named your_db_name associated to the IBM Workload Scheduler instance, run the command:
```
uncatalog db your_db_name_DB
```
To see which node is attached to the master domain manager, run the command:
```
list node directory
```
Run the command:
```
uncatalog node your_node
```

If the master domain manager was installed on the DB2 client, perform the same procedure also on the workstation where the master domain manager is installed.

On ORACLE:

Complete the following steps:

Access the Oracle command line.

Run the command:

sqlplus system/password@net_service_name

Delete all the tables related to the IBM Workload Scheduler instance by running the command:
```
drop user ORACLE_TWS_user cascade;
```

4. Delete the IBM Workload Scheduler administrative user that was created at installation time.

5. Delete the IBM Workload Automation and the IBM Workload Scheduler registries

Edit the /etc/TWS/TWSRegistry.dat file.
Delete the lines tagged with TWS_user.
Go to the /etc/TWA directory which contains two files for each IBM Workload Scheduler instance installed.
Look for the properties file that applies to the IBM Workload Scheduler instance to remove.
Delete the properties file and the file with the same filename and extension .ext.
Delete the /etc/init.d/tebetl-tws_cpa_agent_TWS_user directory.

6. Remove the Common Platforms Agent configuration file

Remove the file named /etc/teb/teb_tws_cpa_agent_TWS_user.ini.

7. Remove WebSphere Application Server Liberty

Delete all files located in the IWA_install_dir/wlp directory and the wlp directory itself.

Note: Do not delete the above files and directories if other components are installed and using WebSphere Application Server Liberty, such as the Dynamic Workload Console.