Certification Suite BC-ILM 3

Master GuideCertification Suite ABAPDocument Version: 1.1 – 2016-06-27

PUBLIC

Certification Suite BC-ILM 3.0 ABAP

2PUBLIC© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Certification Suite BC-ILM 3.0Typographic Conventions

Typographic Conventions

Type Style Description

Example Words or characters quoted from the screen. These include field names, screen titles,pushbuttons labels, menu names, menu paths, and menu options.Textual cross-references to other documents.

Example Emphasized words or expressions.

EXAMPLE Technical names of system objects. These include report names, program names,transaction codes, table names, and key concepts of a programming language when theyare surrounded by body text, for example, SELECT and INCLUDE.

Example Output on the screen. This includes file and directory names and their paths, messages,names of variables and parameters, source text, and names of installation, upgrade anddatabase tools.

Example Exact user entry. These are words or characters that you enter in the system exactly asthey appear in the documentation.

<Example> Variable user entry. Angle brackets indicate that you replace these words and characterswith appropriate entries to make entries in the system.

EXAMPLE Keys on the keyboard, for example, F2 or ENTER .

Certification Suite BC-ILM 3.0Document History

PUBLIC© 2015 SAP SE or an SAP affiliate company. All rights reserved. 3

Document History

CautionBefore you start the implementation, make sure that you have the latest version of this document that isavailable on SAP Service Marketplace at http://service.sap.com/instguides.

Version Date Change

1.0 2015-09-25 Initial Delivery

1.1 2016-06-27 Additional Plug-ins added


Certification Suite BC-ILM 3.0Table of Contents

Table of Contents

1 Getting Started ........................................................................................................................ 71.1 About this Document ............................................................................................................................ 7

2 Certification Suite ABAP BC-ILM 3.0 Overview .....................................................................82.1 Software Units of Certification Suite ABAP BC-ILM 3.0 .................................................................... 82.2 Prerequisites .......................................................................................................................................... 82.3 Required Authorizations ....................................................................................................................... 9

3 Certification Suite Cockpit .................................................................................................... 103.1 Toolbar.................................................................................................................................................. 103.2 Left Panel (List of Plug-Ins for Execution) ......................................................................................... 103.3 Right Panel (List of Available Plug-Ins) ............................................................................................... 11

4 Execution Procedure .............................................................................................................. 124.1 Implementation Sequence................................................................................................................... 12

4.1.1 Variant Creation ................................................................................................................... 124.1.2 Certification Execution ........................................................................................................ 124.1.3 Display and Analysis of Results .......................................................................................... 12

5 Maintenance of Run ID........................................................................................................... 13

6 BC-ILM 3.0 Certification Plug-Ins ......................................................................................... 146.1 Acceptance Test ...................................................................................................................................14

6.1.1 Description............................................................................................................................146.1.2 Input Parameters and Setup ...............................................................................................146.1.3 Behavior ................................................................................................................................ 156.1.4 Expected Results .................................................................................................................. 15

7 Tester Plug-Ins ....................................................................................................................... 167.1 SAP ILM Storage - Simple Performance Test ....................................................................................16

7.1.1 Description............................................................................................................................167.1.2 Input Parameters and Setup ...............................................................................................167.1.3 Behavior ................................................................................................................................ 177.1.4 Expected Results .................................................................................................................. 17

7.2 SAP ILM Storage - Performance Test Loop - Small BLOBs .............................................................. 177.2.1 Description............................................................................................................................ 177.2.2 Input Parameters and Setup ............................................................................................... 177.2.3 Behavior ................................................................................................................................187.2.4 Expected Results ..................................................................................................................18

7.3 SAP ILM Storage - Performance Test Loop - Big BLOBs ..................................................................187.3.1 Description............................................................................................................................197.3.2 Input Parameters and Setup ...............................................................................................197.3.3 Behavior ................................................................................................................................197.3.4 Expected results ...................................................................................................................19

Certification Suite BC-ILM 3.0Table of Contents


7.4 Plug-in for Testing Framework Functionality ....................................................................................207.4.1 Description ...........................................................................................................................207.4.2 Input Parameters and Setup ..............................................................................................207.4.3 Behavior ...............................................................................................................................207.4.4 Expected Results ................................................................................................................. 21

7.5 Plug-in for Testing of Framework Functionality 2 ............................................................................. 237.5.1 Description ........................................................................................................................... 237.5.2 Input Parameters and Setup .............................................................................................. 237.5.3 Behavior ............................................................................................................................... 237.5.4 Expected Results ................................................................................................................. 23

