[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: parsing help

From: Mike Krebs <mkrebs@xxxxxxxxxxxxxxxxxx>
To: HTTPAPI and FTPAPI Projects <ftpapi@xxxxxxxxxxxxxxxxxxxxxx>
Subject: RE: parsing help
Date: Mon, 1 Dec 2014 12:27:32 -0600
Without knowing how the web service logs you in, it is hard to know how to log you out unless the webservice provides such a function.

A common technique is that the login sends back some cookies. These cookies then provide the needed information to make sure you are a validated user. If look in your debug listing, you might see this happening.  HTTPAPI does not have a destroy cookie function but the ordinary cookies are destroyed when the activation group ends. So, it would be possible to create your program that calls the web service in its own activation group and that would allow you to reclaim the activation group after running the program. 

FWIW, Unless this is belt and suspenders, government work or high security issue, I would not worry about logging out of the web service. There is a lot of security by obscurity involved with the IBMi and HTTPAPI and it probably is not worth the effort to write a destroy_cookie routine. However, if you do, please share!

-----Original Message-----
From: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx [mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of CXGBaldwin@xxxxxxxxxxxxx
Sent: Monday, December 1, 2014 11:49 AM
To: HTTPAPI and FTPAPI Projects
Cc: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re: parsing help

I do not have to connect using Userid or password I consume the service from behind our firewall so I do not have to log on.. 

Can anyone out there Help Donnie with his last question????


Thanks,

George A. Baldwin
CGI Consultant
Cell: 614-284-5679



From:   Donnie Barrow <ddbarrow@xxxxxxxxx>
To:     HTTPAPI and FTPAPI Projects <ftpapi@xxxxxxxxxxxxxxxxxxxxxx>, 
Cc:     "ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx" 
<ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx>
Date:   12/01/2014 12:24 PM
Subject:        Re: parsing help
Sent by:        ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx



Boom Boom I got it. Last question. I have to sign on with a profile and password to the webservice.Is there a routine that will disconnect me from the web service? 
      From: "CXGBaldwin@xxxxxxxxxxxxx" <CXGBaldwin@xxxxxxxxxxxxx>
 To: HTTPAPI and FTPAPI Projects <ftpapi@xxxxxxxxxxxxxxxxxxxxxx>
Cc: "ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx" 
<ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx>
 Sent: Monday, December 1, 2014 7:31 AM
 Subject: Re: parsing help
 
  Yes, when I return the XML from the web service using the command it is
  built in to call the procedure PARSERTRNXML... Code as follows:
    /////////////////////////////////////////////////////////////////
    // send and get the response, and parse it as an XML document.
    //  http_url_get_xml() will call the PARSERTRNXML procedure
    //  for each XML tag found.
    /////////////////////////////////////////////////////////////////

      rc = http_url_get_xml( uri: *null: %paddr(PARSERTRNXML): *null);

    //  If error on process then display message to user
      if (rc <> 1);
          @MSGID = 'CMS9898';
          @MSGFI = 'CISMSGFILE';
          @MSGDA = 'Error while processing data with server';
          $ERRMSG = 'Error while processing data with server';

  Now the  procedure in the program itself is like this:
  D PARSERTRNXML    PR
  D  userData                      *  value
  D  depth                      10I 0 value
  D  name                      1024A  varying const
  D  path                    24576A  varying const
  D  value                    65535A  varying const
  D  attrs                        *  dim(32767)
  D                                    const options(*varsize)
  P PARSERTRNXML    B
  D                PI
  D  userData                      *  value
  D  depth                      10I 0 value
  D  name                      1024A  varying const
  D  path                    24576A  varying const
  D  value                    65535A  varying const
  D  attrs                        *  dim(32767)
  D                                    const options(*varsize)
  D title          s          24576a  varying static

  D a              s            10i 0
  D attrName        s          1024a  varying
  D attrVal        s          65535a  varying
  *** Then the code I sent earlier to you as an example. ***
  NOTE: This code is similar to what is in the example program for the
  weather forcast (sorry I do not remember what program that was) that is
  in the examples in Scott's Package.
  Good Luck,
  George A. Baldwin
  CGI Consultant
  Cell: 614-284-5679
  From:        Donnie Barrow <ddbarrow@xxxxxxxxx>
  To:        HTTPAPI and FTPAPI Projects <ftpapi@xxxxxxxxxxxxxxxxxxxxxx>,
  Cc:        "ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx"
  <ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx>
  Date:        11/26/2014 12:20 PM
  Subject:        Re: parsing help
  Sent by:        ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
    __________________________________________________________________

  Hey George thanksI have this in my program except just like with
  example17 I used the embedded prototype and I don't see it working. the
  only exception I see is where you are using the HTTP_nextXMLAttr  in a
  dowhile.  are you calling this in a routine?
        From: "CXGBaldwin@xxxxxxxxxxxxx" <CXGBaldwin@xxxxxxxxxxxxx>
  To: HTTPAPI and FTPAPI Projects <ftpapi@xxxxxxxxxxxxxxxxxxxxxx>
  Cc: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
  Sent: Wednesday, November 26, 2014 11:48 AM
  Subject: Re: parsing help

    I had to do this for parsing the XML coming back from VIN look ups we
    do and here is how I done it... I think this may be what your looking
    for at least???
    in the D specs:
      D  name                      1024A  varying const
      D  path                    24576A  varying const
      D  value                    65535A  varying const
      D a                        s            10i 0
      D attrName        s          1024a  varying
      D attrVal              s          65535a  varying
    In the code:
    individual tags:
        //*******************************************************
        //**** Bring Back the Values when <<VIN DATA>>passed in**
        //*******************************************************
        if path = '/PolkServiceResponse/VinData';
          select;
          when name='vin';
            eval SAVVIN = Value;
          when name='correctedVin';
            eval SUGVIN = Value;
      // HANDLE INDIVIDUAL ATTRIBUTES IN THE VDTA RETURN XML //
          when name='fields';
            A = 1;
            dow HTTP_nextXmlAttr( attrs: a: attrName: attrVal );
              select;
              when attrVal = 'ABS_BRK_CD';
                WK_VNDATA(1) = Value;
              when attrVal = 'BODY_STYLE_CD';
                WK_VNDATA(9) = Value;
    I do load this data to another array for other uses but this should
    give you an Idea of how to handle the tags in the XML being returned.
    Hope this helps you,
    George A. Baldwin
    CGI Consultant
    Cell: 614-284-5679
    From:        Donnie Barrow <ddbarrow@xxxxxxxxx>
    To:        HTTPAPI and FTPAPI Projects
  <ftpapi@xxxxxxxxxxxxxxxxxxxxxx>,
    Date:        11/26/2014 11:25 AM
    Subject:        parsing help
    Sent by:        ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
      __________________________________________________________________
    I have HTTPAPI and EXPAT loaded. I have attached a program I used
  from
    example 17. I call a web service and I am writing the return xml to
  the
    IFS /tmp folder. This all works YAiii!  But for some reason I am
  stuck
    trying to parse the daggone return XML to my array.[ or even a field]
    UGHHH!  Can someone help push me in the right direction? I looked at
    CHARDATA1 in the EXPAT examples and I kinda understand it
    but....hmmmmhow do I pull this in?  HeLP        Donnie BarrowiSeries
    Consultant 513.709.0370[attachment "pca001cnsm.txt" deleted by George
    Baldwin/ACIC]

  -----------------------------------------------------------------------
    This is the FTPAPI mailing list.  To unsubscribe, please go to:
    [1][1]http://www.scottklement.com/mailman/listinfo/ftpapi

  -----------------------------------------------------------------------
  References
    1. [2]http://www.scottklement.com/mailman/listinfo/ftpapi
  -----------------------------------------------------------------------
  This is the FTPAPI mailing list.  To unsubscribe, please go to:
  [3]http://www.scottklement.com/mailman/listinfo/ftpapi
  -----------------------------------------------------------------------
    ----------------------------------------------------------------------
  -
  This is the FTPAPI mailing list.  To unsubscribe, please go to:
  [4]http://www.scottklement.com/mailman/listinfo/ftpapi
  -----------------------------------------------------------------------

References

  1. http://www.scottklement.com/mailman/listinfo/ftpapi
  2. http://www.scottklement.com/mailman/listinfo/ftpapi
  3. http://www.scottklement.com/mailman/listinfo/ftpapi


  4. http://www.scottklement.com/mailman/listinfo/ftpapi

-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------


  -----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------

-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------
Follow-Ups:
- Re: parsing help
  - From: Donnie Barrow
References:
- Re: parsing help
  - From: CXGBaldwin
- Re: parsing help
  - From: Donnie Barrow
- Re: parsing help
  - From: CXGBaldwin
Prev by Date: Re: parsing help
Next by Date: Re: parsing help
Previous by thread: Re: parsing help
Next by thread: Re: parsing help
Index(es):
- Date
- Thread