The other day I was thinking about how our customers are accessing data residing in their webMethods OneData platform. Surprisingly, there are so many ways.
For example, we have customers embedding OneData portlets in some of their applications. This provides read-only access to data, but it’s just like being there. Actually it IS being there, with anonymous user privileges.
We have other customers granting permissions to view only specific data for the intended user through direct links into OneData Objects. Yes, you can actually filter this data which might be useful for sensitive data, or to comply with privacy or other regulatory mandates.
Some of our customers are accessing data in the field using their iPads. This becomes quite handy when you’re on the go and can’t wait until you get to a computer to obtain needed information.
We even have customers who have placed OneData in the cloud, providing data and services to THEIR customers!
As companies scale up, they find that they may need additional database licenses, which can quickly add to their TCO. But we have a solution. Using Terracotta, you can load your MDM repository contents into memory. Not only do you get better performance, but you save the cost of additional database licenses. You only need a small database to persist this data.
To summarize, we have portlets to access mastered data, direct database links to specific data, iPad access, cloud access and in-memory access to trusted data.
In addition, OneData has a unique capability to centrally master data in the enterprise which is external to it’s own repository! It can manage this data as if it were it’s own. Really!
So when I started thinking about the many places where master data can be accessed and managed, I came up with the idea that webMethods OneData is the trusted data everywhere MDM platform. And there you have it.
RSS Feed
Email Subscription
Recent comments