7.6 Plug-in for Load Test............................................................................................................................ 247.6.1 Description ........................................................................................................................... 257.6.2 Input Parameters and Setup .............................................................................................. 257.6.3 Behavior ............................................................................................................................... 257.6.4 Expected Results ................................................................................................................. 25

7.7 Plug-in for Concurrent Load Measurement ....................................................................................... 257.7.1 Description ........................................................................................................................... 267.7.2 Input Parameters and Setup .............................................................................................. 267.7.3 Behavior ............................................................................................................................... 267.7.4 Expected Results ................................................................................................................. 27

7.8 Plug-in for Store Phase Simulation .................................................................................................... 277.8.1 Description ........................................................................................................................... 277.8.2 Input Parameters and Setup .............................................................................................. 277.8.3 Behavior ............................................................................................................................... 287.8.4 Expected Results ................................................................................................................. 28

7.9 Plug-in for Store Phase Simulation (Direct) ...................................................................................... 287.9.1 Description ........................................................................................................................... 297.9.2 Input Parameters and Setup .............................................................................................. 297.9.3 Behavior .............................................................................................................................. 307.9.4 Expected Results ................................................................................................................ 30

7.10 Plug-in for Attachment Simulation .................................................................................................... 307.10.1 Description ........................................................................................................................... 317.10.2 Input Parameters and Setup .............................................................................................. 317.10.3 Behavior ............................................................................................................................... 317.10.4 Expected Results ................................................................................................................. 32

7.11 Plug-in for Attachment Simulation (Direct) ...................................................................................... 327.11.1 Description ........................................................................................................................... 327.11.2 Input Parameters and Setup .............................................................................................. 337.11.3 Behavior ............................................................................................................................... 337.11.4 Expected Results ................................................................................................................. 33

7.12 Plug-in for SAP ArchiveLink Retention Propagation......................................................................... 337.12.1 Description ........................................................................................................................... 347.12.2 Input Parameters and Setup .............................................................................................. 347.12.3 Behavior ............................................................................................................................... 357.12.4 Expected Results ................................................................................................................. 35

8 References ............................................................................................................................. 36


Certification Suite BC-ILM 3.0Getting Started

Certification Suite BC-ILM 3.0Getting Started


1 Getting Started

1.1 About this Document

Purpose

This guide is the central starting point for the technical implementation of Certification Suite ABAP (BC-ILM 3.0).Use this guide to get an overview of the ABAP implementation of the BC-ILM 3.0 Certification Suite.


Certification Suite BC-ILM 3.0Certification Suite ABAP BC-ILM 3.0 Overview

2 Certification Suite ABAP BC-ILM 3.0Overview

Certification Suite ABAP BC-ILM 3.0 is an ABAP tool that should be able to replace all functions of theCertification Suite JAVA implemented solution in analyzing the BC_ILM 3.0 compatibility of storage solutions thatclaim to be “ILM-aware”.The designed ABAP tool consists of a framework and plug-ins (various sets of test cases) as separate units. Theframework builds, executes, and evaluates the test cases. Test cases are a key part of the tool and qualified tocertify the storage service. As of the creation of this document, ILM-aware storage implementation existsexclusively via WebDAV.

2.1 Software Units of Certification Suite ABAP BC-ILM 3.0

Two main reports have been delivered for interaction with the Certification Suite.· ILM Store: Certification Suite Cockpit (ILM_STOR_CS_COCKPIT) – Executes Certification Suite framework

(available for end users to perform general storage tests scenarios)· ILM Store: Test for Framework Functionality (ILM_STOR_CS_TEST) – Edit and maintain test RUNIDs and

results (at certification time this report is restricted and should be maintained in agreement with the SAPIntegration and Certification Center (ICC) personnel)

2.2 Prerequisites

Certification Suite is available for the ILM Store as of:· SAP NetWeaver 7.40 SP13· SAP NetWeaver 7.50 SP01

This documentation does not cover the enablement/installation support of the SAP ILM or the Storage andRetention Service. They are expected to be available and operational.

For more information, see http://service.sap.com/ilm

http://service.sap.com/ilm

Certification Suite BC-ILM 3.0Certification Suite ABAP BC-ILM 3.0 Overview


2.3 Required Authorizations

Authorization Object Activity Description

ILM Store: Authorization forCertification Suite(SILMSTORCS)

ExecuteMaintainRead

Plug-in executionVariant maintenanceDisplay of data

