Oracle Mobile Cloud Service (MCS for short) is Oracle's Mobile Backend as a Service (MBaaS) offering. MCS enables companies to create and deploy scalable, robust, and secure mobile applications quickly and easily, and empowers developers to leverage enterprise IT systems—without having to get IT involved. With MCS, you get:
Many of today's cloud offerings are simply existing technologies that were repurposed and shoehorned into the cloud. By contrast, Mobile Cloud Service was designed and built from the ground up, specifically to capitalize on all the affordances provided by the cloud. In addition, Mobile Cloud Service offers continuous lifecycle management, API management, built-in security and security mediation, versioning, and easy deployment between environments (Development, Staging and Production).
Mobile Cloud Service addresses the top-of-mind concerns in departments spanning your entire organization.
Mobile App Developer
Mobile app developers use MCS to line up and test the resources they need for their apps to work. This includes selecting from MCS platform APIs and custom APIs, and collaborating with other team members to create new custom APIs.
Mobile Program Manager
The mobile program manager is charged with the overall success of a company's mobile initiative. Using Mobile Cloud Service's dashboards and analytics tools, the mobile program manager can easily see how mobile users are using the applications, backends, and APIs, and answer questions like, "Are the users enjoying a high degree of success with the app, or are there some areas of the apps where the users seems to have problems?"
Enterprise architects are concerned with the strategic direction of the mobile initiative, ensuring that the tactical implementations meet the strategic needs of the company. They also set the security policies and other environment policies that govern mobile deployment. MCS provides an array of tools to help the enterprise architect complete these tasks successfully.
Mobile Cloud Administrator
The mobile cloud administrator is charged with monitoring MCS and ensuring that everything is running smoothly. MCS provides an extensive diagnostic dashboard to help the administrator with this task, and to handle other admin tasks like adding and removing users.
To help simplify mobile app development, Mobile Cloud Service provides these built-in APIs:
Mobile Application Accelerator (MAX) is a new feature of Mobile Cloud Service that enables non-technical citizen developers (such as business analysts or power users) to quickly compose an on-device mobile application. It supports a browser-based development, that allows you to edit, test, and publish mobile apps all from a browser console. You can preview the application with live data using the browser console, without having to deploy to device simulators. There is absolutely no coding required, and deploying the application is as simple as scanning the QR code from your mobile device to trigger the application download process.
Restricted use of Oracle Mobile Application Framework is included with your Oracle Mobile Cloud Service subscription. For the exact language and terms of the restricted use, please refer to ”Oracle Platform as a Service and Infrastructure as a Service – Public Cloud Service Descriptions” document in the Oracle Cloud Services Contract page. To summarize:
No. Mobile Cloud Service can leverage and work with other Oracle Platform As a Service (PaaS) and Software as a Service (SaaS) solutions, but nothing is required for an MCS subscription.
Mobile Cloud Service was designed with enterprise security baked right in. Mobile applications automatically have access to MCS security features through the mobile backend, a logical grouping of resources for an app or group of apps. Among other things, the mobile backend provides the gateway for your app to access MCS assets through basic auth and/or OAuth2.0. This means that all the resources provided by MCS are protected by default, such as storage in collections, custom API endpoints, and more. Permission must be granted to access these resources through role-based access (RBA). MCS propagates identity from the mobile user into backend enterprise systems, using standards such as Basic Auth, SAML 2.0, and UserName Token profiles. Finally, MCS can integrate with on-premise security infrastructure such as Oracle Access Manager or Active Directories, which allows mobile application to authenticate with enterprise SSO credentials.
You can learn more about MCS by checking out the MCS eBook. Then contact your Oracle Sales Representatives if you’re interested in subscribing.
A full set of training videos, spanning a range of topics from overview through feature deep-dives, are available on Oracle Mobile Platform YouTube channel. You can subscribe to the channel by clicking this link.
You can ask questions in the Oracle Mobile Cloud Service Community page.
The current subscription pricing for Mobile Cloud Service is listed on the Pricing tab, and is based on two criteria: API Calls and Storage. The amount of API Calls and Storage you get is based on the terms you have set up with your Oracle Sales Rep. There is also a minimum number of API Calls you must subscribe to per month, as described on the Pricing tab.
You get one development portal plus a runtime environment. You would typically subscribe to three environments for development, testing/staging, and production uses. You have the flexibility of subscribing to any number of environments, while managing the full lifecycle of each of the environments.
An API Call includes any API Call and notifications made between the mobile application and Mobile Cloud Service. For example, in a span of 24 hours, a user uses a mobile application that makes five calls to MCS, and receives two push notifications from MCS. That makes a total of seven API Calls for that day.
No. An API Call is counted only for calls or notifications between MCS and mobile applications. Calls between MCS and backend services are not counted as API calls.
Storage is defined as the amount of block storage within MCS used by mobile applications. For example, suppose a mobile application uploads ten pictures sized at 1 MB each to a storage collection in MCS. This means that 10 MB of Storage space will be counted towards this subscription.
You can purchase additional capacity as extra API Call Packages or Storage Packages. See the Pricing tab for details.
The number of API Calls is calculated across all MCS environments and reported as a single bundle. The total number of API Calls is then compared against the number of API Calls your subscription entitles you per month. For example, let’s say the following API Calls occur as follows over a given month:
Total execution time for page wcsHomepageExLayout is:281ms
Call opcMetaData ran 1 times with an average time of 1.00ms and a total time of 1.0ms
Call navBarMenu ran 1 times with an average time of 1.00ms and a total time of 1.0ms
Call opcFooter ran 1 times with an average time of 0.00ms and a total time of 0.0ms
Call wcsContactandFooter ran 1 times with an average time of 1.00ms and a total time of 1.0ms