D. B. Lange and M. Oshima. Mobile Agents with Java: The Aglet API. World Wide Web, 1(3):111--121, 1998.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....to another server, the agent s code, data as well as execution state are captured and transferred to the next server. It is re instantiated after arrival at the next server. The ability to roam the net is provided by a middle ware platform, a mobile agent execution environment (e.g. Aglets [2], Concordia [3] and Mole [4] Reliability as well as fault tolerance are vital issues for the deployment of a mobile agent system. A number of research work is done in these areas. Some researchers adopt the use of replication as well as masking [5, 6] The idea is to use replicated servers to ....

D. Lange and M. Oshima. Mobile agents with java: the aglet API. Special Issue on Distributed World Wide Web Processing: Applications and Techniques of Web Agents 1(3) (Baltzer Science Publishers, 1998), pp.111-121.

....2. Autonomy: It means that the agent has the both ability which self control and decide the action with the event that occurred. 3. Flexibility: Besides above characteristics, agents can also choice the profitable behavior to complete each mission. Besides, agents have some characteristics [4]: They (1) reduce the network load, 2) overcoming network latency (3) encapsulate protocols (4) execute asynchronously and autonomously (5) adapt dynamically (6) are naturally heterogeneous (7) are robust and fault tolerant. In one word, agent technology has revolutionized the E commerce field. ....

D.B. Lange and M. Oshima, Mobile Agents with Java: The Aglet API, Addison Wesley, 1998.

....as well as its management. Chrysanthis s contribution is the idea of using workflows to support multi organizational processes to form a VE and [5] gives a brief description on how to utilize the mobile agent technology. Lange briefly introduced a mobile agent based marketplace architecture in [6] and showed that the IBM Aglet Software Developing Kit (ASDK) system [4, 7] is suitable to build an electronic marketplace and the meeting pattern and communication mechanism of Aglets, which are mobile Java objects, can be adopted to meet the requirements for representing the behaviors of mobile ....

Lange, D., and Oshima, M. "Mobile Agents with java: The Aglet API", appears in Mobility: Process, Computers, and Agents (edited by Milojicic, D., Douglis, F. and Wheeler, R.), Addison-Wesley Press, Reading, Massachusetts, USA, 1999, pp. 495-512.

....as well as its management. Chrysanthis s contribution is the idea of using workflows to support multi organizational processes to form a VE and [1] gives a brief description on how to utilize the mobile agent technology. Lange briefly introduced a mobile agent based marketplace architecture in [8] and showed that the IBM Aglet Software Developing Kit (ASDK) system [5,7] is suitable to build an electronic marketplace and the meeting pattern and communication mechanism of Aglets, which are mobile Java objects, can be adopted to meet the requirements for representing the behaviors of mobile ....

D. Lange and M. Oshima, "Mobile agents with Java: The Aglet API," in Mobility: Process, Computers, and Agents, eds. D. Milojicic, F. Douglis, and R. Wheeler, Addison-Wesley: Reading, MA, 1999, pp. 495--512.

....model can be found in [11] There are two important implications of our model of agents and multi agent systems. First, since agents are not objects, existing language facilities provided by object oriented languages cannot solve all the problems that software engineers face in developing agents [20]. Therefore, new language facilities must be introduced to support agent oriented software development. Second, because agents are generalisations of objects, we believe that agent orientation should be and can be a natural evolution of object orientation so that the so called agent oriented ....

Lange, D.B., Oshima, M.: Mobile Agents with Java: The Aglet API. World Wide Web Journal (1998)

....replaces the lengthy connection by two short connections, one when starting the task and one when collecting the result. 3.2. IMPLEMENTATION We have implemented a prototype of the agenTa system described in this paper. In our prototype implementation we have used the Aglets SDK 1. 1 beta 3 [4]. It is a mobile agents system development kit which was recently released to the open source community by its creator, IBM. The SDK contains an agent server, the API needed to write agents in Java, examples and documentation. The prototype implementation of agenTa has around 3500 lines of Java ....

Danny B. Lange, Mitsuru Oshima, \Mobile agents with Java: The Aglet API," World Wide Web Journal, 1998.

....no longer a need for one single trusted execution site. 4.4. CURRENT IMPLEMENTATION WITH AGLETS agenTa is the name of our prototype implementation of a secure meeting scheduling system. Currently it uses the custom made protocol described in this paper. We have used the Aglets SDK 1. 1 beta 3 [7], a mobile agents system development kit which was released to the open source community by its creator, IBM. The SDK contains an agent server, the API needed to write agents in Java (called aglets) examples and documentation. The prototype implementation of agenTa has around 3500 lines of Java ....

