Is integration knowledge stored in a repository so that it can be reused across the entire integration landscape?
Since it encapsulates all collaboration knowledge, the Enterprise Services Repository serves the purpose of storing integration knowledge. The repository objects can be subdivided into business processes in general – business scenarios and more refined business processes – and into interfaces and mappings. Information on the application components that are used can be assigned to the Enterprise Services Repository from the System Landscape Directory (SLD).