...
In most cases, the user, if administrator, will interact with this service through a specially designed Siege view (refer to the tutorial for specifics). The programmatic interactions, such as those accomplished by the broker, take place via the web service ports. The sections which follow thus are only of interest to potential developers wishing to gain understanding of what lies "under the hood". There is an example of the XML data representation at the end of this page.
API
Service
...
WSDL
Repository
Info be obtained through its retrieve ports, updated or modified through its add, update and remove ports. In addition, the find calls can be used to do simple listings.
...
Defines a node mapping for a resource. This is usually the name of a physical "head node" with a specific IP address, but a logical name is also possible, provided the protocol contacts actually point to physical nodes. The node is thus a way for specifying independent configurations of interactive, batch and file movement protocols available on the resource.
| Code Block |
|---|
public class NodeInfo implements Updateable
{
/*
* Updateable
*/
public Element asElement();
public Element createUpdateableElement();
public void initializeFromElement( Element element );
/*
* Hibernate
*/
public Integer getId();
public void setId( Integer id );
public void addFileProtocol( ProtocolInfo info );
public void addInteractiveProtocol( ProtocolInfo info );
public void addBatchProtocol( ProtocolInfo info );
public String getNodeId();
public void setNodeId( String nodeId );
public String getSoftEnvScript();
public void setSoftEnvScript( String softEnvScript );
public Map getBatchProtocols();
public void setBatchProtocols( Map batchProtocols );
public Map getFileProtocols();
public void setFileProtocols( Map fileProtocols );
public Map getInteractiveProtocols();
public void setInteractiveProtocols( Map interactiveProtocols );
public ProtocolInfo[] orderProtocols( String type );
}
|
...