Con guring SAP R/3 for Archive Services for SAP

Transcription

1 Con guring SAP R/3 for Archive Services for SAP Version 5.3 SP3 September 2006

2 SAP, SAP R/3, SAP NetWeaver, SAP ArchiveLink, ABAP, BAPI are trademarks or registered trademarks of SAP AG in Germany and in several other countries. Copyright EMC Corporation. All rights reserved.

3 Table of Contents Preface... 7 Chapter 1 Introducing Archive Services for SAP Overview Understanding the Archive Services for SAP architecture Supported SAP document formats Understanding SAP and Archive Services for SAP terms Chapter 2 Con guring the ArchiveLink Interface for Archive Services for SAP Overview oac0 Defining a logical ArchiveID oag1 Configuring basic settings oanr Configuring number ranges oaqi - Creating queues oaat - Scheduling jobs spad Configuring optical archives as output devices sm50 Verifying spool processes oaa3 Configuring the SAP inline Print List viewer protocol Chapter 3 Customizing SAP Document Classes Overview oac0 Configuring content repositories sm59 RFC destination archives sm59 - Testing connections oac2 - Defining document types oac3 - Defining links Chapter 4 Testing the Archiving Process Using a Print List Overview Creating a document type in SAP Testing connection between SAP and Archive Services Archiving a Print List Displaying the archived Print List in SAPGUI Deleting archived and linked documents Con guring SAP R/3 for Archive Services for SAP 3

4 Table of Contents List of Figures Figure 1 1. Archive Services and SAP Con guring SAP R/3 for Archive Services for SAP

5 Table of Contents List of Tables Table 1 1. Terms and definitions Table 2 1. Field descriptions of Change Output Device screen Table 3 1. Field descriptions of Change Content Repositories screen Table 3 2. Field descriptions of New Entries table Con guring SAP R/3 for Archive Services for SAP 5

6 Table of Contents 6 Con guring SAP R/3 for Archive Services for SAP

7 Preface Purpose of this guide This guide explains how to configure SAP to use Archive Services for SAP 5.3 SP3 (Archive Services 5.3 SP3.) It provides task-based instructions for configuring SAP, so that it works together with Archive Services. Note: For the sake of brevity, throughout this document, Archive Services for SAP will be referred to as Archive Services. Intended audience In order to address the manuals to the correct audience, the roles of the users of the manuals have been defined as follows: System Administrator - This role covers users who install and configure Archive Services. The Archive Services application integrates Documentum and the SAP R/3 system. As a result, system administrators must have experience with the software products listed in the Software Requirements section of the Archive Services for SAP Release Notes. Archive Services Administrator - This role covers users who manage Archive Services using WebAdmin. Standard User - This role covers users who view documents using SAPGUI. This manual is intended for system administrators. Revision history This section contains a description of this document s revision history. Revision history Revision Date September 2006 Description Initial publication of document for Archive Services for SAP 5.3 SP3 Con guring SAP R/3 for Archive Services for SAP 7

8 Preface Organization of this guide This guide contains the following chapters. The table below lists the information that you can expect to find in each. Organization of this guide Chapter Chapter 1, Introducing Archive Services for SAP Chapter 2, Configuring the ArchiveLink Interface for Archive Services for SAP Chapter 3, Customizing SAP Document Classes Chapter 4, Testing the Archiving Process Using a Print List Contents Provides an overview of Archive Services. Describes how to configure SAP for document, report, and data archiving. Describes how to configure SAP for scanning. Describes how to test the archiving process using a Print List. Typographic conventions This 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> Information in this font Represents a variable name for which you must provide a value, or a defined term. Represents code samples, user input, and computer output. [] square brackets Used in method command syntax specifications, square brackets indicate an optional argument. {} curly brackets Used in method command syntax specifications, curly brackets indicate an optional argument that can be repeated more than once. 8 Con guring SAP R/3 for Archive Services for SAP

