One of the usage scenarios of STRATEGIC platform is sharing of the applications among the public entities, both nationally and internationally. This allows to replicate success stories in implementing a particular scenario across users of the STRATEGIC. The sharing basically means publishing of a properly packaged application in the STRATEGIC Service Store.
Definition of a new STRATEGIC application involves several steps and is done inside the STRATEGIC Service Store. STRATEGIC-defined applications are essentially deployment artifacts following a specific metadata model. For the sake of clarity, such descriptions are called STRATEGIC Workloads.
Workloads provide an easy-to-manage, virtual container managing for all application components as a single entity. A workload can contain a single app running on a single server instance, a webserver, or a developer stack. A workload can also be more complex: for example, a multi-component app like Hadoop application with Name Nodes and multiple Slave Nodes or a multi-tier business application running on multiple instances. The STRATEGIC Service Store makes it easy to manage these multi-tier applications using the workload containers.
Steps for configuration of a new application in the STRATEGIC Service Store include:
- Basic definition of the packaging information: name, icons, descriptions, etc.
- Definition of the cost of running the workload: sharing of applications can be done pro-bono or for a fee.
- Providing of the technical description, including server configuration and application contextualisation parameters.
- Limitation of the application to the IaaS service providers.
- Validation and publication in the Marketplace.
Adaptation and localisation support provided by the STRATEGIC platform allows to reduce the effort of getting a new application to the market. It can range from a basic setup of deployment specific usernames to theming and localisation support.
Such an example configuration allows to parameterize an application on creation, so that deployment of a new service becomes a several click process, requiring only configuration of these parameters, selection of the target deployment site and setting up some additional technical aspects. The screenshots below showcase the required steps.
At first, an administrator of a public body that wants to deploy a new OpenData application needs to define parameters of the deployed application: passwords and emails. These will be used for automatic configuration of the application during the provisioning.
After the application configuration step, administrator proceeds to the target IaaS selection, which can include both public and private clouds providers.
Finally, administrator can tune the server configuration adjusting it for the expected load or storage requirements.
Stay tuned to learn more about STRATEGIC!