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


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 begin

Stop all message flows in the integration server. For more details, see Stopping an integration server.

About this task

If you want to remove a shared library, you must first remove any resources that reference that shared library.

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

Removing a deployed object with the IBM Integration Toolkit

About this task

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

Procedure

  1. In the Integration Nodes 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 node, and a synchronous response is sent back.

Removing a deployed object with 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.
    On distributed systems:
    mqsideploy -i ipAddress -p port -e integrationServerName
    -d file1.cmf:file2.cmf:file3.dictionary:file4.xml

    The -i (IP address) and -p (port) parameters represent the connection details for the queue manager that is associated with the integration node. If you have created the integration node on the computer on which you run this command, you can specify the integration node name instead, as in the following example:

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

    If you have a .broker file that contains the connection details for a local or remote 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.cmf:file3.dictionary:file4.xml
    where integrationNodeFileName is the path and file name of the .broker file.
    On z/OS®:
    /f integrationNodeName,dp e=integrationServerName d=file1.cmf:file2.cmf:file3.dictionary:file4.xml

    where integrationNodeName is the name of the integration node.

    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. When you remove a message flow or message set, the -m parameter is ignored.

Results

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

Removing a deployed object with 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 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 2015-05-28 20:51:08