Below table lists the current methods that can be utilized for transferring FDW or ODW data to GE SaaS EMS Platform. Please reach out to EMS platform engineering team to discuss technical details when needed. In first 4 options, the sending party should check completion of each data transmission and be able to resend data when needed.
| Data Transfer Method | Suitable Data Types | Data Action | Authentication | Protocol | Tooling | Pros | Cons |
| Azure SFTP | - FDW - ODW | PUSH to GE SaaS | - Username & Password - SSH Key | SFTP | SFTP Clients | - Easy to deploy - Encryption at rest - Directory copy allowed | Documented limitations |
| Azure Blob Store | - FDW - ODW | PUSH to GE SaaS | Service Principal | HTTPS | - AzCopy - Azure Rest API - Azure SDK | - Easy to deploy - Encryption at rest | No directory copy |
| EMS Rest API | - FDW - ODW | PUSH to GE SaaS | Username & Password | HTTPS | Rest API | - Periodic server maintenances (temporary service interruption expected) - Performance should be observed - No directory copy | |
| EMS SFTP | - FDW - ODW | PUSH to GE SaaS | - Username & Password - SSH Key | SFTP | SFTP Clients | - Easy to setup - Directory copy allowed | - Periodic server maintenances (temporary service interruptions expected) - Not available to new customers |
| Wasabi | - FDW - ODW | PUSH to GE SaaS | Username & Password | HTTPS | GEAero Wasabi Client | - Auto forwarding - Retrial on failures - Directory copy allowed | - Client tool config & installation - Periodic server maintenances (temporary service interruptions expected) - No active development |
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article