OpenText AppWorks 16.7 install guide

I should add: for Documentum newbies in OpenText products 🙂

I’ve recently had to test/evaluate OpenText AppWorks as a suitable solution for development purposes.

If you’re not familiar with OpenText portfolio, AppWorks is OpenText equivalent to Documentum’s xCP. A “framework” that allows you to build “process oriented” applications. Also, somewhat like D2, as there’s no coding in AppWorks.

For those of you that are wondering, installing this wasn’t really that easy, and it seems Documentum documentation is not the only “lacking” documentation 🙂

So, let’s start:


Windows 10 x64 8GB RAM
VMware Workstation Player 12

CentOS 7 x64 25GB HD 4GB RAM 2 cores
PostgreSQL 9.6
Documentum 16.4

VM Creation

I’ve used the VM created on the Opentext Documentum 16.4 PostgreSQL Developer Edition, but you can use any VM with PostgreSQL.

PostgreSQL Configuration

Follow the instructions on any of the previous guides (Opentext Documentum 16.4 PostgreSQL Developer EditionOpentext Documentum 16.7 PostgreSQL Developer Edition) to get PostgreSQL running, then create a new database. I’ve used phpPgAdmin to create a user (appworks), tablespace (appworks, remember to create the folder on the filesystem before creating the tablespace) and a database (appworks).

Additionally, you also need to download PostgreSQL’s JDBC driver from this page.

TomEE Configuration

Be aware that this is not Tomcat 🙂 You’ll need to download the TomEE (I’ve used the Plume 8.0.0 version) from TomEE download page. As with Tomcat, just unzip and you’ll have a familiar structure. Also, set this TomEE to run under openJDK (I used openJDK 11, as this is required later by AppWorks).

Additional configuration to do:

  • Modify tomcat-users.xml with the following:

<role rolename=”tomee-admin” />
<role rolename=”manager-gui”/>
<role rolename=”manager-script”/>
<role rolename=”manager-jmx”/>
<role rolename=”manager-status”/>
<role rolename=”admin-gui”/>
<role rolename=”admin-script”/>

<user username=”tomee” password=”tomee” roles=”admin-gui,manager-gui,tomee-admin”/>
<user username=”opentext” password=”opentext” roles=”admin-gui,admin-script,manager-gui,manager-script,manager-jms,manager-status,tomee-admin”/>
<user username=”rpc” password=”rpc” roles=”admin-script,manager-script,manager-jmx”/>


  • Rename /lib/openejb-core-eclipselink-8.0.0.jar to /lib/openejb-core-eclipselink-8.0.0.bak
  • Copy postgresql JDBC driver to \lib folder (although I’m quite sure this is not really needed)
  • Configure a service on the server for Tomee and name it “tomee”

CARS Configuration

  • Run the installer:

sudo JAVA_HOME=/opt/opentext/jdk-11 CLASSPATH=/opt/opentext/postgresql-42.2.9.jar PATH=/opt/opentext/jdk-11/bin:$PATH ./OpenText_CARS_2.6.bin

2020-01-08 20_01_33-01

2020-01-08 20_01_51-02

2020-01-08 20_02_01-03

2020-01-08 20_02_14-04

2020-01-08 20_02_39-06

2020-01-08 20_02_58-07

2020-01-08 20_03_12-08

2020-01-08 20_03_41-09

AppWorks Configuration

You’ll need a license to install AppWorks. This trial license can be requested from the support site.

  • Run the installer:

sudo JAVA_HOME=/opt/opentext/jdk-11 CLASSPATH=/opt/opentext/postgresql-42.2.9.jar PATH=/opt/opentext/jdk-11/bin:$PATH ./OpenText_AppWorks_Platform_16.7.bin

2020-01-08 20_06_59-01_1

2020-01-08 20_07_26-02_1

2020-01-08 20_07_40-03_1

2020-01-08 20_07_54-04_1

2020-01-08 20_08_04-05_1

2020-01-08 20_08_19-06_1

2020-01-08 20_08_30-07_1

2020-01-08 20_08_41-08_1

2020-01-08 20_08_59-09_1

2020-01-08 20_09_45-10_1

2020-01-08 20_10_10-11_1

2020-01-08 20_10_26-12_1

2020-01-08 20_11_00-13_1

2020-01-08 20_11_10-14_1

2020-01-08 20_12_03-15_1

2020-01-08 20_12_23-16_1

2020-01-08 20_12_40-17_1

2020-01-08 20_13_52-18_1

Last, but not least, some sources of information related to AppWorks:

Opentext Documentum is coming next month

I didn’t realize that roadmap documents were updated last month. It looks like the February release is still going to happen (and I’ve been told a definite date, so it looks it won’t be delayed). After reviewing them (haven’t seen any changes :D), I can say:

  • Not much features regarding CS, the pattern/usage visualization and the s3 support (which, as far as I know, can be already done without official support) are the new features.
  • No word about DFS, and I know for a fact that several customers have actively asked for updates to current libs and extended support for application servers.
  • Clients get barely any changes (D2, Webtop, xCP).

I’m curious to see how many bugs are found in this first release from Opentext (and the brave customers that go first into the unknown :D), considering that some of the experienced Documentum staff left the company and the changes to the development cycle (that I guess happen when you move from a hardware company to a software company)

Updated roadmap, webinar and FAQ from OpenText Documentum