Danny B. Lange, Mitsuru Oshima, \Mobile agents with Java: The Aglet API." http://www.genmagic.com/asa/danny/Wwwj.pdf.

....simplify these tasks. Java has been touted as the language of the internet, and it provides many features that make it easier to develop internet applications. Nevertheless, Java is still just a conventional programming language, better suited to implementing components than to composing them [8]. Furthermore, Java is not well suited to defining abstractions which are not objects (such as coordination abstractions, generic wrappers, and synchronization policies) We have argued elsewhere that component based software development can be summarized as Applications = Components Scripts ....

Danny B. Lange and Mitsuru Oshima, "Mobile Agents with Java: The Aglet API," World Wide Web Journal, 1998.

....required, more ne grained restriction on executing dangerous operations can be easily done by, for example, extending the rewall to use more thread groups to represent di erent classes of services. There is a limit, however, in how much can be gained by leveraging o the JVM security mechanisms. [3, 15] For example, a thread can theoretically allocate any amount of free memory. Doing so might lead to a denial of service for another thread in the same JVM. And, a thread cannot be forced to terminate without its cooperation, so once a resource is allocated it cannot, in the general case, be ....

Danny B. Lange and Mitsuru Oshima. Mobile Agents with Java: The Aglet API. In Dejan Milojicic, Frederick Douglis, and Richard Wheeler, editors, Mobility, Mobile Agents and Process Migration - An edited Collection. Addison Wesley, 1999.

.... at MCC as a part of the InfoSleuth project [73, 80] ActTalk for object oriented programming at Universit Paris [15] Act for Real time Systems at Virginia Tech [40] and ActorFoundry for Actor based mobile computation in Java at 5 Illinois [60] Recent agent implementations such as Aglets [46] and Concordia [81] also follow actor semantics to varying degrees. 2.1 Resource Management In an open system, agents may migrate from one node to another searching for computation environments suitable for completing their tasks at affordable costs. These agents may also spawn child agents to ....

....to wait until security for mobility support matures, such as composite delegation. Nevertheless, MASIF happened too early in the development stage of the field of mobile agents. There were only a few systems that adopted it and that were MASIF compliant, such as Grasshopper [14] and IBM Aglets [46]. 4.4 Related Work Within the FIPA organization there is another effort pursuing standardization of agent mobility [22] FIPA standardizes agents in general, and addresses mobility as just another capability of agents. The MASIF team is participating in FIPA efforts and MASIF is a contender for ....

[Article contains additional citation context not shown here]

D. Lange, and M. Oshima, "Mobile Agents with Java: The Aglet API," World Wide Web, 1(3), September 1998.

....the security J. Vitek and C. Bryce 97 code in an access control module independent from the main logic, and thus eases the task of verifying security properties. The choice of synchronous communication is somewhat controversial as most other systems offer asynchronous communication mechanisms [8, 2, 25]. The advantages of synchronous communication are that (1) messages from the same thread are causally ordered, 2) acknowledgments of message reception are not needed, and (3) the number of outstanding request is bounded by the number of threads in a seal. This last property makes it easier to ....

D. B. Lange and M. Oshima. Mobile agents with Java: The Aglet API. World Wide Web Journal, 1998.

....eliminate the overheads of Java reflection using program specialization [8] These techniques could useful in extending our approach to a checkpointing implementation based on reflection. Several Java based mobile agent systems use serialization to transmit the state of an agent to another host [18, 33]. The Concordia system also provides extensive checkpointing facilities based on serialization to recover from transmission failures [33] Specialization of the checkpointing process could improve the performance of these systems as well. 7 Conclusion and future work We have shown that automatic ....

D.B. Lange and M. Oshima. Mobile agents with Java: The Aglet API. World Wide Web, 1(3):111--121, 1998.

....state of the agent is nevertheless preserved. Two mobility models have been investigated for agents: in the case of strong mobility the entire state of the agents is moved 1 including all running threads [44] while in the case of weak mobility, only a portion of the data state is transfered [37, 38, 6, 22, 29]. This paper reports on the design and implementation of the JavaSeal mobile agent kernel. JavaSeal is not a full featured agent system, but rather a kernel upon which different agent systems can be implemented. Our design goals were to investigate three basic issues that all agent systems must ....

D. B. Lange and M. Oshima. Mobile agents with Java: The Aglet API. World Wide Web Journal, 1998.