9 Preface Related documentation This 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 can be found on Documentum s download center: From Subscribenet, you can download the latest version of Archive Services for SAP and the related documentation suite. To access the contents in Subscribenet, you will need to provide the login credentials assigned to you when you first applied for access. Note: Your login ID, by default, is your address. If you cannot locate your password, 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 and obtain a user name and password. Refer to Applying for access. Archive Services for SAP Documentation suite Title Description Target role Archive Services for SAP Release Notes Archive Services for SAPr Installation Guide Configuring SAP R/3 for Archive Services for SAP Provides an overview of new and amended features, known bugs, limitations, miscellaneous technical notes, and documentation correctness and clarifications. Provides the procedures for installing Archive Services. Describes the configuration tasks that need to be performed in SAP so that SAP can communicate with Archive Services. Standard User, System Administrator, System Administrator (SAP), and Archive Services Administrator System Administrator System Administrator (SAP) Archive Services for SAP Administration Guide Archive Services for SAP User Guide Describes how to configure Archive Services using the WebAdmin tool. Describes how SAP users view documents. Archive Services Administrator Standard User Note: Archive Services extensively uses SAP s ArchiveLink component. Please refer to SAP ArchiveLink s documentation for information on how you can perform advanced tasks. Con guring SAP R/3 for Archive Services for SAP 9

10 Preface Applying for access To apply for access to Support online: 1. In your Web browser, open 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 documentation at the Documentum Web site. You must have a valid user name and password, and Adobe Acrobat Exchange or Acrobat Reader installed on your system in order to view the documentation. To access documents online: 1. In your Web browser, open 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. To place an order, call the Documentation Order Line at (925) You can pay with a purchase order, check, or credit card. 10 Con guring SAP R/3 for Archive Services for SAP

11 Chapter 1 Introducing Archive Services for SAP Overview The Archive Services application integrates the EMC Documentum content management system with the SAP R/3 system. Based on SAP ArchiveLink 4.Version 5 HTTP interface, Archive Services provides a technology bridge between EMC Documentum and SAP R/3. Archive Services for SAP provides the following functionalities: Enables users to easily access and display documents stored in a Documentum repository 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 ArchiveLink TM 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 Con guring SAP R/3 for Archive Services for SAP 11

12 Introducing Archive Services for SAP Understanding the Archive Services for SAP architecture Figure 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 archive reports, data, incoming and outgoing documents from SAP to the Documentum repository. Archive Services is a J2EE servlet that communicates with SAP ArchiveLink. The reports and archived documents can later be retrieved and viewed through SAPGUI. RFC archiving services A server component that enables you to archive reports, data, incoming and outgoing documents from SAP to the EMC Documentum repository. The archived 12 Con guring SAP R/3 for Archive Services for SAP

13 Introducing Archive Services for SAP reports and documents can later be retrieved and viewed through SAPGUI and Documentum clients. This component uses SAP Remote Function Calls (RFCs) to communicate 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 information about specific OS versions and supported software environments. Supported SAP document formats Documentum 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 SAP terms This section presents some terms and their definitions, as used in this guide. Table 1-1. Terms and de nitions Term Archive Services for SAP Definition Product that connects Documentum to SAP and vice versa. Con guring SAP R/3 for Archive Services for SAP 13

14 Introducing Archive Services for SAP Term HTTP Archiving Services RFC Archiving Server WebAdmin DMCL ArchiveLink Definition Server component that, using an HTTP connection to SAP, enables you to archive reports, data, incoming and outgoing documents from SAP to the Documentum repository. HTTP Archiving Services is a J2EE servlet that communicates with SAP ArchiveLink. The reports and archived documents can later be retrieved and viewed through. A server component that enables you to archive reports, data, incoming and outgoing documents from SAP to the EMC Documentum repository. The archived reports and documents can later be retrieved and viewed through SAPGUI and Documentum clients. This component uses SAP Remote Function Calls (RFCs) to communicate with SAP. An administrative console that allows you to: Create and manage archives Manage certificates for the archive Create repository connections for Archive Services for SAP Documentum Client Library. Manages communication between clients and EMC Documentum Content Server. Contains a library of API calls that are used by clients for execution on the EMC Documentum Content Server. All client requests to the EMC Documentum Content Server go through the DMCL. Cross-functional interface that is part of the SAP Basis System. ArchiveLink handles storing and retrieving documents and data to and from a repository external to SAP. 14 Con guring SAP R/3 for Archive Services for SAP

15 Introducing Archive Services for SAP Term SAP DMS SAP PLM SAP Master Record SAP GUI Original Document SAP Document Definition Document Management System that is part of the SAP Basis System. Presents a logical layer to integrate with external systems like AutoCAD or Documentum. Not directly related to ArchiveLink. Product Life-Cycle Management (PLM). SAP PLM provides an integrated environment that ensures all people involved in product development, manufacturing, and service have quick and secure access to current information. It provides a set of BAPI calls that can be used by external systems like Documentum. A set of master data, such as customer or vendor data, which is used in the creation of SAP documents. SAP Graphical User Interface. Graphical menu/screen tool that connects a client to the SAP server. Paper based version of a document. Example 1-1. An invoice may consist of two sheets of paper received from a supplier. Paper documents are scanned in and stored as electronic originals in Documentum. An electronic transactional record of header data and line items in SAP. Con guring SAP R/3 for Archive Services for SAP 15

