There are multiple real live application scenarios that can be supported by the ACC to enhance a given SAP archiving landscape or to facilitate specific transitory functions during a migration process.
Typical application scenarios:
Serving as a proxy during an archive migration by sending r/w calls to the target repository and sending read-only calls the source repository, while actively migrating in the background. This allows switching to the target repository on day one and guaranties a fully user transparent transition.
Supporting partial archive copies during company mergers and splits by functioning as a security gateway, restricting call for copies to selected documents and selected repositories only.
Forwarding (spoofing), securing (HTTPS) and/or signing (SAP SecKey) calls to a new target repository without changing the configuration or coding of the triggering application.
Supporting split storage setups, with a section of the archive in a cloud base reduced access location and another section in a high availability on premise location.
The Archive Content Connector (ACC) is an HTTP Servlet that connects one SAP system to several SAP ArchiveLink content repositories. In a round robin schema, it attempts to handle a call by forwarding to real repositories, possibly manufactured by different vendors, in sequence. The first successful response is passed back to the caller (usually an SAP system).
Additional features include:
Restricting access to listed repositories only
Restricting/allowing read/write/delete access to repositories
Restricting access to only certain document ids (whitelisting)
Obscuring document content while verifying the existence of a document (placeholder display)
Forwarding calls to a specific archive system through URL rewrite (IP address, service name, port number)
Adding HTTPS security to the transmission
Adding/replacing SAP SecKey identification, including link expiration to unsecured calls with custom security certificate
7 months into a 12 months divestiture project, it became clear to the divesture management team, that archived PDF documents, attached to SAP, had to be included in the scope of the SAP system split efforts. SolutionXchg was contacted by KGS and implementation Partner enowa and tasks to jump onto the running project train steaming at full speed towards a November 1st delivery date, with steep penalties attached to any delays. SolutionXchg developed a phased approach based on a primary migration and several delta migrations, closely following the SAP split cycles 2, 3, and 4. Always on standby and working through nights and on weekends, the SolXchg team managed to deliver the data in time, on budget, and with great accuracy.
“Thank you Jochen, and if I do not speak with you again, now that the project comes to an end, I wanted to say, you have been a wonderful partner to work with! You matched with the team very well! I hope our partner enowa can get you into additional opportunities. Thanks again for all your great work!”
7 months into a 12 months divestiture project, it became clear to the divesture management team, that archived PDF documents, attached to SAP, had to be included in the scope of the SAP system split efforts. SolutionXchg was contacted by KGS and implementation Partner enowa and tasks to jump onto the running project train steaming at full speed towards a November 1st delivery date, with steep penalties attached to any delays. SolutionXchg developed a phased approach based on a primary migration and several delta migrations, closely following the SAP split cycles 2, 3, and 4. Always on standby and working through nights and on weekends, the SolXchg team managed to deliver the data in time, on budget, and with great accuracy.
“I was chatting with [our mother company’s] IT Global head today and I expressed how impressed I was with the cost of the KGS solutions and your ability to implement it flawlessly. He asked that I share your contact information.”
Michael B., Executive Adviser – Management Consultant
