Con guringSAPR/3 forArchive Services forSAP - Dell EMC · PDF...

Conguring SAP R/3® for ArchiveServices for SAP®

Version 5.3 SP3September 2006

SAP®, SAP® R/3®, SAP NetWeaver®, SAP ArchiveLink®, ABAP™, BAPI® are trademarks or registered trademarks of SAP AG in Germanyand in several other countries.Copyright © 1994-2006 EMC Corporation. All rights reserved.

Table of Contents

Preface ........................................................................................................................... 7

Chapter 1 Introducing Archive Services for SAP ................................................... 11Overview ................................................................................................... 11Understanding the Archive Services for SAP architecture.............................. 12Supported SAP document formats............................................................... 13Understanding SAP and Archive Services for SAP terms............................... 13

Chapter 2 Conguring the ArchiveLink Interface for Archive Servicesfor SAP .................................................................................................. 17Overview ................................................................................................... 17oac0 — Defining a logical ArchiveID............................................................ 18oag1 – Configuring basic settings................................................................. 18oanr – Configuring number ranges .............................................................. 19oaqi - Creating queues ................................................................................ 19oaat - Scheduling jobs ................................................................................. 20spad – Configuring optical archives as output devices................................... 20sm50 – Verifying spool processes ................................................................. 21oaa3 – Configuring the SAP inline Print List viewer protocol ......................... 22

Chapter 3 Customizing SAP Document Classes .................................................... 25Overview ................................................................................................... 25oac0 – Configuring content repositories........................................................ 25sm59 – RFC destination archives.................................................................. 27sm59 - Testing connections ...................................................................... 29

oac2 - Defining document types................................................................... 30oac3 - Defining links ................................................................................... 30

Chapter 4 Testing the Archiving Process Using a Print List .................................. 33Overview ................................................................................................... 33Creating a document type in SAP ................................................................ 33Testing connection between SAP and Archive Services.................................. 34Archiving a Print List.................................................................................. 34Displaying the archived Print List in SAPGUI .............................................. 35Deleting archived and linked documents ..................................................... 36

Conguring SAP R/3® for Archive Services for SAP® 3

Table of Contents

List of Figures

Figure 1–1. Archive Services and SAP ............................................................................... 12

4 Conguring SAP R/3® for Archive Services for SAP®

Table of Contents

List of Tables

Table 1–1. Terms and definitions ..................................................................................... 13Table 2–1. Field descriptions of Change Output Device screen .......................................... 21Table 3–1. Field descriptions of Change Content Repositories screen ................................. 26Table 3–2. Field descriptions of New Entries table ............................................................ 31


Table of Contents


Preface

Purpose of this guideThis guide explains how to configure SAP to use Archive Services for SAP 5.3 SP3 (ArchiveServices 5.3 SP3.) It provides task-based instructions for configuring SAP, so that it workstogether with Archive Services.

Note: For the sake of brevity, throughout this document, Archive Services for SAP willbe referred to as Archive Services.

Intended audienceIn order to address the manuals to the correct audience, the roles of the users of themanuals have been defined as follows:

• System Administrator - This role covers users who install and configure ArchiveServices. The Archive Services application integrates Documentum and the SAP R/3system. As a result, system administrators must have experience with the softwareproducts listed in the “Software Requirements” section of the Archive Services forSAP Release Notes.

• Archive Services Administrator - This role covers users who manage Archive Servicesusing WebAdmin.

• Standard User - This role covers users who view documents using SAPGUI.This manual is intended for system administrators.

Revision historyThis section contains a description of this document’s revision history.

Revision history

Revision Date Description

September 2006 Initial publication of document forArchive Services for SAP 5.3 SP3


Preface

Organization of this guideThis guide contains the following chapters. The table below lists the information thatyou can expect to find in each.

Organization of this guide

Chapter Contents

Chapter 1, Introducing Archive Servicesfor SAP

Provides an overview of Archive Services.

Chapter 2, Configuring the ArchiveLinkInterface for Archive Services for SAP

Describes how to configure SAP fordocument, report, and data archiving.

Chapter 3, Customizing SAP DocumentClasses

Describes how to configure SAP forscanning.

Chapter 4, Testing the Archiving ProcessUsing a Print List

Describes how to test the archivingprocess using a Print List.

Typographic conventionsThis guide uses the following text conventions:

Typographic conventions used in this guide

Convention Description

> Represents a pop-up or pull-down menu.

<Text enclosed within angle brackets> Represents a variable name for which youmust provide a value, or a defined term.

Information in this fontRepresents code samples, user input, andcomputer output.

[] square brackets Used in method command syntaxspecifications, square brackets indicate anoptional argument.

{} curly brackets Used in method command syntaxspecifications, curly brackets indicate anoptional argument that can be repeatedmore than once.


Preface

Related documentationThis manual forms part of a documentation suite designed to support those who install,configure, and use Archive Services for SAP. The product and documentation suite canbe found on Documentum’s download center: https://documentum.subscribenet.com.

