Using the Java IBM Integration API - IIBv10 deprecated classes

IBM Knowledge Center

Learn how to use the ACEv11 Java IBM Integration API's deprecated com.ibm.broker.config.proxy.* classes (requires v11.0.0.5 or higher). This tutorial demonstrates how existing applications for adminstering IIBv10 can easily be updated to administer ACEv11.

Import projects

When you click Import, two projects will be created in your workspace: An application named ExampleApplication and a Java project name ExampleIIBV10AdminProgram.

ExampleApplication provides a single message flow named ExampleFlow. This message flow is not important - it simply provides an HTTPInput node wired to an HTTPReply. The only purpose for providing this flow is so that when the Java program is executed, there are some deployed artifacts to report on.

Once imported using the link on the right, the application ExampleApplication is ready to be deployed and tested. To deploy, you can use a provided BAR file, as described on the Prepare tab.

Create an integration node owned server, deploy the message flow and inspect the Java program

Prepare the scenario by executing the following steps:

  1. Create an integration node by starting an App Connect Enterprise command console and executing the following commands:
    mqsicreatebroker TESTNODE
    mqsistart TESTNODE
    mqsicreateexecutiongroup TESTNODE -e server
  2. Back in the Toolkit, drag and drop deploy the provided BAR file named DeployApplication.bar which you will find inside the ExampleApplication application.
  3. Inspect the provided java application. Switch to the Java perspective and then open ExampleIIBV10AdminProgram.java which you will find inside the Java project named ExampleIIBV10AdminProgram. If required by your runtime environment, update the values of the two variables, nodeHostName and nodePortNumber which enable the Java program to communicate with your integration node. Have a look through the rest of the Java. You will see that many of the methods are displayed with strike-through warnings symbolising the fact that these methods are deprecated in ACEv11. Despite the deprecated methods, note that the same Java can run against both IIBv10 and ACEv11, making migration of ancilliary applications very easy.
  4. Check the Java Build Path for the provided java application. Right-click the project ExampleIIBV10AdminProgram, select Properties and choose the Java Build Path. You will see that the project has been configured to expect several jar files to be available from the default installation location on Windows at C:\Program Files\IBM\ACE\11.0.0.5. If you are using a different platform or install location you will need to use the Remove and Add External JARs buttons to satisfy the required dependencies. The precise versions of these files may change in future, but at ACEv11.0.0.5 the required libraries are as follows:
    • From C:\Program Files\IBM\ACE\11.0.0.5\common\classes: IntegrationAPI.jar
    • From C:\Program Files\IBM\ACE\11.0.0.5\common\jackson\lib: jackson-annotations-2.9.8.jar, jackson-core-2.9.8.jar, jackson-databind-2.9.8.jar, jackson-dataformat-yaml-2.9.8.jar, snakeyaml-1.23.jar
    • From C:\Program Files\IBM\ACE\11.0.0.5\common\jnr\lib: asm-7.0.jar, jffi-1.2.19.jar, jffi-1.2.19-native.jar, jnr-a64asm-1.0.0.jar, jnr-constants-0.9.12.jar, jnr-enxio-0.21.jar, jnr-ffi-2.1.10.jar, jnr-posix-3.0.50.jar, jnr-unixsocket-0.23.jar, jnr-x86asm-1.0.2.jar

Run the provided Java application from within Toolkit and view the Console to test the tutorial scenario

  1. Open ExampleIIBV10AdminProgram.java.
    • Right-click ExampleIIBV10AdminProgram.java and select Run As > Java application.
    • The Console view should open at the base of the screen and as the Java application runs, you should see logging like this:
      (12/08/19 10:38:45) ==========================================================================================
      (12/08/19 10:38:45) This v11 admin program shows the use of com.ibm.broker.config.proxy.* classes (DEPRECATED)
      (12/08/19 10:38:45) ==========================================================================================
      (12/08/19 10:38:47) Connecting to host localhost and port 4414
      (12/08/19 10:38:47) TESTNODE is running
      (12/08/19 10:38:47) TESTNODE,server is running
      (12/08/19 10:38:47) TESTNODE,server,ExampleApplication is running
      (12/08/19 10:38:47) TESTNODE,server,ExampleApplication,ExampleFlow is running

This tutorial has shown how to use the ACEv11 Java IBM Integration API's com.ibm.broker.config.proxy.* classes. These classes are supported but deprecated in ACEv11, but this tutorial has shown how an administrative Java application for IIBv10 can easily be moved to run against ACEv11.

Find out more