Restart EnterWorks Services - Precisely_EnterWorks - Sales_and_Services_Portal - EnterWorks - Match_and_Merge - 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.997000

The Process of Restarting EnterWorks Services

The scripts for starting and stopping EnterWorks services on Windows servers are:

  • Start Enterworks.cmd

  • Stop Enterworks.cmd

They are installed on each server that contains EnterWorks services and EPX. These scripts will call the appropriate component Stop and Start scripts to stop and start the services running on that server. This may include one or more of the following commands:

  • EPIM Stop.cmd and EPIM Start.cmd: Stop and start the EnterWorks Server services.

  • EPX Stop.cmd and EPX Start.cmd: Stop and start the EPX services.

  • enable2020-stop.cmd and enable2020-start.cmd: Stop and start the microservices.

The component scripts will only stop and start the corresponding services that have been configured on the server. Some components may be installed on more than one server. For example, the EPIM Stop.cmd and EPIM Start.cmd scripts on one server might stop and start the EnterWorks Tomcat and JBoss Controller processes, while the same scripts on another server might stop and start the JBoss Worker processes.

The Start Enterworks.cmd and Stop Enterworks.cmd command scripts on each server are located in:


        <drive>:\Enterworks\bin

When you run any start or stop scripts, run them as Administrator.

It is important to stop and start services in the correct order, depending on your system's configuration.

Important: Unless directed to do so, do not restart third-party applications such as RabbitMQ. If you do need to restart them, all EnterWorks components on all servers must also be restarted. The third-party applications must be running if any EnterWorks services are running, so the third-party applications are the last to be stopped and the first to start.

Every time the EnterWorks services are started using the <component-name> Start.cmd scripts, system log files are moved to an archive folder whose name is comprised of the current year, date, and time. The archive folders are stored in: 


        <drive>:\Enterworks\logs\archive

For example: 


        <drive>:\Enterworks\logs\archive\2019-03-14@15-23-43-84

might hold the following folders:

  • DAMReportUtility

  • EnableServer

  • EPX

  • MonitorDAMDrop

  • RegenerateDAMVariant

which would contain log files for those components of EnterWorks.

Periodically, older archive directories should be removed to prevent the archives from becoming large enough to impact EnterWorks system's efficiency.

To stop all EnterWorks Services

Important: EPX must be stopped first and started last, otherwise EPX will continue attempting to interact with Tomcat and repeatedly fail, which causes invalid workflow processing.

Some servers need their services stopped before other servers. The order in which servers should be stopped depends on which services are located on them. EPX must always be stopped first and started last, otherwise EPX will continue attempting to interact with Tomcat and repeatedly fail, which causes invalid workflow processing.

The table below indicates the server sequence for stopping services. For a list of which services reside on which servers, see EnterWorks Services.

Stop servers in this order Server name
1 app
2 dam
3 work-<n>
Do not stop the esb server. esb

To stop all EnterWorks services on all servers in an environment, perform these steps on each server in the order given in the table above:

  1. Open File Explorer and go to: 
    <drive>:\Enterworks\bin
  2. Right-click Stop Enterworks and select Run as Administrator.
  3. A command prompt will appear and services will begin stopping.
  4. Once the script is finished, verify that no EnterWorks related services are still running.
    1. Open Task Manager and select the Processes tab.
    2. Right-click either CPU or Memory on the header to bring up the list of available columns.
    3. Select Command line.
    4. Expand the width of the Command line column until you can see the path and name of any running processes.
    5. Verify that the following processes do not appear in the list:

      • Commons Daemon Service Runner: Any that have EnableServer in the file path.

      • enable-<serviceName>-service

      • Java(TM) Platform SE Binary: Any that have Enterworks or EPX in the file path.

    6. If any of the listed processes appears, right-click the process and select End Task.

EnterWorks services are now stopped.

To start all EnterWorks Services

Some servers need their services started before other servers. The order in which servers should be started depends on which services are located on them. For a list of which services reside on which servers, see EnterWorks Services.

The table below indicates the server sequence for starting services.

Start servers in this order Server name
Do not restart the esb server. esb
1 work-<n>
2 app
3 dam

To start all EnterWorks services on all servers in an environment, repeat the following steps on each server, following the server sequence given above:

  1. Open File Explorer and go to: 
    <drive>:\Enterworks\bin
  2. Right-click Start Enterworks and select Run as Administrator.
  3. A command prompt will appear indicating that the services are starting. This prompt will close once all services have been started.
  4. Verify that the services have been started by opening the Services control panel and confirming that all Enable* and enable* services (that have not been disabled) have a status of Running.

The EnterWorks services have been started.