REST API Samples

REST End Points can be triggered using any REST client, such as Postman. The following table describes the END point and sample JSON request data.

The following Headers are common for all End Points: Content-Type? application/json

Table 20-81 REST APIS with Sample Data

URL	JSON Request Body	Purpose
<appurl>/<context>/docdatamign/ datamignservice/migndatamaint Type: POST	{ mignEndTime:23,INFODOM:OFSAAAII NFO,APPID:OFS_CRR,mignStartTime:1,	To add Entry into the Utility Registration Table
Auth:Basic	batchSize:100,THREADSIZE:2	-
Header: gsUsrID	}	-
URL : <appurl>/<context>/ docdatamign/datamignservice/ mignpropdatamaint	{ "INFODOM": "MIGPOP8124", "APPID":"OFS_NGECM",	-
TYPE : POST	"mignPropValue":"CMCS",
AUTH : BASIC	"mignPropKey":"OBJECTTYPE"
HEADER : gsUsrID	}
-	{INFODOM:OFSAAAIINFO,mignProcTur	To TurnOff / Turn ON migration
	nOffOn:N,APPID:OFS_CRR}	processfor a given Application
	{INFODOM:OFSAAAIINFO,mignProcTur	-
	nOffOn:Y,APPID:OFS_CRR	-
-	Toadd / update bearer token { INFODOM: OFSAAAIINFO, APPID:OFS_CRR, mignPropValue: <<BEARER TOKEN>>, mignPropKey:BEARERTOKEN }	ToAdd / Modify Properties

The migration process can be tracked under the AAI_DOC_MIGN_PROCESSOR table in both On- premise (config schema) and Cloud (ws1meta schema).