03-10-2016 03:45 PM
Hello all,
I was wondering if there was a way to interface with Oracles Agile PLM through LabVIEW. My company moved its documentation control to Agile and I was hoping to be able to interface with Agile to allow an operator to pull up the most recent version of a test procedure or a profile file with test equipment settings from a control VI. I have done the cursory Google search and searches on this forum and Oracles forum. Any information would be greatly appreciated. Thank you.
03-11-2016 02:27 AM
I don't know anything about this (never even heard of the software), but what you should be looking at is what APIs it has for working with it (which I'm guessing it does) and that's what you will want to use.
I do have one customer who told me "we want you to get the settings from PDM", which I assume is an Oracle product too, but that ended up simply being files on a network path, so I didn't see any details beyond that. It's possible you can configure your software to do the same and to simply expose the files as files on a network drive.
07-21-2016 03:50 AM
Hi,
Has anyone been able to do this?
Cheers, Ben
07-21-2016 04:53 AM
My answer would be the same as it was last time - find out which APIs it has with someone who knows the system. The only difference would be that since I made that reply that same customer also requested that we interact with their PLM system and we had a meeting where we determined that it is possible, but I don't remember any details about it and nothing has moved on it since. I'm assuming the interaction we decided on was either files, SQL or web services, but that's a guess. I seem to remember it also required some work on the PLM side.
07-21-2016 06:11 AM - edited 07-21-2016 06:24 AM
Years ago I used the REST API of Agile to download a test procedure.
You need to know the Agile Smart Object URL path to your specific server, and of course have the REST API enabled.
https://blogs.oracle.com/PLM/entry/smart_urls_enabling_reference_1
The whole process is contained in one VI. See attached (LV2014).