From Subscribenet, you can download the latest version of Archive Services for SAP andthe related documentation suite. To access the contents in Subscribenet, you will need toprovide the login credentials assigned to you when you first applied for access.

Note: Your login ID, by default, is your email address. If you cannot locate yourpassword, use the password finder at the bottom of the login page.

If you’re accessing Subscribenet for the first time, you will need to apply for access andobtain a user name and password. Refer to Applying for access.

Archive Services for SAP — Documentation suite

Title Description Target role

Archive Services for SAPRelease Notes

Provides an overviewof new and amendedfeatures, known bugs,limitations, miscellaneoustechnical notes, anddocumentation correctnessand clarifications.

Standard User, SystemAdministrator, SystemAdministrator (SAP),and Archive ServicesAdministrator

Archive Services for SAPrInstallation Guide

Provides the proceduresfor installing ArchiveServices.

System Administrator

Configuring SAP R/3 forArchive Services for SAP

Describes the configurationtasks that need to beperformed in SAP so thatSAP can communicate withArchive Services.

System Administrator(SAP)

Archive Services for SAPAdministration Guide

Describes how to configureArchive Services using theWebAdmin tool.

Archive ServicesAdministrator

Archive Services for SAPUser Guide

Describes how SAP usersview documents.

Standard User

Note: Archive Services extensively uses SAP’s ArchiveLink component. Please refer toSAP ArchiveLink’s documentation for information on how you can perform advancedtasks.


https://documentum.subscribenet.com

http://help.sap.com/saphelp_47x200/helpdata/en/5e/566039b85f9443e10000000a114084/frameset.htm

Preface

Applying for access

To apply for access to Support online:

1. In your Web browser, open http://www.documentum.com

2. Click the Support link.

3. Click the Request Access link.

4. Complete the form and send it.Documentum will respond to your request within two business days.

Accessing documentation online

Customers with a Software Support Agreement can read our product documentationat the Documentum Web site. You must have a valid user name and password, andAdobe Acrobat Exchange or Acrobat Reader installed on your system in order to viewthe documentation.

To access documents online:

1. In your Web browser, open http://www.documentum.com

2. Click the Support link.

3. Log on to the Support page.

4. Click the Documentation link.

5. Select how you want to display the documentation.

6. Click List.

7. Click the name of the document.

Purchasing bound paper manuals

Our product documentation is available for purchase as bound paper manuals. Toplace an order, call the Documentation Order Line at (925) 600-6666. You can pay witha purchase order, check, or credit card.


http://www.documentum.com

http://www.documentum.com

Chapter 1Introducing Archive Services for SAP

OverviewThe Archive Services application integrates the EMC Documentum content managementsystem with the SAP R/3 system. Based on SAP ArchiveLink 4.Version 5 HTTP interface,Archive Services provides a technology bridge between EMCDocumentum and SAP R/3.

Archive Services for SAP provides the following functionalities:

• Enables users to easily access and display documents stored in a Documentumrepository from within a variety of SAP modules.

• Links documents stored in Documentum to a variety of SAP objects.• Archives SAP data, reports, and documents through ArchiveLinkTM certified

interfaces in Documentum.This chapter covers the following topics:• Understanding the Archive Services for SAP architecture, page 12• Supported SAP document formats, page 13• Understanding SAP and Archive Services for SAP terms, page 13


Introducing Archive Services for SAP

Understanding the Archive Services for SAParchitectureFigure 1-1. Archive Services and SAP

Archive Services for SAP consists of the following components:

• HTTP archiving services

A server component that, using an HTTP connection to SAP, enables you to archivereports, data, incoming and outgoing documents from SAP to the Documentumrepository. Archive Services is a J2EE servlet that communicates with SAPArchiveLink. The reports and archived documents can later be retrieved and viewedthrough SAPGUI.

• RFC archiving services

A server component that enables you to archive reports, data, incoming andoutgoing documents from SAP to the EMC Documentum repository. The archived



reports and documents can later be retrieved and viewed through SAPGUI andDocumentum clients. This component uses SAP Remote Function Calls (RFCs) tocommunicate with SAP.

• WebAdmin

An administrative console that allows you to:

— Create, configure, and manage archives

— Manage certificates for the archive

— Create repository connections for Archive Services

— Configure document archival for Archive Services

Note: Please refer to the Archive Services for SAP Release Notes for detailed informationabout specific OS versions and supported software environments.

Supported SAP document formatsDocumentum supports the following SAP document classes/formats:

• Incoming or Scanned Documents (FAX class, Tiff format)• Outgoing Documents (OTF class, PDF format)• Archived Data (REO class, REO format)• Reports or Print Lists (ALF class, ALF format)

Understanding SAP and Archive Services for SAPterms

This section presents some terms and their definitions, as used in this guide.

Table 1-1. Terms and denitions

Term Definition

Archive Services for SAP Product that connects Documentum toSAP and vice versa.



