Bulk object create and update in agile plm.
Is it possible to create or update objects in agile plm without using agile api.?
Can we write some plsql or SQL to create or update objects in agile from backend db?
I am looking for a solution where bulk objects can be created and updated in agile with some business logic checks. The business logic checks would be needed to process the objects in agile. It can include advance search of agile to be implement for business logic checks.
Please let me know your suggestions..
Thanks in advance .
Hi
A part of this is possible but not advisable. If something breaks in the process then Oracle won’t support your there. Creation of any kind of objects starting from Item to Change and others require data manipulation in multiple tables so not a safe approach.
Coming to update part, It is possible and i personally have done it quite a few times. To proceed with that you need to test it thoroughly in your non-prod environment. To state a few updates i tried as test is Page-Two,Page-Three values, status change, User group name changes etc, they worked fine. At times they require a bit of time to reflect on front-end after you update them from back-end. Still i try to avoid this from back-end unless i have no choice.
So for Create personally Not Advisable, for Update proceed with caution is what i can suggest.
Regards,
Arif
Hello
To your question on update
<<Do you mean db changes take lot of time to reflect in UI>>
Primary issue is if the item is already in the cache and you update it via backend, Agile doesn’t know about the changes and it will just show what it has. It will requery from DB when something else changes on the object via UI OR you restart Agile. So, it is unpredictable
For mass updates, we typically use Agile import. We would split the file into multiple chunks and run it on multiple machines concurrently
Agree with Arif on avoiding creation of objects via backend. We have used API to create. Similar to import, we break into into chunks and run it concurrently to reduce the time it takes. Hope this helps
Creating or updating objects using SQL*Plus or PL/SQL is highly not advised. There are 2 HUGE problems with trying to do this :
1) For you to figure out how it should be done would require a LOT of work, as the schema is rather complicated and there is NO public documentation on how things work.
2) If you do manage to mess things up by doing this, Oracle will make you pay through the nose (and most likely all other body orifices) to fix it.
Arif is very correct, if you do update things using SQL*Plus or PL/SQL, it will take time for those updates to show up in in the GUI. Agile uses a large memory cache to keep the data for frequently checked/updated objects handy, so it does not have to access the database every time an object is searched for. The amount of time it takes for an object to fall out of the cache (and thus forcing a database query) is highly dependent on your environment and the size of the cache.
I suspect that rchinnia has the right idea. Do this via a batch job and Import if you don’t want to use the API. I have been working with the Agile database for almost 2 decades, and so I probably know more about it than at best a handful of people (outside of Oracle, anyway). Do not try this using SQL*Plus or PL/SQL.
Even if you can figure it out (or find someone who can) and get it to work correctly, note that you run the risk of having to test and possibly update it every time you upgrade Agile (not that there will be any such past 9360). Whereas if you use Import, it will always work. And after thinking about it for 5 minutes, you run the risk of your SQL process not working even if all you do is simply update the configuration.
Oracle provides a high-speed dataloader to select third-party support organizations, without support.
It’s been years since i used it, but we were able to load thousands of records in minutes.
The Oracle Agile Support manager owns it & might provide the loader on request.
How many business objects are you talking about? Agile’s import utility is quite fast. It’ll create the object update the object if the field is mapped correctly and there’s an update to be made. I feel as though that without API, Import utility will be well worth your time.
