Upload files to the EFS file system for data storage so that the elastic runtime environment can use them.
You can upload the following types of files:
•Flat files for a flat file connection in tasks
•Parameter files for mapping tasks
•Supplementary files like JAR files and libraries for certain transformations and connections
Uploading parameter files
Upload parameter files to data storage so that the elastic runtime environment can use them.
Store parameter files under the file system mount point.
Uploading flat files for flat file connections
Upload flat files to data storage so that you can use them in a flat file connection in tasks.
Upload flat files to the EFS file system for data storage using the following location:
/etc/infa/pod/<elastic runtime environment ID>/
To find the elastic runtime environment ID, open the Runtime Environments page in Administrator and copy the elastic runtime environment 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.
When you create a flat file connection, set the directory to /etc/infa/pod/<elastic runtime environment ID>/. For more information about flat file connections, see the help for the appropriate connector.
Uploading supplementary files
Supplementary files include JAR files and libraries that certain transformations and connections need. Upload supplementary files to data storage so that the elastic runtime environment can use them.
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
1Create directories under the file system mount point to store the files.
For example, if you create a /mnt/efs directory to use as the file system mount point, you can create a /mnt/efs/jdbc directory to store JDBC drivers.
2Copy the supplementary files to the appropriate directories.
3Use the REST API to update the supplementary file specification.