Uninstalling Document Format Conversion Application

Silently uninstall the Document Format Conversion Application from the Windows™ or Linux system.

About this task

To perform a silent uninstallation, complete the following steps:

Procedure

  • For a single server or the first node in a Conversion cluster, begin from the Conversion node itself, not from the Deployment Manager node:
    1. Log in to the system where you installed IBM® Conversion service, with the user who runs the server or cluster node process.
    2. Open a command prompt and change it to the conversion_install_root\installer directory, for example, on Windows, it is C:\IBM\IBMConversion\installer, and on Linux, it is opt/IBM/IBMConversion/installer.
    3. Run the uninstallation script: uninstall.bat(Windows) or uninstall.sh (Linux).
      If you do not specify the WebSphere® Application Server administrative user ID and password in the command line, you are prompted to enter them.
  • For each additional cluster node server:
    1. Log in to the system where you installed the Conversion server, with the user who runs the cluster node process.
    2. Open a command prompt and change to the conversion_install_root\installer directory, for example, on Windows, it is C:\IBM\IBMConversion\installer, and on Linux, it is opt/IBM/IBMConversion/installer.
    3. Run the uninstallation script: uninstall_node.bat(Windows) or uninstall_node.sh(Linux).
      If you do not specify the WebSphere® Application Server administrative user ID and password in the command line, you are prompted to enter them.
      Note: If you run uninstallation scripts from the original installer folder, you must first configure the cfg.properties file.
    Note:
    1. You can set options to uninstallation scripts:
      • -wasadminID {name}: Specifies the user name of WebSphere® Application Server administrator. Prompts the user to enter the name during uninstallation if it is not specified.
      • -wasadminPW {password}: Specifies the password of WebSphere® Application Server administrator. Prompts the user to enter the password during uninstallation if it is not specified.
    2. If the process fails and reports errors, remove the JAR files that the Conversion server copied to the WebSphere® Application Server plug-in folder. JAR files that are related to the Conversion server have names such as com.ibm.symphony.conversion.jarname.
      Note: If other processes (for example, Deployment Manager or another profile's server) occupy these JAR files, you see errors such as The process cannot access the file because it is being used by another process. The failure does not affect other applications in WebSphere® Application Server. However, to avoid further conflicts, it is best that you manually remove these JAR files, after you stop all WebSphere® Application Servers.
    3. After you uninstall, if soffice.exe and soffice.bin are still running, stop them manually.
    4. After you uninstall, if nodeagent or WebSphere® Application Server cannot start normally, run WAS_INSTALLPATH_Windows(for example, C:\IBM\WebSphere\AppServer)\bin\osgiCfgInit.bat on Windows, and opt/IBM/WebSphere/AppServer/bin/osgiCfgInit.sh on Linux) to clean the bundle cache, and then start nodeagent or WebSphere® Application Server again.

Results

When you are finished uninstalling, check the conversion_uninstall.log file for errors, and repeat this task if necessary. The log file is in the ConversionCluster_INSTALLPATH directory, for example, C:\IBM\IBMConversion)\logs on Windows and opt/IBM/IBMConversion/logs on Linux.