- Docs Home
- Getting started
- XL Release
- Overview
- Installation
- Get started with XL Release
- Manage your installation
- Model your releases
- Release your software
- Release overview
- Create and start releases
- Configure release properties
- Scheduling releases
- Start a release from an archived release
- Start a release from a template
- Start a release from another release
- Create a release from a Git repository
- Add a phase to a release or template
- Add a task to a phase in a release or template
- Import a release template
- Trigger releases
- Work with running releases
- Work with plugins
- Using reports
- Customize XL Release
- API and scripting overview
- Create custom task types
- Create custom configuration types
- Create custom trigger types
- Extend the XL Release GUI
- Declare custom REST endpoints
- Create custom tiles
- Create custom task types
- Create custom configuration types
- Using scheduling in scripts to connect to long running jobs
- Implement a custom failure handler
- Listen to XL Release events
- Configuration settings
- Release manuals
- XL Deploy
- Connect to your infrastructure
- Set up applications and environments
- Prepare your application for XL Deploy
- Create a deployment package
- Define application dependencies
- Configure an environment
- Using placeholders and dictionaries
- Working with deployment packages
- Preparing your application for XL Deploy
- Understanding deployables and deployeds
- XL Deploy manifest format
- Deprecated XL Deploy manifest format
- Using the XL Deploy Manifest Editor
- Understanding archives and folders in XL Deploy
- Add an externally stored artifact to a package
- Extend the external artifact storage feature
- Add a package to XL Deploy
- Export a deployment package
- XL Deploy for developers
- Tips and tricks for deployment packages
- Deploy an application
- Deployment overview
- Understanding the XL Deploy planning phase
- Steps and step lists in XL Deploy
- Understanding tasks in XL Deploy
- Deploy an application
- Use tags to configure deployments
- Preview the deployment plan
- Use orchestration
- Working with deployments
- Stopping, aborting, or canceling a deployment
- Schedule a deployment
- Update a deployed application
- Staging artifacts in XL Deploy
- Monitor and reassign deployment tasks
- Make previously deployed property values available in a PowerShell script
- Undeploy an application or deprovision an environment
- Perform canary deployments
- Perform dark launch deployments
- Perform hot deployments
- Deploying an externally stored artifact using the XL Deploy CLI
- Schedule or reschedule a task
- Using the deployment pipeline view
- Deploy to remote datacenters
- Get started with provisioning
- Use control tasks
- Work with the CLI
- Work with plugins
- Create an XL Deploy plugin
- Base plugins and the deployed object
- Implement custom XL Deploy plugpoints
- Add a checkpoint to a custom plugin
- Step options for the Generic, PowerShell, and Python plugins
- Sample Java-based XL Deploy plugin
- XL Deploy plugin tutorial
- Standard plugins
- Middleware plugins
- Apache Tomcat
- BizTalk
- F5 BIG-IP
- GlassFish
- IBM WebSphere Application Server
- IBM WebSphere Process Server
- IBM WebSphere Liberty Profile Server
- IBM WebSphere MQ
- JBoss Application Server 5 and 6
- JBoss Application Server 7 and up
- Microsoft Internet Information Services
- Microsoft Windows
- NetScaler
- Oracle Service Bus
- Oracle Service-Oriented Architecture
- Oracle WebLogic Application Server
- Provisioning plugins
- Container platform plugins
- Tools
- Community plugins
- Using the Explorer
- Introduction to the release dashboard
- Using XL Deploy reports
- Manage your installation
- Logging in XL Deploy
- Start XL Deploy
- Shut down XL Deploy
- Back up XL Deploy
- Upgrade XL Deploy
- The XL Deploy Repository
- Configure the repository
- Configure XL Deploy to fetch artifacts from a Maven repository
- Manage security
- Manage system settings
- Configure failover for XL Deploy
- Configure active/hot-standby mode
- Configure the task execution engine
- Troubleshoot the Jackrabbit JCR repository
- Configure XL Deploy client settings
- Enable XL Deploy maintenance mode
- Update the XL Deploy digital certificate
- The XL Deploy work directory
- Reclaim disk space on an XL Deploy server
- Hide internal XL Deploy server errors
- Automatically purge packages according to a user-defined policy
- Automatically purge the task archive according to a user-defined policy
- Specify file encoding on the XL Deploy server
- Automatically archive tasks according to a user-defined policy
- Best practices for maintaining XebiaLabs tools
- Customize XL Deploy
- XL Release plugins
- XL Deploy plugins
- Standard plugins
- Middleware plugins
- Apache Tomcat
- BizTalk
- F5 BIG-IP
- GlassFish
- IBM WebSphere Application Server
- IBM WebSphere Process Server
- IBM WebSphere Liberty Profile Server
- IBM WebSphere MQ
- JBoss Application Server 5 and 6
- JBoss Application Server 7 and up
- Microsoft Internet Information Services
- Microsoft Windows
- NetScaler
- Oracle Service Bus
- Oracle Service-Oriented Architecture
- Oracle WebLogic Application Server
- Provisioning plugins
- Container platform plugins
- Tools
- Community plugins
Valid since:
XL Deploy 8.0.0
Introduction to the XL Deploy Cloud Foundry plugin
The XL Deploy Cloud Foundry plugin supports:
- Creating spaces
- Deploying Cloud Foundry applications
- Creating routes for a Cloud Foundry application
- Binding services with a Cloud Foundry application
- Creating Cloud Foundry services
- Deploying Cloud Foundry application using a manifest file
For more information about the XL Deploy Cloud Foundry plugin requirements and the configuration items (CIs) that the plugin supports, refer to the Cloud Foundry Plugin Reference.
Using the XL Deploy Cloud Foundry plugin
The XL Deploy Cloud Foundry plugin can push and remove applications on a Cloud Foundry organization. To use the plugin:
- Download the XL Deploy Cloud Foundry plugin ZIP from the distribution site.
- Unpack the plugin inside the
XL_DEPLOY_SERVER_HOME/plugins/
directory. - Restart XL Deploy.
Create the Cloud Foundry organization
To create a Cloud Foundry organization in XL Deploy:
- Under Infrastructure, create a
cloudFoundry.Organization
CI. - Specify the following properties:
- Organization Name: Organization name on the Cloud Foundry server.
- API Endpoint: API endpoint of Cloud Foundry server (for example,
api.run.pivotal.io
). - Username: User name to use for authentication.
- Password: Password to use for authentication.
Provision a Cloud Foundry space
To provision a new Cloud Foundry space:
- Under Applications, create an application (
udm.Application
) and deployment package (udm.DeploymentPackage
). - Under the deployment package, create a
cloudFoundry.SpaceSpec
CI. - Specify the Space Name to use. If not provided, the CI name will be used as the space name.
Alternatively, you can use a space that already exists in Cloud Foundry by creating a cloudFoundry.Space
CI under the cloudFoundry.Organization
CI (in Infrastructure).
Push an application to Cloud Foundry
To push an application to Cloud Foundry:
- Under Applications, create an application (
udm.Application
) and deployment package (udm.DeploymentPackage
). - Under the deployment package, create a
cloudFoundry.AppSpec
CI. Specify the following required properties:- App Name: Application name to use.
- Build Pack: Build pack to use (for example, Java, Go, Binary, and so on). To specify a custom build pack, fill in the Custom Build Pack URL property instead.
Configure Cloud Foundry services
To configure Cloud Foundry services:
- Under Applications, create an application (
udm.Application
) and deployment package (udm.DeploymentPackage
). - Under the deployment package, create a
cloudFoundry.Services
CI. - Specify the Service Type.
Push an application to Cloud Foundry using a manifest
To push an application to Cloud Foundry:
- Under Applications, create an application (
udm.Application
) and deployment package (udm.DeploymentPackage
). - Under the deployment package, create a
cloudFoundry.ManifestModuleSpec
CI. - In the File property, specify a ZIP file that contains the manifest file and artifacts required to create the application.