Livelink Enterprise Archive vs. SAP Content Server - DETAILED.ppt

Presentation ObjectivesThis presentation willprovide you with information about the strategic importance of an enterprise-wide document repositorygive you an overview about the Open Text product and solution offering for SAPgive you a better understanding of the SAP Content Serverinform you about the differences between SAP Content Server and Livelink ECM - Enterprise Archive

AgendaWhy ECM for SAP?Livelink ECM Suite for SAP SolutionsLivelink ECM Enterprise ArchiveSAP Content Server Summary

Content Integration in SAPNo process efficiency (Call Center response times, etc.)Processing takes to long and decisions are based on incomplete informationBusiness continuity at riskCost of (non-) complianceHigh administrative costs due to (manual) process of combining content coming from various sources

Content Integration Complexity Increases

Implications of missing ECM CapabilityProcess inefficiencyHigh administrative costs due to the need to manually integrate various information sourcesDecisions based on incomplete informationCosts and risks of (non-) compliance

Getting Value out of Combining ECM with SAP solutionsLivelinkPDMContractsProject Docs.PLMSpecificationsDrawingsDocumentationGroupwareEmails

Getting Value out of Combining ECM with SAP solutionsLivelinkPDMContractsProject Docs.Other Solutions:WCM, KM, RM, DAM, etc.

Livelink ECM Suite for SAP SolutionsSD DocFlow in MSFT Outlook9

The Power of Content IntegrationContextDocumentBusiness InfoContractInvoiceDunningDelivery note80% Unstructured20% Structured Contact data Pricing & conditions Billing information +=ContentValue

AgendaWhy ECM for SAP?Livelink ECM Suite for SAP SolutionsComponent OverviewBusiness ScenariosLivelink ECM Enterprise ArchiveSAP Content Server Summary

Livelink ECM - Suite for SAP Solutions ArchitectureSAP ArchiveLinkLivelink ViewersLivelink ECM for SAP SolutionsSAP KM RMLivelinkDocuLinkfor SAP SolutionsFISDPLM...Livelink DC for ESFormsManagmentDesktopLinkCOLDLivelink Enterprise Archive ServerRendition ServerHigh SecurityHigh AvailabilityDesktop ScanEnterpriseScanExchnageLinkNotesLinkIXtractor

Livelink ECM - Suite for SAP Solutions ArchitectureDocuLink Provides a process centric view on documents SAP and non-SAP documents. SAP documentsFormsManagement Form overlay for compliant management of outgoing documentsDesktopLink / ExchangeLink / NotesLink Integration of desktop documents and emails into SAP. Complete documentation of business process in SAPcan origin different SAP transactions, modules or even systemsCOLD Mass document import interface in SAP / LEA for e.g. external scan providers or legacy decommissioningIXtractor Offline access to SAP documentsEnterpriseScan High volume document scan client for mass-document scanning at e.g. a central scan station ( mail room )

Livelink ECM - Suite for SAP Solutions ArchitectureDesktopScan Ad-hoc scanning of single documents like e.g. confidential document in a HR departmentSAP Knowledge Management Repository Manager Integrates SAP ArchiveLink documents in SAP KMDocument Viewer Windows or java applet (no client installation required) viewer for business documentsRendition Server Enables a compliant storage of documents in a long-term document format like PDF or TIFFHigh Security / Availability High Security and High Availability support trough Hot and Remote Stand-By

AgendaWhy ECM for SAP?Livelink ECM Suite for SAP SolutionsComponent OverviewBusiness ScenariosLivelink ECM Enterprise ArchiveSAP Content Server Summary

Business Solutions for SAP for SAP Solution Map for SAP R/3 ERPFinanceHuman ResourcesAccts PayableOperations Acc. ReceivableOrder MgmtAdministrationPurchasingStd. ProcessesSAP R/3 Enterprise Resource PlanningSCMOrder Ledger SD Document FlowPricing Folder Contract MgmtLivelink ECM -Enterprise ArchiveDispute ManagementLockbox SolutionAutomatic Invoice ReaderVendor InvoiceManagementPaymentAuditProcess Monitoring e-Distribution of A/R DocumentsRecruiting WF Compliant ArchivingPaper Folders of Terminated Empl.e-Employee FolderTravel Request & Expenses ManagementNew & Leaving Employee WFPurchase Requisition WFProcess ControllingCRMVendor Self Service

Business Solutions for SAP for SAP Example: SAP Accounts Payable Improves operational efficiency & productivity of the accounting departmentReduces risks and helps to stay compliantwith legal rulesSaves costs in process maintenance

