OpenInsight 9.4 “Roll Up” Patch v5.1 released


OpenInsight 9.4

Revelation have recently released a brand new roll up patch for OpenInsight, taking the series to version 9.4.4.

This patch includes additional fixes to RTP16 (xlate), all the patches and fixes from the previous “Roll Up” patches, as well as:

  • An updated datatbl.dll and oinsight.exe to fix changes in how Windows displays forms.
  • A fixed DICT_MFS_BUILD to ensure that associated group names are included when a dictionary’s %FIELDS% record is rebuilt.
  • A fixed RTP16 (XLATE) to restore previous functionality when explicitly passing a null in parameter 5.
  • An enhancement to OIPI (VSPRINTER1) to improve performance.

After installing this patch, your system will report that it is running version 9.4.4.

This zip file contains an updated RevelationDotNetSetup.msi, RevelationDotNetSetup.exe, revjapi.dll, OESocketServer.jar, OInsight.exe and an OpenInsight RDK, for use in OpenInsight 9.4.0 systems.

This patch replaces the original “Roll Up” Patch v1 released on March 3, 2016, the second “Roll Up” Patch v2 released on March 8, 2016, the “Roll Up” Patch v3 released on June 13, 2017, and the “Roll Up” Patch v4 (and v4_1) released on January 5, 2018, and includes all the previous fixes for OpenInsight 9.4.

Works Members can download this patch from the Works Downloads section of our web site.

Advertisements

OpenInsight 10 named in DBTA’s 2019 Trend-Setting Products


DBTA_TSP_2019
You can call it the new oil, or even the new electricity, but however it is described, it’s clear that data is now recognised as an essential fuel flowing through organisations and enabling never before seen opportunities.  However, data cannot simply be collected; it must be handled with care in order to fulfil the promise of faster, smarter decision making.

More than ever, it is critical to have the right tools for the job.  Leading IT vendors are coming forward to help customers address the data-driven possibilities by improving self-service access, real-time insights, governance and security, collaboration, high availability, and more.

To help showcase these innovative products and services each year, Database Trends and Applications magazine looks for offerings that promise to help organisations derive greater benefit from their data, make decisions faster, and work smarter and more securely.

This year their list includes newer approaches leveraging artificial intelligence, machine learning, and automation as well as products in more established categories such as relational and NoSQL database management, MultiValue, performance management, analytics, and data governance.

This year, Revelation Software are proud to have OpenInsight 10 featured in DBTA’s “Trend-Setting Products in Data and Information Management for 2019”.  You can view the full listing, featuring OpenInsight here.

Click HERE for Mike Ruane’s Product Spotlight on OpenInsight 10.

Universal Driver 5.2 released


benchtestresultsUniversal Driver NUL v5.2 for OpenInsight 10 – This is a 64-bit server side installation for use with OpenInsight 10.  The Universal Driver NUL 5.2 allows files from OpenInsight 10 and OpenInsight 9.4 to share the same Universal Driver.  This version has been updated with the latest ACE libraries.

Management of the Universal Driver is done via the Management Console.  When paired with OpenInsight 10.0.4 and above “child” processes launched from OpenInsight can be configured so that they do not consume additional license seats.

Universal Driver NUL v5.2 for OpenInsight 9.4 – This is a 64-bit server side installation for use with OpenInsight 9.4 and a 32-bit client side installation for use with OpenInsight 9.4.  The Universal Driver NUL 5.2 allows files from OpenInsight 10 and OpenInsight 9.4 to share the same Universal Driver.  This version has been updated with the latest ACE libraries.

Management of the Universal Driver is done via the UD Manager.

Software downloads can be found on the Universal Driver page.

Starting the Presentation Server


didyouknowoiWhile most of an application’s configuration information is stored in various application database records, there are some startup options that need to be determined before the actual database can be accessed (i.e. before the OpenEngine virtual machine is loaded).

The Presentation Server can be configured with a wide range of options at startup, via means of an RXI configuration file, and/or a set of command line switches.  Both methods support nearly all of the same options, but any option specified by a command line switch always overrides the same option specified in the configuration file.

Presentation Server configuration (RXI) files

