An embedded blob is when the blob data is contained within the clip itself. As such, a separate blob is not created thus there is no separate content address for the blob.

Non-embedded blobs are stored separately and have their own content address. The clip references the blob content address when the clip is written. Because the blob is its own entity, multiple clips can reference the same blob (singe instance store). This cannot be done using embedded blobs.

Hi Dennis,
Thanks for the reply. It is helpful but you did not answer my main question.

What I need is the small utility that will display the BLOB IDs
(content addresses) for all BLOBS in a given Clip ID. The utility will help
during the QA testing phase to verify the data deduplication for the documents
larger than the embedding threshold we are using in our application.

What I am currently doing is writing the content of the ClipRAW open stream to
the file (using JCASScripty) and than comparing the eclipblob md5 xml tag from
the RAW files for different document clips.
Example of the eclipblob entry in the clip RAW file:

As far as I can see, the Centera SDK does not provide a direct way to get the BLOP content addresses.
Is there any better way of getting this information programmatically short of parsing the clip RAW file/stream?

Thanks,
andrej

This might better be answered on our developers portal

https://developer-content.emc.com/

Yes, they will have their own ID's. The embedded C-Clip will have the clip ID.

This might better be answered on our developers portal

https://developer-content.emc.com/

EMC Corporation

Robert Pruden

Advisory Field Support Specialist

Hi Robert,

So how can I obtain these BLOB ID's programmatically (using Centera SDK API)?

Thanks,

andrej

Hi all

What you need to do is to write an application that uses the Centera CLI and iterate through all the tags.  As you can see in the CDF below the value eclipblob md5 lists the Content Address for the BLOB.

C:\CLI>c-get EIHH1UPM18KQFe5NKH1EP54ED98G4152GPUAC00K3U4U382I017O7@194.124.156.134?c:\tmp\dd1.pea -cdf






















"true" permissions="438" winattributes.indexed="true" winattributes.archive="true" winattributes.compressed="false" wina
ttributes.encrypted="false" winattributes.hidden="false" winattributes.system="false" winattributes.temp="false">

Holger

Hi Andrej,

I see you posted a question regarding getting the Blob ID programmatically and that your question in this post appears to have been answered. Was this a correct or helpful answer? If so could you please mark the question as Answered (helpful or correct)?

Thanks for your assistance and participation in the Support Forums.

Regards,

Ronan

Hi Ronan,
I labeled two answers as helpful and none was really a correct/complete answer.
The answer from Holger Jakob is really the closest to full answer, but since I labeled it as Helpful
I can't label it as Correct at the same time.

Regards,

Andrej

The answer from Holger Jakob is really the correct answer, but since I labeled it as Helpful I can't label it as Correct at the same time.

Using Centera SDK you would need to obtain the CDF file (using "raw" calls) and parse it (possibly using XML tools) to obtain the value of BLOB ID.