Blue chip professional skills from an independent

Other CODA interfaces

In this context we define an interface as a way to interact with the CODA product /database other than the normal front end user screens.

The CODA Interfaces detailed elsewhere on this site are:

  • web services;
  • XMLi;
  • table link;
  • callable link.

eCustomiser and direct database access achieve some of the functionality of an interface, but also have other abilities, so we would class them separately.

In nearly all cases these interfaces will be fine for people's requirements. Some other ways to interact with CODA are provided; a quick summary is provided below.

What are the other interfaces?

There are a few other interfaces, which we mention here for completeness. In theory they are completely usable, but in practice there is not really much need nowadays.They are:

  • OLE object link;
  • other command line utilities;
  • database direct bulk load.

What can they do?

OLE object link

This is a wrapper for callable link, introduced a number of years ago to keep pace with the then 'current' Windows technology. Things have moved on nowadays, and we would not recommend using this; XMLi calls exist which achieve the same effect and are a lot easier to use. Whilst the necessary XMLi licence might have a cash cost, you will save a lot of development time in using it instead of OLE object link.

Other command line utilities

These are such tools as assisting with allocation runs (oas_allocchain etc), balance audit (oas_balaud), pay runs (oas_payauth et al), reminder letters (oas_remconfirm etc), ledger updates (oas_ult) and others. These can be very useful for large sites where there are large quantities of data to process; they can be set to run overnight via a scheduling tool.

Database direct bulk load

There is a program provided (named oas_filedtl) that is advertised as being able to load data into CODA faster than the link processes will allow. It needs to be used in combination with the database's own bulk load tools. There is a good description of how to use this in the CODA documentation; however, it will generally be easier/safer to use the link tables and oas_dtl. Oas_filedtl is provided for 'ultimate speed' of loading documents but on modern servers you generally have enough horsepower that the normal table link process will be adequate nine times out of 10.

How can we help?

We have experience of using these utilities and would be very happy to work with you to tailor them and integrate them into your end-to-end CODA solution.