There are nearly twenty options that can be applied when starting the Presentation Server and adding these as switches to a command line shortcut can be a tedious and error-prone exercise. In order to remedy this, it is possible to create an RXI (Revelation Xml Ini) file to store these options instead, where they are read and parsed by the PS during its boot-up sequence.  Read On…

What’s New in OpenInsight 10.0.4


didyouknowoiStarting with OpenInsight 10.0.4, “child” processes launched from OpenInsight can be configured so that they do not consume additional license seats. In particular, CTO, AREV64, BRW, and O4W calls (using the engine server’s built-in web server) made from a copy of OpenInsight will not count against the licensed count of users.

For example, a single user copy of OpenInsight can now run the IDE, a CTO session, and generate a BRW report at the same time.

Note that this enhancement requires both OpenInsight 10.0.4 (or above), and the Universal Driver 5.2 (or above).

OpenInsight 10.0.4 will work with the Universal Driver 5.1, but it will not exhibit these license enhancements until it is
“paired” with a UD 5.2.

To take advantage of this license enhancement for O4W and engine server tasks, users/developers must update their eserver.cfg file (either directly or through the Settings dialogs). In particular, any passwords that are currently explicitly embedded in the eserver.cfg can be replaced with an asterisk (“*”); this indicates that the specific connection should use the enhanced licensing.

This also has the additional advantage of no longer requiring manual updates to the eserver.cfg file when passwords are changed for the applications or users defined in the connection string. (As an additional enhancement, the username can also be replaced with “*” if you wish to use the ‘default user’ created for an application).     

OpenInsight 10 (10.0.4) will be the final version to target Microsoft’s .Net framework version 4.6.  The next version of OpenInsight 10 will target .Net 4.7.

Certain versions of Windows (for example, those running Windows 10 version 1507 or earlier) may have difficulty installing the .Net 4.7 framework.  Before you install the next release of OpenInsight 10, please ensure that all required systems have been upgraded to .Net 4.7.  For more information click HERE.

Click HERE for a copy of the OpenInsight 10.0.4 ChangeLog.

Modernising the writing, debugging and management of Symbolic Code – Scheduled for OI 10.0.4.


youtubeoi10-e1529069260513.pngI was recently working on a new application and I came across an issue with one of my symbolic dictionary items.  The code was pretty simple, but not being a professional developer, I just could not see what the issue was.

Now, I would usually have dropped in a simple debug statement to see what variables were being set when and with what values.  This would have quickly told me where I had gone wrong in my code.  So, I dropped a Debug statement into my symbolic code, saved the table, ran the form and we dropped into the debugger.

Alas, no variable information is displayed in the debugger for the symbolic code and I was none the wiser for my efforts.  Back to the very simple Symbolic Code editor and I had to work things out for myself.  With only three lines of code, I actually managed to find the error pretty quickly, but just imagine if that was a 100 lines of code, a thousand lines of code or more – yes I have seen this on more than a few occasions.

I was talking to Bob Carten during one of our exploratory and (for me) learning sessions and I mentioned how difficult the symbolic editor is to work in.  He laughed and asked if I’d be interested in a new feature coming in OpenInsight 10.0.4 and which specifically addressed my issue.

In fact, Bob told me excitedly that this new method of writing symbolic code, opens up a whole host of other possibilities.  He touched on them, but I am afraid that he quickly left me scratching my head.  For example, why would you want to have a three part conversion, at least that’s what I think we were talking about?  Anyway, that’s for another time.

For now, you can see this new technique in my latest OI10 Quick Start Video which has just finished uploading to my YouTube channel.

Elegant debug statements


youtubeoi10.pngI recently uploaded an OpenInsight 10 lesson and at the beginning of the video I talk about a rogue debug statement that I had left in my code in the previous video (on purpose you understand).

Mark Marsh (Professional OpenInsight Application Developer) emailed me with an extremely useful tip to using debug statements in code and which will avoid the issue and embarrassment of leaving a rogue debug statement in your code.  It is also great for those of you with OpenInsight development teams because the trick is user specific.

I’d like to offer Mark a huge thank you for sharing this invaluable tip with me and for enabling me to then share it with you.

You can see the video here and the tip is in the video comments – it’s well worth a look.