User manual SAS SAS IT MANAGEMENT ADAPTER 3.2 FOR SAP

[. . . ] SAS IT Management Adapter 3. 2 for SAP User's Guide ® The correct bibliographic citation for this manual is as follows: SAS Institute Inc. Cary, NC: SAS Institute Inc. SAS® IT Management Adapter 3. 2 for SAP: User's Guide Copyright © 2010, SAS Institute Inc. , Cary, NC, USA All rights reserved. For a hard-copy book: No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, or otherwise, without the prior written permission of the publisher, SAS Institute Inc. For a Web download or e-book: Your use of this publication shall be governed by the terms established by the vendor at the time you acquire this publication. [. . . ] For further details about SAS Unicode server, see the SAS support site. Installation and Customization of SAS IT Management Adapter for SAP 41 Note: Steps 1­4 are not applicable for z/OS, as there is no Unicode server in a z/OS environment. Deploying SAS IT Management Adapter for SAP Jobs and Tables Metadata After the installation of SAS IT Management Adapter for SAP, deploying jobs and tables metadata for the adapter is a manual process. In a Windows environment, when you install the adapter, the files in the following screen are available in the path C:\Program Files\SAS\SASITResourceManagementAdapterSAPData\3. 2\CustomSASCode While working in a Windows or UNIX environment, delete the following files; they are specific to MVS: preprocglobal_mvs. sas get_sap_lib_info_mvs. sas In a z/OS environment, delete the following files; they are specific to a Windows or UNIX environment: preprocglobal. sas get_sap_lib_info. sas After you delete the preceding files in a z/OS environment, you need to rename the remaining files by deleting _mvs. To deploy metadata objects (in this case, jobs and tables) for the SAS IT Management Adapter for SAP, use the standard metadata import and export features of the SAS Data Integration Studio. The components for the SAS IT Management Adapter for SAP are stored as package files. The standard Install location in a Windows environment for storing the package file is C:\Program Files\SAS\SASITResourceManagementforAdapterSAPData\3. 2\SASPackages Note: The above install location is platform-dependent, and it can be changed as needed. For example, the path would be in z/OS <SASHOME>/SASITResourceManagementAdapterforSAPData/3. 2/ SASPackages 42 Deploying SAS IT Management Adapter for SAP Jobs and Tables Metadata Chapter 4 As the SAS packages are installed in the z/OS, you need to transport them manually via File Transfer Protocol (FTP) to the PC where the client is running. This enables the import function of the SAS Data Integration Studio to read the SAS package files. To deploy tables and jobs, complete the following steps: 1 2 Open SAS Data Integration Studio with Connection Profile for the user. In the metadata profile, select the project that you defined when you added the SAP server and SAP library. The SAS IT Management Adapter for SAP is imported to the project that you select in this step. 3 Right-click Products in the SAS Folders Tree, and then click Import. Display 4. 3 SAS Data Integration Studio: Products In the Import from SAS Package dialog box, click Browse, and then open the SASPackages folder. You can find the SASPackages folder within the Install folder that you created at the time of installation. Retain the default options and continue. Installation and Customization of SAS IT Management Adapter for SAP 43 Display 4. 4 Export SAS Package Wizard The objects to be imported appear. Display 4. 5 Select Objects to Import 6 Click Next to continue. The following screen appears. Display 4. 6 Summary, Import from SAS Package Window 7 Review the summary, and then click Next. A progress indicator appears. 44 Deploying SAS IT Management Adapter for SAP Jobs and Tables Metadata Chapter 4 Display 4. 7 Important Objects Window 8 The Import from SAS Package dialog box displays a completion message. If the import process fails, click View Log, check for messages, and take appropriate action. Display 4. 8 Import Complete Message Note: Use the following sequence while performing the preceding steps to deploy application folders, data sources, and jobs. SASITMAdapterforSAP_DIS_ProductFolders. spk SASITMAdapterforSAP_DIS_AppFolders. spk Installation and Customization of SAS IT Management Adapter for SAP 45 SASITMAdapterforSAP_DIS_Tables. spk SASITMAdapterforSAP_DIS_Jobs. spk Note: For importing the second package SASITMAdapterforSAP_DIS_AppFolders. spk, right-click System in the SAS Folders Tree, and then click Import. For other packages, right-click Products in the SAS Folders tree and then click Import. While importing to the package file SASITMAdapterforSAP_DIS_Tables. spk, perform the following steps: 9 In the Import from SAS Package dialog box, select the package SASITMAdapterforSAP_DIS_Tables. spk. 10 Under Import Options, select All Objects, and then click Next. Retain the default options and continue. Display 4. 9 SAS Application Servers Window 11 Verify that the SAS Application Servers is set correctly as SASITRM. Select Next. 46 Deploying SAS IT Management Adapter for SAP Jobs and Tables Metadata Chapter 4 Display 4. 10 Other Servers Window 12 Select an SAP server. Installation and Customization of SAS IT Management Adapter for SAP 47 Display 4. 11 Directory Paths, Import from SAS Package Window 13 Verify that all directories and paths appear correctly. Note: The SAS log might contain the warning the person ETL Developer 1 was not found. [. . . ] e n, communication steps mig occur bet ght tween the ser rver and the front-end system. During a round trip, th server tra r he ansfers data f the contro to the fron for ols nt-end system The user m. The t ks it time line for every s on nce rk nce round trip is measured o the server in GUI time. The influen of networ performan and front-end sys stem perform mance on the SAP respons time can b defined wi the help o GUI se be ith of time. [. . . ]