-
Notifications
You must be signed in to change notification settings - Fork 80
Building applications for TIBCO BusinessWorks Container Edition in PCF
POM GENERATION
When the PCF platform is selected in the POM Generation UI, for deploying the applications to Pivotal Cloud Foundry, PCF environment-specific details have to be filled in.
GUIDELINES FOR SPECIFIC PCF FIELDS
-
PCF Server Name = PCF_UK_credential (Define this as <\server> inside your config/settings.xml of Apache Maven Home)
PCF_UK_credential admin xxxxxxxxxxxx -
App Memory: Minimum should be 1024 MB
-
App Buildpack: BWCE buildpack which developer has pushed to PCF instance
-
Select Services: Button where you login to PCF and select required services you want to bind to your app
PROPERTIES FILES
-
pcfdev.properties and pcfprod.properties files are generated by default, with variable name as pcf.property.file .
-
For more environments, one of these properties file can be copied and renamed it to the other environment (eg. pcfqa.properties) . Its values can be customized for required environment.
GOALS FOR CLOUD FOUNDRY
-
Execute Maven Build goals such as cf:push , cf:scale etc.
-
While executing the goals, provide your credentials using system arguments: -Dcf.username and -Dcf.password .
-
You can try other goals from studio, by creating new Maven Run Configurations for different goals , or from terminal pointing to your workspace using 'mvn initialize cf:command -Dpcf.property.file=pcfdev.properties'
NOTE: For all non-web application if you are using PCF Elastic Runtime 1.6 or above (Diego) then, it will give health-check error while cf:push, so you have to use PCF CLI (6.13 or above) to set health-check as 'none' after pushing your application and re-push after setting health-check as 'none'. You can use below command on CLI - cf set-health-check App_Name none
- Please refer to http://docs.run.pivotal.io/buildpacks/java/build-tool-int.html for detailed PCF-specific information.
Getting started
- Steps to Mavenize BW Application
- Building applications for BWCE
- EAR deployment with Config File
- Shared Modules with Maven
- Add Process Diagram in EAR
- BW Design Utility Goals
- CI/CD using Jenkins
- Custom XPath Function
- Deploy Shared Module on Remote Repository
- TCI Deployment using Maven Plugin
Unit Testing
- Primitive Assertion
- Activity Assertion
- Activity Assertion with Gold Input File
- Mock Output
- Mock Fault
- Test Suite
- Plugin Properties
Help & Contribute