Clarity

  • 1.  Parse the output of the XML file

    Posted Jul 12, 2017 04:26 PM

    Hi,

    Does anybody have the same experience with parsing the XOG output?

    When I XOG out a user with only one CA default group (for example “Group ID= baseUserGroup”) I cannot XPATH query any value (it seems that the output is empty).

    I tried to create XML file in my gel script (below) and the result is the same - empty. (The example1_not working.xml)

     

    BUT – When I XOG out a user with many groups including “Group ID= baseUserGroup” it worked. I can get the values from XML file. (The example2_working.xml)

     

    Any idea how to figure out the issue?

     

    SAAS environment -  14.3

     

    Thanks,

    Karel

     

     

    Output  Example1_not working:

     

    Output  Example2_working

     

    Attachment(s)



  • 2.  Re: Parse the output of the XML file

    Posted Jul 12, 2017 05:05 PM

    They're both showing output for me.

     

    I suspect in the course of doing your tests, you've been making a number of changes.

     

    I also suspect that the bg has had instances running with the older versions of the same scripts at the time you was trying to change it, and it is still referencing the older version from the caches.

     

    If you can't get it sorted out by either:

     

    1) Stopping/removing the existing instances.

    2) Putting the process into full draft mode

    3) Updating the GEL

    4) Validating/activating the process

    5) Creating a new instance

     

    -or-

     

    Create a new a process and put the revised example1 script in there.

     

    Then you may need to find a time when you get the bg services restarted.

     

    Running the scripts from the command line (changing gel:log's to gel:out's) avoided those issues for me and showed no issue with it outputting the parsed XML variable in both cases.



  • 3.  Re: Parse the output of the XML file

    Posted Jul 12, 2017 05:40 PM

    Hi Nick,

     

    Thank you for testing.

    I am planning to create a new CA case because

     

    1.       I was able to reproduce the issue on two environments  (DEV, TEST)

     

    2.       I created two processes from scratch so there shouldn’t be any cashed  information.

     

    3.       I let restarted bg and the result was the same.

     

    4.       Not sure on which environment you tested but it can be connected to SAAS.

     

    Thanks,

     

    Karel



  • 4.  Re: Parse the output of the XML file

    Posted Jul 12, 2017 05:49 PM

    Fair enough, it could warrant a case.  Those had just been some typical causes I had seen intermittently.

     

    To confirm, I just used the XOG client without a connection to SaaS or on-premise PPM setup.

     

    E.g.:

    C:\Clarity\misc\gels>\Clarity\xog1430\bin\gel example1_notworking.gel

     

    Warning: JAVA_HOME environment variable is not set.

     

    Could not load logger template. Using default configuration.
    PPM Installation Directory not found: Continuing with out gel script validation
    Logging configuration could not be determined. Setting logger to root logger.
    Userxogresult_pre:
    <?xml version="1.0" encoding="UTF-8"?>
    <NikuDataBus xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../xsd/nikuxog_user.xsd">
      <Header action="write" externalSource="NIKU" objectType="user" version="14.3.0.298"/>
      <Users>
        <User externalId="01238">
          <Groups>
            <Group id="baseUserGroup">
    ...
            </Group>
          </Groups>
        </User>
      </Users>
    </NikuDataBus>


    C:\Clarity\misc\gels>

     

    Possible for some very limited testing like this parsing, until you start running into the tags used for PPM's internals (e.g. logging, db queries, etc.).