We have a proven web application architecture that supports multi-tenancy
without partitioning.
A CL command creates an "environment" for each tenant.
Each tenant has their own HTTP server instance and web portal instance via
URL sub-domain (i.e. tenant.domain.com).
Each tenant has their own set of library lists, and IFS root directory.
A CL command starts a tenant environment.
A CL command ends a tenant environment.
Every IBM i web application launched by clicking on a portal menu item
adopts the library list pertaining to that tenant.
All IBM i Jobs for each tenant run under a set of subsystems assigned to
that tenant (facilitates workload management).
We should schedule a demo.
</vendor>
In the absence of an environment like that, the fall-back appears to be
the use of IBM i partitioning, with each tenant getting their own partition.
Most web-application architectures are distributed - web applications run
in one-to-many virtual machines and connect to a database that is running
in another virtual machine. Have you considered that?
As an Amazon Associate we earn from qualifying purchases.
This thread ...
Re: multi-tenant issues with stored procedures, (continued)
This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
