Upload parameter files and supplementary files to the EFS for system storage to allow tasks to access parameter configurations and custom dependencies.
You can upload the following types of files:
•Supplementary files, such as JDBC drivers, third-party libraries, license files, and custom scripts
•Parameter files for mapping tasks
Uploading custom drivers, libraries, and scripts
To access dependencies in mappings and tasks, such as JDBC drivers, third-party libraries, license files, and custom scripts, upload the supplementary files to the EFS for system storage.
You can upload the following supplementary files:
•Database drivers
•JAR files and Java libraries for the Java transformation
•Native libraries and executables
•SAP connectivity drivers and libraries
•SSL/TLS certificates and keystores
To upload the files, perform the following steps:
1In Administrator, get the elastic runtime environment ID.
aOpen the Runtime Environments page.
bNext to the elastic runtime environment, open the Actions menu and select Edit.
cCopy the ID from the URL.
For example, in the URL https://usw1.dmr-us.informaticacloud.com/cloudUI/products/administer/main/elastic-agent/KUBERNETES/0141GU25000000000002/overview, the elastic runtime environment ID is 0141GU25000000000002.
2SSH into the master node.
3Navigate to the file system mount point:
cd /mnt/system_disk
Note:
During cluster deployment, the cluster installer automatically provisions an EFS mount point for system files. The directory /mnt/system_disk acts as a logical alias that maps to the following EFS path:
/mnt/<file system ID>/<access point>/sys
For example:
/mnt/fs-06ee607d6bac45c8d/idmc-qa-sysdisk-ap/sys
4Navigate to the subfolder that has the same name as the elastic runtime environment ID. For example:
cd 0141GU25000000000002
5Create subfolders to organize supplementary files according to their type.
For example, create a jdbc folder to store database drivers:
mkdir jdbc
6Upload the supplementary files by adding them to their appropriate subfolders.
For example, place JDBC drivers in /mnt/system_disk/0141GU25000000000002/jdbc/.
7Register the supplementary files by updating the supplementary file specification using the REST API.
To use a parameter file to pass different parameter values to mapping tasks, upload the parameter file to the EFS for system storage.
1In Administrator, get the elastic runtime environment ID.
aOpen the Runtime Environments page.
bNext to the elastic runtime environment, open the Actions menu and select Edit.
cCopy the ID from the URL.
For example, in the URL https://usw1.dmr-us.informaticacloud.com/cloudUI/products/administer/main/elastic-agent/KUBERNETES/0141GU25000000000002/overview, the elastic runtime environment ID is 0141GU25000000000002.
2SSH into the master node.
3Navigate to the file system mount point:
cd /mnt/system_disk
Note:
During cluster deployment, the cluster installer automatically provisions an EFS mount point for system files. The directory /mnt/system_disk acts as a logical alias that maps to the following EFS path:
/mnt/<file system ID>/<access point>/sys
For example:
/mnt/fs-06ee607d6bac45c8d/idmc-qa-sysdisk-ap/sys
4Navigate to the subfolder that has the same name as the elastic runtime environment ID. For example:
cd 0141GU25000000000002
5Create a folder for parameter files. For example:
mkdir parameters
6Upload the parameter files to the parameters folder.