Technical Overview of inpoint Content Server for SAP

Transcription

1 1 P a g e

2 H&S contact Details Contact: Bernd Machner Phone: +49 ()) Address: Introduction H&S has been an FIS Information Systems partner for more than 5 years and have extensive knowledge and project experience for more than 25 years. H&S are located in Vienna, Austria (Headquarters), Schwabach (Germany) and St Gallen (Switzerland) The inpoint Content Server provides a secure access to documents via FIS/edc (invoice monitor) as well as additional monitors (i.e.. document monitor, order confirmation monitor, sales order monitor). 2 P a g e

3 Functionality Summary of H&S inpoint Content Server for SAP Certified SAP ArchiveLink TM interface IinPoint CSS is certified by SAP as an archive link software solution In Point CSS stores images from FIS/edc monitors (scanned documents and ed attachments). The images can also be viewed through SAP (i.e. MIRO MIR4) transaction inpoint CSS is able to set a retention time for archived images, after this period it is possible to delete the image. inpoint CSS can also store other SAP related documents Administration is possible with SAP Basic Know how Supports all archiving methodology Supports all SAP Releases form SAP R/3 onwards Document view with SAP Standard features Support and legal archiving and certified for several WORM storages. 3 P a g e

4 inpoint CSS - Display of Image via FIs/edc monitors and SAP ERP. For every document FIS/edc will create an IDoc with a link to the image (i.e. pdf format). The images are stored on the inpoint CSS server not a file server creating additional space on the SAP server. SW- and HW requirements Application server inpoint ContentServer Hardware: Physical or virtualized OS: Windows Server 2008 Windows Server 2008 R2 Windows Server 2012 Windows Server 2012 R2 Memory (min.) 4 GB Processor: act. server generation with Quad-Core processor Hard disk: 100 GB (System + Data) Additional software: IIS 7.0 or higher.net Framework 3.5 SP1 WSE 3.0 (Web Service Extension) in case of oracle database: oracle client 32 bit (compatibility with used oracle version) 4 P a g e

5 Roles Web Server (IIS) Web Server Common HTTP Features Default Document Static Content Health and Diagnostics HTTP Logging Security Basic Authentication IP and Domain Restrictions URL Authorization Windows Authentication Application Development.NET Extensibility 3.5.NET Extensibility 4.5 ASP ASP.NET 3.5 ASP.NET 4.5 ISAPI Extensions ISAPI Filters Management Tools IIS Management Console IIS 6 Management Compatibility IIS Management Scripts and Tools Management Service Features.NET Framework 3.5.NET Framework P a g e

6 Database server (Oracle) Oracle Server Oracle 10g Oracle 11g Software and hardware requirements see oracle server requirements Database scheme 1 archive per system (optional test, quality, production) 1 HSM per system (optional test, quality, production) Tablespace min. 2 per scheme (data and index) Hard disk 250 MB (for 50,000 documents in 5 years) Database server (MSSQL) MSSQL Server Microsoft SQLServer 2008 Microsoft SQLServer 2012 Microsoft SQLServer 2014 Software and hardware requirements see MS-SQL server requirements Database 1 archive per system (optional test, quality, production) 1 HSM per system (optional test, quality, production) Hard disk 250 MB (for 50,000 documents in 5 years) Storage system Supported certified systems NetApp iternity Fast-LTA HDS-NAS Hitachi GRAU Filelock / Archivemanager Supported system EMC Centera HP Riss IBM Tivoli all systems which support access via windows share (CIFS protcol) 6 P a g e