Informatica ILM Nearline for use with SAP NetWeaver BW (Version 6.1) Configuration Guide

Transcription

1 Informatica ILM Nearline for use with SAP NetWeaver BW (Version 6.1) Configuration Guide

2 Informatica ILM Nearline Configuration Guide Version 6.1 February 2013 Copyright (c) Informatica Corporation. All rights reserved. This software and documentation contain proprietary information of Informatica Corporation and are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright law. Reverse engineering of the software is prohibited. No part of this document may be reproduced or transmitted in any form, by any means (electronic, photocopying, recording or otherwise) without prior consent of Informatica Corporation. This Software may be protected by U.S. and/or international Patents and other Patents Pending. Use, duplication, or disclosure of the Software by the U.S. Government is subject to the restrictions set forth in the applicable software license agreement and as provided in DFARS (a) and (a) (1995), DFARS (1)(ii) (OCT 1988), FAR (a) (1995), FAR , or FAR (ALT III), as applicable. The information in this product or documentation is subject to change without notice. If you find any problems in this product or documentation, please report them to us in writing. Informatica, Informatica Platform, Informatica Data Services, PowerCenter, PowerCenterRT, PowerCenter Connect, PowerCenter Data Analyzer, PowerExchange, PowerMart, Metadata Manager, Informatica Data Quality, Informatica Data Explorer, Informatica B2B Data Transformation, Informatica B2B Data Exchange Informatica On Demand, Informatica Identity Resolution, Informatica Application Information Lifecycle Management, Informatica Complex Event Processing, Ultra Messaging and Informatica Master Data Management are trademarks or registered trademarks of Informatica Corporation in the United States and in jurisdictions throughout the world. All other company and product names may be trade names or trademarks of their respective owners. Portions of this software and/or documentation are subject to copyright held by third parties, including without limitation: Copyright DataDirect Technologies. All rights reserved. Copyright Sun Microsystems. All rights reserved. Copyright RSA Security Inc. All Rights Reserved. Copyright Ordinal Technology Corp. All rights reserved.copyright Aandacht c.v. All rights reserved. Copyright Genivia, Inc. All rights reserved. Copyright Isomorphic Software. All rights reserved. Copyright Meta Integration Technology, Inc. All rights reserved. Copyright Intalio. All rights reserved. Copyright Oracle. All rights reserved. Copyright Adobe Systems Incorporated. All rights reserved. Copyright DataArt, Inc. All rights reserved. Copyright ComponentSource. All rights reserved. Copyright Microsoft Corporation. All rights reserved. Copyright Rogue Wave Software, Inc. All rights reserved. Copyright Teradata Corporation. All rights reserved. Copyright Yahoo! Inc. All rights reserved. Copyright Glyph & Cog, LLC. All rights reserved. Copyright Thinkmap, Inc. All rights reserved. Copyright Clearpace Software Limited. All rights reserved. Copyright Information Builders, Inc. All rights reserved. Copyright OSS Nokalva, Inc. All rights reserved. Copyright Edifecs, Inc. All rights reserved. Copyright Cleo Communications, Inc. All rights reserved. Copyright International Organization for Standardization All rights reserved. Copyright ej-technologies GmbH. All rights reserved. Copyright Jaspersoft Corporation. All rights reserved. Copyright is International Business Machines Corporation. All rights reserved. Copyright yworks GmbH. All rights reserved. Copyright Lucent Technologies. All rights reserved. Copyright (c) University of Toronto. All rights reserved. Copyright Daniel Veillard. All rights reserved. Copyright Unicode, Inc. Copyright IBM Corp. All rights reserved. Copyright MicroQuill Software Publishing, Inc. All rights reserved. Copyright PassMark Software Pty Ltd. All rights reserved. Copyright LogiXML, Inc. All rights reserved. Copyright Lorenzi Davide, All rights reserved. Copyright Red Hat, Inc. All rights reserved. Copyright The Board of Trustees of the Leland Stanford Junior University. All rights reserved. Copyright EMC Corporation. All rights reserved. Copyright Flexera Software. All rights reserved. Copyright Jinfonet Software. All rights reserved. This product includes software developed by the Apache Software Foundation ( and other software which is licensed under the Apache License, Version 2.0 (the "License"). You may obtain a copy of the License at Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. This product includes software which was developed by Mozilla ( software copyright The JBoss Group, LLC, all rights reserved; software copyright by Bruno Lowagie and Paulo Soares and other software which is licensed under the GNU Lesser General Public License Agreement, which may be found at The materials are provided free of charge by Informatica, "as-is", without warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability and fitness for a particular purpose. The product includes ACE(TM) and TAO(TM) software copyrighted by Douglas C. Schmidt and his research group at Washington University, University of California, Irvine, and Vanderbilt University, Copyright ( ) , all rights reserved. This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (copyright The OpenSSL Project. All Rights Reserved) and redistribution of this software is subject to terms available at and This product includes Curl software which is Copyright , Daniel Stenberg, <daniel@haxx.se>. All Rights Reserved. Permissions and limitations regarding this software are subject to terms available at Permission to use, copy, modify, and distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies. The product includes software copyright ( ) MetaStuff, Ltd. All Rights Reserved. Permissions and limitations regarding this software are subject to terms available at license.html. The product includes software copyright , The Dojo Foundation. All Rights Reserved. Permissions and limitations regarding this software are subject to terms available at This product includes ICU software which is copyright International Business Machines Corporation and others. All rights reserved. Permissions and limitations regarding this software are subject to terms available at

3 This product includes software copyright Per Bothner. All rights reserved. Your right to use such materials is set forth in the license which may be found at kawa/software-license.html. This product includes OSSP UUID software which is Copyright 2002 Ralf S. Engelschall, Copyright 2002 The OSSP Project Copyright 2002 Cable & Wireless Deutschland. Permissions and limitations regarding this software are subject to terms available at This product includes software developed by Boost ( or under the Boost software license. Permissions and limitations regarding this software are subject to terms available at / This product includes software copyright University of Cambridge. Permissions and limitations regarding this software are subject to terms available at This product includes software copyright 2007 The Eclipse Foundation. All Rights Reserved. Permissions and limitations regarding this software are subject to terms available at This product includes software licensed under the terms at license.html, license.html, license-agreement; and This product includes software licensed under the Academic Free License ( the Common Development and Distribution License ( the Common Public License ( the Sun Binary Code License Agreement Supplemental License Terms, the BSD License ( the MIT License ( and the Artistic License ( This product includes software copyright Joe WaInes, XStream Committers. All rights reserved. Permissions and limitations regarding this software are subject to terms available at This product includes software developed by the Indiana University Extreme! Lab. For further information please visit This Software is protected by U.S. Patent Numbers 5,794,246; 6,014,670; 6,016,501; 6,029,178; 6,032,158; 6,035,307; 6,044,374; 6,092,086; 6,208,990; 6,339,775; 6,640,226; 6,789,096; 6,820,077; 6,823,373; 6,850,947; 6,895,471; 7,117,215; 7,162,643; 7,243,110, 7,254,590; 7,281,001; 7,421,458; 7,496,588; 7,523,121; 7,584,422; ; 7,720,842; 7,721,270; and 7,774,791, international Patents and other Patents Pending. DISCLAIMER: Informatica Corporation provides this documentation "as is" without warranty of any kind, either express or implied, including, but not limited to, the implied warranties of noninfringement, merchantability, or use for a particular purpose. Informatica Corporation does not warrant that this software or documentation is error free. The information provided in this software or documentation may include technical inaccuracies or typographical errors. The information in this software and documentation is subject to change at any time without notice. NOTICES This Informatica product (the Software ) includes certain drivers (the DataDirect Drivers ) from DataDirect Technologies, an operating company of Progress Software Corporation ( DataDirect ) which are subject to the following terms and conditions: 1. THE DATADIRECT DRIVERS ARE PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. 2. IN NO EVENT WILL DATADIRECT OR ITS THIRD PARTY SUPPLIERS BE LIABLE TO THE END-USER CUSTOMER FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR OTHER DAMAGES ARISING OUT OF THE USE OF THE ODBC DRIVERS, WHETHER OR NOT INFORMED OF THE POSSIBILITIES OF DAMAGES IN ADVANCE. THESE LIMITATIONS APPLY TO ALL CAUSES OF ACTION, INCLUDING, WITHOUT LIMITATION, BREACH OF CONTRACT, BREACH OF WARRANTY, NEGLIGENCE, STRICT LIABILITY, MISREPRESENTATION AND OTHER TORTS. Part Number: INL-CFG

4 Table of Contents 1 CONFIGURING THE SAP NEARLINE ADD-ON CONFIGURING AN INTERVAL IN NUMBER RANGE OBJECT /SAND/0NLS CONFIGURING THE DIRECTORY FOR DATA EXCHANGE CONFIGURING THE RFC CONNECTION Configuring the User for the RFC Connection Configuring the RFC Connection Verifying the RFC Connection CONFIGURING THE LOG OBJECT CREATING AN INFOAREA FOR AUTOMATICALLY CREATED OBJECTS ACTIVATE BI CONTENT FROM INFORMATICA CONFIGURING NEARLINE SETTINGS RSDANLCON Settings Configuring ILM Nearline Program (/SAND/0_CONFIG) CONFIGURING THE SCHEMA FOR DATA EXCHANGE Existing Connections Retrieving Information about File Archive Service Schemas TESTING THE CONFIGURATION Viewing ILM Nearline Version Information SETTING UP AUTHORIZATION CHECKING SELECTING THE AUTHORIZATION CLASS FOR AN SAP SYSTEM ASSIGNING AUTHORIZATION PROFILES TO USERS EXAMPLES PER-SYSTEM CONFIGURATION CONFIGURATION TABLES THE /SAND/0_CONFIG PROGRAM Adding New SAP System IDs... 31

5 3.2.2 Activating Per-system Configuration Per-system Settings MANAGING NEARLINE CONNECTIONS CONFIGURATION CHECKING Types of Configuration Checking OTHER FUNCTIONS SAVING THE PER-SYSTEM SETTINGS TRANSPORT CONSIDERATIONS TRANSPORTING NEARLINE CONFIGURATION ACROSS THE SAP SYSTEM LANDSCAPE PREPARING FOR INFORMATICA TECHNICAL SUPPORT SETTING UP THE SAP SUPPORT CONNECTION SINGLE MACHINE INSTALLATION Accessing the Nearline Service Log Files Within SAP Executing Commands at the Operating System Level Within SAP Accessing the Nearline Service Installation at the Operating System Level MULTI-MACHINE INSTALLATION Accessing Nearline Service Installation Files Executing Commands at the Operating System Level Within SAP Accessing the Nearline Service Installation at the Operating System Level APPENDIX A: SAMPLE CONFIGURATION FILES NUCLEUS.INI SSA.INI ODBC.INI SAND_NLIC.PROPERTIES APPENDIX B: UNIX (U)LIMIT SETTINGS HP-UX APPENDIX C: CONFIGURATION TABLES... 69

6 RSDANLCON /SAND/0_NLS_CFG /SAND/0CONFIG /SAND/0_NLS_CFGP /SAND/0_SYSIDS /SAND/0_NLS_VAR /SAND/0_NLS_CFGA... 72

7 Preface Informatica Resources Informatica Customer Portal As an Informatica customer, you can access the Informatica Customer Portal site at The site contains product information, user group information, newsletters, access to the Informatica customer support case management system (ATLAS), the Informatica How-To Library, the Informatica Knowledge Base, the Informatica Multimedia Knowledge Base, Informatica Product Documentation, and access to the Informatica user community. Informatica Documentation The Informatica Documentation team takes every effort to create accurate, usable documentation. If you have questions, comments, or ideas about this documentation, contact the Informatica Documentation team through at We will use your feedback to improve our documentation. Let us know if we can contact you regarding your comments. The Documentation team updates documentation as needed. To get the latest documentation for your product, navigate to Product Documentation from Informatica Web Site You can access the Informatica corporate web site at The site contains information about Informatica, its background, upcoming events, and sales offices. You will also find product and partner information. The services area of the site includes important information about technical support, training and education, and implementation services. Informatica How-To Library As an Informatica customer, you can access the Informatica How-To Library at The How-To Library is a collection of resources to help you learn more about Informatica products and features. It includes articles and interactive demonstrations that provide solutions to common problems, compare features and behaviors, and guide you through performing specific real-world tasks. Informatica Knowledge Base As an Informatica customer, you can access the Informatica Knowledge Base at Use the Knowledge Base to search for documented solutions to known technical issues about Informatica products. You can also find answers to frequently asked questions, technical white papers, and technical tips. If you have questions, comments, or ideas about the Knowledge Base, contact the Informatica Knowledge Base team through at KB_Feedback@informatica.com. Informatica Multimedia Knowledge Base As an Informatica customer, you can access the Informatica Multimedia Knowledge Base at The Multimedia Knowledge Base is a collection of instructional multimedia files that help you learn about common concepts and guide you through performing specific tasks. If you have

8 questions, comments, or ideas about the Multimedia Knowledge Base, contact the Informatica Knowledge Base team through at Informatica Global Customer Support You can contact a Customer Support Center by telephone or through the Online Support. Online Support requires a user name and password. You can request a user name and password at Use the following telephone numbers to contact Informatica Global Customer Support: North America / South America Europe / Middle East / Africa Asia / Australia Toll Free Toll Free Toll Free North America Brazil Mexico United Kingdom: France : Netherlands : Germany: Switzerland: Spain: Portugal: Italy: Australia: New Zealand: Standard Rate India: Standard Rate France: Belgium: Germany: Netherlands: United Kingdom:

9

10 1 Configuring the SAP Nearline Add-On After the installation, configure the SAP Nearline Add-On. 1.1 Configuring an Interval in Number Range Object /SAND/0NLS The number range object /SAND/0NLS is delivered without any preconfigured intervals. Create a new interval for this number range object. 1. From the /SAND/0_MAINP menu, select Setup > Configure Number Ranges or start transaction /SAND/0_S_SNRO. 2. Enter object name /SAND/0NLS. 3. Click Number ranges. 4. Click Change intervals. 5. Click Insert interval. 6. Enter a new interval ID for the /SAND/0NLS number range object. The following table describes the number range interval parameters: Parameter Interval ID Description Any two-character string, such as "20". You must also enter the interval ID in the configuration table. For more information, see section 1.7. From Number Must be greater than or equal to 1. To Number Must be less than External Number Range Do not enable. If the upper limit of the number range is set too low, the configuration checker program, /SAND/0_CONFIG_CHECK, generates a warning. The configuration checker program also gives a warning if and when the current number reaches 95% of the number range limit. For more information about resetting the current number range, see the ILM Nearline for SAP BW Administration Guide. 1

11 1.2 Configuring the Directory for Data Exchange If you use HTTP communication to exchange all data between SAP and the Nearline Service, you can skip this section. Warning: If errors occur when you configure variable configuration of path names, see SAP note Implementation of the SAP Nearline Add-On component may exchange data via a file system. In this case, communication between SAP BW and external components is accomplished through a tasks directory. The following considerations apply to the tasks directory: Both the account that runs the SAP system and the account that runs the external software must have write permissions on the tasks directory. If the SAP system is installed on separate application servers than the File Archive Service and the Nearline Service, the tasks directory must be "visible" under the same name to all of the servers. The directory name cannot be longer than 25 characters and must not contain spaces In Windows, the directory name should be specified using the UNC style (\\<server name>\<directory name>). To configure the tasks directory for data exchange: 1. From area menu /SAND/0_MAINP, select Setup > Maintain exchange directories or start transaction FILE. 2. Click New Entries. Enter the name and description of the ZSAND_PATH logical file path as shown in Figure Save the entries. Figure 1: Logical File Path New Entry 4. Select the ZSAND_PATH entry and double-click Assignment of Physical Paths to Logical Paths in the left-hand pane. 2

12 An empty list appears for the logical path ZSAND_PATH. 5. Click New Entries. Figure 2: Assignment of Physical Paths to Logical Paths - List 6. Enter the appropriate mapping for the operating system. Note that the path must end with the "<FILENAME>" variable. Optionally, the path can contain the "<SYSID>" variable, which inserts the current SAP System ID into the path where <SYSID> appears. Using <SYSID> can make the configuration transportable throughout the SAP landscape without modification, however all SAP systems must use the same directory structure, with the exception of the system name, as defined below. For example: UNIX: Warning: The <SYSID> value is always inserted in an uppercase format. This variable should therefore not be used with lowercase SAP system IDs in UNIX. /snic/<sysid>/tasks/<filename> Windows: c:\snic\<sysid>\tasks\<filename> -or- \\<server name>\<directory name>\<sysid>\tasks\<filename> 3

13 7. Save the settings. Figure 3: Assignment of Physical Paths to Logical Paths 8. Double-click Logical Filename Definition, Cross Client in the right-hand pane, then click New Entries and enter the appropriate values. For example, create the logical file ZSAND_FILE with the following values: Physical File: <PARAM_1> Logical path: ZSAND_PATH 9. Save the settings. Figure 4: Logical Filename Definition 4

14 1.3 Configuring the RFC Connection An RFC connection is used in the transport management system during import activities. This ensures that the import processes that run in client 000 can access the number range object configured in the SAP BW client. For more information, see section 1.1. Note that the RFC connection is not needed to install the SAP Nearline Add-On. It is used only when transporting SAP BW objects relevant to nearline, such as DAPs (Data Archiving Processes), from a source system (DEV) to a target system within the SAP system landscape (for example, QA or PROD). The RFC connection required in this case is for the target system only. It is used so that the target system can connect from its client 000, which is performing the import of the transport, to the client on which the SAP Nearline Add-On is configured (usually client 100) Configuring the User for the RFC Connection This step is required only if a BWREMOTE user is not already configured in the system. For more information about how to verify if this user exists, see section Log in to the SAP BW client, then access the following section of the SAP Reference Implementation Guide (transaction SPRO, click the SAP Reference IMG button): SAP Customizing Implementation Guide > SAP NetWeaver > Business Intelligence > Automated Processes > Create User for Background Processes When the IMG is used, it is only necessary to specify a password for the user. An alternative method is to create the BWREMOTE user manually. From area menu /SAND/0_MAINP, select Setup > Enable authorization check for nearline users or start transaction SU01. Create the user manually with at least the following settings: On the Logon data tab: o o Initial/Repeat password: <enter desired password> User Type: System On the Profiles tab: S_BI-WHM_RFC On the Address tab: Last name: <enter anything> Configuring the RFC Connection To configure the RFC connection, log in to the SAP BW client, then access the following section of the SAP Reference Implementation Guide (IMG, transaction SPRO): SAP Customizing Implementation Guide > SAP NetWeaver > Business Intelligence > Transport Settings > Create Destination for Import Post-Processing 5

15 After pressing the execute button, you need to fill information for Client (your BW client), Destination (the name of the RFC connection; choose an unused name of your choice, for example, "BWCLIENT"), User ( BWREMOTE ), and the Password of the user in your BW client Verifying the RFC Connection To verify the RFC connection settings: 1. Start the SE16 transaction, enter the table RSADMINA, and make sure that the TPBWMANDTRFC field contains the RFC connection name from section (for example, "BWCLIENT") and BW_USER contains "BWREMOTE". 2. Start the SM59 transaction and double-click the RFC connection name (for example, "BWCLIENT") in ABAP Connections to bring up the RFC definition. On the Logon & Security tab, make sure the following fields are set as indicated below: Client: <your BW client number> User: BWREMOTE PW Status: saved 3. From area menu /SAND/0_MAINP, select Setup > Enable authorization check for nearline users or start transaction SU01. Verify the following settings for the user BWREMOTE: Logon data tab: User Type: System Profiles tab: S_BI-WHM_RFC 1.4 Configuring the Log Object To create one log object and two log sub-objects, complete the following steps: 1. From area menu /SAND/0_MAINP select Setup > Configure log objects or start transaction SLG0. 2. Create a log object called ZNLS: a. Select Objects in the Dialog Structure pane. b. Click New Entries. c. Enter the object name (ZNLS) and the desired object text (for example, "SNIC Application Log"). 6

16 Figure 5: The ZNLS Log Object 3. Create a sub-object of the ZNLS log object called ZNLS_DATA: a. Select the ZNLS log object in the list. b. Double-click Sub-objects in the Dialog Structure pane. c. Click the New Entries button. d. Enter the sub-object name (ZNLS_DATA) and the desired sub-object text (for example, "SNIC NLS data"). Figure 6: Log Sub-Objects 4. Save the log objects, choosing the appropriate SAP Workbench Request. The names of these objects must also be entered in the configuration table /SAND/0CONFIG. For more information, see section 1.7 Configuring. 7

17 1.5 Creating an InfoArea for Automatically Created Objects To create an InfoArea for automatically created Virtual InfoProviders, complete the following steps: 1. From area menu /SAND/0_MAINP, select Setup > Maintain default InfoArea and activate BI content or start transaction RSA1. 2. In the Modeling pane on the left, select InfoProvider. 3. In the InfoProvider list on the right, right-click the "InfoProvider" heading and choose Create InfoArea from the menu. 4. Name the InfoArea ZSAND_INFOPROVIDER and type SAND Nearline InfoArea in the Description field. 5. Click the green checkmark to create the InfoArea, choosing the appropriate SAP Workbench Request. (If the popup message "Make repairs in foreign namespaces only if they are urgent" appears, click the green checkmark.) Figure 7: The ZSAND_INFOPROVIDER InfoArea This InfoArea also needs to appear in the configuration table /SAND/0CONFIG. For more information, see section 1.7 Configuring. 8

18 1.6 Activate BI Content from Informatica To activate BI content delivered by Informatica, complete the following steps: 1. From area menu /SAND/0_MAINP, select Setup > Maintain default InfoArea and activate BI content or start transaction RSA1. 2. On the BI Content tab in the left pane, select InfoObjects by InfoAreas : Figure 8: BI Content InfoObjects by InfoAreas 3. Drag and drop the following objects from the middle pane to the right pane: InfoArea /SAND/INFOAREA InfoObject catalog /SAND/IOC_KF InfoObject /SAND/DUMMY If prompted to select one or more source systems, click the green checkmark on the prompt, then click the X in the upper-right corner of the Select Source Systems dialog. Since the objects that are being installed are not source-system dependent, no source system needs to be selected. 9

19 The following screen appears: Figure 9: BI Content Selected Objects Pane 4. On the right-hand (Collected Objects) pane, make sure that all Install field check boxes are enabled, while none of the Match (X) or Copy check boxes should be enabled. 5. Install the selected objects by choosing Install> Install on the right-hand (Collected Objects) pane: Figure 10: BI Content Install If the popup message "Make repairs in foreign namespaces only if they are urgent" appears, click the green checkmark. The install may ask for a package. If so, a package for transport purposes may need to be selected. 10

20 The installation of these objects should not display any errors (double-click the appropriate Date/Time/User entry to view the installation messages): Figure 11: BI Content Successful Install 1.7 Configuring Nearline Settings To finalize the installation, from the /SAND/0_MAINP area menu, select Configuration > Configure ILM Nearline or use transaction /SAND/0_CONFIG to configure the nearline settings. Note that, if authorization checking is enabled, this program requires either the YSAND_NLS001 or ZSAND_NLS001 authorization profile in the user's account, or else it runs only in read-only mode. For more information, see chapter 2 Setting Up Authorization Checking RSDANLCON Settings Since the nearline connection information has not yet been defined in the RSDANLCON table, the initial start of the /SAND/0_CONFIG program generates an information message that states there is no connection configured in RSDANLCON. To add a nearline connection to the RSDANLCON table, complete the following steps: Note: Access to transaction SM31 is required for this procedure. 11

21 1. Click the green checkmark on the /SAND/0_CONFIG popup to edit the RSDANLCON table (which should be empty). Figure 12: Initial RSDANLCON Table 2. Click the New Entries button on the toolbar (F5) to bring up the New Entries screen. 3. Enter the following settings only: Nearline Conn.: SAND Name of Class: /SAND/CL0_NLS_CONNECTION 4. Click Save. Figure 13: New RSDANLCON Entry 12

22 While these entries are being saved, error messages may appear in the lower panel. These can be ignored, as the SCHEMA for the new connection will be configured using the /SAND/0_CONFIG program. Figure 14: The RSDANLCON Entry Saved Once the install is completed, the error in the screenshot above should no longer occur. 5. Click Back to return to the /SAND/0_CONFIG screen Configuring ILM Nearline Program (/SAND/0_CONFIG) Note: This section pertains to configuring the current system only. For more information about how to use the /SAND/0_CONFIG program to configure multiple systems in the SAP landscape, see chapter 3 Per-system Configuration. Also note that the /SAND/0_CONFIG program makes it possible to directly change the local configuration for any unlocked system in the SAP landscape. However, such changes to non-development systems should be avoided except in an emergency. The recommended procedure is to change the configuration in the development instance using /SAND/0_CONFIG, and then transport that configuration to the target system. Once the RSDANLCON table has an entry for the nearline connection, you can use the /SAND/0_CONFIG program to configure the other settings. 13

23 Communication Figure 15: Initial ILM Nearline Configuration Screen ILM Nearline uses file-based or HTTP-based communication to exchange data between the SAP Nearline Add-On and the Nearline Service. The SAP Nearline Add-On and the Nearline Service exchange control information and nearlined data. The control information is stored in small XML structures. The nearlined data is the data that is stored in the nearline store. The data is stored in CSV files. ILM Nearline has the following options to exchange the data: File-Based Communication All data exchanged between the SAP Nearline Add-On and the Nearline Service is stored in a shared tasks directory. You configure the location of the task directory when you install the ILM Nearline services. HTTP-Based Communication All data exchanged between the SAP Nearline Add-On and the Nearline Service is transferred through HTTP. You configure port number for communication when you install the ILM Nearline services. Combination of File-Based and HTTP-Based Communication 14

24 The XML structures that contain control information are transferred through HTTP. The CSV files that contain the nearlined data are stored in a shared tasks directory and are transferred through the file system Configuration Settings The configuration settings are the following: Configurable Item Authorization Class Description The authorization class currently used for the SAP system. For more information about authorization classes, see chapter 2 Setting Up Authorization Checking. SAP Nearline Add-On Configuration Nearline Connection The connection to which the configuration settings apply. Initially, only the default connection should be available. Connection to Nearline Service For information about managing nearline connections, see section Skip Buffer No. range no. Wait response sec. Wait response tick Object Subobject InfoArea Flag for bypassing the buffer. Include this flag only if requested by Informatica Global Customer support. The interval ID created for the /SAND/0NLS number range object (see section 1.1) Value to be used as the timeout setting during transfers. Default: (see online help). Default: 1.0 (see online help) The log object name (see section 1.4, Configuring the Log Object) The name of the sub-object of the log object (see section 1.4, Configuring the Log Object) The InfoArea for automatically created Virtual InfoProviders (see section 1.5, Creating an InfoArea for Automatically Created Objects) File Configuration 15

25 Configurable Item Filename Description The logical file used for data exchange via the shared tasks directory. If this field has a value, and the URL to the Nearline Service field also has a value, XML structures will be transferred via HTTP while CSV data (InfoProvider content) will be transferred via the tasks directory. If all data is to be transferred via HTTP, leave this field empty. Wait file fini. sec. Wait file fini. tick Delete Time Default: 2.0 (see online help); if using Nearline Service version or higher, enter 0 to disable additional wait time Default: 0.01 (see online help) Specifies when files from the tasks directory will be automatically deleted. Possible values: Never Immediate (default) Close Delete State Specifies in what cases files will be automatically deleted from the tasks directory. Possible values: On success (default) Force HTTP Configuration URL to Nearline Service URL for HTTP communication between SAP BW and the Nearline Service. It has the following format: name or IP address>:<port> For example: If this field has no value, data will be exchanged via the tasks directory defined by the Filename setting. If this field has a value, and the Filename field (see above) also has a value, XML structures will be transferred via HTTP while CSV data (InfoProvider content) will be transferred via the tasks directory. 16

26 Configurable Item Server Group Description Server group to be used for parallel execution of HTTP communication activities. To create a server group, use the RZ12 transaction. Table 1: ILM Nearline Configuration Settings Note that if an invalid setting is made, attempting to save the settings or execute the configuration checker program will generate an error on the taskbar at the bottom of the screen. The error message indicates that the attribute No. range no. of the connection is initial. Warnings, on the other hand, are not displayed on the taskbar. If any warnings exist, they can be viewed when the configuration checker program /SAND/0_CONFIG_CHECK is executed. For more information, see section Managing Nearline Connections There can be multiple nearline connections defined for the system, each with its own configuration settings. For instance, one connection can be set to use file-based communication, while another connection uses HTTP, and yet another connection combines file-based and HTTP. The actual nearline connection information is stored in the RSDANLCON table, described in section You modify the RSDANLCON table when you create new connections. To create new connections, select Configuration > Configure ILM Nearline from area menu /SAND/0_MAINP or start transaction /SAND/0_CONFIG. Select "Maintain RSDANLCON" from the NLS Configuration menu, or press Shift+F9. Initially, only the default nearline connection is available, but other ones defined in the RSDANLCON table can be subsequently added or removed. For detailed information about adding new connections and deleting existing connections, refer to section 3.3 Managing Nearline Connections. Note that if a nearline connection is use by a DAP in an SAP system, the DAP can only be transported to another system if the nearline connection with the same name exists in the target system Checking ILM Nearline Configuration The /SAND/0_CONFIG_CHECK program can be run at any point during configuration to check the validity of the settings and optionally generate a report. To check the ILM Nearline configuration, select Configuration > Verification > Verify ILM Nearline configuration from area menu /SAND/0_MAINP or start transaction /SAND/0_CONFIG_CHECK. To run the program with a summary report, use one of the following options: Click the LIST AND CHECK CONFIGURATION button on the toolbar. -or- 17

27 Select "List Configuration" from the configuration menu. -or- Press F9. This will generate a report listing the parameter values for each connection, as well as a summary of warnings and/or errors, if any (warnings are preceded by the letter "W" and a yellow triangle; errors are preceded by the letter "E" and a red circle). A list of the configuration check messages can be viewed by clicking DISPLAY MESSAGES. Figure 16: ILM Nearline Configuration Check Report To run the program without the summary report, use one of the following options: Click the CHECK CONFIGURATION button on the toolbar. -or- Select "Check Configuration" from the configuration menu. -or- 18

28 Press Ctrl+F3. This will bring up a list of the configuration check messages. The following messages are examples of configure check messages: Messages of ILM Nearline configuration check. (SYSID=TA1) Messages ILM Nearline configuration check for connection <connection> No configuration error detected for connection <connection> Other Functions The /SAND/0_CONFIG program also allows users to run connections tests and configure schemas for data exchange. To test a connection between SAP and the Nearline Service: Click "Connection Test" on the toolbar. This starts the /SAND/0_UTIL_TEST_CONNECTION program, which tests the currently displayed nearline connection. For more information, refer to section 1.9 Testing the Configuration. To configure a schema for data exchange: Click "Configure SCHEMA" on the toolbar. This starts the /SAND/0_CONFIG_SCHEMA program, which is used to maintain the /SAND/0_NLS_CFGP table. For more information, refer to section 1.8 Configuring the Schema for Data Exchange Saving the Configuration Settings Once the desired configuration is done, the settings must be saved in order to enable them. To save the configuration settings: Click SAVE on the toolbar. -or- Select "Save Configuration" from the configuration menu. -or- Press Ctrl+S. 19

29 Before the configuration is actually saved, the /SAND/0_CONFIG_CHECK program is called to check the settings. The results of the check are displayed in a window. The following figure shows an example of configuration warnings: Figure 17: List of Configuration Warnings If there are no issues with the settings, or the warnings are expected and acceptable, click the green checkmark to accept the results and continue. Otherwise, click cancel and return to the settings screen to make corrections. 1.8 Configuring the Schema for Data Exchange Establishing a connection between the SAP BW system and the File Archive Service requires configuration of a File Archive Service schema for data exchange. The association between a connection and schema is stored in the /SAND/0_NLS_CFGP table. To access this table, select Configuration > Configure ILM Nearline from area menu /SAND/0_MAINP or start transaction /SAND/0_CONFIG_CHECK. Click Configure Schema. This runs program /SAND/0_CONFIG_SCHEMA. If multiple SAP BW systems are connecting to the Nearline Service, a different schema must be specified for each connection. However, Informatica does not recommend the use of a single Nearline Service instance for multiple SAP systems. If a single ILM Nearline system is used by multiple SAP systems, an upgrade of the ILM Nearline system might entail an upgrade of each of the SAP systems. Also, a system refresh will not be possible if multiple SAP systems are connected to a single ILM Nearline system. When you configure the schema, you can select the following options: Help ( ) provides an overview of the program List Schemas displays a list of all File Archive Service schemas available via the currently selected connection (for more information, see section 1.8.2). List Configuration displays all entries in the /SAND/0_NLS_CFGP table. Save FAS Schema allows you to change the value of the File Archive Service Schema field for the currently selected Nearline Connection. Each alteration to this value is 20

30 tracked, along with the timestamp when the change was made and the user account that performed it. Note that specified schema names should have this form: Z_<system ID>_<client number> If you see a warning message that provides the default value for the parameter, press ENTER to continue. Any other reaction such as pressing a button aborts your initial activity. This is SAP standard behavior. Note that during a system refresh the schema name does not need to be modified in the refreshed system (even though it contains the previous system ID), as the refreshed ILM Nearline system and the SAP system will both contain the same schema name Existing Connections The initial screen for a connection that is already used by a DAP will appear as follows: Figure 18: Existing Connection Note that in this case the File Archive Service Schema field is disabled and does not accept input. Five commands are available on this screen: Help List Schemas List Configuration List DAPs using connection displays a list of all DAPs that use the currently selected connection. Enable changes to FAS Schema makes it possible to change the value of the File Archive Service schema. WARNING: Once the schema is set in the SAP system, it should not be changed unless the proper adjustments are made to the File Archive repository. Changes to this schema after that data has been nearlined can cause loss of data and make the ILM Nearline systems inconsistent. The decision to change this schema should not be taken lightly. 21

31 Note that even though it is recommended to have a schema name that is associated with the SAP system ID, it is not necessary to change the schema when a system is refreshed to another. Changes to the schema should only be done when absolutely necessary Retrieving Information about File Archive Service Schemas The List Schema function retrieves schema information from the File Archive Service and may take a few seconds to display results. The File Archive Service schema list appears as follows: Figure 19: File Archive Service Schemas To see a list of all tables belonging to a particular schema, double-click on the appropriate row in the list. 1.9 Testing the Configuration To test the configuration, select Configuration > Verification > Verify ILM Nearline configuration from area menu /SAND/0_MAINP or start transaction /SAND/0_CONFIG_CHECK. To check the communication between SAP and the Nearline Service, select Configuration > Verification > Test connection to Nearline Service from area menu /SAND/0_MAINP or start transaction /SAND/0_TEST_CONNECT. If the system is properly configured and the Nearline Service is running, a message appears in the last line of the list that indicates the connection test ended successfully. If the connection test fails, use transaction SMICM to verify if the HTTP service is up and running on the system, and to activate the service if necessary. For more information, see the "Troubleshooting HTTP Communication" section in the ILM Nearline for SAP BW Administration Guide (BW 7). 22

32 1.9.1 Viewing ILM Nearline Version Information To view version information for the installed ILM Nearline software components, double-click anywhere in the list produced by the configuration test. This will display a list of the installed components, along with certain system information, such as host name, environment details (SAP system ID, connection name), and the timestamp for when the version information was retrieved. Figure 20: ILM Nearline Version Information More information about this Status Information window, including detailed descriptions of the fields, can be found in the Nearline Service and File Archive Service Components section of the ILM Nearline for SAP BW Administration Guide. 23

33 2 Setting Up Authorization Checking ILM Nearline supports the use of authorization profiles, set at the SAP system level, to limit the activities of any user. When authorization checking is enabled, a user must possess required permissions to execute certain Nearline Service functions, or to execute them in non-read-only mode. 2.1 Selecting the Authorization Class for an SAP System Before assigning authorization profiles to users, the appropriate authorization class must be selected for the SAP system. The authorization classes provided by Informatica are the following: Authorization Class /SAND/CL0_NLS_AUTHORIZATION_D (default) Description All activities are permitted except for ones that involve the deletion of archive requests or files: /SAND/0_DELETE_NLS_REQUEST /SAND/0_UTIL_FILE Important: This restriction applies to all users, including ones that have the SAP_ALL authorization. If deletion activities are needed, the authorization class must be changed to one of the other classes. /SAND/CL0_NLS_AUTHORIZATION_E /SAND/CL0_NLS_AUTHORIZATION_Y /SAND/CL0_NLS_AUTHORIZATION_Z All activities are permitted with no restrictions. Users require assigned authorization profiles to perform certain activities. This class uses the Y* authorization object (see below). This is identical to the /SAND/CL0_NLS_AUTHORIZATION_Y class, except that it uses the Z* authorization object (see below). Table 2: Authorization Classes You can change the authorization class when you configure ILM Nearline. By default, /SAND/CL0_NLS_AUTHORIZATION_D is set, which disallows all deletion activities by nonadministrator users. Either /SAND/CL0_NLS_AUTHORIZATION_Y or /SAND/CL0_NLS_AUTHORIZATION_Z is used for authorization checking. The /SAND/CL0_NLS_AUTHORIZATION_E authorization class should be used cautiously, if at all, as it can be dangerous to allow every user to execute all Nearline Service functions. 24

34 To select the authorization class for the system: 1. From area menu /SAND/0_MAINP, select Configuration > Configure ILM Nearline or start transaction /SAND/0_CONFIG. 2. Click anywhere in the Authorization Class value and press the button next to the Authorization Class field. The list of authorization classes appears. Figure 21: Authorization Class Field 3. Select the desired authorization class, and then click the Continue button. 4. After all desired changes are made, save the configuration settings and add them to a transport order. For more information about these last steps, see section 3.6 Saving the Per-system Settings. 2.2 Assigning Authorization Profiles to Users When the authorization class has been set to either /SAND/CL0_NLS_AUTHORIZATION_Y or /SAND/CL0_NLS_AUTHORIZATION_Z, specific authorization profiles can be added to any user account. There are two different authorization objects that correspond to the two aforementioned authorization classes: YSAND_NLS0 (associated with /SAND/CL0_NLS_AUTHORIZATION_Y) ZSAND_NLS0 (associated with /SAND/CL0_NLS_AUTHORIZATION_Z) These two authorization objects actually provide the exact same predefined authorizations and profiles. The reason for the redundancy is because the objects will be in the customer namespace, since SAP does not support a private namespace for these objects. Having two identical authorization objects means that, just in case a customer has already defined an object with the same name, the other authorization object can be used instead. The two authorization objects provide the following authorizations/profiles: YSAND_NLS0 Profile ZSAND_NLS0 Profile Activity Code Authorization Category / Nearline Service Usage YSAND_NLS000 ZSAND_NLS000 (everything) 25

35 YSAND_NLS001 ZSAND_NLS Change YSAND_NLS002 ZSAND_NLS Delete YSAND_NLS003 ZSAND_NLS Transport Full use of area menu /SAND/0_MAINP Configuration > Configure ILM Nearline or transaction /SAND/0_CONFIG. (Programs /SAND/0_CONFIG and /SAND/0_CONFIG_SCHEMA). Read-only access if this authorization is absent. Full use of area menu Administration > Delete nearline requests or transaction /SAND/0_DELETE_REQ. (Program /SAND/0_DELETE_NLS_REQUESTS). YSAND_NLS004 ZSAND_NLS Extended Maintenance YSAND_NLS005 ZSAND_NLS Check Read-only access if this authorization is absent. Use of area menu Administration > ILM Nearline Virtual InfoProviders > Transport Virtual InfoProviders or transaction /SAND/0_VIRT_TRANSP. (Program /SAND/0_VIRTUAL_MAINTAIN_META.) The program aborts if this authorization is absent. Full use of area menu Administration > Maintain Nearline Service Directories or transaction /SAND/0_UTIL_FILE. (Program /SAND/0_UTIL_FILE.) If this authorization is absent, only the List files action will be available as the service type. Use of area menu /SAND/0_MAINP Configuration > Verification > Verify Consistency between SAP and Nearline Service, area menu /SAND/0_MAIN Verification > Verify Consistency between SAP and Nearline Service, or transaction /SAND/0_CONSIS_CHECK. (Program /SAND/0_CONSISTENCY_CHECK) The program aborts if this authorization is absent. 26

36 YSAND_NLS006 ZSAND_NLS Model Table 3: Authorizations and Profiles Full use of area menu Administration > ILM Nearline virtual InfoProviders > Maintain virtual InfoProviders or transaction /SAND/0_VIRT_MAINT. (Program /SAND/0_VIRTUAL_MAINTAIN). Read-only access if this authorization is absent. All other Nearline Service programs can be accessed and executed without special authorization. To add one or more authorization profiles to a user account: 1. From area menu /SAND/0_MAINP, select Setup > Enable authorization check for nearline users or start transaction SU Specify the user name in the User field, and then click the Create button (F8) to create a new user, or the Change button (Shift+F6) to edit an existing user. The Maintain User screen appears. Figure 22: User Maintenance Initial Screen 27

37 Figure 23: Maintain User Screen 3. On the Profiles tab, add the desired authorization profile(s) from Table 3 above. 28

38 Figure 24: Assigned Authorization Profiles Note that the profile name to specify depends on which authorization class is configured. For example, if /SAND/CL0_NLS_AUTHORIZATION_Y is the authorization class for the system, and the Change authorization is being added, the profile to add is "YSAND_NLS001". Conversely, if the authorization class is set to /SAND/CL0_NLS_AUTHORIZATION_Z, the Change profile is "ZSAND_NLS001". 4. When the user configuration is complete, click Save. The user configuration is saved, and the User Maintenance: Initial Screen is displayed again. Note: A user whose account profile has been changed will have to log off and then log in again before the changes take effect. 2.3 Examples Assume a user has been assigned the YSAND_NLS001 (Change) and YSAND_NLS005 (Check) authorization profiles. The user is therefore authorized to execute the /SAND/0_CONSISTENCY_CHECK program, as well as the /SAND/0_CONFIG and /SAND/0_CONFIG_SCHEMA programs in write mode (as opposed to read-only mode). If the user attempted to start /SAND/0_VIRTUAL_MAINTAIN_META, the user receives an error that the user is not authorized for activity 21. The error occurs because the user does not have the YSAND_NLS003 authorization (note that 21 is the activity code for this authorization). If the user ran /SAND/0_DELETE_NLS_REQUESTS, there would be a warning that the program is running in read-only mode, since the user does not have the YSAND_NLS002 authorization: Similarly, if the user ran /SAND/0_UTIL_FILE program, even though the user does not have the YSAND_NLS004 authorization, only the "List files" service type is available to the user. The user receives a warning that the service type is restricted due to missing authorizations. 29

39 3 Per-system Configuration In addition to configuring the current system settings, the /SAND/0_CONFIG program can also be used to configure multiple systems in the SAP landscape. This program allows variable parameters to be set on a per-system, and even per-connection, basis. The variant settings can then be exported to transport orders for the target systems. Per-system configuration eliminates the need to open each SAP system for setup or to make changes to their configuration. The main configuration for all systems will be transportable from the definition that can be set up in the development environment. Indeed, this is the recommended procedure for changing the configuration across the landscape. While the /SAND/0_CONFIG program can directly change the local configuration for any unlocked system, this should never be done in non-development systems unless there is an emergency. Note that, in order for configurations defined on the development system to be transportable to other systems, the schema will need to be set in all systems where the SAP Nearline Add-On is installed. The schema setup must be done when the ILM Nearline installation is complete. Before setting up the schema, the SAP Nearline Add-On configuration must be manually configured or transported from another system. 3.1 Configuration Tables The /SAND/0_CONFIG program reads the current system configuration parameters from the /SAND/0_NLS_CFG and /SAND/0CONFIG tables, gets information about the different systems in the SAP landscape from the /SAND/0_SYSIDS table, and uses the RSDANLCON table for nearline connection information. Per-system settings made through /SAND/0_CONFIG are stored in the /SAND/0_NLS_VAR table. 3.2 The /SAND/0_CONFIG Program Use program /SAND/0_CONFIG program for Per-system configuration. To access the program, select Configuration > Configure ILM Nearline from area menu /SAND/0_MAINP or start transaction /SAND/0_CONFIG. Note that this program requires the proper authorization profiles in the calling user's account to run in write mode, as discussed in chapter 2, 30

40 Setting Up Authorization Checking. Before per-system configuration is enabled in /SAND/0_CONFIG, the parameter values displayed on-screen are the existing settings for the current system and connection. Figure 25: Before Enabling /SAND/0_CONFIG Per-system Settings To enable per-system configuration in /SAND/0_CONFIG, one or more SAP system IDs must be added to the /SAND/0_SYSIDS table Adding New SAP System IDs To add new SAP system IDs for per-system configuration, complete the following steps: 1. From area menu /SAND/0_MAINP, select Configuration > Configure ILM Nearline or start transaction /SAND/0_CONFIG. 2. Click Maintain SYSIDS, select "Maintain SYSIDS" from the NLS Configuration menu, or press Shift+F8. This will open the "SAND NLS: list of SYSID" screen which is used to edit the /SAND/0_SYSIDS table. 31

41 Figure 26: The NLS: list of SYSID Screen 3. Click the New Entries button (F5) and enter one or more SAP system IDs in the SYSID list. These are the systems to which the per-system configuration settings will be applied. Figure 27: Enter SAP System IDs on the NLS: list of SYSID Screen 4. Click SAVE. You will be prompted to add the new SAP system ID(s) to a request. Figure 28: Select a Request for the New SAP System IDs 5. Select an existing request or specify a new one for the new SAP system ID(s), then click the green checkmark to continue. 6. On the NLS: list of SYSID screen, click BACK twice to return to the main screen. The screen will now have per-system checkboxes next to each configuration option. Now that multiple SAP system IDs are defined, per-system configuration can be used Activating Per-system Configuration Each configuration parameter on the screen has an associated checkbox. To enable per-system configuration, click the checkbox associated with a parameter so that a checkmark appears. A 32

42 new field displaying the current SAP system ID will appear below the Nearline Connection field. If the current system is not in the list of SAP System IDs, a warning will be displayed on the taskbar at the bottom of the screen. Figure 29: Current Nearline Connection and SAP System Now, the check-marked parameter can be set on a per-system/per-connection basis. To set any per-system/per-connection parameter, complete the following steps: 1. Click the checkbox associated with the desired parameter so that a checkmark appears. 2. Select the appropriate nearline connection: Click the icon in the Nearline Connection field and select the desired connection from the drop-down list. -or- Cycle through the list of connections by clicking the nearline connection navigation buttons on the toolbar: 3. Select the appropriate SAP system ID: Click the icon in the SAP System ID field and select the desired SAP system from the drop-down list. -or- Cycle through the list of SAP systems by clicking the system navigation buttons to the right of the SAP System ID field: 4. Change the value of the parameter specified in Step Repeat Steps 2-4 to change the parameter value for other connections and/or systems. The per-system configuration parameters are described in the next section (3.2.3). Note that if an invalid setting is made, a message appears in the taskbar at the bottom of the screen with a description of the error. Warnings, on the other hand, are only displayed when the configuration checker program /SAND/0_CONFIG_CHECK is executed. Refer to section 3.4 Configuration Checking for more information about this program. Important! If a checkbox does not have a checkmark, the associated value will apply to all SAP system IDs 33

43 defined in the per-system configuration. If you navigate to a different SAP system ID and change the value of an attribute without a checkmark, this change will apply to all systems. A per-system parameter can be reverted back to current system only by deselecting the associated checkbox (that is, removing the checkmark). However, if the per-system parameter has variant values defined, you will be prompted to select the value that will apply to the current system (Figure 30). Figure 30: Per-system Setting Removal Prompt Per-system Settings The per-system configuration items are the same ones described in section Configuring ILM Nearline Program (/SAND/0_CONFIG). In addition, there is an SAP System ID setting that appears only in the context of per-system configuration: Configurable Item SAP System ID Description The SAP system to which the configuration settings apply. Available SAP systems can be viewed in the associated drop-down list. To add new SAP systems, refer to section Adding New SAP System IDs. Table 4: Per-system Configuration Setting 3.3 Managing Nearline Connections There can be multiple nearline connections defined, each with its own configuration settings. For instance, one connection can be set to use file-based communication, while another connection uses HTTP, and yet another connection combines file-based and HTTP. Initially, only the default nearline connection is available to /SAND/0_CONFIG, but other ones can be subsequently added or removed. Note that in the most common implementations, only one connection is created in a system (the transfer method is usually unique for all objects in the system). Whatever connections are created, they must exist throughout the landscape to allow the transport of nearline objects. 34

44 To create and add a new nearline connection, complete the following steps: 1. Select Configuration > Configure ILM Nearline from area menu /SAND/0_MAINP or start transaction /SAND/0_CONFIG. 2. Select "Maintain RSDANLCON" from the NLS Configuration menu, or press Shift+F9. Figure 31: BW Archiving Connection to Nearline Storage Screen a. Click New Entries to open the New Entries screen. Figure 32: New Entries Screen b. Enter the connection name in the Nearline Conn. field, and select the class in the Name of Class field. The other fields can be left blank. c. Click SAVE. The taskbar at the bottom of the screen displays a message that indicates the data was saved. d. Click BACK to return to the Configure Informatica ILM Nearline screen. 3. Add the new connection: a. Click the New Connection icon. This will open the Configure Informatica ILM Nearline dialog box. b. In the Nearline Connection field, select an available connection. c. Click the green checkmark to add the connection. The newly added connection becomes the current connection. d. Enter a value in the No. range no. field. 35

45 e. Make other configuration changes for the connection as desired. f. Click SAVE. This will automatically run the /SAND/0_CONFIG_CHECK program to verify the settings and display the results in a window. g. Review the /SAND/0_CONFIG_CHECK output. If there are no issues relating to the new nearline connection, then the connection has been successfully added. h. Click the green checkmark to close the configuration check window. 4. Add the new connection to the /SAND/0_NLS_CFGP table: a. From the Configure Informatica ILM Nearline screen, click "Configure SCHEMA" on the toolbar to start program /SAND/0_CONFIG_SCHEMA. b. Make sure the Nearline Connection field displays the new connection that was set in the /SAND/0_CONFIG program (Step 2), and specify the File Archive Service schema to be used with the connection. c. Click the Save File Archive Schema button (Ctrl+F5) to save the connection/schema settings. d. Click BACK to return to the Configure Informatica ILM Nearline screen. To remove a nearline connection, complete the following steps: 1. Make sure that all DAPs using the connection have been deleted. 2. Remove the connection entry from the /SAND/0_NLS_CFGP table: a. Select Configuration > Configure ILM Nearline from area menu /SAND/0_MAINP or start transaction /SAND/0_CONFIG. b. Click "Configure SCHEMA" on the toolbar to start program /SAND/0_CONFIG_SCHEMA. c. On the Configure Schema for NLS Connections screen, select the connection in the Nearline Connection field that you want to remove. d. Click the "Delete connection from /SAND/0_NLS_CFGP" button. The File Archive Service schema field will become empty, and a message at the bottom of the screen will indicate that the connection has been removed. e. Click Back to return to the Configure ILM Nearline screen. 3. Remove the connection entry on the Configure ILM Nearline screen: a. In the Nearline Connection field, select the connection that will be deleted. b. Click the Delete Connection button on the toolbar (Shift+F2). The selected connection is deleted. 4. Remove the connection entry from the RSDANLCON table: 36

46 a. From the Configure Informatica ILM Nearline screen, select "Maintain RSDANLCON" from the NLS Configuration menu, or press Shift+F9. b. From the list of Nearline Connections, select the one to be removed. Figure 33: Select Nearline Connection for Deletion c. Click the Delete button on the toolbar (Shift+F2). The connection is removed from the list. d. Click SAVE. e. Click BACK to return to the Configure Informatica ILM Nearline screen. 5. On the Configure Informatica ILM Nearline screen, click SAVE. This will automatically run the /SAND/0_CONFIG_CHECK program to verify the settings and display the results in a window. 6. Review the /SAND/0_CONFIG_CHECK output. If there are no issues relating to the deleted nearline connection, then the connection has been successfully removed. 7. Click the green checkmark to close the configuration check window. 3.4 Configuration Checking At any point during per-system configuration, the /SAND/0_CONFIG_CHECK program can be run to check the validity of the settings and optionally generate a report. To run /SAND/0_CONFIG_CHECK with a summary report: Click the LIST AND CHECK CONFIGURATION button on the toolbar. -or- Select "List Configuration" from the NLS Cconfiguration menu. -or- Press F9. 37

47 This will generate a report listing the common and per-system parameter values for each connection, as well as a summary of warnings, if any. Warnings are preceded by the letter "W" and a yellow triangle. The /SAND/0_CONFIG program should trap errors during per-system configuration and force users to correct them, but if any appear in the configuration check report, they will be preceded by the letter "E" and a red circle. A list of the configuration check messages can be viewed by clicking DISPLAY MESSAGES. Figure 34: /SAND/0_CONFIG_CHECK Report To run /SAND/0_CONFIG_CHECK without the summary report: 38

48 Click the CHECK CONFIGURATION button on the toolbar -or- Select "Check Configuration" from the NLS Configuration menu -or- Press Ctrl+F3. This will bring up a list of the configuration check messages. Figure 35: Configuration Check Messages Types of Configuration Checking There are two types of configuration checks: "Deep" checks: Done when per-system configuration is disabled or when the system ID of the current SAP system is being checked. "Weak" checks: Carried out if per-system configuration is active but the current SAP system is checking for a different system ID. In general, weak checks mention initial values as errors only. When doing deep checks, the existence of objects (like the interval of the number range object) is checked. The following checks on the configuration are currently implemented: CL_RSDA_NEARLINE_READER=>C_DEFAULT_PACKAGE_SIZE (constant defined within SAP code describing the package size) must be smaller than (constant within Informatica code describing the maximum amount of characters that can be handled by a single package; this is currently limited by the size of a string variable). Note that this SAP configuration value is usually set to 20 MB by default and should not be changed unless you are instructed otherwise. Check of RFC connection definition. 39

49 The above checks are connection-independent, whereas the following checks are done for each connection and every configured SYSID in table /SAND/0_SYSIDS: Contents of table RSDANLCON: o o Is there an entry in the table for the current connection? Does this entry refer to class /SAND/CL0_NLS_CONNECTION? Connection to Nearline Service: One of the fields Filename or URL to SNIC must have a value. Skip Buffer: A warning will be displayed if this flag is marked. No. range no.: This field must have a value. The existence of the interval is only checked during a deep check. Wait response sec.: This value must be larger than 1 otherwise an error will be generated. A warning will be listed if a value other than 7200 (default) is used. Object: o o Deep check: A log object must exist. Weak check: A log object must not be blank. Subobject: o o Deep check: A log sub-object must exist. Weak check: A log sub-object must not be blank. InfoArea: o o Deep check: InfoArea must exist. Weak check: InfoArea must not be blank. Filename: o o o Is the given value referring to a valid entry? If FILENAME is referring a valid entry, does this refer to a valid logical path? If both conditions are met, will the filename name be replaced correctly? Wait response tick. (dependency: Filename must have a value): The value must be larger than 0, and it must not be larger than Wait response sec. / 5. Wait file fini. sec. (dependency: Filename must have a value): The value must be less than or equal to 120. Wait file fini. tick (dependencies: Filename must have a value; Wait file fini. sec. must be larger than 0): The value must be larger than 0, and it must not be larger than Wait file fini. sec. / 5. Delete Time, Delete State (dependency: Filename must have a value): Check that only the permitted values are used. 40

50 URL to NLS Service: If the field has a value, it must match the following characteristics: o o o o o A list of names separated by "." characters, having at least one non-digit character each Besides digits and characters, the hyphen "-" and underscore "_" characters are allowed in the middle of each name Names consisting of characters only must have a length of at least two characters Names starting and ending with digits must have a length of at least three characters IPv4: tuple of 4 decimals without leading zeros, separated by "." characters, having a value between 0 and 255 o IPv6: tuple of 8 hexadecimal values enclosed by [ and ], separated by ":" characters, consisting of 1 to 4 hexadecimal digits each o Replacing of tuples by "::" is not supported. Server Group (dependency: URL to NLS Service must have a value): o o Deep check: if there is a value, an existing SAP server group must be referenced. Weak check: none. 3.5 Other Functions The /SAND/0_CONFIG program also allows users to run connections tests and configure schemas for data exchange. To test a connection between SAP and the Nearline Service: Click "Connection Test" on the toolbar. This starts the /SAND/0_UTIL_TEST_CONNECTION program, which tests the currently displayed nearline connection. To configure a schema for data exchange: Click "Configure SCHEMA" on the toolbar. This starts the /SAND/0_CONFIG_SCHEMA program, which is used to maintain the /SAND/0_NLS_CFGP table. 41

51 3.6 Saving the Per-system Settings Once the desired per-system configuration is done, the settings must be saved before they can be added to a transport. To save the per-system configuration: Click SAVE. -or- Select "Save Configuration" from the NLS Configuration menu -or- Press Ctrl+S. Before the per-system configuration is actually saved, the /SAND/0_CONFIG_CHECK program is called to check the settings. The results of the check are displayed in a window. For example: Figure 36: List of Per-system Configuration Warnings If there are no issues with the settings, or the warnings are expected and acceptable, click the 42