A potential client of RAM wants to know answers to these que

On 7/2/2010 11:38 AM, vperumal wrote:

1)Does RAM follows reusable API's/standards for to maintain data
compatibility?

What is the customer's definition of reusable API's/standards and data
compatibility? That is a very broad question.

2) Can we export data from DB2 and import in RAM?
3) Can we export from CQ to RAM and vice versa?

These are totally different usages. DB2, CQ and RAM serve very different
purposes and aren't directly related.

DB2 is a relational database.
CQ is a defect tracking system.
RAM is a published asset manager that allows governance, access control,
searching, storage of assets.

A customer can write a program that will take data from a DB2 or CQ and
create or update assets in RAM. But the data itself is not directly
importable because they are not related.

4)Is data compatibility ensured from one file system to another? How
is this done?

Not sure what they mean by data compatibility. Data is just bits and
bytes and characters. What do they consider compatibility to mean?

Rich

RAM is based on RAS (http://www.omg.org/technology/documents/formal/ras.htm).

You can use OSLC (http://open-services.net/bin/view/Main/WebHome) based API with 7.2.0.2, or Java, Ant API as documented here:

http://publib.boulder.ibm.com/infocenter/ramhelp/v7r2m0/topic/com.ibm.ram.api.doc/topics/overview-summary.html

http://publib.boulder.ibm.com/infocenter/ramhelp/v7r2m0/topic/com.ibm.ram.ant.doc/topics/toc.html

You will have to transform data from your source (DB/CQ Schema) to your specific RAM informational model Schema using the API above, or extending the batch client:

http://publib.boulder.ibm.com/infocenter/ramhelp/v7r2m0/topic/com.ibm.ram.doc/topics/t_extend_batch_api.html