The ActiveControl integration framework can be used to perform outbound integration on potentially any external system. Two tables need to be maintained here, table ‘/BTI/TE_INT_SYST’ is the table that holds all the external system id’s and descriptions along with any RFC Destinations that may possibly be needed for example for a Solution Manager system, also table ‘/BTI/TE_INT_CLAS’ needs to be maintained and this holds the class that the framework references.
| /BTI/TE_INT_SYST – AC Integration System List | |
|---|---|
| Field | Description |
| EXTSYS_NO | Main external system identifier, this is the identifier of the system that you wish to integrate with we can have as many systems as we want. An example of this could be: 1 – Remedy 2 – Solution Manager 3 – ServiceNow 4 – HP-ALM 5 - GitLab |
| EXTSYS_ID | Single word identifier for external system. E.g. REMEDY |
| EXTSYS_NAME | Full description of external system |
| RFC_DEST | Some external systems that you want systems with could possibly be SAP systems for example Solution Manager so the RFC destination is held here. |
| DDC Identifier | |
| Task Field Link (Text ID) | Business Task field ID of label wanting to be defaulted. |
| Form Field Link (Text ID) | Transport Form field ID of label wanting to be defaulted. |
| Integration User | System user name of target system for access, outbound, if connecting through SAP RFC Destination HTTP to External Server. |
| Integration Password | System user password of target system for access. |
| Integration Port (Int_Port) | If connection between applications requires a Proxy, define the proxy port here. |
| Version | Always use the value = 2 |
Example Configuration
Example configuration for table /BTI/TE_INT_SYST in the Domain Controller for a ActiveContro <> ServiceNow integration.
Post your comment on this topic.