Configure DAM to Use Azure Blob

Controller/Worker vs Master/Slave: EnterWorks software prior to version 10.1.x used the terms "master" and "slave" rather than "controller" and "worker" in process and folder names. Folders and processes in newer versions of EnterWorks use the terms "controller" and "worker". If you are installing or patching an older version of EnterWorks, you may need to adapt the filepaths and process names accordingly. For instance, if this documentation refers to:

<drive>:\Enterworks\EnableServer\jbossController\standalone\configuration\conf\sharedConfig.properties

you may need to use the filepath:

<drive>:\Enterworks\EnableServer\jbossMaster\standalone\configuration\conf\sharedConfig.properties

Wildfly vs Jboss: Additionally, Red Hat has changed the name of their JBoss platform to Wildfly. Depending on the version of EnterWorks you are running, the names of some folders and processes may appear as either JBoss or Wildfly. If you are installing or patching an older version of EnterWorks, you may need to adapt the filepaths and process names accordingly. For instance, if this documentation refers to:

<drive>:\Enterworks\EnableServer\WildflyController\standalone\configuration\conf\sharedConfig.properties

you may need to use the filepath:

<drive>:\Enterworks\EnableServer\jbossMaster\standalone\configuration\conf\sharedConfig.properties

Microservice names: The names of the microservices have also been updated. The prefix of "enable2020-" has been changed to "enable-". For instance:

enable2020-channel-readiness-service

is now called:

enable-channel-readiness-service