WebSphere brand IBM WebSphere IP Multimedia Subsystem Connector, Version 6.2

Uninstalling IBM WebSphere Diameter Enabler Component from the WebSphere Application Server

Uninstalling the IBM® WebSphere® Diameter Enabler Component will remove the IBM WebSphere Diameter Enabler Component and associated Web services.

About this task
You will need the following file for this uninstallation task:
  • DiameterChannelUninstall.py (in was_root/installableApps/ImsConnector/install)
    Note: was_root is the installation root directory for WebSphere Application Server Network Deployment. By default, this directory is:
    • AIX /usr/IBM/WebSphere/AppServer
    • Linux /opt/IBM/WebSphere/AppServer
    • Solaris /opt/IBM/WebSphere/AppServer

Complete the following steps to uninstall Diameter Enabler from the WebSphere Application Server:

  1. Start the application server. In case of a clustered installation (Network Deployment environment), start the deployment manager, all node agents, and then all application servers.
  2. Uninstall all of the Diameter Enabler applications (Rf, Ro, and Sh Web services) from the administrative console:
    1. Open the WebSphere Application Server administrative console.
    2. In the navigation panel, click Applications > Enterprise Application.
    3. Select all of the Diameter Web service applications (for example, DHADiameterRfWebServiceEAR, DHADiameterRoWebServiceEAR, or DHADiameterShWebServiceEAR).
    4. Click Uninstall.
    5. Click OK.
    6. Click Save.
  3. Uninstall the Diameter base from the wsadmin command line.
    Important: Enter the following parameters on a single line.
    Note: was_profile_root is the directory for a WebSphere Application Server Network Deployment profile called profile_name. By default, this directory is:
    • AIX /usr/IBM/WebSphere/AppServer/profiles/profile_name
    • Linux /opt/IBM/WebSphere/AppServer/profiles/profile_name
    • Solaris /opt/IBM/WebSphere/AppServer/profiles/profile_name

    For example, AppSrv01 in a standalone environment, or Dmgr01 in a clustered environment.

    • AIXLinuxSolaris was_profile_root/bin/wsadmin.sh -username user_name -password password -f script_path/DiameterChannelUninstall.py cell_name node_name server_name install_type
    Where:
    • user_name represents your WebSphere Application Server user ID. This parameter is required if security is enabled.
    • password represents the password associated with your user_name. This parameter is required if security is enabled.
    • script_path represents the path to DiameterChannelUninstall.py
    • cell_name represents the name of cell where the server is installed
    • node_name represents the name of node where the server is installed
    • server_name represents the name of the application server where Diameter Enabler base is installed (first cluster member in case of a clustered installation)
    • install_type represents the environment in which the script is running, use standalone for a standalone environment, and cluster for a clustered environment
    For example:
    wsadmin.sh -f ./DiameterChannelUninstall.py west107Node01Cell west107Node01 server1 standalone
  4. For a clustered installation only, remove the cluster.
    Note: Removing the cluster deletes the cluster and any servers associated with it. Make sure you do not have applications other than Diameter Web services applications installed on the cluster.
    1. In the navigation panel, click Servers > Cluster.
    2. Select Diameter cluster.
    3. Click Delete.
    4. Click Save.
  5. Remove the Diameter Enabler data source:
    1. In the navigation panel, click Resources > JDBC > Data Sources.
    2. Select Diameter DataSource.
    3. Click Delete.
    4. Click Save.
  6. Remove the authentication definition for the Diameter Enabler data source:
    1. In the navigation panel, click Security > Secure Administration, Applications, and infrastructure > Java Authentication and Authorization service > J2C Authentication Data.
    2. Select the database alias (<nodename>/diameter_alias).
    3. Click Delete.
    4. Click Save.
  7. DB2 Remove definitions for the DB2® database variables created during the installation process:
    1. In the navigation panel, click Environment > WebSphere Variables.
    2. Perform one of the following:
      • On a standalone installation or on a clustered installation which modified this variable at the cell level, select the cell scope and click the DB2UNIVERSAL_JDBC_DRIVER_PATH variable.
      • On a clustered installation which modified this variable at each node level, select the node scope and click the DB2UNIVERSAL_JDBC_DRIVER_PATH variable.
    3. Clear the value field for this variable; then, click OK.
    4. On a clustered installation which modified this variable at each node level, repeat b. and c. for each node.
    5. Click Save.
  8. Oracle Remove definitions for the Oracle database variables created during the installation process:
    1. In the navigation panel, click Environment > WebSphere Variables.
    2. Perform one of the following:
      • On a standalone installation or on a clustered installation which modified this variable at the cell level, select the cell scope and click the ORACLE_JDBC_DRIVER_PATH variable.
      • On a clustered installation which modified this variable at each node level, select the node scope and click the ORACLE_JDBC_DRIVER_PATH variable.
    3. Clear the value field for this variable; then, click OK.
    4. On a clustered installation which modified this variable at each node level, repeat b. and c. for each node.
    5. Click Save.
  9. Stop the application server. In case of clustered installation (Network Deployment environment), stop all application servers, all node agents and then deployment manager.
  10. Remove the file com.ibm.ws.diameter_6.2.0.jar from the plugins directory:
    • AIXLinuxSolaris was_root/plugins
    Note: In case of a clustered installation, repeat this step for each node in the cluster.
  11. Remove the Diameter properties files (Diameter_Rf.properties, Diameter_Ro.properties, and Diameter_Sh.properties) from the properties directory:
    • AIXLinuxSolaris was_profile_root/properties
    Note: was_profile_root is the directory for a WebSphere Application Server Network Deployment profile called profile_name. By default, this directory is:
    • AIX /usr/IBM/WebSphere/AppServer/profiles/profile_name
    • Linux /opt/IBM/WebSphere/AppServer/profiles/profile_name
    • Solaris /opt/IBM/WebSphere/AppServer/profiles/profile_name

    For example, AppSrv01 in a standalone environment, or Custom01 as the name of a federated node profile in a clustered environment.

    Note: In case of a clustered installation, repeat this step for each node in the cluster.
  12. Remove was_root/installableApps/ImsConnector.
    Note: In case of a clustered installation, repeat this step for each node in the cluster.
  13. Remove was_root/lib/ext/DHAIMSConnectorTAI.jar. In case of a clustered installation, repeat this step for each node in the cluster.
    Note: For more information, refer to the Trust Association Interceptor Information Center.
  14. Remove version information:
    • was_root/properties/version/IMSConnector.component
    • was_root/properties/version/IMSConnector.product
    • was_root/properties/version/nif/componentmaps/componentmap.ImsConnector.core.xml
    Note: In case of a clustered installation, repeat this step for each node in the cluster.
  15. Clear the contents of DB2 database tables whenever you reinstall the WebSphere IMS™ Connector. Optionally, you can also perform this task when uninstalling the WebSphere IMS Connector. See database specific references for information on clearing database tables, removing tables and removing a database.
  16. Clear the contents of Oracle database tables whenever you reinstall the WebSphere IMS Connector. Optionally, you can also perform this task when uninstalling the WebSphere IMS Connector. See database specific references for information on clearing database tables, removing tables and removing a database.



Terms of use
(C) Copyright IBM Corporation 2009. All Rights Reserved.