Citrix Developer Network
The place for unfiltered straight talk on Citrix products. Blogs, code downloads, best practices, APIs, and more can all be found here.
Citrix Ready
Share ideas and integration techniques with Citrix Products and our Alliance Partners.
Blogs
Learn the latest from the Citrix employees who are
building application delivery infrastructure technologies.
Blogosphere
The Citrix Blogosphere is a window into the thousands of conversations
taking place about Citrix and Application Delivery.
Community Contributed NetScaler - AppExpert Samples
Searching for a particular solution? Browse all the scripts and tools written by Citrix insiders, as well as by members of the NetScaler-AppExpert community.
Want to showcase your script or sample then login and contribute to the NetScaler-AppExpert Developer community.
Login with your MyCitrix account and start contributing.
The responder module on the NetScaler can be used to generate respones based on some attribute of the incoming connection. The responder module is only available with NetScaler 8.0 (or later). This defines the prcocedure to create a 404 Not Found response based on the URL of the incoming request.
I am having difficulty getting access to server objects. I am using Java and have generated Java stubs from the WSDL. I can successfully run, for instance, the lbvserver examples. However, when I attempt to do something like the following:
getserverresult = client.getserver("", false);
System.out.println("post server" + System.currentTimeMillis());
Server[] serverNames = getserverresult.getList();
for (int j = 0; j < serverNames.length; j++)
{ System.out.println(" server name: " + serverNames[j].getName() + " " + serverNames[j].getState()); } I get the following SOAP problems:
AxisFault
faultCode:
{http://schemas.xmlsoap.org/soap/envelope/\}
Client
faultSubcode:
faultString: XML syntax error
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/\}
stackTrace:XML syntax error
at org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
at org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
at org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(Unknown Source)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(Unknown Source)
at javax.xml.parsers.SAXParser.parse(Unknown Source)
Is there a known problem with the XML emitted from the getserver call?
I have ran several examples successfully right out of the box. I am going to post a video on how to get started. Meanwhile you can check the getting started resources.
Thanks, perhaps I should clarify. I have worked through the examples and those do seem to work fine, but I was wondering specifically about listing server objects in the netscaler, as mentioned above. I seem to specifically have problems with that.
Looking forward to seeing this site fill up !!