I'm trying to create a storage block using this SDK and view it's contents using the Commander Utility. I have successfully created the block and can read back (according to non error return values). I am able to see the storage block I created using the Commander Utility but am unable to see its' contents.
Does anyone know how I would give permission to the Commander Utility to view the contents of the created storage block?
Yes I have. I'm using the SDK in a Linux environment to locally create an enterprise, application, and storage block. As of right now I am only able to use the Commander Utility on the localhost to see this "TestBlock". If I use connect from another machine I cannot see the storage block. I am able to see the Vendor/Application associated with the storage block.
I would like to use this 3PDS storage block as a mailbox. My question is how do I make this storage block visible to foreign machines and allow this block to be read and writeen? The session handle associate with the allocation block only alows me to read and write while running my program. When used from another machine the same session and block handles are return invalid.
All the return values of these function are valid if done from a local machine and I can see the entire hierarchy of the block (enterprise, application...) using the Commander Utility except for the storage block.
Thanks for the response. I do not believe I was setting up permissions incorrectly. Using the AMT WS-Management Flows document, sections 4.18 and 4.19, I am now able to locally read and write to a location in 3PDS and remotely view it using the Commander Utility.
I have seen the HLAPI but I've found the storage sample that is part of the WIndows section of the SDK (/Windows/Intel_AMT/Samples/WS-Management/Storage/C++/StorageFlow.cpp) to be more helpful.
My focus right now is on prolonging the timeout associated with a session handle so I am able to access the wrtten part of 3PDS indefinitely.