Re: [Embedlets-dev] Interested in sharing a J2EE perspective

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
  <title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
Hi,<br>
<br>
Have taken a very first cut responses to teh questions. Just to
stimulate further queries. WIll try and send out a more detailed
Architecture Possibility for integrating Devices into a J2EE Biz App
platform shortly.<br>
<br>
Please see inline comments below. <br>
<br>
Ted Kosan wrote:<br>
<blockquote type="cite"
 cite="mid...@we...">
  <blockquote type="cite">
    <pre wrap="">Ted Kosan asked if I could participate in the deliberations and present a J2EE angle to the technology.

<!----></pre>
  </blockquote>
  <pre wrap=""><!---->
  </pre>
  <pre wrap=""><!---->First off, thank you for taking the time to add a J2EE perspective to this
discussion, it is much appreciated :-)

I think that a good way to begin is with some background information. [...]</pre>
</blockquote>
<blockquote type="cite"
 cite="mid...@we...">
 <pre wrap="">Now for the fun part ;-) Here are some of the issues related to this problem
that we currently view as unknowns:

1) How many Internet-connected embedded devices is a typical J2EE system able
to handle and at what load levels? Are the bottlenecks going to be the
embedded devices themselves, the network, the presentation layer, the business
logic layer or the database layer? (For example, I studied Sun's new RFID
reference implementation white paper recently and they needed to develop a
special architecture in order to accommodate the massive amounts of data that
large groups RFID tags are capable of generating into the network as these
groups are moved past a given reader).</pre>
</blockquote>
Given that each tag doesnt represent too much data, the traffic may not
be too much. Say if each tag holds 1k data, then even 1000 tags will
generate only abt 1MB. But the fact remians that this (amount of tag
movements and teh data generated) has to be factored into the overall
solution sizing. 
 
<blockquote type="cite"
 cite="mid...@we...">
 <pre wrap="">2) What are going to be the best-practice protocols that will be used to
communicate between these Internet-connected embedded devices and the J2EE
system?</pre>
</blockquote>
One key aspect here would be to ensure that there is some intervening
infrastructure piece that sits in the middle to provide a pure J2EE
abstraction to the devices. In any rfid based system,&nbsp; the key event to
process is the tag movements (moved in, moved out). Once thismovement
is captured, then a layer on top can procide the current status- what
is there in which location. The movement in itself is an 'event'. Which
will need to be processed. 
 
Now, the specific processing involved depends on the biz application
udner consideration. As teh device is an independant resource, there
could be other apps also that are processing the events. So one
architecture option could be to have a J2EE bridge as an infrastructrue
pice, that will detect any movements and accordingly provide a 'j2ee
event' for teh biz layer to process. Teh j2ee event could copnceivably
be a JMS message. Once a j2ee event is generated, then teh biz
processing would be entirely within the J2EE domain (programming wise),
with all complexities of the devices itself well abstracted. 
<blockquote type="cite"
 cite="mid...@we...">
 <pre wrap="">

3) J2EE developers currently have 100% control over any web applications that
they develop but it is unlikely that J2EE developers will be personally
configuring, deploying and managing these new Internet-connected embedded
devices on a company's intranet. As indicated above, IT support personnel will
most likely be doing this job. This new scenario entails splitting the
responsibility/control for this class of application between the J2EE
developers and the IT support personnel which has not been encountered before. 
What are the best-practice strategies for handling this new scenario?</pre>
</blockquote>
The bridge-approach above will provide the necessary separation from
teh devices domain to the applications domain. 
<blockquote type="cite"
 cite="mid...@we...">
 <pre wrap="">

4)  As things stand right now, almost no one in the traditional embedded
systems community has any idea what a J2EE application server is nor even what
the function of an enterprise system is in general.  Conversely, almost no J2EE
developers have ever had their hands on any type of embedded systems and, at
best, most only have a vague idea of what their capabilities are.  Before the
"sensor to boardroom" vision can be realized these two communities will somehow
need to be brought closer together.

With respect to the J2EE developer community, what might be some promising ways
to raise its level of awareness with regards to this issue?  Once the awareness
level is raised, what are some workable strategies for enabling J2EE developers
that are interested in moving into this new and promising area of monitoring
and controlling the physical world to start gaining some experience with these
technologies?

</pre>
</blockquote>
Guess one key aspect here is to identify biz cases where the devices
intergate into core biz applications. (This would also be the key for
getting budgetary approvals). Assuming there is a biz case, then the
main challenge will be to integrate the two domains- devices/embedded
world 
 
<blockquote type="cite"
 cite="mid...@we...">
 <pre wrap="">

I know that this has been somewhat of a large amount of information to relay
all at one time but these are some of the main issues that this group has been
working on for over a year now.

Don't feel like you need to comment on everything that has been listed above
but we would appreciate hearing your perspective on any parts of it that you
find especially interesting.

</pre>
</blockquote>
Will be glad to keep the dialog going. Ultimately organisations look
for solutions to solve their problems. The solutions themsleves will
always be integral (all aspects addressed). To that end any enabling
pieces that can integrate the devices &amp; the application tiers, will
help deliver better solutions. 
 
Cheers, 
Ramesh 
<blockquote type="cite"
 cite="mid...@we...">
 <pre wrap="">
Thanks,

Ted Kosan

__________________________________
Do you Yahoo!?
Yahoo! Finance: Get your refund fast by filing online.
<a class="moz-txt-link-freetext" href="http://taxes.yahoo.com/filing.html">http://taxes.yahoo.com/filing.html</a>

-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps &amp; Web services for Linux with
a free DVD software kit from IBM. Click Now!
<a class="moz-txt-link-freetext" href="http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click">http://ads.osdn.com/?ad_id=1356&amp;alloc_id=3438&amp;op=click</a>
_______________________________________________
Embedlets-developer mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Emb...@li...">Emb...@li...</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/embedlets-developer">https://lists.sourceforge.net/lists/listinfo/embedlets-developer</a>
  </pre>
</blockquote>
<br>
<div class="moz-signature">-- <br>
<table style="width: 95%;" font="arial" size="1" border="0" padding="0">
  <tbody>
    <tr>
      <td style="vertical-align: top; font-family: arial;"><font
 ="arial" size="1">Ramesh <a href="http://www.jroller.com/page/rameshl">
Loganathan</a></font></td>
      <td style="vertical-align: top;"><br>
      </td>
    </tr>
    <tr>
      <td style="font-family: arial; width: 70%;"> <font ="arial"
 size="1">VP,
Engineering&nbsp; <br>
      </font></td>
      <td style="font-family: arial;"> <font ="arial" size="1">Ph:&nbsp;
(+91) 40 341
1672 </font></td>
    </tr>
    <tr>
      <td style="font-family: arial;"> <font ="arial" size="1"><a
 href="http://www.pramati.com">Pramati</a>
Technologies, Hyderabad, India </font></td>
      <td style="font-family: arial;"> <font ="arial" size="1">Cell:(+91)
98 490 42997 </font></td>
    </tr>
    <tr>
      <td style="font-family: arial;"><font ="arial" size="1"><a
 href="http://devportal.pramati.com"><span
 style="text-decoration: underline;">devportal.pramati.com</span></a></font></td>
      <td style="font-family: arial;"><font ="arial" size="1"><a
 href="http://www.jroller.com/page/rameshl">&lt;views&gt;</a></font> </td>
    </tr>
  </tbody>
</table>
:-)
<br>
<font ="arial" size="1">
"Logic is a systematic method of coming to the wrong
conclusion with confidence.." -- Murphy
</font></div>
</body>
</html>