You can translate the question and the replies:

Using Create Revision API of Solution Manager

I am looking at the documentation of creating a Revision from a VQL file Couple of questions on the usage of this API- 1. The "**request**" body has only 3 inputs - name, description and content. How can we specify other options that are available to us when we create revisions using a GUI of Solution Manager. E.g. i want to select includeJars, includeServerProperties, includeWebContainerProperties, includeVDPDependencies etc. These options are available as checkboxes on the GUI but I dont see them as inputs to this API 2. The third input of this API is "**content**", has a comment written in the documentation that it is ***a VQL file content as xsd:base64Binary encoded in UTF-8***. Does this mean I have to first encode the VQL file (which I got after executing Export command over Denodo VDP and not Solution Manager VDP) into base64 format and then plug in that content here in the API ? 3. The same documentation for this API also recommends(in the **Note** section) that while creating revisions, it is better to use a VQL and a separate properties file(both of them are outputs of Export command over normal Denodo platform's VDP and not over the Solution Manager's VDP)and that deploying a revision created from a vql without separate environment properties can generate unexpected results. How would these 2 files (VQL and properties) be fed to this API now ? API has only one input parameter called "**content**"
05-07-2020 05:40:35 -0400

1 Answer

Hi, In order to include jars in the **Create Revision from VQL** file when using the REST API of Solution Manager, please follow the below steps: * [Export]( the revision element from the Virtual DataPort Administration by checking the option **Include Jars** in your export dialog. While exporting, always ensure to generate the VQL file with specific environment properties separately. That is, in the export dialog you need to check the option **Export environment specific properties separately** otherwise deploying the revision will trigger unexpected results. * Convert the VQL file content to base64 format encoded in UTF-8. * Copy-paste the converted output in POST body request for content. Regarding your question on how to feed the properties file through a request, the properties file needs to be included in the target environment within the Solution Manager Administration Tool. The properties will be validated during deployment of the created revision. You may refer to the section [Configuring Virtual DataPort Properties]( of Solution Manager Administration Guide for more information on this topic. So in your POST body request, you will include only the name of the revision, description of the revision and the VQL file content not the properties file. Hope this helps!
Denodo Team
07-07-2020 02:41:52 -0400
You must sign in to add an answer. If you do not have an account, you can register here