Message Alerting for SAP NetWeaver PI Advanced Adapter Engine Extended Applies to SAP NetWeaver PI Advanced Adapter Engine Extended 7.30. Summary This article explains how to set up Message Alerting for the java-only SAP NetWeaver PI AEX. Since PI Message Alerting is done on ABAP stack, it is necessary to configure some ABAP system (an ABAP Integration Server or Solution Manager System, e.g.) as central Monitoring System for the AEX, on which the alerts are processed then. Author: Stefan Boller Company: SAP AG Created on: 6 May 2011 Author Bio Stefan Boller is Development Architect for SAP NetWeaver PI. He works with SAP since almost 10 years and is responsible for PI Monitoring and Operations. 2011 SAP AG 1
Table of Contents Introduction... 3 Configuration of Message Alerting... 3 Overview... 3 Identify an ABAP System... 3 Add AII Config Service Properties... 3 Create Users on CEN... 6 Activate ICF Services... 6 Configure Alerting... 7 Using Message Alerting... 8 Limitations... 8 Related Content... 9 Copyright... 10 2011 SAP AG 2
Introduction With SAP NetWeaver Process Integration 7.30 a new java-only installation option of PI is introduced, the so called Advanced Adapter Engine Extended (AEX). This simplifies significantly the operation of PI and reduces the total cost of ownership. However, currently it is not possible out-of-the-box to use message alerting with this installation, since it is still only available on the ABAP stack. This article explains how you can work around this limitation und use an arbitrary ABAP system as Central Monitoring Server (CEN) for your AEX. This Central Monitoring Server will then receive also the alerts from AEX, processes them, and forward them according to the alert rules, which are well known from the double stack installation. Configuration of Message Alerting Overview As prerequisite for using Message Alerting on AEX you have to execute the following configuration steps: Identify an ABAP System, which can be used as Central Monitoring System Add the properties of the Central Monitoring System to the AII Config Service Create a service user for RWB and dialog users on your Central Monitoring System Activate the ICF service needed for alerting on your Central Monitoring System Configure alerting using the Alert Configuration in Runtime Workbench These steps are explained in more details in the following sections of this document. Identify an ABAP System In principle you can use any ABAP System with basis release 7.0 and higher as Central Monitoring System. Typical candidates for it are another ABAP Integration Server in your landscape or your Solution Manager system. Note: If you use your Integration Server as CEN (or use the same system for more than one AEX), you have to pay attention to the fact that the alerting does not distinguish the different sources of the alert. Accordingly the alert rules are global for all attached PI systems and can therefore interfere each other. Add AII Config Service Properties For connecting you AEX system with the Central Monitoring System you have to specify the connection parameters of CEN in your AEX. These connection parameters are specified in the AII Config Service, which replaces the Exchange Profile on Java-only installations. The following parameters have to be specified: com.sap.aii.rwb.server.centralmonitoring.httpport: HTTP port of the WebAS (ABAP part) on which the central PMI, CCMS and Alert Server run. Required for HTTP connections to the monitoring server. com.sap.aii.rwb.server.centralmonitoring.httpsport: HTTPS port of the WebAS (ABAP part) on which the central PMI, CCMS and Alert Server run. Required for HTTPS connections to the monitoring server. com.sap.aii.rwb.server.centralmonitoring.name: Contains the hostname of the WebAS on which the central PMI, central CCMS and central Alert Server run. com.sap.aii.rwb.server.centralmonitoring.r3.ashost: Application server of the WebAS on which the centtral PMI, central CCMS and central Alert Server run. Required for JCO connections and HTTP connections to the monitoring server. 2011 SAP AG 3
com.sap.aii.rwb.server.centralmonitoring.r3.client: Client on which the central PMI, CCMS and Alert Server run. Required for JCO connections. com.sap.aii.rwb.server.centralmonitoring.r3.group: Name of the group of application servers of Central Monitoring Server (see JCO documentation of property jco.client.group) com.sap.aii.rwb.server.centralmonitoring.r3.mshost: Host name of the message server of Central Monitoring Server (see JCO documentation of property jco.client.mshost) com.sap.aii.rwb.server.centralmonitoring.r3.r3name: Name of the SAP system of Central Monitoring Server (see JCO documentation of property jco.client.r3name) com.sap.aii.rwb.server.centralmonitoring.r3.sysnr: System number of the WebAS on which the central PMI, CCMS and Alert Server run. Required for JCO connections. All these parameters have to point to the system, you have chosen in the first step. To configure these parameters you have to open NWA->Configuration->Infrastructure->Java System Properties on your AEX: 2011 SAP AG 4
Then go to Services->XPI Service: AII Config Service: And add com.sap.aii.rwb.server.centralmonitoring.* properties: Now save your changes. 2011 SAP AG 5
As next step you have to specify the user, the alerting shall use to send the alerts to the Central Monitoring Server. For this purpose, the RWB user is used, which is configured via the following parameters: Note: This user does not have to be created on AEX! It will be created later on CEN. Therefore, remember the user name and password, you entered here. You will need them in the following step. As last step, you can check if the parameter alerting.isactive of service AF Core is set to true. Now you have to restart your AEX. In the meantime you can do the configuration on Central Monitoring System. Create Users on CEN Now go to your CEN and create the user, which is used for the receiving of the alerts. It has to be a technical user, whose id is the name, you entered in the previous step, and also the password has to be the same as in the previous step. Please, assign the role SAP_XI_RWB_SERVUSER to it. For the persons, that shall configure the alerting, you have to create dialog users with the role SAP_XI_ADMINISTRATOR. For those, who shall receive alerts in their alert inbox, you have to create dialog users with role SAP_XI_MONITOR. Both user groups have to be created on CEN. Activate ICF Services As last step before you can do the actual alert configuration you have to activate the ICF services, which are needed for the alert configuration UI and the alert inbox. This configuration has again to be executed on CEN. Open in SAPGUI transaction SICF and activate the following services: /default_host/sap/bc/bsp/sap/alertinbox /default_host/sap/bc/bsp/sap/alertpersonalize_rules /default_host/sap/bc/bsp/sap/alertsubscription /default_host/sap/bc/bsp/sap/sxms_alertrules /default_host/sap/bc/gui/sap/its/webgui 2011 SAP AG 6
Configure Alerting Now you are ready to configure the alerting itself. For this, go again to your AEX and open the Alert Configuration of AEX via the following link: http://<host>:<port>/rwb/frontcomponent/fc_secure.jsp?doaction=showalerting, where <host> and <port> are those of your AEX. If everything is configured correctly this page will forward you to the Alert Configuration UI on CEN, where you can logon with your Administrator user, you created in one of the steps before. Here you can configure now your alert rules as you are used to do on double stack installations. 2011 SAP AG 7
Using Message Alerting The Alert Inbox can be reached via the following link: http://<host>:<port>/rwb/frontcomponent/fc_secure.jsp?doaction=showalertinbox, where <host> and <port> are again those of AEX. For log in to this page you need one of the users with SAP_XI_MONITOR role on CEN. To check, if everything is configured correctly, you can send a test alert using the alert test page of Adapter Engine: http://<host>:<port>/adapterframework/alerting/ping.jsp and check if the test alerts appear in your Alert Inbox. Limitations As already mentioned you have to pay attention to the fact, that the alerts from different installations are not distinguished on CEN. 2011 SAP AG 8
Related Content Configuration of Service Properties in NWA List of Exchange Profile Parameters Alert Configuration Alert Inbox 2011 SAP AG 9
Copyright Copyright 2011 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iseries, pseries, xseries, zseries, eserver, z/vm, z/os, i5/os, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. 2011 SAP AG 10