<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!--
- Licensed Materials - Property of IBM* and/or HCL**
- UrbanCode Deploy
- (c) Copyright IBM Corporation 2011, 2017. All Rights Reserved.
- (c) Copyright HCL Technologies Ltd. 2019. All Rights Reserved.
-
- U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by
- GSA ADP Schedule Contract with IBM Corp.
-
- * Trademark of International Business Machines
- ** Trademark of HCL Technologies Limited
--><pluginInfo>

  <author name="IBM">
    <organization>IBM UrbanCode</organization>
    <email>ucplugin@us.ibm.com</email>
    <website>https://developer.ibm.com/urbancode/plugins/</website>
    <bio/>
  </author>

  <!--

  **intergration type IS Required**

  The integration type section identifies where the plugin fits into the process
  excepted types are SCM, 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 Business Process Manager is a comprehensive business process management platform, providing full visibility and insight to managing business processes. It provides tooling and a runtime environment for process design, execution, monitoring and optimization, along with basic system integration support. The product can be configured to support various levels of complexity and involvement with business process management.</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="Please visit this site for more information on Websphere BPM" title="IBM Websphere BPM Homepage" type="WEBSITE" url="http://www-03.ibm.com/software/products/en/business-process-manager-family"/>
  </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>13.1056526</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="9">....</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="1">
Installing this plugin will enable you to deploy process application snaphots on an online or offline Process Server.
      </release-note>

      <release-note plugin-version="2">
Added a step to import process application into a Process Center server.
Added a step to export process application from a Process Center server.
      </release-note>

      <release-note plugin-version="3">
Fixes APAR PI35342 - compatibility defect with IBM Urbancode Deploy version 6.1.0.4 and later.
      </release-note>

      <release-note plugin-version="4">
Added functionality to pass the hostname to the wsadmin script in all steps.
      </release-note>

      <release-note plugin-version="5">
Added steps for the following BPM commands:
- BPMExportInstallPackage
- BPMInstallPackage
- BPMExtractMigrationPolicy
- BPMMigrateInstances
- BPMSetDefaultSnapshot
- BPMSyncEnvironmentVariables
- BPMSyncEPVValues
- BPMSyncTeamBindings
- BPMStop
- BPMDeactivate
- BPMUpdateInstallationInformation
      </release-note>
      <release-note plugin-version="6">
Updated the regex that found the Track, Snapshot, and Process Application acronym.
Added property to print additional output for wsadmin.sh calls.
      </release-note>
      <release-note plugin-version="7">
Added timeout to Generate Offline Package to prevent BPM command line race conditions.
The Track, Container, and Snapshot acronym finder will return the entered value if not found. This will help debugging issues as the command line will exit with valuable output.
      </release-note>
    <release-note plugin-version="8">
Support property file encryption.
    </release-note>
  <release-note plugin-version="9">
Fixes APAR PI78360 - Updated acronym parsing and identification.
  </release-note>
<release-note plugin-version="10">
All step descriptions now include their wsadmin scriptings commands.
</release-note>
<release-note plugin-version="11">
Updated all descriptions to specify whether the step connects to a Process Server or Process Center server.
    All step descriptions have the BPM command they are utilizing. If you are having trouble, we recommend referencing the WebSphere BPM documentation for CLI specific help. Many questions can be answered by following WebSphere BPM's official CLI documentation.
    Most steps will connect to the Process Center server. However, we recommend that there is at least one agent is installed on every Process Server and Process Center server. By running against the agent located on the correct server, this will eliminate the need to specify each step's Host property. This is achievable through proper UrbanCode Deploy environment and resource management.
The Update Installation Information step's Process application track property is now optional for Process Center servers. It is still required for Process Servers.
</release-note>
<release-note plugin-version="12">
Warn the user when either conflicting credential properties or no credential properties are set. General refactoring.
</release-note>
<release-note plugin-version="13">
Fixes APAR PH08137: Exception WASX8009E Invalid Parameter with BPM Deploy Process Application Snapshot step with spaces in Process Server Name
</release-note>
  </release-notes>
</pluginInfo>
