![\"Oracle](\"http:\/\/iamwcew.fr.oracle.com\/blog\/wp-content\/uploads\/2016\/06\/mcsgs_dt_015_mobile_bkend.png\")
<\/a><\/p>\n
Cr\u00e9ation de services pour MAX<\/h3>\n
cf documentation Creating Services for MAX<\/a><\/p>\n Important<\/a>:<\/p>\n The apps that you create using MAX are specific to the needs and activities of an organization. They\u2019re meant for internal use, so you don\u2019t need to download them from an application market like the iOS App Store or Google Play<\/em><\/p>\n Unlike MCS developers, the business users are MAX-only users. They never see MCS (and can’t log into it).<\/em><\/p>\n he MAX user interface recasts APIs as services that group together the business objects.<\/p>\n In MAX you need business objects, not endpoints, to wire your UI to data. Whether you\u2019re creating an API specifically for MAX, retooling an existing one, or using MAX to test your API, you need to define JSON schemas for the endpoints.<\/p>\n In MAX, POST methods are always used for fields used for create actions. Read actions are always GET methods.<\/p>\n The ICS Connector API enables a mobile backend to act as a gateway to the enterprise backend.<\/p>\n In MCS, the Oracle Credential Store Framework (CSF) is used to manage credentials in a secure form. A credential store is a repository of security data (credentials stored as keys) that certify the authority of users and system components. CSF lets you store, retrieve, update, and delete credentials (security data) for a web service and other apps.<\/p>\n Oracle Mobile Cloud Service (MCS) provides the Sync Client SDK and its supporting Data Offline API for caching MCS custom and REST resources in an efficient, uniform and transparent way. The Sync Client SDK, along with the Storage SDK, also provides support for caching storage objects.<\/p>\n The Storage API enables your mobile app to store, update, retrieve, and delete media, such as JSON objects, text files, and images, in collections in your MCS environment. The media are stored as opaque<\/span> objects, which means that each object is stored and retrieved from the collection by a a user- or system-generated GUID (globally unique ID). You use mobile user roles to control who can read and write the objects in the collection.<\/p>\n Note that this API isn\u2019t intended to act as a database-as-a-service (DBaaS) solution by storing business data used by external systems, nor is it intended to host HTML 5 applications as a content management system (CMS) would.<\/p>\n In Oracle Mobile Cloud Service (MCS), all resources are secured and can only be accessed by authenticated users. As a mobile app developer, you specify the authentication method in the mobile backend and then write app code to use that authentication method.<\/p>\n The authentication methods available are:<\/p>\n If you want to use your own identity provider to authenticate users of your apps, you can enable Oracle Cloud\u2019s single sign-on (SSO) capability to connect with that identity provider and then configure your mobile backends to use it. This is particularly useful if you are rolling out apps for your company\u2019s employees and you want them to be able to sign into the apps using their existing employee login credentials. Similarly, this could work for consumer applications where the customers already have user accounts for corresponding web applications.<\/p>\n If you develop hybrid mobile apps based on the Apache Cordova framework, you can use the SDK that Oracle Mobile Cloud Service (MCS) provides for Cordova. This SDK simplifies authentication with MCS and provides native wrapper classes for MCS platform APIs.<\/p>\n The Cordova SDK doesn\u2019t support the Data Offline and Sync API.<\/p>\n Location devices, places and assets provide the tools you need to create location-aware mobile apps.<\/p>\n A location device<\/span> is any device that provides location services, like a Bluetooth proximity beacon. Location devices transmit an ID within a defined space, so mobile apps can use these signals to trigger notifications and other actions. MCS currently supports the following location protocols:<\/p>\n A place<\/span> is a physical location associated with one or more location devices. You can define places through the MCS UI or by uploading a CSV file.<\/p>\n An asset<\/span> is a physical object that\u2019s associated with one or more location devices, typically something mobile and valuable like a forklift or hospital bed. You can define location assets through the MCS UI or by uploading a CSV file.<\/p>\n A location device<\/span> is any device that provides location services, like a Bluetooth proximity beacon. You can define location devices through the MCS UI or by uploading a CSV file.<\/p>\n Make your mobile apps location-aware by querying for location devices, places and assets using the Location Platform API.<\/p>\n The Location Platform API allows you to query about location devices and the places where they are located. These requests can be performed anonymously or by a user with access to a realm associated with the mobile backend where the device is registered.<\/p>\n cf post\u00a0Suhas Uliyar<\/a><\/p>\n Use case<\/p>\nOffline<\/h3>\n
Authentication Service<\/h3>\n
\n
Location Services<\/h3>\n
\n
\n
Uses Cases<\/h4>\n