16 Introducing Archive Services for SAP 16 Con guring SAP R/3 for Archive Services for SAP

17 Chapter 2 Con guring the ArchiveLink Interface for Archive Services for SAP Overview You can store and retrieve documents, reports, and data through SAP ArchiveLink and DMS interfaces. Prior to running the Archive Services, the SAP R/3 system must also be configured. This chapter describes how to configure your R/3 ArchiveLink and other related transactions through SAPGUI and the R/3 system. Note: The configuration steps often reference direct transaction codes. These codes allow you to navigate directly to the correct configuration screen. Most of the system configuration 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 Archive Server or an RFC (Remote Function Call) Archive Server. Note: Documentum recommends that all new installations are based on the HTTP-based Archive Server. The primary reason is that SAP will focus future development at the HTTP-based archive protocol. The configuration steps are different for RFC and HTTP based archiving. Configuration steps 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 following sections: 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 Con guring SAP R/3 for Archive Services for SAP 17

18 Con guring the ArchiveLink Interface for Archive Services for SAP oac0 De ning a logical ArchiveID Note: The name of the logical ArchiveID must be the same as the ArchiveID created using WebAdmin (refer to the Configuring, Viewing, and Editing Archives section of the Archive Services for SAP Administration Guide). To de ne 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 content repository (specifically whose Storage type is HTTP content server. 3. In the Display Content Repositories: Detail page, click the Display/Change icon The 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 using WebAdmin (refer to the Configuring, Viewing, and Editing Archives section of the Archive Services for SAP Administration Guide). 6. In the Transfer drctry field, enter the directory path where SAP can write the Print List 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 Con guring basic settings You must define the basic settings for ArchiveLink. To con gure 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. 18 Con guring SAP R/3 for Archive Services for SAP

19 Con guring the ArchiveLink Interface for Archive Services for SAP oanr Con guring number ranges You must configure the number ranges for ArchiveLink. To con gure 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. 4. Save your changes. oaqi - Creating queues When Print Lists are archived, the SAP print spooler puts the document into the asynchronous queue. The scheduler then picks up the document and sends it to the archive. The queue serves as a buffer for everything sent to an SAP archive. Other queues are used for outgoing documents and barcodes. These queues can be seen on the ArchiveLink Monitor screen (transaction code: oam1). If this screen shows the word MISSING instead of zeros, you must create queues and specify an administrator. Define an SAP user with the proper ArchiveLink administrator profile as the administrator for this queues. Defining an administrator will automatically create the queues. Check that the queues have been created by reviewing transaction oam1. To create queues: 1. Execute the following transaction in the transaction code field: oaqi The 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. Con guring SAP R/3 for Archive Services for SAP 19

20 Con guring the ArchiveLink Interface for Archive Services for SAP oaat - Scheduling jobs The SAP schedule job periodically checks the output queue and sends all the items in the queues to the archive. You must configure the schedule job to successfully archive documents 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. 5. Save your changes. 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 Con guring optical archives as output devices An output device is the driver software for the logical output device which archives documents using the ArchiveLink interface. To correctly archive a document to SAP, you must define the output device as an optical archive. Configuring an output device includes defining the type, the device, the spool server, and so on. There should be only ONE ARCH device; therefore, prior to defining a device with the ARCH short name, you should delete any existing ARCH devices such as ARCHIXOS. To con gure an optical archive as the output device: 1. Start SAPGUI and connect to your R/3 server. 20 Con guring SAP R/3 for Archive Services for SAP

21 Con guring the ArchiveLink Interface for Archive Services for SAP 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. If you are already using a printer named ARCH you can either delete it or using the existing 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 Output Device Short Name Device Type Spool Server Device Class Type Access Method Fill Location Fill Message Fill Value ARCHIVE ARCH ARCHLINK Select spool server from drop down list. Usually there is only one spool server listed A, for archive program I, for archive service Archive ArchiveLink Device 8. Click Enter and the dialog box changes. 9. Save your changes. sm50 Verifying spool processes Archive Services uses the standard SAP print spooler to send reports to the ArchiveLink queue. 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. Con guring SAP R/3 for Archive Services for SAP 21

22 Con guring the ArchiveLink Interface for Archive Services for SAP 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 Con guring the SAP inline Print List viewer 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 must configure the protocol to support the viewer. To con gure 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 Archive Services 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-defined protocol. 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. 22 Con guring SAP R/3 for Archive Services for SAP

23 Con guring the ArchiveLink Interface for Archive Services for SAP 12. In the Overview of a Protocol window showing the list of Document Classes, select the 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] key No 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 ALF document class are indicated as Maintained Explicitly. All other document classes should be indicated as Not Maintained Explicitly. Con guring SAP R/3 for Archive Services for SAP 23

