-
Notifications
You must be signed in to change notification settings - Fork 77
Port reference
rjrudin edited this page Apr 25, 2019
·
4 revisions
A common question with ml-gradle is - what ports does it use? The answer depends slightly on the kind of application you're deploying, and note that if you're deploying a Data Hub Framework or Service application, the answer is quite different because DHF/S apps add several other ports.
The table below shows the common ports used by ml-gradle. Note that the Property Reference defines all of the connection properties for the various ports, so use this as a high level summary and quick reference.
Port | Property | Description |
---|---|---|
8000 | mlAppServicesPort | This is the default port for the App-Services server that ml-gradle uses for loading non-REST modules and schemas via a /v1/documents endpoint. This defaults to the App-Services port so that applications without a REST server don't need a REST server just for loading modules and schemas. If your application has a REST server, you can change mlAppServicesPort to match the port of your REST server so that you don't have any dependency on App-Services. |
8001 | mlAdminPort | This is the default port for the Admin server that ml-gradle uses for a handful of Manage API endpoints that are executed against the Admin server. |
8002 | mlManagePort | This is the default port for the Manage server that ml-gradle uses for deploying all ML resources - i.e. databases, app servers, users, etc. |
Custom | mlRestPort | For loading REST modules - i.e. options, services, transforms - ml-gradle uses the value of mlRestPort, which is expected to define an application-specific REST server. |
Custom | mlTestRestPort | If you define mlRestPort, you can optionally define mlTestRestPort as well so that a separate REST server and database are created that mirror your main REST server and content database. These resources can then be used for e.g. running automated tests without affecting the data in your main content database. |