IBM Integration Bus, Version 9.0.0.8 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Removing a deployed object from an integration server

You might want to remove deployed objects from an integration server if, for example, you want to rename them.

Before you start:

Stop all message flows in the integration server. For more details, see Stopping an integration server using the IBM Integration Toolkit or IBM Integration Explorer.

You can remove deployed objects from an integration server in the following ways:

Using the IBM Integration Explorer
Using the mqsideploy command
Using the CMP

Using the IBM Integration Toolkit

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

In the Integration Nodes view, right-click the object that you want to remove.
Click Delete, then OK to confirm.

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

Using the IBM Integration Explorer

To remove an object from an integration server by using the IBM Integration Explorer, complete the following steps.

In the Navigator view, expand the broker and integration server with which you want to work.
Right-click the object that you want to remove.
Click Delete, then OK to confirm.

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

Using the mqsideploy command

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

Open a command window that is configured for your environment.
Enter the appropriate command for your operating system and configuration, using the following examples as a guide.
On distributed systems:
```
mqsideploy -i ipAddress -p port -q qmgr –e egroup
            –d file1.cmf:file2.cmf:file3.dictionary:file4.xml
```
The -i (IP address), -p (port), and -q (queue manager) parameters represent the connection details for the queue manager associated with the broker. If you have created the broker on the computer on which you run this command, you can specify the broker name instead.
```
mqsideploy -n brokerName -e egroup
-d file1.cmf:file2.cmf:file3.dictionary:file4.xml
```
On z/OS®:
```
/f MQ01BRK1,dp e=egroup d=file1.cmf:file2.cmf:file3.dictionary:file4.xml
```
where MQ01BRK1 is the name of the broker.
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.cmf, 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. For a remove message flow or message set operation, the -m parameter is ignored.

The command reports when responses are received from the broker. If the command completes successfully, it returns zero (0).

Using the CMP

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 MQBrokerConnectionParameters
                      ("localhost", 1414, "QM1");
    try {
      BrokerProxy b =
            BrokerProxy.getInstance(bcp);
      ExecutionGroupProxy e =
            b.getExecutionGroupByName("default");
      e.deleteDeployedObjectsByName(
            new String[] { "file1.cmf",
                           "file2.cmf",
                           "file3.dictionary",
                           "file4.xml" }, 0);
    }
    catch (ConfigManagerProxyException e) {
      e.printStackTrace();
    }
  }
}

Next:

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

af03950_.htm |

Last updated Friday, 21 July 2017