|
Summary
|
|
JudicialOutlook was designed to be implemented in many possible ways. It's
possible to implement a staggard rollout approach as well as a complete
implementation. Because the scheduling and docket management is the "hub" it is
suggested that a Court start by implementing the scheduling as one of the first
stages. |
|
|
|
Infrastructure implementation |
|
Microsoft SQL Server is the native database server used to develop the
JudicialOutlook products. Although it can be implemented on other database
platforms
(see product specs)
it is suggested that, in the case of a new server installation, it be Microsoft SQL Server 2005 or
2008.
|
|
|
|
Web Services / SOAP |
|
JudicialOutlook accesses and maintains its datasource connections using SOAP-XML
based objects and methods. All integrated products also use this business/data
layer to interact with the respective datasources.
|
|
|
|
|
|
|
|
|
|
|
|
Individually Available Products
|
- JudicialOutlook 2009
- JCalendar 2009 Web Standard
- JCalendar 2009 Web Enterprise & Hosted
- JDocs 2009 (Word component)
- JCast 2009 (RSS casting solution)
- JDocket 2009 (Docket management)
- JCourier 2009 (E-Filing)
- JForms 2009 (InfoPath component)
|
|
|
|
Licensing and Services |
-
Windows XP and Vista +
-
Windows XPe
-
Windows Mobile 5.0 - 6.1 +
-
Microsoft PPC 2003 |
|
|
|
Supported application versions |
-
Microsoft Office 2003 - 2007
|
|
|
|
Other technologies |
-
Microsoft .Net 2.0 - 3.5
-
Microsoft Silverlight 2.0 (Client-side web interfaces)
-
Microsoft ClickOnce (release and distribution management)
|
|
|
|