Changes in Functionality
The following functionality and features have been changed in this release of TIBCO Control Plane and capabilities.
TIBCO Control Plane
You can now update Observability resource configuration at data plane level. For more information, see Configuring Observability Resource.
TIBCO BusinessWorks Container Edition Capability
-
From this release onwards, the install goal does not deploy the EAR. The install goal only installs the artifacts in the local maven repository. For any deployment and pushing artifacts to a remote repository, the deploy goal must be used.
Remote repository must be configured in the parent
pom.xml
file in the below format before using deploy goal. For example,<distributionManagement>
<repository>
<id>remote_repo</id>
<name>remotem2repo</name>
<url>remote_repo</url>
</repository>
</distributionManagement>
-
For Push to Platform option, you can now select appropriate values from dropdown to create build. Once the apps are successfully pushed you can deploy the apps using the Managed By BW Provisioner or Managed By Helm Charts options. For more information, see Deploying TIBCO BusinessWorks Container Edition applications using Push to Platform .
TIBCO ActiveMatrix BusinessWorks™ 5 and TIBCO ActiveMatrix® Adapters
Machines connected to TIBCO ActiveMatrix BusinessWorks™ 5 domains can be monitored under BW5 and Adapters Product Card.
TIBCO Flogo Capability
-
It is now mandatory to accept the End-User Agreement (EUA) to deploy apps via both V1 and V2 APIs.
-
On the Data Plane home page, in the Applications section, the Deploy an App option now only creates the app build. Previously, this option combined two functionalities: creating the app build and deploying the app. To deploy an app, see Deploying an App Build.