| Info |
|---|
The pace report service is required to run performance reports via the ReST API adhocReport endpoint; clients within EagleAccess should instead use the eql ReST endpoint, which does not utilize the pace-reportservice. |
The pace-reportservice is not included in the deployment of AllServices.
The pace-reportservice can be installed with the deploy_demand stream in Message Center Console using the Artifactory delivery method:
...
The report service can also be installed with the deploy_demand stream using the File in a folder delivery method.jar is also available for download from artifactory for manual installation:
Upload the pace-reportservice jar to the data/msgcenter/cmw_staging_folder from
http://inno-artifactory.eagleinvsys.com/artifactory/rd-release-local/com/eagleinvsys/pace-reportservice/The jar needs to be in the estar/tpe/servers/pace-reportservice/ directory
and must have a symbolic link pace-reportservice.jar referring to it.
For example, in /apps/eagle/estar/tpe/servers/pace-reportservice/:
Anchor
pace-reportservice.jar -> /apps/eagle/Deploy with the deploy_demand stream using file method, specifying the relative path to the specific jar:
...
The .jar is also available for download from artifactory for manual installation:
https://artifactory.engops.az.eagleinvsys.com/ui/repos/tree/General/maven-local-dev/com/eagleinvsys/pace-reportservice
The jar needs to be uploaded to the estar/tpe/servers/pace-reportservice/ pace-reportservice-1.0.0.jardirectory.
MC2 needs to be restarted after a manual deployment.
The jar upload and MC2 restart needs to be done on every application host of a multi-server environment.