24 Con guring the ArchiveLink Interface for Archive Services for SAP 24 Con guring SAP R/3 for Archive Services for SAP

25 Chapter 3 Customizing SAP Document Classes Overview The following sections describe how to archive document classes from SAP. The customization of each SAP setup is different depending on which document class the archived document belongs to. The document classes are: ALF FAX OTF REO For all classes, you must configure, at least: oac0 oac2 oac3 plus any specific customizations. These customizations are described in the following sections: oac0 Configuring content repositories, page 25 oac2 - Defining document types, page 30 oac3 - Defining links, page 30 oac0 Con guring content repositories SAP allows you to define a content repository (previously known as a logical archive). This content repository is mapped to a Documentum archive via WebAdmin. The Documentum archive links to a set of rules such as content folders, Documentum document types, and so on in the Documentum repository. It is recommended that you store each document type in a separate archive. Using WebAdmin, you must create a matching archive for each ArchiveID defined in SAP. This ArchiveID defines what actions (types, folders, retention, and so on) are applied on a SAP document when it is archived. The following sections explain how to create an archive in SAP for each represented document class. Con guring SAP R/3 for Archive Services for SAP 25

26 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. HTTP based archives. The configuration steps below have been listed as being relevant only to RFC- or HTTP-based archiving. Note: Documentum recommends that all new installations are based on the HTTP-based Archive Server. The primary reason is that SAP will focus future development at the HTTP-based archive protocol. However legacy RFC archives are still supported. To de ne 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 Content rep Description Storage Type Protocol Version No. Output Device Value Specify a two-letter archive name. For example, AA A meaningful name. For example, SAP Print Lists (AA) Select HTTP or RFC The previously configured protocol for HTTP or 0031 for RFC ARCHIVE 6. Depending on whether you selected HTTP or RFC based archiving, type appropriate 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 a server name here, ensure that you can ping the server by name from the SAP server. Port Number Type the port number being used (default is 80). 26 Con guring SAP R/3 for Archive Services for SAP

27 Customizing SAP Document Classes When using a default Tomcat configuration, this value is usually 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 content into. 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 archived documents 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 RFC destination archives, page 27). Basic path Type the file system path to the location where SAP will put archived documents 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 to define any Documentum archives in SAP. sm59 RFC destination archives This section applies to RFC archiving only. The SAP server considers Content Services for SAP an external RFC service or RFC destination. The destination is identified with a symbolic name that was configured in Documentum during the Content Services Archive Service installation. The name of the RFC destination must be unique for each repository/sap client connection and identical in the Content Services Archive Services and WebAdmin configurations. To con gure the RFC destination: 1. Start SAPGUI and connect to your R/3 server. Con guring SAP R/3 for Archive Services for SAP 27

28 Customizing SAP Document Classes 2. Execute the folliwng transaction: sm 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 Services Archive 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 to communicate. 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 WebAdmin and transaction code sm59 because the value of this field must correspond to the configuration parameter RFC Program ID in the WebAdmin ArchiveLink configuration tab RFC Destination parameter RFC Program ID. If you have not yet installed Content Services, you will need to make a note of this value so that you can configure your RFC destination in Content Services WebAdmin, and when the RFC services are installed on the Content Services host server. This value must be unique for each repository/sap client connection which is why the RFC destination name <DCTMHOSTNAME>_<SAPSYSID_CLIENT> is recommended. If two Content Services archive processes register under the same ID or name the second one connected receives all requests from SAP. The first process will not receive an error message so it will wait indefinitely for RFC requests that never come. 12. Save your changes. 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 Con guring SAP R/3 for Archive Services for SAP

29 Customizing SAP Document Classes sm59 - Testing connections You must have created SM59 RFC destination, WebAdmin RFC config, and Content Services RFC services via the Content Services installation program and started with the SHARE user ID (refer to Installing Content Services for SAP) before you begin this procedure. To test the ArchiveLink RFC connection to Content Services archive: 1. Switch on debugging before processes or services are started the first time by setting the 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 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 Content Services. 7. Click on Test Connection. A message appears on the status bar, stating that the connection is OK. A new window 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 server which 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... : Con guring SAP R/3 for Archive Services for SAP 29

