DX Infrastructure Manager

Expand all | Collapse all

automated_deployment_engine scripting

  • 1.  automated_deployment_engine scripting

    Posted 11-11-2013 01:47 PM



    Has anyone used the "submit_job_xml" callback on automated_deployment_engine? I'm trying to create a simple custom interface for pushing robots.


    Probe utility doesn't show what parameters the callback takes. Why they should be any kind of secret, I don't know. However, looking into it, I figured it requires two parameters:


    "filename" which contains the name of the xml file uploaded from USM. This is a string type field.

    "file_content" which contains the xml with the installation information. This is of type "22" and I can't figure out just what that means. 21 is PDS.


    I tried submitting the XML as a string, but that just results in an error message "content is not allowed in trailing section". I assume this is due to the wrong data type there.


    I can find data types in different API references, but not their corresponding numeric representations. Furthermore it seems, that this datatype is not supported by Perl API or NSA. If anyone knows more about this I would be grateful.



  • 2.  Re: automated_development_engine scripting

    Posted 11-11-2013 01:59 PM

    I just realized I've answered similar question myself earlier..


    .NET API PdsType enumeration tells that 22 is type VOID.


    Here's reference for anyone who might wonder the same thing:


            PDS_NULL = 0,
            PDS_I = 1,
            PDS_PI = 2,
            PDS_PPI = 3,
            PDS_RGI = 4,
            PDS_RGPI = 5,
            PDS_CH = 6,
            PDS_PCH = 7,
            PDS_PPCH = 8,
            PDS_RGCH = 9,
            PDS_RGPCH = 10,
            PDS_DUM_L = 11,
            PDS_DUM_PL = 12,
            PDS_DUM_PPL = 13,
            PDS_DUM_RGL = 14,
            PDS_DUM_RGPL = 15,
            PDS_F = 16,
            PDS_PF = 17,
            PDS_PPF = 18,
            PDS_RGF = 19,
            PDS_RGPF = 20,
            PDS_PDS = 21,
            PDS_VOID = 22,
            PDS_SEP = 23,
            PDS_PPDS = 24,
            PDS_CPCH = 25,
            PDS_CPDS = 26,
            PDS_INT64 = 27,
            PDS_BOOL = 28,


  • 3.  Re: automated_development_engine scripting

    Posted 11-12-2013 08:45 AM

    Apparently this  type is only available for use in C and Java SDK

  • 4.  Re: automated_development_engine scripting

    Posted 11-13-2013 11:46 AM

    Managed to do this with C SDK, but I have to admit it was a quite a battle even to get a working build with Nimbus stuff included. I'm very newbie when it comes to C so that might affect..


    Would love it if all SDK's were up to par with C.


    Fortunately I don't need to write the GUI in C..



  • 5.  Re: automated_deployment_engine scripting

    Posted 07-16-2015 03:13 PM

    Actually, since posting this I've learned I was wrong, type PDS_VOID is available in .NET SDK as well. It's the PutBytes Method



  • 6.  Re: automated_deployment_engine scripting

    Posted 07-16-2015 10:31 PM

    Applause for adding what you learned to your original question.