Operational Verification Procedures - Precisely_EnterWorks - EnterWorks

Operational Verification Procedures - 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

2024

First publish date

2007

Last updated

2025-01-07

Published on

2025-01-07T07:44:20.997352

Log into the Classic UI and check the system statuses reported in the System Health widget. You may need to add the widget to the Home Page. No warnings or errors should appear in any of the status indicators.
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 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 New 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.

Log onto the EPX design console. This confirms the installation of EPX.
Run a Scheduled Export. This can verify exports and also Workflow and EPX at the same time. If you do not have an existing Scheduled Export to run, configure one. If you are testing Scheduled Exports as part of a fresh install, you can configure a Scheduled Export of type Repository on the DamConfig repository because it is the only repository that will have data.