Customer Example: AventisBACKGROUNDCore Business: Prescription drugs, human vaccines and 50% equity stake in Merial, an animal health joint venture with Merck & Co.Revenue: 17,59 Billion in 200271.000 employees in 2002Worldwide presence and markets

CHALLENGEStreamline financial processes globallyDesign and implement an integrated Receipt to Pay Process for all European countries

OPEN TEXT SOLUTIONReorganization of the Accounts Payable processCombination of SAP Workflow, BPM Server and PDMS7.000 users involved in approval process

BENEFITSIncreased productivity of A/P staffReduce the time and cost associated with resolving anomalies and invoice approvalEliminate time and cost associated with recovering documentsFlexibility for organizational changes

AVENTIS - Optimizing Accounts PayableLivelink Enterprise ArchiveApprovalRequired

Business Solutions for SAP for SAP Example: Customer Folder Improves operational efficiency & productivity of the accounting departmentReduces risks and helps to stay compliantwith legal rulesSaves costs in process maintenance

Reference: Volkswagen BankBACKGROUNDLeading European financial service provider in the automotive area > 3 million customers.

CHALLENGEDifferent business units are in contact with the same customer.Business Units are using separate systems (mySAP CRM, ERP, ...).Cross-Selling potentials not fully used

OPEN TEXT SOLUTIONStoring of all customer relevant information inside the Livelink Enterprise Archive ServerCustomer folder with Livelink DocuLink for SAP Solutions

BENEFITSImproved Customer ServiceNo unnecessary recallsUse of Cross-Selling PotentialOne information basis for all authorized employees and customers

Customers, Customer-Care-Center-employees and financial advisor are using the same data basis. We improved our processes significant with this ECM solution from Open Text. With the online postbox we created the fundament for a future with less paper.Joachim Walter, Head of Archiving Systems, Volkswagen Bank GmbH

Volkswagen Bank: ChallengeBusiness UnitFinancing

Dealer CustomerCustomer- Care-Center

Insurance

Leasing

Direct Banking

Volkswagen Bank: SolutionBusiness UnitDealerCustomerFinancingInsuranceOnline Portal Account Statements11/0412/0401/0502/05

WartungReparaturCustomer FolderLeasingContractFinancingInsuranceMaintenanceRepairingCustomer-Care-CenterLeasingDirect BankingLivelink ECM - Enterprise Archive

Strategic value of the Livelink ECM - Enterprise Archive

Supported Storage MediaHarddisks Primary as a temporary storage for performance reasons (cache, STORM, etc.)ASM StorageTekHSM, SUN SAM FS, GrauNettApp NearStore HDS (Hitachi Data System) EMC Centera Optical media CD, DVD, WORM Support of various jukebox vendors)Provides the highest possible security level - tamper proofInerasable, robust - water, dirt and magnetic field resistantBackup freeLivelink ECM - Enterprise Archivesupports almost every existing storage media

Fail-Over and DistributionRemote StandbyLocal StandbyLoad balancing for read accessRead failover if one medium not availableFull Remote StandbyPerformance balancingFull Read Access in case of failover (Document Server is not available)Automatic switch over to remote standby within a defined time without any user interactionRemote Standby for 2 or more local sitesFull Read Access for large distributed organizations

Fail-Over and DistributionHot-StandbyFull system availability after few minutesClients who didnt access the LEA during downtime will not notice the server swapRead / Write access in case of failoverNo mirroring of storage systemsRecommended for critical scenariosAvailability > 99.9 %High access ratesWorkflow scenariosCombination of Hot- and Remote Standby offers the best possible fail-over security!

Advanced Archive ManagementRetention ManagementDeletion of out-dated documents or documents extending the retention periodRendition managementAutomated rendition of office documents to long-term storage formats like TIFF or PDFDigital Signature (TimeStamp)Single Instance ArchivingBlob StoreLong term access to documents guaranteedStructured storage of documentsLogical archives, pooling concept and advanced management clientsIntegration of SAP meta dataNotification in case of problemsFully supports the SAP HTTP Content Server Cache technologySAP certification for SAP ArchiveLink 4.60 available

(for more information please read Whitepaper Livelink ECM Enterprise Archive)

One Enterprise-wide RepositoryWCMPDMSCollaborationSharePointGroupwareLivelink ECM Enterprise ArchiveEnterpriseApplicationsKMRecords Mgmt

Examples of large LEA installationsExamples for large Open Text customer installations:

