<?xml version="1.0" encoding="UTF-8"?><!--
- Licensed Materials - Property of IBM* and/or HCL**
- UrbanCode Deploy
- (c) Copyright IBM Corporation 2002-2017. All Rights Reserved.
- (c) Copyright HCL Technologies Ltd. 2018. 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 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>
    <website>https://www.ibmdw.net/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="https://www.ibmdw.net/urbancode/plugin/application-deployment-for-websphere-ibmucd/"/>

  <!--
  **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>WebSphere is the leading software for on demand business, delivering business integration, application and transaction infrastructure, portals, application transformation, mobile/speech middleware, product information management and e-commerce.</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 the Websphere tool." title="IBM Websphere Homepage" type="WEBSITE" url="http://www-01.ibm.com/software/websphere"/>
  </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>117.987411</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="9">
 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="10">
Changing names of some steps to fix a bug when adding them to uDeploy.
      </release-note>
      <release-note plugin-version="11">
Added new steps for creating Clusters and ClusterMembers
      </release-note>
      <release-note plugin-version="12">
Added new steps for initial and maximum heap size of server jvms.
      </release-note>
      <release-note plugin-version="13">
Added new steps for exporting and importing initial and maximum heap size of server jvms.
      </release-note>
      <release-note plugin-version="14">
Added new steps for exporting and import properties from datasources.
      </release-note>
      <release-note plugin-version="15">
Added new steps for creating JDBCProviders and DataSources.
      </release-note>
      <release-note plugin-version="16">
Added new steps for creating JDBCProviders and DataSources.
      </release-note>
      <release-note plugin-version="17">
Add a step for checking for the existence of a config object.
      </release-note>
      <release-note plugin-version="18">
Add a step for creatinga SIBJMSQueues.
      </release-note>
      <release-note plugin-version="19">
Add a step for creatinga SIBJMSTopics.
      </release-note>
      <release-note plugin-version="20">
Add a step for creatinga SIBJMSConnectionFactories.
      </release-note>
      <release-note plugin-version="21">
Add a step for updating a simple attribute on an object.
      </release-note>
      <release-note plugin-version="22">
Add a step for creating or updating J2EEResourceProprties on objects.
      </release-note>
      <release-note plugin-version="23">
Add a step to check to see if an application is already installed in the cell. This step will set an output property named "installed" to either "true" or "false".
      </release-note>
      <release-note plugin-version="24">
Allowing choosing Application Type to check for in check application is/not running.
      </release-note>
      <release-note plugin-version="25">
Add timeout properties for wait for application and wait for server or cluster.
      </release-note>
      <release-note plugin-version="26">
Make the required resources for configure resources of create jdbc more generic.
      </release-note>
      <release-note plugin-version="27">
Add a step for waiting for a server or cluster to stop.
      </release-note>
      <release-note plugin-version="28">
Add the ability to immediately stop a cluster in stop server step.
      </release-note>
      <release-note plugin-version="29">
Add a terminate server or cluster step. This step will send a signal to the node agents that are involved with the server or cluster to hard terminate the server, or all servers associated with the cluster.
This step should only be used when a stop server or cluster step does not succeed in fully stopping the server or cluster in time. Please be careful of the use of this step.
      </release-note>
      <release-note plugin-version="30">
Add interval specifications to wait for server or cluster, Wait for application, and Wait for server or cluster to stop.
      </release-note>
      <release-note plugin-version="31">
Add steps for creating shared libraries and associating them with applications.
      </release-note>
      <release-note plugin-version="67">
Add the ability to immediately stop a cluster in stop server step.
Add a terminate server or cluster step. This step will send a signal to the node agents that are involved with the server or cluster to hard terminate the server, or all servers associated with the cluster.
This step should only be used when a stop server or cluster step does not succeed in fully stopping the server or cluster in time. Please be careful of the use of this step.
Add interval specifications to wait for server or cluster, Wait for application, and Wait for server or cluster to stop.
      </release-note>
      <release-note plugin-version="68">
Conflicts will no longer occur over the 'temp.py' file.
      </release-note>
      <release-note plugin-version="69">
Auto discover support for multiple profiles/installs on the same agent machine.
      </release-note>
      <release-note plugin-version="70">
Add ability to inline script for Execute wsadmin script.
      </release-note>
      <release-note plugin-version="71">
Added option to not delete generated jython/jacl scripts on failure.
Added steps for working with BLAs, assets, OSGI bundles, and composition units.
Add steps for mapping targets to modules, resource-references and roles to users for Enterprise Applications.
      </release-note>
      <release-note plugin-version="72">
Extra functionality to work with Application Editions.
      </release-note>
      <release-note plugin-version="73">
Extra functionality to work with Application Editions.
      </release-note>
      <release-note plugin-version="74">
Added step for mapping shared libraries to modules.
Allow mapping multiple shared libraries in one step.
      </release-note>
      <release-note plugin-version="75">
Update description text.
      </release-note>
      <release-note plugin-version="79">
Added steps for disabling/enabling node auto sync.
Added step to invoke AdminTask.updateAppOnCluster.
      </release-note>
      <release-note plugin-version="81">
Added step to check status of nodes.
      </release-note>
      <release-note plugin-version="83">
Added steps to createUnmanagedNode and createIHSWebServer.
      </release-note>
      <release-note plugin-version="87">
Added an additional argument parameter to "Check Application is installed" step
      </release-note>
      <release-note plugin-version="88">
Added support for partial application updates.
      </release-note>
      <release-note plugin-version="89">
Fixed Add Target To Module step so that plugin-cfg.xml is generated correctly
      </release-note>
      <release-note plugin-version="90">
Updated version so that plugin would install over previous testfixes.
      </release-note>
      <release-note plugin-version="91">
