-
Notifications
You must be signed in to change notification settings - Fork 82
Building applications for TIBCO BusinessWorks Container Edition
This plug-in is subject to the license shared as part of the repository. Kindly review the license before using or downloading this plug-in.
It is provided as a sample plug-in to support use-cases of integrating TIBCO BusinessWorks™ Container Edition 1.0.0 and higher with Apache Maven.
PREREQUISITES
- Maven should be installed on the Machine. M2_HOME should be set. The Maven Executable should be available in the Path. This can be confirmed by running the command mvn -version from Terminal/Command Prompt.
- TIBCO BusinessWorks™ Container Edition should be installed.
- Configure Maven Installation Version in studio using the steps given in the link https://github.com/TIBCOSoftware/bw6-plugin-maven/wiki/Troubleshooting#configure-maven-installation-and-local-m2-repo-location-in-eclipse
INSTALLATION
a. Goto https://github.com/TIBCOSoftware/bw6-plugin-maven/releases
b. Download TIB_BW_Maven_Plugin_x.y.z.zip
c. Unzip the file in a folder on local drive.
d. Open the Terminal and run install.bat ( for Windows based OS ) or install.sh ( for Unix based OS)
e. The Installer will ask for TibcoHome location. Provide the TibcoHome to the Script.
This will install the Maven Plugin to the TibcoHome.
STEPS FOR BUILDING THE APPLICATION
Running the Maven Build from Studio
a. Open the Studio.
b. Right-Click on the Application project.
c. The Context Menu will show the option "Generate POM for Application".
d. Clicking it will launch the POM Generation UI as shown below.
e. There are two platforms supported by this plugin -
-
CloudFoundry: Please refer to https://github.com/TIBCOSoftware/bw6-plugin-maven/wiki/Building-applications-for-TIBCO-BusinessWorks-Container-Edition-in-PCF
-
Docker + Kubernetes/Openshift: Please refer to https://github.com/TIBCOSoftware/bw6-plugin-maven/wiki/Building-applications-for-TIBCO-BusinessWorks-Container-Edition-in-Docker-and-Kubernetes-or--Openshift
NOTE - For Docker/Kubernetes you also need to download gCloud-sdk and kubectl (CLIs), and make sure you add them to your path environment-variable.
h. The Project will be converted to Maven (Eclipse Project) nature. Note the workspace will index after generating POM files for the first time and may take some time. You can continue with the steps below by allowing this indexing to run in the background.
- You will find parent project will get created in your workspace with a pom file.
- You will find the platform specific properties files, which are explained in more detail in the articles for the specific platforms referenced by the links above.
i. Open Run/Debug Configurations. Create a new Maven Build.
j. Under the "Base directory" choose add variable for pom location choose ${project_loc} or browse parent project as workspace.
k. In the 'Goal' enter the goal to be executed.
-
Make sure you add initialize before all maven goals.
-
'package' goal is standard Maven goal, which is independent of cloud platform and can be executed to create application 'EAR'.
-
There are platform-specific goals for Docker, Kubernetes/Openshift and PCF, which are explained in detail in the platform-specific articles referenced by the links above.
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