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 Installing and configuring 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 need to run the uninstallSdoRepository.jacl script.
This script continues when it finds unexpected results, so it can
clean up a broken or partial installation.
Note: Run the script from within QShell.
The script is provided in the app_server_root/bin directory, where app_server_root is the root directory for the installation of IBM® WebSphere® Application Server. 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 app_server_root/profiles/profile_name/bin directory then specify the following path to the script:wsadmin -f app_server_root/bin/uninstallSdoRepository.jacl
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
standalone server, the
-createDb flag
tells the install command to create a default (
Cloudscape Version 10.1.x (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
Cloudscape Version 10.1.x (Derby) database:
wsadmin -f installSdoRepository.jacl -createDb
wsadmin -f uninstallSdoRepository.jacl -removeDb
Note:
- If you did not use -createDb on the installer,
because you had already configured a Cloudscape Version 10.1.x (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 Cloudscape Version 10.1.x (Derby) database.
If you are certain that you want to delete the database, you can do
so manually. A Cloudscape Version 10.1.x (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 install fails stating that the SdoRepDb directory
already exists.
For installation or removal of the SDO repository
application from a
standalone server:
wsadmin -f installSdoRepository.jacl
wsadmin -f uninstallSdoRepository.jacl
For installation or
removal of the SDO repository application in a network deployment
environment, for a deployment manager or a server that is not part
of a cluster:
wsadmin -f installSdoRepository.jacl node_name server_name
wsadmin -f uninstallSdoRepository.jacl node_name server_name
For installation or
removal of the SDO repository application in a network deployment
environment, for a cluster:
wsadmin -f installSdoRepository.jacl -cluster cluster_name
wsadmin -f uninstallSdoRepository.jacl -cluster cluster_name