In general, there are organizations that use their own applications to bring about their purposes and accomplish their tasks in a unique way. Some may use uncommon applications that cover their purposes and not all are highlighted as application templates. But TAC is capable of publishing those uncommon or organization’s unique applications using Custom Application templates.
TAC provides two types of custom web application templates:
Custom web application (Site’s host name)
Custom web application (own host name)
Administrator may publish almost all types of generic web applications using either custom web application (Site’s host name) or custom web application (own host name) template.
Please identify which application template is best suited to publish your own application through TAC.
Definition of a Custom web application (Site’s host name):
The term “Site’s host name” in the custom web application is used for applications that are accessed using Site’s host name. What if the Site has many applications that are using Site’s host name? How does TAC identify which request comes to what server? The answer is: Site’s host name application, known as non-AAM (Alternate Access Mapping) like applications, are using its site host name with a unique ID to launch the applications. Applications published using the Site’s hostname template use the Site’s host name and therefore rely upon the HAT mechanism (or Host Address Translation).
Example: The TAC Site’s host name is the same for all published applications. Therefore, when a request comes to TAC using Site’s host name, how does TAC identify which relevant application to publish the request? This is where HAT becomes relevant. When the Host Address Translation comes into play to identify the request, TAC attaches a unique ID to each incoming request and the request is then sent out to the appropriate internal server.
To publish Custom web application (Site’s host name), do the following:
1) Select the Site and Click Add under Applications
2) In Add New Application wizard select Custom (Site’s host name) under web dropdown menu.
3) Click Next.
4) Provide an application name and an application type.
5) Click Next.
6) Select Server-type, Single application server or farm of application servers.
7) Click Next
8) Define the internal application server properties.
Addresses: Define the back-end web application server IP Addresses or subnet that web servers belong to, or the Host name or the Regex.
HTTP Ports: HTTP port numbers, comma-separated or port range or type ‘ANY’ for any port number
HTTPS ports: HTTPS port numbers, comma-separated or port range or type ‘ANY’ for any port number
Paths: Enter web application paths
Select authentication server for the application if the application uses Single SignOn (SSO).
a) Click Add under Single SignOn (SSO).
This will open Authentication and Authorization window.
b) Select the Authentication Server from the configured servers.
c) Click Select.
d) Select Pre-authentication type.
e) Click Next.
Under the security window, select Authorize All Users to authenticate all users.
Note: If you select the Authorize All Users checkbox, it will provide access to all valid users except users that have Deny Attribute set on Users and Device Management console. Please see Users and Device Management for more details.
Under Security window, you can select the access policies that are defined for your infrastructure. You may use predefined access policy templates or you can define your own custom access policies. Before you define any access policies for an application, you have to create the policies. See Access Policy for more details.
Under the application link, you can provide a name for the application. The URL shows how the application link is rendered in the portal. You can select an icon for how the application appears in the portal.
Configure how application logoff is handled (optional):
a) Enter Log off URL path.
b) Select Call application log off URL on backend server to logoff the user from backend server.
c) Select Redirect User to TAC application log off page that users will be landing to TAC log off page. Note: This option will become active upon selecting first option.
d) Select Remove application specific SSO credentials on application log off to wipe SSO credentials on application log off.
e) Select Trigger automatic application log off in case of no activity (no data exchange) after value of seconds. Enter the seconds in the box.
Your Custom application is ready to publish. Remember to apply configuration to take affect your changes in TAC.