JIKD Integration Architecture

1
JIKD Integration Architecture

• T.J.Rogers
• UMIACS (rogers_at_cs.umd.edu)
• University of Maryland at College Park

2
JIKD Integration

• Issues
• Numerous, large data collections (want to avoid
  cloning huge dataset everywhere).
• Large, multidisciplinary, somewhat distributed
  research effort (diverse set of software
  languages, libraries, and approaches used).

• Solution approaches
• Use commercial data stores and tools where
  possible and efficient.
• Decouple GUIs from data sets (allows
  light-weight web-served GUIs).
• Wrap search and analysis processes as server
  module function calls.
• Wrap raw data sets and access APIs as proxy
  server modules (1stJava RMI, 2ndTCP/IP,
  3rdWSDL).

3
JIKD diagram box color coding
Green (dark) Existing Commercial API
Green (light) Existing JIKD code module (Beta)
Yellow Developing JIKD code module (Alpha)
White Proposed JIKD code module (unimplemented)
Black Targeted research / feature focus
(unintegrated)
4
eMail Proxy service layer (1st)
(Java Object I/O)
(String URL I/O)
MJE_ProxyServer (RMI)
MJE_ProxyServer (TCP/IP)
Caches larger data blocks as Web Server
files, reducing proxy band-width.
MJE_Proxy
JDBC
JavaMail API
JIKD_MH Store Provider
??? Store Provider
MSTOR Store Provider
Local eMail stores (Raw format)
Caches discovered network nodes in RDF store
as appropriate.
5
eMail Proxy commands

• getEmailAddresses(Collection)
• getTimeBounds(Collection)
• getEmailMessage (ID)
• getEmailMsgHeaders(ID)
• getEmailMsgBody(ID)
• getEmailMsgAttachCount(ID)
• getEmailMsgAttachment( ID, Nr)
• getSenders(ID)
• getReceivers(ID)

• getEmailMsgKeyWords(ID)
• get/putEmailMsgCategorys( ID, x)
• get/putEmailMsgSummary( ID, x)

Generally, echos JavaAPI Command set, plus
shortcuts for discovered Addendum data.
6
JIKD client / server proxies
JIKD eMail analysis GUI
Java NetLens GUI ??
MJE_ProxyClient_RMI
MJE_ProxyClient_RMI
Internet layer
MJE_ProxyServer_RMI
7
JIKD RMI proxy client modules

• Exposes the underlying proxy servers interface
  (objects in/out) to the client application (GUI,
  other module, etc.).
• Hides the underlying RMI communications
  requirements (executing a proxy interface call
  automatically handles server connections as
  appropriate).
• Prototyped eMail proxy layer first working on
  PhoneCall (Voice) proxy layer next (other modules
  to follow as necessary).
• Each proxy client main method provides module
  initialization and test call encoding to help
  guide developers.

8
JIKD Integration JavaDocs
http//neoborg.cs.umd.edu/TJR/Docs/JavaDocs/JIKD/
9
JIKD Black-Box hookup
(All back-end processes)
Prob-Reasoning
eMail/Phone Alignment
Phone messages
Summarization
MJV_Proxy Service
Threading
Feature Based Indexing
MJE_Proxy Service
eMail messages
Caches discovered network nodes in RDF store as
appropriate.
Social Networks
10
JIKD GUI data connections
NetLens Direct hookup for 09 Sept Demo
GUI should rely on distributed services which
provide quick retrieval and display of derived
data as well as raw-data files (drill downs).
ODBC
??? JIKD Thin-Client GUI ???
MJV_Proxy Service
MJE_Proxy Service
Caches discovered network nodes in RDF store
as appropriate.
?