Supplementing Drivers
To supplement Oracle-Thin Driver and EMS driver, create a .zip file before uploading the drivers using TIBCO Cloud - Command Line Interface®.
Note:
- You must run the supplement command before you run the driver-specific applications.
- Supplementing is necessary only once for an entire organization. The subsequent application pushes by users in that organization automatically uses the supplemented plug-in.
- For the JMS applications, you can also push the application by keeping the ems.zip alongside .EAR and manifest.json, but ems.zip is available for that specific application only and not for the organization.
- While creating the .zip file, it is mandatory that all the .jar files are zipped directly into the zip folder with no parent folder inside the zipped folder.
Oracle:
- Install the driver with the
bwinstallutility. - Zip up the contents of
bwcloud/1.1/config/drivers/shells/jdbc.oracle.runtime/runtime/plugins/*com.tibco.bw.jdbc.datasourcefactory.oracle*folder (typically the contents arecom,lib,META-INF, andOSGI-INF). - Name the file
oracle.zip. - Place .zip in a newly created temp folder.
- Run the following supplement command from inside that temp folder.
tibcli bwplugin supplement oracle
EMS:
- Zip the contents of required EMS directories at:
<EMS_installation_directory>/EMS/components/shared/1.0.0/pluginsfolder. - Name the .zip file: ems.zip.
- Place this .zip in a newly created temp folder.
- Run the following supplement command from inside that temp folder:
tibcli bwplugin supplement ems
Note: If EMS drivers are not supplemented, default EMS drivers (EMS 10.2) will be used.
Note: You can also use the Web UI for supplements. For more information, see
Supplementing Plug-ins and Connectors.