Demo Points:

1. Reduces Development time

2. Rules capability
Key Points:
Customers and developers ( build apps)
3. Whole authentication and security aspect of these apps eg forging data or transaction
4. Ease with Expose, document, developers can acess the APIs for production (backend
integration)

Demo
1. How it integrates with backened system
( Expose Rest or SOAP service ) Just want to show particular context sensitivity , rule engine,
security (processing logic is on Trujunction)
2. Show all the connectors , all we can connect, even if they are not exposing any services
There is method the connectors send a respond from backend
IA what all will reside on mobile app at the trujunction level
To what service , what service will read,add or delete etc
Steps: Define, Operations of those entities, integration, last step create endpoint services
Developers can use these endpoint services to create the mobile apps
Developer need not worry on backend services, from which backened it is coming, Developer
can just focus on Development.
Finally we will get
Along with that we can demo Rules etc
Developer perspective We have client SDK,

TJ can be used in following scenarios

Developer Ecosystems by exposing enterprise services as REST JSON services
Connecting mobile apps with SOAP based enterprise Systems
App connecting to multiple backend systems and External internet
Offline data access on Mobile Apps
Quick App development is required for Mobile Apps

Questions:
13-21 By Trujunction?? Firewall?? Security?
With their APIs?
Client APIs easy accessible or not?
Error code ?? already have? Or we have to implement?
147489

Key Point:
1. End to end Mobility Enterprise needs
Storage caching- Server side caching data storage, user doesnt have to suffer. Always
latest data can be taken
DAR Client SDK module have
Notification only leverage our APIs, we will take care of integration

Marketing: