Clarity

  • 1.  XOG and Java 8

    Posted Apr 27, 2015 01:07 PM

    My company is in progress of replacing Java 7 with Java 8 on all machines as 7 is no longer supported by Oracle.  Thankfully, Java 7 is installed within the MSP Schedule Connect package.  We are still able to use that tool as security will allow use of a JRE that was installed as part of a package.  Unfortunately, there is no JRE included with XOG and XOG will not run on any Java other than 7.  I looked into directing XOG to use the MSP Schedule Connect JRE but was informed by CA Support that that version is 32-bit and XOG requires a 64-bit version.  As we are on 13.3, the application-based XOG client is not an option for use either.  I looked into IT ROI's XOG & Query Bridge Tool linked to elsewhere on this community but they do not currently support their tool with Java 8.  Is anyone aware of other tools or workarounds available to run XOG with Java 8 installed? 



  • 2.  Re: XOG and Java 8

    Posted Apr 27, 2015 02:03 PM

    There is something wrong with that!

     

    XOG client on the client PC requires 32 bit jre.

    Just tested that with v13.3 Community sandbox.



  • 3.  Re: XOG and Java 8
    Best Answer

    Posted Apr 27, 2015 02:24 PM

    Did not find much on jre 8 for XOG on the comunity, but there are some threads on the 32/64 bits, but not conlclusive.

    https://communities.ca.com/message/109206070#109206070

    solved my issues and therefore my plan is to use 32 bit jre 7 with XOG regardsless of the bits of the OS as long it works or it proven to be wrong

    More old threads

    https://communities.ca.com/message/97992674#97992674

    Really old, but my first hickup with XOG client in 64 bit os

    https://communities.ca.com/message/18133765#18133765

    A lengthy discussion on XOG client which really does not give the final answer on 32 or 64 bits

    https://communities.ca.com/message/241702612#241702612

    If you are looking for the old GUI client see

    https://communities.ca.com/message/241721205#241721205

    In addition to ITRoi there is another from ITdesign in this thread

    https://communities.ca.com/message/241721205#241721205



  • 4.  Re: XOG and Java 8

    Posted Apr 30, 2015 10:46 AM

    Thanks for all the links Urmas.  I have been testing the portlet from ITdesign and have been very happy with its performance.  It's a shame that CA didn't produce something like this themselves if they were going to refuse to build an new XOG client that is not dependent upon an unsupported Java version.



  • 5.  Re: XOG and Java 8

    Posted Apr 30, 2015 11:00 AM

    I would think that the "Clarity portlet" (itdesign) solution would have the same fundamental issue as to why CA disabled the xog.client page in the tool, essentially they would be doing the same thing ; that the XOG call was being handled "within Clarity" (ref that Re: RE: xog.client and V13.3 thread for the explanations as to why it was removed).

     

    But we can call XOG from "anything" that can call the web-service, so you should not be restricted to finding something that is called a "xog client" - so any "web-development" tool/IDE should be able to call the services with a little setup?



  • 6.  Re: XOG and Java 8

    Posted Apr 30, 2015 11:55 AM

    I was told that it does not have similar issues.

    But here definitely is no single truth. Anybody can use his or her own choice for best tool depending on the skill and will.



  • 7.  Re: XOG and Java 8

    Posted May 01, 2015 10:40 AM

    I can confirm that any HTML portlet approaches calling the /niku/xog endpoint in Clarity for XOG requests is fundamentally different and free from the issues of the old xog.client action that ran all the processing (as both client and server on the backend) through the /niku/app and /niku/nu servlets.

     

    So whoever said it does not have similar issues would have been correct about that.

     

    The HTML portlet /niku/xog versions are no worse or burdensome to the server than using any third party SOAP tool like SoapUI, and they are fine (so long as they work - I don't know at which point you might cause the client browser to explode for example, but the backend load is the same as though any other client is connected and pulling data).



  • 8.  Re: XOG and Java 8

    Posted May 01, 2015 10:57 AM

    Nick Darlington wrote:

     

    So whoever said it does not have similar issues would have been correct about that.

     

    Good to know (and I stand corrected )



  • 9.  Re: XOG and Java 8

    Posted May 01, 2015 10:43 AM

    32-bit or 64-bit is fine, I haven't used a 32-bit JRE for a long time (years) personally.

     

    C:\Users\darni01>java -version
    java version "1.7.0_71"
    Java(TM) SE Runtime Environment (build 1.7.0_71-b14)
    Java HotSpot(TM) 64-Bit Server VM (build 24.71-b01, mixed mode)

     

    C:\Users\darni01>\Clarity\xog1330\bin\xog

     

    -----------------------------------------------------------
    Clarity XML Open Gateway ( version: 13.3.0.285 )
    -----------------------------------------------------------
    Usage: xog

    login [user/passwd@host:port] Create new active session.
    logout                        Close active session.
    call <file>                   Invoke given XOG request.
    verbose <on|off>              Turn on verbose error logging.
    output <console|path>         Output to console or file.
    exit                          Logout and exit the shell.
    ?                             Display this help information.

    Examples:
       call xml/cmn_users_read.xml
    >