In this Page
A few sample pipelines may be provided to each organization when the account is created. Additionally, step-by-step examples are available in the Use Cases section of the documentation.
Development and testing has primarily been done with:
The recommended minimum screen resolution is 1024 x 768.
SnapLogic was vulnerable to Heartbleed, but the services were patched early the week of April 7th in Amazon's update to their platform. We advise, as a precaution, that customers should change their passwords to avoid risk. We will continue to keep customers informed if there are any known breaches as a result of this or other vulnerabilities.
Currently only desktop devices are fully supported.
Touch screens are not supported.
Tentatively, expect updates every quarter, though urgent patches may be made available in between releases. When the site is refreshed, you may need to clear your browser’s cache file to make sure you are accessing the latest code.
Each organization has a user with Admin rights. This Organization Admin can add users to the organization by logging into the Manager and clicking the Users link. On the User Details page, permissions can be set to provide the necessary access for that user.
See the Data Snaps section under Snap Reference for the list of supported databases
Yes, as long as it is visible to our production instance running in AWS or you have an on-premises Snaplex enabled.
Files on a local machine can be accessed if an on-premises Snaplex is configured in that location. Source/Feed files should be uploaded to sldb using the Manager. This location is also used for retrieving output files.
Select Pipeline Runtime from the Dashboard.
Currently, pipelines can be run from within Designer or from the Task scheduler (available in the Manager).
Pipeline execution will fail. Currently, unavailability of the endpoint is only checked at pipeline runtime. In the future, there will be some semantic validation done at design time as well.
No. A pipeline runs in its entirety. However, you could split a pipeline manually to run it partially.
Email notification is available for scheduled pipeline runs.
SnapLogic does not store your data. Data is kept wherever you set your endpoints to write to.
Files uploaded to SLFS have a 100MB per file limit. There are limits on the number of concurrent triggered pipelines and total triggered pipelines per day, these limits vary based on the size and number of Snaplexes. There are no limits currently on non-triggered pipeline executions.
See the "Snaps" topic in the sidebar.
Since the new SnapLogic is a cloud-based service - there is no concept of local files. Files can be fetched from many places.
Navigate to the “Files” tab from within the Manager. This will show you files that have been uploaded - and from here you can upload files from your local computer. To use a file in sldb (SnapLogic database) in a pipeline property you must use the sldb scheme: sldb:///Snaplogic/alpha/<your file path>. This can be used for output files as well. Read more about the file system.
Example:
select m.smtpid as message_id, m.messagedt as date, s.email as from_address, s.name as from_name, m.subject as subject, b.body as body from messages m join people s on m.senderid=s.personid join bodies b on m.messageid=b.messageid limit 10;
Yes. Click the Run Pipeline button in the toolbar. While a pipeline is running, you can click the stop button to stop execution of the pipeline.
When a pipeline is running, Snaps will have a yellow background color. When a Snap has completed, it will have a green background color of it's completed normally, and a red background if it has completed with a failed state
After you've started a pipeline, you can click on the Check Server Response button to open the server response window. This window will automatically refresh when the server has new status information
Yes. You can have multiple tabs open at the same time, each with a different pipeline.
Click the icon on the top right hand side of Designer.
Any Snap that does not have a native library dependency (like SAP, Tableau) can be used on a Hadooplex.
These questions are for those who are familiar with SnapLogic's existing product.
In the new SnapLogic, the term Snap is used for what was previously referred to as “Components” or “Snaps”. Additionally, a Snap has been streamlined to be a succinct action.
The Components from 3.x code line can not be migrated over to the new SnapLogic. There will not necessarily be a one-to-one parity between the 3.7 Components and the latest Snaps.
Migration to the new SnapLogic is not supported at this time.
It is there. For example, if you’re using the Structure Snap, the Source Schema and Target Schema fields are in fact introspecting the source and the target (i.e. working as Suggest).