Livelink ECM Enterprise Archive CustomersMore than 3000 customers are running Livelink ECM - Enterprise Archiveworld-wide!

Value Proposition for Livelink Enterprise ArchiveTechnologyRobust technology Scalability (many users, high document volumes) Platform independent (Support of many different storage and devices)Fully integrated in leading applications like SAP, Siebel, ...

Compliance with legal regulationsSecurity (encryption, timestamps, HTTPS, SecKeys) Long-term accessibility (Storage media and document formats)Unalterable storage (Storage without difference in formats)Ensure data consistencySupporting the document live cycle (Retention periods)

Economical ReasonsCost efficiency Manage all enterprise documents Manageable (central administration, high availability, distributed scenarios, disaster recovery) Protection of investment

AgendaWhy ECM for SAP?Livelink ECM Suite for SAP SolutionsLivelink ECM Enterprise ArchiveSAP Content Server What SAP recommendsFunctional OverviewSAP CS and File SystemSummary

What SAP recommendsWhat is SAP Content Server? The SAP Content Server is a separate and server based component to store content such as electronic documents originating from different formats. The SAP Content Server ist provided by development of technology and is to be used cross application for any SAP applications. He is to be installed on a separate system. Typical content is training material and documentation from Knowledge Warehouse or technical drawings originating from mySAP PLM Document Management System. Is the SAP Content Server an archiving system? The SAP Content Server is not an archiving system. It does not support optical storage or optical archiving. Storage takes place in a database or on a file system. Compared to archiving or other external document management systems there is no scanning and OCR (optical character recognition) service supplied by SAP.SAP Content Server FAQs - SAP Service Marketplace (November 2005)

What SAP recommendsSAP Help http://help.sap.comConstraintsThe SAP Content Server is not intended to replace optical storage systems and other storage media for long-term archiving of documents.

What SAP recommendsDoes the SAP Content Server replace an archiving system? No. The SAP Content Server can be used to store electronic documents but is not able to scan or archive them on optical media. Typically with archiving systems a scan-client, viewer, retrieval and administrations tools and jukeboxes or HSM are provided.

What is the latest available SAP Content Server version? SAP Content Server 6.30 is the most recent version. It has been available since October 31, 2003 SAP Content Server FAQs - SAP Service Marketplace (November 2005)

What SAP recommendsIs the SAP Content Server released to beused for data archiving?Until release SAP CS 6.20 is not intended to handle large files as it is with data archiving. SAP CS 6.30 was optimized to handle large files. However there are some restrictions to consider: Data archiving on optical media is not supportedRegular backups are requiredSupports only storage in uncompressed formatSAP CS for Windows is not released for data archivingSAP CS and the underlying SAP DB have to be installed on the same machineSAP Content Server FAQs - SAP Service Marketplace (November 2005)

What SAP recommendsHow does the SAP Content Server store content?The SAP Content Server stores content on a separate SAP DB. SAP DB and SAP Content Server are both installed on a separate server. With SAP Content Server 6.30 it is now possible to store documents alternatively on SAP DB or file system. SAP recommends to use the SAP DB as preferred storage place, because it has administration tools.A file system has to be administrated and access has to be restricted according to execution rights of users.As well SAP DB as file system stores content on magnetic disks.

What SAP recommendsIs it possible to run SAP Content Server in ahigh availability or fail-over environment?It is possible to run SAP Content Server in a high availability environment using Microsoft Cluster Service (MSCS). However there are some restrictions to consider:All servers must run MS Windows 2000 Advanced ServerAll users have to be maintained in a MS NT domain (or in Active Directory Service)SAP Content Server for UNIX does not support high-availability scenario (cluster service).See details within the white paper SAP Content Server in an MSCS Environment.How can I replicate documents from one server to another? The SAP Content Server does not support replication. SAP Content Server FAQs - SAP Service Marketplace (November 2005)

What SAP recommendsWhich operating systems are supported by the SAP Content Server?The SAP Content Server 6.30 supports Unix and Windows platforms. Details see SAP note 622509. Until SAP Content Server Release 6.20 only Windows operating system is a supported. What are the SAP Content Server pricing conditions?SAP Content Server is available for all SAP customers without any additional license costs (November 2005).SAP Content Server FAQs - SAP Service Marketplace (November 2005)

Internal Note: Open Text Services performed a series of tests with SAP Content Server on Windows and UNIX/Linux. Our experiences with SAP CS on UNIX/Linux were disappointing. There are many changes in installation procedure documented in SAP notes and missing in the product documentation. There are many version restrictions and most-current UNIX and Linux versions are not supported. The installation procedure includes many manual tasks. This all makes installation on UNIX/Linux very difficult.