Term Definition

HTTP Archiving Services Server component that, using an HTTPconnection to SAP, enables you to archivereports, data, incoming and outgoingdocuments from SAP to the Documentumrepository. HTTP Archiving Services is aJ2EE servlet that communicates with SAPArchiveLink. The reports and archiveddocuments can later be retrieved andviewed through .

RFC Archiving Server A server component that enables youto archive reports, data, incoming andoutgoing documents from SAP to theEMC Documentum repository. Thearchived reports and documents canlater be retrieved and viewed throughSAPGUI and Documentum clients. Thiscomponent uses SAP Remote FunctionCalls (RFCs) to communicate with SAP.

WebAdmin An administrative console that allows youto:• Create and manage archives• Manage certificates for the archive• Create repository connections forArchive Services for SAP

DMCL Documentum Client Library. Managescommunication between clients and EMCDocumentum Content Server. Contains alibrary of API calls that are used by clientsfor execution on the EMC DocumentumContent Server. All client requests to theEMC Documentum Content Server gothrough the DMCL.

ArchiveLink Cross-functional interface that is partof the SAP Basis System. ArchiveLinkhandles storing and retrieving documentsand data to and from a repository externalto SAP.



Term Definition

SAP DMS Document Management System that ispart of the SAP Basis System. Presentsa logical layer to integrate with externalsystems like AutoCAD or Documentum.Not directly related to ArchiveLink.

SAP PLM Product Life-Cycle Management (PLM).SAP PLM provides an integratedenvironment that ensures all peopleinvolved in product development,manufacturing, and service have quickand secure access to current information.It provides a set of BAPI calls thatcan be used by external systems likeDocumentum.

SAP Master Record A set of master data, such as customer orvendor data, which is used in the creationof SAP documents.

SAP GUI SAP Graphical User Interface. Graphicalmenu/screen tool that connects a client tothe SAP server.

Original Document Paper based version of a document.

Example 1-1.An invoice may consist of two sheets ofpaper received from a supplier. Paperdocuments are scanned in and stored aselectronic originals in Documentum.

SAP Document An electronic transactional record ofheader data and line items in SAP.


Chapter 2Conguring the ArchiveLink Interfacefor Archive Services for SAP

OverviewYou can store and retrieve documents, reports, and data through SAP ArchiveLink andDMS interfaces. Prior to running the Archive Services, the SAP R/3 system must also beconfigured. This chapter describes how to configure your R/3 ArchiveLink and otherrelated transactions through SAPGUI and the R/3 system.

Note: The configuration steps often reference direct transaction codes. These codesallow you to navigate directly to the correct configuration screen. Most of the systemconfiguration is performed in the SAP Implementation Guide for R/3 customizing (IMG).You can navigate to this screen using the following transaction code: spro.

When configuring Archive Services, you can configure either an HTTP-based ArchiveServer or an RFC (Remote Function Call) Archive Server.

Note: Documentum recommends that all new installations are based on the HTTP-basedArchive Server. The primary reason is that SAP will focus future development at theHTTP-based archive protocol.

The configuration steps are different for RFC and HTTP based archiving. Configurationsteps have been marked as being relevant only to RFC- or HTTP-based archiving.

The various configuration tasks that you have to perform are described in the followingsections:

• oac0 — Defining a logical ArchiveID, page 18• oag1 – Configuring basic settings, page 18• oanr – Configuring number ranges, page 19• oaqi - Creating queues, page 19• oaat - Scheduling jobs, page 20• spad – Configuring optical archives as output devices, page 20• sm50 – Verifying spool processes, page 21• oaa3 – Configuring the SAP inline Print List viewer protocol, page 22


Conguring the ArchiveLink Interface for Archive Services for SAP

oac0 — Dening a logical ArchiveIDNote: The name of the logical ArchiveID must be the same as the ArchiveID createdusing WebAdmin (refer to the Configuring, Viewing, and Editing Archives section of theArchive Services for SAP Administration Guide).

To dene a logical ArchiveID in SAP:

1. Execute the following transaction in the transaction code field: oac0.

