Unsolved

This post is more than 5 years old

2 Posts

1210

June 6th, 2013 13:00

Centera XAM SDK

We have an old Centera application that was written in .NET that used the XAM SDK. Now we need to access that data using Java. I tried to locate the XAM SDK for Java, but to no avail.

Can you do one of two things for me...

1. Provide me with the location I can download the XAM SDK.

2. Provide me with the information on how to tie the Binding and Non-Binding CDFs/Clips together.

I assume the XUID = ClipID. But that gets me the Binding clip, correct? The non-binding clip is different and holds my meta-data. How do I associate the two using the information found using the Java APIs?

Also, the tag names for the Blobs stored in the tags of the binding seem to be encoded. Like if I had a blob named "1", it has a tag name of Zgr. This appears to be a base32 encode of the data? If so, how do I decode that. It isn't a standard base32, They only use capital letters.

Bill

208 Posts

June 6th, 2013 13:00

Hi Bill -

I think you will have to get this data back through XAM.  The non-binding clip ID is stored in mutable metadata inside Centera (the same facility that supports ARM and legal hold); there are no public interfaces to the mutable attributes from the Centera SDK. 

EMC should be able to provide a download for the current XAM interface kit, which includes a Java wrapper.

I think it's likely that you are already aware of this, but: if you want to use XAM and SDK DLLs from a single process you will need to use versions which are built on matching revisions of the underlying FPxxx libraries (like SDK 3.2.705 and XAM 1.0P2 I think).  I bring this up in case you wanted to convert your XAM data, e.g. read back XAM objects and translate them into equivalent SDK objects which are then written back to Centera.

Good Luck,

Mike Horgan

409 Posts

June 7th, 2013 04:00

Hi

As you are using the .NET XAM wrapper you must already have the XAM libraries on your system.

The XUID doesnt = the ClipID but it does contain it - see one of my other posts on converting to the Centera API from XAM

As far as I've found the tag names are not not encoded in anyway however if you have enabled embedded blobs the blob data may be base64 encoded as a tag attribute.  Could you post a cut n paste of what you are seeing?

As Mike said, if you are reading the xset through XAM the binding non-binding cdfs are handled for you.  Are you trying to read the non-binding cdf from the Centera API?


2 Posts

June 10th, 2013 17:00

Previous developers have kept the Binaries and .Net pieces, but no the Java

stuff. I cannot find the download for XAM anywhere on your site. Can you

point me at a resource where I can get it?

Bill

On Fri, Jun 7, 2013 at 7:30 AM, Paul Mckeown

409 Posts

June 11th, 2013 04:00


could you email me directly at paul.mckeown@emc.com confirming that you have a previously developed XAM integration and confirm the revision of XAM you are using and your operating system and I'll see about getting you the .jar JNI wrapper

No Events found!

Top