Added additional functionality to Synchronize Node step which allows for individual nodes to be synchronized rather than all nodes every time.
      </release-note>
      <release-note plugin-version="92">
Added additional functionality to return node profile name during topology discovery.
      </release-note>
      <release-note plugin-version="93">
WebSphere topology discovery was failing if an unmanaged node is in the topology.
      </release-note>
      <release-note plugin-version="94">
Added additional functionality to modify soap.client.props file.
      </release-note>
      <release-note plugin-version="95">
Added small quality of life changes to the "Edit soap.client.props File" step.
      </release-note>
      <release-note plugin-version="96">
Support application install/update at the cell scope.
Support application start/stop at the cell scope.
Update plugin steps to support WebSphere 9 environments.
      </release-note>
      <release-note plugin-version="97">
Fixes APAR PI63546 - Importing a plugin may fail with null pointer exception due to missing required plugin
Fixes APAR PI67024 - PluginCfg.xml improperly generated when executed at a cell scope level
Add support to check application status at the cell scope
Update the Modify Application ClassLoaders step to allow specifying warClassLoaderPolicy
      </release-note>
      <release-note plugin-version="98">
Add support to uninstall application from the cell scope.
Remove extra double-quote from command when checking application status at cell scope.
      </release-note>
      <release-note plugin-version="99">
Topology discovery step can now be called directly by a process, though, it still supports being called by a wrapper step.
Topology discovery will set an output property named "createdResources", this can be accessed only when calling this step directly.
Auto discover will also set an output property named "createdResources".
Add new step named Set Application Defaults.
      </release-note>
      <release-note plugin-version="100">
Fixed problem where new EJB was mapped to DMGR instead of cluster on application update.
Added new steps Update Context Root for Web Modules and Update Virtual Host for Web Modules.
      </release-note>
      <release-note plugin-version="101">
Add support for encrypted input/output properties files.
Fixes APAR PI74876 - Performance problem with UCD WAS-Deploy plugin when running syncnodes
Add new plugin step 'Delete Server'
      </release-note>
      <release-note plugin-version="102">
Added new plugin steps for Properties File Based Configuration support.
Fixes APAR PI75224 - "Add Target To Module" step fails if the modURI name contains spaces.
Fixes APAR PI76072 - Full SyncNode does not execute an epoch refresh.
      </release-note>
      <release-note plugin-version="103">
Fixes APAR PI77499 - Error occurs when adding multiple shared libraries to an application.
      </release-note>
      <release-note plugin-version="104">
Fixes APAR PI80980 - Check Status plugin step fails when same server name exists on multiple nodes.
      </release-note>
      <release-note plugin-version="105">
Fixes APAR PI83021 - Find application edition in validation mode if one is not specified on the Cancel Validation Mode plugin step.
      </release-note>
      <release-note plugin-version="106">
Add debug statement to assist diagnosis of topology discovery failures.
      </release-note>
      <release-note plugin-version="107">
Only invoke AdminTask.cancelValidation() if application edition information is available.
      </release-note>
      <release-note plugin-version="108">
Provided task completion message for deleteServer.
Fixes APAR PI87625 - time out issue with stopping and starting server
Fixes auto discovery failures caused by trailing whitespaces in wsadmin.path or websphere.profilePath
      </release-note>
      <release-note plugin-version="109">
RFE 105793 - Add support for Intelligent management features on the target WAS cell with following additional steps:
- Intelligent Management - Enable
- Intelligent Management - Disable
- Intelligent Management - List Trace Rules
- Intelligent Management - Add Remote Cell
- Intelligent Management - Delete Remote Cell
- Intelligent Management - List Remote Cells
- Intelligent Management - Modify
- Intelligent Management - Modify Remote Cell
- Intelligent Management - Refresh Local Cell
- Intelligent Management - Refresh Remote Cell
- Intelligent Management - Add Conditional Trace Rule
- Intelligent Management - Set Default Trace Rule
- Intelligent Management - Remove Conditional Trace Rule
- Intelligent Management - Generate Plugin
Fixes APAR PI87795 - WebSphere Configuration Discovery may fail to retrieve passwords if multiple profiles are defined as part of the
WebSphere installation.
Fixes APAR PI87070 - Websphere Topology Discovery removes default impersonation set on WebSphereCell resource
- Handled both the cases where wrapper is invoked and not invoked
- Included the impersonation settings in the cell resource
      </release-note>
      <release-note plugin-version="110">
RFE 98521 - Add step to return the list of nodes running on a cluster, given a cluster name
Add step to support WebSphere PropertiesBasedConfiguration through extractConfigProperties task
RFE 108953 - Add "disable autostart for application" step to the Websphere Application Server Deployment Plugin
      </release-note>
      <release-note plugin-version="111">
RFE 112023 - WAS deployment plugin to support enable autostart of an application
      </release-note>
      <release-note plugin-version="112">
Fixes issue where Start Application and Stop Application plugin steps did not work for application names that contained spaces.
      </release-note>
      <release-note plugin-version="113">
Fixes APAR PI91329 - Terminate server/cluster step fails when node agent is stopped
      </release-note>
      <release-note plugin-version="114">
Change dependency on UrbanCode Deploy Versioned File Storage plug-in to version 30.
      </release-note>
      <release-note plugin-version="115">
Fixes issue where Wait for Server or Cluster to Stop step considers a server stopped when the server is in a stopping state.
      </release-note>
      <release-note plugin-version="116">
Fixes APAR PI99446 - "Execute Wsadmin Script" plugin step fails on z/OS when using the "Script Body" parameter.
      </release-note>
      <release-note plugin-version="117">
Fixes APAR PH00570 - "Execute Wsadmin Script" plugin step not producing proper output.
      </release-note>
  </release-notes>
</pluginInfo>