ILM Store: Authorization forCertification Suite Testers(SILMSTORCT)

Execute Tester plug-ins are displayed in the plug-in list and duringexecution

ILM Store: Authorization forAccess (SILMSTOR)

Execute Execution of processing in the SAP ILM Store

ILM Storage and RetentionService (S_ILM_SRS)

Execute Execution of processing in the Storage and RetentionService


Certification Suite BC-ILM 3.0Certification Suite Cockpit

3 Certification Suite Cockpit

You use the transaction ILM_STOR_CS_COCKPIT. You can prepare for the certification run and actual start ofcertification takes place. This screen consists of three main parts:· Toolbar· Left Panel (List of Plug-Ins for Execution)· Right Panel (List of Available Plug-Ins)

3.1 Toolbar

The toolbar consists of buttons that help in certification run actions and variant preparation actions. The buttonsare as follows:· Execute Listed Plug-ins: Creates a background job that executes all of the plug-ins within the created variant.

Once the run starts, the user is redirected to a screen that displays the certification run results. Eachexecution is logged and identified by a Run ID. The run ID is a unique identifier for the execution run. Youcannot delete or change the results after execution through the cockpit (RILM_STOR_CS_COCKPIT). You canmaintain the results only by using the report ILM Store: Test for Framework Functionality(RILM_STOR_CS_TEST).

· Display Run Statistics: Displays certification run results and provides search and filter functionalities foranalyzing the results.

· Create New Variant: Creates a new variant. This button is displayed only when the existing variant is alreadyloaded. It provides an option for creating a new variant.

· Choose Variant: Loads one of the existing variants stored in framework.· Save Variant: Saves the variant.· Variant Information: Displays information such as the variant name, description, created by, timestamp of

creation, last changed by, and timestamp when changed. This button is displayed only when the existingvariant is loaded.

3.2 Left Panel (List of Plug-Ins for Execution)

The execution of the listed plug-ins is performed in a top-down approach.This panel displays the plug-ins that are available for execution. You can perform the following operations on theplug-ins:· Move Down: Move selected plug-in down· Move Up: Move selected plug-in up· Move Bottom: Move selected plug-in to the end of plug-in list· Move Top: Move selected plug-in to the beginning of plug-in list

Certification Suite BC-ILM 3.0Certification Suite Cockpit


· Remove: Remove selected plug-in from plug-in list· Remove All: Remove all plug-ins

3.3 Right Panel (List of Available Plug-Ins)

This panel displays the list of available plug-ins. The list of available plug-ins contains two types of plug-ins: TheCertification plug-in and the Test plug-in. For the test plug-ins, authorization SILMSTORCT is needed and isintended for the system administrator. You can perform the following operations on the plug-ins:· Add Selected Plug-in: Adds selected plug-in into the Left Panel (List of Plug-Ins for Execution). You can also

drag and drop the plug-ins from the right panel to the left panel.· Information about Selected Plug-in: Displays information about the selected plug-in.


Certification Suite BC-ILM 3.0Execution Procedure

4 Execution Procedure

4.1 Implementation Sequence

Step Action

1 Variant Creation

2 Certification Execution

3 Display and Analysis of Results

4.1.1 Variant Creation

Creating a test variant is a major part of initiating a certification procedure. During variant creation you need toconsider an applicable scenario for the storage being used. Maintaining plug-in parameters is a core function thatallows users to maintain and control the test parameters for each plug-in (each test operation). This enables dateand time changes for retention control as well as allowing volume and size changes for basic and advanced loadtesting. All plug-ins are delivered with default values. You can enhance the parameters. This functionality issupported, and in some cases even required (retention date maintenance). The change in parameter values canresult in extended processing times.

4.1.2 Certification Execution

Certification execution is logged and identified by a run ID. A run ID is a unique identifier of the certificationexecution. When you execute the plug-ins by choosing the Execute Listed Plug-Ins button, a pop-up windowshows where you can provide the run ID. Once executed, the results cannot be deleted or changed in theCertification Suite cockpit (RILM_STOR_CS_COCKPIT). You can use the report RILM_STOR_CS_TEST tomaintain the results.

4.1.3 Display and Analysis of Results

You can display the results by loading and executing run ID and entering Display mode. The analysis of the resultsis supported and made easy by green and red lights indicating the success or failure of the individual scenariosand test cases. For a user friendly analysis, the Display Run Evaluation Data window lets you filter messages bytype. It also lets you expand and collapse folders by type. You can also navigate to the ILM Store's application log.

