Technical Notes |
|
In some environments, users may want to launch a Reflection for the Web session from an existing web page; a page on your company's intranet, for example, rather than from the default links list page included with Reflection for the Web. This technical note describes how to modify a web page to include a hyperlink that launches a Reflection for the Web terminal session.
If your Reflection for the Web installation uses None, Single Sign-on through IIS, Single Sign-on through Windows or LDAP Access Control, follow these steps to create the hyperlink:
Note: If your session is an unprotected static session, it will not appear on the Links List page. Instead, record its name from the web-servable directory in which it resides. (Unprotected static sessions are a non-default type of session that require custom, manual configuration and are not widely used.)
Dynamic Sessions are the default type of session in Reflection for the Web. Dynamic sessions are generated by Reflection management server when a session is requested. These sessions are not associated with a physical HTML file on the web server. If your session is dynamic, use the following example code:
To start Reflection for the Web, <A HREF="javascript:void(window.open('https://<your server>:<your port>/<application context name>/RwebSession.do?link=<session name>'))">click here</A>.For example:
To start Reflection for the Web, <A HREF="javascript:void(window.open('https://mycompanyserver.mycompany.com:443/rweb/RwebSession.do?link=mysession'))">click here</A>Protected Static Sessions are associated with a physical HTML file located on the web server. The request for a protected static session goes through the Reflection for the Web authentication and authorization process before it is served. Protected static sessions appear on the Reflection for the Web Links List page. If your session is a protected static session, use the following example code:
To start Reflection for the Web, <A HREF="javascript:void(window.open('https://<your server>:<your port>/<application context name>/RwebSession.do?static=true&link=<session name excluding .html>*u002ehtml'))">click here</A>For example:
To start Reflection for the Web, <A HREF="javascript:void(window.open('https://mycompanyserver.company.com:443/rweb/RwebSession.do?static=true&link=myProtectedStaticSession*u002ehtml'))">click here</A>Unprotected Static Sessions are associated with a physical HTML file located on the web server. They are accessed by direct URL addresses and do not take advantage of the Reflection for the Web authentication and authorization process. Unprotected static sessions do not appear on the Reflection for the Web Links List page. If your session is an unprotected static session, and the .html for it is located in the /session folder under webapps/rweb, use the following example code:
To start Reflection for the Web, <A HREF="javascript:void(window.open('https://<your server>:<your port>/<application context name>/session/<session name>.html'))">click here</A>.For example:
To start Reflection for the Web, <A HREF="javascript:void(window.open('https://mycompanyserver.mycompany.com:443/rweb/session/myUnprotectedStaticSession.html'))">click here</A>.