Furthermore, many SAP CS customer (UNIX/Linux) claim bad stability and system performance. In fact, this is the most important reason for customers to replace SAP CS with an Archive.

AgendaWhy ECM for SAP?Livelink ECM Suite for SAP SolutionsLivelink ECM Enterprise ArchiveSAP Content Server What SAP recommendsFunctional OverviewSAP CS and File SystemSummary

SAP Content Server CharacteristicsFail Over and BackupHigh-Availability (Hot-Standby)Only with MSCS (Microsoft Cluster Service) on Windows 2000 Professional ServerNot available for UNIX operating systemsNo Remote-Standby scenarios supportedNo local backup of mediaNo replication of logical archives also important for performance reasons

Backup & Recovery strategyProblems might occur if time required for the backup extends the maximal available backup time (e.g. nightly hours)Costs and efforts for backups are rinsing fast on a increasing document and data volumeContent restore recovers only data and documents archived at the time of the last backup. New documents and data is lost.

SAP Content Server CharacteristicsSupported Storage MediaSAP Content Server and SAP DBRequires regular database backups Additional storage space and maintenance requiredBackup time might extend the available maintenance period (nightly backup)SAP DB most likely outperforms Filesystem storage on high loaded servers Is the recommended storage media (because of the performance, security and administration support)SAP DB is a proprietary SAP system. Documents stored in the SAP Content remain accessible only through the SAP ERP system / SAP Content Server

SAP recommends to use SAP DB for document and content storage with SAP Content Server

SAP Content Server CharacteristicsSupported Storage MediaSAP Content Sever and filesystem storageNo transaction security in the filesystemNo administration tools provided by SAPSeparate not integrated administration clients for user and permission management, filesystem management, SAP Content Server administration, Backup and Recovery administrationNo support for data recovery on the FSSIn case of exception there is no administrational support. It is up the customer how to implement a backup and recovery strategySelf-contained data organization with a minimum of management tables or metadataIf repositories are not well maintained data privacy cannot be guaranteedLots of easy way to screw consistency if documents are modified outside of SAP application domainRequires regular database backups additional storage space and maintenance required

SAP Content Server CharacteristicsSupported Storage MediaHans-Joachim Both, SAP Content Server Running on UNIX (Ver. 6.30), SAP Tech ED 2002

SAP Content Server CharacteristicsBusiness Scenario SupportSAP Content Sever is a content storage not a business solutionNo scan software for mass-document scanning (e.g. for Invoice Verification)Customers need to purchase additional third-party scan applicationAdditional project and consulting costs and for integration of the third-party scan solution with SAP Content Server and SAP R/3 Customers are restricted to the SAP ECL (or EAI) - Viewer or an other third-party document viewer missing Open Text specific functionality likeNotes, Annotations, Form overlay, etc.Integration of MS Office documentsEmail integration ScanningNo batch import interface / COLD No out-of-the-box solution for automated mass document import in SAP (e.g. for imports of large amounts of scanned documents)Requires consulting partner supportNo product maintenance and no compatibility guaranteedNo Rendition Management

AgendaWhy ECM for SAP?Livelink ECM Suite for SAP SolutionsLivelink ECM Enterprise ArchiveSAP Content Server What SAP recommendsFunctional OverviewSAP CS and FilesystemSummary

SAP Content Server CharacteristicsFilesystem Storage Most HSM systems provide sophisticated security and backup capabilitiesSome HSM systems allow optical archiving very high level of securityCompanies having an HSM system are able to reuse existing hardware resources lower initial costs SAP Content Server supports filesystem storage. This allows to store SAP CS content on a HSM or other SAN system.

SAP Content Server CharacteristicsFilesystem StorageNot designed to support large document filesThe combination of SAP Content Server and a HSM system is not designed to support large document files. The complete document has to be retrieved from the HSM system in order to access just a part of it. This results in long response times and bad performance on the client sidePerforms bad with huge amounts of small documentsHSM system are designed to store large volumes of documents, but they perform bad with huge amounts of small documents. Many vendors as well as EMC recommend to package small documents in ISO images in order to improve the system performance. This requires an additional archiving system. SAP Content Server is not able to group files in packages.No optimization for high-loaded environmentsNo optimization for high-loaded environments (e.g media change reduction). Livelink ECM Enterprise Archive usually outperforms a HSM system in high-loaded environmentsNot suitable as a long-term storage systemsHSM systems are not suitable as a long-term storage systems. Tapes and harddisk might get damaged. No migration support. No alternative access to documents. Backups are readable only by the same type storage system, etc. Long response timesAccess requests to documents located on tapes (the preferred HSM storage media) especially on high loaded servers result in very long response times. This result in many cases in time-out errors on the client side and poor user acceptance.No Rendition Management

