When a user clicks a resource name (a link) on a custom web page, the URL behind it must have one of following formats:
https://<server>/userportal/?appinfo=https://<webserver>/<app-name>.js&theme=<theme-name>#/launch
or
https://<server>/<theme-name>/?appinfo=https://<server>/<app-name>.js#/launch
where:
<server> is the IP address or FQDN of the RAS Secure Gateway server.
<webserver> is a web server from where information about published resources and authorized users is served.
<app-name>.js is a payload in JSONP format containing user credentials and a published resource information. Note that since payload must contain user credentials, the payload should be generated dynamically for every user and every application, desktop, published resource to which a user has access through the web portal. For testing purposes, you can create a temporary ".js" file with all the required information and save it in a folder on your web server. The payload structure is described in the section that follows this one.
<theme-name> is the name of the Theme that will be used. This parameter is optional if you use the first URL format.
Note: You can use the /RASHTML5Gateway suffix instead of /userportal, but this is not recommended.