Integration Points,
Just a Click Away!
Capture and promote
WebSphere Application Server
in your development process
Utilize our plugin database to
define your unique deployment
process with your existing
tool set
New and Noteworthy
Category
Description
The Microsoft TFS plug-in imports version artifacts from a TFS server. TFS is supported both as a source of builds via the build service, as well as via direct retrieval of deployable artifacts from source control via the TFS_scm plugin.
Note: Microsoft .NET Framework 3.5 must be installed on the agent computer where the plug-in is installed. If Microsoft .NET Framework 3.5 is not installed on the agent computer, the following error message is displayed when you attempt to import version artifacts: Error Creating New Version: Error retrieving latest build.
Compatibility
- This plug-in supports Team Foundation Server 2010 - 2017.
- This plug-in requires version 6.0 or later of IBM UrbanCode Deploy.
- For UrbanCode Deploy 6.0, both the agent and the server must be installed on Microsoft Windows. For UrbanCode Deploy 6.0.1 or later, only the agent is required to be on a system running Microsoft Windows.
Microsoft TFS (Team Foundation Server)
13
Learn more about Plugins
Source Config Plugin
IBM UrbanCode Deploy
Category
Description
JIRA is an issue tracking product, developed by Atlassian. The JIRA plug-in for IBM UrbanCode Release provides an integration with JIRA. JIRA work items are available on the Impact Analysis view, and additional functionality is provided by automated and custom field mapping. This plug-in represents a significant enhancement to the earlier JIRA plug-in for IBM UrbanCode Release. At this time, an upgrade path is not available from the earlier version to the current plug-in version.
Description
To get started with the plug-in, read the plug-in documentation and watch the tutorial video:
You can use the Microsoft IIS – Configure plug-in to manage Microsoft's Internet Information Services (IIS) configurations and applications. The plug-in includes steps to discover configurations and package them into .zip files by using Microsoft Web Deploy, which must be installed on the agent computer. You can modify the configuration files that are produced in the .zip archive file that the plug-in creates. The .zip file created by the plug-in is the same format that is created by the Microsoft Web Deploy package provider. You can use the tokenization steps that the plug-in provides to modify the configuration files to work with multiple environments. After you modify a configuration, you can apply it to the original environment or to a different environment. You can work with entire Microsoft IIS configurations, or at a specific scope such as Sites, Apps, or App Pools.
Category
Description
This plug-in provides steps to publish API Definitions and Loopback Apps to an API Connect server. This plug-in communicates to API Connect through the use of the apiconnect (apic) command line toolkit.
Platform Support:- This plug-in is supported to run on all operating systems that are supported by both the IBM UrbanCode Deploy agent (except for z/OS) and the apic toolkit.
- The apic toolkit must be downloaded and installed separately. Directions can be found here. This plug-in supports apic v2.0.18 and higher.
- Authentication issues exist within the apic toolkit. Please refer to the troubleshooting page for a secure workaround.
Available Steps
Login: Authenticate with an API Connect cloud via the management server. This step is a prerequisite for all steps. Logout: Remove local authentication credentials for an API Connect cloud. Suggested to run on the completion of each deployment process. Publish API and Product Definitions: Publish and deploy a product and its referenced APIs to a catalog. Publish Application to Provider App: Publish a Node.js (Loopback) application to a provider app. Push Local API or Product Definitions to Drafts: Push a local API or Prouducd definition to drafts on API Connect cloud. Replace Product in Catalog: Replace a Product in a Catalog with another Product. Set Configuration Variable: Set one configuration variable. The 'Login' step is not required. This is a wrapper step for the App and Catalog Identifier. If you understand and have access to the Identifier command, use the Shell step to run that command.
Category
Description
The Docker Compose plug-in for IBM UrbanCode Deploy automates deployment and resource creation for services.
Read our Docker Compose Deployments for the Enterprise blog post for an in-depth walkthrough of the Docker Compose plug-in.
Jump start your deployment strategy with our preconfigured Docker templates.Description
This plug-in includes steps for installing and updating applications in the IBM WebSphere Liberty Profile, working with the profile configuration and managing Liberty collectives.
Available Steps
Create Collective: Create a collective controller configuration in the WebSphere Liberty Profile. Create Server: Create a server in the WebSphere Liberty profile. Delete Server: Delete a server in the WebSphere Liberty profile. Generate Component-Resource Properties: Generate component-resource properties from variable tags in the server.xml file. Generate Plugin ConfigGenerate plug-in configuration for a WebSphere Liberty server. Install Server Archive: Install a WebSphere Liberty archive file. Install or Update Application: with Server XMLInstall or update an application in the WebSphere Liberty profile by editing the server.xml file. Install or Update Application: with DropinsInstall or update an application in WebSphere Liberty by using the dropins directory. Join Collective: Join a server to the collective controlled by the designated controller. Register Host: Register a new host with the collective controlled by the designated controller. Replace Variable Values with Component-Resource Properties: Replace variable values in the server.xml file with component-resource properties. Start Application: Start an application in the WebSphere Liberty profile. Start Server: Start a server in the WebSphere Liberty profile. Stop Application: Stop an application in the WebSphere Liberty profile. Stop Server: Stop a server in the WebSphere Liberty profile. Uninstall Application from Dropins: Uninstall an application from the WebSphere Liberty profile by using the dropins directory. Uninstall Application via Server XML: Uninstall an application in the WebSphere Liberty profile by editing the server.xml file. Unregister Host: Unregisters a host and all of its associated servers from the collective. Update Host: Updates the authentication information for a host that has been registered with the collective. Upload File To Collective Host: Upload a file to the target collective host. The target host must already be registered with the collective. Wait for Application to be Started: Wait for an application to run (have a status of Started).Category
Description
The IBM® UrbanCode™ Mobile plug-in provides integration between the IBM UrbanCode Release server and a cloud-based service. It allows deployment data to be synced between the IBM UrbanCode Release server and a mobile device using the cloud-based service. The mobile device user must be a registered UrbanCode Release user to receive deployment information that is limited to the defined security permissions associated with the user.This plug-in is deprecated. Use the UrbanCode Release for Cloud Sync plug-in instead. The UrbanCode Release for Cloud Sync plug-in is installed into the UrbanCode Sync utility.
Description
Important: This version of the WebSphere Application Server - Configure plug-in requires version 48 or later of the File Utils plug-in. If the minimum level of the File Utils plug-in is not installed, the WebSphere Application Server - Configure plug-in cannot be installed because the sample processes cannot be imported.
Overview
Starting with version 14 of the WebSphere Application Server – Configure plug-in for IBM UrbanCode Deploy, you can use JSON files to manage WebSphere Application Server configuration. The configuration data is stored in a series of JSON files. The JSON files can be grouped to represent cell and Deployment Manager configurations, node and node agent configurations, cluster and cluster member configurations, and configurations for other WebSphere objects. You can then associate the groups of JSON files with IBM UrbanCode Deploy components, which allow for assigning versions to the JSON files. Finally, you can create processes to apply configurations and configuration changes to WebSphere Application Server instances.Benefits
Scope-specific application of changes
Because you can group JSON files into components such as cell configuration, node configuration, and other configurations, you can apply changes for one component without affecting the other components. For example, you can choose to apply only cell configuration changes. Changes to the cell configuration are then applied, but the node configuration remains unchanged.Version comparison
Because the JSON files are stored as component artifacts, they are assigned versions. You can compare versions to identify configuration changes by using the IBM UrbanCode Deploy user interface.Template creation for multiple clusters and environments
You can build a JSON template that represents a server cluster member. Users can then create any number of server cluster members based on the template. For example, in a development environment, users might want to deploy a cluster with two servers on each node. In a QA environment, each cluster might contain four servers. You can use the JSON server template with IBM UrbanCode Deploy to create these multiple servers.Videos:
Prerequisites
The IBM WebSphere Application Server – Deploy plug-in (version 92 or later) must be installed.Compatibility
- This plug-in requires version 6.2 or later of IBM UrbanCode Deploy.
- IBM WebSphere Application Server versions 6.1, 7.0, 8.0, 8.5 and 9.0 and later are supported.
- This plug-in uses the wsadmin tool to manage connections to an IBM WebSphere Application Server profile. Specific user rights are required to run the wsadmin tool. To learn more about the wsadmin tool and the required user rights, see the WebSphere Application Server Network Deployment help.
- Database queries are used to create roles when you install this plug-in. If DB2 SQL error messages are logged when you install the plug-in, increase the transaction log size in DB2. To learn more, see the Troubleshooting page in the plug-in documentation.
Most Popular
Category
Description
Important: This plug-in is different and separate from the previous Jenkins plug-in. This plug-in is a Jenkins build step rather than a post-build action.
Jenkins is a continuous integration server that supports interactions with other technologies by using a plug-in model.
This plug-in is installed into the Jenkins server and includes functions to interact with IBM UrbanCode Deploy components and deployments. With this new plug-in, you can complete the following tasks:
- Create components
- Publish artifacts to a version
- Start component version imports
- Deploy snapshots or component versions
- Run the step multiple times within a single job
- Accomplish all of the above with pipeline script syntax
Compatibility:
- This plug-in is supported to run against Jenkins Server 2.0 or later
- This plug-in requires IBM UrbanCode Deploy 6.1 or later
Jenkins Pipeline (Formerly Jenkins 2.0)
2.5
Learn more about Plugins
Source Config Plugin
IBM UrbanCode Deploy
Category
Description
Jenkins is a continuous integration server that supports interactions with other technologies by using a plug-in model.
This plug-in is installed into the Jenkins server and provides the ability to publish artifacts into an IBM UrbanCode Deploy component as a post-build action.
For the Jenkins build step rather than a post-build action, please refer to the Jenkins Pipeline (Formerly Jenkins 2.0) plug-in.
Compatibility
The plug-in supports:
- Jenkins 1.424 and later.
- IBM UrbanCode Deploy 6.1 and later.
Jenkins Publisher (Formerly Jenkins)
1.9
Learn more about Plugins
Source Config Plugin
IBM UrbanCode Deploy
Description
The WebSphere Application Server – Deployment plug-in provides a number of steps for deploying application files to and performing administrative tasks for WebSphere Application Server. The plug-in also contains a number of steps that are related to configuration management, such as creating data sources and JMS requests. These configuration steps are deprecated; instead, use the WebSphere Application Server - Configure plug-in for all configuration-related activities.
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 were replaced by steps available in the WebSphere Application Server - Configure 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 that are 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 at the bottom to download version 72 of the plug-in.
- 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.
- User: WebSphere user
- Password: [empty]
- Group: WebSphere group
- You do not need to select the Always use default impersonation check box unless a Resource overrides it in an incompatible way.
- 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.
Category
Description
Docker automates the deployment of applications inside Linux containers. This plug-in maps Docker images to components in IBM UrbanCode Deploy. The included component template provides a process for running Docker containers.
This automation plug-in requires the Docker source configuration plug-in. The IBM-supported source config plug-in is available here.
Uncertain on where to start? Read up on our Docker Deployments for the Enterprise blog post. It is a great place to understand how IBM UrbanCode Deploy's automation capabilities complement the value of Docker.
Jump start your deployment strategy with our preconfigured Docker templates.
The Docker Source Plug-in may be found here.
The previous community project can be found here.
Category
Description
Kubernetes is an open-source system for automating deployment, operations, and scaling of containerized applications.
This plug-in provides the ability to interact with Kubernetes resources within IBM UrbanCode Deploy.
Be sure to review our tutorial on how you may use the plug-in to enhance your Kubernetes experience, or watch a video walk-through on how you may deploy your applications to IBM Bluemix.Category
Description
The PowerShell plug-in provides a step for running user-defined PowerShell scripts.
The following features are included in the initial release:
- PowerShell script text box
- Bidirectional passing of script variables and IBM UrbanCode Deploy parameters
- Custom exit status handling
- User-specified session parameters
Description
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 that are 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 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.Description
Important: This version of the WebSphere Application Server - Configure plug-in requires version 48 or later of the File Utils plug-in. If the minimum level of the File Utils plug-in is not installed, the WebSphere Application Server - Configure plug-in cannot be installed because the sample processes cannot be imported.
Overview
Starting with version 14 of the WebSphere Application Server – Configure plug-in for IBM UrbanCode Deploy, you can use JSON files to manage WebSphere Application Server configuration. The configuration data is stored in a series of JSON files. The JSON files can be grouped to represent cell and Deployment Manager configurations, node and node agent configurations, cluster and cluster member configurations, and configurations for other WebSphere objects. You can then associate the groups of JSON files with IBM UrbanCode Deploy components, which allow for assigning versions to the JSON files. Finally, you can create processes to apply configurations and configuration changes to WebSphere Application Server instances.Benefits
Scope-specific application of changes
Because you can group JSON files into components such as cell configuration, node configuration, and other configurations, you can apply changes for one component without affecting the other components. For example, you can choose to apply only cell configuration changes. Changes to the cell configuration are then applied, but the node configuration remains unchanged.Version comparison
Because the JSON files are stored as component artifacts, they are assigned versions. You can compare versions to identify configuration changes by using the IBM UrbanCode Deploy user interface.Template creation for multiple clusters and environments
You can build a JSON template that represents a server cluster member. Users can then create any number of server cluster members based on the template. For example, in a development environment, users might want to deploy a cluster with two servers on each node. In a QA environment, each cluster might contain four servers. You can use the JSON server template with IBM UrbanCode Deploy to create these multiple servers.Videos:
Prerequisites
The IBM WebSphere Application Server – Deploy plug-in (version 92 or later) must be installed.Compatibility
- This plug-in requires version 6.2 or later of IBM UrbanCode Deploy.
- IBM WebSphere Application Server versions 6.1, 7.0, 8.0, 8.5 and 9.0 and later are supported.
- This plug-in uses the wsadmin tool to manage connections to an IBM WebSphere Application Server profile. Specific user rights are required to run the wsadmin tool. To learn more about the wsadmin tool and the required user rights, see the WebSphere Application Server Network Deployment help.
- Database queries are used to create roles when you install this plug-in. If DB2 SQL error messages are logged when you install the plug-in, increase the transaction log size in DB2. To learn more, see the Troubleshooting page in the plug-in documentation.
Description
Docker is an open platform for distributed applications for developers and sysadmins.
Leverage this plugin to build Docker images with UrbanCode Build
Available Steps
Docker BuildBuild a Docker image from a Dockerfile and set the image id as a build life property.
Docker PushPublish a Docker image to a registry.
Description
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.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
- Enable application, Disable application
CICS TS V5.1 or CICS TS V5.2 with APAR PI56706, or CICS TS V5.3 is required for the following CICS TS plug-in steps. These steps also require the UCD agent to run in the same sysplex as the target CICSPlex SM CMAS region:
- Deploy bundle, Undeploy bundles
- Deploy application, Undeploy application
CICS TS V5.3 is required for the following CICS TS plug-in steps:
- Phase in resources for the resource type of Bundle
Installation
No special steps are required for installation. See Installing plug-ins in UrbanCode Deploy.Community Showcase
Category
Description
A plugin for management of TIBCO applications – includes steps for deployment, configuration, export etc. The plugin to provides smooth and transparent interaction between TIBCO Administrator and IBM UrbanCode Deploy tool. It automates the app management process for TIBCO applications by providing simplified process.
This community plugin is supported on a best effort basis. For a commercially supported Tibco integration, please see the Partner Plugin provided by ScaleFocus.
Downloads:
If you encounter issues with the plug-in, or want to send feedback:
- See the plug-in documentation.
- Ask Tibco plug-in specific questions on the GitHub Issues page.
- For general plug-in issues, submit questions to our dW Answers page. Use the following tags: urbancode | ucdev | plugins
Category
Description
IBM Sterling B2B Integrator integrates critical B2B processes, transactions, and relationships.
This plug-in includes steps to manage and automate the functionality and configuration of an IBM Sterling B2B Integrator server.
This is a community plug-in. For more information, see the IBM Sterling B2B Integrator v1.0.docx file in the doc folder of the project.
This plug-in currently supports only Microsoft Windows operating systems.
Downloads: If you encounter issues with the plug-in, or want to send feedback:- Ask Sterling B2Bi plug-in specific questions on the GitHub Issues page.
- For general plug-in issues, submit questions to our dW Answers page. Use the following tags: urbancode | ucdev | plugins
Available Steps
- Add Workflow
- Apply Configurations
- Assemble Import Batch File
- Get Service Status
- Import Batch File
- Import MAPs
- Install or Uninstall Third-Party Jars
- Restart Windows Service
- Start B2Bi
- Stop B2Bi
Category
Description
This plug-in provides access to utilities that are related to integrating with IBM MaaS360 via web services. For example, you can use this plug-in to request an authentication token.
This plug-in is developed and supported by the UrbanCode Deploy Community on the IBM® DevOps Services platform. Click Visit Project at the top of the page to navigate to the project for further information.
Downloads:
If you encounter issues with the plug-in, or want to send feedback:
- See the plug-in documentation.
- Ask IBM MaaS360 plug-in specific questions on the GitHub Issues page.
- For general plug-in issues, submit questions to our dW Answers page. Use the following tags: urbancode | ucdev | plugins
Available Steps
- Add iOS Mobile App
- Distribute App
- Get App Details
- Get Device Groups
- Mark As Primary
- Request Authentication
- Upgrade App
- Upgrade App Plus
Category
Description
Overview
Informatica PowerCenter is an enterprise data integration platform. The Informatica plug-in for IBM UrbanCode Deploy is an automation plug-in that connects to specific repositories and directly accesses and merges data across remote systems in your organization. For details on how the plug-in is constructed, how it works internally, or how to extend it yourself, see the README.md file that is contained in the project. Downloads: The Informatica plug-in is an open source project that is maintained by the IBM UrbanCode Development Community. If you encounter issues or want to send feedback:- See the plug-in documentation.
- Ask Informatica plug-in specific questions on the GitHub Issues page.
- For general plug-in issues, submit questions to our dW Answers page. Use the following tags: urbancode | ucdev | plugins
Available Steps
- Apply Label
- Assign Permission
- Create Dynamic Deployment Group
- Create Folder
- Create Static Deployment Group
- Deploy Deployment Group
- Import Objects
- Roll Back Deployment Group
- Run PMREP Command
- Validate Deployment Group
Category
Description
Siebel is a customer relationship management (CRM) system that is produced by Oracle.
The Siebel plug-in is a community supported plug-in. Community plug-ins are open source projects that are developed and supported by the IBM UrbanCode development community. Click Visit Project at the top of the page to go to the project for further information.
The Siebel plug-in for IBM UrbanCode Deploy uses the Siebel Java Data Bean (JDB) API and shell processes to connect to a specific Siebel infrastructure and remotely deploy and configure Siebel components.
For details on how the plug-in is constructed, how it works internally, or how to extend it yourself, see the design document that is contained in the project.
The GitHub release of the Siebel plug-in includes steps to complete the following tasks:
- Automate the Siebel deployment process.
- Configure business objects. For example: configure applications, groups, and servers.
- Configure business services. For example: import workflows, Siebel Messages, and business services XML files.
- Run shell scripts. For example: import repository files, start and stop servers, and generate browsers.
- See the plug-in documentation.
- Ask Siebel plug-in specific questions on the GitHub Issues page.
- For general plug-in issues, submit questions to the dW Answers page. Use the following tags: urbancode | ucdev | plugins
Category
Description
Slack is a team collaboration tool. This plug-in sends deployment notifications to Slack in a specified channel.
Downloads:
If you encounter issues with the plug-in, or want to send feedback:
- See the plug-in documentation.
- Ask Slack plug-in specific questions on the GitHub Issues page.
- For general plug-in issues, submit questions to our dW Answers page.Use the following tags: urbancode | ucdev | plugins
Available Steps
Post Notification to Slack Post Attachment Notification to SlackCategory
Description
Gradle is a tool for automating common build tasks including testing and deployment. This plug-in calls the gradle command line to run a build script with the provided options against the defined tasks.
Agent system requirements
Compatible Gradle version: Gradle 1.10
This plug-in is developed and supported by the UrbanCode Deploy Community on the IBM DevOps Services platform. Click the “Visit Project” button at the top of the page to navigate to the project for further information.Category
Description
Liquibase is an open source tool that brings source control for tracking, managing and applying database schema changes.
This plug-in is developed and supported by the UrbanCode Deploy Community on IBM-UrbanCode's GitHub organization. Click the "Visit Project" button at the top of the page to navigate to the project for source code, the plug-in distributable, and further information.
Downloads:
If you encounter issues with the plug-in, or want to send feedback:- See the plug-in documentation.
- Ask Liquibase plug-in specific questions on the GitHub Issues page.
- For general plug-in issues, submit questions to the dW Answers page. Use the following tags: urbancode | ucdev | plugins
Available Steps
Update: Applies given count of change sets is specified. Else updates database to current version. Rollback: Rolls back change sets. dbDoc: Execute Liquibase in dbDoc mode to produce or update database reference documentation. DropAll: Drops all database objects owned by the user. Tag: Tags the current database state for future rollback. Generate Changelog: Generates change log of the database. Export Data: Export the data from the targeted database. Changelog Sync: Mark all changes as executed in the database. Update Testing Rollback: Updates the database, then rolls back changes before updating again. Validate: Checks the changelog for errors.Description
Puppet is a declarative, model-based approach to IT automation, helping you manage infrastructure throughout its lifecycle, from provisioning and configuration to orchestration and reporting. Using Puppet, you can easily automate repetitive tasks, quickly deploy critical applications, and proactively manage change, scaling from 10s of servers to 1000s, on-premise or in the cloud.
This plug-in enables you to apply puppet manifests, or call a puppet agent.
This plug-in is developed and supported by the UrbanCode Deploy Community on the IBM DevOps Services platform. Click the "Visit Project" button at the top of the page to navigate to the project for further information.
Downloads:
If you encounter issues with the plug-in, or want to send feedback:
- Ask Puppet plug-in specific questions on the GitHub Issues page.
- For general plug-in issues, submit questions to our dW Answers page. Use the following tags: urbancode | ucdev | plugins
Available Steps
Apply one or more manifest through puppet Run puppet agent to get updates from masterCategory
Description
The Apache Hadoop software library is a framework that allows for the distributed processing of large data sets across clusters of computers using simple programming models. It is designed to scale up from single servers to thousands of machines, each offering local computation and storage. Rather than rely on hardware to deliver high-availability, the library itself is designed to detect and handle failures at the application layer, so delivering a highly-available service on top of a cluster of computers, each of which may be prone to failures.
This plug-in enables you to run a Hadoop application on a NamedNode as part of an UrbanCode Deploy process.
This plug-in is developed and supported by the UrbanCode Deploy Community on the IBM DevOps Services platform. Click the "Visit Project" button at the top of the page to navigate to the project for further information.