This article contains the release notes for OpenText AppWorks Gateway version 1.2.1.
These Release Notes provide an overview of AppWorks Gateway 1.2.1, including new features, delivery information, and supported platforms. OpenText recommends that you read these Release Notes in conjunction with the documentation included with the software package. If any conflicts exist, the Release Notes supersede the other documentation.
We also recommend that you check the OpenText Developer Site for any patches or documentation updates that may have been posted after the initial release of AppWorks Gateway 1.2.0 and 1.2.1.
|Revision Date||Sections Revised||Description of Revisions|
|2015-03-23||First release.||All new content.|
|2015-03-27||Final release.||Minor updates to content.|
|2015-05-08||Patch 1 Updates.||Changes for AppWorks 1.2.1.|
AppWorks Gateway 1.2.0 Includes the following new features.
- The Single Sign on from Windows Desktop browsers only works for Content Server 10.5 installations.
- Content Server 10 users must disable the OpenText Directory Services (OTDS) single sign-on option in the Advanced Settings of the Appworks Gateway. however they will still be able to login with any OTDS supported user format.
- Content Server 10 users will not have single sign-on functionality, but will be able to login with any OTDS supported user format.
- If Content Server authentication is used, single sign-on is disabled automatically on addition of the Content Server identity provider.
The following new features have been added to AppWorks 1.2.1:
The single sign-on from Windows desktop browsers with SAML, two-factor authentication and Google Oauth 2.0 authentication only works for Content Server 10.5 installations.
The following features have been deprecated in this release:
Downloads and documentation for AppWorks Gateway are available on the OpenText Developer Site.
The software and documentation for AppWorks Gateway includes:
For additional information about AppWorks Gateway, or for supplemental information about related products, refer to OpenText Developer.
This section provides details about supported platforms, systems, and versions.
|Component||Version||Level of Support|
|Tomcat Application Server||7.0.59||C|
|Tomcat Application Server||8.0.21||C|
|Microsoft Windows Server||2012 R2||C|
|Red Hat Linux||6||S|
|Microsoft Windows Server||2012||S|
|Microsoft Windows Server||2008 R2||S|
|Microsoft SQL Server||2012||C|
|Oracle Database||11G R2||C|
Notes on Supported Platforms:
C = Certified
This platform was used for regression testing with this release of AppWorks Gateway. Use of this platform is fully supported by OpenText Customer Support for customers that have purchased product licenses.
S = Supported
This platform received limited testing for this release of OpenText AppWorks Gateway. Use of this platform is fully supported by OpenText Customer Support for customers that have purchased product licenses.
Not Listed = Unsupported
This received no testing by OpenText. There may or may not be known issues with this platform. Its use is not supported by OpenText Customer Support.
The section provides details about which versions of other OpenText products are compatible with this release of AppWorks Gateway 1.2.1.
For the latest compatibility information for OpenText products, refer to the Compatibility Matrix on the OpenText Knowledge Center.
|Content Server||10||Update 13 and above|
|Content Server||10.5||Update 2014-06 and above|
AppWorks Gateway is currently localized in the following languages. Future releases may add additional languages.
|Appworks Gateway Admin UI||B|
|AppWorks Gateway Web Access||B|
UI = user interface only
B = both user interface and online help
This section provides additional installation and upgrade information, including related or third-party product information and any required critical patches.
Before you install AppWorks Gateway, review these additional installation notes and verify related product or third-party product requirements.
The AppWorks Gateway supports upgrading from AppWorks 1.1.5 and higher. Complete upgrade details are available in the installation documentation that is available on the OpenText Developer Site. To summarize, upgrade using the following steps:
<TOMCAT_HOME>/webappsfolder and delete the existing gateway.war file and gateway folder.
appworks_gateway_1.2.1.zipfile into the root of the Apache Tomcat folder. For example,
C:\Program Files\Apache Software Foundation\Tomcat 7.0.
<https://Tomcat_Host:port>/gatewayto view the OpenText AppWorks Gateway.
The following patches must be applied to AppWorks Gateway 1.2.1. OpenText also recommends that you check the OpenText Developer Site for any patches or documentation updates that may have been posted after this release.
Before installing the patch, ensure that you have met the following prerequisites:
You must download the following to install this patch:
Further information on installing, upgrading and administering the AppWorks Gateway is available here:
This section provides information about past issues that have been fixed in this release.
|Issue Name||Issue Description|
|OTAG-1354||Single Sign On to Web access from Windows desktop.|
|OTAG-2201||Web Access Login page is replaced with OTDS login page to allow Single Sign On.|
|OTAG-2300||Update to Add-on Bundle to remove Client and Server Traffic reports.|
|OTAG-1969||URL is not updating for sub domains.|
|OTAG-2114||AppWorks doesn’t rewrite URLS when used with Tempo Social.|
|OTAG-2125||Enhancements to OTDS configuration options screen.|
|OTAG-2180||Option to use ORACLE SID or Service Name for Database connection.|
|OTAG-2153||User can log into Web Access regardless of how user is stored in Content Server.|
|OTAG-2176||AppWorks cookies are not cleaned up correctly on logout.|
|OTAG-2236||Enhancement to notifications database performance.|
|OTAG-2238||OTDS 10.5.0 Patch prevents external user login and receipt of sharing requests.|
|OTAG-2397||Error in rendering user photo within notifications.|
|OTAG-2329||Admin UI should allow for Single Sign On to be disabled.|
|OTAG-2347||Common Header should allow for sign out as well as sign in as a different user.|
|OTAG-2342||App.Properties file allows developers to download an app dependent on device platform.|
|OTAG-2270||Enhancements to notifications cleanup from developed apps.|
|OTAG-1933||Online help in Web UI does not resize correctly.|
|OTAG-2637||Update of OTDS client libraries to latest version.|
|OTAG-2595||Improvements to event-based database queries.|
|OTAG-2624||SMTP SSL Settings do not take effect without restart.|
|OTAG-2640||Sign in button displays incorrectly when anonymous access is enabled.|
|OTAG-2641||Creating and modifying OTDS users fails.|
|OTAG-2676||Increase webaccess notification interval to improve performance.|
|OTAG-2631||Additional configuration option for Oracle SCAN VIP connections in Oracle RAC.|
|OTAG-2370||External users are presented with a Windows Security dialogue when single sign-on is enabled.|
Note on OTAG-2370
- External users will be presented with an authentication dialogue when they access the Web UI using webaccess. This dialogue must be dismissed by the end user to load the correct login page.
- This can be overcome by routing the OTDS URL using the AppWorks Gateway Reverse Proxy Service and by ensuring that the OTDS URL when accessed from the external network has the otds no-sso query parameter added. For example,
- An article will be published to OpenText Developer to provide further details on this configuration.
The following known issues exist in this release.
An Installation of AppWorks Gateway cannot be installed in the same Tomcat as a standalone instance of OTDS 10.5.0 patch 5 and above.
This is an issue that will be resolved in a future release of AppWorks
275 Frank Tompa Drive
Canada, N2L 0A1
Knowledge Center: https://knowledge.opentext.com
OpenText Developer: https://developer.opentext.com/
For more information, visit www.opentext.com
You need to sign in before voting.