Date post: | 31-Dec-2015 |
Category: |
Documents |
Upload: | allan-green |
View: | 214 times |
Download: | 0 times |
Slide 1
For information contact Product Management at [email protected]
This presentation contains forward-looking statements that are based on management’s expectations, estimates, projections and assumptions. Forward-looking statements are made pursuant to the safe harbor provisions of the Private Securities Litigation Reform Act of 1995, as amended. These statements are not guarantees of future performance or functionality and involve certain risks and uncertainties, which are difficult to predict. Therefore, actual future functionality, features, results and trends may differ materially from what is forecast in forward-looking statements due to a variety of factors.
Slide 2© 2010 Ingres Corporation
Confidential — © 2010 Ingres Corporation Slide 4
Why a New Set of Tools?
“infodb”
“logstat”
Putting GUI interface on command line tools
Confidential — © 2010 Ingres Corporation Slide 5
Why a New Set of Tools?
Replacement of “Old” Interfaces
“netutil”
“ipm”
Confidential — © 2010 Ingres Corporation Slide 6
Why a New Set of Tools?
Set of rich GUI tools on all platforms, not just Windows
“ivm”
“vdba”
Confidential — © 2010 Ingres Corporation Slide 7
Why a New Set of Tools?
Other Goals & Benefits: Improved workflows
– Drag and drop (direct manipulation)– Normal conventions (Cut, Copy, Paste)
Innovations– Discover and control multiple Ingres installations from
a single tool– Support multiple Ingres versions at the same time
Platform to build custom Tools– Rich API available to build on– Easy-to-customize user interface
Confidential — © 2010 Ingres Corporation Slide 2
Tools API (Application Programming Interface)
What’s the foundation?
Confidential — © 2010 Ingres Corporation Slide 10
Tools API Architecture
Loadable Tools Library: Independent of Ingres version (10.x, 9.3, 9.2 at
least) “Static” library that accesses Ingres internals
without Ingres running C/C++ Interface with Java/JNI version One per Ingres installation Multiple modules can be loaded at once
– II_SYSTEM set automatically
Confidential — © 2010 Ingres Corporation Slide 11
Tools API Architecture
Remote Command Server: Basically an RPC (Remote Procedure Call)
interface Protocol is carried on top of SSL (Secure Socket
Layer) connection (encrypted) Every function completely checked for correct
number and type of arguments– Impossible to send “format c:” remote command
Every action authenticated by Ingres authentication
Confidential — © 2010 Ingres Corporation Slide 12
Tools API Architecture
Ingres Discovery Server: Normally a daemon process that simply keeps
track of Ingres installations Listens on “known” TCP/IP port First one running becomes the “Master” server All other processes simply register themselves
with Master Master responds to requests for list of installations Master also acts as HTTP server Tools API function to request installation list on
given host machine
Confidential — © 2010 Ingres Corporation Slide 13
Tools API Architecture
Want More Information? http://community.ingres.com/wiki/Tools_API_Home
– Preliminary design documents– February 11, 2010 presentations– This presentation– Discussion pages
More next week
Confidential — © 2010 Ingres Corporation Slide 15
Tools User Interface
Built using portable code: 100% Pure Java Apache Pivot Framework (http://pivot.apache.org)
– Designed by VMWare, in use in VMWare Server 2.0– Apache-licensed, Rich Internet Application framework– Active development and community
UI Layout using XML (WTKX) files– Declarative interface simplifies coding– Even allows code scripting (JavaScript) within UI layout
Prototype code currently running (already) on Windows, Mac OSX, Linux
Confidential — © 2010 Ingres Corporation Slide 20
Tools User Interface
Want More Information? http://community.ingres.com/wiki/Ingres_Director_Ho
me– Functional Specification version 1.0.1– Discussion pages
Again, more next week
Confidential — © 2010 Ingres Corporation Slide 22
Plans – Code Sprint Results
“Sprinted” along with DBMS & OpenROAD Review of Functional Specification Valuable feedback and suggestions Spent one day of training with two Ingres
engineers Another day of coding and testing
Confidential — © 2010 Ingres Corporation Slide 23
Plans – Product Release
Guidelines for Release: “No product released before its time”
– Don’t want to have yet another incomplete Tool Usability Testing
– Easy to use for novices– Familiar enough for migrating users– Inviting enough for Roy Hann to use daily ;)
Available on major Ingres platforms Support for Ingres IVW, 10.x, 9.3, 9.2 (?!)
Confidential — © 2010 Ingres Corporation Slide 24
Plans – “Orchestram” Integration
“Director” fills a hole in “Orchestram”: Need for local Ingres Administration Need for Ingres Discovery
“Director” needs “Orchestram”: Software delivery (installation) Job scheduling Reporting / Charting Monitoring capability (Nagios-compatible)
Confidential — © 2010 Ingres Corporation Slide 25
Plans – Timeline
Watch the Community Wiki
Watch my blog at:– http://community.ingres.com/forum/blogs/
whiro01/