2. Create and Shape Effective APIs and Microservices for Mobile Apps and Chatbots
Parvez Syed Mohamed
Sr. Principal Product Manager
Oracle Mobile Cloud Service
April 2017

4. Program Agenda Case Studies & Solutions Express API Demo1
Case Studies & Solutions
Express API Demo
Connecter Demo
ChatBot APIs 2 3 4

5. Case A - Apps in Remote Locations
Poor Network Connectivity
Constraints
Rural India
Implement Caching
Reduce latency
Allow bulk download
Solution? 1 2 3
MCS - Data Offline and Sync APIs

6. MCS – Data Offline and Sync
Sync Express for JavaScript and Cordova
var mcs_config = {
"logLevel": mcs.LOG_LEVEL.INFO,
"mobileBackends": { "myBackend": { ... } }
"syncExpress": {
"policies": [ {
"path": /mobile/custom/myApi/departments/:deptId(\\d+)/:_employees?/:empId(\\d+)?' } ] };
Just specify the rest resource and we take care of the rest. When the device goes offline, the REST resource is available for offline use and then synchronized when the device goes online.
If you have extensive polices on objects, and want to either specify client or server wins, you would need to use our syncronization API for Native platforms
Click here to learn more

7. Case B: Personalized Apps - Employee Self Service
A time card app
Build a personalized apps for Employees and Managers
Oracle Confidential – Internal

8. Case B: Personalized Apps - Manager Self Service
Oracle Confidential – Internal

9. MCS –Mobile Users Extended Operations API
Response
Custom Code {
"id":"295e450a-63f0-41fa-be43-cd2dbcb21598",
"username":“dcole", "firstName":“Dylan",
"lastName":“Cole",
"roles": [ “Sales Consultant" ],
….}
req.oracleMobile.ums.getUserExtended().then( function(result) {
res.send(result.statusCode, result.result); },
function(error)
res.send(500, error.error);
} );

10. Case C: Brocade Unified Mobile Application (BUMA)
Solution Objectives
Unified Mobile app : For Oracle EBS, Salesforce and MS Outlook.
Automate Oracle EBS : Approvals and iExpense creation process.
Streamline workflow: Better tracking, better approvals and all records managed online.
Reduced Process Time : Improve the per transaction time from days to few minutes and thereby achieve better efficiency.
Salesforce cloud integration : For viewing and managing CRM Opportunities.
View MS Outlook Calendar appointments in same mobile app.
Integrate SFDC and MS Outlook calendar : To enable create events from SFDC to Calendar.
The business objective for Brocade was to create a cross platform mobile application for extending the Oracle EBS ERP modules of iExpense and Approvals. Brocade wanted to leverage the enterprise security and login mechanisms which was built using Microsoft AD for user authentications and OAM/OID for authentication & authorization with Oracle EBS ERP. In addition to extending Oracle EBS iExpense and Approvals module, Brocade also wanted to take ‘Lead’ and ‘Opportunity’ data from ‘Salesforce’ and create a single mobile app to manage Oracle iExpense, Approvals and Salesforce Lead & Opportunity. The same has to integrate with MS Outlook Calendar to show the appointments on mobile.
The user also need to get real-time push notifications for approvals alert, have offline feature for working when no data connectivity, have secure application and user management.
Technology:
Brocade communications IT system consists of Oracle EBS 11i for enterprise resource planning. They use Salesforce for CRM management. They have OAM/OID for identity management and authorization. Microsoft AD is used as corporate LDAP for SSO authentication. The company was early to adopt mobility and only had “purchase requisition” approval mobile app, which was very basic with respect to User experience and functionality as well as features.
The mobile application had to be developed in short time frame i.e. 6 weeks with real-time Oracle EBS integration. The requirement was for one mobile app, which can be run on both iOS and Android phones/ tablet.
The other major technical challenges were to establish a secure login from mobile app using an LDAP directory service for Brocade using the federated services.
Interfacing with multiple systems like Oracle EBS, Salesforce and MS Outlook was always a challenge, and all systems need to be authenticated using a single security credential (SSO). Enabling Push notifications for real time alerts in this time frame was a technical requirement. Also, Brocade wanted to have user and application access control (i.e. all users in AD /Oracle EBS need not access mobile app).

11. Building Good Mobile Apps is Hard, Expensive and Slow
Speaker’s Notes: So now the mobile developer has to figure out
What tool will they use to build the mobile, native or cross platform ?
How do they integrate to these multiple systems of record – 7 in this case
What are the user identity policies for these backend systems. They may be different based on the authentication policy of the backend
IT would need to provide environments for dev, test and prod – multiple environments since the app is not static and will have continuous development
What about adding mobile services like the ability to work in an offline mode, to get push notifications, add geo coding to the employee record
What about diagnostics, analytics to determine how the app is performing, who is using the app etc
In summary, there is a lot that goes on in building a mobile app. Building the UI becomes the easy part. The hard part is managing all these other areas.
Multiple
Environments
Mobile
Services
Monitor & Analyze
Client Dev
Tools
Security
Integration

12. Oracle Mobile Cloud Service
Web
Voice
Messaging
Analytics
Mobile
Oracle App Development Tools
3rd Party App Development Tools
Client SDK / API
Mobile Services
(Push, Sync, LBS…)
Customer experience analytics
Intelligent Bots
Artificial Intelligence
Cross Channel Data Aggregation
Mobile APP Integration (Mobile core)
AI / ML
Mobile API Catalog
API Shaping
Connectors
ORACLE APPS
3RD PARTY APPS
CUSTOMER APPS

13. Mobile Core
Express API Demo

14. Mobile Core
Connectors Demo

15. We are in a new world where conversational interfaces will replace the most common interfaces on computers and connected devices
Millennials love to chat. Their personal lives rotate around messaging and instant gratification. From getting their pals’ views on a new t-shirt they are thinking of buying to sharing their New Year’s resolutions publicly, Gen Z, which comprises the majority of the workforce today, lives an instant and synchronous life, one that is built on the foundations of consumerism. We are also living in a time where we are facing Mobile App fatigue and are unable to deal with the number of apps on our mobile device.
It is only natural that people’s preferences at work mirror those of their personal lives. And we are witnessing a paradigm shift in the way people work. The asynchronous nature of makes it one of the most hated forms of office communication today. Anyone who has ever tried to ask a question, make a suggestion, or request an approval through will understand the anxiety and subsequent loss in productivity caused by an excessive dependence on .
Popular communication platforms like FB Messenger, Line, WeChat, Slack, that facilitate instant messaging are playing a pivotal role in the way enterprise are beginning to engage with consumers and in the future of our workplaces. By reducing the threshold to starting a conversation or voicing a concern, these platforms are democratizing information. They help inculcate ideas and values that are near and dear to millennials. These platforms are taking the good ol’ corporate open-door policy to the next level. By keeping conversations and discussions synchronous, the workforce is working in a way it loves to. Just as the early innovation in enterprise software liberated people from the inconvenience of paperwork, the new enterprise tools are aimed at enabling a more potent collaboration experience.

16. Oracle Bots: AI Flow Channel Integration Intent Classification
Entity Extraction
Dialog Execution
Channel Agnostic
Webhook
Security
Message Processing
Intent Modeling
Natural Language
Linguistic Modeling
Bot Model Training
Entity Parsing
Entity Resolution
Entity Type
Entity Value
YAML Dialog Flow
Dialog State
Built Component
Custom Component
The balance in your checking account is $
Integration
Component
Enterprise data
Required Entities:
Account Type
Entity Values
Checking Savings
Credit
NL Understanding
Intent Classification:
Balances
Intent Ranking
Confidence  98%
Alexa…what’s my balance
For which account?
Savings

17. APIs for BOTS Key take Away Don’t make the user wait too long!!
Reduce number of REST calls
Pre-fetch and cache data
Keep data close to the end user
Fine tune API payloads