A EMC's technician did a check in my machine with JCenteraVerify, and the retrieve time was 10 times lower.
I realized that the versions of the JCenteraVerify's .DLL are newer than the ones I have. So, I downloaded the Centera_SDK-3.3.718, there's a version of XAM compatible with this version?
Yes, those times seem well below the normal range.
That said, if this is a new system you are developing, the recommended integration path is through the Centera SDK. XAM support for Centera is being deprecated by EMC, see the announcement toward the bottom of the main community page (https://community.emc.com/community/edn/centera).
I don't know if EMC has produced a XAM package compatible with the 3.3.718 SDK series, perhaps someone from the CSE team could comment.
Normally when there is a difference in reading via XAM it's due to using too small a buffer size for the IO, make it as large as the file if possible. Certainly not something small like 8KB
I'm in the process of writing a whitepaper which discusses these sort of differences between the two API so an extract from that...
Under the covers the Xset is actually a "normal" centera CDF and the XUID has the "real" content address in it.
If you base64 encode the XUID when you get it back from a commit, base64 decode it and then the first 8 bytes can be discarded and the content address starts at byteoffset 8 (from 0). You can use that with the Centera API to open the clip.
If you are using non-binding fields you cant directly access these values but if you really need to get at it let me know.
If you havent figured it out for yourself by now by looking at CDFs....
XAM adds xfields to the underlying Centera CDF in a different way to the Centera API. With the Centera API you would porbably just see the equivalent for xfields as custom attributes. However the XAM sdk actually creates each xfield as a tag with the tag attributes of type and value. Here is an example of an xset with three fields as viewed from jcasscript
CASScript>crv
...
so to get the value of your xfields you would need to use FPClip_GetTopTag() to position yourself at the first tag and then use FPTag_GetTagName() to see if you are the correct tag. If not call FPClip_FetchNext() and see if thats it and repeat if not
If it is you can then use FPTag_Get Attribute() providing the Attribute name "value", Note there is no float or double type so you can just use string and do the conversion yourself.
mfh2
1 Rookie
•
208 Posts
980
0
Posted May 28th, 2013 14:00
Hello Cruzcunha -
How big are the streams you are reading back from Centera? And when you say the recovery time is large, how much time are we talking about?
Regards,
Mike Horgan