API support for Livereport creation/updates

Vikas Mann · 2023-05-01T20:35:32+00:00

There was an error rendering this rich post.

We are converting a customer database platform from Oracle to PostgreSQL. As part of this, one of the requirement is to also convert the existing Liveports in the Content Server from Oracle to PostgreSQL (e.g. syntex changes).

As there are 1k+ livereports in the system, we are planning to export all livereport SQLs from Content Server schema and work on the conversion externally outside the Content Server. After the conversion, the livereports need to be updated in Content Server with the new SQLs.

I have a technical question in order to execute this process in a more automated way.

1) Does Content Server (v22.4) have API support (REST, SOAP etc.) for creation and updates of livereports e.g. update the SQL?

Find more posts tagged with

SOAP

Content Server

Comments

appuq

My gut feel is a LR is a dangerous object to be manipulated by an external tool and that may be the reason why OT does not want to do any programmability to its support.However the SQL that a LR executes is in the extendeddata of the node so any decent tool who can perhaps reach that ,for e.g a custom WR tag could probably accomplish that.I think Christopher Meyer @Chris Meyer also has some experience in this subject.

In retrospect as one of the gurus of OT Chris Webster pointed out if people added queries in ANSI SQL then all database vendors are supposed to honor that,I know it is easier said than done,regardless wanted to point that out.

This site does not get read by OT people but see if I can tag @Nizar Ghazal who always have some trick up his sleeve:)

Most likely if you compared the 1k+ LR extended data more than likely half of them might be copies of one another so it may be done as an analysis job as well.At one of the previous projects we did this we exported the extendeddata and did a lot of optimization on its use.tools,excel,notepad++ etc.

If you exported the LR from the source system as a transport,each one of them is actually a XMLExport with options and mostly the readable part is base64 enoded.You probably could replace that with the correct postgres sql things .not sure if that would be easy….Note OT does not expect you to unzip it out so you may have to cheat it by using a 7zip or winzip to appy the changes :)

Even if creation of a LR is not supported by a API like SOAP or REST what prevents you from creating a LR and copying it en-masse?

Vikas Mann

Exporting and importing using ExtendedData seems like the best option for doing it in bulk. But I need to validate if there will be any incompabilities in the ExtendedData value between Oracle and PostgreSQL.

Thanks for your inputs. I have reached out to other experts on the subject too for their opinions.

Nizar Ghazal

Since LiveReports aren't versionable, your best bet is dumping all the rows with LRs from DTree and doing a syntax scan to identify which ones need to be updated, or doing the same from the admin pages, which gives you syntax that way.

Come up with a conversion scheme to identify Oracle-specific terms that need to be changed.

The page for export is kind of annoying to select each LR you want, so you can probably do this to just check everything off and deselect what you don't need (built-in LRs): $("input[type=checkbox]").prop('checked', 'true');