Summary

SummaryLivelink Enterprise Archive is a as an long-term enterprise-wide document backbone. It provides a series of build-in functions to support companies over the time in line with the increasing size of the archive, new requirements and the installation complexity.

SummaryShort-term storageof dynamic contentSecure long-term storageECMSolutionLivelink Enterprise Archive is an ECM solution!Security, reliability, and the ability to run in many different environments make LEA a enterprise-wide document management backbone for all business related documents within a company!

SummarySAP Content Server is not an archiving system. It is missing important functionality to ensure secure, authentic, unaltered and long-term document storage, which is required to meet legal rules and regulations e.g for financial documents.SAP Content Server is storage solution without additional components (like scan client) required to support complex customer scenarios. In opposite to this, Open Text is offering a complete product and solution suite. Open Text offering results in higher license costs, but lower project costs and maintenance efforts as well as in a much higher system security.SAP Content Server is suitable to store dynamic content like marketing materials or knowledge management content. LEA is a high-available and high-secure solution required by companies for a secure long-term storage of business critical documents and information.SAP Content Server is a SAP-only solution. There are no integrations with other legacy systems available. LEA is a ECM document repository and supports a variety of different leading enterprise applications.

Decisions based on incomplete information Examples:A/P: Invoice verification (accepting/rejecting invoice)Call center agent answers customer call with incomplete customer information at handTechnical documents are not available at production site High administrative costs due to (manual) process of combining content coming from various sources A/R: Dispute resolution Non-integrated processes decrease the overall process efficiencyLong response times, e.g. resulting in call-backs in call centersInformation gathering takes long, e.g. all documents for a customer projectSlow information flow (workflow), e.g. applicant processingInformation vanishes, e.g. technical documentation for machines in plantsLimited information sharing, e.g. across business units

Business continuity at risk

Cost of (non-)compliance

GOS General Object Service: Einklicken in die SAP Menuleiste, ffnen aus SAP GUI Menu eine OTEX DocuLink Applikation und bergeben der MetaDaten.So what we learn is. A closer look at the Livelink ECM - Suite for SAP Solutions whats in? see slide

A closer look at the Livelink ECM - Suite for SAP Solutions whats in? see slide

If you compare LEA with SAP Content Server, you shouldnt forget that Open Text offering is not limited to LEA and other products. Open Text is also supporting and offering complete business solutions, which help customers to increase the efficiency, to save costs, ensure legal compliance and protect from risks.

The map shows how Open Text provides content within the context of SAP ERP. This is done directly within the native SAP modules (Accounts Payable, etc.) and through content-centric Open Text application modules (e.g. Open Text Solution for Accounts Payable) that complement SAP functionality. For example: An excerpt from the combined Open Text/SAP solution map, showing SAP business processes (e.g. in Finance: Accounts Payable, Accounts Receivable, etc.). Open Text provides business information integration through additional content-centric applications like the Invoice Reader (which provides automatic capturing and indexing of incoming invoice documents through intelligent character recognition), Invoice Ledger (which tracks and manages all incoming invoices through the entire life cycle from receipt to pay), Invoice Verification Workflows (which are based on SAP Workflow; Ranging from single-step to complex multi-step approval workflows for Non-PO invoices), Payment Audit, etc.). Open Text provides this level of depth all across all modules of SAP.This is a business solution example for Accounts Payable in SAP with LEA.

The three core business values are This three values are an umbrella for all benefits which a customer can get out of the Open Text investment.

Customer Folder is another example for a business solution with Open TextProblemstellung:Die in der Vergangenheit eigenstndig agierenden Geschftsbereiche der Volkswagen Bank nutzen unterschiedliche IT Systeme und Bereichs- und Abteilungsspezifische Ablageorte fr Dokumente. Das fhrte dazu das verschieden Bereiche mit dem selben Kunden in Kontakt sind ohne voneinander zu wissen. Es war deshalb schwierig Cross-Selling Potentiale zu nutzen. So wusste z.B. der Bereich Fahrzeugfinanzierung nicht ob der Kunde schon im Besitz einer Volkswagen Fahrzeugversicherung ist.Fr den Mitarbeiter im Call-Center war es sehr schwierig auf alle relevanten Informationen aus den einzelnen Bereichen zuzugreifen um dem Kunden schon beim ersten Anruf kompetent und umfassend zu helfen. Dies fhrte dazu das viele Anfragen erst in weiteren Zeit und kostenintensiven Telefonaten geklrt werden knnen.

