IBM App Connect Enterprise, Version 11.0.0.2 Operating Systems: Windows, Linux


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:
Note: You cannot delete message flows or other resources that are contained in an integration service, application, or library. You cannot delete shared libraries if they are being referenced by any of the other resources that are deployed on the integration server.

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.

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.

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, 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 the standalone integration server or the 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 a standalone 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 (d= on z/OS®) 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 (m= on z/OS) 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 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, it returns zero (0).


be10030_.htm | Last updated 2018-11-02 14:46:23