2. In the Display Content Repositories: Overview page, click on any contentrepository (specifically whose Storage type is HTTP content server.

3. In the Display Content Repositories: Detail page, click the Display/Change iconThe Copy as ... button is now enabled.

4. Click the Copy as ... button.

5. Edit the Content Rep. field so that it’s the same as ArchiveID created usingWebAdmin (refer to the Configuring, Viewing, and Editing Archives section of theArchive Services for SAP Administration Guide).

6. In the Transfer drctry field, enter the directory path where SAP can write the PrintList till it is in the Storage Queue.

7. In the HTTP Server field, type your system name.

Note: You are recommended to type the IP address of your system in this field.

8. In the HTTP Script field, type the following:/archivelink/archivelink/<name-of-repository>

9. To save the logical ArchiveID configuration, choose Content Repository→Save.

oag1 – Conguring basic settingsYou must define the basic settings for ArchiveLink.

To congure the basic settings:

1. Execute the following transaction in in the transaction code field: oag1.

2. Ensure that the Deactivate Print List Management in DMS box is checked.

3. Save your changes.



oanr – Conguring number rangesYou must configure the number ranges for ArchiveLink.

To congure the number ranges:

1. Execute the following transaction in the transaction code field: oanr.

2. To edit the configuration, click on the Intervals button (marked with a pencil).The Display Number Range Intervals window opens.

3. Configure the Number Range 01 with default values.


oaqi - Creating queuesWhen Print Lists are archived, the SAP print spooler puts the document into theasynchronous queue. The scheduler then picks up the document and sends it to thearchive. The queue serves as a buffer for everything sent to an SAP archive. Otherqueues are used for outgoing documents and barcodes. These queues can be seen onthe ArchiveLink Monitor screen (transaction code: oam1). If this screen shows the wordMISSING instead of zeros, you must create queues and specify an administrator. Definean SAP user with the proper ArchiveLink administrator profile as the administrator forthis queues. Defining an administrator will automatically create the queues. Check thatthe queues have been created by reviewing transaction oam1.

To create queues:

1. Execute the following transaction in the transaction code field: oaqiThe SAP ArchiveLink: Create All Queues (CFBC, CARA, CGDA) screen appears.

2. Fill in all the options with ‘x’.

3. Enter a valid SAP login name in the Queue Administrator field.

4. Choose Program>Execute.

5. Click Cancel to exit this window.



oaat - Scheduling jobsThe SAP schedule job periodically checks the output queue and sends all the items inthe queues to the archive. You must configure the schedule job to successfully archivedocuments to an SAP archive.

To schedule a job:

1. Execute the following transaction in the transaction code field: oaat

2. Create a new job.

3. Type ILQBATCH in the ABAP Program field.

4. To verify that there are no errors, click Check.


6. Click Back to return to the Define Background Job window.

7. Click the Start Date button.

8. Set Start Time to Immediate.

9. Select the Periodic Job checkbox.

10. Click Period Values and specify an interval such as 20 minutes.This value should be determined by the following factors:• Frequency of archival• Time taken to archive your largest document; for example, your largest Print List

11. Save your changes

12. Click Exit.

spad – Conguring optical archives as outputdevices

An output device is the driver software for the logical output device which archivesdocuments using the ArchiveLink interface. To correctly archive a document to SAP,you must define the output device as an optical archive. Configuring an output deviceincludes defining the type, the device, the spool server, and so on. There should be onlyONE ARCH device; therefore, prior to defining a device with the ARCH short name, youshould delete any existing ARCH devices such as ARCHIXOS.

To congure an optical archive as the output device:

1. Start SAPGUI and connect to your R/3 server.



2. Execute the following transaction in the in the transaction code field: spad.

3. Click the Output Devices button.

4. Click the pencil button to edit settings.

Note: You can only have one printer and that printer must be named ARCH. Ifyou are already using a printer named ARCH you can either delete it or using theexisting ARCH device.

5. In case ARCH already exists, select device ARCH and click the Delete button.

6. Click the New Entries button to create a new output device.The Change Output Device screen is displayed.

7. Fill in the following information:

Table 2-1. Field descriptions of Change Output Device screen

Field name Value

Output Device ARCHIVE

Short Name ARCH

Device Type ARCHLINK

Spool Server Select spool server from drop down list.Usually there is only one spool serverlisted

Device Class Type A, for archive program

Access Method Fill I, for archive service

Location Fill Archive

Message Fill ArchiveLink Device

8. Click Enter and the dialog box changes.


sm50 – Verifying spool processesArchive Services uses the standard SAP print spooler to send reports to the ArchiveLinkqueue. To successfully archive a document, the print spooler must be running.

To verify if a spool process is running:

1. Execute the following transaction in the transaction code field: sm50.



2. Verify that a process named SPO is waiting or running.If you do not have a spool process running, contact your SAP system administrator.Starting a spool process usually involves restarting the SAP server.

oaa3 – Conguring the SAP inline Print Listviewer protocol

SAP R/3 includes a Print List viewing feature that allows you to view saved Print Lists,in SAPGUI, in their native ALF format. To view saved Print Lists in SAPGUI, you mustconfigure the protocol to support the viewer.

To congure the Print List viewer to display the Print Lists in SAPGUI:

1. In the transaction code field, execute the following transaction: oaa3.The SAP ArchiveLink: Communications interface administration page appears.

2. Click Create.The New Protocol dialog box appears.

Example 2-1.You may wish to define the protocol name as DCTMALF; this could refer to ArchiveServices with ALF Viewer.

3. Type version 0045 for HTTP-based archiving.

4. Save your changes.The Overview of a Protocol window appears, displaying your newly-definedprotocol.

5. Double-click Display Stored Document.The Overview of a Protocol window appears, showing a list of Document Classes.

6. Select the * row which indicates all document classes.

7. Click the pencil button.The Overview of a Protocol dialog box appears.

8. Type OPEN in the Communication Type field.

9. Press the [Enter] key.

10. Type DCTM in the Application field.

11. Click Continue.



12. In the Overview of a Protocol window showing the list of Document Classes, selectthe ALF document class.

13. Click the pencil button.The Overview of Protocol dialog box appears.

14. Type R/3 in the Communication Type field.

15. Press the [Enter] keyNo application is entered here.

16. Save your changes.You are returned to the Overview of a Protocol window.If you repeat step 4 and 11, you should see that the * document class and the ALFdocument class are indicated asMaintained Explicitly. All other document classesshould be indicated as Not Maintained Explicitly.


Chapter 3Customizing SAP Document Classes

OverviewThe following sections describe how to archive document classes from SAP. Thecustomization of each SAP setup is different depending on which document class thearchived document belongs to. The document classes are:

• ALF• FAX• OTF• REOFor all classes, you must configure, at least:

• oac0• oac2• oac3plus any specific customizations. These customizations are described in the followingsections:

• oac0 – Configuring content repositories, page 25• oac2 - Defining document types, page 30• oac3 - Defining links, page 30

oac0 – Conguring content repositoriesSAP allows you to define a content repository (previously known as a logical archive).This content repository is mapped to a Documentum archive via WebAdmin. TheDocumentum archive links to a set of rules such as content folders, Documentumdocument types, and so on in the Documentum repository. It is recommended thatyou store each document type in a separate archive. Using WebAdmin, you mustcreate a matching archive for each ArchiveID defined in SAP. This ArchiveID defineswhat actions (types, folders, retention, and so on) are applied on a SAP document whenit is archived. The following sections explain how to create an archive in SAP for eachrepresented document class.


Customizing SAP Document Classes

When configuring Archives, you can configure either an HTTP-based Archives or RFC(Remote Function Call) Archives. The configuration steps are different for RFC vs. HTTPbased archives. The configuration steps below have been listed as being relevant only toRFC- or HTTP-based archiving.

Note: Documentum recommends that all new installations are based on the HTTP-basedArchive Server. The primary reason is that SAP will focus future development at theHTTP-based archive protocol. However legacy RFC archives are still supported.

To dene an SAP content repository:

1. Execute the following transaction in the transaction code field: oac0

2. Click the pencil button to edit the table.

3. Click New Entries.

4. Select Full administration.The Change Content Repositories window opens.

5. Fill in the following information on the Change Content Repositories window:

Table 3-1. Field descriptions of Change Content Repositories screen

Field name Value

Content rep Specify a two-letter archive name. Forexample, AA

Description A meaningful name. For example, SAPPrint Lists (AA)

Storage Type Select HTTP or RFC

Protocol The previously configured protocol.

Version No. 0045 for HTTP or 0031 for RFC

Output Device ARCHIVE

6. Depending on whether you selected HTTP– or RFC–based archiving, typeappropriate values in the following fields:• For HTTP–based archiving:

— HTTP server

Type the hostname or IP address of the Archive Services host. If you use aserver name here, ensure that you can ping the server by name from theSAP server.

— Port Number

Type the port number being used (default is 80).



When using a default Tomcat configuration, this value is usually 8080.

— HTTP Script

Type the following value in this field: <virtual-directory>/archivelink/<repository>

<repository> is the name of the repository that you will be archiving contentinto. You must configure a corresponding archive in the Archive Services,using WebAdmin.

— Basic path

Type the file system path to the location where SAP will put archiveddocuments to be picked up by Archive Services.

— Arch path

Usually, the same as the Basic path.• For RFC–based archiving:

— RFC destination

Type the RFC destination that you created previously (refer to sm59 – RFCdestination archives, page 27).

— Basic path

Type the file system path to the location where SAP will put archiveddocuments to be picked up by Archive Services.

— Arch path

Usually, the same as the Basic path.Repeat this procedure to define the additional archives. You may use this procedure todefine any Documentum archives in SAP.

sm59 – RFC destination archivesThis section applies to RFC archiving only.

The SAP server considers Content Services for SAP an external RFC service or RFCdestination. The destination is identified with a symbolic name that was configured inDocumentum during the Content Services Archive Service installation. The name of theRFC destination must be unique for each repository/SAP client connection and identicalin the Content Services Archive Services and WebAdmin configurations.

To congure the RFC destination:

1. Start SAPGUI and connect to your R/3 server.



2. Execute the folliwng transaction: sm59.

3. Select the folder icon labeled TCP/IP connections.

4. Click Create.

5. Type in a name for the RFC destination.Use the naming conventions that uniquely identify Documentum Content ServicesArchive connections, such as <DCTMHOSTNAME>_<SAPSYSID_CLIENT>.You must use the same destination name configured in the WebAdmin.

Note: It is important that an exact match is made for the RFC connection tocommunicate. The ID is case sensitive and should not contain any spaces.

6. Type T in the Connection Type field.This specifies a TCP/IP connection.

7. Leave the Login parameters field blank.

8. Enter a description in the Description field.

9. Press [Enter].

10. Click Registration.START is not correct here and will invalidate the program ID entry.

11. Copy the RFC destination name into the Program ID field.Documentum recommends that you copy and paste the name between WebAdminand transaction code sm59 because the value of this field must correspond tothe configuration parameter RFC Program ID in the WebAdmin ArchiveLinkconfiguration tab RFC Destination parameter RFC Program ID.If you have not yet installed Content Services, you will need to make a note ofthis value so that you can configure your RFC destination in Content ServicesWebAdmin, and when the RFC services are installed on the Content Services hostserver. This value must be unique for each repository/SAP client connection whichis why the RFC destination name <DCTMHOSTNAME>_<SAPSYSID_CLIENT>is recommended.If two Content Services archive processes register under the same ID or name thesecond one connected receives all requests from SAP. The first process will notreceive an error message so it will wait indefinitely for RFC requests that never come.


13. Click Back to exit.You return to the RFC Destination window.

14. Verify that the parameters have not changed.This is a check to make sure the save operation succeeded.

15. Run the test described in sm59 - Testing connections, page 29.



sm59 - Testing connections

You must have created SM59 RFC destination, WebAdmin RFC config, and ContentServices RFC services via the Content Services installation program and started withthe SHARE user ID (refer to Installing Content Services for SAP) before you begin thisprocedure.

To test the ArchiveLink RFC connection to Content Services archive:

1. Switch on debugging before processes or services are started the first time by settingthe debug level:• Windows NT In the registry: Set HKEY_LOCAL_

MACHINE\SOFTWARE\Documentum\Doclink\Archive\Docbase\<Name_Of_Repository> to 3.

• UNIX In the dmal.ini file: Set the debug level to 3.2. Start your Content Services services or processes.

3. Start SAPGUI and connect to your R/3 system.

4. Execute the following transaction: sm59.A new window opens, listing the folder hierarchy.

5. Click on the plus symbol in front of the folder labeled TCP/IP Connections.A list of all RFC Destinations opens.

6. Double-click on the RFC destination that links SAP to the repository via ContentServices.

7. Click on Test Connection.A message appears on the status bar, stating that the connection is OK. A newwindow opens, displaying some performance figures (similar to ping).

8. Verify the connection by checking the Content Services log files.The following entries should appear in the log file on the Content Services serverwhich may be located in C:\temp\dmalaxxxxxx.log::>>> SAP open>>> Running RfcEnvironment>>> Running RfcInstallFunction>>> SAP event handler ok, entering event loop...>>> Calling RfcDispatch...>>> RfcDispatch returned 0>>> Calling RfcDispatch...>>> RfcDispatch returned 0>>> Calling RfcDispatch...>>> RfcDispatch returned 0>>> Calling RfcDispatch...:



Note: If you receive errors, check back through the configuration on SAP,WebAdmin, and the services or processes to verify there are no typos. You can turnon the RFC trace via the checkbox on SM59, and look for information in your logs.You may need to check the SAP gateway in your .../etc/services file.

oac2 - Dening document typesYou must select which document types you will be archiving, and correlate those to SAPdocument classes, such as FAX, ALF, OTF, and REO, The list of document types providedby SAP, when using transaction OAC2, are the templates to be used for categorizing yourSAP documents for archiving. You can customize the standard document types byusing the SAP XYZ naming conventions.• FAX documents are documents that will be scanned and linked to SAP.• ALF are reports produced and linked from SAP.• OTF are outgoing SAPSCRIPT documents produced and linked from SAP.• REO documents are data archive files which are compressed by the SAP ADK and

stored externally in that format.To dene document types for SAP:


2. If you are defining a new document type, select New Entries.You may also copy existing document types.

3. If you are modifying an existing document type, use Change and Details.

4. Enter information in the Description and Doc. class fields as appropriate for yourconfiguration.

5. When you have finished selecting document types, save your changes.

oac3 - Dening linksUsing the link table, you can categorize SAP documents to define what combination ofSAP object type (for example, SOOD) and SAP document type (for example, GENPRILIS)are stored and linked to which archive.

The SAP document type is linked to the SAP document class, previously known as SAPdocument type (for example, ALF, OTF, REO) which determines how the document isproduced and linked. For example, the ALF class refers to reports, FAX to scanneddocuments, and OTF to outgoing SAPSCRIPT documents.



To dene links:

1. Execute the following transaction in the transaction code field: oac3.The Display View “Links for Content Repositories": Overview screen appears.

2. Select Table View > Display -> Change.

3. Fill in the following information in the New Entries table:

Table 3-2. Field descriptions of New Entries table

Field name Value

Object Type Use legitimate object type such as SOODfor Print Lists, and BKPF for accountingdocuments

Document Type The SAP doc type as defined in OAC2above such as GENPRILIS

S (Status) Enter an “x” in this column

Arch. ID Enter the archive ID of a newly createdarchives for example, AA

Link Enter the name of the link tables wherelinks will be maintained. TOA01-TOA03

Ret Prd. 0



Chapter 4Testing the Archiving Process Using aPrint List

OverviewOnce you have completed the configuration procedures described previously in thisguide, you should test the archiving process by:

• defining an ArchiveID in WebAdmin.

For more information, refer to the Configuring, Viewing, and Editing Archives section ofthe Archive Services for SAP Administration Guide.

• testing the connection between SAP and Archive Services.• creating a document type in SAP.• archiving a Print List.• displaying the archived Print List in SAPGUI.This chapter contains the following topics:

• Creating a document type in SAP, page 33• Testing connection between SAP and Archive Services, page 34• Archiving a Print List, page 34• Displaying the archived Print List in SAPGUI, page 35• Deleting archived and linked documents, page 36

Creating a document type in SAPTo fully test the archival and retrieval cycle, a simple Print List can be configured byfollowing the instructions give below:

1. Execute the following transaction in the transaction code field: oac3.The Display View “Links for Content Repositories": Overview screen appears.

2. Select Table View > Display -> Change.

3. From the list, select any item with the ObjectType SOOD.


Testing the Archiving Process Using a Print List

4. Click the Copy As ... icon and execute.

5. In the page that appears, enter any piece of text starting with the alphabet Z in theDocument type field.Thus, Z<Your Text> will be the document type.

6. In the Storage system field, enter the name of the logical ArchiveID that you createdearlier (refer to oac0 — Defining a logical ArchiveID, page 18), where the documentswill be archived.


Testing connection between SAP and ArchiveServices


2. In the Display Content Repositories: Overview page, click on any contentrepository (specifically whose Storage type is HTTP content server).

3. In the Display Content Repositories: Detail page, click the Test connection button.An information messages appears at the bottom of the page, indicating that theconnection test has been successful.

Archiving a Print ListTo archive a Print List:

1. Execute the following transaction in the transaction code field: : f.21.

2. Click the Execute button.

3. In the List of Customer Open Items page that appears, select List>Print.The Print Screen List dialog box appears.

4. Click the Properties button.The Spool Request Attributes dialog box appears.

5. In the Parameters name column, click Output Options.

6. From the Storage Mode drop-down menu, select Archive only.

Note: Whenever you edit a parameter in this dialog box, we recommend that youcheck the Show Selected Print Parameters on Initial Screen checkbox. This ensuresthat the customized settings are available in the initial Print Screen List dialog box.



7. Verify that the Object Type and Document Type fields contain the correct values, asconfigured in the New Entries table (refer to oac3 - Defining links, page 30). Pickthe following values for example: SOOD GENPRILIS.If your Document Type is incorrectly configured, refer to the following proceduresfor configuring document types in SAP archives:oac2 - Defining document types,page 30 and oac3 - Defining links, page 30.

8. Type additional information in the Information field.This label may be anything you wish; for example, your initials.

9. Optionally, type a description of the Print List in the Text field.

10. In the Parameter name column, select General attributes > Time of printing.

11. From the Time of print drop-down list, select Print out immediately.

12. Click Continue in the Spool Request Attributes dialog box.

13. Click Continue in the Print Screen List dialog box.

14. To verify that the Print List is in the archiving queue, execute the followingtransaction in the transaction code field: oam1.The ArchiveLink Monitor screen appears.The Print List is now queued, waiting for the scheduler to pick it up and transfer itto the archive.oaat - Scheduling jobs, page 20, contains information about configuring theArchiveLink scheduler.

15. To accelerate the transfer of the Print List from the queue to the archive in therepository, click Storage Queue.The Queue: Content server (CARA) screen appears. You should now see an entryfor the newly-archived Print List in this screen.

16. To view the archiving parameter details, double-click the Print List entry.The Archiving request window opens.Verify that the details are correct

17. To archive the Print List in an archive located in a repository, click Execute.You should see a confirmation message that the queue has been processed.If no errors occur, you can continue testing by displaying the archived Print List.

Displaying the archived Print List in SAPGUITo display the newly-archived Print List in SAPGUI:

1. Execute the following transaction in the transaction code field: oadr.



2. To find a particular Print List, type appropriate search parameters in the appropriatefields.The ArchiveLink: Hit List for Stored Print Lists page appears.

3. Double-click an item in the list to select it.

4. Choose Print List>Display From Content Server.SAP executes the GET command to retrieve the document from the Documentumarchive. The retrieved document is displayed in SAPGUI and has the DocumentIDof the Print List in Documentum.

Deleting archived and linked documentsIn a repository, if you delete version 1.0 of a document that is linked to SAP or archivedfrom SAP, the link to SAP is also deleted. This is because the dm_relation object whichcreates the link to SAP is deleted when the parent object (which is always version 1.0)is deleted.

We recommend that you do not delete the original version of objects that are linked toSAP if you want to maintain their link to SAP. If you need to delete version 1.0 of adocument, but want to keep the link to SAP, then, after deleting the document, you mustrelink the object to SAP, outside of Archive Services.


Index

AAdministrative Console, 13ALF, 25, 30ALF class, 13ALF format, 13Archive Services, 7

configuring ArchiveLink for, 17Archive Services administrator, 7Archive Services for SAP, see Archive

Servicesdefined, 11

archived and deleting documents,deleting, 36

archived data, 13archived Print List

displaying in SAPGUI, 35ArchiveLink

configuring for Archive Services, 17ArchiveLink Monitor window, 35archiving

Print List, 34archiving process

testing using a Print List, 33Archiving request window, 35asynchronous queue, 19

Bbasic settings, configuring, 18

CChange Content Repositories window, 26class

ALF, 13FAX, 13OTF, 13REO, 13

configuration procedures, 27configuring

ArchiveLink for Archive Services, 17

basic settings, 18number ranges, 19optical archive as output device, 20SAP inline Print List viewer

protocol, 22connection

between SAP and Archive Services,testing of, 34

content repositories, 25Content Services server, 29creating

document type, 33queues, 19

Ddefining

document types, 30links, 31logical ArchiveID, 18

deletingarchived and linked documents, 36

displayingarchived Print List in SAPGUI, 35

documentincoming, 13outgoing, 13scanned, 13supported formats in SAP, 13

document classesALF, 25FAX, 25OTF, 25REO, 25

document formats, supported in SAP, 13document type

creating, 33document types

ALF, 30defining, 30FAX, 30


Index

OTF, 30REO, 30

Ff.21, 34FAX, 25, 30FAX class, 13format

ALF, 13PDF, 13REO, 13Tiff, 13

frequency of archival, 20

HHTTP Archiving Server, 12HTTP-based archiving, 22

Iintended audience, 7

Jjobs, scheduling, 20

Llinks

defining, 31logical ArchiveID

defining, 18

Nnumber ranges, configuring, 19

Ooaa3, 22oaat, 20oac0, 18, 25, 34oac2, 30oac3, 30, 33oadr, 35oag1, 18oam1, 19oanr, 19oaq1, 19oaqi, 19

ObjectType, SOOD, 33optical archive, configuring as output

device, 20organization of this guide, 8OTF, 25, 30OTF class, 13output device

configuring logical archive as, 20Overview of a Protocol window, 22

PPDF format, 13prerequisites

system administrator, 7Print List

archived, displaying in SAPGUI, 35archiving, 34testing archiving process using, 33

Print Lists, 13ALF class, 13ALF format, 13

purpose of the guide, 7

Qqueues, creating, 19

RREO, 25, 30REO class, 13REO format, 13Reports, see Print ListsRFC destination archive, 27

SSAP

print spooler, 21supported document formats in, 13transaction code, f.21, 34transaction code, oaa3, 22transaction code, oaat, 20transaction code, oac0, 18, 25, 34transaction code, oac2, 30transaction code, oac3, 30, 33transaction code, oadr, 35transaction code, oag1, 18transaction code, oam1, 19transaction code, oanr, 19


Index

transaction code, oaq1, 19transaction code, oaqi, 19transaction code, sm50, 21transaction code, spad, 20transaction code, spro, 17

SAP Document Classescustomizing, 25

SAP inline Print List viewer protocol,configuring, 22

SAPGUIArchiveLink Monitor window, 35Archiving request window, 35Change Content Repositories

window, 26displaying archived Print List in, 35Overview of a Protocol window, 22Queue Administrator field, 19Test connection button, 34

schedulingjobs, 20

sm50, 21SM59, 27, 29SOOD, ObjectType, 33spad, 20SPO process, 21spool process, 21spool processes, verifying, 21spro, 17standard user, 7supported document formats in SAP, 13

ALF class, 13ALF format, 13FAX class, 13OTF class, 13PDF format, 13REO class, 13REO format, 13Tiff format, 13

system administrator, 7prerequisites, 7

TTest connection button, SAPGUI, 34testing

connection between SAP and ArchiveServices, 34

testing archiving process using a PrintList, 33

testing the connection, 29Tiff format, 13transaction code

f.21, 34oaa3, 22oaat, 20oac0, 18, 25, 34oac2, 30oac3, 30, 33oadr, 35oag1, 18oam1, 19oanr, 19oaq1, 19oaqi, 19sm50, 21spad, 20spro, 17

Transfer drctry field, 18

Uueue Administrator field, 19user roles, 7

Vverifying, spool processes, 21version 0045, 22

WWebAdmin, 13


Con guringSAPR/3 forArchive Services forSAP - Dell EMC · PDF...

Documents

Transcript of Con guringSAPR/3 forArchive Services forSAP - Dell EMC · PDF...