Adobe Experience Platform Launch has been rebranded as a suite of data collection technologies in Adobe Experience Platform. Several terminology changes have rolled out across the product documentation as a result. Please refer to the following document for a consolidated reference of the terminology changes.
If you do not want to have Adobe manage your hosted libraries, your other option is to have Adobe Experience Platform deliver builds to a secured SFTP server that you host.
Platform connects to your SFTP site using an encrypted key. There are a few steps to set this up correctly:
The structure of tag builds has changed over time. They use symbolic links (symlinks) internally to maintain backward compatibility so that previous embed codes will continue to work with the latest build structure. Your SFTP server must support the usage of symlinks in order to serve as a valid destination for tag builds.
For more detailed information, refer to the following Medium article on how to set up SFTP servers to deliver a build.
Open the Hosts tab.
Create the new Host.
Name your host.
Select SFTP as the host type.
Enter the host, path, port, username, and encrypted private key.
The port must be one of the following:
As a security best practice, Adobe limits the number of ports that can be used for outgoing traffic. The selected ports are commonly allowed through corporate firewalls, plus they include some ranges for flexibility.
When you select Save, the connection and ability to deliver the files to your SFTP server is tested. Platform creates a folder, writes a file within that folder, checks to make sure the file is there, then cleans up after itself. If the user account on your SFTP server (the one attached to the secure certificate you provided to Platform) does not have the necessary permissions to perform this action, then the Host goes into a “Failed” status.