Adobe Connect Support Blog

Add a Custom Page to an On-Premise Adobe Connect Domain

This article pertains only to on-premise Adobe Connect deployments.

Note: This article contains an image. You may need to refresh the WordPress page in your browser to view it.

As with the version.txt page in Adobe Connect, you may allow direct access to a page in Adobe Connect. The version.txt is is a fitting example because it is viewed by appending version.txt to the Adobe Connect Fully Qualified Domain Name (FQDN).

The version.txt is found in the common directory on the Adobe Connect server so you may also find it at this URL:

The feature.xml file in Adobe Connect is edited to allow access to the version.txt file without appending the common directory depicted in the URL above; version.txt is found in /appserv/common however you you don’t need /common to call it because of the /appserverv/apps/feature.xml entry below. You can just hit /version.txt on the FQDN and it works. That is because in feature.xml you have this entry:

  1. <!–  friendlier version of /common/version.txt  –>
  2. <feature name=”version.txt” protocol=”content”>
  3. <attribute name=”path” value=”version.txt”/>
  4. </feature>

For example, if you have an html page called ‘test.html’ and drop it in /appserv/common, but don’t want /common in the path to gain direct access to it, you can add this to feature.xml:

  1. <!–  friendlier version of /common/test.html  –>
  2. <feature name=”test.html” protocol=”content”>
  3. <attribute name=”path” value=”test.html”/>
  4. </feature>

Then, after cycling the Adobe Connect services, you can call https://fqdn/test.html instead of /common/test.html

Adobe Connect 12, Adobe Connect 12.2, Clustering, Connect Server, General, Install, Uncategorized, XML API

Join the discussion