Log errors in Gel Script when XOGGING

OK, so it is important to be able to log while creating Gel Scripts.  This can be a pain because different environments, like Saas (ondemand) might not allow access to certain logging features.

So first problem is to change the XOG from an XML object ot a string as shown in line 3

Then Set the error level to "ERROR" so that even the Saas environment will have to process it.
Saas sets logging off so that the logs do not fill up.  setting it to ERROR will force a log to be thrown

1. 
   
2.   
3. <gel:set var="xogbodystr" select="$xogBody" asString="true"/>  
4. <gel:log category="XOG" level="ERROR">${xogBodystr}</gel:log>  

XOG Command Line Post

It is always nice to keep a library of tools that make things work faster in Clarity. When you are trying to XOG information out of your instance, it can be helpful to XOG data out through a command line statement that outputs to a file on your computer. These can be managed through BAT batch files.

Since you might not easily find the syntax from CA. I will supply it to you.

../bin/xog -servername yourserver.yourdomain.com -verbose on -input content_read.xml -output Content_out.xml -username "admin" -password "admin1" -portnumber 8080

The server is your server URL

Verbose gives you back messages about errors in the statement.

For SSL you will need a parameter -SSL