Ursache der Probleme:Es gab keine einheitliche und aktuelle Informationsbasis auf die alle berechtigten Mitarbeiter zugreifen knnen.

Ziel:Nach Zusammenfhrung der Finanzdienstleistungs-Aktivitten (Finanzieren, Leasen, Versichern, Direct Banking) in der Volkswagen Bank wird eine gemeinsame zentrale Datenbasis aufgebaut.Lsung:Ein Kundenordner im SAP System bietet eine zentrale Sicht auf alle kundenrelevanten Informationen, dabei werden unter anderem Informationen aus einem SAP R/3 und mySAP CRM System in einem zentralen Kundenordner dargestellt. Die Mitarbeiter im Call Center oder in den einzelnen Geschftsbereichen knnen nun sehr einfach ber eine Browser-Oberflche auf alle relevanten Kundeninformationen zugreifen. ber Berechtigungen wird gesteuert welcher Mitarbeiter welche Informationen sehen, verndern oder hinzufgen darf.Alle Dokumente werden zentral im Livelink Enterprise Archive Server langfristig und sicher gespeichert.Die Kunden der Volkswagen Bank haben weiterhin die Mglichkeit online auf Ihre Kontoauszge zuzugreifen.Strategic Value of the LEAsee slideOpen Text supports all common storage types Harddisk - Open Text recommends this media as a cache or temporary storage (for performance reasons)Optical media LEA supports a large variety of various jukebox vendors. Optical media provide the highest possible security and are a cheap, media . They are inerasable, robust, water, dirt or magnetic field resistant. NettApp NearStore with SnapLock, which is basically a large hard disk RAID systemsEMC Centera and Symmetrix works like a library. There is no file structure available. EMC returns a kind of ticked for each stored file. This ticked is required to access the file again. If the ticked gets lost, you want be able to find the file again. So EMC customers need a archive or document management system on-top in order to store documents in EMC.HSM Open Text supports StorageTek, ASM, SUN, SAM FS, Grau DataStorage, InfiniStore and others not listed here

Take this quote from our customer as a proof for the security and reliability of the Open Text product

Hurricane Floyd completely destroyed our paper files ... If we had not had IXOS installed, we would have lost them - we never interrupted production because of IXOS. Stan Olszyk, System Analyst Configurator , Heraeus Amersil

see slide see slideThese are features supported by Open Text but not by SAP CS!Retention Management Extremely important e.g in the HR department. Personal documents need to be stored for a certain period but not longer! The HR department has to ensure all documents are deleted on time.Rendition Management with Open Text RenditionServer. Required for e.g. contracts which are dynamic documents (e.g. MS Word) but become static after document release. In order to meet legal requirement, this documents needs to be stored in a long-term document format (TIFF or PDF). Encryption supports Data Archiving and large document files (partial document encryption) for fast document accessDigital Signature Resolves the problem of a handwritten signature required for some business processes. This are usually business processes, which have multiple steps and lead to a significant business transaction (e.g. allocation of mortgage loans or inspection reports of aircraft parts). Long term access to documents guaranteed - Single Instance Archiving only one copy of a document is archived, even if the same document was archived multiple times. Important especially for email archiving.Blob Store The content is stored in a cache until it exceeds a predefined size. After this, storage image is written at one (important for optical media). This improves the system performance and optimizes storage space usageLong term access to documents guaranteed Open Text guarantees the long-term access to all archived documents by using accepted long-term document formats (TIFF, PDF) and the ISO filesystem structure. Notification in case of problems - Fully supports the SAP HTTP ... LEA is certified to run as a SAP HTTP Content Server Cache server. It also provides own separate caching functionalityThe LEA is the central component in this architecture. It is the basis document storage for almost all existing Open Text solutions. Solutions not supporting the LEA server right now will do it in the future. With LEA documents from applications like SAP, Siebel, Groupware (Emails in Exchange), Web Content Management can be stored as a part of one and the same repository. This allows customers to join information from different applications at one location and have a cross-system and process-centered view on documents and information. Continuing the Order Management example, with LEA customers is able to store and provide one central view on all documents related to a sales order. This might be invoices or other fiscal documents from SAP, emails from Exchange or Notes an customer contracts created and maintained using Open Text DMS.

