What Are the Differences Between Tunnel Resources and Web Resources?
Supported Architectures Differ
Tunnel resources support both B/S (browser/server) and C/S (client/server) architecture applications.
Web resources support only B/S (browser/server) architecture applications.
Different Access Methods
The iOA client must be installed for tunnel resources, and they can be accessed only through the service backend address.
Web resources do not require client installation. You can access services through a browser or other methods, and access is supported through frontend addresses or custom domain names.
Different Address Types for Access
Tunnel resources can be accessed only through the backend address.
Web resources support access through frontend addresses or custom domain names. Access through backend addresses is prohibited.
Summary of Key Differences
Architecture compatibility: Tunnel resources can adapt to more complex C/S architecture applications, such as traditional desktop clients, while Web resources are only suitable for web-based applications.
Access threshold: Tunnel resources require a client and are suitable for strict control scenarios, while Web resources have zero client dependency and are suitable for quick access.
Address access rules: Backend addresses are forcibly hidden for tunnel resources, and only standardized entry points are exposed. Web resources provide friendly access entry points through frontend addresses/custom domain names, while backend details are shielded to enhance security.
Why Are Web Resources Not Displayed in the Client?
Web resources are designed for clientless scenarios and are currently not supported for delivery to the client homepage.
How to Configure a Custom Domain Name for a Web Resource?