If you registered for the webinar OpenText held a few weeks ago (if you didn’t, maybe you can check Andrey’s post on the subject), you should have received an invitation to some site from OT with a FAQ about the Documentum stack. I’m not going to paste it here, just in case it’s not public, but IMHO, the highlights are:

  • Content Server: Aligment with ECD. No new features but trying to move to a microservices architechture. It probably means CS won’t evolve anymore.
  • Webtop: Several points on this. Will keep being supported and updated to support latest CS.
  • Rest: Every new product based on this. No mention about DFS (I hope it’s dead, unless they decide to update with libraries from this decade)
  • xCP: It looks like xCP 1.x support will be over by the end of 2019.
  • Support: Still through EMC’s site until the end of the year.

D2 (and Webtop and xCP) CTF

CTF (Content Transfer Framework) is how EMC Dell calls their “new UCF”. It works as a browser extension, and is the same extension you’ve used for the latest version of Webtop (new functionality getting first to Webtop? LOL). And this mode is not the default (why?) so you’ll need to change it in the file of D2.

Also, this extension will generate some “index” files on the folder where you download files:

  • .checkout.xml
  • .d2_edit_storage.json
  • .d2_view_storage.json
  • .view.xml

That contain object names, ids, operation performed, and folder paths of the files transferred.

Tested on latest Firefox Nightly x64 and Chrome.

FYI, I’m pasting the “wonderful” ASCII compatibility matrix provided by Dell in the configuration file:

#     +——————-+——+——+——+——+
#     | Browser:OS \ Mode | Thin | Java | ctf  | Note |
#     +——————-+——+——+——+——+
#     | IE 11             | yes  | yes  | yes  |      |
#     +——————-+——+——+——+——+
#     | Edge              | yes  | NO   | NO   | (1)  |
#     +——————-+——+——+——+——+
#     | Firefox           | yes  | yes  | yes  |      |
#     +——————-+——+——+——+——+
#     | Chrome            | yes  | NO   | yes  | (1)  |
#     +——————-+——+——+——+——+
#     | Safari:Mac_OSX    | yes  | yes  | yes  |      |
#     +——————-+——+——+——+——+
#     | Safari:Mac_IOS    | yes  | NO   | NO   | (2)  |
#     +——————-+——+——+——+——+
# Notes:
# (1) Chrome and Edge do not support java applets, and Edge does not support the CTF plugin.
#     D2 will fallback to thin client mode appropriately when java or ctf has been
#     specified in the value of the browser.plugin.mode setting as described above.
# (2) If browser.plugin.mode contains java or ctf, then D2 will silently continue to run in
#     thin client mode. Safari running on Mac_IOS does not support the java or ctf plugin.

  • Prompt for installing the extension:


  • View content prompt:


  • Edit:


  • Check in:


What I expect for Documentum from ECD/OpenText

What I think OpenText should keep:

  • Support Community
  • ContentHub
  • EMC Support (at least the search engine with the knowledge base)
  • Download Center (After so many changes, I really don’t want to change again :P)
  • EMC GitHub
  • Webtop (It’s the only client that works OOTB)

What I think OpenText should change:

  • Sales policy (Stop pushing products that customers don’t need, and yes, that means D2 and xCP for customers that simply want a “library”)
  • Sort libraries/dependencies in the Documentum stack (if 7.x is released, make it that every product has the same version of every library). Rebrand products accordingly (yeah, Webtop 7.x if it is using DFC 7.x)
  • Detailed changelog of the products (don’t force us to go through every single customization to check if some component we’re extending has changed and broke the customizations)
  • Kill lockbox with fire (or at least, make it optional for both CS and D2). Nobody understands it, nobody knows how to set it up, so it is more a pain in the ass than a security feature
  • Oh, and remove D2 dependency on JMS

I’ve lost any hope to see dmbasic gone for good, or JBOSS replaced with something “lighter”, that’s why those didn’t make it into the list (as probably many others, that I don’t remember now)

(And yes, I’m not a huge fan of D2 :P)

What happens when you don’t configure OOTB Jobs (DCTM/xCP)

Environment: DCTM 7.2 + PE 2.2, 2 months running an empty test repository:

  • …/dba/logs/…/agentexec: +150k files
  • …/dba/logs/…/dmadmin: +150k files
  • /Temp/Jobs/…/: +60k objects in several folders (dm_document objects)
  • /System/Sysadmin/Reports/…: +60k versions of some objects (dm_document objects)
  • dm_audittrail: +1.5 million objects
  • Database File Size: ~ 5GB

Be specially careful with the methods that by default run every minute:

  • bpm_XCPAutoTaskMgmt
  • Iniatilizae_WQ

And those that run every hour:

  • QmPriorityAging
  • QmThresholdNotification
  • WfmsTimer
  • WFSuspendTimer

If you’re not using those features you should really disable them. Or run logpurge+audittrail+dmclean as often as possible.

xCP and D2 developer edition announced in EMC World

EMC has announced the future availabily of two new developer edition VMs and hopefully someone will read this wishlist

  • xCP developer edition (June 30th)
    • Confirmed: A working CTS in Linux (wondering how/if office files transformation works).
    • CIS 7.1
    • Now that you guys have installed everything in Linux, take those installation/configuration scripts that you had to modify because were made in windows and bundle them with the linux installers, so we don’t have to run dos2unix for every script file.
    • “Modular” xCP / remove the need to install every component (at least in development environments). (I don’t expect to see this “working” in this developer edition, but hopefully they’ll consider it for the next xCP release…)
  • D2 developer edition (May 30th)
    • I have doubts about this, is this also an open-source VM? If D2-Config is still an activeX you’ll need a windows machine to configure D2.

And hopefully, we’ll see a production-supported PostgreSQL content in a future version (7.1 SP1? Bedrock?) or at least an official statement about this…