Tenant Module in DataPower
Hi,
Has anyone used Tenant features of DataPower. Does it really add any advantage when you have single API Connect Portal with different organisation with the other line of business.
Another bit which I am confused on how it is linked with the API Connect ? How can I specify the firmware upgrade only with the particular DataPower Cluster from API Domain ? In the IBM documentation, it is mentioned that we can create only two tenant, so suppose I have two line of business using same API connect portal but same DataPower as API Gateway, how's the tenant solution going to make my life easy ?
Well, I'm just Support, not an actual user, so can only sell the usecase again.
Tenant feature allows you to have some extend of separation.
For example,
- you can run your traditional DP workloads on the landlord with some certain firmware level you know works well for those.
- then run your API Connect workload of line of business A on tenant A with maybe a more recent version of DataPower because it has a certain feature or fix that that line of business hotly needs.
- then run your API Connect workload of line of business B on tenant B with maybe another version of DataPower that this line of business has tested and approved integration with.
Also if one of those tenants runs into unexpected behaviour or some resource issue, only one line of business is affected, not the other.
Of course there are appliance wide resources like networking that are not separated that 100% to a tenant so that can still impact all, landlord and tenants.
So in APIC, as I understand it, you'd configure tenant A (like a standalone DP) for LoB A and tenant B for LoB B.
I hope this is at least a bit illustrative or helpful and not just Sales blahblah, but keep on shooting questions so we can try to clear up the idea for you.
What about the network connection, The knowledge center is mentioning that the tenant will have its own management/data interfaces, Does this mean to assign mgt1 for example for the tenant? and another eth*xx* interface for the data? I would suggest also to add the some diagram to describe the suggest structure, and how services will be created within the tenant.
My curiosity is if any one has used one tenant for production, and the other tenant for staging code. When code is ready to be activated in production you would switch traffic to the new tenant. Both tenants would technically be the same DataPower instance, just one tenant would have new services/code updates other would be current released version of code. Idea being is if there were issues with the DataPower updates/deployments, rollback would be simple to get back to a working version.