Certification Suite BC-ILM 3.0Maintenance of Run ID


5 Maintenance of Run ID

Once the run ID is executed, you cannot execute it again. The results cannot be deleted or changed afterexecution with the Certification Cockpit (RILM_STOR_CS_COCKPIT). You can use the reportRILM_STOR_CS_TEST to maintain the run ID. The use of this report is restricted to test executions of thecertification report and storage performance tests. You can select a run ID and perform the following actions:· Display Result· Start Run· Terminate Run· Delete a Run ID.


Certification Suite BC-ILM 3.0BC-ILM 3.0 Certification Plug-Ins

6 BC-ILM 3.0 Certification Plug-Ins

6.1 Acceptance Test

Type: Certification plug-in for BC-ILM 3.0Name: CL_ILM_STOR_CS_PLG_ATCoverage Area: This plug-in is executed using the SRS server.

Required Authorizations:

Authorization object Activity Description

SILMSTORCS ExecuteMaintainRead


SILMSTOR Execute Execution of processing in the SAP ILM Store

S_ILM_SRS Execute Execution of processing in SRS server

6.1.1 Description

The plug-in tests whether the Store and Storage and Retention Service accept and support:· Creation and access to collections, resources, and properties· Required character set· URI length· Auto naming of resources

6.1.2 Input Parameters and Setup

Mandatory Parameters:Archive Store Name [ARCHIVE_STORE]: You enter the technical name of the targeted archive store. Archivestore names are maintained in transaction ILMSTOREADM.Optional Parameters:Deletion Phase [DELETION_PHASE]: You use this as an indicator of the deletion phase when cleanup of residualstructures (collections, resources, and properties) is executed. This parameter expects a Boolean value:· ‘X’ – TRUE· Empty field/ FALSE

Certification Suite BC-ILM 3.0BC-ILM 3.0 Certification Plug-Ins


6.1.3 Behavior

One of the plug-in's tasks is to test the ability of a store to set an expiration date for collections and resources. Theexpiration date restricts the deletion of a bound object. The expiration date used within the plug-in has the relativevalue <tomorrow> so that a direct cleanup after execution of a plug-in is not possible. Therefore the plug-in has tobe executed in two waves:· Standard Run – The parameter DELETION_PHASE is initial· Deletion Run - Scheduled for the day after tomorrow (or later) – the parameter DELETION_PHASE is set to

‘X’

If an error occurs during a plug-in execution, cleanup is automatically triggered. The cleanup procedure is thesame as that used by the deletion run. If an error occurs after an expiration date is set, the cleanup will beunsuccessful. Therefore the deletion runs always have to be scheduled.

6.1.4 Expected Results

The acceptance test is passed if all function calls of the standard run phase are executed successfully.


Certification Suite BC-ILM 3.0Tester Plug-Ins

7 Tester Plug-Ins

7.1 SAP ILM Storage - Simple Performance Test

Type: ILM Store single performance testName: CL_ILM_STOR_CS_PLG_PF_SINGLECoverage Area: Certification via SRS client





SILMSTORCT Execute Tester plug-ins are displayed in the plug-in list and duringexecution


7.1.1 Description

The test is focused on the basic functionality of WebDAV commands for the ILM Store. It will create the collectionpath, store only one resource, read the resource and finally delete it.


Mandatory Parameters:Destination [RFC_DESTINATION]: RFC destination pointing to WebDAV-service of the ILM StoreOptional Parameters:· BLOB size in MB [BLOB_SIZE]: Size of the BLOB that will be sent to the ILM Store. The only permitted values

are 100, 200, 500, 700 and 1000 MB. The default value is 100 MB.· Resource counter [ILM_STOR_CS_PARAM_NAME]: Determines the name of the stored resource with pattern

“res_<resource_counter>.bin”. This can be any integer value, 999 being the highest number. The defaultvalue is 1.



7.1.3 Behavior

If an error is raised in the plug-in run then deletion is executed in an emergency teardown.


The test has to be finished without errors. This means all WebDAV requests have to be executed successfully.There is no time limit for test execution.

7.2 SAP ILM Storage - Performance Test Loop - Small BLOBs

Type: ILM Store performance testName: CL_ILM_STOR_CS_PLG_PF_R_SMALLCoverage Area: Certification via SRS client







7.2.1 Description

The test is focused on the write/read performance of small resources via WebDAV to the ILM Store. It will createthe collection path, write the desired count of resources, read resources, and finally delete them.


