We are upgrading our Tuxedo application to support a multi‑tenant architecture. As part of this upgrade, we have created two separate server groups. Each server group is configured to connect to a different database group, and each group is assigned its own WSL port.
The application starts successfully. However, when we submit transactions, the data is being fetched from the wrong database. It appears that the database connections are being established dynamically at runtime, and cross‑database access is occurring even though the client is connecting through the correct WSL port associated with its server group.
We need guidance on the correct architectural approach to ensure strict isolation between tenants so that:
- Each WSL port routes requests only to its designated server group
- Each server group connects exclusively to its assigned database
- No cross‑database data access occurs under any circumstances
Could you please advise on the recommended configuration or architectural pattern for implementing multi‑tenant isolation in oarcel Tuxedo 22c?