Good morning,
At the moment, we're exploring the possibilities of using OutSystems as a SCIM provider. From OutSystems, we want to synchronize data to other applications. Some of these applications only support the SCIM protocol.
In my research into the possibilities, I've come across options for synchronizing into OutSystems, but we actually want to synchronize from OutSystems to other parties.
Are there people who have experience with this and are willing to share it with us?
Thanks in advance!
Regards,
Bart
1. Deploy to OutSystems Platform: This is a straightforward option where you can deploy your application directly to the OutSystems Platform, a cloud-based service that helps you host and manage your applications. It's like putting your app in a big, secure box that's accessible from anywhere.
2. ZIP Archive: This option lets you export your application as a ZIP archive. A ZIP archive is like a suitcase that contains all the necessary files and stuff for your app to work. You can open this suitcase on any computer, and it'll have everything your app needs to run.
3. WAR Archive: This is another way to export your application, similar to the ZIP archive, but in a different format called WAR (Web Application Archive). A WAR file is like a treasure chest that has all the important stuff for your app to work on a web server. It's a bit more organized than a suitcase, but it still has everything your app needs.
4. WAR for GlassFish: This option is similar to the WAR archive option, but it's specifically designed for deployment on the GlassFish application server. The GlassFish server is like a big, powerful computer that helps your app run smoothly. This option makes it easy to bring your app to the GlassFish server.
5. WAR for WildFly: This is similar to the WAR archive option, but it's specifically designed for deployment on the WildFly application server. The WildFly server is another big, powerful computer that helps your app run smoothly. This option makes it easy to bring your app to the WildFly server.
6. WAR for JBoss: This is similar to the WAR archive option, but it's specifically designed for deployment on the JBoss application server. The JBoss server is yet another big, powerful computer that helps your app run smoothly. This option makes it easy to bring your app to the JBoss server.
7. WAR for Geronimo: This is similar to the WAR archive option, but it's specifically designed for deployment on the Geronimo application server. The Geronimo server is yet another big, powerful computer that helps your app run smoothly. This option makes it easy to bring your app to the Geronimo server.
8. WAR for MyFaces: This is similar to the WAR archive option, but it's specifically designed for deployment on a MyFaces-based application server, such as GlassFish or Tomcat. MyFaces is like a special helper that makes it easier for your app to work with the server.
9. WAR for Seam: This is similar to the WAR archive option, but it's specifically designed for deployment on a Seam-based application server, such as GlassFish or Tomcat. Seam is like a special helper that makes it easier for your app to work with the server.
10. WAR for JSF: This is similar to the WAR archive option, but it's specifically designed for deployment on a JSF-based application server, such as GlassFish or Tomcat. JSF is like a special helper that makes it easier for your app to work with the server.
11. WAR for Struts: This is similar to the WAR archive option, but it's specifically designed for deployment on a Struts-based application server, such as GlassFish or Tomcat. Struts is like a special helper that makes it easier for your app to work with the server.
12. WAR for Velocity: This is similar to the WAR archive option, but it's specifically designed for deployment on a Velocity-based application server, such as GlassFish or Tomcat. Velocity is like a special helper that makes it easier for your app to work with the server.
13. WAR for Tiles: This is similar to the WAR archive option, but it's specifically designed for deployment on a Tiles-based application server, such as GlassFish or Tomcat. Tiles is like a special helper that makes it easier for your app to work with the server.
14. WAR for Facelets: This is similar to the WAR archive option, but it's specifically designed for deployment on a Facelets-based application server, such as GlassFish or Tomcat. Facelets is like a special helper that makes it easier for your app to work with the server.
15. WAR for Velocity and Tiles: This is similar to the WAR archive option, but it's specifically designed for deployment on a Velocity-based application server, such as GlassFish or Tomcat, and a Tiles-based application server, such as GlassFish or Tomcat. This option is like having two special helpers, Velocity and Tiles, working together to make it easier for your app to work with the server.