Agnostic Guides
...
Developers Guide
Ping and Load API's

CMS_API_PING

1min

Functionality

Description

FileNet Notes

Documentum Notes

Box Notes

M365/SharePoint Notes

IV_CMSPROFILE 



Required: Determines which configured CMS Profile in Link Enterprise SAP to utilize. Combination of CMS Profile and CMS Tag determine the API destination and thus load across an RFC destination. 









IV_CMSTAG 

Required: Determine which configured CMS Profile in Link Enterprise SAP to utilize. Combination of CMS Profile and CMS Tag determine the API destination and thus load across an RFC destination. 









IV_PING_MIDDLEWARE 

Checks that status of the connection to the connector only. 









IV_PING_CMS 

Checks the status of the connection right through to the CMS system (requires IV_TYPE) 









IV_REPOSITORY 

Required: Determines which configured repository in Link Enterprise SAP to utilize 



Object Store 

Docbase 

Default is the only Store/Repository supported since Box currently doesn’t support the notion of different repositories. 

Site, site collection 

IV_TYPE 



What CMS type to PING (mandatory for CMS ping) 

DOCUMENT CLASS 

OBJECT TYPE 

METADATA TEMPLATE 

CONTENT TYPE 

IV_USE_MAPPING 



Optional: use mapping of IV_TYPE to CMS type in Enterprise Connector if CMS. Used if ArchiveLink doctype name to CMS type mapping is required. 









ET_RETURN 

Table that indicates a success of an error. The TYPE field will contain an ‘S’ or ‘E’ respectively and the MESSAGE field will contain information in the case of an error. 









CT_CUSTOM 

Future use