Object…What?

Object…What?

Until the mid-1970s, most systems were built using functional systems. Object-oriented systems were introduced with a flurry of promises in the early ‘80s, many of which actually proved to be true, for once.

More recently, people have been talking about object-based systems, object stores and object-based file systems. In this article, I’d like to clarify the characteristics of each type of technology. Truth in advertising—there’s a lot of overlap, so I’ll try to smooth out the bumps in the ride.

A walk down the memory lane of object data modeling

A walk down the memory lane of object data modeling

In my last blog, I covered the last ten years working with a particular Objectivity customer. In this blog, I want to go back even further, more than 25 years ago to the start of Objectivity.

Let me start by presenting a brief timeline:

The 1980s: Object technologies became popular, although even prior to that time, objects had been used in some significant projects. These technologies included languages, modeling, tools and databases.
1989: The Object Management Group (OMG) was formed to coordinate and standardize efforts among multiple organizations in different verticals, all trying to leverage the power of objects.
1996: The Unified Modeling Language (UML) was accepted by the OMG, unifying modeling methods from luminaries like Grady Booch, Ivar Jacobson and James Rumbaugh.
2005: A Task Force was set up with OMG to bring together multiple tools in the Business Process space.
2011: The Cloud Standards Customer Council was created.
So suffice it to say that objects have been around for a long time and are still here.

Upgrading Your Federated Database to New Catalogs

Submitted by tnatar on September 6, 2013 - 8:54am Terms used and their meanings fd – federated database db - database old catalogs – pre-R9.0 internal database format new catalogs – R9.0 or later version’s internal database format Reason to upgrade Starting from Release 11.3, support for the old catalog format is no longer available. R11.2 is the last release of Objy that is backwards compatible with dbs using old catalogs. Identify if you are using old catalogs You will most likely have fds or dbs with old catalogs if you created them using a pre-R9.0 version of Objy/DB. You can be using an R9.0 or later version of Objy/DB but still use old catalog fds or dbs. How to check if you have old catalog fds or dbs If you are not sure whether the fds or dbs are using old catalogs or new catalogs, you can determine that by using one of these two methods below: Run oofile on the fd or any individual database files, to see the release with which they are compatible. If the output displays: Compatible with Objectivity release 5 through 11 The fd or db is using old catalogs. If the output displays: Compatible with Objectivity release 9 or later The fd or db is using new catalogs. Write a utility program that calls isR9catalog() on a handle to the fd or an individual database. If the API call returns 0, The fd or db is using old catalogs. If the API call returns 1, The fd or db is using new catalogs. How to upgrade from old catalogs to new catalogs...

Toolrunner: More Administrative Tools

Some of the traditional Objy/DB Admin tools now use a new mechanism of execution known as tool tunner. You can find the change in tool name and tool options below. All tools now require the –bootFile flag with the bootFilePath. The following are a subset of the Objectivity DB Admin tools. More Administrative tools have been added to the tool runner interface which are listed in a separate table after the Tool Runner table.

Here are the list of tools using tool runner:
ooattachdb
oochange
oochangedb
oocheckams
oocheckls
oocleanup
ooconvertformat
oocopydb
oocopyfd
oodeletefd
oodumpcatalog
ooexportfd
ooinstallfd
oolicense
oolistwait
oolockmon
oonewfd
ooschemadump
ooschemaupgrade
ootidy

Managing a Federated Database’s License

The license file is used to access the federated database and must always be up-to-date. If you received a new license from a recent purchase, or you’re replacing an expired license with a new one, the federated database must be updated with the new license information, otherwise, it will use the old license and cause an error. Note: These steps for managing a Federated Database’s License are the same for both Objectivity/DB and InfiniteGraph. Setting up a License File 1. Create a new default license file: a. Check whether a file called oolicense.txt already exists in your installation directory. If so, rename that file. b. Save your new license as a text file called oolicense.txt in your installation directory . Updating a Federated Database’s License Run oolicense with either the -licensefile or -fromdefault option, and the bootFilePath. Example: oolicense -licensefile C:\Program Files\Objectivity 10.2\oolicense.txt C:\Users\johndoe\Desktop\RunApp\app.boot Verifying a Federated Database’s License To display a federated database’s license, run oolicense with the bootFilePath and no other options. Example: oolicense C:\Users\johndoe\Desktop\RunApp\app.boot You can verify the version of the license you are using and when it expires.   To view the full documentation, you may access the following link: Administration...