Topic
  • 21 replies
  • Latest Post - ‏2014-02-12T15:09:07Z by DorSe
Ronenbe
Ronenbe
24 Posts

Pinned topic SOMA

‏2013-12-25T13:43:29Z |

Hi

Is the dp:get-diff SOMA request supported in firmware 6.0.0.0?

I am trying to send the following request to url https://myIP:5550/service/mgmt/3.0

and not getting any response.

In firmware 5.0.0.9 is works great

 

<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Body>
<dp:request domain="default" xmlns:dp="http://www.datapower.com/schemas/management">
<dp:get-diff>
<dp:from>
<dp:object class="all-classes" name="all-objects" recursive="false" persisted="true"/>
</dp:from>
<dp:to><!--You have a CHOICE of the next 3 items at this level-->
<dp:object class="all-classes" name="all-objects" recursive="false" persisted="false"/>
</dp:to>
</dp:get-diff>
</dp:request>
</env:Body>
</env:Envelope>

 

 

please advice

 

Regards

Ronen

  • DorSe
    DorSe
    27 Posts
    ACCEPTED ANSWER

    Re: SOMA

    ‏2014-02-12T15:09:07Z  
    • smrt
    • ‏2014-01-29T07:21:31Z

    No it is on XI50.5.0.0.11 when I use the Privileged user access I could able to get the response.

    It is very contrdicting and weird behaviour when I create a user called "somauser" with  similar access it doesn't work and this was not the case with the previous firm ware versions which was absolutely working fine.

    Thanks for your followup.

    Srinivas

    Hi,
    After creating the user, have you tried to log-in with it to DataPower?

    I created a new user, logged in with it. Then, I was prompted for password change. changed it.
    Then sent SOMA request and got a response as expected.

    Current firmware i'm using is 6.0.1.0

    BR,
    Dor.

  • HermannSW
    HermannSW
    6065 Posts

    Re: SOMA

    ‏2013-12-25T14:21:14Z  

    > Is the dp:get-diff SOMA request supported in firmware 6.0.0.0?
    >

    Yes, I did run  "diff" command on 5.0.0/6.0.0/6.0.1 versions of "get-diff", no difference.

    $ xpath++ "//xs:element[@name='get-diff']" xml-mgmt-ops.xsd

    -------------------------------------------------------------------------------
    <xsd:element xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://www.datapower.com/schemas/management" name="get-diff">
              <xsd:complexType>
                <xsd:choice>
                    <xsd:sequence>
                        <xsd:element name="from">
                            <xsd:complexType>
                                <xsd:choice>                
                                    <xsd:element name="export" type="tns:base64-binary"/>
                                    <xsd:element name="backup" type="tns:base64-binary"/>
                                    <xsd:element name="object">
                                        <xsd:complexType>
                                            <xsd:attribute name="class" type="tns:export-class"/>
                                            <xsd:attribute name="name" type="tns:export-name"/>
                                            <xsd:attribute name="recursive" type="xsd:boolean"/>                    
                                            <xsd:attribute name="persisted" type="xsd:boolean"/>
                                        </xsd:complexType>
                                    </xsd:element>
                                </xsd:choice>
                            </xsd:complexType>
                        </xsd:element>
                        <xsd:element name="to">
                            <xsd:complexType>
                                <xsd:choice>                
                                    <xsd:element name="export" type="tns:base64-binary"/>
                                    <xsd:element name="backup" type="tns:base64-binary"/>
                                    <xsd:element name="object">
                                        <xsd:complexType>
                                            <xsd:attribute name="class" type="tns:export-class"/>
                                            <xsd:attribute name="name" type="tns:export-name"/>
                                            <xsd:attribute name="recursive" type="xsd:boolean"/>
                                            <xsd:attribute name="persisted" type="xsd:boolean"/>
                                        </xsd:complexType>
                                    </xsd:element>
                                </xsd:choice>
                            </xsd:complexType>
                        </xsd:element>
                    </xsd:sequence>
                                      
                    <xsd:element name="object">
                        <xsd:complexType>
                            <xsd:attribute name="class" type="tns:export-class"/>
                            <xsd:attribute name="name" type="tns:export-name"/>
                            <xsd:attribute name="recursive" type="xsd:boolean"/>                    
                            <xsd:attribute name="from-persisted" type="xsd:boolean"/>
                            <xsd:attribute name="to-persisted" type="xsd:boolean"/>
                        </xsd:complexType>
                    </xsd:element>
                </xsd:choice>
              </xsd:complexType>
            </xsd:element>
    $


    Hermann<myXsltBlog/> <myXsltTweets/> <myCE/> <myFrameless/>

  • Ronenbe
    Ronenbe
    24 Posts

    Re: SOMA

    ‏2013-12-25T14:32:30Z  
    • HermannSW
    • ‏2013-12-25T14:21:14Z

    > Is the dp:get-diff SOMA request supported in firmware 6.0.0.0?
    >

    Yes, I did run  "diff" command on 5.0.0/6.0.0/6.0.1 versions of "get-diff", no difference.

    $ xpath++ "//xs:element[@name='get-diff']" xml-mgmt-ops.xsd

    -------------------------------------------------------------------------------
    <xsd:element xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://www.datapower.com/schemas/management" name="get-diff">
              <xsd:complexType>
                <xsd:choice>
                    <xsd:sequence>
                        <xsd:element name="from">
                            <xsd:complexType>
                                <xsd:choice>                
                                    <xsd:element name="export" type="tns:base64-binary"/>
                                    <xsd:element name="backup" type="tns:base64-binary"/>
                                    <xsd:element name="object">
                                        <xsd:complexType>
                                            <xsd:attribute name="class" type="tns:export-class"/>
                                            <xsd:attribute name="name" type="tns:export-name"/>
                                            <xsd:attribute name="recursive" type="xsd:boolean"/>                    
                                            <xsd:attribute name="persisted" type="xsd:boolean"/>
                                        </xsd:complexType>
                                    </xsd:element>
                                </xsd:choice>
                            </xsd:complexType>
                        </xsd:element>
                        <xsd:element name="to">
                            <xsd:complexType>
                                <xsd:choice>                
                                    <xsd:element name="export" type="tns:base64-binary"/>
                                    <xsd:element name="backup" type="tns:base64-binary"/>
                                    <xsd:element name="object">
                                        <xsd:complexType>
                                            <xsd:attribute name="class" type="tns:export-class"/>
                                            <xsd:attribute name="name" type="tns:export-name"/>
                                            <xsd:attribute name="recursive" type="xsd:boolean"/>
                                            <xsd:attribute name="persisted" type="xsd:boolean"/>
                                        </xsd:complexType>
                                    </xsd:element>
                                </xsd:choice>
                            </xsd:complexType>
                        </xsd:element>
                    </xsd:sequence>
                                      
                    <xsd:element name="object">
                        <xsd:complexType>
                            <xsd:attribute name="class" type="tns:export-class"/>
                            <xsd:attribute name="name" type="tns:export-name"/>
                            <xsd:attribute name="recursive" type="xsd:boolean"/>                    
                            <xsd:attribute name="from-persisted" type="xsd:boolean"/>
                            <xsd:attribute name="to-persisted" type="xsd:boolean"/>
                        </xsd:complexType>
                    </xsd:element>
                </xsd:choice>
              </xsd:complexType>
            </xsd:element>
    $


    Hermann<myXsltBlog/> <myXsltTweets/> <myCE/> <myFrameless/>

    Hi

    Does not work for us

    did you sent to the same url ttps://myIP:5550/service/mgmt/3.0?

    Ronen

  • HermannSW
    HermannSW
    6065 Posts

    Re: SOMA

    ‏2013-12-26T18:34:59Z  
    • Ronenbe
    • ‏2013-12-25T14:32:30Z

    Hi

    Does not work for us

    did you sent to the same url ttps://myIP:5550/service/mgmt/3.0?

    Ronen

    Hi,

    I have no problem running "get-diff.xml" against 6.0.0.1 box, I used "/service/mgmt/current" endpoint.
    It does compare persisted with running config.

    $ doSoma admin get-diff.xml wolverine:5550 -s | xpath++ "count(//*)" -
    Enter host password for user 'admin':
    1403
    $
    $ cat ~/bin/doSoma
    #!/bin/bash
    curl -k -u $1 --data-binary @$2 https://$3/service/mgmt/current $4
    $

    $ cat get-diff.xml
    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
      <env:Body>
        <dp:request xmlns:dp="http://www.datapower.com/schemas/management">
          <dp:get-diff>
            <dp:from> <dp:object persisted="false"/> </dp:from>
            <dp:to> <dp:object persisted="true"/> </dp:to>
          </dp:get-diff>
        </dp:request>
      </env:Body>
    </env:Envelope>
    $

     

    Hermann<myXsltBlog/> <myXsltTweets/> <myCE/> <myFrameless/>
     

    Updated on 2013-12-26T18:36:02Z at 2013-12-26T18:36:02Z by HermannSW
  • DorSe
    DorSe
    27 Posts

    Re: SOMA

    ‏2013-12-30T16:37:39Z  
    • HermannSW
    • ‏2013-12-26T18:34:59Z

    Hi,

    I have no problem running "get-diff.xml" against 6.0.0.1 box, I used "/service/mgmt/current" endpoint.
    It does compare persisted with running config.

    $ doSoma admin get-diff.xml wolverine:5550 -s | xpath++ "count(//*)" -
    Enter host password for user 'admin':
    1403
    $
    $ cat ~/bin/doSoma
    #!/bin/bash
    curl -k -u $1 --data-binary @$2 https://$3/service/mgmt/current $4
    $

    $ cat get-diff.xml
    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
      <env:Body>
        <dp:request xmlns:dp="http://www.datapower.com/schemas/management">
          <dp:get-diff>
            <dp:from> <dp:object persisted="false"/> </dp:from>
            <dp:to> <dp:object persisted="true"/> </dp:to>
          </dp:get-diff>
        </dp:request>
      </env:Body>
    </env:Envelope>
    $

     

    Hermann<myXsltBlog/> <myXsltTweets/> <myCE/> <myFrameless/>
     

    Hello Hermann,

    I, as well, tried to run the same SOAP request through SOAPUI against XI52 6.0.0.0 VM and I did no get the expected response using the endpoint suggested.

    This is the response I get:

    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
       <env:Body>
          <dp:response xmlns:dp="http://www.datapower.com/schemas/management">
             <dp:timestamp>2013-12-26T18:50:12-05:00</dp:timestamp>
             <dp:diff/>
          </dp:response>
       </env:Body>
    </env:Envelope>

    As Ronen wrote, for earlier firmware it works fine.

    BR,
    Dor

  • HermannSW
    HermannSW
    6065 Posts

    Re: SOMA

    ‏2013-12-30T18:58:37Z  
    • DorSe
    • ‏2013-12-30T16:37:39Z

    Hello Hermann,

    I, as well, tried to run the same SOAP request through SOAPUI against XI52 6.0.0.0 VM and I did no get the expected response using the endpoint suggested.

    This is the response I get:

    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
       <env:Body>
          <dp:response xmlns:dp="http://www.datapower.com/schemas/management">
             <dp:timestamp>2013-12-26T18:50:12-05:00</dp:timestamp>
             <dp:diff/>
          </dp:response>
       </env:Body>
    </env:Envelope>

    As Ronen wrote, for earlier firmware it works fine.

    BR,
    Dor

    You get an empty diff -- that means either no diff, or you did not specify <dp:from> and <dp:to> correctly.
    Please see my example above which works, the diff consists of 1403 elements.


    Hermann<myXsltBlog/> <myXsltTweets/> <myCE/> <myFrameless/>

  • DorSe
    DorSe
    27 Posts

    Re: SOMA

    ‏2013-12-30T19:54:02Z  
    • HermannSW
    • ‏2013-12-30T18:58:37Z

    You get an empty diff -- that means either no diff, or you did not specify <dp:from> and <dp:to> correctly.
    Please see my example above which works, the diff consists of 1403 elements.


    Hermann<myXsltBlog/> <myXsltTweets/> <myCE/> <myFrameless/>

    Hi Hermann,
    I use the exact example above and that's the response I get.
    I can assure there are differences in my default domain, so there is no reason I'll get an empty response.

    I'm attaching a screenshot from SOAPUI of what I sent.
    The only difference is, that I added the Domain attribute the request tag.
    I tried with and without it.

    Thank you kindly for your help,
    Dor.
     

    Attachments

    Updated on 2013-12-30T19:54:36Z at 2013-12-30T19:54:36Z by DorSe
  • smrt
    smrt
    36 Posts

    Re: SOMA

    ‏2014-01-24T10:03:29Z  
    • DorSe
    • ‏2013-12-30T19:54:02Z

    Hi Hermann,
    I use the exact example above and that's the response I get.
    I can assure there are differences in my default domain, so there is no reason I'll get an empty response.

    I'm attaching a screenshot from SOAPUI of what I sent.
    The only difference is, that I added the Domain attribute the request tag.
    I tried with and without it.

    Thank you kindly for your help,
    Dor.
     

    Hi,  Empty response for SOMA request.

    After the firmware upgrade from XI50 4.0 to XI50.5.0.0.11 I am getting the empty response for all the SOMA requests. The request is reaching the box without any issue.

    Request used:

    curl -k --user user:password --data-binary Request.xml https://MyDataPower:MyPort/service/mgmt/current

    <?xml version="1.0" encoding="UTF-8" ?>
    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
    <env:Body>
    <dp:request xmlns:dp="http://www.datapower.com/schemas/management">
          <dp:get-status class="MemoryStatus"/>
        </dp:request>

    </env:Body>
    </env:Envelope>

     

    The Response I am getting is

    Used the below command which has been using for long time in the previous version of 4.0

     

    <?xml version="1.0" encoding="UTF-8"?>
    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
    <env:Body>
    <dp:response xmlns:dp="http://www.datapower.com/schemas/management">
    <dp:timestamp>2014-01-T15:16:43+05:30</dp:timestamp>
    <dp:status/>
    </dp:response>
    </env:Body>
    </env:Envelope>

     

    Please let me know your thoughts.

    Thanks, Srinivas

     

     

  • kenhygh
    kenhygh
    2034 Posts

    Re: SOMA

    ‏2014-01-24T10:51:31Z  
    • smrt
    • ‏2014-01-24T10:03:29Z

    Hi,  Empty response for SOMA request.

    After the firmware upgrade from XI50 4.0 to XI50.5.0.0.11 I am getting the empty response for all the SOMA requests. The request is reaching the box without any issue.

    Request used:

    curl -k --user user:password --data-binary Request.xml https://MyDataPower:MyPort/service/mgmt/current

    <?xml version="1.0" encoding="UTF-8" ?>
    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
    <env:Body>
    <dp:request xmlns:dp="http://www.datapower.com/schemas/management">
          <dp:get-status class="MemoryStatus"/>
        </dp:request>

    </env:Body>
    </env:Envelope>

     

    The Response I am getting is

    Used the below command which has been using for long time in the previous version of 4.0

     

    <?xml version="1.0" encoding="UTF-8"?>
    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
    <env:Body>
    <dp:response xmlns:dp="http://www.datapower.com/schemas/management">
    <dp:timestamp>2014-01-T15:16:43+05:30</dp:timestamp>
    <dp:status/>
    </dp:response>
    </env:Body>
    </env:Envelope>

     

    Please let me know your thoughts.

    Thanks, Srinivas

     

     

    I think the command you need is

    curl -k --user user:password --data-binary "@Request.xml" https://MyDataPower:MyPort/service/mgmt/current

  • smrt
    smrt
    36 Posts

    Re: SOMA

    ‏2014-01-24T11:11:41Z  
    • kenhygh
    • ‏2014-01-24T10:51:31Z

    I think the command you need is

    curl -k --user user:password --data-binary "@Request.xml" https://MyDataPower:MyPort/service/mgmt/current

    Thanks for the reply.

    The command I have used is been using for quite long time after the firmware upgrade I am unable to execute that command.

    curl -k --user user:password --data-binary "@Request.xml" https://mydp.com:5550/service/mgmt/current

    Getting empty response.


    <?xml version="1.0" encoding="UTF-8"?>
    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
    <env:Body>
    <dp:response xmlns:dp="http://www.datapower.com/schemas/management">
    <dp:timestamp>2014-01-24T16:28:12+05:30</dp:timestamp>
    <dp:status/>
    </dp:response></env:Body>
    </env:Envelope>

    Regards

  • kenhygh
    kenhygh
    2034 Posts

    Re: SOMA

    ‏2014-01-24T11:18:19Z  
    • smrt
    • ‏2014-01-24T11:11:41Z

    Thanks for the reply.

    The command I have used is been using for quite long time after the firmware upgrade I am unable to execute that command.

    curl -k --user user:password --data-binary "@Request.xml" https://mydp.com:5550/service/mgmt/current

    Getting empty response.


    <?xml version="1.0" encoding="UTF-8"?>
    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
    <env:Body>
    <dp:response xmlns:dp="http://www.datapower.com/schemas/management">
    <dp:timestamp>2014-01-24T16:28:12+05:30</dp:timestamp>
    <dp:status/>
    </dp:response></env:Body>
    </env:Envelope>

    Regards

    I get:

    <?xml version="1.0" encoding="UTF-8"?>
    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
      <env:Body>
        <dp:response xmlns:dp="http://www.datapower.com/schemas/management">
          <dp:timestamp>2014-01-24T00:11:01-05:00</dp:timestamp>
          <dp:status>
            <MemoryStatus xmlns:env="http://www.w3.org/2003/05/soap-envelope">
              <Usage>27</Usage>
              <TotalMemory>3368442</TotalMemory>
              <UsedMemory>929203</UsedMemory>
              <FreeMemory>2439239</FreeMemory>
              <ReqMemory>963752</ReqMemory>
              <HoldMemory>34549</HoldMemory>
              <ReservedMemory>689922</ReservedMemory>
              <InstalledMemory>4058364</InstalledMemory>
            </MemoryStatus>
          </dp:status>
        </dp:response>
      </env:Body>
    </env:Envelope>
    

    But I'm running v6.0.1.

    It's possible there's a bug in your specific firmware version, you'd have to open a PMR with IBM support to get a definitive answer.

     

  • smrt
    smrt
    36 Posts

    Re: SOMA

    ‏2014-01-24T12:28:20Z  
    • kenhygh
    • ‏2014-01-24T11:18:19Z

    I get:

    <pre class="html dw" data-editor-lang="js" data-pbcklang="html"><?xml version="1.0" encoding="UTF-8"?> <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"> <env:Body> <dp:response xmlns:dp="http://www.datapower.com/schemas/management"> <dp:timestamp>2014-01-24T00:11:01-05:00</dp:timestamp> <dp:status> <MemoryStatus xmlns:env="http://www.w3.org/2003/05/soap-envelope"> <Usage>27</Usage> <TotalMemory>3368442</TotalMemory> <UsedMemory>929203</UsedMemory> <FreeMemory>2439239</FreeMemory> <ReqMemory>963752</ReqMemory> <HoldMemory>34549</HoldMemory> <ReservedMemory>689922</ReservedMemory> <InstalledMemory>4058364</InstalledMemory> </MemoryStatus> </dp:status> </dp:response> </env:Body> </env:Envelope> </pre>

    But I'm running v6.0.1.

    It's possible there's a bug in your specific firmware version, you'd have to open a PMR with IBM support to get a definitive answer.

     

    Thanks for pasting your response.

    Will check.

  • smrt
    smrt
    36 Posts

    Re: SOMA

    ‏2014-01-27T06:45:11Z  
    • smrt
    • ‏2014-01-24T12:28:20Z

    Thanks for pasting your response.

    Will check.

    Even tried enabling the Statistics Settings under Admin--> Device--> Statistics Settings across allt he domains. Still the issue persists.

  • HermannSW
    HermannSW
    6065 Posts

    Re: SOMA

    ‏2014-01-27T10:49:25Z  
    • smrt
    • ‏2014-01-27T06:45:11Z

    Even tried enabling the Statistics Settings under Admin--> Device--> Statistics Settings across allt he domains. Still the issue persists.

    Hi,

    MemoryStatus works fine against 5.0.0.11 for me.

    Can you please let us know whether <FirmwareVersion> SOMA command works against your 5.0.0.11 box?

    $ cat version.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
    <env:Body>
    <dp:request xmlns:dp="http://www.datapower.com/schemas/management">
    <dp:get-status class="FirmwareVersion"/>
    </dp:request>
    </env:Body>
    </env:Envelope>
    $
    $ doSoma admin version.xml nightcrawler:5550 ; echo
    Enter host password for user 'admin':
    <?xml version="1.0" encoding="UTF-8"?>
    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><env:Body><dp:response xmlns:dp="http://www.datapower.com/schemas/management"><dp:timestamp>2014-01-27T10:45:46Z</dp:timestamp><dp:status><FirmwareVersion xmlns:env="http://www.w3.org/2003/05/soap-envelope">
    <Serial>68A2208</Serial>
    <Version>XI50.5.0.0.11oc</Version>
    <Build>238653oc</Build>
    <BuildDate>2014/01/08 08:09:20</BuildDate>
    <WatchdogBuild>XI50.5.0.0.11oc</WatchdogBuild>
    <InstalledDPOS>XI50.5.0.0.11oc</InstalledDPOS>
    <RunningDPOS>XI50.5.0.0.11oc</RunningDPOS>
    <XMLAccelerator>xg3ng</XMLAccelerator>
    <MachineType>9235</MachineType>
    <ModelType>4BX</ModelType></FirmwareVersion></dp:status></dp:response></env:Body></env:Envelope>
    $ 
    $ doSoma admin MemoryStatus.xml nightcrawler:5550 ; echo
    Enter host password for user 'admin':
    <?xml version="1.0" encoding="UTF-8"?>
    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><env:Body><dp:response xmlns:dp="http://www.datapower.com/schemas/management"><dp:timestamp>2014-01-27T10:45:56Z</dp:timestamp><dp:status><MemoryStatus xmlns:env="http://www.w3.org/2003/05/soap-envelope">
    <Usage>14</Usage>
    <TotalMemory>4194304</TotalMemory>
    <UsedMemory>604888</UsedMemory>
    <FreeMemory>3589416</FreeMemory>
    <ReqMemory>1013424</ReqMemory>
    <HoldMemory>408536</HoldMemory>
    <ReservedMemory>3999604</ReservedMemory>
    <InstalledMemory>8193908</InstalledMemory></MemoryStatus></dp:status></dp:response></env:Body></env:Envelope>
    $
    


    Hermann<myXsltBlog/> <myXsltTweets/> <myCE/> <myFrameless/> <GraphvizFiddle/> <xqib/>

  • smrt
    smrt
    36 Posts

    Re: SOMA

    ‏2014-01-27T12:11:16Z  
    • HermannSW
    • ‏2014-01-27T10:49:25Z

    Hi,

    MemoryStatus works fine against 5.0.0.11 for me.

    Can you please let us know whether <FirmwareVersion> SOMA command works against your 5.0.0.11 box?

    <pre class="javascript dw" data-editor-lang="js" data-pbcklang="javascript" dir="ltr">$ cat version.xml <?xml version="1.0" encoding="UTF-8"?> <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"> <env:Body> <dp:request xmlns:dp="http://www.datapower.com/schemas/management"> <dp:get-status class="FirmwareVersion"/> </dp:request> </env:Body> </env:Envelope> $ $ doSoma admin version.xml nightcrawler:5550 ; echo Enter host password for user 'admin': <?xml version="1.0" encoding="UTF-8"?> <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><env:Body><dp:response xmlns:dp="http://www.datapower.com/schemas/management"><dp:timestamp>2014-01-27T10:45:46Z</dp:timestamp><dp:status><FirmwareVersion xmlns:env="http://www.w3.org/2003/05/soap-envelope"> <Serial>68A2208</Serial> <Version>XI50.5.0.0.11oc</Version> <Build>238653oc</Build> <BuildDate>2014/01/08 08:09:20</BuildDate> <WatchdogBuild>XI50.5.0.0.11oc</WatchdogBuild> <InstalledDPOS>XI50.5.0.0.11oc</InstalledDPOS> <RunningDPOS>XI50.5.0.0.11oc</RunningDPOS> <XMLAccelerator>xg3ng</XMLAccelerator> <MachineType>9235</MachineType> <ModelType>4BX</ModelType></FirmwareVersion></dp:status></dp:response></env:Body></env:Envelope> $ $ doSoma admin MemoryStatus.xml nightcrawler:5550 ; echo Enter host password for user 'admin': <?xml version="1.0" encoding="UTF-8"?> <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><env:Body><dp:response xmlns:dp="http://www.datapower.com/schemas/management"><dp:timestamp>2014-01-27T10:45:56Z</dp:timestamp><dp:status><MemoryStatus xmlns:env="http://www.w3.org/2003/05/soap-envelope"> <Usage>14</Usage> <TotalMemory>4194304</TotalMemory> <UsedMemory>604888</UsedMemory> <FreeMemory>3589416</FreeMemory> <ReqMemory>1013424</ReqMemory> <HoldMemory>408536</HoldMemory> <ReservedMemory>3999604</ReservedMemory> <InstalledMemory>8193908</InstalledMemory></MemoryStatus></dp:status></dp:response></env:Body></env:Envelope> $ </pre>


    Hermann<myXsltBlog/> <myXsltTweets/> <myCE/> <myFrameless/> <GraphvizFiddle/> <xqib/>

    Thanks for your input Herman.

    No I haven't received the out put, all I got  is the same response.

    REquest Used:

    <?xml version="1.0" encoding="UTF-8" ?>
    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
    <env:Body>
    <dp:request xmlns:dp="http://www.datapower.com/schemas/management">
          <dp:get-status class="FirmwareVersion"/>
        </dp:request>

    </env:Body>
    </env:Envelope>

     

    Response Obtained:

     

    <?xml version="1.0" encoding="UTF-8"?>
    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
    <env:Body>
    <dp:response xmlns:dp="http://www.datapower.com/schemas/management">
    <dp:timestamp>2014-01-27T17:26:07+05:30</dp:timestamp>
    <dp:status/>
    </dp:response>
    </env:Body>
    </env:Envelope>

    Thanks Srinivas

  • HermannSW
    HermannSW
    6065 Posts

    Re: SOMA

    ‏2014-01-27T14:17:15Z  
    • smrt
    • ‏2014-01-27T12:11:16Z

    Thanks for your input Herman.

    No I haven't received the out put, all I got  is the same response.

    REquest Used:

    <?xml version="1.0" encoding="UTF-8" ?>
    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
    <env:Body>
    <dp:request xmlns:dp="http://www.datapower.com/schemas/management">
          <dp:get-status class="FirmwareVersion"/>
        </dp:request>

    </env:Body>
    </env:Envelope>

     

    Response Obtained:

     

    <?xml version="1.0" encoding="UTF-8"?>
    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
    <env:Body>
    <dp:response xmlns:dp="http://www.datapower.com/schemas/management">
    <dp:timestamp>2014-01-27T17:26:07+05:30</dp:timestamp>
    <dp:status/>
    </dp:response>
    </env:Body>
    </env:Envelope>

    Thanks Srinivas

    Can you please run my "doSoma" command with <FirmwareVersion>" from above?

    $ cat ~/bin/doSoma 
    #!/bin/bash
    curl -k -u $1 --data-binary @$2 https://$3/service/mgmt/current $4
    $
    


    Hermann<myXsltBlog/> <myXsltTweets/> <myCE/> <myFrameless/> <GraphvizFiddle/> <xqib/>

  • smrt
    smrt
    36 Posts

    Re: SOMA

    ‏2014-01-28T08:03:32Z  
    • HermannSW
    • ‏2014-01-27T14:17:15Z

    Can you please run my "doSoma" command with <FirmwareVersion>" from above?

    <pre class="javascript dw" data-editor-lang="js" data-pbcklang="javascript" dir="ltr">$ cat ~/bin/doSoma #!/bin/bash curl -k -u $1 --data-binary @$2 https://$3/service/mgmt/current $4 $ </pre>


    Hermann<myXsltBlog/> <myXsltTweets/> <myCE/> <myFrameless/> <GraphvizFiddle/> <xqib/>

    Hi Hermann,

    To execute this comand it requries a  Unix/Linux/Cygwin which i don't have at present, but the problem appeared after the firmware upgrade.  I have extensively used SOMA requet for our deployment and monitoring tools through CURL and SOAPUI.  Please let us know if any significance in using the doSoma command tool.

     

    Thanks, Srinivas

     

  • DorSe
    DorSe
    27 Posts

    Re: SOMA

    ‏2014-01-28T12:24:14Z  
    • smrt
    • ‏2014-01-28T08:03:32Z

    Hi Hermann,

    To execute this comand it requries a  Unix/Linux/Cygwin which i don't have at present, but the problem appeared after the firmware upgrade.  I have extensively used SOMA requet for our deployment and monitoring tools through CURL and SOAPUI.  Please let us know if any significance in using the doSoma command tool.

     

    Thanks, Srinivas

     

    Hi smrt,
    What user are you using when sending the request?
    Have you tried using the admin user?

    I get the same problem, but when I use admin user I get a response.

    I've been struggling to solve this issue for some time now (firmware v6.0.0.3, at firmware 5 and lower it works great!) and today I found out using the admin user bring back a real response for the exact same request!

    Please share your results, if using admin solves this issue for you too I assume opening a PMR is required...

    BR,
    Dor

  • smrt
    smrt
    36 Posts

    Re: SOMA

    ‏2014-01-28T13:46:17Z  
    • DorSe
    • ‏2014-01-28T12:24:14Z

    Hi smrt,
    What user are you using when sending the request?
    Have you tried using the admin user?

    I get the same problem, but when I use admin user I get a response.

    I've been struggling to solve this issue for some time now (firmware v6.0.0.3, at firmware 5 and lower it works great!) and today I found out using the admin user bring back a real response for the exact same request!

    Please share your results, if using admin solves this issue for you too I assume opening a PMR is required...

    BR,
    Dor

    Dorse and Hermann Thanks for your valuable inputs.

    It worked with the userid which was created long back  having Privileged access level, even the soma user having the same level of Privileged access it doesn't get the response.

    Further to that, have created the new user with similar Privileged access but it is not working.

     

    <?xml version="1.0" encoding="UTF-8"?>
    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><env:Body>
    <dp:response xmlns:dp="http://www.datapower.com/schemas/management">
    <dp:timestamp>2014-01-28T18:57:01+05:30</dp:timestamp><dp:status>
    <CPUUsage xmlns:env="http://www.w3.org/2003/05/soap-envelope">
    <tenSeconds>0</tenSeconds>
    <oneMinute>0</oneMinute>
    <tenMinutes>0</tenMinutes>
    <oneHour>1</oneHour>
    <oneDay>1</oneDay></CPUUsage></dp:status></dp:response></env:Body>
    </env:Envelope>

    Thanks, Srinivas

  • DorSe
    DorSe
    27 Posts

    Re: SOMA

    ‏2014-01-28T14:00:10Z  
    • smrt
    • ‏2014-01-28T13:46:17Z

    Dorse and Hermann Thanks for your valuable inputs.

    It worked with the userid which was created long back  having Privileged access level, even the soma user having the same level of Privileged access it doesn't get the response.

    Further to that, have created the new user with similar Privileged access but it is not working.

     

    <?xml version="1.0" encoding="UTF-8"?>
    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><env:Body>
    <dp:response xmlns:dp="http://www.datapower.com/schemas/management">
    <dp:timestamp>2014-01-28T18:57:01+05:30</dp:timestamp><dp:status>
    <CPUUsage xmlns:env="http://www.w3.org/2003/05/soap-envelope">
    <tenSeconds>0</tenSeconds>
    <oneMinute>0</oneMinute>
    <tenMinutes>0</tenMinutes>
    <oneHour>1</oneHour>
    <oneDay>1</oneDay></CPUUsage></dp:status></dp:response></env:Body>
    </env:Envelope>

    Thanks, Srinivas

    Hi Srinivas,
    Just to make sure;
    You are using firmware 6+ and get response for SOMA requests only when using the "admin" user.
    Am I correct? 

  • smrt
    smrt
    36 Posts

    Re: SOMA

    ‏2014-01-29T07:21:31Z  
    • DorSe
    • ‏2014-01-28T14:00:10Z

    Hi Srinivas,
    Just to make sure;
    You are using firmware 6+ and get response for SOMA requests only when using the "admin" user.
    Am I correct? 

    No it is on XI50.5.0.0.11 when I use the Privileged user access I could able to get the response.

    It is very contrdicting and weird behaviour when I create a user called "somauser" with  similar access it doesn't work and this was not the case with the previous firm ware versions which was absolutely working fine.

    Thanks for your followup.

    Srinivas

  • DorSe
    DorSe
    27 Posts

    Re: SOMA

    ‏2014-02-12T15:09:07Z  
    • smrt
    • ‏2014-01-29T07:21:31Z

    No it is on XI50.5.0.0.11 when I use the Privileged user access I could able to get the response.

    It is very contrdicting and weird behaviour when I create a user called "somauser" with  similar access it doesn't work and this was not the case with the previous firm ware versions which was absolutely working fine.

    Thanks for your followup.

    Srinivas

    Hi,
    After creating the user, have you tried to log-in with it to DataPower?

    I created a new user, logged in with it. Then, I was prompted for password change. changed it.
    Then sent SOMA request and got a response as expected.

    Current firmware i'm using is 6.0.1.0

    BR,
    Dor.