....In this case, the communication proceeds: the portal is first closed, the capsule is copied into B, and then both strands are notified that the communication was successful. The choice of synchronous communication is somewhat controversial. Many systems offer asynchronous communication mechanisms [8, 2, 26]. The advantages of synchronous communication are that (1) messages from the same thread are causally ordered, 2) acknowledgments of message reception are not needed, and (3) the number of outstanding request is bounded by the number of threads in a seal. This last property makes it easier to ....

....envlets harder. Java brought a wave of Java based agent systems. The reason for this is that use of Java is widespread, it has enough utility classes and possesses notions of security and mobility. Example systems include Mole [4] D Agents [18] from Tcl Tk) Voyager [16] Ajanta [24] and Aglets [26]. However, these systems do not provide a level of security based on strict separation between agents, since the kernel does not occupy a different domain to the agent domains. A protection domain in the J Kernel is also a name space implemented using a class loader [19] Communication between ....

D. B. Lange and M. Oshima. Mobile agents with Java: The Aglet API. World Wide Web Journal, 1998.

.... Although there is still no definitive answer as to whether mobile code systems will live up to the expectations placed upon them, there is a growing body of work (Vitec and Tschudin 1997, Rothermel and Hohl 1998, Papaioannou and Minar 1999) and an expanding number of frameworks, including Aglets (Lange and Oshima 1998), Voyager (Object Space 1997) Mole (Straber et al. 1996) and Hive (Minar et al. 1999) 6 4.1 Classification The mobile agents discussed and used in the work described in this paper will be defined as: Software agents that are able to autonomously migrate from one host to another in a ....

....it is returned to the SalesAgent for processing. The mobile object does not make autonomous decisions based on the acquired information. 6 The Systems The experimental work described in this paper was implemented using IBM s Aglet Software Development Kit, a mobile agent development framework (Lange and Oshima 1998). The model, scenario and investigations described have been undertaken using both mobile agent and mobile object systems. The two systems consist of a selection of individual agents and objects. The types identified for the SOP model are SalesAgents, StockControlAgents, ManufacturingAgents, ....

Lange, D.B., Oshima, M., (1998) "Mobile Agents with Java: The Aglet API", World Wide Web Journal.

....are autonomous objects that are able to migrate from node to node in a computer network using services offered on these nodes. The ability to roam the net (by moving the agent s code, data and execution state) is provided by a middleware platform, a mobile agent execution environment (e.g. Aglets[7], Ara[8] Concordia [11] Mole[1] In electronic commerce scenarios, agents autonomously go shopping on the user s behalf, make the reservations needed for a business trip, or monitor the stock market and trigger user defined operations when certain conditions occur. Obviously, many of these ....

....caused by the protocol. Also a flexible itinerary concept is proposed that gives agent systems the freedom to choose from a set of possible optimizations to maximize efficiency when determining the next node and constructing a stage. More rigid types of itineraries are used in the Aglet system [7], in Telescript [2] and in Concordia [11] The paper is structured as follows. In the next Section, a novel type of itinerary is introduced, which allows for the flexible specification of an agent s travel plans. Based on the notion of an itinerary we will then define the notion of exactly once ....

Lange, D.; Oshima, M.: "Mobile Agents with Java: The Aglet API." In "Special issue on Distributed World Wide Web Processing: Applications and Techniques of Web Agents." Baltzer Science Publishers, 1998.

No context found.

D. B. Lange and M. Oshima. Mobile Agents with Java: The Aglet API. World Wide Web, 1(3):111--121, 1998.

No context found.

D.Lange and M.Oshima "Mobile Agents with java: The Aglet API", appears in Mobility: Process, Computers, and Agents (edited by Milojicic, D., Douglis, F. and Wheeler, R.), Addison-Wesley Press, Reading, Massachusetts, USA, pp. 495-512, 1999.

No context found.

D.Lange and M. Oshima, "Mobile Agents with java: The Aglet API", appears in Mobility: Process, Computers, and Agents (edited by Milojicic, D., Douglis, F. and Wheeler, R.), Addison-Wesley Press, Reading, Massachusetts, USA, pp. 495-512,1999.

No context found.

D. Lange and M. Othima. Mobile Agents with Java: The Aglet API. World Wide Web 1(3), September 1998.

No context found.

D. B. Lange, M. Oshima, "Mobile Agents with Java: The Aglet API", World Wide Web Journal, 1998.

No context found.

D. B. Lange, M. Oshima, "Mobile Agents with Java: The Aglet API", World Wide Web Journal, 1998.

No context found.

D. Lange and M. Oshima, Mobile agents with java: the aglet API, in Special Issue on Distributed World Wide Web Processing: Applications and Techniques of Web Agents 1(3) (Baltzer Science Publishers, 1998) 111-121.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC