Systems Components

Environments

An EnterWorks system typically consists of three separate environments: DEV, QA, and PROD. The data model is developed in the DEV environment, tested in the QA environment, and put into production in the PROD environment.

Services

Controller and Worker Services

Some user tasks such as Importing, Exporting, Validation, and Mass updates are submitted as background jobs. These background jobs are distributed to an available free Worker service to execute. The Controller service monitors for new jobs. When it receives one, it determines if it can be run simultaneously with other jobs or if it must be run sequentially, then sends the job to the next free Worker service. If the job is run on a separate server, log files associated with the job will be located with that server. In general, the greater the number of Workers configured, the greater the number of jobs that can run concurrently. However, some jobs will be serialized due to resource constraints. For example, import jobs to the same target repository will be processed serially, regardless of the number of configured workers.

EnterWorks Services

For a list of configuration options for each service, open a command prompt and run:

<drive>:\Enterworks\enable2020\services\bin\<service> -h

Depending on the version of EnterWorks your system is running, the microservices names will be in one of the following forms:

  • enable-<name>-service

  • enable2020-<name>-service

EnterWorks 10.3 Services

EnableServerTomcat
EnableServerWildflyController
EnableServerWildflyWorker<n>
enable-api-go-service
enable-channel-readiness-service
enable-dam-manager-service
enable-epx-broker-service
enable-es-indexer-service
enable-es-manager-service
enable-esms-service
enable-es-search-service
enable-monitor-dam-drop-service
enable-mq-logger-service
enable-webcm-broker-service
enable-web-server-service
EPXJboss
EPXTomcat