Key concepts about the platform
The OpenText™ Cloud Platform separates application development, application management, and application runtime into distinct layers. This architecture allows teams to build an application once, manage it centrally, and deploy it to one or many isolated environments.
Understanding the relationship between Organizations, Applications, Tenants, and Subscriptions is essential for designing, deploying, and managing applications effectively. The platform intentionally separates application design from application runtime, allowing a single application to be deployed to multiple environments while maintaining tenant isolation.
Overview
Developers interact with Organizations, Application Extensions, Tenants, and Application Subscriptions during the extension application lifecycle, but each serves a different purpose.
Think of the platform as having two distinct responsibilities:
- You manage an application extension at the Organization level.
- You run and consume that application extension through a Subscription within a Tenant.
| Layer | Purpose |
| Organization | Where application extensions are configured, designed, versioned, and managed. |
| Application Extension | Development of an application extension occurs in Thrust Studio. |
| Tenant | Where users, data, security, integrations, and application instances live. |
| Application | The OpenText Core application and application blueprint. |
| Subscription | Connect an application to a tenant. |
Understanding the application lifecycle
The easiest way to think about the platform is to follow the application lifecycle from creation to usage.
- Develop
A developer creates the application extension in Thrust Studio. - Publish
The application extension is registered and managed through the Organization in Admin Center. - Subscribe
A tenant subscribes to the application extension. - Run
Tenant users authenticate, access the application extension, and work with tenant-specific data.
Understanding these layers is key to understanding how applications are developed and deployed on the platform.
Build in Thrust Studio
Application extensions are created and maintained using the Thrust Studio extension for Visual Studio Code.
This is where developers define the application extension's structure and behavior, including:
- Namespaces
- Object Types
- Traits
- Workflows
- Decision Models
- Business Logic
- Application Artifacts
Together, these definitions form the application extension's blueprint.
Think of Thrust Studio as your development workspace. It is where the application extension is designed, versioned, and prepared for deployment.
Admin Center
Organization: Manage the Application Extension
An Organization represents your company's account within an OpenText Cloud region. Application extensions are built in Thrust Studio and then managed through the Organization in Admin Center.
The Organization serves as the governance and lifecycle management layer for applications.
At the Organization level, you can:
- Register and manage applications
- Publish new application versions
- Configure application-level OAuth service clients
- Control application availability
- Manage subscriptions
- Govern application lifecycle activities
The Organization does not contain customer data or business content. Instead, it provides centralized management for the applications your team develops.
Tenant: Run the Application
A Tenant is an isolated runtime environment where applications are used. Each tenant maintains its own users, security settings, integrations, and data.
A tenant contains:
- Users
- Groups
- Roles
- Administrators
- Authentication and SSO configuration
- Integrations
- Runtime application data
- Security and access controls
Everything created or stored while the application is running belongs to the tenant.
Subscription: Connecting an Application to a Tenant
A Subscription links an application to a tenant.
When a tenant subscribes to an application:
- An application instance becomes available within the tenant.
- Tenant users gain access to the application.
- Application data is stored within the tenant.
- Tenant security and authentication policies are applied.
- The application operates within the tenant's isolated environment.
A single application can be subscribed to by multiple tenants, and a tenant can subscribe to multiple applications.