Mandatory Parameters:Destination [RFC_DESTINATION]: RFC destination pointing to the WebDAV-service of the ILM Store



Optional Parameters:· BLOB size in kB [BLOB_SIZE]: Size of the BLOB that will be stored in the ILM Store. The only permitted values

are 100, 500 and 1024 kB. The default value is 100 kB.· Number of Retries (Max. 999) [RETRIES]: Determines the number of stored resources with the pattern

“res_<iteration>.bin”. This can be any integer value, 999 being the highest number. The default value is 1.

7.2.3 Behavior



The test has to be finished without errors. This means that all WebDAV requests have to be executed successfully.There is no time limit for test execution.

7.3 SAP ILM Storage - Performance Test Loop - Big BLOBs

Type: ILM Store performance testName: CL_ILM_STOR_CS_PLG_PF_R_BIGCoverage Area: Certification via SRS client









7.3.1 Description

The test is focused on write/read performance of big resources via WebDAV to ILM Store. It will create thecollection path, write the desired count of resources, read resources, and finally delete them. Running this testcan consume huge amounts of memory on the application server and massively reduce the DB size for a shortperiod of time.


Mandatory Parameters:Destination [RFC_DESTINATION]: RFC destination pointing to WebDAV-service of ILM StoreOptional Parameters:· BLOB size in MB [BLOB_SIZE]: The size of the BLOB that will be stored in the ILM Store. The only permitted

values are 100, 250 and 500 MB. The default value is 100 MB. The setup of this value is limited by the setup ofthe application server memory and the maximum allowed HTTP request size on the client and ILM Storeserver.

· Number of Retries (Max. 999) [RETRIES]: Determines number of stored resources with pattern“res_<iteration>.bin”. This can be any integer value, 999 being the highest number. The default value is 1.

7.3.3 Behavior


7.3.4 Expected results

The test has to be finished without errors. This means that all WebDAV requests have to be executed successfully.There is no time limit for test execution.



7.4 Plug-in for Testing Framework Functionality

Type: Certification Suite Framework testName: CL_ILM_STOR_CS_PLUGIN_TESTCoverage Area: Certification Suite functionality for plug-ins






7.4.1 Description

The test is focused on the validation of the functionality of the CS framework provided for plug-in runs. It tests thecorrect run of plug-in phases, evaluation of functionality, and message processing.


Mandatory Parameters:Simulate exception in SID [RAISE_EXCEPTION_IN]: Start ID where you simulate raising of exception. If SIDdoesn’t exist during run then the exception will not be raised. Default value is 0.Optional Parameters:· Duration of setup phase [s] [SETUP_DURATION]: This determines how long the setup phase of the plug-in

should run. The default value is 1 second.· Duration of execute phase [s] [EXECUTE_DURATION]: This determines how long the execute phase of the

plug-in should run. The default value is 1 second.· Duration of execute phase [s] [TEARDOWN_DURATION]: This determines how long the teardown phase of

the plug-in should run. The default value is 1 second.· Duration of emergency cleanup [s] [EMERGENCY_CLEANUP]: This determines how long the emergency

cleanup of the plug-in should run. The default value is 1 second.

7.4.3 Behavior

In each phase, a test of the plug-in is executed to test all possible evaluation functions of the framework.




When finished, the test displays the results for each of these phases: Startup, Execution, and Teardown. There isno time limit for test execution.



7.5 Plug-in for Testing of Framework Functionality 2

Type: Certification Suite Framework testName: CL_ILM_STOR_CS_PLUGIN_TEST2Coverage Area: Certification Suite result view functionality





SILMSTORCT Execute Tester plug-ins are displayed in plug-in list and duringexecution

7.5.1 Description

The test is focused on the validation of the Certification Suite's result view. It tests the correct representation ofmessages in the result tree.


Optional Parameters:· Simulate exception in SID [RAISE_EXCEPTION_IN]: Start ID where you simulate raising of exception. If the

SID doesn’t exist during the run then the exception will not be raised. The default value is 0.· Number of result repetitions [TEST_CASE_COUNT]: Number indicates how many times the test with all

possible results should be repeated. The default value is 10.

7.5.3 Behavior

In each phase, a test of the plug-in is executed to test all possible output results of the CS framework.


The test has to be finished without errors. There is no time limit for test execution.



7.6 Plug-in for Load Test

Type: Certification Suite Framework testName: CL CL_ILM_STOR_CS_PLG_LTCoverage Area: Certification Suite result view functionalityRequired Authorizations:








