JPPF, java, parallel computing, distributed computing, grid computing, parallel, distributed, cluster, grid, cloud, open source, android, .net
JPPF, java, parallel computing, distributed computing, grid computing, parallel, distributed, cluster, grid, cloud, open source, android, .net
JPPF

The open source
grid computing
solution

 Home   About   Features   Download   Documentation   Forums 

Recognizing .Net-capable nodes

From JPPF 6.0 Documentation

Jump to: navigation, search

Contents

Main Page > .Net Bridge > Recognizing .Net-capable nodes


1 From the node configuration

Each node which successfully initializes the .Net bridge sets the following property in its configuration:

jppf.dotnet.bridge.initialized = true

A practical use of this property is when specifying an execution policy, for instance before submitting a job:

JPPFJob job = new JPPFJob();
// execute the job only on .Net-capable nodes
ExecutionPolicy policy = new Equal("jppf.dotnet.bridge.initialized", true);
job.getSLA().setExecutionPolicy(policy);

2 From the management API

The class JPPFManagementInfo has a method called isDotnetCapable(), which determines whether the node can run .Net tasks. A typical usage of this API would be as follows:

// get a JMX connection to the driver
JMXDriverConnectionWrapper jmx = ...;
// collect innformation on all the nodes
java.util.Collection nodes = jmx.nodesInformation();
// iterate over the nodes
java.util.Iterator it = nodes.iterator();
while (it.hasNext()) {
  JPPFManagementInfo nodeInfo = (JPPFManagementInfo) it.next();
  // if the node is .Net-capable
  if (nodeInfo.isDotnetCapable()) {
    // ...
  }
}

3 In the administration console

In all relevant views, the administration console uses distinctive icons to differentiate .Net-capable from standard nodes:

  • node-master.png and node.png for master and non-master standard nodes, respectively
  • node-master-dotnet.png and node-dotnet.png for master and non-master .Net-capable nodes, respectively


For instance, the "topology tree" view would display as follows:

DotnetNodeDistinction.gif

Here, we can see that the nodes running on "127.0.0.1" are standard JPPF nodes, whereas the nodes running on "192.168.1.24" are .Net capable.


Main Page > .Net Bridge > Recognizing .Net-capable nodes



JPPF Copyright © 2005-2017 JPPF.org Powered by MediaWiki