Disable an application 

You might decide to disable an application temporarily for maintenance or if, for example, you are deploying the product and this application is not yet ready for use.


Before you begin

Only perform this task if you want to disable an application temporarily.

Note: Do not disable applications that are used by all of the other applications, such as the News or Search applications.


Procedure

  1. Open the Integrated Solutions Console of the WAS that is hosting the application.

  2. Expand Applications -> Application Types, and then select WebSphere enterprise applications.

  3. Click the name of the application that you want to disable.

  4. Click Target specific application status.

  5. Select the check box next to the cluster name, and then click Disable Auto Start.

  6. Click Save to save your changes.

  7. Click Apply, and then click OK.

  8. Start the wsadmin client from the following directory of the system on which you installed the deployment manager:

      app_server_root>\profiles\<dm_profile_root>\bin

      Note: You must start the client from this directory or subsequent commands that you try to run will not execute properly. See Starting the wsadmin client for more details.

  9. Remove the link to the application from the navigation bar by editing the IBM Connections configuration file.

    1. Enter the following command to access the IBM Connections configuration file: execfile("connectionsConfig.py")

        If prompted to specify a service to connect to, type 1 to pick the first node in the list. Most commands can run on any node. If the command writes or reads information to or from a file using a local file path, pick the node where the file is stored. This information is not used by the wsadmin client when you are making configuration changes.

    2. Check out the IBM Connections configuration files:

        LCConfigService.checkOutConfig("<working_directory>","<cell_name>")

        where:

        • <working_directory> is the temporary working directory to which the configuration XML and XSD files are copied and are stored while you make changes to them. Use forward slashes to separate directories in the file path, even if you are using the Microsoft Windows operating system.

            AIX and Linux only: The directory must grant write permissions or the command does not run successfully.

        • <cell_name> is the name of the WAS cell hosting the IBM Connections application. This argument is case-sensitive, so type it with care. To obtain the cell name:print AdminControl.getCell()

        For example:

        • AIX or Linux:LCConfigService.checkOutConfig("/opt/temp","foo01Cell01")

        • Microsoft Windows:LCConfigService.checkOutConfig("c:/temp","foo01Cell01")

  10. To see a list of the properties and their current settings, use the following command:

      LCConfigService.showConfig()

  11. Enter the following commands:

      LCConfigService.updateConfig("<application_name>.enabled", "false")
      LCConfigService.updateConfig("<application_name>.ssl.enabled", 
       "false")

      where <application_name> is the name of the application that you are disabling.

  12. After making changes, check the configuration files back in and do so during the same wsadmin session in which you checked them out for the changes to take effect. See Apply common configuration property changes for information about how to save and apply your changes.

  13. Stop the WAS clusters, and then restart the WAS clusters.


Parent topic

Administer applications


Related tasks


Starting the wsadmin client
Apply common configuration property changes
Change common configuration property values


   

 

});