API Tutorial Lesson 10 - Adding a Solution to VersaCloud

This lesson's sample code displays the usage of the 'SolutionAddAllow' and 'SolutionAddCommit' APIs to add a new solution to our cloud-based time-limited transaction manager. By calling these two APIs, the developer adds a new name to the list of solutions managed by the transaction manager.

Once the 'SolutionAdd' transaction has been committed, the 'SolutionTokenGet' API can be used to retrieve the just created solution's master token. The calls to the 'SolutionTokenSinceSetAllow' and 'SolutionTokenSinceSetCommit' APIs define that this solution's resources can be used (run) only from July, 1st, 2016 onwards. However, this does not limit building up the solution in any way.

Additionally, the 'SolutionTokenSinceGet' and 'SolutionTokenUntilGet' API calls are available to retrieve each tokens initial and final timestamp, as well as the 'SolutionTokenUntilSetAllow' and 'SolutionTokenUntilSetCommit' API calls to define the final timestamp.

Knowledge of a solution's master token is equivalent to the ownership of the solution: it can be used to modify the solution in any way, even turning it off (for example, by sending a final usage date through calls to APIs 'SolutionTokenUntilSetAllow' and 'SolutionTokenUntilSetCommit' – note that no 'SolutionDelete…' API exists). This is the reason why our transaction manager includes the concept of cloned solution tokens: they identify the same solution than the master token from which they have been cloned, but are less 'powerful'.

Before logging the user off, the sample code in the Figure demonstrates the usage of the 'SolutionDocumentationSetAllow', 'SolutionDocumentationSetCommit' and 'SolutionDocumentationGet' APIs to ask for and modify the solution's 'documentation', which contains a description of the solution in as many specific human languages as necessary.

US Patent Requested