Changes between Version 15 and Version 16 of TITAN


Ignore:
Timestamp:
Oct 22, 2010, 12:37:03 PM (14 years ago)
Author:
mirco.rossi
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TITAN

    v15 v16  
    3535The Java ME PersonalProfile code for the Titan Network Manager is located in the TITAN_Mobile directory (Eclipse project). The Titan Network Manager can be started by the ch.ethz.ee.ife.sensei.titanmanager.titan.mobile.TitanMobile::main(String[] args) method.
    3636
    37 Currently the Java ME version cannot be directly accessed as a Titan REP. Workaround: Set-up a Titan Network Manager on a PC and connect the Java ME version as a "Titan Node Pool" (see below: "Titan Nodes").
     37Currently the Java ME version cannot be directly accessed as a Titan REP. Workaround: Set-up a Titan Network Manager on a PC and connect the Java ME version as a "Titan Node Manager" (see below: "Titan Nodes").
    3838
    39 === Titan Node Pool
    40 A Titan Node Pool hosts a number of Titan Nodes (see below) and is connected to the Titan Network Manager through a TCP/IP connection. A Titan Node pool is addressed by a subnet-ID (e.g. ID=1, ID=0 is reserved for the Titan Network Manager), whereas Titan Nodes are addressed by the pool's subnet-ID and thier local ID (e.g. a Titan Node in the subnet 2 and with local ID 100 has a global address 2100).
     39=== Titan Node Manager
     40A Titan Node Manager hosts a number of Titan Nodes (see below) and is connected to the Titan Network Manager through a TCP/IP connection. A Titan Node Manager is addressed by a subnet-ID (e.g. ID=1, ID=0 is reserved for the Titan Network Manager), whereas Titan Nodes are addressed by the manager's subnet-ID and thier local ID (e.g. a Titan Node in the subnet 2 and with local ID 100 has a global address 2100).
    4141
    42 ==== Set-Up a Framework with Titan Node Pool
     42==== Set-Up a Framework with Titan Node Manager
    4343
    44441.
    45 - in Java SE: set the ''m_NodePoolID'' variable located in the ch.ethz.ee.ife.sensei.titanmanager.rep.TitanConnector.TitanNodePoolMain::main(String[] args) method to the corresponding sub-net ID. Start the Node Pool by this method.
     45- in Java SE: set the ''m_NodeManagerID'' variable located in the ch.ethz.ee.ife.sensei.titannodemanager.TitanNodeManagerMain::main(String[] args) method to the corresponding sub-net ID. Start the Node Manager by this method.
    4646- in Java ME: start the application by the ch.ethz.ee.ife.sensei.titanmanager.titan.mobile.TitanMobile::main(String[] args) method. In the GUI start the router with the corresponding sub-net ID.
    4747
    48 2. Titan Network Manager: put the hostname of the Titan Node Pool in the ''TitanNodePool_HostNames'' located in the method ch.ethz.ee.ife.sensei.titanmanager.titan.mobile.TitanMobile::main(String[] args) and start the Network Manager.
     482. Titan Network Manager: put the hostname of the Titan Node Manager in the ''TitanNodeManager_HostNames'' located in the method ch.ethz.ee.ife.sensei.titanmanager.titan.mobile.TitanMobile::main(String[] args) and start the Network Manager.
    4949
    5050=== Installing the Nodes
     
    9090
    9191==== Titan Nodes
    92 Titan Nodes are virtual nodes running on a Java SE VM or Java ME PersonalProfile VM. Similar to the TelosB Sensor nodes, they provide services (e.g. sensors, actuators, or processing resources) for the SENSEI framework. Titan Nodes are hosted by the "Titan Network Manager" or by a "Titan Node Pool". The number of created nodes can be set before starting the Network Manager/Node Pool (see parameter  ''m_node_nr'' in the corresponding main method).The nodes will get ID 100,101,...
     92Titan Nodes are virtual nodes running on a Java SE VM or Java ME PersonalProfile VM. Similar to the TelosB Sensor nodes, they provide services (e.g. sensors, actuators, or processing resources) for the SENSEI framework. Titan Nodes are hosted by the "Titan Network Manager" or by a "Titan Node Manager". The number of created nodes can be set before starting the Network Manager/Node Manager (see parameter  ''m_node_nr'' in the corresponding main method).The nodes will get ID 100,101,...
    9393
    9494