Network Deployment (Distributed operating systems), v8.0 > Reference > Administrator best practices
The SDO repository uninstall script
Use this script to uninstall a Service Data Objects (SDO) repository that was previously installed, or failed to install correctly.
You install the SDO repository application on every server or cluster that you plan to use for one or more of the service integration bus-enabled web services roles as described in Configure the SDO repository.
If the data source already exists, or there has been a previous broken or partial installation of the SDO repository application, the installSdoRepository.jacl script fails to complete and configuration changes are not saved. In these cases, you have to run the uninstallSdoRepository.jacl script. This script continues when it finds unexpected results, so it can clean up a broken or partial installation.
The script is provided in...
WAS_HOME/bin, where WAS_HOME is the root directory for the installation of WAS. If you choose to run the wsadmin scripting client from another directory, specify the full path to the script on the command option. For example to work with a profile other than the default profile, change to the WAS_HOME/profiles/profile_name/bin directory then specify the following path to the script:wsadmin.ext -f WAS_HOME/bin/uninstallSdoRepository.jaclwhere .ext is the file extension .bat for a Windows system, or .sh for a UNIX, Linux or z/OS system.
The SDO repository script install and uninstall pairs
The following are the install and uninstall command pairs, where each uninstall command undoes the action of the related install command. If you attempt to uninstall with a different set of arguments to those previously used with the installSdoRepository.jacl script, you might find that the uninstall does not remove everything or that it displays warnings when it tries to remove non-existent settings.
For configuration of the SDO repository on a stand-alone server, the -createDb flag tells the install command to create a default (Apache Derby) database and configure it for use with this application server. The -removeDb flag tells the uninstall command to remove the database configuration from the application server, but not to delete the Apache Derby database:
wsadmin -f installSdoRepository.jacl -createDb wsadmin -f uninstallSdoRepository.jacl -removeDb
- If you did not use -createDb on the installer, because you had already configured an Apache Derby database for some other purpose, then you should not use the -removeDb flag on the uninstaller.
- To avoid deleting data that you might want to keep, the -removeDb flag does not delete the Apache Derby database. If you are certain to delete the database, you can do so manually. An Apache Derby database is a directory on the file system. The one created by the installer with the -createDb flag is in the PROFILE_ROOT/databases/SdoRepDb directory, where PROFILE_ROOT is the directory in which profile-specific information is stored. If you do not delete the database, and you try to install again with the -createDb flag, the installation process fails stating that the SdoRepDb directory already exists.
For installation or removal of the SDO repository application from a stand-alone server:
wsadmin -f installSdoRepository.jacl wsadmin -f uninstallSdoRepository.jaclFor installation or removal of the SDO repository application in a WAS Network Deployment environment, for a dmgr or a server that is not part of a cluster:
wsadmin -f installSdoRepository.jacl node_name server_namewsadmin -f uninstallSdoRepository.jacl node_name server_name
For installation or removal of the SDO repository application in a WAS Network Deployment environment, for a cluster:
wsadmin -f installSdoRepository.jacl -cluster cluster_name wsadmin -f uninstallSdoRepository.jacl -cluster cluster_name