Operational Verification Procedures

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

Verify Enable Server is Operational

  • Confirm that EnterWorks Tomcat is operational by logging into the EnterWorks UI using the URL:

    http://<tomcatServerName>:8090/webcm/

    where

    <tomcatServerName>

    is the name of the server hosting the EnableServerTomcat service.

    If possible, this should be performed on a browser running on the same server to avoid possible firewall issues.

  • Confirm that the EnterWorks Classic UI is accessible via http://<WebServerName>/webcm/ by logging in as the default system user. This confirms installation of Application Request Routing.

  • Confirm that the Enterworks 2020 UI is accessible via http://<WebServerName>/enable2020 by logging in as the default system user.

  • Confirm that EnableJBossController is operational via the web server’s Services console.

  • Confirm all EnableJBossWorker<n> services are installed and operational via the server’s Services console.

Verify EPX is Operational

Successfully log onto the EPX design console. This confirms installation of EPX.

Verify DAM is Operational

To confirm the DAM application is functional:

  1. Upload an asset and make sure it is processed and shows up in DamMaster.

  2. Link the image to a record and verify that the thumbnail appears.

Verify Third-party Tools are Operational

  • Ensure you can connect to MongoDB with Robo3T.

  • Enable RabbitMQ management console. Create a username and password.

  • Ensure Elasticsearch is available/active from your browser or Postman with: 

    • GET http://{servername}:9200

    The response should be a message such as:

    {
"name" : "vPDW8Ym",
"cluster_name" : "elasticsearch",
"cluster_uuid" : "KB6d9BH6Rhe-wimhmpVOuw",
"version" : {
    "number" : "5.0.0",
    "build_hash" : "253032b",
    "build_date" : "2016-10-26T04:37:51.531Z",
    "build_snapshot" : false,
    "lucene_version" : "6.2.0"
  },
  "tagline" : "You Know, for Search"
}