7.6.1 Description

The plug-in tests if the Store and SRS can handle big load of data in appropriate time. You cantest the following waves of data load:· One time 500 MB resource· 10000 times 100KB resource· 100000 times 100KB resourceNote: Each resource is deleted right after it has been written to ILM Store by PUT method. Only duration of thewrite operation is measured. Every test deletes its collection after the PUT method has been executed (delayed by30sec).


Mandatory Parameter:Archive Store Name [ARCHIVE_STORE]: Indicates technical name of targeted archive store. Archive store namesare maintained in the transaction ILMSTOREADM.

7.6.3 Behavior

Each time the plugin is executed a cleanup function is triggered. The plugin expects that thereare no residual structures from a previous plugin execution otherwise it ends with an error.If an error occurs during a plugin execution cleanup is automatically triggered.


The acceptance test is passed if all function calls of the plugin run are executed successfully andalso the test cases are finished within the following time ranges:· One time 500 MB resource is executed in one minute· 10000 times 100KB resource is executed in 10 minutes· 100000 times 100KB resource is executed in 100 minutes

7.7 Plug-in for Concurrent Load Measurement

Type: Certification Suite Framework test



Name: CL CL_ILM_STOR_CS_PLG_CLM

Coverage Area: Certification Suite result view functionality






7.7.1 Description

This plug-in is executed using the SRS client. The plugin tests if the archive store can assure anappropriate data throughput. It executes the tasks and iterations in parallel.


Mandatory Parameter:· RFC Destination [RFC_DESTINATION]: RFC destination pointing to the WebDAV-service of the ILM Store.· Concurrent Tasks [CONCURRENT_TASKS]: Number of concurrent tasks· Iterations [ITERATIONS]: Number of iterations per operation PUT, GET and DELETE· Content Size [kB] [CONTENT_SIZE]: The size of the content in kilobytes that is written into a Store by each

PUT operation

7.7.3 Behavior

After each plugin run a cleanup function is triggered. The plugin expects that there are noresidual structures from a previous plugin run otherwise it ends with an error. If an error occursduring a plugin execution cleanup is automatically triggered.

Recommendation: You need to consider the available system resources prior to execution and scheduleyour execution for a time when the base load is low or maintain your configuration accordingly to enablehigher workload as needed. For example, check the available number of maximum background jobs.




The KPI is the time it takes for each operation (for example, PUT or GET / GET RANGE)averaged across all tasks. The mandatory KPI in this case for each operation is 10 MB/second.

7.8 Plug-in for Store Phase Simulation

Type: Certification Suite Framework testName: CL CL_ILM_STOR_CS_PLG_SPSCoverage Area: Certification Suite result view functionality







7.8.1 Description

This plug-in is executed using the SRS server.This is a simulation of the ILM store phase to evaluate how long a predefined store process forarchiving files would take. The test runs follow this sequence:· To create collections and resources· To set the ILM properties (for example, expiration dates) on the created collections


Mandatory Parameter:Archive Store Name [ARCHIVE_STORE]: You enter the technical name of the targeted archive



store. Archive store names are maintained in transaction ILMSTOREADM.Optional Parameters:Deletion Phase [DELETION_PHASE]: You use this as an indicator of the deletion phase whencleanup of residual structures (collections, resources, and properties) is executed. This parameterexpects a Boolean value:· ‘X’ – TRUE· SPACE - FALSE· Empty field/ FALSE

7.8.3 Behavior

One of the plug-in's tasks is to test the ability of a store to set an expiration date for collectionsand resources. The expiration date restricts the deletion of a bound object. The expiration dateused within the plug-in has the relative value <tomorrow> so that a direct cleanup after executionof a plug-in is not possible. Therefore the plug-in has to be executed in two waves:· Standard Run – The parameter DELETION_PHASE is initial· Deletion Run - Scheduled for the day after tomorrow (or later) – the parameter DELETION_PHASE is set to ‘X’

If an error occurs during a plug-in execution, cleanup is automatically triggered. The cleanupprocedure is the same as that used by the deletion run. If an error occurs after an expiration dateis set, the cleanup will be unsuccessful. Therefore the deletion runs always have to be scheduled.


The mandatory KPI for the entire process is 5 seconds.

7.9 Plug-in for Store Phase Simulation (Direct)

Type: Certification Suite Framework testName: CL CL_ILM_STOR_CS_PLG_SPS_DIRECTCoverage Area: Certification Suite result view functionality









7.9.1 Description


