SYSTEMS AND PROCESSES OF ACCESSING BACKEND SERVICES WITH A MOBILE APPLICATION

• US 20160266882A1
• Filed: 03/13/2015
• Published: 09/15/2016
• Est. Priority Date: 03/13/2015
• Status: Active Grant

• Current Assignee: Kony, Inc. (Temenos AG)
• Original Assignee: Kony, Inc. (Temenos AG)
• Inventors: KATZ, Keith, HILDAHL, Bjorn, AGHARA, Amit, Trevathan, Matthew B., TERRY, Matthew, GUSTIN, Destry, GROSS, Edward
• Granted Patent: US 11,113,047 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 8/61 Installation
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

Systems and processes of accessing selected backend services throughout a software development lifecycle with a singly deployable mobile application is provided. The method includes deploying a mobile application a single time on a mobile device during a development lifecycle. The method further includes providing the singly deployed mobile application access to different service endpoint destinations during the development lifecycle based on one or more application policies associated with at least the mobile application.

Claims

1. A method, comprising:

deploying a mobile application a single time on a mobile device during a development lifecycle of the mobile application; and

pointing the singly deployed mobile application to selected different environments in different service endpoint destinations during the development lifecycle of the mobile based on one or more application policies associated with at least the mobile application.

2. The method of claim 1, wherein the application policies are obtained from a policy management system of an enterprise mobility management (EMM) computing system.

3. The method of claim 1, wherein the application policies are based on at least one of context and device ID.

4. The method of claim 3, wherein the application policies are based on context only, without use of device ID, and wherein the context includes at least one of time of day, location and mobile application type.

5. The method of claim 1, wherein the mobile application includes a properties file that contains a list of the service endpoint destinations, and wherein the service endpoint destinations include QA servers, staging servers, and production servers.

6. The method of claim 1, wherein the mobile application is deployed a single time on the mobile device even when there is a client-side problem in production with a specific building code.

7. The method of claim 1, wherein the mobile application moves its way through the service endpoint destinations without being rebuilt or recompiled.

8. The method of claim 1, further comprising, upon login:

returning a token based on identification information received from the mobile device deploying the mobile application; and

returning an endpoint definition of the service endpoint destinations from a remote computing system based on the returned token.

9. The method of claim 8, wherein the endpoint definition of the service endpoint destinations is returned based on context.

10. The method of claim 1, wherein the service endpoint destinations are stored locally on the mobile device deploying the mobile application.

11. The method of claim 1, wherein the application policies are dynamically applied through dynamic URLs which are hard coded, with the application policies applying a correct hard coded set.

12. The method of claim 1, wherein the mobile application includes a properties file that contains a list of all of the service endpoint destinations from QA to production, and the mobile application uses the application policies to determine which service endpoint destinations to use within the properties file.

13. The method of claim 12, wherein the service endpoint destinations are retrieved from a policy server based on context.

14. A computer program product comprising a computer readable storage medium having program instructions embodied therewith, wherein the computer readable storage medium is not a transitory signal per se, and the program instructions are readable by a computing device to cause the computing device to perform a method comprising:

receiving identification information of a mobile device deploying a mobile application;

returning a token based on the identification information received from the mobile device deploying the mobile application;

receiving at least one of the token and context from the mobile device; and

providing service endpoint definitions based on the at least one of the token and context to allow pointing the mobile application to selected different environments in selected ones of the service endpoint definitions during different stages of a development lifecycle of the mobile application.

15. The computer program product of claim 14, wherein the identification information is received by an identity manager.

16. The computer program product of claim 14, wherein the mobile application retrieves the service endpoint definitions from a policy server based on at least one of the token and context.

17. The computer program product of claim 14, wherein the identification information is a Unique Device ID.

18. A system comprising:

a CPU, a computer readable memory and a computer readable storage medium;

program instructions to deploy a mobile application on a mobile device; and

program instructions to direct the mobile application to selected different environments in different endpoint destinations during a software development lifecycle of the mobile application based on application policies associated with the mobile application,

wherein the program instructions are stored on the computer readable storage medium for execution by the CPU via the computer readable memory.

19. The system of claim 18, wherein the policies are based on at least one of context and mobile device identification, and the policies provide authorization for the mobile application to access selected ones of the different endpoint destinations during the software development lifecycle.

20. The system of claim 18, further comprising program instructions to provide a token based on an identification of the mobile device, wherein the token is used to provide access to selected ones of the different endpoint destinations during the software development lifecycle.