The OnBase ArchiveLink Server exists to provide a connection between an existing SAP system and an OnBase content management system. Through a set of OnBase components, it allows OnBase users to interact with their SAP system, providing a tight integration between the OnBase solution and SAP. This integration allows enterprises using SAP the ability to use OnBase as a Content Management System in conjunction with their SAP system.
The OnBase Connector for use with SAP ArchiveLink solution has three major points of integration:
HTTP ArchiveLink Content Server
OLE/HTTP front end functionality via the Unity Client for use with SAP ArchiveLink, DocPop, or UnityPop (OLE viewer)
Bar Code BAPI (BAPI RFC)
Each piece of the solution requires the deployment of either the OnBase Client, Unity Client for use with SAP ArchiveLink, or the Core Services platform. Scanning stations operators can utilize the OnBase Client to perform indexing and bar code processing. These scan queues are then linked to SAP via the BAPI scan queue configuration in the configuration module, allowing users to link OnBase documents to SAP business objects from the OnBase scanning station.
Users can also view documents directly from SAP by using the Unity Client for use with SAP ArchiveLink, DocPop, or UnityPop as an OLE viewer. The Unity Client for use with SAP ArchiveLink can also be used to link OnBase documents to SAP, as well as bring new documents into both SAP and OnBase using its various archive functions.
The OnBase ArchiveLink Content Server is an N-tier web application that provides HTTP based linking between OnBase documents and SAP. This server acts as the primary connection between OnBase and SAP, providing linking services. The OnBase ArchiveLink Content Server requires an underlying Microsoft Internet Information Server 7.0 running on Microsoft Windows 2008. All communications with the exception of BAPI RFC are performed using standard Internet network protocols that are compatible with HTTPS bindings and VPN secure connections. Communications between the OnBase ArchiveLink Server and SAP for bar-coding purposes utilize RFC and should have their servers placed appropriately as a result. Any firewall or other network-limiting factor could have an impact upon these communications.