Step 3: ZMF Connector communicates with ZMF. If the connector cannot reach ZMF, those errors will also be in serenatomcat-stderr.log or serenatomcat-stdout.log (by default located at C:\Program Files\Micro Focus\common\ tomcat \8.0\logs) Step 4: ZMF will run the job
The ZMF connection information is configured in C:\Program Files\Micro Focus\common\tomcat\8.0\webapps\almzmf\WEB-INF\conf\zmf_resource.properties If the connector cannot reach ZMF, those errors will also be in serenatomcat-stderr.log or serenatomcat-stdout.log (by default located at C:\Program Files\Micro Focus\common\ tomcat \8.0\logs) Step 4: ZMF will run the job and communicate back to the ZMF Connector
A customer has been testing their upgrade to 8.2 Patch 3. Suddenly and unexpectedly all attempts to run audit against ZMF packages resulted in the file tailoring (e.g. CMNsADSP) tasks hanging. They had to restart both their ZMF Server and their REST API Tomcat started tasks to resolve the issue.
After implementing ZMF V8.2.03 REST API Revision-1 and recycling the ZMF started task and Tomcat server, the existing subscriber got an HTTP 500 Response Code: ===================================== Event Response Code: 500
Customer is on ZMF 8.2 Patch 3 and has the REST Services Tomcat server up. They noticed in the Tomcat log the SEVERE error message listed below. The customer confirmed the file does exist using ISPF option 3.17.
The same setup was used in the previous release ZMF 8.2 Patch 4 installation and the message was not displayed, so it seems to be specific to the ZMF 8.2 Patch 5 setup. As the ZMFRESTCONTEXT keyword still exists in the shipped ZMFPARMS member
