# Source architecture
<a name="source-architecture"></a>

The following diagram shows a typical OpenText Customer Experience application architecture that uses OpenText core components, custom functionalities connected to the OpenText core components, and databases, files, and repositories. Although an OpenText architecture varies for each customer implementation, the diagram shows the typical components and these are covered by this guide. 

![The different components of an OpenText migration to the AWS Cloud.](http://docs.aws.amazon.com/prescriptive-guidance/latest/migration-opentext-teamsite/images/opentextmigration-diagram1.png)


The main architectural elements that are targeted for migration by this guide are described in the following table. 



- ****Solution****
  - Main elements to consider for migration

- **OpenText TeamSite**
  - TeamSite instance
  - Content store
  - Configuration files (for example, tsgroups.xml or roles.xml)
  - Custom code – Code customizations such as integrations with external data sources or custom-made functionalities
  - Authoring database – This database is typically deployed in a dedicated database server
  - TeamSite search – Deployed in its own server (optional)
  - OpenDeploy:[See the AWS documentation website for more details](http://docs.aws.amazon.com/prescriptive-guidance/latest/migration-opentext-teamsite/source-architecture.html)

- **OpenText LiveSite**
  - LiveSite instance
  - Web assets repository 
  - Configuration files
  - Custom code
  - A runtime database deployed on its own server
  - OpenDeploy: [See the AWS documentation website for more details](http://docs.aws.amazon.com/prescriptive-guidance/latest/migration-opentext-teamsite/source-architecture.html)

- **Indexed search**
  - This can be an OpenText LiveSite content server or a similar index search implementation, such as [Apache Solr](https://solr.apache.org/)

- **OpenText Media Management or MediaBin **
  - MediaBin instance
  - Custom code for customizations or existing plugins
  - MediaBin asset repository
  - MediaBin database



The migration strategy and AWS products and services that you can choose depend on the characteristics of your source system and your individual requirements. The following table describes the most common strategies for the migrations. 


|  |  |  | 
| --- |--- |--- |
| Element type | Target AWS services | Migration strategies | 
| OpenText core components |  [See the AWS documentation website for more details](http://docs.aws.amazon.com/prescriptive-guidance/latest/migration-opentext-teamsite/source-architecture.html)  | [See the AWS documentation website for more details](http://docs.aws.amazon.com/prescriptive-guidance/latest/migration-opentext-teamsite/source-architecture.html)Typically, you install new instances of the products. Installation of each instance type is fully automated. | 
| Custom functionalities and integrations |  [See the AWS documentation website for more details](http://docs.aws.amazon.com/prescriptive-guidance/latest/migration-opentext-teamsite/source-architecture.html)  | [See the AWS documentation website for more details](http://docs.aws.amazon.com/prescriptive-guidance/latest/migration-opentext-teamsite/source-architecture.html)Provision and configure the deployment pipelines that are used for the maintenance and evolution of the OpenText platform. These pipelines are used to deploy code.<br />Some dependent functionalities that are built as OpenText TeamSite customizations or as external applications can be containerized or refactored as Lambda functions. If this is the case, you can orchestrate the serverless functions through API Gateway. | 
| Databases |  [See the AWS documentation website for more details](http://docs.aws.amazon.com/prescriptive-guidance/latest/migration-opentext-teamsite/source-architecture.html)  | [See the AWS documentation website for more details](http://docs.aws.amazon.com/prescriptive-guidance/latest/migration-opentext-teamsite/source-architecture.html)Typically, you can migrate databases to Amazon RDS DB instances by using AWS Database Migration Service (AWS DMS). | 
| Storage |  [See the AWS documentation website for more details](http://docs.aws.amazon.com/prescriptive-guidance/latest/migration-opentext-teamsite/source-architecture.html)  | [See the AWS documentation website for more details](http://docs.aws.amazon.com/prescriptive-guidance/latest/migration-opentext-teamsite/source-architecture.html)Data repositories are copied to the Amazon EBS volumes associated with the OpenText core component instances. <br />S3 buckets can be used for larger data repositories, such as OpenText MediaBin or the Media Management assets repository. |