Hi.
If it is Dev Portal 3.5 it need to be one portal to one gateway.
On portal 4.x you may have different strategies (considering on premises configuration):
a) one portal server for each environment ( each env has your own server )
b) one portal server with one tenant for each environment (each env has your own tenant on a shared server)
c) one portal server with one tenant and multiple proxy gateways configured. (one server has one tenant and each environment is a different proxy gateway)
The option C is the scenario used to explain the
Deployment TypesThe approach will depend on various aspects like company security rules (e.g.: dev and qa envs cannot share resources with production) and api publish type (
Portal Published?,
Gateway Published? mixed?)
------------------------------
Sr. Consultant Services
HCL Enterprise Studio
------------------------------
Original Message:
Sent: 10-15-2019 06:27 AM
From: Pratyush Singh
Subject: Number of Portals per Environment
Hi All,
I have a below query as below:
1.) How many number of API Developer Portal we can configure per Environment , like for DEV or QA or PROD , do we need 1 Portal for each or just 1 portal for all environment (DEV, QA and PROD) ?
2.) Do we have such recommendations in API Portal or API Gateway Document, if yes please share the link.
Just wanted to know the Pros /Cons of it . So please help accordingly.
Best Regards
Praty