Software platform providing deployment and configuration settings for a second platform
A platform on a platform system has a first platform that provides deployment and configuration settings for applications developed on the platform; and a second platform developed using the deployment and configuration settings provided by the first platform. The second platform provides second deployment and second configuration settings, and the second platform also provides services that allow second applications to interact with the first platform through the second platform services.
1. A second platform on a first platform system, having a hardware processor, the second platform on a first platform system comprising:
a first platform that provides first deployment and first configuration settings for first applications developed on the first platform; and
a second platform that provides second deployment and second configuration settings for second applications developed on the second platform, wherein:
the second deployment and the second configuration settings are based on the first deployment and the first configuration settings,
the second deployment and the second configuration settings are different from the first deployment and the first configuration settings,
the second platform facilitates a user to update the second applications via the second platform without reinstallation of one or more software applications and without user interaction with the first platform,
the second platform provides services that allow the second applications to interact with the first platform through the second platform services, and
one of the services provided by the second platform comprises a dispatcher service that ensures that an application, of the second applications, meets requirements of the first platform during an attempted installation of the application, wherein the dispatcher service confirms that during installation of the application of the second applications, (1) the application of the second applications has a routing rule, (2) the routing rule is enabled, (3) the application of the second applications is registered, (4) and the application of the second applications is enabled.
2. The second platform on a first platform system of claim 1 , wherein another one of the services provided by the second platform comprises a configuration service that confirms that another application, of the second applications, can be updated or created on the second platform.
3. The second platform on a first platform system of claim 2 , wherein the configuration service, upon an attempted installation of the another application, checks to ensure that the another application has an app namespace.
4. The second platform on a first platform system of claim 3 , wherein if the app namespace does not exist, the second platform checks whether the app namespace matches a global registry, wherein if the app namespace matches the global registry, the second platform creates an exception, and wherein if the app namespace does not match the global registry, the second platform begins a registration process to register a new app namespace.
5. The second platform on a first platform system of claim 4 , wherein if the app namespace does not match the global registry and no new app namespace is registered, the second platform generates another exception.
6. The second platform on a first platform system of claim 1 , wherein another one of the services provided by the second platform comprises a license manager service that confirms whether installation of another application, of the second applications, is permitted.
7. The second platform on a first platform system of claim 6 , wherein the license manager service, upon an attempted installation of the another application, checks to ensure that a source of the installation is permitted to perform the installation.
8. The second platform on a first platform system of claim 7 , wherein if the source is permitted, the license manager service confirms that an object within the installation is enabled, and in an event that the source is permitted and the object is enabled, the license manager service approves the installation.
9. The second platform on a first platform system of claim 8 , wherein if the source is not permitted and/or the object is not enabled, the license manager service checks whether a core configuration is enabled, and wherein if the core configuration is not enabled, the license manager service returns an error message.
10. The second platform on a first platform system of claim 9 , wherein if the core configuration is enabled, the license manager service checks to see if a trigger is executing.
11. The second platform on a first platform system of claim 1 , wherein the dispatcher service checks whether a core is enabled, wherein if the core is not enabled, the dispatcher service returns an error, and wherein if the core is enabled, the dispatcher service checks to ensure that a registered application is enabled.
12. The second platform on a first platform system of claim 1 , wherein another one of the services provided by the second platform comprises a domain meta service that determines which service or function the second platform should call.
13. The second platform on a first platform system of claim 1 , wherein another one of the services provided by the second platform comprises an install service that confirms one or more steps taken in order to install another application of the second applications.
14. A method to install and update an application on a second platform that was developed on top of a first platform, the method comprising:
providing, by the first platform, first deployment and first configuration settings for first applications developed on the first platform;
developing a second platform that provides second deployment and second configuration settings for second applications developed on the second platform, wherein:
the second deployment and the second configuration settings are based on—the first deployment and the first configuration settings provided by the first platform, and
the second deployment and the second configuration settings are different from the first deployment and the first configuration settings; and
installing an application, of the second applications, on the second platform, wherein the second platform provides services that allow the second applications to interact with the first platform through the second platform services, and
the second platform facilitates a user to update the second applications via the second platform without reinstallation of one or more software applications;
one of the services provided by the second platform comprises a dispatcher service that ensures that an application, of the second applications, meets requirements of the first platform during an attempted installation of the application, wherein the dispatcher service confirms that during installation of the application of the second applications, (1) the application of the second applications has a routing rule, (2) the routing rule is enabled, (3) the application of the second applications is registered, (4) and the application of the second applications is enabled.
15. The method of claim 14 , wherein one of the services provided by the second platform comprises a configuration service that confirms that an application, of the second applications, can be updated or created on the second platform.
16. The method of claim 14 , wherein one of the services provided by the second platform comprises a license manager service that confirms whether the installation is permitted.
17. The method of claim 14 , wherein one of the services provided by the second platform comprises a domain meta service that determines which service or function the second platform should call.
18. The second platform on a first platform system of claim 1 , wherein the application meets requirements of the first platform during an attempted installation of the application through the steps comprising: confirming that a core has triggers enabled, confirming that the core has registered object triggers enabled, and confirming that the second application is enabled, and in the event that one of these steps cannot be confirmed, the dispatcher service denies the attempted installation.
19. The method of claim 14 , wherein the application meets requirements of the first platform during an attempted installation of the application through the steps comprising: confirming that a core has triggers enabled, confirming that the core has registered object triggers enabled, and confirming that the second application is enabled, and in the event that one of these steps cannot be confirmed, the dispatcher service denies the attempted installation.