Using aliasId as a request parameter
In Avaya Context Store Snap-in, you can use the Context alias feature to retrieve the same context object using alternative identifiers. Context aliasIds provide more flexibility in retrieving and updating context objects.
You can index a context object by using the usual contextId and groupId. The object can also be indexed with context aliasIds such as a customer account number, a billing authorization number, and a mobile phone number. A customer object can be retrieved using any of these aliasIds to retrieve the context object.
Context aliasIds are subject to the same restrictions as all other context identifiers - such as permissible characters and length - and must be unique in the data grid.
You can add up to three aliasIds for any one context object. In addition to defining aliasIds when a context object is first created, you can add and delete aliasIds post creation. For more information about adding, updating, or deleting an aliasId, see Avaya Context Store Snap-in Developer Guide.
Note:
If you add three aliasIds for a context, you must reduce your context data size to 1.5 KB to achieve the same capacity as that certified through performance tests. The performance tests test with 2KB context objects.
Each aliasId for a context must be unique within the context object, and the Context Store data grid. The same aliasId can exist in each cluster in a Geo solution, but the routingId distinguishes them from one another. Any attempt to duplicate an existing aliasId or retrieve a context using an unknown aliasId results in error messages.
The aliasing capability impacts the performance of Context Store, in particular latency, due to the increased number of lookups and data comparisons required to find the correct object in the data grid.
When creating a context, you can specify up to three aliasIds as parameters in the requests. For all other by aliasId operations, provide only the aliasId that identifies the context on which an operation is to be executed.
For more information about the usage of the aliasId feature, see Avaya Context Store Snap-in Developer Guide.