Besides of that, LEA is a central management component for all storage media within a company. LEA support almost all existing common storage media optical media like CD-ROM, DVD, WORMS, etc., HSM, EMC, Harddisks, NetApp from many different hardware vendors.Customers using Open Text archivingAll these answer and questions are result of a summary of the SAP Content Server FAQs (SAP Service Marketplace ) and other SAP material available in SAP Service Marketplace.All these answer and questions are result of a summary of the SAP Content Server FAQs (SAP Service Marketplace ) and other SAP material available in SAP Service Marketplace.

All these answer and questions are result of a summary of the SAP Content Server FAQs (SAP Service Marketplace ) and other SAP material available in SAP Service Marketplace.





Customers are able to use the high-availability functionality of the SAP Content Server based on the Microsoft Cluster Service. High-Availability means:Multiple SAP Content Server are acting (working) as one large server. All SAP Content Server within the cluster are sharing the same data source located on a network fileserver (database)If one of these servers crashes other take over his tasksIn companies with a high user load server cluster allow the to balance the user load on several separate serversIn a high availability scenario only the servers are running synchronous the data source remains the same. If the file server crashes the whole serve cluster will crash. Restrictions:Is available only if running on MS Windows 2000 Professional Server (not available for UNIX)Not recommended for scenarios using file system as storage media

SAP Content Server does not offer any High-Security (Open Text terms Remote-Standby) featuresRemote-Standby means:Data security is ensured (disaster security - no data loose)In a remote-standby scenario the entire (or parts) of the whole document/data repository are replicated on another server located in an another location. This ensures data remains available even if the original server gets destroyed by fire or flood.Increases the system performance (access time) in scenarios where users are located in different locations on different continents (one document server is located in EMEA, another USA, etc.).SAP Content Server does not offer any data or archive replication tools or functionality in order to run in a high security scenario.

The SAP CS backup strategy is to backup the complete database (or filesystem storage) on external storage media (e.g. tapes). In case of emergency this backup is used to reconstruct the SAP Content Server.Problems might occur if time required for the backup or recovery extends the maximal available backup time (e.g. nightly hours) Doubles the required storage space (tapes, additional file system space, etc.)Efforts for Backups are increasing proportional to the data and document volumeSAP Content Server is able to use the SAP DB and the filesystem to store archived documents and data. SAP DB is the recommended storage media offering the better performance and security compared with the filesystem. SAP DBHowever, SAP DB requires regular database backupsIn order to ensure data security using SAP DB, administrator need to backup the database on filesystem and then start a backup process copying the database dump on some backup media like tapes (this is the normal procedure, there might be other strategies used by customers). This requires additional administration, hardware and maintenance efforts administration somebody needs to know how to backup and RESTORE SAP DB a maintenance somebody needs to take care for the backup strategy, verify the backup, media availability and status, etc... hardware database backup is usually done on a filesystem, then backuped on magnetic media like tape. This means additional costs for storage space, tapes and backup hardware, etc.SAP DB allows to restore only complete database repositories, not single documents. (Imagine, you need to recover a 4-5 TB large system...)SAP admits that the SAP DB will mostly outperform filesystem storages on high loaded servers.FilesystemThe new filesystem interface allows customers to reuse existing storage capacities (like fileservers with disk arrays, HSM systems, etc.)However this interface provides noNo transactional security means, if the user click on store document in SAP GUI SAP does not guarantee the file is really stored in the filesystem.No administration tools means, there are no tools to maintain the filesystem storage (check-up the capacity, mount additional drives, set permissions and verify SAP Content Server is still working fine, etc.). Customers needs to use other hardware or operational system specific tools.No support for data recovery on the filesystem. There are no management tools provided by SAP to backup and restore a filesystem storage. There are no SAP tools allowing to schedule a regular backup, reselect all required files for backup, etc. On the other side recovery customer has to find the right location for the recovery (which file has to be copied in which folder). Which files are required for a recovery? This becomes really difficult, if customer Self-containing data organizationmight get easily damaged if modified outside SAPCustomer is responsible for securityRequires additional backups -> administration, maintenance