30 Customizing SAP Document Classes 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 turn on 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 - De ning document types You must select which document types you will be archiving, and correlate those to SAP document classes, such as FAX, ALF, OTF, and REO, The list of document types provided by SAP, when using transaction OAC2, are the templates to be used for categorizing your SAP documents for archiving. You can customize the standard document types by using 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 de ne document types for SAP: 1. Execute the following transaction in the transaction code field: oac2. 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 your configuration. 5. When you have finished selecting document types, save your changes. oac3 - De ning links Using the link table, you can categorize SAP documents to define what combination of SAP 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 SAP document type (for example, ALF, OTF, REO) which determines how the document is produced and linked. For example, the ALF class refers to reports, FAX to scanned documents, and OTF to outgoing SAPSCRIPT documents. 30 Con guring SAP R/3 for Archive Services for SAP

31 Customizing SAP Document Classes To de ne 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 Object Type Document Type S (Status) Value Use legitimate object type such as SOOD for Print Lists, and BKPF for accounting documents The SAP doc type as defined in OAC2 above such as GENPRILIS Enter an x in this column Arch. ID Link Ret Prd Save your changes. Enter the archive ID of a newly created archives for example, AA Enter the name of the link tables where links will be maintained. TOA01-TOA03 Con guring SAP R/3 for Archive Services for SAP 31

32 Customizing SAP Document Classes 32 Con guring SAP R/3 for Archive Services for SAP

33 Chapter 4 Testing the Archiving Process Using a Print List Overview Once you have completed the configuration procedures described previously in this guide, you should test the archiving process by: defining an ArchiveID in WebAdmin. For more information, refer to the Configuring, Viewing, and Editing Archives section of the 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 SAP To fully test the archival and retrieval cycle, a simple Print List can be configured by following 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. Con guring SAP R/3 for Archive Services for SAP 33

