Page Comparison

...

<?xml version="1.0" encoding="UTF-8"?>
<system version="1.1">
  <servers baseport="20000" server_type="1" starversion="**Eagle Version 13.1**">
...
    <server ignorewsdb="1" name="extractservice" offset="220" type="extractservice"/>

The MC2 base port will be 20000 + 220 = 20220.

All other endpoints have an offset, which added to the base port will result in that specific endpoint port number.For example, REST endpoint has an offset of 207. The REST endpoint port number will be the base port (20220) + 207 = 20427

1. MC2 will initiate a TpeSend listener to process requests from the EagleMLWebService30 endpoint on the MC2 base port (i.e. 20220 in the example above).
2. A REST API to the Eagle MC2 Extract Service at base port + 207 (i.e. 20427 in the example above).
3. A REST API for health checks and information about the running instance of MC2 at port + 202 (i.e. 20422 in the example above). The information may be accessed at:

•        http://mc2host:20422/actuator

This request will retun a JSON document with the links to all other available management/monitoring links.

•        http://mc2host:20422/health

This will return a simple health status check.

1. A REST endpoint to reinitialize the rule cache at base port + 206 (i.e. 20426 in the example above). The URL will be:

     http://mc2host:20426/services/eagle/v2/commands/reinitrulecache

               The above request will reinitialize the rule cache for all of the MC2 service instances.

1. A SOAP endpoint to execute requests, exposed directly without the TpeSend/IIS at base port + 201 (i.e. 20421 in the example above). The URL to invoke the SOAP endpoint is:

http://mc2host:20421/services/eagle/v2/EagleMLWebService20

NOTE: The URL for the direct SOAP endpoint will be changed to EagleMLWebService30 in future releases.