content_image/1005319.jpg
GLYPH<SM590000> Centrally managed and supported Infrastructure : Where a single team owns the API Connect Cloud (including gateway definitions, gateway mapping and TLS profiling), all options are available for splitting of teams. However, when there is no centralized team exists, API Provider teams need to manage their APIs. This means that each team should have their own organization if teams are intended to be isolated and decoupled. 

It is worth noting that teams that exist in their own organization will have their own portals. Yet, they might still be tightly coupled to other teams on the same cloud for upgrades, certificate management, and gateway provisioning. 

GLYPH<SM590000> Isolated and independent development teams: Teams can manage their API lifecycle without interaction and in some cases awareness of other teams. By setting permissions and roles at any of the levels managing the API lifecycle without interaction can be achieved, but this ties in with other considerations like one portal. 

Even when teams are isolated, there might still need coordination from a central team to keep consistent API naming conventions, exposure requirements, for example only to select organization types, and deployment timelines. 

GLYPH<SM590000> Isolation of billing, security, roles, and registration: Certain aspects that are defined at the organization layer would need to be considered and might include how API Provider teams log in to API Connect, how billing is configured, and whether TLS Profiles are available to other teams in a tightly restricted API management environment. 

These four factors along with the roles, responsibilities, and actions that are detailed for each API Connect level need to be considered in unison for a clear and scalable approach when splitting teams. The use of the matrix looks to set recommendations at a high level, but each organization has different needs and as such one size will not fit all. 

## 8.4 Automated provisioning of a new API provider team 

As new API Provider teams join the API Connect Cloud, you need the ability to quickly provision new deployment targets. Typical targets include a new Organization with a Catalog, a new Catalog in an existing Organization, or a new Space in an existing Catalog. 

New teams have a variety of requirements. They need administrators and owners that are assigned, the fully qualified deployment target must be passed to API deployment teams, new TLS profiles might need to be added for both upstream and downstream authentication, new gateway clusters must be created, new communities and elementary tests must be completed to confirm that the setup was successful. 

## Manual process 

Initially a manual process might be used to quickly onboard teams that want to use API Connect. This manual process is likely to be communication heavy and requires both infrastructure and API deployment teams for task completion and verification. 

Typical tasks from an API Connect perspective that might need completing will be as follows (Table 8-2). 

<img src='content_image/1005319.jpg'>