34 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 the Document 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 created earlier (refer to oac0 Defining a logical ArchiveID, page 18), where the documents will be archived. 7. Save your changes. Testing connection between SAP and Archive Services 1. Execute the following transaction in the transaction code field: oac0. 2. In the Display Content Repositories: Overview page, click on any content repository (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 the connection test has been successful. Archiving a Print List To archive a Print List: 1. Execute the following transaction in the transaction code field: : f 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 you check the Show Selected Print Parameters on Initial Screen checkbox. This ensures that the customized settings are available in the initial Print Screen List dialog box. 34 Con guring SAP R/3 for Archive Services for SAP

35 Testing the Archiving Process Using a Print List 7. Verify that the Object Type and Document Type fields contain the correct values, as configured in the New Entries table (refer to oac3 - Defining links, page 30). Pick the following values for example: SOOD GENPRILIS. If your Document Type is incorrectly configured, refer to the following procedures for configuring document types in SAP archives:oac2 - Defining document types, page 30 and oac3 - Defining links, page 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 following transaction 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 it to the archive. oaat - Scheduling jobs, page 20, contains information about configuring the ArchiveLink scheduler. 15. To accelerate the transfer of the Print List from the queue to the archive in the repository, click Storage Queue. The Queue: Content server (CARA) screen appears. You should now see an entry for 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 SAPGUI To display the newly-archived Print List in SAPGUI: 1. Execute the following transaction in the transaction code field: oadr. Con guring SAP R/3 for Archive Services for SAP 35

36 Testing the Archiving Process Using a Print List 2. To find a particular Print List, type appropriate search parameters in the appropriate fields. 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 Documentum archive. The retrieved document is displayed in SAPGUI and has the DocumentID of the Print List in Documentum. Deleting archived and linked documents In a repository, if you delete version 1.0 of a document that is linked to SAP or archived from SAP, the link to SAP is also deleted. This is because the dm_relation object which creates 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 to SAP if you want to maintain their link to SAP. If you need to delete version 1.0 of a document, but want to keep the link to SAP, then, after deleting the document, you must relink the object to SAP, outside of Archive Services. 36 Con guring SAP R/3 for Archive Services for SAP

37 Index A Administrative Console, 13 ALF, 25, 30 ALF class, 13 ALF format, 13 Archive Services, 7 configuring ArchiveLink for, 17 Archive Services administrator, 7 Archive Services for SAP, see Archive Services defined, 11 archived and deleting documents, deleting, 36 archived data, 13 archived Print List displaying in SAPGUI, 35 ArchiveLink configuring for Archive Services, 17 ArchiveLink Monitor window, 35 archiving Print List, 34 archiving process testing using a Print List, 33 Archiving request window, 35 asynchronous queue, 19 B basic settings, configuring, 18 C Change Content Repositories window, 26 class ALF, 13 FAX, 13 OTF, 13 REO, 13 configuration procedures, 27 configuring ArchiveLink for Archive Services, 17 basic settings, 18 number ranges, 19 optical archive as output device, 20 SAP inline Print List viewer protocol, 22 connection between SAP and Archive Services, testing of, 34 content repositories, 25 Content Services server, 29 creating document type, 33 queues, 19 D defining document types, 30 links, 31 logical ArchiveID, 18 deleting archived and linked documents, 36 displaying archived Print List in SAPGUI, 35 document incoming, 13 outgoing, 13 scanned, 13 supported formats in SAP, 13 document classes ALF, 25 FAX, 25 OTF, 25 REO, 25 document formats, supported in SAP, 13 document type creating, 33 document types ALF, 30 defining, 30 FAX, 30 Con guring SAP R/3 for Archive Services for SAP 37

38 Index F OTF, 30 REO, 30 f.21, 34 FAX, 25, 30 FAX class, 13 format ALF, 13 PDF, 13 REO, 13 Tiff, 13 frequency of archival, 20 H HTTP Archiving Server, 12 HTTP-based archiving, 22 I intended audience, 7 J jobs, scheduling, 20 L links defining, 31 logical ArchiveID defining, 18 N number ranges, configuring, 19 O oaa3, 22 oaat, 20 oac0, 18, 25, 34 oac2, 30 oac3, 30, 33 oadr, 35 oag1, 18 oam1, 19 oanr, 19 oaq1, 19 oaqi, 19 ObjectType, SOOD, 33 optical archive, configuring as output device, 20 organization of this guide, 8 OTF, 25, 30 OTF class, 13 output device configuring logical archive as, 20 Overview of a Protocol window, 22 P PDF format, 13 prerequisites system administrator, 7 Print List archived, displaying in SAPGUI, 35 archiving, 34 testing archiving process using, 33 Print Lists, 13 ALF class, 13 ALF format, 13 purpose of the guide, 7 Q queues, creating, 19 R REO, 25, 30 REO class, 13 REO format, 13 Reports, see Print Lists RFC destination archive, 27 S SAP print spooler, 21 supported document formats in, 13 transaction code, f.21, 34 transaction code, oaa3, 22 transaction code, oaat, 20 transaction code, oac0, 18, 25, 34 transaction code, oac2, 30 transaction code, oac3, 30, 33 transaction code, oadr, 35 transaction code, oag1, 18 transaction code, oam1, 19 transaction code, oanr, Con guring SAP R/3 for Archive Services for SAP

39 Index transaction code, oaq1, 19 transaction code, oaqi, 19 transaction code, sm50, 21 transaction code, spad, 20 transaction code, spro, 17 SAP Document Classes customizing, 25 SAP inline Print List viewer protocol, configuring, 22 SAPGUI ArchiveLink Monitor window, 35 Archiving request window, 35 Change Content Repositories window, 26 displaying archived Print List in, 35 Overview of a Protocol window, 22 Queue Administrator field, 19 Test connection button, 34 scheduling jobs, 20 sm50, 21 SM59, 27, 29 SOOD, ObjectType, 33 spad, 20 SPO process, 21 spool process, 21 spool processes, verifying, 21 spro, 17 standard user, 7 supported document formats in SAP, 13 ALF class, 13 ALF format, 13 FAX class, 13 OTF class, 13 PDF format, 13 REO class, 13 REO format, 13 Tiff format, 13 system administrator, 7 prerequisites, 7 T Test connection button, SAPGUI, 34 testing connection between SAP and Archive Services, 34 testing archiving process using a Print List, 33 testing the connection, 29 Tiff format, 13 transaction code f.21, 34 oaa3, 22 oaat, 20 oac0, 18, 25, 34 oac2, 30 oac3, 30, 33 oadr, 35 oag1, 18 oam1, 19 oanr, 19 oaq1, 19 oaqi, 19 sm50, 21 spad, 20 spro, 17 Transfer drctry field, 18 U ueue Administrator field, 19 user roles, 7 V verifying, spool processes, 21 version 0045, 22 W WebAdmin, 13 Con guring SAP R/3 for Archive Services for SAP 39