AUTOMATIC CONFIGURATION OF MOBILE PROGRAMS

• US 20140372981A1
• Filed: 06/14/2013
• Published: 12/18/2014
• Est. Priority Date: 06/14/2013
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP SE
• Inventors: Said, Bare, Eberlein, Peter
• Granted Patent: US 9,632,802 B2
• Time in Patent Office: Days
• US Class Current: 717/121
• CPC Class Codes: G06F 9/44505 Configuring for program initiating, e.g. using registry, configuration files

Abstract

The subject matter disclosed herein provides methods for automatically configuring a mobile program based on a customer'"'"'s access to one or more applications. This method may maintain metadata for a mobile program in a directory. The mobile program may be configured to provide one or more services when installed on a mobile device. Each service may be associated with one or more applications. Customer landscapes identifying applications accessible by a customer may be maintained in the directory. A program identifier may be received from a mobile device of the customer. The program identifier may identify a mobile program installed on the customer'"'"'s mobile device. A configuration file may be generated based on the received program identifier and transmitted to the customer'"'"'s mobile device. Related apparatus, systems, techniques, and articles are also described.

Claims

1. A method comprising:

maintaining metadata for one or more mobile programs in a directory, the one or more mobile programs configured to provide one or more services when installed on a mobile device, each of the one or more services associated with one or more applications;

maintaining one or more customer landscapes in the directory, the one or more customer landscapes identifying one or more applications accessible by a customer;

receiving a program identifier from a mobile device of the customer, the program identifier identifying a mobile program installed on the mobile device of the customer;

generating a configuration file based on the received program identifier; and

transmitting the generated configuration file to the mobile device of the customer.

2. The method of claim 1, wherein the generating the configuration file further comprises:

accessing, based on the received program identifier, one or more service variants stored in the directory, the one or more service variants identifying a different combination of the one or more services provided by the mobile program;

for each of the one or more service variants

identifying applications associated with the combination of services, and

comparing the identified applications with the one or more applications accessible by the customer; and

selecting a service variant based on the comparing.

3. The method of claim 2, wherein a service variant is selected if the applications associated with the combination of services are all accessible by the customer.

4. The method of claim 2, wherein the identifying and the comparing of the one or more service variants are performed in a predetermined order based on a number of services associated with the service variant.

5. The method of claim 2, wherein the configuration file is generated from metadata associated with the selected service variant.

6. The method of claim 5, wherein the metadata associated with the selected variant includes at least layout information and binding information.

7. The method of claim 6, wherein the binding information includes at least an endpoint for the application and one or more communication parameters for establishing a connection between the mobile device of the customer and the application.

8. The method of claim 2 further comprising:

receiving a notification from the one or more applications, the notification indicating a status of the application transmitting the notification; and

determining that an application is inactive when the application has not sent the notification after a predetermined period of time or when the notification indicates that the application is unavailable for scheduled maintenance.

9. The method of claim 8 further comprising:

identifying, from the one or more service variants, an impacted service variant, the impacted service variant having at least one service associated with the inactive application; and

prohibiting the selecting of the impacted service variant.

10. The method of claim 9 further comprising:

selecting a new solution variant if the generated configuration file is based on the impacted service variant;

generating a new configuration file for the new solution variant; and

transmitting the new configuration file to the mobile device of the customer.

11. A non-transitory computer-readable medium containing instructions to configure a processor to perform operations comprising:

maintaining metadata for one or more mobile programs in a directory, the one or more mobile programs configured to provide one or more services when installed on a mobile device, each of the one or more services associated with one or more applications;

maintaining one or more customer landscapes in the directory, the one or more customer landscapes identifying one or more applications accessible by a customer;

receiving a program identifier from a mobile device of the customer, the program identifier identifying a mobile program installed on the mobile device of the customer;

generating a configuration file based on the received program identifier; and

transmitting the generated configuration file to the mobile device of the customer.

12. The non-transitory computer-readable medium of 11, wherein the generating the configuration file further comprises:

accessing, based on the received program identifier, one or more service variants stored in the directory, the one or more service variants identifying a different combination of the one or more services provided by the mobile program;

for each of the one or more service variants

identifying applications associated with the combination of services, and

comparing the identified applications with the one or more applications accessible by the customer; and

selecting a service variant based on the comparing.

13. The non-transitory computer-readable medium of claim 12, wherein a service variant is selected if the applications associated with the combination of services are all accessible by the customer.

14. The non-transitory computer-readable medium of claim 12, wherein the identifying and the comparing of the one or more service variants are performed in a predetermined order based on a number of services associated with the service variant.

15. The non-transitory computer-readable medium of claim 12, wherein the configuration file is generated from metadata associated with the selected service variant.

16. A system comprising:

a processor; and

a memory, wherein the processor and the memory are configured to perform operations comprising;

maintaining metadata for one or more mobile programs in a directory, the one or more mobile programs configured to provide one or more services when installed on a mobile device, each of the one or more services associated with one or more applications;

maintaining one or more customer landscapes in the directory, the one or more customer landscapes identifying one or more applications accessible by a customer;

receiving a program identifier from a mobile device of the customer, the program identifier identifying a mobile program installed on the mobile device of the customer;

generating a configuration file based on the received program identifier; and

transmitting the generated configuration file to the mobile device of the customer.

17. The system of claim 16, wherein the generating the configuration file further comprises:

accessing, based on the received program identifier, one or more service variants stored in the directory, the one or more service variants identifying a different combination of the one or more services provided by the mobile program;

for each of the one or more service variants

identifying applications associated with the combination of services, and

comparing the identified applications with the one or more applications accessible by the customer; and

selecting a service variant based on the comparing.

18. The system of claim 17, wherein a service variant is selected if the applications associated with the combination of services are all accessible by the customer.

19. The system of claim 17, wherein the identifying and the comparing of the one or more service variants are performed in a predetermined order based on a number of services associated with the service variant.

20. The system of claim 17, wherein the configuration file is generated from metadata associated with the selected service variant.