Clarity

  • Private Community

  • 1.  GEL SCRIPT and WINSCP

    Posted Jan 28, 2013 12:03 PM
    Hi, Good afternoon,
    I'm facing a problem with the command gel, throughout Start > All Programs > CA > Clarity > CA Clarity On Demand > XML Open Gateway.
    Not even a simple 'hello world!!' is working properly.


    C:\CA\Clarity\XOG\bin>gel RecursoGelUsuariosDTI.xml -validate
    \WinSCP\ was unexpected at this time.


    How can I solve this?


    Thanks!


  • 2.  RE: GEL SCRIPT and WINSCP
    Best Answer

    Posted Jan 28, 2013 12:19 PM
    Have you tried the "hello world" from the "GEL - Why helloworld is useful.doc" in the zip file attached to the FAQ thread?
    <gel:script xmlns:core="jelly:core" xmlns:gel="jelly:com.niku.union.gel.GELTagLibrary">
<core:forEach indexVar='i' begin='1' end='3'>
<gel:out>Hello World ${i}!</gel:out>
</core:forEach>
</gel:script>
    That "WinSCP" message looks strange - is that referenced in your 'RecursoGelUsuariosDTI.xml' GEL script anywhere?


  • 3.  RE: GEL SCRIPT and WINSCP

    Posted Jan 28, 2013 12:37 PM
    That "WinSCP" is not referenced in the xml.
    If you have seen the Integration 300 Lab Guide I'm trying to import resources like in the Lab 9-2.

    I've tried the hello world again, like you sent above, but unfortunately I received the same: \WinSCP\ was unexpected at this time.

    I'm accessing a VM from the server, in this server is installed WinSCP. I don't know so much about servers but WinSCP is a software that allows you send FTP data. I'm not using it.


  • 4.  RE: GEL SCRIPT and WINSCP

    Posted Jan 28, 2013 12:44 PM
    OK perhaps WinSCP is on your "path" somewhere and that is the problem.... :unsure:


  • 5.  RE: GEL SCRIPT and WINSCP

    Posted Jan 29, 2013 06:28 AM
    Yes, it was there. This error doesn't appear anymore, but another came. I had '\Nmap was unexpected at this time.'
    So I took it away from the Path 'User Variables for Administrator (C:\Program Files (x86)\Nmap).'
    Now I have the following error above:

    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation. All rights reserved.

    C:\CA\Clarity\XOG\bin>gel RecursoGelUsuariosDTI.xml
    java.lang.reflect.InvocationTargetException
    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)
    Caused by: com.niku.union.config.ConfigurationException: Error unmarshalling con
    fig file: properties.xml
    at com.niku.union.config.ConfigurationManager.fetchConfigFileObject(Conf
    igurationManager.java:4562)
    at com.niku.union.config.ConfigurationManager.fetchConfigObject(Configur
    ationManager.java:3964)
    at com.niku.union.config.ConfigurationManager.getProperties(Configuratio
    nManager.java:657)
    at com.niku.union.config.ConfigurationManager.getRawProperties(Configura
    tionManager.java:635)
    at com.niku.union.config.ConfigurationManager.isSingleTenantMode(Configu
    rationManager.java:791)
    at com.niku.union.utility.UtilityThreadLocal.init(UtilityThreadLocal.jav
    a:108)
    at com.niku.union.gel.GELClient.invoke(GELClient.java:83)
    at com.niku.union.gel.GELClient.main(GELClient.java:57)
    ... 6 more
    Caused by: java.io.IOException: The system cannot find the path specified
    at java.io.WinNTFileSystem.createFileExclusively(Native Method)
    at java.io.File.createNewFile(Unknown Source)
    at com.niku.union.config.ConfigurationManager.getConfigFileProperties(Co
    nfigurationManager.java:4370)
    at com.niku.union.config.ConfigurationManager.fetchConfigFileObject(Conf
    igurationManager.java:4419)
    ... 13 more


    C:\CA\Clarity\XOG\bin>


  • 6.  RE: GEL SCRIPT and WINSCP

    Posted Jan 29, 2013 06:35 AM

    daniel.aiub wrote:

    Caused by: com.niku.union.config.ConfigurationException: Error unmarshalling con
    fig file: properties.xml
    The answer to that is in the "Basic guide to getting started with GEL.doc" document in the 'gel.zip' file attached to the FAQ thread that I also mentioned earlier! cool)

    (I am not going to just tell you what the answer is because I want to make sure that you get those documents and read them! :tongue )


  • 7.  RE: GEL SCRIPT and WINSCP

    Posted Feb 04, 2013 11:03 AM
    Well Dave,
    I've done it all, and nothing worked properly.
    I reached the conclusion that the problem is the environment.
    Now I'm going to open an Issue in the Support.

    Thank you so much.


  • 8.  RE: GEL SCRIPT and WINSCP

    Posted Apr 02, 2014 10:49 PM

    Hi Daniel

     

    Did you find solution for this problem?? even I'm facing the same issue in our environment

     

    Thanks

    Siva



  • 9.  Re: GEL SCRIPT and WINSCP

    Posted Apr 24, 2015 12:16 PM

    Hi sivasairam

     

    there ins't solution for this issue, at this moment.

     

    Harlem



  • 10.  Re: GEL SCRIPT and WINSCP

    Broadcom Employee
    Posted Apr 25, 2015 01:11 AM

    This may not be in right vein, but I guess my first question is, "What version of windows are you using and how did you install the XOG client?"

     

    I am wondering, for example, if the GEL executable is truly accessable in your C:\CA\Clarity\XOG\bin directory?  Windows 7, for example wants to put your GEL executable file into c:\program files (x86)\ca\Clarity XOG\bin when installing a XOG client through the IE browser.  This is because 64-bit Windows 7 IE has a built-in predeliction to install 32-bit executables there.

     

    This is further complicated by the fact that GEL can't seem to recognize directories with parentheses in the name.  There was a time not too long ago when those characters were illegal in a Windows directory name.

     

    The work-around is to use the 8-byte directory designation for "program files (x86)".  So instead of setting your directory to say "c:\program files {x86}\ca\clarity XOG\bin" you use "c:\progra~2\ca\clarity XOG\bin".

     

    Again, I don't know if this is relevant to the specific problem you are experiencing, but this is the first suspect that comes to mind.  My second suspect is content of your PATH expression, but one suspect at a time.

     

    Good hunting.