Note: The test is directly executed on the store bypassing SRS.


Mandatory Parameters:RFC Destination [RFC_DESTINATION]: RFC destination pointing to WebDAV-service of theStore.Optional Parameters:Deletion Phase [DELETION_PHASE]: You use this as an indicator of the deletion phase whencleanup of residual structures (collections, resources, and properties) is executed. This parameterexpects a Boolean value:· ‘X’ – TRUE· SPACE - FALSE· Empty field/ FALSE



7.9.3 Behavior

User can test the ability of a store to set an expiration date for collections and resources. Theexpiration date restricts the deletion of a bound object. The expiration date used within the plug-in has the relative value <tomorrow> so that a direct cleanup after execution of a plug-in is notpossible. Therefore the plug-in has to be executed in two waves:· Standard Run – The parameter DELETION_PHASE is initial· Deletion Run - Scheduled for the day after tomorrow (or later) – the parameter DELETION_PHASE is set to ‘X’




7.10 Plug-in for Attachment Simulation

Type: Certification Suite Framework testName: CL CL_ILM_STOR_CS_PLG_ASCoverage Area: Certification Suite result view functionality









7.10.1 Description

This plug-in is executed using the SRS server. It simulates the retention propagation process forattachments. The test runs follow this sequence:· To create collections and resources· To set the ILM properties (for example, al* properties) on the created resources

Note: The actual propagation of the retention to archive link documents is not consideredbecause based on the certification specification, retention constraint cannot be applied to aphysical archive Link document when the reference is not valid. The test provides the value0000000000000000000000000000000000000000 for the property al_doc_id, which does notpoint to any actual document.


Mandatory Parameters:Archive Store Name [ARCHIVE_STORE]: Indicates the technical name of targeted archivestore. Archive store names are maintained in transaction ILMSTOREADM.Optional Parameters:Deletion Phase [DELETION_PHASE]: You use this as an indicator of the deletion phase whencleanup of residual structures (collections, resources, and properties) is executed. This parameterexpects a Boolean value:· ‘X’ – TRUE· SPACE - FALSE· Empty field/ FALSE

7.10.3 Behavior

One of the plug-in's tasks is to test the ability of a store to set an expiration date for collectionsand resources. The expiration date restricts the deletion of a bound object. The expiration dateused within the plug-in has the relative value <tomorrow> so that a direct cleanup after executionof a plug-in is not possible. Therefore the plug-in has to be executed in two waves:· Standard Run – The parameter DELETION_PHASE is initial· Deletion Run - Scheduled for the day after tomorrow (or later) – the parameter DELETION_PHASE is set to ‘X’

If an error occurs during a plug-in execution, cleanup is automatically triggered. The cleanupprocedure is the same as that used by the deletion run. If an error occurs after an expiration dateis set, the cleanup will be unsuccessful. Therefore the deletion runs always have to be scheduled





7.11 Plug-in for Attachment Simulation (Direct)

Type: Certification Suite Framework testName: CL CL_ILM_STOR_CS_PLG_AS_DIRECTCoverage Area: Certification Suite result view functionality







7.11.1 Description


Note: The test is directly executed on the store bypassing SRS.The actual propagation of the retention to ArchiveLink documents is not considered, because,based on the certification specification, retention constraint cannot be applied to a physicalarchive link document when the reference is not valid. The test provides the value0000000000000000000000000000000000000000 for the property al_doc_id, which does notpoint to any actual document




Mandatory Parameters:RFC Destination [RFC_DESTINATION]: RFC destination pointing to WebDAV-service of theStore.Optional Parameters:Deletion Phase [DELETION_PHASE]: You use this as an indicator of the deletion phase whencleanup of residual structures (collections, resources, and properties) is executed. This parameterexpects a Boolean value:· ‘X’ – TRUE· SPACE - FALSE· Empty field/ FALSE

7.11.3 Behavior

One of the plug-in's tasks is to test the ability of a store to set an expiration date for collectionsand resources. The expiration date restricts the deletion of a bound object. The expiration dateused within the plug-in has the relative value <today> so that a direct cleanup after execution ofa plug-in is not possible. Therefore the plug-in has to be executed in two waves:· Standard Run – The parameter DELETION_PHASE is initial· Deletion Run - Scheduled for the next day (or later) – the parameter DELETION_PHASE is set to ‘X’




7.12 Plug-in for SAP ArchiveLink Retention Propagation

