Note: This plug-in is a beta release. The functionality and compatibility are subject to change. This information is for planning purposes only. The information herein is subject to change or removal without notice before the products described may become available. The PowerShell plug-in, currently a beta release, provides a step for running user-defined PowerShell scripts. The following features are included in the initial beta release:

• PowerShell script text box
• Bi-directional passing of script variables and IBM UrbanCode Deploy parameters
• Custom exit status handling
• User-specified session parameters

If you encounter issues with the plug-in and want to send feedback:

• See the plug-in documentation.
• Search on our answers page (note that the Open Link in New Tab function can interfere with the search terms in the link): dW Answers: urbancode | deploy | plugins | powershell | beta
• If there are no search results, submit your issue as a question to our answers page. Use the following tags: urbancode | deploy | plugins | powershell | beta.

 

IBM UrbanCode Deploy

Note: This plug-in is a beta release. The functionality and compatibility are subject to change. This information is for planning purposes only. The information herein is subject to change or removal without notice before the products described may become available.

Overview

IBM® CICS® Configuration Manager is a tool for managing and maintaining CICS Transaction Server definitions. It provides audit, reporting and lifecycle change management control facilities to support the build, management, and deployment of complex mainframe CICS applications.

You can use the CICS CM Beta plug-in for UrbanCode Deploy to automate your resource management process. The resource management process can be simplified by modelling the processes, that might be complex, across each of your environments. For example, these environments might be development, test, and production in different data centers.

To feedback to us about the CICS CM Beta plug-in, or if you have any questions, please contact us by using the CICSdev forum.

Compatibility

Platform Support:

Before you download the CICS CM Beta plug-in for UrbanCode Deploy, ensure that you are using the following levels of software:

• IBM CICS Transaction Server for z/OS Version 4, or later
• IBM CICS Configuration Manager for z/OS Version 5, or later

The CICS CM Beta plug-in requires UrbanCode Deploy 6.1.1.1, or later.

Installation

The CICS CM Beta plug-in can be installed by following the steps outlined in Installing plug-ins in UrbanCode Deploy.

IBM UrbanCode Deploy

Docker automates the deployment of applications inside Linux containers. This plug-in provides the ability to map Docker images to components within IBM UrbanCode Deploy. The included component template provides a process for running Docker containers. This automation plug-in requires two source configuration plug-ins. They are available on the community page, and are mirrored here for convenience: Download Docker Source Plug-in Download ICS Source Plug-in The previous community project can be found here.

IBM UrbanCode Deploy

Overview

The IBM WebSphere Application Server - Install plug-in includes a sample application that automates a standard installation of WebSphere Application Server Network Deployment. This application is provided as an example and must be modified or used as a guide for creating your own installation process. The plug-in also includes steps related to installing WebSphere Application Server.

Prerequisites

IBM Installation Manager must be installed on the target system. The IBM WebSphere Application Server – Deploy plug-in (version 76 or later) must be installed, and the IBM Installation Manager plug-in (version 3 or later) must be installed.

Compatibility

This plug-in requires version 6.1.1.2 or later of IBM UrbanCode Deploy. The sample application supports IBM WebSphere Application Server Network Deployment version 8.0 and later. Note: The sample application demonstrates installing IBM WebSphere Application Server Network Deployment on Linux.

IBM UrbanCode Deploy

Docker is an open platform for distributed applications for developers and sysadmins. Leverage this plugin to build Docker images with UrbanCode Build

UrbanCode Build

Overview

CICS® Transaction Server for z/OS provides scalable, general-purpose, transaction processing solutions for high-volume updates to shared data. Businesses have used CICS to differentiate themselves by creating, extending, and evolving their critical applications. You can use steps from the CICS TS plug-in for UrbanCode Deploy, in combination with other plug-ins, to automate the deployment and undeployment of CICS applications. In a wider context, the CICS TS plug-in can be used in conjunction with other CICS tooling to automate the build and deployment of CICS artifacts as part of a continuous delivery environment. Please post feedback about the CICS TS plug-in and questions on its usage to the CICSdev forum.

Compatibility

Platform Support: The CICS TS plug-in is supported to run against any of the following CICS editions:

• IBM CICS Transaction Server for z/OS Version 4 or above
• IBM CICS Transaction Server for z/OS Developer Trial Version 4 or above
• IBM CICS Transaction Server for z/OS Value Unit Edition Version 5 or above

Additionally, you must also have configured a CICS management client interface (CMCI) port, as described in topic Setting up access for CICS Explorer in the IBM Knowledge Center. This plug-in requires UrbanCode Deploy 6.1.1.4 or later, and the zOS Utility 10 plug-in or later. Step Support: CICS TS V5.1 or above is required for the following CICS TS plug-in steps:

