Communication models of remote applications and the Pega Process Fabric Hub
Work management in the Pega Process Fabric Hub is possible because of data publication from a remote application. When you host your instance of the Pega Process Fabric Hub on Pega Cloud, the communication schema depends on the deployment of your remote application.
For example, you need to configure a remote application that you host on an on-premises Pega Platform instance differently than a remote application that you manage in a Pega Cloud environment.When you host your instance of Pega Process Fabric Hub on Pega Cloud or a client-managed cloud, you can choose between the following deployment models for your remote applications:
- An application is hosted on Pega Cloud or a client-managed cloud, and the access is public through the Internet.
- An application is hosted on an on-premises Pega Platform instance and the access is public through the Internet.
- An application is hosted on Pega Cloud or a client-managed cloud, and the access is private through a VPN.
- An application is hosted on an on-premises Pega Platform instance and the access is private through a VPN.
Remote application with public access
When a remote application has public access through the Internet, you create the connection between the application and the Pega Process Fabric Hub by configuring OAuth 2.0 authentication. You do not need to perform any additional configuration, either for remote applications hosted on a cloud or on the premises.
For more information, see Providing access rights for the Pega Process Fabric Hub by editing a service package.
The following figure shows a schema of communication between a remote application that you host on a client-managed cloud and the Pega Process Fabric Hub on Pega Cloud:

Remote application with private access
When a remote application has private access through a VPN, you connect the application to the Pega Process Fabric Hub by establishing a tunnel connection and configuring the OAuth 2.0 authentication.
When you host your remote application on Pega Cloud or a client-managed cloud, you can implement the following solutions:
- VPN tunnel
- Transit gateway
- VPC peering
The following figure shows a schema of communication between the Pega Process Fabric Hub on Pega Cloud and a remote application hosted on a client-managed cloud:

When you host your remote application on the premises, you can implement the following solutions:
- VPN site-to-site connection
- Direct connection
The following figure shows a schema of communication between the Pega Process Fabric Hub on a client-managed cloud and a remote application hosted on premises:

Previous topic Custom connectors for the Pega Process Fabric Hub Next topic Application registration life cycle for third-party applications