SAP Content Server is able to use the SAP DB and the filesystem to store archived documents and data. SAP DB is the recommended storage media offering the better performance and security compared with the filesystem. SAP DBHowever, SAP DB requires regular database backupsIn order to ensure data security using SAP DB, administrator need to backup the database on filesystem and then start a backup process copying the database dump on some backup media like tapes (this is the normal procedure, there might be other strategies used by customers). This requires additional administration, hardware and maintenance efforts administration somebody needs to know how to backup and RESTORE SAP DB a maintenance somebody needs to take care for the backup strategy, verify the backup, media availability and status, etc... hardware database backup is usually done on a filesystem, then backuped on magnetic media like tape. This means additional costs for storage space, tapes and backup hardware, etc.SAP DB allows to restore only complete database repositories, not single documents. (Imagine, you need to recover a 4-5 TB large system...)SAP admits that the SAP DB will mostly outperform filesystem storages on high loaded servers.FilesystemThe new filesystem interface allows customers to reuse existing storage capacities (like fileservers with disk arrays, HSM systems, etc.)However this interface provides noNo administration tools means, there are no tools to maintain the filesystem storage (check-up the capacity, mount additional drives, set permissions and verify SAP Content Server is still working fine, etc.). Customers needs to use other hardware or operational system specific tools.No support for data recovery on the filesystem. There are no management tools provided by SAP to backup and restore a filesystem storage. There are no SAP tools allowing to schedule a regular backup, reselect all required files for backup, etc. On the other side recovery customer has to find the right location for the recovery (which file has to be copied in which folder). Which files are required for a recovery? This becomes really difficult, if customer Self-containing data organizationmight get easily damaged if modified outside SAPCustomer is responsible for securityRequires additional backups -> administration, maintenanceNot designed to... A HSM system returns always a complete document. This means for large files (especially data archiving print lists) the complete file has to be read from a tape and returned to SAP CS in order to access only e.g. one line item. Imagine how much time is required te read a 3GB large document and then to transfer this document to the client. Especially, if there are multiple users requesting with this file. Open Text is able to read only a part of a large print list from storage media in order to return the requested data. This works even if the customer decides to use document encryptionPerforms bad with HSM system are designs to handle large volumes of data. However, their get problems with a huge amounts of single (small) files. This is sometimes the case for large amounts of outgoing or incoming TIFF documents. There are many HSM vendors recommending to bundle small packages in ISO images (and therefore to reduce the amount of files To do this, an archive system on-top the HSM is required. LEA supports this feature.No optimization for A HSM system usually moves documents and data on tapes after a perid based on pre-defined rules. There are usually a lot of different, sometimes hundreds or even more tapes in a HSM system. If there are a lot of request for documents located on several separate medias the storage system has to change the media (tape, WORM, etc.). Open Text checks the document request queue for documents located on the same media. This requests are bundled allowing to reduce the amount of media changes resulting in a better system performance. SAP CS does not support this functionality and even if the HSM system does support this it cannot work that efficient than with Open Text.Access requests to documents located... Imagine how long it takes to put a tape in a drive, rewind or find a document on a 250m long tape. Some HSM vendors even confirm response times up to 1.5 hour. see slide see slideNot designed to... A HSM system returns always a complete document. This means for large files (especially data archiving print lists) the complete file has to be read from a tape and returned to SAP CS in order to access only e.g. one line item. Imagine how much time is required te read a 3GB large document and then to transfer this document to the client. Especially, if there are multiple users requesting with this file. Open Text is able to read only a part of a large print list from storage media in order to return the requested data. This works even if the customer decides to use document encryptionPerforms bad with HSM system are designs to handle large volumes of data. However, their get problems with a huge amounts of single (small) files. This is sometimes the case for large amounts of outgoing or incoming TIFF documents. There are many HSM vendors recommending to bundle small packages in ISO images (and therefore to reduce the amount of files To do this, an archive system on-top the HSM is required. LEA supports this feature.No optimization for A HSM system usually moves documents and data on tapes after a perid based on pre-defined rules. There are usually a lot of different, sometimes hundreds or even more tapes in a HSM system. If there are a lot of request for documents located on several separate medias the storage system has to change the media (tape, WORM, etc.). Open Text checks the document request queue for documents located on the same media. This requests are bundled allowing to reduce the amount of media changes resulting in a better system performance. SAP CS does not support this functionality and even if the HSM system does support this it cannot work that efficient than with Open Text.Access requests to documents located... Imagine how long it takes to put a tape in a drive, rewind or find a document on a 250m long tape. Some HSM vendors even confirm response times up to 1.5 hour. see slide see slide see slide.. see slide.. see slide

Thank You!

Livelink Enterprise Archive vs. SAP Content Server - DETAILED.ppt

Documents

Transcript of Livelink Enterprise Archive vs. SAP Content Server - DETAILED.ppt