sap icc-bc-al interface document
DESCRIPTION
SAP interfacesTRANSCRIPT
SAP ArchiveLink / HTTP Content Server 6.20 Test Plan SAP AG
SAP Integration and Certification Center
1
SAP ArchiveLink / HTTP Content Server 6.20 Test Plan
Version 1.0, 2011-02-14
Release 6.20
SAP AG SAP ArchiveLink / HTTP Content Server 6.20 Test Plan
SAP Integration and Certification Center
2
Copyright
Copyright 2011 SAP AG. All rights reserved.
Neither this document nor any part of it may be copied or reproduced in any form or by any means, or translated into another language, without the prior consent of SAP AG.
SAP AG makes no warranties or representations with respect to the content here of and specifically disclaims any implied warranties of merchantability or fitness for any particular purpose. SAP AG assumes no responsibility for any errors that may appear in this document. The information contained in this document is subject to change without notice. SAP AG reserves the right to make any such changes without obligation to notify any person of such revision or changes. SAP AG makes no commitment to keep the information contained herein up to date. Some software products marketed by SAP AG and its distributors contain proprietary Software components of other software vendors.
Microsoft®, WINDOWS®, NT®, EXCEL®, Word® and SQL Server® are registered Trademarks of Microsoft Corporation.
IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®,
S/390®, AS/400®, OS/390®, and OS/400® are registered trademarks of IBM
Corporation.
ORACLE® is a registered trademark of ORACLE Corporation, California, USA.
INFORMIX®-OnLine for SAP and Informix® Dynamic Server are registered trademarks of Informix Software Incorporated.
UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of The Open Group.
HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®,
World Wide Web Consortium, Laboratory for Computer Science NE43-358, Massachusetts Institute of Technology, 545 Technology Square, Cambridge, MA 02139.
JAVA® is a registered trademark of Sun Microsystems, Inc. , 901 San Antonio Road, Palo Alto, CA 94303 USA.
JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.
ADABAS® is a registered trademark of Software AG.
SAP, SAP Logo, mySAP.com, mySAP.com Marketplace, mySAP.com Workplace, mySAP.com Business Scenarios, mySAP.com Application Hosting, WebFlow, R/2, R/3,
RIVA, ABAP, SAP Business Workflow, SAP EarlyWatch, SAP ArchiveLink, BAPI,
SAPPHIRE, Management Cockpit, SEM, SAP DB are trademarks or registered
Trademarks of SAP AG in Germany and in several other countries all over the world. All other
products mentioned are trademarks or registered trademarks of their respective companies.
SAP ArchiveLink / HTTP Content Server 6.20 Test Plan SAP AG
SAP Integration and Certification Center
3
Contents
SAP ARCHIVELINK / HTTP CONTENT SERVER 6.20 TEST PLAN ........................................................................... 1
CHAPTER 1 : OBJECTIVES............................................................................................................................... 4
CHAPTER 2 : PRINCIPLE REQUIREMENTS FOR THE FUNCTIONAL TEST ........................................................ 5
CHAPTER 3 : TESTING THE TECHNICAL CONNECTION BETWEEN SAP AND THE SUB SYSTEM (ONLY IF
CERTIFICATION HELD IN WALLDORF) ................................................................................................................ 6
CHAPTER 4 : HTTP COMMUNICATION .......................................................................................................... 7
4.1 TEST PROGRAM RSCMST ............................................................................................................... 8
4.2 TEST PROGRAM Z_NEW_PRI_LIST ................................................................................................ 10
4.3 TEST PROGRAM Z_NEW_OUT_DOC ............................................................................................. 11
4.4 SINGLE TESTS ............................................................................................................................. 12
CHAPTER 5 : OLE-2.0 AUTOMATION ........................................................................................................... 14
5.1 OLE – SINGLE STAGE ARCHIVING IN DIALOG ....................................................................................... 15
5.2 OLE - SINGLE STAGE DISPLAYING OF ARCHIVED DOCUMENT ................................................................... 16
CHAPTER 6 : BAR CODE BAPI - CONFIRMATION OF MULTIPLE BARCODES WITH BAPI_BARCODE_SENDLIST
17
6.1 TEST BARCODE SEND WITH THE BAPI METHOD ‘BAPI_BARCODE_SENDLIST’ ........................................ 18
6.2 CORRECT ERROR HANDLING BY THE ARCHIVE SYSTEM ........................................................................... 19
CHAPTER 7 : GET INFORMATION FOR CERTIFICATE ................................................................................... 20
SAP AG SAP ArchiveLink / HTTP Content Server 6.20 Test Plan
SAP Integration and Certification Center
4
Chapter 1 : Objectives
This section describes the technical certification of an interface for SAP ArchiveLink
Release 6.20. The Interface Release 6.20 (0045 in transaction OAC0) refers to the
according SAP Release where this interface has been first introduced (SAP R/3 4.5B); it
does not refer to the SAP Release itself. Therefore, since SAP ArchiveLink 6.20 has not
been changed all certifications will be made under the same conditions as before in the
current SAP NetWeaver Application Server releases. The objective is communication
between the R/3 System and a partner‟s archive
1. Via HTTP (Hyper Text Transfer Protocol) between application server – front-end
and Content Server. The communication between a SAP system and a HTTP Content
Server can be certified separately. A full SAP ArchiveLink certification requires the
certification of the OLE 2.0 Automation and Barcode Handling
2. Via OLE 2.0 Automation between front-end and archive
3. Barcode Handling via BAPI method BAPI_BARCODE_SENDLIST
4. OPTIONAL: The quality assurance test sequence for AL-LOAD
As preparation please work through the SAP Content Server HTTP Interface and SAP
ArchiveLink documentation.
To assist you further, please refer to the Online Help Portal of SAP:
http://help.sap.com
This documentation is valid only in junction with a consulting appointment and
the given verbal explanation. This documentation is handed out as part of the
consulting from SAP Integration and Certification Center (ICC).
After every certification test a test report is handed out. All the chapters within the
minute also refer to this test plan.
If you face any problems during your certification preparations please contact your ICC
contact.
SAP ArchiveLink / HTTP Content Server 6.20 Test Plan SAP AG
SAP Integration and Certification Center
5
Chapter 2 : Principle requirements for the functional test
Systems for which the following requirements should be met are connected via SAP
ArchiveLink:
o Data protection guarantee
o High-performance filing and access to archived documents
o Data security guarantee
o Extensive potential for managing disks/volumes, including extensive safety
mechanisms, such as copying disks, difference security, mirror disks
o Convenient, largely automatic archive system administration
If an archive system does not meet any of these individual requirements, the archive
system supplier must specifically indicate this.
All the specified functions are tested in a package and must be implemented for
certification. There are no optional parts.
Part of the certification test is the Solution Manager Ready functionality, which is
described in a separate test pan.
The mentioned test reports beginning with “Z_” will be provided to you by your ICC
consultant on your request.
SAP AG SAP ArchiveLink / HTTP Content Server 6.20 Test Plan
SAP Integration and Certification Center
6
Chapter 3 : Testing the technical connection between SAP and the
sub system (only if certification held in Walldorf)
For the test it is necessary to bring in the following hardware:
Any kind of hardware with the appropriate operating system installed, Network card
and enough disk space sufficient to run all tests described in this document. SAP will
not provide any hardware or software needed for the vendor‟s products.
The following software should be installed if applicable:
Content Server-software with the related HTTP functionality (HTTP Content Server),
OLE and Barcode application, and an installed current SAPGUI.
We will use DHCP in the certification LAB, documentation is available to change the
appropriate network settings accordingly. The connectors are of type RJ45.
SAP ArchiveLink / HTTP Content Server 6.20 Test Plan SAP AG
SAP Integration and Certification Center
7
Chapter 4 : HTTP Communication
Description
The implementation of HTTP calls as specified in the SAP Content Server HTTP
interface documentation is fundamental for the certification test.
Preparation
An http connection between the SAP System and the Content Server has to
been established.
Realize
The following http-functions are tested:
Access functions:
info
get
docGet
create
mCreate
append
update
delete
search
attrSearch
Server Functions:
putCert
serverInfo
Check
All messages must function on an error-free basis.
The following criteria are used to estimate each message. All criteria must be met:
Correct answer message string in accordance with the specification
Correct status display
Correct document retrieval
SAP AG SAP ArchiveLink / HTTP Content Server 6.20 Test Plan
SAP Integration and Certification Center
8
4.1 Test program RSCMST
Description
The test framework RSCMST allows starting several independent test reports.
Synchronous filing and retrieval of documents via the application server are tested.
During the test several test reports are called such as:
RSCMSTH0
create
info
search
delete
docGet
get
RSCMSTH1
serverInfo
create
docGet
info
update
delete
putCert
RSCMSTH2
serverInfo
update
create
get
info
delete
RSCMSTH3
create
docGet
info
mCreate
delete
RSCMSTA0 (SCMS_API test suit)
create
info
search
delete
docGet
get
SAP ArchiveLink / HTTP Content Server 6.20 Test Plan SAP AG
SAP Integration and Certification Center
9
The other test reports RSCMSTAC, RSCMSTAT and RSCMSTHS, which can also be
started within the test framework, are not relevant for the certification tests with
interface version 0045 and are only relevant for interface version 0046. Interface
version 0046 is only relevant for using the SAP Cache Server in conjunction with a
third-party content server to cache documents while they are being read accessed.
The test is carried out for documents with a maximum document size of 512 KB. These
tests are only for the interface tests.
Preparation
Version 0045 of the interface is supported. Your content repository needs to be
maintained with transaction OAC0. Use only two characters for ArchiveLink
Repositories. Security must be enabled and a certificate needs to be sent to the HTTP
Content Server either via transaction OAC0 or.with transaction SE37 by function call
SCMS_HTTP_PUT_CERT – single test:
Fill CREP_ID with Content Repository (e.g. KL)
Realize
Start all reports in a sequential order.
Check
Security is tested Are the Return Codes correct (marked green)? Handling of multiple documents Status of a document immediately after confirming the doc_Id
Further Hints
The header and body data must be returned correctly, look at the header return values. The Content Server must be able to process several HTTP calls simultaneously.
Starting the dedicated report in a separate mode. After the archived object has been deleted, the status of the object must be “unknown”.
Retrieval should no longer be possible. The document must be „online‟ immediately after confirmation of the doc_Id. The mCreate function expects the doc_Ids in the response in the same order as in the
request. Delete trace file with transaction SE38 and report RSHTTP40 (RFC-Destination –
SAPHTTPA, enable trace delete. Activation of RFC trace via transaction SM59. See OSS note 164203 for further information.
SAP AG SAP ArchiveLink / HTTP Content Server 6.20 Test Plan
SAP Integration and Certification Center
10
4.2 Test program Z_NEW_PRI_LIST
Description
The HTTP functions search, attrSearch (attribute search) and append of an archived
print list are tested. Also http-functions info, create and get (offset) are tested.
Preparation
Version 0045 of the interface is supported. Security must be enabled.
ICC provides a test print list with data and index file
ICC provides source code of Z_NEW_PRI_LIST
Realize
Start report Z_NEW PRI_LIST and fill in the following entries:
CONTREP: Your content repository id
PATH: Specify the full path including the file name of the print list data
component) in field PATH (e.g.
C:\temp\Storage\Printlist\000000490200001.MBS)
Use transaction OADR for retrieval – report name = Z_NEW_PRI_LIST
Mark displayed entry and go for free search and attribute search.
Check
Check status Display list Look whether attribute search button is enabled. Check free search, jump to the appropriate line in the list. Check attribute search, enter page number e.g. 12, and jump to the appropriate page in
the list. Please keep in mind the search range (cursor or global in list) Use different program-names and page numbers to search in the list Add note (free entry for text) – the http function append is checked
Further Hints
The test report source and the data and index file of the print list can be obtained from SAP as a part of the certification test kit
SAP ArchiveLink / HTTP Content Server 6.20 Test Plan SAP AG
SAP Integration and Certification Center
11
4.3 Test program Z_NEW_OUT_DOC
Description
Simple test for outgoing documents (document class is PDF). The goal of this test is to
guarantee a minimal performance of a HTTP content server. A content server which
does not reach this minimal goal of 5 documents per second will not pass the
certification test.
Preparation
Version 0045 of the interface is supported. Security must be enabled.
Customizing for archiving outgoing documents must be done.
Use BUS0815 as object type and Z_OUT_DOC as document type, these settings are already used within the report Z_NEW_OUTDOC. A customizing of the combination of object type BUS0815 and document type Z_OUT_DOC and your content repository in transaction OAC3 is required to store the corresponding documents in your content repository. The document type Z_OUT_DOC with document class PDF must be customized before with transaction OAC2.
Store a sample document (e.g. invoice.pdf) with transaction OAAD and use the content repository ID and the received document ID in the CONTREP and DOC_ID fields of your variant of the report Z_NEW_OUT_DOC.
Realize
Create a variant of report with the following entries in the appropriate fields:
CONTREP (see Content Repository),
DOC_ID (see preparation)
COUNT (default 1000)
Execute report Z_NEW_OUT_DOC with the variant in background task and check the
job processing time.
Check
At least 5 documents per second should be successfully stored in the content repository.
Check with transaction OAAD whether the documents have been created and can be accessed and displayed. SAP object identifier is “STRESS”. Check document status. Status should be ONLINE.
Further Hints
The test report source and the test document invoice.pdf can be obtained from SAP as a part of the certification test kit.
SAP AG SAP ArchiveLink / HTTP Content Server 6.20 Test Plan
SAP Integration and Certification Center
12
4.4 Single Tests
Description
The following http functions can be tested randomly for detailed analysis or
in case previous problems occurred. The following steps maybe used for
detailed investigation in any error situation.
Preparation
Use an archived document for testing.
Realize
Delete trace file with transaction SE38 and executing report RSHTTP40.
Use transaction SE37 (function call – single test) and use function group SCMS_HTTP
with the following function calls:
SCMS_HTTP_INFO
SCMS_HTTP_GET
SCMS_HTTP_DOC_GET_FILES
SCMS_HTTP_CREATE
SCMS_HTTP_APPEND
SCMS_HTTP_UPDATE
SCMS_HTTP_DELETE
SCMS_HTTP_SEARCH
SCMS_HTTP_PUT_CERT
SCMS_HTTP_SERVER_INFO
Look into the RFC trace for analysis.
Check
Return codes are checked for consistency.
SAP ArchiveLink / HTTP Content Server 6.20 Test Plan SAP AG
SAP Integration and Certification Center
13
Further Hints
Use undefined Archive
Use undefined document ids
Check proper return codes (see HTTP Content Server documentation)
Check document header
Check document body
Disable security and try to access document
Delete document and check status
SAP AG SAP ArchiveLink / HTTP Content Server 6.20 Test Plan
SAP Integration and Certification Center
14
Chapter 5 : OLE-2.0 Automation
Description
The following functions are tested:
OLE - single stage archiving (Archive from frontend)
OLE - single stage displaying (Display Stored Document)
Preparation
One ArchiveLink protocol for one content repository has to be customized with
transaction OAA3 and linked to the content repository with transaction OAC0. Within
the protocol definition for each relevant document class the communication type OPEN
(OLE) and OLE application has to be maintained for the functions “Display Stored
Document” and “Archive from frontend”. Within the application-definition (transaction
OAA4) the content repository supplier has to customize the methods and properties for
the corresponding ArchiveLink functions. An entry within transaction „SOLE‟ for the
OLE automation application has to be made as well.
An entry in transaction OAC3 has to be maintained for the combination of SAP
business object type, document type and content repository.
In transaction OAC2 a document type with the document class used in transaction
OAA3 has to be maintained.
Realize
Communication protocol and corresponding application has to be maintained for OLE Automation.
Further Hints
SAP ArchiveLink / HTTP Content Server 6.20 Test Plan SAP AG
SAP Integration and Certification Center
15
5.1 OLE – Single stage archiving in dialog
Description
A currently scanned document has to be archived via OLE.
Preparation
Within application-definition (transaction OAA4) the content repository supplier has to
customize methods and properties for the corresponding ArchiveLink function “Archive
from frontend”.
Realize
Fill the scan-dialog with at least one document (or a pipeline of document) and archive
this document in the content server via creating a document with transaction OAAD.
Check
The document should be archived in the content repository.
Via transaction OAAD the document should be found and the status should be
ONLINE.
Further Hints
SAP AG SAP ArchiveLink / HTTP Content Server 6.20 Test Plan
SAP Integration and Certification Center
16
5.2 OLE - single stage displaying of archived document
Description
The archived document from the single stage archiving in dialog should be displayed
via OLE Automation.
Preparation
Within application-definition (transaction OAA4) the content repository supplier has to
customize methods and properties for the corresponding ArchiveLink function “Display
Stored Document”.
Realize
Go to transaction OAAD and search for the previously archived document. The status
should be ONLINE. Display the document via OLE Automation.
Check
The document viewer must be started
The document must be displayed properly
Further Hints
SAP ArchiveLink / HTTP Content Server 6.20 Test Plan SAP AG
SAP Integration and Certification Center
17
Chapter 6 : Bar code BAPI - Confirmation of multiple barcodes
with BAPI_BARCODE_SENDLIST
Description
Test bar code sending with the BAPI method “BAPI_BARCODE_SENDLIST”.
Correct error handling by the archive system in situations when identical bar codes
entries have been sent again.
Preparation
Realize
Check
Further Hints
SAP AG SAP ArchiveLink / HTTP Content Server 6.20 Test Plan
SAP Integration and Certification Center
18
6.1 Test barcode send with the BAPI method
‘BAPI_BARCODE_SENDLIST’
Description
Test sending bar codes for already archived documents with the BAPI method
„BAPI_BARCODE_SENDLIST‟.
Preparation
Go to transaction OAM1. Go to Bar Codes – External. Select all open external bar
codes. Mark all entries and delete them.
Realize
Send several bar code entries to the SAP system via using the BAPI method
„BAPI_BARCODE_SENDLIST‟ according to the documentation of this method.
Check
Are the correct entries in the external barcode queue after calling
„BAPI_BARCODE_SENDLIST‟?
Is the table barcode_entrys filled in properly?
Is function „BAPI_BARCODE_SENDLIST‟ used? (transaction SMGW)
Further Hints
The new bar codes appear in transaction OAM1 under „Open external bar codes‟.
The table barcode_entrys must be filled properly, with unique bar code IDs and
document ids (left-justified).
The content repository identification must correspond to the declared identification.
Select one entry. Show detail and display the document from the content repository.
SAP ArchiveLink / HTTP Content Server 6.20 Test Plan SAP AG
SAP Integration and Certification Center
19
6.2 Correct error handling by the archive system
Description
Correct error handling by the content repository in case identical bar code entries have
been sent by the content repository.
Preparation
Keep several bar codes ready in the database.
Realize
Send the bar codes used in section 6.1 twice (bar codes must have identical: bar code,
content repository id and document id)
Check
Check proper error message handling (return code number 241 “No bar code entry
could be made” is to be expected from the BAPI call)
Further Hints
SAP AG SAP ArchiveLink / HTTP Content Server 6.20 Test Plan
SAP Integration and Certification Center
20
Chapter 7 : Get information for certificate
Description
The partner receives a test protocol. If certification is successful, issue of a certificate
and logo will be set in action.
Preparation
Realize
SAP certification employees:
1. Maintain the certification status in the partner database (PDB).
2. Issue certificate number (Partner Database).
The following information is required from the partner:
1. Exact product name and release
2. Exact name of partner company
3. Exact description of hardware platform
4. Operating systems and release
5. Exact description of the partner‟s or third party‟s trademark that is to be observed
Check
Further Hints
Contact info mailto: [email protected]