• Enable application, Disable application

CICS TS V5.3 is required for the following CICS TS plug-in steps:

• Deploy bundle, Undeploy bundles
• Phase in resources for the resource type of Bundle
• Deploy application, Undeploy applications

Installation

No special steps are required for installation. See Installing plug-ins in UrbanCode Deploy.

IBM UrbanCode Deploy

The WebSphere Application Server – Deployment plug-in provides a number of steps for deploying application binaries to and performing administrative tasks for WebSphere Application Server. The plug-in also contains a number of steps related to configuration management, such as creating data sources, JMS requests, and so on. These configuration steps will be deprecated in a future release; the IBM Middleware Configuration for WebSphere plug-in should be used for all configuration-related activities. To learn more about different solutions for WebSphere Application Server, see Frequently Asked Questions about IBM UrbanCode Deploy solutions for WebSphere Application Server. This plug-in also supports WebSphere Application Server capabilities that were incorporated from WebSphere Virtual Enterprise (WVE) such as application editioning and dynamic clustering. Steps in this plug-in that are identified as OBSOLETE have been replaced by steps available in the Middleware Configuration for WebSphere Application Server plug-in. There are no current plans to enhance or remove these steps in this plug-in. Platform Support:

• This plug-in is supported to run on all operating systems supported by the IBM UrbanCode Deploy agent.
• This plug-in is supported to run against WebSphere Application Server v7 or higher. This plug-in also supports WebSphere Virtual Enterprise version 7 or higher. The Start Server step works only with WebSphere Application Server Network Deployment. The Start Server step does not work on WebSphere Application Server Base.
• This plug-in requires UrbanCode Deploy 6.1.1.2 or later. If you are running a version of UrbanCode Deploy earlier than 6.1.1.2, use the links below to download version 72 of the plug-in.

Impersonation:

• You can configure impersonation for the WebSphere Discovery step if the IBM UrbanCode Deploy server is at version 6.1.1.4 or later.
• The impersonating user must have access rights to both the WebSphere Application Server profile directory and the IBM UrbanCode Deploy agent directory. For example, if the WebSphere user is named wasusr with the group wasgrp, and the agent user is named ucdusr with the group ucdrgp, the user wasusr must be a member of the group ucdgrp.You can restrict the WebSphere Application Server profile directory so that only the WebSphere user has read, write, and execute permissions; the group and other users do not need any permissions. In this case, the WebSphere user starts all WebSphere processes.You can restrict the agent directory in the following ways:
  • The agent user has read, write, and execute permissions everywhere.
  • The group has read and execute permissions everywhere and write permissions in the var/ subfolder.
  • Other users have no access.
  By default, set the impersonation settings as follows:
  • User: WebSphere user
  • Password: [empty]
  • Group: WebSphere group
• There is no need to select the "Always use default impersonation" check box unless a Resource overrides it in an incompatible way.

Limitations:

• The Start Server step works only with WebSphere Application Server Network Deployment. The Start Server step does not work on WebSphere Application Server Base.
• This plug-in uses the wsadmin tool to manage connections to a WebSphere Application Server profile. Specific user rights are required to run the wsadmin tool. To learn more about user rights and the wsadmin tool, see the WebSphere Application Server Network Deployment documentation.

IBM UrbanCode Deploy

The IBM Middleware Configuration for WebSphere (MCWAS) plug-in extends the capabilities of the Deploy server to allow for the management of WebSphere Application Server (WAS) configurations. Configurations are stored as a template, which is a set of XML files that can be generated automatically by analyzing an exemplar WAS environment or created/modified using an XML editor. With the MCWAS plug-in, you can create configuration templates for the Cell, Cluster, Node and Server scopes. To learn more about different solutions for WebSphere Application Server, see Frequently Asked Questions about IBM UrbanCode Deploy solutions for WebSphere Application Server. The following scenarios are supported:

• Tokenization of configuration to account for environment specific differences (e.g. DataSource URLs, etc.)
• Deploy a configuration template to a specified WAS cell and scope. This overwrites the existing configuration, ensuring it matches the “golden master” template
• Promote a configuration across your SDLC using Application Snapshots
• Rollback a configuration
• Configuration drift detection. Detailed comparison of a configuration template against a live WAS target. This can be scheduled to run periodically to detect intentional or unintentional changes that have been made to a WAS target so an informed decision can be made to rollback or update the golden master template.
• Support for layered templates (note - minimum UrbanCode Deploy version 6.0.1.4 required for this capability)
• Export of all configuration data to WAS in a single transaction
• Supply custom jython files which can be used to run custom code when running import and export of WAS data.

The MCWAS plug-in contains several steps, however, the steps are not intended to be used directly. When the MCWAS plug-in is im