Type: Certification Suite Framework testName: CL CL_ILM_STOR_CS_PLG_RPCoverage Area: Certification Suite result view functionality









7.12.1 Description

This plug-in is executed using the SRS server. You can use this to test the enforcement ofarchive link retention requirements. The test consists of two test cases:· ILM Retention Management scenario· System decommissioning scenario


Mandatory Parameters:· Archive Store Name [ARCHIVE_STORE]: Indicates the technical name of targeted archive store. Archive store

names are maintained in transaction ILMSTOREADM.· Content repository [AL_CREP_ID]: Content Repository ID. The IDs are maintained using the transaction

OAC0.· SAP ArchiveLink: System ID [AL_SID]: ID of a system where the specified content repository ID is registered.· SAP ArchiveLink: Document ID for _1.bin [AL_DOC_ID_1]· SAP ArchiveLink: Object ID for _1.bin [AL_OBJ_ID_1]· SAP ArchiveLink: Document ID for _2.bin [AL_DOC_ID_2]· SAP ArchiveLink: Object ID for _2.bin [AL_OBJ_ID_2]

Optional Parameters:· Decommissioning Scenario Indicator (yes = ‘X’) [DECOMISSIONING]· Phase [PHASE]: This indicates the type of an execution phase type. This parameter expects one of the

following values:o ‘S’ – Standard phase: Standard execution of selected scenario



o ‘L’ – Legal hold lifting phase: Legal hold that is set during the standard phase (‘S’) is lifted. It is importantto specify an URI of the target resource _1.bin. The target URI can be found within evaluation results of thestandard phase.

o ‘D’– Deletion phase: Cleanup of residual structures (collections, resources and properties)· URI [URI]: Allows you to specify an URI of a collection or a resource which is required for the legal hold lifting

phase.

Environmental prerequisites· SAP system with SAP NetWeaver 7.40 SPS 13/ 7.50 SPS 01 or higher Application Server ABAP· Storage system with SAP Archive Link-Interface BC-HCS 6.20 and WebDAV-Interface BC-ILM 3.0.· Content Repository of type “HTTP Content Server” that is customized in the SAP system so that it can be

used to store Archive Link documents in your storage system (from here on known as ZK).

7.12.3 Behavior

The ILM Retention Management scenario and System Decommissioning scenarios requiremanual preparation steps. The outcome of the preparation phase is a structure of collections andresources with setup properties for retention enforcement.

One of the plug-in's tasks is to test the ability of a store to set an expiration date for collectionsand resources. The expiration date restricts the deletion of a bound object. The expiration dateused within the plug-in has the relative value <tomorrow> so that a direct cleanup after executionof a plug-in is not possible. Therefore the plug-in has to be executed in two waves:· Standard Run – The parameter PHASE is set to 'S'.· Legal Hold Lifting Run - The parameter PHASE is set to 'L'.· Deletion Run - Scheduled for the day after tomorrow – The parameter PHASE is set to ‘D’



No collection / resource can be deleted while it has assigned a valid retention policy (expirationdate or legal hold).


Certification Suite BC-ILM 3.0References

8 References

References

The following table lists all of the documents mentioned in this Master Guide.

Title

WebDAV Storage Interface for SAPNetWeaver Information LifecycleManagement - (BC-ILM)

ILM Store Help portal documentation

ILM Store Business FunctionDocumentation

http://scn.sap.com/docs/DOC-8734

http://help.sap.com/saphelp_nw74/helpdata/en/27/017835919640619f07e7fc3e6ef599/frameset.htm

http://help.sap.com/erp2005_ehp_07/helpdata/en/1a/741c5219609b33e10000000a44538d/content.htm?frameset=/en/a3/c0c8f9eff344008e6fad1744b13174/frameset.htm&current_toc=/en/a3/c0c8f9eff344008e6fad1744b13174/plain.htm&node_id=15

www.sap.com/contactsap

© 2015 SAP SE or an SAP affiliate company. All rights reserved.No part of this publication may be reproduced or transmitted in anyform or for any purpose without the express permission of SAP SEor an SAP affiliate companySAP and other SAP products and services mentioned herein as wellas their respective logos are trademarks or registered trademarks ofSAP SE (or an SAP affiliate company) in Germany and othercountries. All other product and service names mentioned are thetrademarks of their respective companies. Please seewww.sap.com/corporate-en/legal/copyright/index.epx#trademarkfor additional trademark information and notices.

Material Number:

http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark

Certification Suite BC-ILM 3

Documents

Transcript of Certification Suite BC-ILM 3