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.
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.
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.
Create CollectiveCreate a collective controller configuration in the WebSphere Liberty Profile.
Create ServerCreate a server in the WebSphere Liberty profile.
Delete ServerDelete a server in the WebSphere Liberty profile.
Generate Component-Resource PropertiesGenerate component-resource properties from variable tags in the server.xml file.
Generate Plugin ConfigGenerate plug-in configuration for a WebSphere Liberty server.
Install Server ArchiveInstall 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 CollectiveJoin a server to the collective controlled by the designated controller.
Register HostRegister a new host with the collective controlled by the designated controller.
Replace Variable Values with Component-Resource PropertiesReplace variable values in the server.xml file with component-resource properties.
Start ApplicationStart an application in the WebSphere Liberty profile.
Start ServerStart a server in the WebSphere Liberty profile.
Stop ApplicationStop an application in the WebSphere Liberty profile.
Stop ServerStop a server in the WebSphere Liberty profile.
Uninstall Application from DropinsUninstall an application from the WebSphere Liberty profile by using the dropins directory.
Uninstall Application via Server XMLUninstall an application in the WebSphere Liberty profile by editing the server.xml file.
Unregister HostUnregisters a host and all of its associated servers from the collective.
Update HostUpdates the authentication information for a host that has been registered with the collective.
Upload File To Collective HostUpload a file to the target collective host. The target host must already be registered with the collective.
Wait for Application to be STARTEDWait for an application to run (have a status of Started).
The PowerShell plug-in provides a step for running user-defined PowerShell scripts.
The following features are included in the initial release:
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.
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.
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.
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:
Post Notification to Slack