<?xml version="1.0" encoding="UTF-8"?><!--
    (c) Copyright IBM Corporation 2013, 2017.
    (c) Copyright HCL Technologies Ltd. 2018. All Rights Reserved.
    This is licensed under the following license.
    The Eclipse Public 1.0 License (http://www.eclipse.org/legal/epl-v10.html)
    U.S. Government Users Restricted Rights:  Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
--><pluginInfo>
  <!--

  **author name IS required**

  The Author Section is used to give credit to the author of the plugin.
  Name is the only required element/attribute, but feel free to also include your email,
  website  or bio to allow users of your plugin to praise your work, ask questions
  or share their use case to help grow your plugin's functionality.
  -->

  <author name="UrbanCode">
    <organization>UrbanCode</organization>
    <email>info@urbancode.com</email>
    <website>http://urbancode.com</website>
    <bio/>
  </author>

  <!--

  **intergration type IS Required**

  The integration type section identifies where the plugin fits into the process
  excepted types are SCM, Build, Artifact, Automation, Deploy

  For example:

  The plugin pulls Artifacts from an artifact repository during deployment
  the Type would be "Artifact"
  or
  The plugin deploys to a middleware server
  the Type would be "Deploy"
  -->

  <integration type="deploy"/>


  <!--
  **source is NOT required**

  The source section identifies the location of the plugin source code
  For example
  https://github.com/...
  -->
  <!--
  <source url=""/>
  -->
  <!--
  **license type is NOT required**

  If your plugin uses any licensed software please acknowledge it by
  listing the license type below
  -->
  <!--
  <licenses>
    <license type=""/>
  </licenses>
  -->
  <!--
  **tool-description IS required**

  The tool-description section is used to summarize the software
  the plugin was created to integrate with.

  For example:
  Apache Ant is a software tool to automate software processes during the build or
  deployment of an application. Ant uses an propitiatory XML file to define build
  and/or deployment steps(referred to as targets by ant) . The Ant executable is
  called to execute the targets in the build.xml.
  -->

  <tool-description>IBM's integration broker from the WebSphere product family that allows business information to flow between disparate applications across multiple hardware and software platforms.</tool-description>

  <!--
  **related-info is NOT required**

  The releated-info section is used to define links which may be useful to users of the plugin
  but don't fall into the release-notes or tool-description section.

  For example: releated-info can be links to pdf documentation, help videos related to plugin setup or the product's
  website.

  excepted values for type include: PDF, WEBSITE, VIDEO
  -->

  <related-info>
    <link description="Additonal information about WebSphere Message Broker is available here" title="WebSphere Message Broker-CMP" type="WEBSITE" url="http://www-01.ibm.com/software/integration/wbimessagebroker/"/>
  </related-info>

  <!--
  **meta-html in NOT required**

  The meta-html section is used define the meta description and the meta keywords of the plugin page.The meta
  description tag allows you to influence the description of your page in the web crawlers that support the
  tag The meta keywords tag allows   you to provide additional text for crawler-based search engines to index
  along with your body copy.

  If multiple keywords are used they must be comma(,) delimited
  -->

  <meta-html>
    <meta content="" name="description"/>
    <meta content="" name="keywords"/>
  </meta-html>

  <!-- Do not change the release-version, the build process injects it. -->
  <release-version>42.987832</release-version>


  <release-notes>
    <!--
      **release-note IS required**

      The plugin-version name must match the plugin version found in the plugin.xml file

      The release-note should document the changes, improvements, or bug fixes introduced
      with the new plugin version

      The release-note may contain text or reference a file in the plugin zip package

      For example your release note could be:
      Support for was added for version 10.0 for software X
      or
      releaseNotes/release1.html (where release1.html contains html formatted version information)

      To add a new release note add this with a description in it of the changes:
      <release-note plugin-version="5">....</release-note>

      Our automated release process will replace 'LATEST' with the released version.

      If this already exists in the file, then the described changes have not been released yet and
      you should just append to the existing 'LATEST' tag.
      -->

      <release-note plugin-version="5">
Installing this plugin will give you access to the steps listed below. These steps can be used when designing a component process.
      </release-note>
      <release-note plugin-version="6">
Add a new step for deleting Message Flows that match a regular expression. Useful for deploying to shared Execution Groups.
      </release-note>
      <release-note plugin-version="7">
Add channel property for all steps.
      </release-note>
      <release-note plugin-version="8">
Add step for creating execution group if it doesn't exist.
      </release-note>
      <release-note plugin-version="9">
Add step for creating and deleting configurable services.
      </release-note>
      <release-note plugin-version="10">
Fixes APAR PI35342 - compatibility defect with IBM Urbancode Deploy version 6.1.0.4 and later.
      </release-note>
      <release-note plugin-version="11">
Update plugin to allow for IIB v10 Support.
Add step for overriding local bar files.
Provide backwards compatibility between versions 7 through 10 of IIB.
      </release-note>
      <release-note plugin-version="12">
Fixed issue with incremental deployment always being false
      </release-note>
     <release-note plugin-version="13">
Fixed override bar file throwing null pointer, and IIB10 broker connection parameters
      </release-note>
      <release-note plugin-version="14">
Fixes APAR PI55441 could not establish remote connection in IBM integration Bus step 'Create Execution Group'
Fixes APAR PI52693 Null pointer exception when using the Override Bar Properties step
      </release-note>
      <release-note plugin-version="15">
Additional Error Handling for APAR PI54665 timeout in UCD after deploy finished in IIB
Added functionality to specify mqsiprofile script to set user environment per step
Change names of plugin steps to remove "WMB"
      </release-note>
      <release-note plugin-version="16">
Altered 'Create Execution Group' and 'Deploy' steps to allow multiple execution groups
Add step for restarting execution groups.
      </release-note>
      <release-note plugin-version="17">
Added property for setting environment variables to 'Deploy' step
      </release-note>
      <release-note plugin-version="18">
<p>Fixed NullPointerException in Create Or Update Configurable Service step.</p>
      </release-note>
      <release-note plugin-version="19">
Altered 'Create Execution Group' step so that it will wait until execution group has finished generating before finishing.
      </release-note>
    <release-note plugin-version="20">
Support property file encryption.
    </release-note>
    <release-note plugin-version="21">
Fixed APAR 158492 Updated to a synchronous deployment.
Fixed APAR 158710 Removed deprecated method from 'Create Execution Group.'
Fixed APAR 158738 Added the missing property 'executionGroup' to 'Set Execution Group Properties' step.
Changed to only establish a local broker connection if remote connection parameters aren't specified.
    </release-note>
    <release-note plugin-version="22">
Added output property to specify completion code after deployment, added timestamps, and restructured plugin
    </release-note>
    <release-note plugin-version="23">
Fixed APAR PI73557 Set Broker Properties is using a deprecated method which no longer works.
Fixed APAR IT18861 Groovy classpath updated to include quotations.
    </release-note>
    <release-note plugin-version="24">
Fixed APAR PI75953 Set execution group proxy before stopping all message flows.
Changed Update Configurable Service to configure if missing properties should be deleted.
    </release-note>
    <release-note plugin-version="25">
Fixed spacing error in IIBHelper.
Added MQSI Profile and Shell properties to Override Bar Properties step.
Removed manditory quotations to command lines calls.
Error handling to createConfigurableService.
Updated import path in Create, Delete, Start, and Stop Broker steps.
    </release-note>
    <release-note plugin-version="26">
Add or update the hidden timeout property to many steps.
Error catching for the Restart Execution Groups step.
    </release-note>
    <release-note plugin-version="27">
Fixed APAR PI70440 Restart Execution Group step waits until the server has fully stopped before attempting to start.
    </release-note>
    <release-note plugin-version="28">
Encrypt plugin properties.
    </release-note>
    <release-note plugin-version="29">
Fixes APAR PI79634 Additional plugin decryption updates.
    </release-note>
    <release-note plugin-version="30">
Fixes APAR PI81397 Plug-in failing to import libraries.
    </release-note>
	<release-note plugin-version="31">
Fixes APAR PI81623 Deployments failing in IIB 9 and lower.
	</release-note>
    <release-note plugin-version="32">
Provide proper error output when execution group doesn't exist.
Fixes APAR PI80814 The Deploy and Delete Flow using RegEx steps use the timeout instead of DEPLOYRESULT_WAIT_INDEFINITELY.
    </release-note>
    <release-note plugin-version="33">
Change default property values to be consistent across all steps.
    </release-note>
    <release-note plugin-version="34">
Fixes APAR PI82566 Create Execution Group will successfully create an execution group if it does not exist.
    </release-note>
    <release-note plugin-version="35">
RFE 100083 Added functionality to set environment variables from a file in the Deploy step.
Altered the 'Environment Variables' field to allow environment property values to contain commas in the Deploy step.
Commas can no longer be used as delimiters for Environment Variables in the Deploy step.
    </release-note>
    <release-note plugin-version="36">
Renamed Set Broker Properties step to Set Integration Node Properties.
Added the 'Environment Variables' field to allow environment property values to all non-Integration Node step.
    </release-note>
    <release-note plugin-version="37">
RFE 106783 Added the 'Delete Libraries' field to the 'Delete Flows Using RegEx' step to allow omitting libraries.
    </release-note>
    <release-note plugin-version="38">
RFE 113408 Added the 'Does Execution Group Exist" step to enable better logic for execution group creation and deployment.
    </release-note>
    <release-note plugin-version="39">
Fixes APAR PI90752 Sourcing an environment properties file now uses the default JVM character encoding.
    </release-note>
    <release-note plugin-version="40">
RFE 88341 Added a step to delete a list of applications by name.
    </release-note>
    <release-note plugin-version="41">
Fixes APAR PI98083 Modified 'Delete Applications' step to pass in the correct argument.
    </release-note>
    <release-note plugin-version="42">
RFE 112896 Added step to delete an execution group from the broker.
RFE 104689 Added a parameter to the deploy step to specify a full/incremental deployment.
    </release-note>
  </release-notes>
</pluginInfo>