Keep an API connection's setup in a single configuration file
Also listed as: Single API configuration file
What is it?
Xelence keeps the setup for each API connection in a single configuration file, so its endpoints, settings and mappings are defined in one place.
Why does it matter?
Integrations are easier to review, move between environments and change.
Start thinking about
- Which integrations matter most to your operations, and which would you modernize first?
- Do you keep a current inventory of your interfaces and file exchanges, and who owns each one?
- What does your security policy require for credentials, encryption and access between systems?
- Who approves a new or changed connection to a partner system?
- Which manual hand-offs between systems would you most like to automate?
- How will you coordinate integration testing with partners when you take a new Xelence release?
Terms used on this card
- API
- A defined way for two software systems to exchange data or request actions from each other.
- Environment
- A separate copy of your solution used for one stage of work, such as development, testing or production. Production is the live system that staff and constituents use.