Configuration Overview

this document assumes as a precursor that gimmal link enterprise sap and middleware has been installed, base configuration has been completed, and that you have connectivity between gimmal link enterprise sap< >gimmal link enterprise connector< >cms system as well as the base repository id, cms profiles, tags, destinations and repository id’s ready to roll please ensure all steps in the installation and base configuration guide have been completed sap security is assumed to already by in place for the gimmal link enterprise transactions and that future sap authorization for adding and viewing documents (ex s wfar obj) has been considered please refer to the gimmal link enterprise installation and base configuration guide (separate) for further information on the above for gimmal link enterprise sap abap plug in or direct web services development please refer to the developer guide (separate) for technical overview please refer to the technical overview guide for that particular repository (separate) the below outlines an overview of the various configuration components of gimmal link enterprise covered in this guide saplink provides automated inbound processing from your cms system to sap for a wide variety of integration automated link creation, triggering of workflows, execute custom abap code, and more docmanager controls outbound document storage (via message output as well as service for object) as well as inbound (saplink) options such as linking and custom code triggering, as well as metadata transfer in both directions custom api usage typically for use when only the base gimmal link api product is installed choicelists send sap metadata in the form or flat and hierarchal list for use as drop down and choice menus in your cms system workflow connect code free triggering of sap workflow including container fulfillment wfconnect leverages docmanager for saplink inbound processing auditlink utility to extract documents from your cms system and generate html report with drill down to the extracted images for a disconnected from your sap and cms system access to an audit “bundle” docmigrator migrate content (and metadata) from various sources to a gimmal link ecm endpoint, creating new links, deletion of old ones, as well as various utilities to go with accounts payable a powerful yet flexible sap based invoice processing and approval workflow built on the sap workflow runtime system publisher routines to allow for message output (smartforms, adobeforms, etc ) to be stored with metadata in your cms system linkmanger provides and approval process for end users to delete links, with link managers controlling the final deletion as well as the content as an option viewing and attachment list options configure whether gimmal link docmanager is leveraged to store and view content including advanced viewing options, sap db attachment and note option, and more system messages prevent or warn users and api usage when needed during downtime or critical changes across the gimmal link enterprise platform utilities cms load load various cms system components into sap (properties, docclasses, etc ) link maintenance maintain archivelink links metadata push manually or scheduled metadata updates from sap to your cms system based on configured docmanager rules cleaning gateway errors maintenance of error in the gimmal link enterprise api gateway archiving gateway data maintenance and archiving of gimmal link aenterprise pi gateway log tables that may grow in size over time attachment list dashboard report on archivelink links with an enhanced selection criteria across all link tables working with the api gateway and scrud test harness all gimmal link enterprise processing is logged and reportable, including the testing of basic scrud api's with no coding all configuration and utilities can be accessed via transaction /dflow/sys