Having downloaded and verified a fresh build, I set about looking at tutorials and examples of dissectors.  The intention is to capture network traffic arriving and leaving the iigcd process, currently JDBC and .NET over TCP/IP, and to dissect the packets.

I eventually stumbled on Creating Your Own Custom Wireshark Dissector by Ken Thompson and after a couple of hours had the inklings of a dissector.

The protocol is composed of a network level envelope around a transport level packet which surrounds a Data Access message.  The initial dissector will dissect the network and transport layers, but the message dissection was a bit more complicated than time allowed.

The code is available from https://bitbucket.org/notnull/idamp-dissector-plug-in/, feel free to contribute

Related posts

• Ingres Migration Toolset
• Ingres command line RPM installation
• Ingres doc search plug-in updated
• Ingres package install ain’t misbehavin
• Ingres Documentation site relaunched

The project was divided into the GUI and the migration library and the initial release was a re-factored version of the initial Swing application together with extensive release processes built around it.   Thank heavens for maven lifecycle plug-ins.

One of the more serious challenges was the incorporation of the antlr parser into our build that lead to the development of an ant plug-in that split the generated Java code into multiple interfaces.

As you will notice the source for the project is not hosted on the original Ingres Migration Toolset project; that was our original intention, but our attempts to maintain the development history in mercurial when integrating changes back to the subversion repository failed (lesson learned).

Related posts

• Debugging the Hibernate project with Eclipse
• Button clicks do nothing in Ingres Database Workbench, Eclipse and its derivatives
• Rapid
• Data Access Message Protocol – Wireshark dissector
• Ingres command line RPM installation

Related posts

• Ingres package install ain’t misbehavin
• Data Access Message Protocol – Wireshark dissector
• Ingres Migration Toolset
• Ingres doc search plug-in updated
• Ingres Documentation site relaunched

As a consequence if installing packages by-hand (not using the express install script or the GUI installer) the set-up process will not be run on any versions of Linux.  Post installation configuration is initiated by running either:

service ingresXX configure [response file name]

or

service IngresXX start

• XX should be replaced with the instance code in the package name used to install with II by default.
• A response file name should be supplied with configuration values that differ from the default.

Related posts

• Ingres command line RPM installation
• Data Access Message Protocol – Wireshark dissector
• Ingres Migration Toolset
• Ingres doc search plug-in updated
• Ingres Documentation site relaunched

I created a simple Google gadget to create a document search query that can be added to your iGoogle home page. It took a couple of failed attempts to get it submitted to the Google gadget directory, but the Ingres Doc Search link can be used to install it directly.

Related posts

• Ingres doc search plug-in updated
• UK IUA Conference 2009
• Ingres Engineering Summit 2008
• Google Summer of Code (GSoC) 2008
• Data Access Message Protocol – Wireshark dissector

The Ingres Community wiki page has some simple instructions to get started.  As a guideline to the cost, I ran the image for a week and could probably run it for about 21 weeks to match the cost of a similarly specified bare metal machine.  I uploaded data to Amazon Simple Storage Service (S3) to reduce the cost of moving the data set and removing the need to run a machine for the transfer.

Fast track your Ingres VectorWise evaluation with the AMI.

Related posts

• UK IUA 2010
• Vectorise your data
• Ingres Code Sprint 09
• Data Access Message Protocol – Wireshark dissector
• Ingres Migration Toolset

Related posts

• Cloudy with Ingres VectorWise
• UK IUA 2010
• Button clicks do nothing in Ingres Database Workbench, Eclipse and its derivatives
• Donnez-moi un café Ingres
• Ingres Migration Toolset

Most notably, I extended the work started by Enrico Schenk in introducing additional Ingres dialects. There are now three possible dialects.

• IngresDialect – for use with Ingres II 9.2
• Ingres9Dialect – for use with Ingres II 9.3
• Ingres10Dialect – for use with Ingres II 10.0 – at the moment this is a place holder and uses the 9.3 dialect

The Ingres9Dialect switches uses the ISO date/time types and functions for mapping to their Hibernate equivalents. This changes the behaviour from the IngresDialect which used ingresdate type and functions.

Further changes to Ingres9Dialect will include the introduction of auto-increment columns; a whole host of additions will be required for the Ingres10Dialect and not forgetting the inclusions from the Ingres GeoSpatial project.
A list of new features introduced into each release is published on the “Ingres New Features Per Release” page.

Related posts

