Deleting deployed resources

Use the IBM® App Connect Enterprise Toolkit or the web user interface to remove deployed integration solution resources such as applications and libraries from an integration server.

About this task

You can delete applications, libraries, integration services, and message flows from an integration server by using any of the following methods:

In IBM App Connect Enterprise 12, you can delete deployed applications, shared libraries, and policy projects. To enable compatibility with earlier versions of IBM App Connect Enterprise, you can delete individual resources but only from the default application, and only by using the mqsideploy command or the IBM Integration API.

You cannot delete shared libraries if they are being referenced by any of the other resources that are deployed on the integration server.

You cannot delete policy projects that contain nondynamic policies. The changing or deletion of policies within a policy project is only supported for certain types of policy. To delete a policy project, which contains nondynamic policies, it is necessary to delete all deployed resources from the integration server and then redeploy all resources. For more information about policy properties, see Policy properties.

Deleting a deployed resource by using the web user interface

Procedure

  1. Start the IBM App Connect Enterprise web user interface, as described in Accessing the web user interface.
    Your servers (integration servers), message flows, and other resources are displayed.
  2. Select the resource that you want to delete and click Delete.
    You cannot delete a message flow from a deployed application or library by using the IBM App Connect Enterprise web user interface. You must delete the flow from the toolkit application project or library and then redeploy the application or library. For more information, see Deleting a message flow or subflow.

Results

A message is sent to the integration server to delete the selected resource.

Removing a deployed object by using the IBM App Connect Enterprise Toolkit

About this task

To remove an object from an integration server by using the IBM App Connect Enterprise Toolkit, complete the following steps.

Procedure

  1. In the Integration Explorer view, right-click the object that you want to remove.
  2. Click Delete, then OK to confirm.
    You cannot delete a message flow from a deployed application or library by using the IBM App Connect Enterprise Toolkit. You must delete the flow from the toolkit application project or library and then redeploy the application or library. For more information, see Deleting a message flow or subflow.

Results

The request is sent to the integration server, and a synchronous response is sent back.

Removing a deployed object by using the mqsideploy command

About this task

To remove an object from an integration server by using the mqsideploy command, complete the following steps.

Procedure

  1. Open a command window that is configured for your environment.
  2. Enter the appropriate command for your operating system and configuration, by using the following examples as a guide. 
    mqsideploy -i ipAddress -p port -e integrationServerName
-d file1.cmf:file2.bar:file3.dictionary:file4.xml

    mqsideploy --admin-host ipAddress --admin-port port -e integrationServerName
-d file1.cmf:file2.bar:file3.dictionary:file4.xml

    The -i (IP address) and -p (port) parameters represent the connection details for an independent integration server or an integration node. If you want to run this command against an integration node on the same computer, you can specify the integration node name instead, as in the following example:

    mqsideploy integrationNodeName -e integrationServerName
-d file1.cmf:file2.bar:file3.dictionary:file4.xml

    If you have a .broker file that contains the connection details for an independent integration server or integration node, you can specify this file by using the -n parameter, as in the following example:

    mqsideploy -n integrationNodeFileName -e integrationServerName
-d file1.cmf:file2.bar:file3.dictionary:file4.xml
    where integrationNodeFileName is the path and file name of the .broker file.

    The -d parameter is a colon-separated list of files that you want to remove from the named integration server. When you run the command, the deployed objects (file1.cmf, file2.bar, file3.dictionary, file4.xml) are removed from the specified integration server.

    Optionally, specify the -m parameter to remove all currently deployed message flows and message sets from the integration server as part of the deployment. If you do not set -m, the contents of the BAR file are deployed in addition to what is already deployed to the integration server. Any deployed objects with the same name as an item inside the BAR file are replaced by the version inside the BAR file. When you remove a message flow or message set, the -m parameter is ignored.

    For more information about alternative long names for parameters, and for more information about the command, see mqsideploy command.

Results

The command reports when responses are received from the integration node. If the command completes successfully, a zero return code (0) is displayed.

Removing a deployed object by using the IBM Integration API

About this task

To remove deployed objects from an integration server, get a handle to the relevant ExecutionGroupProxy object, then run the deleteDeployedObjectsByName method. Use the following code as an example.
import com.ibm.broker.config.proxy.*;

public class DeleteDeployedObjects {
  public static void main(String[] args) {
    BrokerConnectionParameters bcp =
            new IntegrationNodeConnectionParameters
                      ("localhost", 4414);
    try {
      BrokerProxy b =
            BrokerProxy.getInstance(bcp);
      ExecutionGroupProxy e =
            b.getExecutionGroupByName("default");
      e.deleteDeployedObjectsByName(
            new String[] { "file1.msgflow",
                           "file2.msgflow",
                           "file3.xsd",
                           "file4.msgflow" }, 0);
    }
    catch (ConfigManagerProxyException e) {
      e.printStackTrace();
    }
  }
}

What to do next

If you remove one or more message flows, you can now remove the resource files that are associated with those message flows; for example, JAR files.