Unify and manage your data

Deploy JAR Dynamically for Tenant

You post a request to deploy JAR dynamically for a tenant.

Request

Operation Endpoint:

POST /{tenantId}/jarDeployments
Table 1. Parameters
Parameter Required Description
Headers Authorization Yes Access Token in format Bearer <accessToken> (see details in Authentication API).
EnvironmentURL Yes Reltio Environment URL.
Path tenantId Yes tenantId.
Body module Yes Complete JAR path in S3.
name Yes Name of the hot deployment.
description No Description for the hot deployment.

Example

Sample Request JSON:

{
   "module":"workflow/prod/OnboardingListeners.jar",
   "name":"OnboardingCustomListeners",
   "description":"Listeners to be used for Onboarding process"
}

Response

Response Structure:

  • module- Complete JAR path in S3
  • name- Name of new deployment
  • description- Description for the deployment
  • createdBy- Name of the user
  • createTime- Creation time of the deployment
  • error- returned if an error is encountered, contains details of the issue:
    • errorCode- 5-digit error code
    • errorMessage- error message
    • errorData- details of the error:
      • exception- exception message
      • stack- stack trace
    • innerError - details of the error from Reltio API:
      • errorMessage- Reltio API error message
      • errorCode- Reltio API error code
      • innerErrorData- Reltio API inner error data
  • warning- returned if the operation is completed with some minor issues
  • status- result of the operation; possible values are "OK" or "failed"

Sample Response JSON:

{
   "module":"workflow/prod/OnboardingListeners.jar",
   "name":"OnboardingCustomListeners",
   "description":"Listeners to be used for Onboarding process",
   "createdBy":"user1",
   "createTime":1234567890,
   "status":"OK",
   "warning":"string"
}