Atmos- RESTfUL API -C#.NET

Hi Raj,

Any updates for the above issue?

There is not an automated means to handle this condition.  Your application is responsible for managing the namespace of object names and directories when using the Atmos namespace interface.  You could perhaps check to see that an object exists using ListDirectory before you attempt to create it.

Using the Atmos object interface the application developer need not manage the object names, directories, etc.  You would simply use the object ID returned by Atmos to access the object.

Hi raj,

     So is there any ListDirectory method in the wrapper class library?I could not find any. Becoz in the previous post u have mentioned "You could perhaps check to see that an object exists using ListDirectory before you attempt to create it.".

Now i want to retrieve file from the atmos and i can achieve this using downloadhelper (passing the Objectid). Is there any other way to retrieve files? i mean passing filename or using object namespace? How to do this?

Thanks in advance

There's a ListDirectory method in the EsuRestApi class that takes an ObjectPath as input.  It returns a list of objects in the given path.

There is a ReadObject method in the EsuRestApi class that can either read an object based on ObjectPath or an ObjectId.

Hi Raj,

     Now we are working on a tool which provides an option for the user to view all folders and file structure in Atmos. Similar to a treeview (list the heirarchical structure.) is there any othe roption apart from tree view so that user could see the data in Atmos.??

Thanks.

Srini

Srini,

You could use the Atmos namespace interface to display objects in a tree view in your application.  The namespace interface is certainly suitable for applications that require file system semantics.  Your application is responsible for managing the view itself --- you can get a list of directories and objects inside of a given directory through the Atmos API. 

Raj

Have a look at RSA Bsafe as an option for storing the keys.

Hello Raj,

     Is there any option to keep the shared key token in a secured way.So that nobody outside egt to kinow that... right now we are hardcoding that in code to access Atmos. Please help!!!!

Hi Raj,

     We are planning to migrate millions of files to Atmos using our own tool... After migrating files to atmos how could we test whether all files are copied? Need your help!!!!!

My suggestion would be to create a table in a database where you can maintain the relationship between the local file, the remote object ID, and perhaps a hash of the object.  After the migration your application can verify that each object was indeed written to Atmos and use the hash to verify its integrity. 

Thanks for your valuable suggestion... one more thing, when we modify or update files in ATMOS, would there be any logs created internally or our API should handle this logs using metadata?

From a developer standpoint there is logging available necessarily.  Your application would need to manage the fact that it has changed an object if that's important to it. 

Can you provide an example of how you would use metadata to manage changes?  I want to understand your requirements better.

I've a file in atmos and i'm updating the information. From my application before actually updating i set the metadata tag say last modified date as current date.... this is just as an example...  i just want to know apart from API  is there any way like atmos internally creates a log file when a files are modified? if so how?Hope u got my question?

Atmos logs a wide variety of activities internally, but those are only accessible to the administrator of the system --- that information is not available to the developer using the API.