Clarity

Hi all,

We are in CA clarity V13.3 OnDemand Server.

I am unable to connect to application using the xog client

This is the property file i am using,

servername= ***.ondemand.ca.com

portnumber=443

sslenabled=true

fipsenabled=false

output=output_read.xml

username=YYY

password=ZZZ

This gives error message --> XOG Invoke Failed, Login Failed.

I believe XOG is not connecting to the intended app server.

Is there anything i need to take care of?

Thanks,

Aish

Try to login on command line and see if you get a more detailed message.

How do you know the port number?

Does the user have any XOG rights?

Try with the IP of the server to see if that is any different.

Thanks for the reply.

Command line gives same message.

Port number is 443 as its https enabled.

Yes the user has XOG rights.

I do not know the IP.

Hi Aish,

I assume that you are using the right version of XOG client.

There are some noted issues if you are using an older version of XOG client with the latest version of Clarity.

In your servername , try entering the url without the https.

Regards

Nitin

Hi Nitin,

I am using the latest XOG Client downloaded from V13.3

I have entered the exact URL without https://

Thanks,

Aish

Hi Aish,

I request you to raise a case with CA Support incase if the solution by Leo also does not work.

Regards

Nitin

Hi Aishwarya,

I have had issues with v13.3 XOG Client as well. Try the XOG 13.1 client, it should work without problems.

Another thing to check is the JDK. If it's 32 bit, then try the 64 bit jdk

Thanks,

Leo.

Agreed that if there are problems with a specific version trying another might allow to establish working connection.However

"XOG Invoke Failed, Login Failed" coming from the command line sound as if the client is not yet connected.

Yes 443 is the default port when https is used but it can be something else as well depending what is set up.

Agreed, check there inst a firewall/proxy blocking you (not from CA Side, from your company network side)

I am OnDemand 13.3 and the 13.3 client works for me with this property file.

# server host name you want to test against

servername=cppm.ondemand.ca.com

portnumber=443

#set to true if running against a SSL enabled server

sslenabled=true

verbose=on

username=admin

password=password

input=GetUsers.xml

output=OutPut.xml

V/r,

Gene

That is a good post.

When everything is OK on the workstation that s the way it should go.

If it does not some of things pointed above are the client install is not OK and jre is not OK.

If they are the next thing a connection attempt hits is the corporate security policies and firewall.

Do they allow the access required?

The XOG bat checks for the Java 7 JRE and that JAVA_HOME and PATH accordingly but the 32bit vs 64bit has bitten me in the past.

If a user can login into the OnDemand environment via a browser then I would assume the security policies and firewall are set correctly since XOG is using the same protocol / port / host to communicate.

My best guess is in the properties file there is a special character or a space at the end of one of the properties.

The other thing to check is to make sure the user has XOG rights.

V/r,

Gene

Thanks all for your response.

As suggested, we tried the same without proxy and it worked.

So, proxy was blocking. Thanks for the suggestion

I've seen it check for JAVA_HOME and mine continues even if I have not set that and neither do I have jre location in the PATH.

I was under the impression that XOG client is 32 bit and should required 32 bit jre even on 64 bit OS.

Is that not so?

I am pointing my xog client to a 64 bit VM.

I added java -version in the gel.bat and this is way I got:

  echo.

  java -version

  echo.

  java  -Xms32m -Xmx512m -cp "%CLASSPATH%" -Dniku.home="%NIKU_HOME%"  -Dlog4j.configuration="file:\%NIKU_HOME%\lib\log4j.properties" -Dforehead.conf.file="%NIKU_HOME%\bin\gel.forehead" com.werken.forehead.Forehead -installDir "%NIKU_HOME%" %GEL_ARGS%

V/r,

Gene

I am not disagreeing with that either.

I think the current XOG client is coded to set the CLASS_PATH, JAVA_HOME etc. for the run as required  or override the settings and thee to return return them to their preceding values  after the run.

Your screenshot certainly looks like 32 bit application to me.

I take it your are referring to the 32bit cmd.exe and not the Java VM.

I tried in the 64bit cmd and got the same results.

V/r,

Gene

That is something new to me.

I take it that if you have only 64 bit jre installed you cannot get XOG client to run in 32 bit cmd.