This adapter enables the connection to a Microsoft Azure Table Storage to perform various operations.
Properties
|
|
Defines the operation executed by the adapter Possible values:
|
Parameters
|
|
Adapter main class (do not change!) Possible values: de.softproject.integration.adapter.microsoft.azure.table.MicrosoftAzureTableStorageAdapter: main class (default) |
|
|
Name of the Microsoft Azure storage account Possible values: Any valid string, e.g. |
|
|
Password of the Microsoft Azure storage account Possible values: Any string containing the serial key provide by Microsoft Azure, e. g. |
|
|
Azure Cosmos DB endpoint |
|
|
Name of the table where entities are stored Possible values: String containing the ID for the new table (information) Table names have the same character requirements as database IDs. Database names must be between 1 and 255 characters, and cannot contain |
|
|
Element of the primary key Entities with the same partition key can be queried faster, and inserted/updated in atomic operations. Possible values: Any string containing the partition key |
|
|
Element of the primary key An entity's row key is its unique identifier within a partition Possible values: Any string containing the row key |
|
|
Use to compare Possible values:
|
|
|
Indicates if Possible values:
|
Status values
|
|
The operation was executed successfully |
|
|
An error occurred during the operation's execution |
|
|
Operation Operation |
Input
The adapter expects an XML document as input
-
In case of
InsertEntityoperation, an XML with the following structure is expected:XML<?xml version="1.0" encoding="UTF-8" <Entity> <Properties1 name="Department" value="ITAdministration"/> <Properties2 name="Address" value="C\Pirandello"/> <Properties3 name="Name" value="Paolo"/> <Properties4 name="Surname" value="Green"/> </Entity>
The property (key)
namecannot be protected words likeId.
-
In case of
ModifyEntityoperation, an XML with the following structure is expected:XML<?xml version="1.0" encoding="UTF-8" ?> <Entity> <Properties name="Name" value="Carlos" /> </Entity>
-
In case of
QueryOfSubsetEntityPropertiesoperation, an XML where the required properties are specified is expected:XML<?xml version="1.0" encoding="UTF-8" ?> <Entity> <Property name="Department" /> <Property name="Surname" /> <Property name="nonExistingProperty" /> </Entity>
Output
The adapter returns different kind of documents depending on the executed operation:
-
Output for operation
RetrieveEntity:XML<?xml version="1.0" encoding="UTF-8" <Entity partitionKey="ITEmployee" rowKey="ref-0001"> <Properties name="Department" value="ITAdministration"/> <Properties name="Address" value="C\Pirandello"/> <Properties name="Name" value="Paolo"/> <Properties name="Surname" value="Green"/> </Entity>
-
Output for operations
RetrieveAllEntitiesandRetrieveRangeEntities:XML<?xml version="1.0" encoding="UTF-8" ?> <ListEntities> <Entity partitionKey="ITEmployee" rowKey="ref-0001"> <Properties name="Department" value="ITAdministration" /> <Properties name="Address" value="C\Pirandello" /> <Properties name="Surname" value="Green" /> <Properties name="Name" value="Paolo" /> </Entity> <Entity partitionKey="ITEmployee" rowKey="ref-0002"> <Properties name="Department" value="Developments" /> <Properties name="Address" value="C\Francisco" /> <Properties name="Surname" value="Lopez" /> <Properties name="Name" value="Luis" /> </Entity> <Entity partitionKey="ITEmployee" rowKey="ref-0003"> <Properties name="Department" value="Sales" /> <Properties name="Address" value="C\Espada" /> <Properties name="Surname" value="Red" /> <Properties name="Name" value="Paula" /> </Entity> </ListEntities>
-
Output for operation
QueryOfSubsetEntityProperties:XML<?xml version="1.0" encoding="UTF-8" ?> <ListEntities> <Entity> <Property partitionKey="ITEmployee" /> <Property rowKey="ref-0001" /> <Property name="Department" value="ITAdministration" /> <Property name="nonExistingProperty" /> <Property name="Surname" value="Green" /> </Entity> </ListEntities>
Properties
partitionKeyandrowKeyare always returned because they are used to uniquely identify the entity. Since the operation is able to return multiple properties of more than one object, it is important to assign the properties to the associated entity.