EnterWorks Services - Precisely_EnterWorks - EnterWorks - 11.0

EnterWorks Guide

Product type
Software
Portfolio
Verify
Product family
EnterWorks
Product
Precisely EnterWorks
Precisely EnterWorks > EnterWorks
Version
11.0
Language
English
Product name
Precisely EnterWorks
Title
EnterWorks Guide
Copyright
2024
First publish date
2007
Last updated
2025-01-07
Published on
2025-01-07T07:44:20.997352
EnterWorks services:
  • EnableServerTomcat
  • EnableServerWildflyController
  • EnableServerWildflyWorker<n>
  • enable-api-go-service
  • enable-channel-readiness-service
  • enable-dam-manager-service
  • enable-dam-variant-processor-service
  • enable-epx-broker-service
  • enable-monitor-dam-drop-service
  • enable-monitor-service
  • enable-mq-logger-service
  • enable-typeahead-service
  • enable-webcm-broker-service
  • enable-web-server-service
  • EPXJboss
  • EPXTomcat
Third-party services:
  • Erlang
  • RabbitMQ
  • BoltDB

Standard EnterWorks service distributions

There are two standard configuration for EnterWorks environments:

  • Distributed: Used for Production (PROD) and other full implementation environments. EnterWorks services are distributed across multiple servers.
  • Standalone: Used for Development (DEV) environments. Typically DEV environments are small scale implementations of non-DEV environments. EnterWorks services are all hosted on one server.
Important: It is possible to distribute services across the EnterWorks servers in a non-standard configuration. It is highly recommended that you do not deviate from the standard service distribution configurations. Using the standard configurations makes your EnterWorks systems easier to administer and maintain, improves system reliability, and will allow you to more easily upgrade to newer versions of EnterWorks.

DEV environments

Development (DEV) environments are used for system development and unit-testing purposes. DEV environments typically have a single worker because they do not need to handle the full process load Production (PROD) environments do. A DEV environment is used to develop changes to the EnterWorks data model, workflows, and any custom processing. It generally has a relatively small number of concurrent users and lower rates of data processing. In a DEV environment, all EnterWorks application services except for the database server reside on a single VM. Third-party components, such as Rabbit MQ and Bolt DB, are located on the same VM as the EnterWorks services.

Server Name Component Comments
app (or web)

EnableServerTomcat

EnableServerWildflyController

EnableServerWildflyWorker1

EPXTomcat

EPXJBoss

enable-api-go-service

enable-channel-readiness-service

enable-dam-manager-service

enable-dam-variant-workerX-service

enable-epx-broker-service

enable-monitor-dam-drop

enable-monitor-service

enable-mq-logger-service

enable-typeahead-service

enable-web-server-service

enable-webcm-broker-service

Damroot folder (possibly)

RabbitMQ

Damroot folder is on this server, unless it is on a network file path.

db SQL Server EPIM and EPX databases

PROD and Non-PROD environments

The PROD and Non-PROD environments are:

  • Production (PROD) environments are used for a business’ day-to-day operations.
  • Non-PROD refers to non-Production environments (such as QA, TEST, and UAT) that are configured identically to the Production environment but are not used for a business’ day-to-day operations.
PROD and Non-PROD environments are distributed. The EnterWorks application services reside on a specific set of servers, with additional servers configured as workers. The number of additional servers is determined by the number of workers that are needed.

You can configure up to three EnableServerWildflyWorker<x> services on each work-<n> server. The number of work-<n> servers configured are:

  • Small environments have only work-1, for up to three worker services.
  • Medium environments have work-1 and work-2, for up to six worker services.
  • Large environments have work-1, work-2, and work-3, for up to nine worker services.
  • Extra-large environments have work-1, work-2, work-3, and work-4, for up to twelve worker services.
Server Name Component Comments
app (or web)

EnableServerTomcat

EnableServerWildflyController

EPXTomcat

EPXJBoss

enable-api-go-service

enable-channel-readiness-service

enable-epx-broker-service

enable-monitor-dam-drop-service (if files will be submitted to the DAM via EPX workflow)

enable-monitor-service

enable-mq-logger-service

enable-typeahead-service

enable-web-server-service

enable-webcm-broker-service

 
work-1

EnableServerWildflyWorker1

EnableServerWildflyWorker2

EnableServerWildflyWorker3

work-1 is configured for all system sizes:
  • Small
  • Medium
  • Large
  • Extra-large
(optional) work-2

EnableServerWildflyWorker4

EnableServerWildflyWorker5

EnableServerWildflyWorker6

work-2 is configured for system sizes:
  • Medium
  • Large
  • Extra-large
(optional) work-3

EnableServerWildflyWorker7

EnableServerWildflyWorker8

EnableServerWildflyWorker9

work-3 is configured for system sizes:
  • Large
  • Extra-large
(optional) work-4

EnableServerWildflyWorker10

EnableServerWildflyWorker11

EnableServerWildflyWorker12

work-4 is configured for system sizes:
  • Extra-large
dam

enable-dam-manager-service

enable-dam-variant-workerX-service

enable-monitor-dam-drop

Damroot folder (possibly)

Multiple enable-dam-variant-worker-services can be configured for parallel variant generation.

Damroot folder is on this server, unless it is on a network file path.

esb

RabbitMQ

db SQL Server EPIM and EPX databases