addVirtualDatabases(String xml, boolean force) Same as addVirtualDatabases(String xml) above, except that a force option
can be specified to bypass the load-order (last-man-down) check.
int
getBacklogSize() Get the controller socket backlog size.
Adds a driver jar file sent in its binary form in the drivers directory of
the controller.
Parameters: bytes - the data in a byte array throws: Exception - if fails
Registers one or several virtual databases in the controller. The
description of each Virtual Database must contain the definition of the
backends and components (cache, scheduler, load balancer) to use.
This function expects the content of an XML file conforming to the Sequoia
DTD to be given as a single String object.
Parameters: xml - XML code to parse exception: ControllerException - if an error occurs while interpreting XML
Same as addVirtualDatabases(String xml) above, except that a force option
can be specified to bypass the load-order (last-man-down) check.
Parameters: xml - vdb.xml config data Parameters: force - set to true to bypass the load-order (last-man-down) check. exception: ControllerException - if an error occurs (vdb xml not valid, other...)
Return the xml version of the controller.xml file without doc type
declaration, just data. The content is formatted using the controller xsl
stylesheet.
controller xml data
Loads a vdb part and initialize it as the first vdb part. This clears the
recovery log. Similarly to addVirtualDatabases() above, several vdb parts
can be specified at once.
Parameters: vdbXmlSpec - an xml string containing the vdb part specification (s) throws: ControllerException - if there is a problem (vdb xml not valid, notfirst in group, ...)
Refreshs the logging system configuration by re-reading the
log4j.properties file.
exception: ControllerException - if the log4j.properties filecannot be found in classpath
Shuts the controller down. The controller can not been shut down if all its
hosted virtual database have not been shut down before
throws: ControllerException - if all the virtual database have not been shutdown or if an error occurs
Update the log4j configuration file with the given content Also call
refreshLogConfiguration method
Parameters: newConfiguration - the content of the new log4j configuration throws: IOException - if cannot access the log4j file throws: ControllerException - if could not refresh the logs