• Debugging the Hibernate project with Eclipse
• Useful or useless? Follow on post …
• In the market for JDBC properties
• Donnez-moi un café Ingres
• Google Summer of Code (GSoC) 2008

drop ima_dbms_fis;
\p\g
register table ima_dbms_fis (
        server varchar(64) not null not default is
                'SERVER',
        id integer4 not null not default is
                'exp.adf.adg.fi_id',
        complement integer4 not null not default is
                'exp.adf.adg.fi_cmplmnt',
        type varchar(20) not null not default is
                'exp.adf.adg.fi_type',
        flags integer4 not null not default is
                'exp.adf.adg.fi_flags',
        opid integer4 not null not default is
                'exp.adf.adg.fi_opid',
        args integer4 not null not default is
                'exp.adf.adg.fi_numargs',
        dtresult integer4 not null not default is
                'exp.adf.adg.fi_dtresult',
        dtarg1 integer4 not null not default is
                'exp.adf.adg.fi_dtarg1',
        dtarg2 integer4 not null not default is
                'exp.adf.adg.fi_dtarg2',
        dtarg3 integer4 not null not default is
                'exp.adf.adg.fi_dtarg3',
        dtarg4 integer4 not null not default is
                'exp.adf.adg.fi_dtarg4'
)
as import from 'tables'
with dbms = IMA,
structure = sortkeyed,
key = (server);
\p\g
grant all on ima_dbms_fis to ingres;
\p\g
grant select on ima_dbms_fis to public;
\p\g

Adding this table to ima_dbms_types and ima_dbms_operators adds the ability to retrieve the list of functions and their signatures.  The query makes use of an internal function iitypename which translates the numeric type code into a name.

select
    a.name,
    case when a.type='COMPARISON' then
        trim(iitypename(b.dtresult)) + ' = ( ' +
        trim(iitypename(b.dtarg1)) + ' ' +
        a.name + ' ' +
        trim(iitypename(b.dtarg2)) + ' )'
        when a.type='OPERATOR' then
        trim(iitypename(b.dtresult)) + ' = ( ' +
        trim(iitypename(b.dtarg1)) + ' ' +
        a.name + ' ' +
        trim(iitypename(b.dtarg2)) + ' )'
    else
        trim(iitypename(b.dtresult)) + ' = ' +
        a.name + '( ' +
            case when b.dtarg1 != '' then trim(iitypename(b.dtarg1)) else '' end +
            case when b.dtarg2 != '' then ', ' + trim(iitypename(b.dtarg2)) else '' end +
            case when b.dtarg3 != '' then ', ' + trim(iitypename(b.dtarg3)) else '' end +
            case when b.dtarg4 != '' then ', ' + trim(iitypename(b.dtarg4)) else '' end
        + ' )'
    end as signature
from
    ima_dbms_operators a,
    ima_dbms_fis b
where
    a.opid = b.opid
group by a.name, 2
order by a.name

Some sample output from this query:

|name                          |signature                       |
|soundex                       |char = soundex( text )          |
|soundex                       |char = soundex( varchar )       |
|sqrt                          |float = sqrt( float )           |
|squeeze                       |nvarchar = squeeze( nchar )     |
|squeeze                       |nvarchar = squeeze( nvarchar )  |
|squeeze                       |text = squeeze( c )             |

So in answer to my own question; yes, it is useful.  I’ll be trying this on an IngresGeospatial build when I get my hands on one.

Related posts

• Debugging the Hibernate project with Eclipse
• Hibernate 3.5.0-Final released
• Google Summer of Code (GSoC) 2008
• IMA Guru (Pronounced, I’m A Guru) – I definitely am not
• Data Access Message Protocol – Wireshark dissector

You have?  Then you must have suffered some of the same frustrations and annoyances of ensuring that the prerequisites and dependencies of each component are satisfied; ending up with downloading some huge quantity of software. The plethora of download, installation and configuration steps required just to get to the starting point can be enough to dissuade all but the most tenacious.
The helpful people at Exadel have taken those many steps to get to the starting point and created an Amazon Machine Image (AMI) called Cloud in a box that includes all the components to create Rich Internet Applications (RIA). With an Amazon Web Services (AWS) account you can launch an instance of the image and take your first step to being productive.  Read the blog post about it RIA on the Cloud with RichFaces and Ingres and register for a free account on the Exadel Web site for more detailed instructions.

Related posts

• Ingres command line RPM installation