Clarity

Expand all | Collapse all

XOG client - connection error

  • 1.  XOG client - connection error

    Posted 07-21-2016 05:54 AM

    Hi,

    I´m trying to connect to CA PPM using the XOG client tool and I´m not able to get connection. The XOG client I have installed on my local PC and the CA PPM server is on CA cloud (we access it using the URL via web and also the XOG web client). The connectivy parameters and errors, please check below.

     

    On red marked text below, the server parameter seems to be redirected to localhost and I´m not able to find where must I change it. Any ideas?. Thanks in advance.

     

    Regards.

     

    D:\XOG_client_v13.x\bin>xog -sslenabled true

    -----------------------------------------------------------

    Clarity XML Open Gateway ( version: 13.2.0.472 )

    -----------------------------------------------------------

    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

    > login user_name@xxxxx.ondemand.ca.com:443

    Password: xxxxx

    Login: user_name@xxxxx.ondemand.ca.com:443@127.0.0.1:80

    URL: http://127.0.0.1:80/niku/xog

    XOG Invoke Failed

    java.net.ConnectException: Connection refused: connect

            at java.net.DualStackPlainSocketImpl.connect0(Native Method)

            at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source)

            at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)

            at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)

            at java.net.AbstractPlainSocketImpl.connect(Unknown Source)

            at java.net.PlainSocketImpl.connect(Unknown Source)

            at java.net.SocksSocketImpl.connect(Unknown Source)

            at java.net.Socket.connect(Unknown Source)

            at java.net.Socket.connect(Unknown Source)

            at sun.net.NetworkClient.doConnect(Unknown Source)

            at sun.net.www.http.HttpClient.openServer(Unknown Source)

            at sun.net.www.http.HttpClient.openServer(Unknown Source)

            at sun.net.www.http.HttpClient.<init>(Unknown Source)

            at sun.net.www.http.HttpClient.New(Unknown Source)

            at sun.net.www.http.HttpClient.New(Unknown Source)

            at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(Unknown Source)

            at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source)

            at sun.net.www.protocol.http.HttpURLConnection.connect(Unknown Source)

            at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(Unknown Source)

            at com.niku.union.xml.SimpleSOAPMessage.processRequest(SimpleSOAPMessage.java:255)

            at com.niku.union.xml.SimpleSOAPMessage.send(SimpleSOAPMessage.java:86)

            at com.niku.union.xml.SimpleSOAPMessage.send(SimpleSOAPMessage.java:77)

            at com.niku.union.xml.SimpleSOAPMessage.send(SimpleSOAPMessage.java:54)

            at com.niku.xog.client.XOGClient.login(XOGClient.java:443)

            at com.niku.xog.client.XOGClient.login(XOGClient.java:365)

            at com.niku.xog.client.XOGClient.processCmd(XOGClient.java:914)

            at com.niku.xog.client.XOGClient.startShell(XOGClient.java:865)

            at com.niku.xog.client.XOGClient.invokeCommand(XOGClient.java:826)

            at com.niku.xog.client.XOGClient.main(XOGClient.java:121)

            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

            at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

            at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

            at java.lang.reflect.Method.invoke(Unknown Source)

            at com.werken.forehead.Forehead.run(Forehead.java:551)

            at com.werken.forehead.Forehead.main(Forehead.java:581)

    >



  • 2.  Re: XOG client - connection error

    Broadcom Employee
    Posted 07-21-2016 12:45 PM

    Hi Francisco,

     

    The URL seems to be wrong, please have a look at our xog documentation XML Open Gateway (XOG) Development - CA PPM - 14.3 - CA Technologies Documentation

     

    URL: http://127.0.0.1:80/niku/xog

     

     



  • 3.  Re: XOG client - connection error

    Posted 07-22-2016 03:35 AM

    Hi Suman,

     

    first of all, thank you very much for your quick reply.

     

    The connection data I used:

     

    D:\XOG_client_v13.x\bin>xog -sslenabled true

    -----------------------------------------------------------

    Clarity XML Open Gateway ( version: 13.2.0.472 )

    -----------------------------------------------------------

    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

    > login user_name@xxxxx.ondemand.ca.com:443

     

    and the reponse on login process do the following:

     

    Login: user_name@xxxxx.ondemand.ca.com:443@127.0.0.1:80 (login process add this red marked servername)

    URL: http://127.0.0.1:80/niku/xog

    XOG Invoke Failed

     

    It seems to be trying to redirect the servername xxxxx.ondemand.ca.com:443 to 127.0.0.1:80

     

    I have not used 127.0.0.1:80 as servename. That´s the reason to ask here about this matter because I´m not able to find the root cause.

     

    Regards.



  • 4.  Re: XOG client - connection error

    Posted 07-22-2016 06:58 AM

    Could it be a firewall issue? A quick search for 127.0.0.1 will give you:

    127.0.0.1 is the loopback Internet protocol (IP) address also referred to as the localhost. The address is used to establish an IP connection to the same machine or computer being used by the end-user.

     

    -Sankhadeep



  • 5.  Re: XOG client - connection error

    Posted 07-22-2016 11:39 AM

    Hi Sankhadeep,

     

    thank you for your comments on this thread.

     

    Only to understand how XOG client tool works:

     

    - XOG client tool is installed locally on my PC

    - The Clarity servername is placed on CA cloud (we can access it through internet and web browser)

    - Currently we use the XOG web client tool using the URL (web browser): https://servername.ondemand.ca.com/niku/app?action=xog.client

    - We have also the possibility to access the Clarity servername using a VPN tunnel (we have also VPN connectivity)

    - The tests performed:

     

    MyPC (XOG Client) ------> Internet -------> CA Cloud (Clarity PPM server)

     

    MyPC (XOG Client)------> Internet -------> CA Cloud (Clarity PPM server)

                                  |------> VPN tunnel ----> |

     

    - On both tests I got the same error: XOG client redirects the provided servername:port to 127.0.0.1:80

     

    D:\XOG_client_v13.x\bin>xog -sslenabled true

     

    > login username@servername.ondemand.ca.com:443

    Password: ******

     

    Login: username@servername.ondemand.ca.com:443@127.0.0.1:80

    URL: http://127.0.0.1:80/niku/xog

    XOG Invoke Failed

     

    - Also checked "hosts" file on my PC and 127.0.0.1 is localhost (not other name or address).

     

    My doubt is if XOG client can connect to remote clarity servers placed on internet or only servers placed on the same lan (intranet).

    In the case of be able to access remote internet servers, I would like what is necessary to be taken into account.

     

    Regards and thanks in advance.



  • 6.  Re: XOG client - connection error

    Broadcom Employee
    Posted 11-22-2017 03:11 PM

    Hi Francior,

     

    Curious to know were you able to solve the issue? I am also facing the same issue .

     

    If yes, could you please mention the steps?

     

    Regards,

    Supriya Chakraborty



  • 7.  Re: XOG client - connection error

    Posted 03-27-2018 10:59 AM

    Not sure why this thread got bumped - maybe it was replied to and then the reply was deleted again.

     

    Anyhow.. the original problem where 127.0.0.1 suddenly appears occurs when the XOG client misinterprets the parameters, which is more likely to happen with usernames containing the @ character (such as those that have their email address set as their username - e.g. SaaS customers).

     

    You have to make sure to include all of the items in the invocation if the address is getting mistaken, like this:

     

    xog -sslenabled true

     

    login user[@domain.com]:password@hostname:port

     

    E.g.

    login jane@acme.com:notVerySecure1@myppmserver:443



  • 8.  RE: Re: XOG client - connection error

    Posted 12-04-2020 12:17 PM
    Hi All,

    I've got the same issue here on a SaaS SSL HTTP : Error returned Received fatal alert: unrecognized_name.

    I've tried many things on client netowrk but doesn't seem to work...

    The server is : XXXXX.clarityppm.saas.broadcom.com
    With the following properties to connect with the XOG client (with user AdminCoPrime) :

    servername=XXXXXX.clarityppm.saas.broadcom.com
    portnumber=443
    sslenabled=true
    fipsenabled=false
    username=AdminCoPrime
    password=XXXX

    Using https
    Configuring context for TLS
    -----------------------------------------------------------
    PPM XML Open Gateway ( version: 15.3.0.200 )
    -----------------------------------------------------------
    XOG Invoke Failed
    Received fatal alert: unrecognized_name
    Turn verbose on for more detail.

    Any ideas ? Is it a proxy thing ?

    Regards,
    David

    ------------------------------
    Consultant
    CoPrime
    ------------------------------