The document discusses the basic configuration settings required after installing SAP NetWeaver Gateway. This includes configuring profile parameters, ICF services, changing the initial logon password, language settings, and activating SAP NetWeaver Gateway. Additional optional configurations covered are for the OData channel, user authorizations, connection settings between systems, and backend event publisher. The document provides an overview of implementation guides and additional software components that may require further configurations.
SAP NetWeaver Gateway allows business users to access SAP applications and data through standard web technologies like RESTful services and OData. The presentation provided an overview of SAP NetWeaver Gateway, including its functionality, architecture, and development process. Developers can create client applications that consume Gateway services using various IDE plugins, without needing knowledge of SAP systems. The demo showed provisioning and consumption tools, and examples of how Gateway enables mobile apps to access SAP back-end systems.
SAP NetWeaver Gateway Service Development
Agenda:
Data Model Definition
–Declarative model definition
–Import data model (EDMX)
–Import DDIC
–Import RFC/BOR Interface
Service implementation
–Code based implementation
–Code based extenstions
–Mapping of RFC/BOR operations
Service registration
–Gateway Hub
–Gateway Backend
The document discusses SAP NetWeaver Gateway, which allows organizations to connect their data, workforce, customers and partners. It addresses challenges like integrating teams, supporting modern user interfaces, and developing applications faster. SAP NetWeaver Gateway provides a standardized way to access SAP data through open standards like OData and REST APIs. It allows for simplified and accelerated development of applications across platforms to engage customers, employees and partners.
The document introduces Representational State Transfer (REST) and how it has been implemented through HTTP. It defines REST as a set of six architectural constraints for networked systems, including separating concerns in a client-server model and making interactions stateless and uniform. HTTP implements the core REST operations of create, read, update and delete through its request methods. The document aims to explain REST as a design philosophy rather than a protocol.
The SAP NetWeaver Gateway Service Builder provides a tool for centrally defining and creating OData services. It allows modeling of entity sets, types and properties from various data sources. Services can be generated based on existing models from SAP applications like ERP, CRM, BW, HANA or custom models. The service builder supports code-based and declarative implementation approaches and registration of the services with the Gateway server.
How to build an agentry based mobile app from scratch connecting to an sap ba...Ganesh Kumar
1. Run the Agentry Server installation executable file as an administrator.
2. Accept the license agreement and enter the provided serial number.
3. Select the Development Server option and specify an installation location.
4. Complete the installation process. Add the Java path to the system environment variables so Agentry can locate the JVM.
This provides a high-level overview of the major steps to install the Agentry Server which is required to develop Agentry-based mobile applications that connect to a SAP backend. Key steps include running the installer, accepting licenses, selecting Development Server, and configuring environment variables.
Accessing Your Existing SAP NetWeaver Portal on Mobile DeviceSAP Portal
The document discusses providing access to existing SAP NetWeaver Portal content on mobile devices. It outlines a two-phase solution: 1) Allowing customers to build their own mobile framework page using an SAP guide. 2) SAP providing a pre-built mobile framework UI and exposing portal services via REST for use in mobile apps. The solution will leverage the portal's existing services while using modern mobile UIs. It will also align with Sybase Unwired Platform for building native mobile business apps using portal services.
This document provides an overview of the SAP Afaria mobile device management solution. It describes the key components of the Afaria architecture including the Afaria server, database server, relay server, enrollment server, and self-service portal server. It also covers deployment scenarios for Afaria including both single server and highly scalable server farm implementations. Device platform support and considerations for scaling the solution are discussed as well.
SAP NetWeaver Gateway allows business users to access SAP applications and data through standard web technologies like RESTful services and OData. The presentation provided an overview of SAP NetWeaver Gateway, including its functionality, architecture, and development process. Developers can create client applications that consume Gateway services using various IDE plugins, without needing knowledge of SAP systems. The demo showed provisioning and consumption tools, and examples of how Gateway enables mobile apps to access SAP back-end systems.
SAP NetWeaver Gateway Service Development
Agenda:
Data Model Definition
–Declarative model definition
–Import data model (EDMX)
–Import DDIC
–Import RFC/BOR Interface
Service implementation
–Code based implementation
–Code based extenstions
–Mapping of RFC/BOR operations
Service registration
–Gateway Hub
–Gateway Backend
The document discusses SAP NetWeaver Gateway, which allows organizations to connect their data, workforce, customers and partners. It addresses challenges like integrating teams, supporting modern user interfaces, and developing applications faster. SAP NetWeaver Gateway provides a standardized way to access SAP data through open standards like OData and REST APIs. It allows for simplified and accelerated development of applications across platforms to engage customers, employees and partners.
The document introduces Representational State Transfer (REST) and how it has been implemented through HTTP. It defines REST as a set of six architectural constraints for networked systems, including separating concerns in a client-server model and making interactions stateless and uniform. HTTP implements the core REST operations of create, read, update and delete through its request methods. The document aims to explain REST as a design philosophy rather than a protocol.
The SAP NetWeaver Gateway Service Builder provides a tool for centrally defining and creating OData services. It allows modeling of entity sets, types and properties from various data sources. Services can be generated based on existing models from SAP applications like ERP, CRM, BW, HANA or custom models. The service builder supports code-based and declarative implementation approaches and registration of the services with the Gateway server.
How to build an agentry based mobile app from scratch connecting to an sap ba...Ganesh Kumar
1. Run the Agentry Server installation executable file as an administrator.
2. Accept the license agreement and enter the provided serial number.
3. Select the Development Server option and specify an installation location.
4. Complete the installation process. Add the Java path to the system environment variables so Agentry can locate the JVM.
This provides a high-level overview of the major steps to install the Agentry Server which is required to develop Agentry-based mobile applications that connect to a SAP backend. Key steps include running the installer, accepting licenses, selecting Development Server, and configuring environment variables.
Accessing Your Existing SAP NetWeaver Portal on Mobile DeviceSAP Portal
The document discusses providing access to existing SAP NetWeaver Portal content on mobile devices. It outlines a two-phase solution: 1) Allowing customers to build their own mobile framework page using an SAP guide. 2) SAP providing a pre-built mobile framework UI and exposing portal services via REST for use in mobile apps. The solution will leverage the portal's existing services while using modern mobile UIs. It will also align with Sybase Unwired Platform for building native mobile business apps using portal services.
This document provides an overview of the SAP Afaria mobile device management solution. It describes the key components of the Afaria architecture including the Afaria server, database server, relay server, enrollment server, and self-service portal server. It also covers deployment scenarios for Afaria including both single server and highly scalable server farm implementations. Device platform support and considerations for scaling the solution are discussed as well.
Balaji has over 3.8 years of experience designing, implementing, and supporting SAP Syclo mobility solutions including Work Manager, Service Manager, Inventory Manager, and Rounds Manager. He has expertise in Agentry development, SMP administration, and configuring Syclo applications for clients in various industries. Balaji is proficient in Java, HTML5, CSS, JavaScript, Eclipse, and SAP mobile platforms. He has led projects for clients such as ITC, KBA, Singapore Power, and SAP.
Attachments should be stored separately from the MBO model and referenced using a URL or key. This avoids unnecessary uploads and downloads of large attachments during synchronization.
Java technology allows programs to run on a variety of hardware platforms, including the mainframe computing platform epitomized by z Systems. The z Systems zOS operating system has a set of unique capabilities, and IBM SDK for Java provides a set of high performance Java APIs complemented by z/OS specific APIs for applications that require deep integration. This talk shows how IBM makes use of the z/OS platform to deliver world-class runtimes on the world leading mainframe.
Originally presented at the z/OS bootcamp in Hursley, 2015
This document provides an overview and agenda for a presentation on SAP Mobile Infrastructure. The presentation covers SAP's mobile solutions including key components of SAP Netweaver Mobile, its architecture, and value propositions. It also discusses several pre-integrated SAP xApp mobile applications for asset management, time and travel, sales, and dealer business management that provide mobile access to back-end SAP systems. The document includes capabilities and benefits of the various mobile applications and infrastructure.
The document provides an overview of Apache Cordova and the SAP Kapsel plugins:
- Apache Cordova allows web-based applications to access hardware features on mobile devices by running the application within a container. SAP Kapsel provides additional plugins for Cordova applications to interact with SAP Mobile Platform services.
- The Kapsel Logon plugin manages the onboarding and authentication process with SAP Mobile Platform/HCPms servers. It handles functions like initializing the login process, logging in users, and providing the application context after successful login.
- Other Kapsel plugins allow offline data access using OData, logging, application updates, push notifications, and encrypted storage. Using Kapsel plugins, a single
This document provides an overview and agenda for a presentation on SAP's mobile platform strategy. It discusses SAP's Afaria, Sybase Unwired Platform, and SAP NetWeaver Gateway mobile solutions. The presentation aims to explain SAP's mobility strategy and the architecture and uses of these three mobile platforms. It also includes a disclaimer stating that the information provided is for discussion purposes only and not final product information.
Java EE 7: Developing for the Cloud at Java Day, Istanbul, May 2012Arun Gupta
The document discusses Java EE 7 and its focus on cloud computing. Key points include:
- Java EE 7 aims to define the Java EE platform as a service (PaaS) to make it easier for developers to leverage public, private and hybrid clouds.
- This includes adding metadata for service provisioning and configuration, and APIs to support features like elastic scaling and multi-tenancy.
- A demo is described showing how a Java EE application can be deployed to the cloud by including service metadata that allows for automatic provisioning of resources.
The Java EE 7 Platform: Developing for the Cloudcodemotion_es
The document discusses Java EE 7 and the focus on supporting Platform as a Service (PaaS) and cloud computing. It outlines how Java EE 7 will define new platform roles and add metadata to support auto-provisioning of services from application dependencies and multi-tenancy. It provides an example scenario of how a Java EE application could be submitted to and deployed on a PaaS provider.
How to part 2 build an agentry based app from scratchGanesh Kumar
Here are the key steps to create the class handler and BAPI wrapper in the SAP backend:
1. Create a class handler (e.g. ZXX_CREATE_FLIGHT_BOOKING) by copying from a template class
(e.g. Z00_CREATE_FLIGHT_BOOKING)
2. Generate and activate the class
3. Create a BAPI wrapper function module (e.g. ZXX_BAPI_CRT_FLIGHT_BOOKING) by copying from
a template function module (e.g. Z00_BAPI_CRT_FLIGHT_BOOKING)
4. Assign the function module to a function group
The Agentry SAP Framework provides an efficient way to build mobile solutions for SAP using SAP Mobile Platform. The framework uses a layered approach with foundation and application components to define standard integration patterns for mobile data, change detection, synchronization, and administration. It includes components for change detection, business logic, integration, configuration, and monitoring to synchronize data between SAP systems and mobile applications.
The document provides instructions for installing the Agentry Editor plug-in for Eclipse and configuring the development environment for building Agentry mobile applications. Key steps include:
1. Downloading the appropriate 32-bit or 64-bit version of Eclipse based on your system.
2. Extracting the Eclipse files and installing the Java Runtime Environment.
3. Adding the Agentry Editor plug-in ZIP file from the SAP Mobile SDK as an update site in Eclipse to enable installation of the plug-in.
This presentation helps you to understand what the SAP Portal Portfolio offers already today, you will be informed on the planned product enhancements and you get insights into strategic directions for the portal portfolio.
WebLogic 12c Developer Deep Dive at Oracle Develop India 2012Arun Gupta
This document discusses Oracle WebLogic Server 12c and its ability to develop modern, lightweight Java EE 6 applications for both conventional and cloud deployment environments. It highlights how WebLogic Server 12c allows developers to extend their existing skills with the latest Java standards and integrate with open source frameworks. Developers can write less glue code and focus more on business logic by leveraging WebLogic Server's integrated services.
The document provides an overview of the technical architecture of Oracle Primavera P6 EPPM R8. It describes the core server components that form a scalable, tiered architecture suitable for small to large enterprises. These include databases, web application servers, and compression servers. It also outlines the various software modules, including windows and web-based clients, and lists the minimum requirements for these modules. Finally, it includes a diagram showing the logical connections between the main solution components.
A sanitized version of slides presented by John Moy at the SAP Australia User Group 2012 for the presentation 'How SAP NetWeaver Gateway can deliver the User Interfaces you've always wanted'
This document provides an overview and introduction to using the SAP HANA Cloud Persistence Service. It discusses how applications can access SAP HANA databases in the cloud using JDBC or JPA, and focuses on JPA as the preferred method. It demonstrates how to add persistence to applications using EclipseLink as the JPA implementation and includes steps for configuring applications to work with SAP HANA Cloud. The presentation concludes with reminders of related resources and a question/answer discussion section.
The document summarizes an SAP HANA Cloud Platform package that enables extensions to SuccessFactors Employee Central. It allows extending SuccessFactors with apps running on HANA Cloud Platform to meet growing business needs. The platform extensions provide harmonized user experience, APIs for data access and UI customization, and an app certification process. It is available externally since Q3 2013.
The document provides an overview of SAP NetWeaver Gateway 2.0, including its high-level architecture, deployment and development scenarios, and options for developing and consuming gateway services. The gateway allows accessing SAP data via RESTful APIs and supports development using code generators, custom ABAP development, and consumption via various programming languages.
The document discusses the features and benefits of implementing SAP's Material Ledger module. Material Ledger allows companies to value inventories in multiple currencies and valuation methods in real-time. It provides a hybrid approach of valuing inventories at standard cost during a period and calculating a periodic moving average price. Material Ledger also enables the amortization of price variances over the life of inventories. Implementing Material Ledger provides enhanced inventory visibility and management.
Balaji has over 3.8 years of experience designing, implementing, and supporting SAP Syclo mobility solutions including Work Manager, Service Manager, Inventory Manager, and Rounds Manager. He has expertise in Agentry development, SMP administration, and configuring Syclo applications for clients in various industries. Balaji is proficient in Java, HTML5, CSS, JavaScript, Eclipse, and SAP mobile platforms. He has led projects for clients such as ITC, KBA, Singapore Power, and SAP.
Attachments should be stored separately from the MBO model and referenced using a URL or key. This avoids unnecessary uploads and downloads of large attachments during synchronization.
Java technology allows programs to run on a variety of hardware platforms, including the mainframe computing platform epitomized by z Systems. The z Systems zOS operating system has a set of unique capabilities, and IBM SDK for Java provides a set of high performance Java APIs complemented by z/OS specific APIs for applications that require deep integration. This talk shows how IBM makes use of the z/OS platform to deliver world-class runtimes on the world leading mainframe.
Originally presented at the z/OS bootcamp in Hursley, 2015
This document provides an overview and agenda for a presentation on SAP Mobile Infrastructure. The presentation covers SAP's mobile solutions including key components of SAP Netweaver Mobile, its architecture, and value propositions. It also discusses several pre-integrated SAP xApp mobile applications for asset management, time and travel, sales, and dealer business management that provide mobile access to back-end SAP systems. The document includes capabilities and benefits of the various mobile applications and infrastructure.
The document provides an overview of Apache Cordova and the SAP Kapsel plugins:
- Apache Cordova allows web-based applications to access hardware features on mobile devices by running the application within a container. SAP Kapsel provides additional plugins for Cordova applications to interact with SAP Mobile Platform services.
- The Kapsel Logon plugin manages the onboarding and authentication process with SAP Mobile Platform/HCPms servers. It handles functions like initializing the login process, logging in users, and providing the application context after successful login.
- Other Kapsel plugins allow offline data access using OData, logging, application updates, push notifications, and encrypted storage. Using Kapsel plugins, a single
This document provides an overview and agenda for a presentation on SAP's mobile platform strategy. It discusses SAP's Afaria, Sybase Unwired Platform, and SAP NetWeaver Gateway mobile solutions. The presentation aims to explain SAP's mobility strategy and the architecture and uses of these three mobile platforms. It also includes a disclaimer stating that the information provided is for discussion purposes only and not final product information.
Java EE 7: Developing for the Cloud at Java Day, Istanbul, May 2012Arun Gupta
The document discusses Java EE 7 and its focus on cloud computing. Key points include:
- Java EE 7 aims to define the Java EE platform as a service (PaaS) to make it easier for developers to leverage public, private and hybrid clouds.
- This includes adding metadata for service provisioning and configuration, and APIs to support features like elastic scaling and multi-tenancy.
- A demo is described showing how a Java EE application can be deployed to the cloud by including service metadata that allows for automatic provisioning of resources.
The Java EE 7 Platform: Developing for the Cloudcodemotion_es
The document discusses Java EE 7 and the focus on supporting Platform as a Service (PaaS) and cloud computing. It outlines how Java EE 7 will define new platform roles and add metadata to support auto-provisioning of services from application dependencies and multi-tenancy. It provides an example scenario of how a Java EE application could be submitted to and deployed on a PaaS provider.
How to part 2 build an agentry based app from scratchGanesh Kumar
Here are the key steps to create the class handler and BAPI wrapper in the SAP backend:
1. Create a class handler (e.g. ZXX_CREATE_FLIGHT_BOOKING) by copying from a template class
(e.g. Z00_CREATE_FLIGHT_BOOKING)
2. Generate and activate the class
3. Create a BAPI wrapper function module (e.g. ZXX_BAPI_CRT_FLIGHT_BOOKING) by copying from
a template function module (e.g. Z00_BAPI_CRT_FLIGHT_BOOKING)
4. Assign the function module to a function group
The Agentry SAP Framework provides an efficient way to build mobile solutions for SAP using SAP Mobile Platform. The framework uses a layered approach with foundation and application components to define standard integration patterns for mobile data, change detection, synchronization, and administration. It includes components for change detection, business logic, integration, configuration, and monitoring to synchronize data between SAP systems and mobile applications.
The document provides instructions for installing the Agentry Editor plug-in for Eclipse and configuring the development environment for building Agentry mobile applications. Key steps include:
1. Downloading the appropriate 32-bit or 64-bit version of Eclipse based on your system.
2. Extracting the Eclipse files and installing the Java Runtime Environment.
3. Adding the Agentry Editor plug-in ZIP file from the SAP Mobile SDK as an update site in Eclipse to enable installation of the plug-in.
This presentation helps you to understand what the SAP Portal Portfolio offers already today, you will be informed on the planned product enhancements and you get insights into strategic directions for the portal portfolio.
WebLogic 12c Developer Deep Dive at Oracle Develop India 2012Arun Gupta
This document discusses Oracle WebLogic Server 12c and its ability to develop modern, lightweight Java EE 6 applications for both conventional and cloud deployment environments. It highlights how WebLogic Server 12c allows developers to extend their existing skills with the latest Java standards and integrate with open source frameworks. Developers can write less glue code and focus more on business logic by leveraging WebLogic Server's integrated services.
The document provides an overview of the technical architecture of Oracle Primavera P6 EPPM R8. It describes the core server components that form a scalable, tiered architecture suitable for small to large enterprises. These include databases, web application servers, and compression servers. It also outlines the various software modules, including windows and web-based clients, and lists the minimum requirements for these modules. Finally, it includes a diagram showing the logical connections between the main solution components.
A sanitized version of slides presented by John Moy at the SAP Australia User Group 2012 for the presentation 'How SAP NetWeaver Gateway can deliver the User Interfaces you've always wanted'
This document provides an overview and introduction to using the SAP HANA Cloud Persistence Service. It discusses how applications can access SAP HANA databases in the cloud using JDBC or JPA, and focuses on JPA as the preferred method. It demonstrates how to add persistence to applications using EclipseLink as the JPA implementation and includes steps for configuring applications to work with SAP HANA Cloud. The presentation concludes with reminders of related resources and a question/answer discussion section.
The document summarizes an SAP HANA Cloud Platform package that enables extensions to SuccessFactors Employee Central. It allows extending SuccessFactors with apps running on HANA Cloud Platform to meet growing business needs. The platform extensions provide harmonized user experience, APIs for data access and UI customization, and an app certification process. It is available externally since Q3 2013.
The document provides an overview of SAP NetWeaver Gateway 2.0, including its high-level architecture, deployment and development scenarios, and options for developing and consuming gateway services. The gateway allows accessing SAP data via RESTful APIs and supports development using code generators, custom ABAP development, and consumption via various programming languages.
The document discusses the features and benefits of implementing SAP's Material Ledger module. Material Ledger allows companies to value inventories in multiple currencies and valuation methods in real-time. It provides a hybrid approach of valuing inventories at standard cost during a period and calculating a periodic moving average price. Material Ledger also enables the amortization of price variances over the life of inventories. Implementing Material Ledger provides enhanced inventory visibility and management.
El documento describe las características de ABAP 7.51 y cómo ayuda a migrar código personalizado de manera exitosa a SAP S/4HANA. Explica que el código personalizado debe adaptarse al nuevo modelo de datos simplificado en SAP S/4HANA. Proporciona una guía de dos fases para la migración, incluida la eliminación de código obsoleto, comprobaciones de compatibilidad con SAP HANA y S/4HANA, y la creación de una lista de trabajo para la adaptación. Las herramientas como el Inspector de Código
Este documento describe los principios clave del presupuesto de ventas y mercadotecnia. 1) El presupuesto de ventas y mercadotecnia vincula el plan estratégico con otros planes funcionales como manufactura, I+D, administración e inversión de capital. 2) Incluye gastos discrecionales de mercadotecnia como ventas, promoción, publicidad y distribución. 3) Se debe desarrollar usando un enfoque incremental y analizando factores operativos clave.
DOES15 DevOps@TGT (re)building an engineering culture Ross Clanton
This document summarizes Target's journey to transform their engineering culture through DevOps. It discusses how they overcame challenges like slow delivery, siloed teams, and outdated tools by enabling engineers, cultivating a grassroots movement, simplifying processes, and aligning executives. Some results of these efforts include a 53x increase in enabled business capabilities, over 80 deployments per week, and establishing a learning environment to develop teams. The next steps discussed are expanding globally and seeking advice from others on challenges of scaling DevOps across a large enterprise.
01 taller decreto 2649 1993 y ley 1314 2009Paola Casal
Este documento presenta 8 preguntas sobre normas contables internacionales según decretos y leyes colombianas. Pregunta sobre los Principios de Contabilidad Generalmente Aceptados, cualidades de la información contable, normas básicas, estados financieros básicos, definiciones de términos contables clave, objetivo y aplicación de la Ley 1314 de 2009, autoridades de regulación, y define las Normas Internacionales de Información Financiera.
Este documento describe una correa con una cámara insertada que permite localizar a una mascota perdida mediante una aplicación en el teléfono móvil. La correa incluye una cámara y chip de vigilancia que muestran la ubicación y imagen de la mascota en Google Maps. Se venderá en tiendas de mascotas y por internet por 156,99€, y si se compran dos se regala un teléfono móvil a los primeros 20 clientes del primer mes.
Open sap fiori1_week_01_unit_01_courseintroNagendra Babu
This document provides an introduction to a 6-week course on the SAP Fiori user experience (UX). It outlines the course objectives of understanding the SAP UX strategy, SAP Fiori app types and architecture, and prerequisites for installing and configuring SAP Fiori apps. The course structure includes videos, assignments, online forums, and a final exam. Special emphasis is placed on collaborating with customers to understand technology, business needs, and human values when developing the SAP Fiori UX.
This document provides an overview of deploying SAP Fiori UX. It discusses the architecture including front-end and back-end servers. It outlines the necessary components to deploy on each end including foundation and functional modules. It recommends tools for installation and maintenance. Finally, it recaps where to access all required assets and components from the SAP Service Marketplace.
La Ley 1314 de 2009 establece la convergencia de las normas contables colombianas a los estándares internacionales de información financiera (NIIF). Designa al Ministerio de Hacienda y Crédito Público y al Ministerio de Comercio, Industria y Turismo para expedir las normas contables de manera conjunta. Además, fija un plazo para la implementación de las NIIF para el 1 de enero de 2014 y reestructura el Consejo Técnico de la Contaduría para redactar las normas.
Este documento describe la implementación de un proxy web Squid para mejorar la seguridad perimetral y filtrar contenidos. Explica cómo instalar y configurar Squid, definir listas de acceso y reglas de control, y también cómo configurar Apache como proxy inverso con los módulos mod_proxy y mod_proxy_balancer.
SAP ABAP Proxy Objects: Configuración del entornoOreka IT
El objetivo del presente documento es describir los pasos de configuración para poder hacer
uso de los Objetos Proxy ABAP en los desarrollos XI.
Esta guía no afecta exclusivamente al servidor de XI. Para poder hacer un uso correcto de los
ABAP Proxy Objects deben llevarse a cabo estos pasos de configuración en todos aquellos
sistemas que vayan a comunicarse con el servidor de XI a través de objetos Proxy ABAP
incluido el propio servidor de XI.
This document provides instructions for configuring SAP NetWeaver Fiori for single sign-on (SSO) via SAML. It outlines the steps to 1) prepare SAP NetWeaver Fiori for configuration by completing prerequisites like assigning roles and activating services, 2) add and begin configuring the SAP NetWeaver Fiori application in the Admin Portal, and 3) finish configuring the application settings and identity provider metadata to enable SSO. The goal is to allow users to launch the SAP NetWeaver Fiori application from the identity provider portal once configuration is complete.
Sap net weaver gateway and o data - sap netweaver gateway - sap libraryNagendra Babu
SAP NetWeaver Gateway exposes SAP business data as REST-based OData services to enable sharing data across technologies easily. OData is a standard protocol that provides a predictable interface for querying different data sources using common operations like GET, PUT, POST and DELETE. It supports features like paging and linking data that help a wide range of clients access and navigate the data. For SAP applications, OData provides additional metadata from the SAP ABAP Dictionary to help developers consume SAP business data.
This document provides configuration steps for setting up basic funds management functionality in SAP, including maintaining FM areas, assigning company codes and fiscal year variants, activating account assignment elements, defining business areas, configuring general ledger and financial accounting settings, and more. The detailed steps cover areas like public sector management configuration, financial documents, grants management, and funds management master data.
This document provides instructions for configuring SAP Solution Manager and SAP Software Lifecycle Manager (SLM) to enable Maintenance Optimizer to automatically download and deploy support packages and enhancement packages to managed systems. Key steps include registering systems in the System Landscape Directory (SLD) and Solution Manager system, installing and configuring SLM, customizing Maintenance Optimizer settings, and configuring the necessary tools on managed systems like Support Package Manager (SPAM) and Java Support Package Manager (JSPM).
Sap screen personas performance optimization guide v0.96Peter Spielvogel
Tips and tricks for optimizing performance in SAP Screen Personas. Learn how to design screens so they load quickly. Understand how caching / pre-fetching affects performance. See what role the ITS plays and how to size it correctly.
The document outlines the basic setup of the CRM WebClient UI, including configuring business roles, profiles, authorizations, and UI elements. It describes adapting navigation bars, work centers, logical links and overview pages for different user groups using configuration tools and customizing transactions.
This document provides instructions for configuring production planning and control in SAP ERP. It covers topics such as:
- Defining BOM usages, modification parameters, planner groups, and material types for bills of material
- Configuring MRP parameters like rescheduling check, range of coverage profile, and planning horizon
- Setting up shop floor control with number ranges, status profiles, and availability checks
- Configuring capacity planning, repetitive manufacturing, and rework processes
- Copying standard settings for process management and defining basic data for PP/PI orders
The guide provides detailed steps to manually configure all the necessary master and transactional data for production planning and control in SAP ERP.
This document provides instructions for configuring production planning and control in SAP, including:
1. Defining basic data such as BOM usages, modification parameters, planner groups, allowed material types for BOM headers and items, and more.
2. Configuring material requirements planning (MRP), including defining MRP groups, safety stock availability, external procurement, and more.
3. Configuring shop floor control (SFC) including number ranges, status profiles, and availability checks.
4. Configuring other areas such as rework, capacity planning, repetitive manufacturing, and more.
This document provides instructions for implementing a custom BADI (Business Add-In) in SAP BOBJ Planning and Consolidation to replicate the functionality of the "Destination_App" scripting keyword. The BADI allows transferring records from a source application to a target application within the same AppSet. It describes transporting required objects to the system, usage syntax, parameter options, and example scenarios. Error messages are also defined to help users address issues with dimension mapping between source and target.
This document provides instructions for installing SAP systems on Windows with an Oracle database. It describes planning the installation, preparing the system, and installing the central instance, standalone database instance, dialog instances, and additional components. Post-installation steps include starting and stopping the system, logging on, installing licenses, and backups. It also covers secure single sign-on and converting an existing installation to a Microsoft Cluster Server configuration for high availability.
This document provides instructions for installing an SAP R/3 system on Windows using an Oracle database. It discusses installation planning considerations, preparation steps, installing the central system components including the database server and R3SETUP, standalone and dialog instances. Post-installation activities like starting/stopping the system and logging on are also covered. The document contains details on hardware and software requirements, directory structure, and input screens for the different installation types.
How to use abap cds for data provisioning in bwLuc Vanrobays
This document provides guidance on using ABAP CDS (Core Data Services) views to provision data from SAP S/4HANA systems into SAP BW/4HANA. It describes two scenarios: [1] directly accessing CDS views from BW for real-time data, and [2] using CDS views to extract delta changes from S/4HANA to populate BW incrementally. The document also discusses replacing existing BW extractors with CDS views when migrating to S/4HANA.
This document provides an overview of configuring warehouse structure and master data for use in SAP Extended Warehouse Management (EWM). It describes automatically configuring warehouse W001 using a report or manually configuring warehouse structure, master data, and application logs. Configuring the warehouse structure and master data is prerequisite for using preconfigured business processes in warehouse W001.
The document provides instructions for configuring single sign-on (SSO) with an SAP HANA database using Kerberos authentication and Microsoft Active Directory. It describes the necessary steps to set up hostname resolution, configure the SAP HANA database server for Kerberos, create an SAP HANA service user in Active Directory, generate a keytab file, create external SAP HANA database users, and verify the SSO configuration. Troubleshooting tips are provided in an appendix. The goal is to enable users to authenticate with the SAP HANA database after logging into the Active Directory domain, without needing to re-enter credentials.
How to configure and use change recordingPhani Kumar
This document provides instructions for configuring and using change recording in SAP NetWeaver to track changes made to portal content and transport them between systems. It describes enabling change recording globally and for specific folders, setting required permissions, making changes in the development portal and activating the change list, releasing and importing the transport request to another system, and testing the changes on the target portal. It also covers optional steps like creating a changelist and working with the team organizer.
This document provides instructions for monitoring end user experience using the End User Experience Monitoring (EEM) tool in SAP Solution Manager. It describes how to record transactions, configure EEM scripts for HTTP and SAP GUI transactions, upload scripts and certificates to the SAP Solution Manager repository, and troubleshoot script execution issues. The document contains information on prerequisites, script design considerations, recording transactions, configuring response checks, creating variables, and uploading scripts.
How to build an agentry based mobile app from scratch connecting to an sap ba...Jaime Marchant Benavides
This document provides instructions for building a mobile application that connects to a SAP backend system using SAP Mobile Platform and Agentry. It includes steps for installing the Agentry server and editor plugin, configuring the backend system, building the fetch mechanism in the Agentry editor by creating projects, connections, objects and screens, and publishing the application. The document also includes prerequisites, a business scenario section, and appendices.
Here are the key steps for sub-capacity licensing:
1. Install the SySAM sub-capacity license utility (sysamcap) on the physical machine.
2. Run sysamcap to discover the virtual environment and generate an XML file describing the virtual environment topology.
3. Upload the XML file to the SAP Service Marketplace to generate sub-capacity license files.
4. Install the sub-capacity license files on the physical machine.
5. Install and configure the SySAM license server.
6. Install SAP Replication Server and other products. The products will check out licenses from the license server based on the number and type of virtual CPUs used.
See
Suse linux enterprise_server_12_x_for_sap_applications_configuration_guide_fo...Jaleel Ahmed Gulammohiddin
This document provides guidance on installing and configuring SUSE Linux Enterprise Server for SAP Applications (SLES for SAP Applications) to be used with SAP HANA. It outlines hardware, software, and other prerequisites. It then provides a sample installation process for SLES 12 on x86_64 and Power architectures, including partitioning disks, selecting software packages, configuring system settings, and installing SAP HANA. Additional sections cover installing high availability, backup, and other optional software.
This document describes a process for preventive maintenance. Key steps include maintaining maintenance strategies, entering task lists for equipment, creating maintenance plans, scheduling maintenance plans, processing maintenance orders, confirming orders, issuing goods, receiving goods, verifying invoices, completing orders, and settling orders. The process aims to ensure high availability of assets through planned maintenance to avoid breakdowns and their associated costs.
This document provides an overview of SAP Fiori apps for the SAP ERP Materials Management (MM) application. It includes a matrix that maps available Fiori roles and their assigned apps to relevant SAP Best Practices baseline scope items. The matrix also identifies whether each app is transactional or analytical and whether it requires the SAP HANA platform. The document then provides descriptions, configurations, and usage instructions for key Fiori apps to support common MM processes such as procurement, inventory management, and purchasing on the SAP Best Practices baseline.
Similar to Sap netweaver gateway_2.0_sap_net_weaver (20)
Z sap boe-2016-techws-04_vs_fiori-app-with-eclipseluna-accessing-zsap-systemNagendra Babu
The document provides steps for developing a sample SAP Fiori application called "Purchase Order Approval" that accesses a SAP backend system running on IBM zSystems. It describes importing backend ABAP code, creating an OData model, configuring SAP Gateway, developing the frontend UI with SAPUI5, and uploading the app to the ABAP frontend server and SAP Fiori Launchpad. The sample app demonstrates how to leverage new proprietary Fiori apps with an on-premise SAP system using Eclipse for development.
Simple exercise on o data and sap ui5 application for the basic crud operatio...Nagendra Babu
This document describes how to create an OData service for basic CRUD operations using SAP Gateway Service Builder and consume it using a SAP UI5 application. It involves creating a backend table and functions for CRUD, generating a data model, mapping functions to OData operations, and registering the service. The SAP UI5 app is then built to display and modify employee data by consuming the OData service.
SAP Fiori is a new user experience for SAP applications that provides 300+ role-based apps for various business functions on desktops, smartphones, and tablets, and is built using SAP UI5. It includes transactional apps, fact sheets, and analytical apps that run on SAP NetWeaver Gateway and either an SAP HANA or other database, with fact sheets and analytical apps requiring HANA. SAP Fiori aims to provide a simple, responsive, and seamless experience across devices.
Sap fiori ll11 – consultants should know about o data troubleshooting sap b...Nagendra Babu
This document provides guidance for SAP consultants on troubleshooting issues with OData services used in SAP Fiori applications. It outlines key steps consultants should take, including identifying the specific OData call, testing the call directly, checking error logs, finding the runtime data provider class, and setting breakpoints to debug the code. The goal is to help consultants understand OData technical behavior and the underlying ERP application functions so they can resolve issues that may be due to different customer backend configurations or data.
Getting started with sap fiori, net weaver gateway & sapui5Nagendra Babu
This document provides an overview of getting started with SAP Fiori, NetWeaver Gateway, and SAPUI5. It discusses installing and setting up SAP NetWeaver Gateway and consuming OData services. It also covers downloading and installing SAPUI5, using text editors like Sublime Text, and creating SAPUI5 applications. Finally, it discusses SAP Fiori, how to customize Fiori applications, and provides tutorials for building Fiori-like apps with SAPUI5.
The document discusses deployment options for the SAP Fiori launchpad including ABAP, SAP Enterprise Portal, and SAP HANA Cloud Platform. It provides recommendations for each option based on factors like existing landscape, scenarios, features, and functions. The ABAP option is best for existing SAP Business Suite customers, Enterprise Portal for existing Portal customers, and HANA Cloud Platform for simplified cloud deployment.
Ac fr ogc7-mj_8ycozkm9utakolnuvpoehmpvpq8scic8rd_r4tapovstrv4txbk5mffoolznngh...Nagendra Babu
The SAP Fiori Client is a native mobile application that provides an enhanced experience for using SAP Fiori applications on Android and iOS devices. It caches application assets to improve performance and provides consistent navigation. The application requires configuration including entering the URL for the SAP Fiori server. Users then log in to access SAP Fiori applications and can configure cache, logging, and other settings to troubleshoot issues.
1. The document outlines 6 steps to add a custom workflow scenario to SAP Fiori Approve Requests.
2. The first step is to gather information about the workflow template such as the ID, approval step ID, task ID, business object, and approval outcomes.
3. The next steps involve defining the workflow scenario in Gateway, adding a tile to the Launchpad, configuring the task decision in ERP, implementing a BADI for outcomes, and displaying application data in Gateway.
Here are the key steps to activate and configure SAP NetWeaver Gateway:
1. Activate the SAP NetWeaver Gateway add-on using transaction SFW5. This will register the required services and configuration.
2. Check the status of the Gateway system using transaction /IWFND/GW_SYSTEM_CHECK. This will validate that all required components are installed and activated.
3. Assign a Gateway system alias using transaction /IWFND/GW_ALIAS. This alias will be used to access the Gateway services.
4. Configure the OData channel using transaction /IWFND/GW_SERVICE. Here you can define metadata generation settings and authorization roles.
5. Configure
This document provides recommendations for common architecture patterns when deploying SAP Fiori applications, the Fiori launchpad, and SAP Enterprise Portal. It discusses high-level overviews of extranet and intranet deployment scenarios, options for deploying the Fiori launchpad, and approaches for implementing risk-based authentication and single sign-on. The presentation also provides legal disclaimers around the information presented.
Physiology and chemistry of skin and pigmentation, hairs, scalp, lips and nail, Cleansing cream, Lotions, Face powders, Face packs, Lipsticks, Bath products, soaps and baby product,
Preparation and standardization of the following : Tonic, Bleaches, Dentifrices and Mouth washes & Tooth Pastes, Cosmetics for Nails.
हिंदी वर्णमाला पीपीटी, hindi alphabet PPT presentation, hindi varnamala PPT, Hindi Varnamala pdf, हिंदी स्वर, हिंदी व्यंजन, sikhiye hindi varnmala, dr. mulla adam ali, hindi language and literature, hindi alphabet with drawing, hindi alphabet pdf, hindi varnamala for childrens, hindi language, hindi varnamala practice for kids, https://www.drmullaadamali.com
This presentation was provided by Steph Pollock of The American Psychological Association’s Journals Program, and Damita Snow, of The American Society of Civil Engineers (ASCE), for the initial session of NISO's 2024 Training Series "DEIA in the Scholarly Landscape." Session One: 'Setting Expectations: a DEIA Primer,' was held June 6, 2024.
The simplified electron and muon model, Oscillating Spacetime: The Foundation...RitikBhardwaj56
Discover the Simplified Electron and Muon Model: A New Wave-Based Approach to Understanding Particles delves into a groundbreaking theory that presents electrons and muons as rotating soliton waves within oscillating spacetime. Geared towards students, researchers, and science buffs, this book breaks down complex ideas into simple explanations. It covers topics such as electron waves, temporal dynamics, and the implications of this model on particle physics. With clear illustrations and easy-to-follow explanations, readers will gain a new outlook on the universe's fundamental nature.
বাংলাদেশের অর্থনৈতিক সমীক্ষা ২০২৪ [Bangladesh Economic Review 2024 Bangla.pdf] কম্পিউটার , ট্যাব ও স্মার্ট ফোন ভার্সন সহ সম্পূর্ণ বাংলা ই-বুক বা pdf বই " সুচিপত্র ...বুকমার্ক মেনু 🔖 ও হাইপার লিংক মেনু 📝👆 যুক্ত ..
আমাদের সবার জন্য খুব খুব গুরুত্বপূর্ণ একটি বই ..বিসিএস, ব্যাংক, ইউনিভার্সিটি ভর্তি ও যে কোন প্রতিযোগিতা মূলক পরীক্ষার জন্য এর খুব ইম্পরট্যান্ট একটি বিষয় ...তাছাড়া বাংলাদেশের সাম্প্রতিক যে কোন ডাটা বা তথ্য এই বইতে পাবেন ...
তাই একজন নাগরিক হিসাবে এই তথ্য গুলো আপনার জানা প্রয়োজন ...।
বিসিএস ও ব্যাংক এর লিখিত পরীক্ষা ...+এছাড়া মাধ্যমিক ও উচ্চমাধ্যমিকের স্টুডেন্টদের জন্য অনেক কাজে আসবে ...
This slide is special for master students (MIBS & MIFB) in UUM. Also useful for readers who are interested in the topic of contemporary Islamic banking.
A review of the growth of the Israel Genealogy Research Association Database Collection for the last 12 months. Our collection is now passed the 3 million mark and still growing. See which archives have contributed the most. See the different types of records we have, and which years have had records added. You can also see what we have for the future.
Exploiting Artificial Intelligence for Empowering Researchers and Faculty, In...Dr. Vinod Kumar Kanvaria
Exploiting Artificial Intelligence for Empowering Researchers and Faculty,
International FDP on Fundamentals of Research in Social Sciences
at Integral University, Lucknow, 06.06.2024
By Dr. Vinod Kumar Kanvaria
Thinking of getting a dog? Be aware that breeds like Pit Bulls, Rottweilers, and German Shepherds can be loyal and dangerous. Proper training and socialization are crucial to preventing aggressive behaviors. Ensure safety by understanding their needs and always supervising interactions. Stay safe, and enjoy your furry friends!
3. SAP NetWeaver Gateway Configuration Guide
(C) SAP AG SAP NetWeaver Gateway 2.0 SPS08 3
Icons in Body Text
Icon Meaning
Caution
Example
Note
Recommendation
Syntax
Additional icons are used in SAP Library documentation to help you identify different types of
information at a glance. For more information, see Help on Help General Information
Classes and Information Classes for Business Information Warehouse on the first page of any
version of SAP Library.
Typographic Conventions
Type Style Description
Example text Words or characters quoted from the screen. These include field names, screen
titles, pushbuttons labels, menu names, menu paths, and menu options.
Cross-references to other documentation.
Example text Emphasized words or phrases in body text, graphic titles, and table titles.
EXAMPLE TEXT Technical names of system objects. These include report names, program
names, transaction codes, table names, and key concepts of a programming
language when they are surrounded by body text, for example, SELECT and
INCLUDE.
Example text Output on the screen. This includes file and directory names and their paths,
messages, names of variables and parameters, source text, and names of
installation, upgrade and database tools.
Example text Exact user entry. These are words or characters that you enter in the system
exactly as they appear in the documentation.
<Example text> Variable user entry. Angle brackets indicate that you replace these words and
characters with appropriate entries to make entries in the system.
EXAMPLE TEXT Keys on the keyboard, for example, F2 or ENTER.
4. SAP NetWeaver Gateway Configuration Guide
(C) SAP AG SAP NetWeaver Gateway 2.0 SPS08 4
Table of Contents
SAP NetWeaver Gateway Configuration Guide......................................................................7
Basic Configuration Settings ..............................................................................................9
Profile Parameters........................................................................................................ 10
ICF Services.................................................................................................................11
Changing Password for Initial Logon.............................................................................16
Language Settings .......................................................................................................19
OData Channel Configuration ..........................................................................................20
User, Developer, and Administrator Authorizations .......................................................23
Creating and Assigning Roles...................................................................................28
Connection Settings on the SAP NetWeaver Gateway Hub System..............................29
Connection Settings: SAP NetWeaver Gateway to Consumer...................................30
Creating a bgRFC Destination for Outbound Queues.............................................31
Registering the bgRFC Destination for the Outbound Queue .................................32
Creating the bgRFC Supervisor Destination...........................................................33
Connection Settings: SAP NetWeaver Gateway to SAP Systems..............................34
Creating a Type 3 RFC Destination on SAP NetWeaver Gateway Host to SAP
System..................................................................................................................35
Defining Trust between the SAP NetWeaver Gateway Host and Your SAP Systems
for Type 3 Connections .........................................................................................36
Configuring SAP System to Accept Assertion Tickets from SAP NetWeaver Gateway
.............................................................................................................................37
Configuring the SAP NetWeaver Gateway Host to Accept Assertion Tickets from
SAP Business Suite Systems ................................................................................38
Creating the SAP System Alias for Applications.....................................................39
Activating SAP NetWeaver Gateway ............................................................................ 41
Settings for OData Channel Service Development on Backend System ........................ 42
Displaying Models and Services................................................................................44
Define Parallelization of Batch Queries .....................................................................45
Settings for OData Channel Service Development on the Hub System ......................... 46
Assigning SAP System Alias to OData Service .........................................................47
Multiple Origin Composition ......................................................................................48
Dynamic System Alias Calculation Via /IWFND/ES_MGW_DEST_FINDER ..............51
Connection Settings on the Backend System................................................................53
Settings for Idempotent Services...............................................................................54
Defining a Remote Function Call to SAP NetWeaver Gateway .................................. 56
Connection Settings to SAP NetWeaver Gateway.....................................................57
Configure the bgRFC Supervisor Destination ............................................................58
Monitoring bgRFC Queues........................................................................................60
Business Enablement Provisioning (IW_BEP) Configuration ............................................61
Configuration Settings for SAP NetWeaver Gateway Supported Scenarios ...................... 62
Configuration Settings for OData Channel Scenarios....................................................63
Configuring Workflow for SAP NetWeaver Gateway..................................................64
Creating an Administrator Role for Workflow..........................................................65
Customizing SAP NetWeaver Gateway Workflow..................................................67
Configuring Workflow Notifications.....................................................................68
Creating a Type G RFC Destination................................................................69
Configuring User Authorizations for Push Notifications....................................70
Running Scheduled Reports...........................................................................71
Workflow Settings ..............................................................................................74
Configuring Business Process Content Services.......................................................78
Configuring Services for Deployment Scenario 1 ...................................................79
Connecting Business Process Content and Business Suite Systems..................80
Creating a Software Version for Provider System............................................82
Mapping the Software Version and Technical Model.......................................83
Creating a System Alias.....................................................................................84
Activating the Process Service...........................................................................85
Registering Process Context Service for Deployment Scenario 1 .......................86
Activating the Process Context Service..............................................................87
5. SAP NetWeaver Gateway Configuration Guide
(C) SAP AG SAP NetWeaver Gateway 2.0 SPS08 5
Configuring Services for Deployment Scenario 2 ...................................................88
Connecting Business Process Content and Business Suite Systems..................89
Creating a Software Version for Provider System............................................91
Mapping the Software Version and Technical Model.......................................92
Creating a System Alias for SAP Business Suite System ...................................93
Connecting SAP NetWeaver Gateway and Business Process Content ............... 94
Creating a System Alias for Business Process Content System.......................... 95
Activating the Process Service...........................................................................96
Registering Process Context Service for Deployment Scenario 2 .......................97
Activating the Process Context Service..............................................................98
User Authorizations for SAP Business Workflow Systems......................................99
Configuring the Task Gateway Service....................................................................100
Former Development .....................................................................................................105
Configurations for ERP on SAP NetWeaver Gateway .................................................106
Role Templates for ERP Scenarios.........................................................................109
Configurations on SAP NetWeaver Gateway for SAP ERP......................................114
Settings for Time Management Application - OData Channel .................................. 116
Configurations on the SAP NetWeaver Gateway for Time Management - OData
Channel ..............................................................................................................117
Configurations on the SAP ERP System (Provider System) for Time Management -
OData Channel ...................................................................................................119
Configurations on the SAP NetWeaver Gateway System (Consumer System) for
Leave Management.............................................................................................121
Configurations for ERP Customer- OData Channel .................................................123
Configurations for ERP Customer on the SAP NetWeaver Gateway System— OData
Channel ..............................................................................................................124
Configurations for ERP Customer on the SAP ERP System (Provider System) —
OData Channel ...................................................................................................126
Configurations for ERP Customer on the SAP NetWeaver Gateway System
(Consumer System)— OData Channel ................................................................127
Configurations for ERP Sales Documents on the SAP NetWeaver Gateway System—
OData Channel.......................................................................................................128
SOA Management Configurations on SAP ERP System .............................................130
Importing a Profile using a XML Template...............................................................131
Profile Management................................................................................................133
Importing Endpoints Template using Business Scenario Configuration.................... 135
Creating Endpoints using a Business Scenario .......................................................137
Verifying the Endpoints Created..............................................................................139
Obtaining the External Key of the Provider System .................................................140
SOA Management Configurations on the SAP NetWeaver Gateway System ..............141
Importing a Profile File............................................................................................142
Creating a System Connection to Provider System .................................................144
User Account Management.....................................................................................145
Importing a Business Scenario Configuration XML..................................................147
Configuring Service Groups using a Business Scenario ..........................................149
Verifying Logical Ports ............................................................................................151
Generic Channel Configuration...................................................................................152
Defining Settings for Idempotent Services...............................................................156
Creating an RFC Destination for the WSIL Service..................................................157
Assigning the System Alias Pointing to the SAP System .........................................158
Checking SAP System Aliases................................................................................159
Subscription Settings ..............................................................................................160
Code List....................................................................................................................161
Code List Usage .....................................................................................................162
Customizing the SAP NetWeaver Gateway System for Code List............................ 168
Code List Cache Cleanup .......................................................................................169
Configuration Settings for Generic Channel Scenarios................................................170
Settings for Customer Relationship Management on SAP NetWeaver Gateway ...... 171
Configuring GSDO to Connect to the SAP CRM System......................................176
SOA Management Configurations on SAP CRM System..................................177
6. SAP NetWeaver Gateway Configuration Guide
(C) SAP AG SAP NetWeaver Gateway 2.0 SPS08 6
Creating a New Profile in the Provider System..............................................178
Configuring Provider Systems.......................................................................179
SOA Management Configurations on SAP NetWeaver Gateway System.......... 181
Creating a Provider System in the Consumer System................................... 182
User Account Management ..........................................................................184
Settings for Reporting Management........................................................................187
Settings for Reporting Management on SAP NetWeaver Gateway....................... 188
Configuring Subscriptions for Report Results.......................................................192
Settings for Reporting Administration...................................................................193
Managing Source Systems, Report Types and Formats ...................................194
Managing Reports and their Properties ............................................................196
Configuring a New Report.............................................................................197
Configuring Report Parameters ....................................................................199
Configuring Multiple Values for a Parameter.................................................201
Configuring Delivery Formats for a Report ....................................................202
Specifying Roles for a Report .......................................................................203
Report Scheduling........................................................................................204
Managing Categories.......................................................................................205
Managing Context Variables ............................................................................206
Configuring System Time Points ......................................................................208
Managing System Time points and Data Change Events .................................209
Settings for Human Capital Management for SAP NetWeaver Gateway .................. 211
Settings for Time Management............................................................................212
Settings for Time Management on SAP NetWeaver Gateway........................... 215
Configurations on the SAP ERP System (Provider System) for Time Management
........................................................................................................................216
Configurations on the SAP NetWeaver Gateway System (Consumer System) for
Time Management...........................................................................................218
Settings for Leave Management ..........................................................................220
Configuring SAP NetWeaver Gateway System for Leave Management ............ 223
Configurations on the SAP ERP System (Provider System) for Leave
Management....................................................................................................225
Configurations on the SAP NetWeaver Gateway System (Consumer System) for
Leave Management .........................................................................................227
Settings for User Profile.......................................................................................229
Settings for Code List in the SAP NetWeaver Gateway System...............................230
Creating a GSDO Type ....................................................................................... 232
Creating a GSDO Group......................................................................................234
Assigning System Alias .......................................................................................235
Maintaining Code Type........................................................................................236
Code List Usage..................................................................................................239
Code List Cache Cleanup....................................................................................241
Configuring SAP NetWeaver Gateway System and SAP ERP System-ESA Service
...........................................................................................................................242
Configurations on the SAP ERP System (Provider System) for Code List......... 243
Configurations on the SAP NetWeaver Gateway System (Consumer System) for
Code List .........................................................................................................245
7. SAP NetWeaver Gateway Configuration Guide
(C) SAP AG SAP NetWeaver Gateway 2.0 SPS08 7
SAP NetWeaver Gateway Configuration Guide
Once you have installed [External] the SAP NetWeaver Gateway components, you must
configure your system to allow the consumer servers’ applications to retrieve the data
requested by users.
The SAP NetWeaver Gateway Configuration Guide contains the steps for customizing
settings for SAP NetWeaver Gateway and describes system configuration activities.
The sequence of mandatory and optional configuration tasks is as follows and depends on
your use case.
1. Basic configuration [Page 9] (mandatory)
2. OData Channel Configuration [Page 20]
3. Configuration Settings for content scenarios [Page 62] (optional)
Implementation Guide
The SAP NetWeaver Gateway specific configuration tasks are included in the
SAP NetWeaver Gateway Implementation Guide (IMG) which is available in the system: In
your SAP NetWeaver Gateway hub system (IW_FND) go to transaction SPRO, open the SAP
Reference IMG and navigate to: SAP NetWeaver Gateway . In your backend system
(IW_BEP) go to transaction SPRO, open the SAP Reference IMG and navigate to: SAP
NetWeaver Gateway Service Enablement .
For all steps in the IMG there is always consumer-independent documentation available. If
you want to see more information, select the Display icon before executing each step.
Note
If you have software components GW_CORE 190 and IW_FND 240 installed in your
system, the IMG tree will only offer the activities for OData Channel.
The same applies if you use SAP NetWeaver Gateway in SAP NetWeaver 7.40
(software component SAP_GWFND).
For more information, see Deployment Options [External].
Recommendation
We strongly recommend using the OData Channel (ODC) programming paradigm for
all SAP NetWeaver Gateway development.
As of SAP NetWeaver Gateway 2.0 Support Package 05, you are strongly
recommended to use the Service Builder (transaction SEGW) for your OData design-
time development . For more information, see SAP NetWeaver Gateway Service
Builder [External].
Depending on whether you want to develop SAP NetWeaver Gateway content in an
SAP Business Suite backend system or in an SAP NetWeaver Gateway hub system,
you can choose between embedded deployment or central hub deployment. For
more information, see Embedded Versus Hub Deployment [External] and
Deployment Options [External].
8. SAP NetWeaver Gateway Configuration Guide
(C) SAP AG SAP NetWeaver Gateway 2.0 SPS08 8
As such, several sections in the Implementation Guide (IMG) are merely available for
reference and maintenance purposes.
In the backend system this is the section in the SAP Reference IMG under SAP
NetWeaver Gateway Service Enablement Generic Channel .
In the SAP NetWeaver Gateway hub system these are the sections in the SAP
Reference IMG under SAP NetWeaver Gateway Former Development .
Additional Software Components
Depending on the additional SAP NetWeaver Gateway components you implement, further
component-specific configuration steps are required:
Business
Enablement
Provisioning
(IW_BEP)
See Connection Settings for OData Channel and BEP [Page 53] and
Backend Event Publisher (BEP) Configuration [Page 61].
The IW_BEP specific configuration tasks are included in the Gateway
Service Enablement Implementation Guide (IMG) which is available in the
system: In transaction SPRO open the SAP Reference IMG and navigate
to: SAP NetWeaver Gateway Service Enablement Backend OData
Channel Connection Settings to SAP NetWeaver Gateway and
Backend Event Publisher Administration.
Screen Scraping
(IW_SCS)
For Screen Scraping you only need to configure roles based on certain
authorization templates. The templates specify the authorizations for
content that can be accessed by the users and activities for developers.
For more information, see Setting Up User and Administrator
Authorizations [Page 23].
SAP NetWeaver
Gateway with
HANA (IW_HDB)
If you want to install the SAP NetWeaver Gateway with HANA component
(IW_HDB), this requires SAP NetWeaver 7.02 SPS09 comprising an ABAP
Database Connectivity (ADBC) installation. ADBC is an object-based
ABAP API for programming relational database accesses. It follows the
Java Database Connectivity (JDBC) diction in its class and model
structure.
Workflow
You can find more information about the Workflow-related configuration
activities in Configuring Workflow for SAP NetWeaver Gateway [Page 64].
In addition, the relevant IMG activities are available in the Implementation
Guide in the backend system: In transaction SPRO open the SAP
Reference IMG and navigate to: SAP NetWeaver Gateway Service
Enablement Content Workflow Settings .
Business Process
Enablement
For the special services provided within Business Process Enablement
[External], such as Process Service and Process Context Service, the
relevant IMG activities are available in the Implementation Guide in the
backend system. In transaction SPRO open the SAP Reference IMG and
navigate to: SAP NetWeaver Gateway Service Enablement Content
Business Process Enablement .
Consumer Settings
For information on configuration settings which need to be carried out for the different
consumer scenarios and applications, see Configuration Settings for SAP NetWeaver
Gateway Supported Scenarios [Page 62].
9. SAP NetWeaver Gateway Configuration Guide
(C) SAP AG SAP NetWeaver Gateway 2.0 SPS08 9
Basic Configuration Settings
After having installed [External] the SAP NetWeaver Gateway software components you need
to carry out several configuration steps.
Before starting with the configuration for SAP NetWeaver Gateway itself, you need to collect
some information about the SAP NetWeaver Gateway host.
Required
Information
Description Example
Fully Qualified
Domain Name
(FQDN)
Name of the SAP NetWeaver Application
Server ABAP (AS ABAP) system or the load
balancing device.
server.domain.com
Administrator
credentials
Login information of the administrator of the
SAP NetWeaver AS ABAP to install and
maintain the system
SAP administrator
HTTP/HTTPS
ports
HTTP and HTTPS port numbers of the central
instance of the AS ABAP
80000 for HTTP and
80001 for HTTPS
SAP system
For each SAP system to which you want to
connect the SAP NetWeaver Gateway server,
you need the following information:
System ID, system number
Server name
HTTP / HTTPS port
Administrator credentials
In addition, several settings are important for smooth operations:
Profile Parameters [Page 10]
ICF Services [Page 11]
Initial Logon [Page 16]
Language Settings [Page 19]
10. SAP NetWeaver Gateway Configuration Guide
(C) SAP AG SAP NetWeaver Gateway 2.0 SPS08 10
Profile Parameters
In both your SAP system and in the SAP NetWeaver Gateway system you need to set the
following profile parameters to certain values:
Profile Parameter Value
login/accept_sso2_ticket 1
login/create_sso2_ticket 2
You maintain these profile parameters via transaction RZ10.
More Information
For information on profile parameters and profile parameter maintenance, see Profile
Parameters for Logon and Password (Login Parameters) [External] and Changing and
Switching Profile Parameters [External].
11. SAP NetWeaver Gateway Configuration Guide
(C) SAP AG SAP NetWeaver Gateway 2.0 SPS08 11
ICF Services
Once you have installed the Application Server ABAP (AS ABAP) all Internet Communication
Framework (ICF) services are available in an inactive state for security reasons. After the
installation you have to decide which services must be activated for the applications you want
to use.
Caution
Activated ICF services represent a security risk because they can be accessed
directly by the HTTP protocol from the Internet. You therefore need to use suitable
methods for restricting access, for example, only permitting access to the ICF service
for users with the appropriate authorizations.
Since multiple services can be executed when you call a URL, all service nodes must be
activated in the SICF tree. The URL path is mapped in ICF subnodes (services). For
example, if you want to activate the services for URL /sap/public/icman, you have to
activate the service tree default_host in transaction SICF. Then you have to activate
services sap, public and icman separately.
You activate an ICF service as follows:
1. Select the required ICF service in the ICF tree in transaction SICF.
2. Activate the ICF service in one of the following ways:
o Using menu option Service/Host Activate .
o Using the context menu and choosing Activate Service.
You can either activate only a selected service node (Yes), or the selected service node
including all the subservices maintained for it in SICF (Yes with tree icon):
(Example)
For SAP NetWeaver Gateway you need to activate the following services:
/sap/public/opu
Note that /sap/public/opu/resources is needed for loading resources, such as
images in the MIME repository. For example, the generic player gets a service
document which contains links to images which the player should display for a Sales
Order. Then the generic player downloads the image via URL from the MIME
Repository; for example, http://.../sap/opu/resources/pic1.png.
12. SAP NetWeaver Gateway Configuration Guide
(C) SAP AG SAP NetWeaver Gateway 2.0 SPS08 12
/sap/opu/odata with its sub-nodes.
This is the standard mode for all new applications. When creating a service a new
node is created automatically.
/sap/opu/sdata with the following sub-nodes:
o /sap/opu/sdata/iwcnt
o /sap/opu/sdata/iwfnd
o /sap/opu/sdata/sap
This is the node used for existing applications, it is called Compatibility Mode for
SP02.
If you use Web service based scenarios, that is, if content is consumed which is provided via
Web services, then you also need to activate the following nodes on your target system:
/sap/bc/srt/xip/sap
/sap/bc/webdynpro/sap/saml2
/sap/public/bc
/sap/public/bc/ur
/sap/public/mysssocnt
Note
If the default_host node is inactive in transaction SICF, the HTTP requests could
result in an ABAP runtime error RAISE_EXCEPTION with the following short text:
Exception condition "HOST_INACTIVE" triggered.
If a service is inactive in transaction SICF, an error text appears when you try to
access the service.
You can also activate services from the SAP Implementation Guide (IMG). In transaction
SPRO, choose Display SAP Reference IMG. The path in the Implementation Guide for SAP
NetWeaver is: Application Server Internet Communication Framework Activate HTTP
Services or Activate Services in Installation.
Note that the system performs a check against the authorization object S_ICF_ADM
[External] when an ICF node is created.
Standard Mode
This standard mode refers to the ICF node /sap/opu/odata. This node is available for
OData Channel based applications. When creating a service a new node is created
automatically.
Note
The standard mode is the default for all new applications. All new development will be
done on this mode. New functions and features will be available for this mode.
13. SAP NetWeaver Gateway Configuration Guide
(C) SAP AG SAP NetWeaver Gateway 2.0 SPS08 13
The request handler for this node is /IWFND/CL_SODATA_HTTP_HANDLER.
The following list consists of the differences of the standard mode as opposed to the
compatibility mode for SP02:
XSRF protection
See also Cross-Site Request Forgery Protection [External]
Content-Type required for Put/Post request
An unsupported media type error is thrown if Content-Type is not set for Put/Post
requests. Set parameter:
Content-Type=application/xml
XSRF Security Token
Security Session Id
$format parameter
$format=xml leads to an error except for service document. Do not use it for all
requests except for those to get service document .
Null values in Put/Post Request
Empty property elements (for example, <name/>) are not allowed anymore. Nullable
needs to be set properly, and besides that, if an entry with a null string is to be
created set m:null="true", for example, <name m:null="true" />.
Null values in the response of a Get/Put request
Intial values for date time fields in combination with nullable properties are rendered
as <...m:null="true" />.
Values of keys in Post request in case of server generated keys
If the keys are generated on the server the values need to be filled in the post request
anyway. m:null is not allowed.
Rendering of key predicates
See http://www.odata.org/developers/protocols/overview#AbstractTypeSystem.
Key properties
Sending properties that are not key fields in an URI is not longer possible.
String parameters
Quotation marks enclosing string parameters (for example, search string) are now
required and removed.
Parameters for function imports
Parametrize with literals, for example, datetime.... See also
http://www.odata.org/developers/protocols/overview#AbstractTypeSystem.
14. SAP NetWeaver Gateway Configuration Guide
(C) SAP AG SAP NetWeaver Gateway 2.0 SPS08 14
Inverted commas in URI
Inverted commas in URI, for example, $filter=name eq 'Jame''s shop' can
now be properly escaped by an inverted comma.
OData error response
The OData error response has been enhanced. See
http://www.odata.org/media/6655/%5Bmc-
apdsu%5D%5B1%5D.htm#_Toc246716641.
The code field is now either build from the leading error message of the message
container [External] or build from the text id of the exception [External].
The structured inner error section is available showing Extended Passport (EPP)
transaction ID. All messages of the message container and the additionally provided
error details are shown in a special format (micro format).
Things
The workspace for Things, element <app:workspace
sap:semantics="things">, is no longer available.
Service maintenance
The service maintenance transaction distinguishes between services of the Standard
Mode and of the Compatibility Mode for SP02.
Compatibility Mode for SP02
This compatibility mode for SAP NetWeaver Gateway 2.0 SP02 refers to the ICF node
/sap/opu/sdata. This node is available for existing applications which might be based
either on OData Channel or Generic Channel.
Caution
This node is in maintenance mode.
The request handler for this node is /IWFND/CL_SDATA_ODATA_APP.
Alias Handling in ICF
The ICF standard function of external aliases [External] is also available for SAP NetWeaver
Gateway for the Standard Mode, that is, for ICF node /sap/opu/odata. Thus you can
define an external alias for your service if you have registered class
/IWFND/CL_SODATA_HTTP_HANDLER as handler in the Handler List for your service node.
Note
Note that external aliases are not supported for namespaces in SICF.
If the handler /IWFND/CL_SODATA_HTTP_HANDLER is not yet registered for your service
node, enter the handler name on tab Handler List and activate your service. After the handler
has been set, you can define the external alias.
15. SAP NetWeaver Gateway Configuration Guide
(C) SAP AG SAP NetWeaver Gateway 2.0 SPS08 15
More Information
Administration of ICF server functions (authorization assignment): Server Function
Administration [External]
Administration of ICF client functions (creation of RFC destinations, and so on): Client
Function Administration [External]
ICF services: Creating and Configuring an ICF Service [External]
Authentication: Defining the Logon Procedure [External]
16. SAP NetWeaver Gateway Configuration Guide
(C) SAP AG SAP NetWeaver Gateway 2.0 SPS08 16
Changing Password for Initial Logon
Note
This section is only relevant if you want to change the password for the initial logon
procedure.
The logon configurations for SAP NetWeaver Gateway are handled via the ICF layer. For
more information, see Defining the Logon Procedure [External].
SAP systems may require some additional (browser) features if the password needs to be
changed because of being initial or outdated. Therefore, the ICF nodes can be configured to
permit the initial password change and the direct logon. An additional ICF node is offered to
allow the change of passwords with a browser.
Using an ICF Node for Changing Passwords
SAP NetWeaver Gateway offers a special ICF node which can be accessed to change the
password, for example for the initial logon sequence. This node is used to change the
password and to redirect to any other custom web page.
You can find this special ICF node in the service tree under
/default_host/sap/opu/utils under the name initial_logon.
You can access this node as soon as it has been activated via the URL
<host>:<port>/sap/opu/utils/initial_logon.
The call of the service requires authentication and does allow to change an initial password
via a browser application. If the URL is extended by ?redirectURL=/X then the browser is
redirected to the URL wherever X points to. A typical use case for such a redirect URL would
be to display additional information, so that the new password data could be used in the
settings of a mobile application. If needed, a redirect URL can be configured and will take
precedence over all basic settings.
(initial_logon)
Changing the Password for ICF Nodes Accessed by Mobile Devices
1. In transaction SICF choose Execute (F8) to display the service tree hierarchy.
2. Expand the default host and navigate to the ICF parent node of the initial logon
/default_host/sap/opu/utils/initial_logon. This node shall be the root
17. SAP NetWeaver Gateway Configuration Guide
(C) SAP AG SAP NetWeaver Gateway 2.0 SPS08 17
node which is accessed by your mobile devices and where you want to deny the
direct access via mobile device.
3. Double-click on the node and change to edit mode.
4. On tab Error Pages choose sub-tab Logon Errors.
5. Choose System Logon.
(System logon)
6. Choose Configuration.
7. Choose Define Service-Specific Settings.
8. Under Logon Layout and Procedure choose Custom Implementation and enter ABAP
Class /IWFND/CL_COC_SYSTEM_LOGIN.
18. SAP NetWeaver Gateway Configuration Guide
(C) SAP AG SAP NetWeaver Gateway 2.0 SPS08 18
(Custom implementation example)
9. Choose Input (Enter) to save your settings.
Caution
If you have administrator rights you have the additional option to save your settings
as global settings. Do not use Save as Global Settings.
10. Activate your ICF node.
Logoff URL
The Internet Communication Framework also offers a default logoff URL on each system.
You can define your own logoff pages via Error Pages Logoff Page .
More Information
For more information on the generic system logon functionality in ICF, see System Logon
[External].
19. SAP NetWeaver Gateway Configuration Guide
(C) SAP AG SAP NetWeaver Gateway 2.0 SPS08 19
Language Settings
The language which is displayed to the user depends on a variety of factors. For more
information see Determining the Logon Language [External].
As to languages, the SAP NetWeaver Gateway system supports only the intersecting set of
the languages of the connected SAP Business Suite backend systems.
20. SAP NetWeaver Gateway Configuration Guide
(C) SAP AG SAP NetWeaver Gateway 2.0 SPS08 20
OData Channel Configuration
Depending on your underlying SAP NetWeaver release the configuration settings for OData
Channel and the structure in the Implementation Guide (IMG) may differ.
SAP NetWeaver 7.00 and 7.01
The OData Channel configuration settings are available in the Implementation Guide (IMG) in
the system where software component IW_FND is deployed. In the SAP Reference IMG
navigate to SAP NetWeaver Gateway .
(OData Channel IMG for IW_FND in 7.00 and 7.01)
SAP NetWeaver 7.02 and 7.31
The OData Channel configuration activities are listed in the Implementation Guide (IMG) in
the system where software component IW_FND is deployed. In the SAP Reference IMG
navigate to SAP NetWeaver Gateway OData Channel .
(OData Channel IMG in IW_FND)
21. SAP NetWeaver Gateway Configuration Guide
(C) SAP AG SAP NetWeaver Gateway 2.0 SPS08 21
Recommendation
We strongly recommend using the OData Channel (ODC) programming paradigm for
all SAP NetWeaver Gateway development.
As of SAP NetWeaver Gateway 2.0 Support Package 05, you are strongly
recommended to use the Service Builder (transaction SEGW) for your OData design-
time development . For more information, see SAP NetWeaver Gateway Service
Builder [External].
Depending on whether you want to develop SAP NetWeaver Gateway content in an
SAP Business Suite backend system or in an SAP NetWeaver Gateway hub system,
you can choose between embedded deployment or central hub deployment. For
more information, see Embedded Versus Hub Deployment [External] and
Deployment Options [External].
Apart from basic configuration settings the OData Channel configuration activities for the
SAP Business Suite backend system are listed in the Implementation Guide (IMG) in the
backend system where software component IW_BEP is deployed. In the SAP Reference IMG
navigate to SAP NetWeaver Gateway Service Enablement Backend OData Channel .
(OData Channel IMG in IW_BEP)
SAP NetWeaver 7.40
If you use software component SAP_GWFND in SAP NetWeaver 7.40, IMG activities for
SAP NetWeaver Gateway Foundation 7.40 are available. In the SAP Reference IMG navigate
to SAP NetWeaver Gateway and SAP NetWeaver Gateway Service Enablement .
There you find all the relevant OData Channel IMG activities.
22. SAP NetWeaver Gateway Configuration Guide
(C) SAP AG SAP NetWeaver Gateway 2.0 SPS08 22
Settings
User, Developer and Administrator Authorizations [Page 23]
Connection Settings on the SAP NetWeaver Gateway Hub System [Page 29]
Activating SAP NetWeaver Gateway [Page 41]
Settings for OData Channel Service Development on Backend System [Page 42]
Settings for OData Channel Service Development on the Hub System [Page 46]
Connection Settings on the Backend System [Page 53]
More Information
Basic Configuration Settings [Page 9]
OData Channel [External]
23. SAP NetWeaver Gateway Configuration Guide
(C) SAP AG SAP NetWeaver Gateway 2.0 SPS08 23
User, Developer, and Administrator Authorizations
After you have installed the SAP NetWeaver Gateway components you require, you need to
set up an administrator role for SAP NetWeaver Gateway components and assign users to it.
Then you set up one or several user roles and assign users to it as well. As you cannot
change existing SAP roles, you create your own roles or copy existing roles to your new
custom roles.
The SAP system includes templates as opposed to actual users, so you must use the
available role templates to create the users you require in the SAP NetWeaver Gateway
system. If the users you require exist in your SAP Business Suite backend system, you can
replicate these users in the SAP NetWeaver Gateway system by connecting the SAP
NetWeaver Gateway system to Central User Administration or to SAP Identity Management
and synchronize the users in this way. If this is not possible, you must create the users
manually.
SAP NetWeaver Gateway provides predefined roles as templates for:
Developers
Administrators
End users of the different content scenarios
These templates follow the naming convention /IWCNT/RT_USER_<application
name>.
Support colleagues
These templates provide display authorizations only and are intended to be used by
support colleagues who need to view applications logs.
Use the predefined templates to create administrator, developer, user, and support roles for
SAP NetWeaver Gateway components. The template names begin with a namespace ID that
corresponds to the software components you use.
SAP NetWeaver Gateway Developer Role
Create a developer role based on the available templates for all users that are to carry out
development tasks such as creating services. Use the developer role /IWBEP/RT_MGW_DSP
for accessing a remote system from the Service Builder (transaction SEGW) at design time.
The following templates are available for developers:
Template Type Template Name Template for
Framework /IWFND/RT_BOR_DEV SAP NetWeaver Gateway BOR Developer
Framework /IWFND/RT_DEVELOPER SAP NetWeaver Gateway Developer
OData Channel /IWBEP/RT_MGW_DEV OData Channel Developer
Screen Scraping /IWSCS/RT_SCR_DEV
SAP NetWeaver Gateway Screen Scraping
Developer
For more information, see Assigning
Authorization to Transaction and Search Help
[External]
24. SAP NetWeaver Gateway Configuration Guide
(C) SAP AG SAP NetWeaver Gateway 2.0 SPS08 24
SAP NetWeaver Gateway Administrator Role
Create a role for an administrator user with permissions and privileges for several tasks,
including the following:
Create services.
Analyze logs and identify potential issues with the SAP NetWeaver Gateway
landscape.
Install, configure, and maintain SAP NetWeaver Gateway components and
applications that run on SAP NetWeaver Gateway.
Configure and maintain users’ data including roles and user mapping.
In the SAP Reference Implementation Guide (IMG) (transaction SPRO), navigate to SAP
NetWeaver Gateway OData Channel Configuration User Settings Define Role for SAP
NetWeaver Gateway Administrator and click on the Activity icon. The Role Maintenance
page displays.
To check that the role was properly created and assigned, log onto the SAP NetWeaver
Gateway system as the user you just assigned. You should be able to access transaction
SPRO and find the SAP NetWeaver Gateway Implementation Guide there. You can now log
onto the SAP NetWeaver Gateway host as the administrator user you have just created to
configure SAP NetWeaver Gateway components and content, and to install consumer
applications.
For more information about SAP user administrator types, see Setting Up User and
Authorization Administrators [External].
The following templates are available for administrators:
Template Type Template Name Template for
Framework /IWFND/RT_ADMIN
SAP NetWeaver Gateway Framework
Administrator
Content Scenario /IWCNT/RT_ADMIN_REP
SAP NetWeaver Gateway Reporting
Management Administrator.
See Settings for Reporting
Management [Page 188] for details on
authorizations required.
OData Channel /IWBEP/RT_MGW_ADM OData Channel Administrator
Business Enablement
Provisioning (IW_BEP
component)
/IWBEP/RT_BEP_ADM Business Enablement Provisioning
Administrator
Workflow /IWWRK/RT_WF_ADM SAP NetWeaver Gateway Workflow
Administrator
25. SAP NetWeaver Gateway Configuration Guide
(C) SAP AG SAP NetWeaver Gateway 2.0 SPS08 25
SAP NetWeaver Gateway User Role
Create a role for a user with permissions and privileges for user-specific tasks. Depending on
your application, you can either specify different authorizations for different user roles or have
all authorizations bundled together in one user role.
Note
You must be a SAP NetWeaver Gateway administrator or have a SAP user
administrator to create user roles.
In the SAP Reference Implementation Guide (IMG) (transaction SPRO), navigate to SAP
NetWeaver Gateway OData Channel Configuration User Settings Define Role for SAP
NetWeaver Gateway User and click on the Activity icon. The Role Maintenance page
displays. Proceed as described below.
Once you have assigned users to the relevant roles, you can log on as one of these users
and work as them.
If you use Web service based scenarios, copy the SAP_BC_WEBSERVICE_CONSUMER role to
a customer role for end users. Then assign this customer role to your end users. To do this,
proceed as follows:
1. Click on the Activity icon of the IMG activity Define Role for SAP NetWeaver Gateway
User mentioned above.
The Role Maintenance page displays.
2. In the Role field, enter your customer role for Web services and choose Change.
3. On the User tab enter the names of the users to whom you want assign this role and
save your settings.
4. Choose User Comparison.
5. Choose Complete Comparison.
6. Save your settings.
To check that you have successfully assigned roles to users, take some of the users assigned
to the different roles and make sure that you can log on successfully. If these steps have not
been performed successfully, an HTTP request of an authenticated user returns an HTTP 500
error.
The following templates are available for end users:
Template Type Template Name Template for
Framework /IWFND/RT_GW_USER SAP NetWeaver Gateway User
Framework /IWFND/RT_TU_NOTIF SAP NetWeaver Gateway Technical User
for Notifications
Content Scenario /IWCNT/RT_USER_LEMA
SAP NetWeaver Gateway Leave
Management User.
See Settings for Leave Management
Application [Page 220] for details on
authorizations required.
26. SAP NetWeaver Gateway Configuration Guide
(C) SAP AG SAP NetWeaver Gateway 2.0 SPS08 26
Template Type Template Name Template for
Content Scenario /IWCNT/RT_USER_REP
SAP NetWeaver Gateway Reporting
Management User
See Settings for Reporting Management
[Page 188] for details on authorizations
required.
Content Scenario /IWCNT/RT_USER_SS SAP NetWeaver Gateway Sample
Services User
Content Scenario /IWCNT/RT_USER_TRVL SAP NetWeaver Gateway Travel User
Content Scenario /IWCNT/RT_USER_TIMA
SAP NetWeaver Gateway Time
Management User.
See Settings for Time Management
Application [Page 212] for details on
authorizations required.
Content Scenario /IWCNT/RT_USER_WF SAP NetWeaver Gateway Workflow User
Content Scenario /IWCNT/RT_USER_ACT
SAP NetWeaver Gateway Activity
Management User
See Settings for Customer Relationship
Management on SAP NetWeaver
Gateway [Page 171] for details on
authorizations required.
Content Scenario /IWCNT/RT_USER_ACCNT
SAP NetWeaver Gateway User for
Account Management
See Settings for Customer Relationship
Management on SAP NetWeaver
Gateway [Page 171] for details on
authorizations required.
Content Scenario /IWCNT/RT_USER_CONT
SAP NetWeaver Gateway User for
Contact Management
See Settings for Customer Relationship
Management on SAP NetWeaver
Gateway [Page 171] for details on
authorizations required.
OData Channel /IWBEP/RT_MGW_USR OData Channel User
OData Channel /IWHDB/RT_USER OData Channel HANA Integration User
OData Channel /IWBEP/RT_SUB_USR On-behalf Subscription User
Business Enablement
Provisioning (IW_BEP
component)
/IWBEP/RT_BEP_USR Business Enablement Provisioning User
Workflow /IWWRK/RT_WF_GW_USR SAP NetWeaver Gateway Workflow User
27. SAP NetWeaver Gateway Configuration Guide
(C) SAP AG SAP NetWeaver Gateway 2.0 SPS08 27
Template Type Template Name Template for
Workflow /IWWRK/RT_WF_SUB_USR
On-Behalf Subscription for
SAP NetWeaver Gateway Workflow
Services
Screen Scraping /IWSCS/RT_SCR_USR
SAP NetWeaver Gateway Screen
Scraping User
For more information, see Assigning
Authorization to Transaction and Search
Help [External]
SAP NetWeaver Gateway Support User Role
The following templates are available for support users (display authorization only). The
support templates are available in the SAP NetWeaver Gateway hub system and the
SAP Business Suite backend systems respectively. These templates contain read-only
authorizations to access SLG1, the application log viewer [External] and the corresponding log
objects and sub-objects.
Template
Type
Template Name Template for
Support /IWFND/GW_SUPPORT_RO Read-only supportability role for SAP NetWeaver
Gateway system
Support /IWBEP/GW_SUPPORT_RO Read-only supportability role for SAP Business
Suite backend system
More Information
Creating and Assigning Roles [Page 28]
Roles in the SAP NetWeaver Gateway Landscape [External]
28. SAP NetWeaver Gateway Configuration Guide
(C) SAP AG SAP NetWeaver Gateway 2.0 SPS08 28
Creating and Assigning Roles
To create a role and assign it to users (user roles, administrator roles or developer roles),
proceed as follows:
1. On the Role Maintenance page enter an existing SAP_BC* role : For an administrator
role choose a listed standard administrator role, for example SAP_BC_BASIS_ADMIN,
and for a user role, enter an existing generic user role, for example
SAP_BC_ENDUSER.
2. Select Copy Role to create a copy of the standard role.
3. In the Query dialog box, enter a name for the new role and then select Copy all.
The new role is created.
4. On the Role Maintenance page, select Change.
5. On the Authorizations tab select Change Authorization Data under the Maintain
Authorization Data and Generate Profiles section.
6. Select Edit Insert authorization(s) From template... .
The Choose Template page displays.
7. Select the appropriate template from the list (see User and Administrator
Authorizations [Page 23]) and choose Continue (Enter).
8. Choose Generate.
9. On the Generate Profile window choose Generate.
10. In the Assign Profile Name for Generated Authorization Profile dialog box, maintain
the profile name according to your requirements and choose Execute (Enter).
11. The Change role: Authorizations page displays, with the Status of the profile showing
as generated.
12. Go back to the Change Roles page and select the User tab.
13. Under User Assignments enter the names of the users to whom you want to assign
this role and save your settings.
14. Choose User Comparison.
15. Choose Complete Comparison.
16. Save your settings.
For more information about role maintenance, see Changing Standard Roles [External].
29. SAP NetWeaver Gateway Configuration Guide
(C) SAP AG SAP NetWeaver Gateway 2.0 SPS08 29
Connection Settings on the SAP NetWeaver Gateway Hub
System
Connection Settings: SAP NetWeaver Gateway to Consumer [Page 30]
Connection Settings: SAP NetWeaver Gateway to SAP Systems [Page 34]
30. SAP NetWeaver Gateway Configuration Guide
(C) SAP AG SAP NetWeaver Gateway 2.0 SPS08 30
Connection Settings: SAP NetWeaver Gateway to
Consumer
When using Push flow and also Web services, you have to specify settings from your
SAP NetWeaver Gateway system to consumers.
In the following sections only the basic configuration activities to set up the connection
between the SAP NetWeaver Gateway host and the consumer system are listed. You can
find the complete set of configuration activities in the SAP NetWeaver Gateway Configuration
implementation guide (IMG) in the system. In Transaction SPRO open the SAP Reference
IMG and navigate to SAP NetWeaver Gateway OData Channel Configuration
Connection Settings SAP NetWeaver Gateway to Consumer .
Creating a bgRFC Destination for Outbound Queues [Page 31]
Registering the bgRFC Destination for the Outbound Queue [Page 32]
Creating the bgRFC Supervisor Destination [Page 33]
31. SAP NetWeaver Gateway Configuration Guide
(C) SAP AG SAP NetWeaver Gateway 2.0 SPS08 31
Creating a bgRFC Destination for Outbound Queues
You must create a Background Remote Function Call (bgRFC) destination for
communications in an outbound queue or an inbound queue respectively.
To create a bgRFC destination for the outbound queue, proceed as follows:
1. In transaction SPRO open the SAP Reference IMG and navigate to: SAP
NetWeaver Gateway OData Channel Configuration Connection Settings SAP
NetWeaver Gateway to Consumer Create RFC Destination for Outbound Queues
and click on the Activity icon.
2. Choose Create.
3. In RFC Destination, enter IWFND_BGRFC_DEST.
4. In Connection Type, enter 3.
5. In Description 1, enter RFC Destination for Outbound Queues.
6. Choose Enter and then select the Special Options tab.
7. In the Select Transfer Protocol section, select the option Classic with bgRFC from the
list and save your settings.
8. Accept the warning message with Yes.
9. Choose Connection test.
Information about the connection type displays.
32. SAP NetWeaver Gateway Configuration Guide
(C) SAP AG SAP NetWeaver Gateway 2.0 SPS08 32
Registering the bgRFC Destination for the Outbound
Queue
Register the bgRFC destination for the outbound queue to handle communications efficiently.
Proceed as follows:
1. In transaction SPRO open the SAP Reference IMG and navigate to: SAP
NetWeaver Gateway OData Channel Configuration Connection Settings SAP
NetWeaver Gateway to Consumer Register RFC Destination for Outbound Queues
and click on the Activity icon.
2. Select the Define Inbound Dest. tab.
3. Choose Create.
4. In the Inb. Dest. Name field, enter IWFND_BGRFC_DEST.
5. Choose Enter and Save.
6. In the New Prefix field, enter IWFND_CNP for example and choose Create. Repeat the
step using IWCNT_WF, for example.
7. Save your settings.
8. On the Scheduler: Destination tab choose Create.
A message displays, asking if you want an outbound or inbound destination.
9. Choose Inbound.
10. In the Destination field, enter IWFND_BGRFC_DEST and choose Save.
11. Save your settings.
33. SAP NetWeaver Gateway Configuration Guide
(C) SAP AG SAP NetWeaver Gateway 2.0 SPS08 33
Creating the bgRFC Supervisor Destination
The supervisor destination for bgRFC receives the configuration settings for the bgRFC
scheduler and also starts or stops the schedulers as required.
Note
The bgRFC supervisor user you specify must have authorizations from authorization
object S_RFC. These are defined in role SAP_BC_BGRFC_SUPERVISOR.
To create the bgRFC supervisor destination, proceed as follows:
1. In transaction SPRO open the SAP Reference IMG and navigate to: SAP
NetWeaver Gateway OData Channel Configuration Connection Settings SAP
NetWeaver Gateway to Consumer Create bgRFC Supervisor Destination and click
on the Activity icon.
2. On tab Define Supervisor Dest. choose Create.
3. In the Destination Name field, enter BGRFC_SUPERVISOR.
4. In the User Name field, enter a user name, for example, BgRFC_user.
5. Select Create User and choose Enter.
6. Choose Save.
7. Select Generate Password and choose Save.
8. On the bgRFC Destination page, select Save.
34. SAP NetWeaver Gateway Configuration Guide
(C) SAP AG SAP NetWeaver Gateway 2.0 SPS08 34
Connection Settings: SAP NetWeaver Gateway to SAP
Systems
You must configure settings for SAP NetWeaver Gateway components and define how these
settings interface with your existing SAP Business Suite system (backend system).
In the following sections only the basic configuration activities are listed. You can find the
complete set of configuration activities in the SAP NetWeaver Gateway Configuration
Implementation Guide (IMG) in the system. In transaction SPRO open the SAP Reference IMG
and navigate to SAP NetWeaver Gateway OData Channel Configuration Connection
Settings SAP NetWeaver Gateway to SAP System .
Defining Trust between the SAP NetWeaver Gateway Host and Your SAP System
[Page 36]
Creating a Type 3 RFC Destination on SAP NetWeaver Gateway Host to SAP [Page
35]
Configuring SAP System to Accept Assertion Tickets from SAP NetWeaver Gateway
[Page 37]
Configuring the SAP NetWeaver Gateway Host to Accept Assertion Tickets [Page 38]
Creating the System Alias for Applications [Page 39]
35. SAP NetWeaver Gateway Configuration Guide
(C) SAP AG SAP NetWeaver Gateway 2.0 SPS08 35
Creating a Type 3 RFC Destination on SAP NetWeaver
Gateway Host to SAP System
A Type 3 connection from the SAP NetWeaver Gateway host to the SAP Business Suite
system is required for all scenarios. Create this as follows
1. In transaction SPRO open the SAP Reference IMG and navigate to: SAP
NetWeaver Gateway OData Channel Configuration Connection Settings SAP
NetWeaver Gateway to SAP System Manage RFC Destinations and click on the
Activity icon.
2. Choose Create.
3. In the RFC Destination field, enter the RFC destination name in the following format:
<system id >CLNT<Client>.
4. In the Connection Type field, enter 3.
5. In the Description 1 field, enter an explanatory text, for example, RFC Destination
to SAP Server.
6. Save your settings.
7. On tab Technical Settings and Load Balancing select the relevant option according to
your system’s settings.
8. In the Target Host field, enter the (message) server name of the of the SAP system.
9. In the System Number field, enter the SAP NetWeaver Gateway system number, for
example, 00.
10. On tab Logon & Security enter the SAP system’s client number.
11. Activate Current User.
12. For Trust Relationship activate Yes.
Note
Ensure that you have previously created the trusted relationship, as outlined in
Defining Trust between the SAP NetWeaver Gateway Host and Your SAP System
[Page 36].
13. Save your settings.
To check that you have successfully created the type 3 connection, choose Connection Test.
The connect test should pass.
If the user ID with which you are logged on to SAP NetWeaver Gateway and your user ID for
the SAP system is the same, and this user ID has the object S_RFCACL assigned to it on the
SAP system, select Remote Logon. You should not see any error messages in the status. If
you have any problems, check SAP Note 128447 for troubleshooting tips.
36. SAP NetWeaver Gateway Configuration Guide
(C) SAP AG SAP NetWeaver Gateway 2.0 SPS08 36
Defining Trust between the SAP NetWeaver Gateway
Host and Your SAP Systems for Type 3 Connections
You define the trust relationship between your SAP Business Suite system and the SAP
NetWeaver Gateway host by configuring the SAP Business Suite system (backend system) to
be the trusting system, and the SAP NetWeaver Gateway host to be the trusted system.
Note
This is simply a technical RFC destination used to establish the trust. It is not used
during runtime.
To configure trust, proceed as follows:
1. On the SAP business system, open transaction SM59 and choose Create.
2. In the RFC Destination field, enter the RFC destination name in the following format:
<system id >CLNT<Client>..
3. In the Connection Type field, enter 3.
4. In the Description 1 field, enter an explanatory text, for example, RFC Destination
to SAP NetWeaver Gateway Server.
5. Save your settings.
6. On tab Technical Settings and Load Balancing select the relevant option according to
your system’s settings.
7. In the Target Host field, enter the (message) server name of the SAP NetWeaver
Gateway system.
8. In the System Number field, enter the SAP NetWeaver Gateway system number, for
example, 00.
9. Save your settings.
10. In transaction SMT1 choose Create.
The wizard for creating trusting relationships displays.
11. Proceed with the steps outlined in the wizard.
In the RFC Destination field, enter the RFC destination you created.
An RFC logon to the SAP NetWeaver Gateway host takes place and the necessary
information is exchanged between the systems.
12. Log on to the SAP NetWeaver Gateway host using your administrator user and
password.
The trusted entry for the SAP NetWeaver Gateway host displays.
13. Save your settings.
Note
End users must have authorization object S_RFCACL assigned to them before they
can use a trusted connection. For more information, see RFC Trusted/Trusting
Systems [External].
37. SAP NetWeaver Gateway Configuration Guide
(C) SAP AG SAP NetWeaver Gateway 2.0 SPS08 37
Configuring SAP System to Accept Assertion Tickets
from SAP NetWeaver Gateway
You must configure your SAP Business Suite (backend) system to accept SAP assertion
tickets from the SAP NetWeaver Gateway host for message-based Web service
communication.
To accept SAP assertion tickets, proceed as follows:
1. Make sure that the profile parameters are set as outlined in Profile Parameters [Page
10].
2. In your backend system go to transaction SSO2 to run the SSO2 administration
wizard.
Note
If transaction SSO2 does not work, use STRUSTSSO2 to import the certificates
from the SAP NetWeaver Gateway server; you must import them manually.
For further information, see Using Transaction STRUSTSSO2 in SAP System
>= 4.6C [External].
3. Enter the Type 3 RFC destination created above (for your SAP NetWeaver Gateway
system) or the Host Name and Instance Number for the SAP NetWeaver Gateway
system in the appropriate fields.
4. Choose Execute.
On the Logon page enter your password.
The SSO2 administration report for the designated SAP system displays.
5. Choose Activate (Enter Certificate in ACL and, if Necessary, Certificate List) to
configure the SAP system.
38. SAP NetWeaver Gateway Configuration Guide
(C) SAP AG SAP NetWeaver Gateway 2.0 SPS08 38
Configuring the SAP NetWeaver Gateway Host to
Accept Assertion Tickets from SAP Business Suite
Systems
You must configure your SAP NetWeaver Gateway host to accept SAP assertion tickets from
the SAP Business Suite (backend) system for message-based Web service communication.
Proceed as follows:
1. In your SAP NetWeaver Gateway system make sure that the profile parameters are
set as outlined in Profile Parameters [Page 10].
2. In your SAP NetWeaver Gateway system go to transaction SSO2 to run the SSO2
administration wizard.
Note
If transaction SSO2 does not work, use STRUSTSSO2 to import the certificates
from the SAP NetWeaver Gateway server; you must import them manually.
For further information, see Using Transaction STRUSTSSO2 in SAP System
>= 4.6C [External].
3. Enter the Type 3 RFC destination created above (from your backend system) or the
Host Name and Instance Number for the backend system in the appropriate fields.
4. Choose Execute.
Note
You may be asked to provide a user name and password.
The SSO administration report for the designated SAP system displays.
5. Choose Activate (Enter Certificate in ACL and, if Necessary, Certificate List) to
configure the SAP NetWeaver Gateway system.
If everything has been configured correctly the traffic lights are green.
39. SAP NetWeaver Gateway Configuration Guide
(C) SAP AG SAP NetWeaver Gateway 2.0 SPS08 39
Creating the SAP System Alias for Applications
You need to specify where the SAP system alias should point to. Depending on the
SAP NetWeaver Gateway content scenario and your system landscape you thus set up the
system alias. The system alias is the result of the routing for an inbound request on SAP
NetWeaver Gateway. It can be a remote or a local system. If that system alias is flagged as a
Local GW instance, it means that the system that is responsible for processing (managing
and storing) the data of an inbound request is the local SAP NetWeaver Gateway instance
itself.
1. In transaction SPRO open the SAP Reference IMG and navigate to: SAP
NetWeaver Gateway OData Channel Configuration Connection Settings SAP
NetWeaver Gateway to SAP System Manage SAP System Aliases and click on the
Activity icon.
2. Choose New Entries.
3. Enter the following details for the SAP system alias:
Field Description
SAP System
Alias
Name of the system alias.
Description Descriptive text for the system alias.
Local GW
The system that is responsible for processing (managing and storing) the data
of an inbound request is the local SAP NetWeaver Gateway instance itself.
This option is typically used for testing scenarios, for example when using the
BOR Generator locally.
If you activate Local GW for a SAP System Alias called LOCAL the RFC
Destination is usually NONE.
For Local
App
The system alias is to be used by BEP. For more information, see the F1 help in
the system and Hub OData Channel with IW_BEP Installation [External].
RFC
Destination
Specify the RFC destination defined for your SAP system.
Software
Version
This setting is specified by the content scenario you are using. Typically it is
DEFAULT.
In the context of Generic Channel development, check the following to
determine the value to set for your GSDOs:
In transaction SPRO open the SAP Reference IMG and navigate to: SAP
NetWeaver Gateway Former Development Former Generic Channel
Development Generic Service Data Object (GSDO) GSDO Types & GSDO
Contexts & GSI Implementations and click on the Activity icon. Select your
GSDO type and choose GSI Implementation.
System ID
Name of the SAP target system.
Note
When specifying SAP system aliases we recommend always to enter the
40. SAP NetWeaver Gateway Configuration Guide
(C) SAP AG SAP NetWeaver Gateway 2.0 SPS08 40
Field Description
system ID. The SAP target system, together with the target client, determines
the system alias for a remote call to a backend system.
Client Target client.
WS Provider
System
Name of the Web service provider business system. Here you only need to
enter a setting if you use content scenarios which are configured via Web
services.
4. Save your settings.
Note
We recommend that you check the system alias configurations using Check SAP
System Aliases [Page 159].
41. SAP NetWeaver Gateway Configuration Guide
(C) SAP AG SAP NetWeaver Gateway 2.0 SPS08 41
Activating SAP NetWeaver Gateway
Before you can use SAP NetWeaver Gateway functionality and theyou have to activate it
globally in your system.
You can activate and deactivate SAP NetWeaver Gateway. When you deactivate it, all
SAP NetWeaver Gateway services stop running, no consumer servers can communicate with
it, and an error message is sent to any system that calls for the services.
When you have completed the installation and post-installation configuration described in the
sections above, you must activate SAP NetWeaver Gateway.
Note
Before activating SAP NetWeaver Gateway, ensure that you have first installed and
configured the consumer server.
Proceed as follows:
1. In transaction SPRO open the SAP Reference IMG and navigate to: SAP
NetWeaver Gateway OData Channel Configuration Activate or Deactivate
SAP NetWeaver Gateway and click on the Activity icon.
A message displays.
2. Choose Activate.
A message displays informing you of the current status.
42. SAP NetWeaver Gateway Configuration Guide
(C) SAP AG SAP NetWeaver Gateway 2.0 SPS08 42
Settings for OData Channel Service Development on Backend
System
OData Channel implementations retrieve the data from an SAP Business Suite (backend)
system. Both application logic and metadata are hosted on the SAP Business Suite system.
After the ABAP development activities, that is developing the runtime service and the model
provider class, the services need to be activated.
For this the following registration process is done on the SAP Business Suite system:
Maintain models
Maintain services
You can maintain these settings in IMG activities in the SAP Business Suite system. In
transaction SPRO open the SAP Reference IMG and navigate to SAP NetWeaver Gateway
Service Enablement Backend OData Channel Service Development for Backend OData
Channel Maintain Models and Maintain Services. For more information see Maintaining
Models and Services [External].
To get an overview of the settings the IMG activity SAP NetWeaver Gateway Service
Enablement Backend OData Channel Service Development for Backend OData Channel
Display Models and Services is provided. Note that this activity is read-only. For more
information see Display Models and Services [Page 44].
After this registration SAP NetWeaver Gateway can expose the corresponding OData
services.
Once a service has been defined in the SAP Business Suite system it can be activated on the
SAP NetWeaver Gateway system. See Maintain Services [External].
Under the IMG path SAP NetWeaver Gateway Service Enablement Backend OData
Channel Service Development for Backend OData Channel an additional activity OData
Channel Generation Tool is provided. For more information, see OData Channel Generation
Tool [External]. In addition, an activity is provided to define parallelization of batch queries.
For more information, see Define Parallelization of Batch Queries [Page 45].
Repository Objects
The registration process of OData Channel models and services is unique: In order to allow
collecting authorizations per data provider class (DPC) a repository object type is available.
This is integrated into transaction SU22. Thus two additional repository object types exist in
SAP NetWeaver Gateway. For more information see Roles in the SAP NetWeaver Gateway
Landscape [External].
These repository objects have the following impact:
Models and services shall only be transported via the transport objects.
The external name of a service is derived from the technical name and cannot be
freely defined to ensure a GTADIR connection to guarantee unique services. You
create service /MYNAMESPACE/MYSERVICE with version 0001 which then results in
http://<host>:<port>/sap/opu/odata/mynamespace/MYSERVICE.
43. SAP NetWeaver Gateway Configuration Guide
(C) SAP AG SAP NetWeaver Gateway 2.0 SPS08 43
Prerequisites
The following entities must exist:
The data provider class for the service
The model provider class for all models
More Information
OData Channel [External]
44. SAP NetWeaver Gateway Configuration Guide
(C) SAP AG SAP NetWeaver Gateway 2.0 SPS08 44
Displaying Models and Services
In the SAP Business Suite backend system you can find this activity in the Implementation
Guide (IMG): In transaction SPRO open the SAP Reference IMG and navigate to SAP
NetWeaver Gateway Service Enablement Backend OData Channel Service Development
for Backend OData Channel Display Models and Services .
In this activity you can display the models and the assignment of models to services. Thus
you get an overview on the existing models and services.
This is a read-only activity which simply provides an overview on existing configuration
settings. The view cluster can still be used to display all registered services and models. The
maintenance activities are done via Maintaining Models and Services [External].
45. SAP NetWeaver Gateway Configuration Guide
(C) SAP AG SAP NetWeaver Gateway 2.0 SPS08 45
Define Parallelization of Batch Queries
The transaction for defining parallelization of batch queries allows you to optimize the
performance of batch request processing. For this an IMG activity is available: In transaction
SPRO open the SAP NetWeaver reference IMG and navigate to Gateway Service
Enablement Backend OData Channel Service Development for Backend OData Channel
Define Parallelization of Batch Queries .
In case of serialization the duration of the consecutive queries is the sum of all query
processing times. Contrary to this, the total duration in parallel mode is just the maximum
duration of these query processing times and a minimal overhead for parallelization.
The following parameters are valid for the current SAP client:
Activate Parallelization for Batch Queries
Mark or unmark this option to enable or disable the parallelization.
Maximum Number of Parallel Queries
Specify the maximum number to limit the amount of parallel processing queries to
save system resources. This number will be ignored if it is greater than the maximum
number of dialog work processes available at parallelization time which is based on
system settings (transaction RZ11, profile parameters rdisp/rfc*) . Zero (0)
means it only depends on current system resources. Default value: 0.
46. SAP NetWeaver Gateway Configuration Guide
(C) SAP AG SAP NetWeaver Gateway 2.0 SPS08 46
Settings for OData Channel Service Development on the Hub
System
After you have made the relevant configuration settings in the SAP Business Suite system in
which component IW_BEP is installed (SAP NetWeaver releases lower than 7.40) or in which
core component SAP_GWFND is installed (SAP NetWeaver 7.40 or higher), you need to make
some additional configuration settings in the SAP NetWeaver Gateway hub system in which
you intend to develop OData services.
Note
If your SAP NetWeaver Gateway hub system is based on an SAP NetWeaver release
lower than 7.40, you will need to install the core component IW_FND in your hub
system. If your SAP NetWeaver Gateway hub system is based on SAP NetWever
7.40 or higher, the core component SAP_GWFND is installed as standard. For more
information, see Deployment Options [External].
Assigning SAP System Alias to OData Service [Page 47]
Activate and Maintain Services [External]
Multiple Origin Composition [Page 48]
Dynamic System Alias Calculation Via /IWFND/ES_MGW_DEST_FINDER [Page 51]
47. SAP NetWeaver Gateway Configuration Guide
(C) SAP AG SAP NetWeaver Gateway 2.0 SPS08 47
Assigning SAP System Alias to OData Service
You can assign SAP system aliases to a service. With this assignment, an OData request
from an SAP NetWeaver Gateway consumer can be routed to the corresponding backend
system. The system can correctly identify the SAP system that is responsible for processing
(managing and storing) the data of an inbound request. Thus, OData Channel based content
which is developed either on the SAP NetWeaver Gateway hub system or on a SAP Business
Suite backend system is based on the service.
The SAP system alias can have a specific role or a specific host name associated to itself, so
that you can specify different roles or host names for the same system alias for a service. If
you leave the User Role or the Host Name field empty, the setting is valid for all roles/host
names. Different backend systems are supported, if you specify corresponding roles/host
names and system aliases. The roles are only for user grouping and do not need to have any
special authorization.
Example
It is possible to separate the development, the quality and the production landscape
via dedicated clients on the SAP NetWeaver Gateway hub system.
The user will be directed as follows if he has not special roles: If there is a system
alias maintained without any role assignment then it is used for all users.
The user will be directed as follows if he has two or several roles relative to different
system aliases: If a user is assigned to more than one system alias the system alias
which is marked as default wins. If more than one system alias is found and either
none of the system aliases or more than one of these aliases are flagged as default
an error is raised.
Ideally you have a system alias without any role assignment for all users without a role
assignment and disjunct roles for the system aliases for all other users to the different
backend systems (development, quality, productive). The system aliases with role assignment
should be marked as default in this case.
For this an IMG activity is available in the SAP NetWeaver Gateway Implementation Guide
(IMG): in transaction SPRO open the SAP Reference IMG and navigate to SAP NetWeaver
Gateway :
For applications based on backend OData Channel system navigate to OData
Channel Administration General Settings Assign SAP System Aliases to OData
Service .
For applications based on OData Channel with IW_BEP on the hub navigate to
OData Channel Development with IW_BEP Registration Assign SAP System
Aliases to OData Service .
Note
In previous support packages OData Channel based content was routed via GSDO
groups which are no longer relevant in SAP NetWeaver Gateway 2.0 SP03.
48. SAP NetWeaver Gateway Configuration Guide
(C) SAP AG SAP NetWeaver Gateway 2.0 SPS08 48
Multiple Origin Composition
Multiple origin composition (MOC) is the ability to collect data from different backend systems,
aggregate them in one single service and updating different backend systems while using the
same user. Thus a service can be made available for several system aliases. For example,
you could have two identical systems, one located in America and one in Europe, and
combine them. MOC is also used for CREATE calls and the metadata. At present, CREATE
calls cannot be done in all configured backend systems, but only in the default system.
Note
This feature is only supported in Standard Mode.
This feature is relevant only for entity sets with an annotation of
addressable=true.
Implementing this feature creates a different version of the service (The
SAP__Origin field is added).
Proceed as follows to use the MOC:
1. Customize your service to support MOC.
1. From the SAP NetWeaver Gateway system, activate the desired service. For
information on how to activate your service, see Register your Service in the
SAP NetWeaver Gateway System [External].
2. Open transaction SPRO and choose SAP Reference IMG.
3. Navigate to SAP NetWeaver Gateway OData Channel Administration
General Settings Activate and Maintain Services to add the system
aliases for the relevant backend systems and define the desired default
system.
1. In the Service Catalog list, select the desired service. The service
appears in the ICF Nodes section on the lower left corner of the
screen.
2. In the ICF Nodes section, select the Standard Mode ICF Node.
3. In the System Aliases section, choose System Alias to add the
system alias.
4. Choose New Entries or select an existing entry and choose Copy.
5. In the Service Doc. Identifier field, enter the ID of the service
document followed by an underscore and the 4–digit version number
(for example, _0001).
6. In the SAP System Alias field, enter the relevant system alias. Only
one system is to be defined as the default.
7. Repeat as necessary to add the desired backend systems.
Note
The default system is used whenever the service is not called as
MOC. If you have defined more than one default system alias, the
first system is used as the default.
49. SAP NetWeaver Gateway Configuration Guide
(C) SAP AG SAP NetWeaver Gateway 2.0 SPS08 49
2. Test the service.
1. On the SAP NetWeaver Gateway system, open the SAP Reference IMG in
transaction SPRO and navigate to SAP NetWeaver Gateway OData
Channel Administration General Settings Activate and Maintain Services
.
2. Search for the desired service with the Filter icon.
3. Select the desired service and choose Call Browser under ICF Nodes.
An example URL for RMTSAMPLEFLIGHT looks as follows:
http://<host name>:<port>/sap/opu/odata/iwfnd/RMTSAMPLEFL
IGHT;mo/
4. Make sure that the SAP__Origin field appears in the service's metadata.
Parallelization of Multiple Origin Composition
When using multiple origin composition you can determine both the minimum number of
backend systems and the maximum number of parallel backend calls. For this a new IMG
activity has been added: On the SAP NetWeaver Gateway system, open the SAP Reference
IMG in transaction SPRO and navigate to SAP NetWeaver Gateway OData Channel
Administration General Settings Define Parallelization for Multiple Origin Composition .
You can use this parallelization of READ_ENTITYSET to several backend systems to achieve
optimized performance. In the In the IMG activity you can set the following configuration
parameters:
Minimum Number of Backend Systems can have following values:
o 0: No parallelization
o n: Parallelization will only be done from n backend systems onwards
The maximum number of parallel backend calls is always based on current resources
of the SAP NetWeaver Gateway hub system. Additionally, you can use parameter
Maximum Number of Parallel Backend Calls to limit the use of current system
resources. The default value zero (0) means it only depends on current system
resources.
Performance Improvement
In case of serialization the duration of a READ_ENTITYSET within a hub system is the sum of
all backend calls. Contrary to this, the duration in parallel mode is just the maximum duration
of all backend calls and means a minimal overhead for parallelization.
Parallelization and Skiptoken
If server paging is realized in any backend data providers, then the OData consumer will only
receive results up to this backend including a skiptoken. The next call with this skiptoken or
any other call with skiptoken will not be parallelized because the result has to be continued by
the backend system which returned this skiptoken before.
50. SAP NetWeaver Gateway Configuration Guide
(C) SAP AG SAP NetWeaver Gateway 2.0 SPS08 50
Changesets
In the context of multiple origin composition, changesets are also supported. All changeset
operations for one backend are collected and sent to this backend via one RFC. You can find
an example in SAP Note 1890049.
More Information
Error Log [External]
51. SAP NetWeaver Gateway Configuration Guide
(C) SAP AG SAP NetWeaver Gateway 2.0 SPS08 51
Dynamic System Alias Calculation Via
/IWFND/ES_MGW_DEST_FINDER
Enhancement spot /IWFND/ES_MGW_DEST_FINDER is provided to help you in dynamically
calculating which system alias should be used. You can therefore use this enhancement spot
to overwrite or enhance the standard routing for a service. Alternatively, you can use this
enhancement spot to control the traffic from the SAP NetWeaver Gateway system to a
backend system, so as to limit the load on that backend system.
The enhancement spot needs the following input:
OData service ID
User ID
Result of the standard routing in the form of a list of system aliases
List of HTTP request parameters which is only provided for data requests and not for
metadata requests.
The enhancement sport returns a list of system aliases with the following fields:
system_alias of TYPE /iwfnd/defi_system_alias.
This has to be defined with the standard implementation guide activity for system
aliases.
user_role of TYPE /iwfnd/defi_role_name.
This field is filled according to the standard routing in the implementation guide which
has the role as an optional “filer”. Note that this field can be empty.
is_default of TYPE /iwfnd/mgw_inma_default_alias.
If the table contains only one entry this can be empty. If the table contains more than
one entry exactly one entry must be flagged as default.
o That system alias is used for all normal (non multi destination composition)
requests.
o That system alias is used for multi destination composition requests in case
of CREATE, metadata or function imports of multiplicity 1.
Example
The service created in the backend system is as follows:
Technical Service Name: /IWBEP/TEA_TEST_APPLICATION
External Service Name: TEA_TEST_APPLICATION
Version: 0001
52. SAP NetWeaver Gateway Configuration Guide
(C) SAP AG SAP NetWeaver Gateway 2.0 SPS08 52
The service registered on the SAP NetWeaver Gateway system is as follows:
Namespace: /IWBEP/
External Service Name: TEA_TEST_APPLICATION
Version: 0001
Technical Service Name:
ZTEA_TEST_APPLICATION (provided during
registration)
Service Document Identifier:
ZTEA_TEST_APPLICATION_0001 (technical service
name plus version)
The URI would be as follows: URI =
/sap/opu/odata/iwbep/TEA_TEST_APPLICATION/TeamCollection
The BAdI input would be as follows:
IV_USER =MRMEYER
IV_SERVICE_ID = ZTEA_TEST_APPLICATION_0001
Table of system aliases containing the result of the standard routing
The BAdI output would then be a table of system aliases which were changed by the BADI (or
not changed) as a result of the standard routing.
Syntax
Sample coding throwing an exception in case of too much load on the backend system:
1. …
2. RAISE EXCEPTION TYPE /iwfnd/cx_mgw_dest_finder
3. EXPORTING
4. textid =
/iwfnd/cx_mgw_dest_finder=>backend_load_too_high
5. http_status_code =
/iwfnd/cx_mgw_dest_finder=>gc_status_service_unavailable
6. system_alias = lv_system_alias.
53. SAP NetWeaver Gateway Configuration Guide
(C) SAP AG SAP NetWeaver Gateway 2.0 SPS08 53
Connection Settings on the Backend System
The following activities can be used by OData Channel to set up the connection settings to
SAP NetWeaver Gateway.
Settings for Idempotent Services [Page 54]
Defining a Remote Function Call to SAP NetWeaver Gateway [Page 56]
Connection Settings to SAP NetWeaver Gateway [Page 57]
Configure the bgRFC Supervisor Destination [Page 58]
Monitoring bgRFC Queues [Page 60]
54. SAP NetWeaver Gateway Configuration Guide
(C) SAP AG SAP NetWeaver Gateway 2.0 SPS08 54
Settings for Idempotent Services
HTTP is an inherently unreliable protocol. If connection or other issues prevent the client from
receiving a response the client is left in doubt if the request was processed by the server.
Idempotency guarantees delivery of synchronous messages exactly once. For idempotent
requests (for example GET) the client can simply re-try the request. But for operations that
change the server state (for example, creating a new item or invoking a side-effecting service
operation such as “Reject Workflow”) re-issuing the request may result in an undesired state,
as for example two items instead of one item are created.
Two optional request header attributes and one response header attribute facilitate the ability
to retry requests without incurring unintended side-effects:
Request Headers
o RequestID
A 32 character GUID string representing a client-generated, globally unique
for all time, identifier for the request.
o RepeatabilityCreation
The date and time at which the request was first created. If specified, the
client directs that the request must be repeatable. The client can make the
request multiple times with the same RequestID and
RepeatabilityCreation header values and get back an appropriate
response without the server executing the request multiple times.
Response Header: RepeatabilityResult
A string describing how the server has handled the requested repeatability. The
following values are possible.
o accepted
The request was accepted and the server guarantees that the server state
reflects a single execution of the operation. The response returns the
success or failure state of the operation as first executed by the server, and
reflects either the current state of the system or the state as it existed when
the request was first received.
o unsupported
The request was rejected because the server does not support repeatable
execution of the request. The server returns 412 (Precondition Failed)
without attempting to execute the request. The server state is the same as if
the request had never been received.
o rejected
The request was rejected because the combination of
RepeatabilityCreation and RequestID was invalid or because the
RepeatabilityCreation time was outside the range of values held by the
server. The server returns 412 (Precondition Failed) without attempting
to execute the request. The server state is the same as if the request had
never been received.
55. SAP NetWeaver Gateway Configuration Guide
(C) SAP AG SAP NetWeaver Gateway 2.0 SPS08 55
The request header attributes are passed on to the SAP Business Suite backend system. In
the backend system the idempotent utility (provided by the underlying SAP NetWeaver)
handles the idempotent support generically. When the backend system receives a request it
delegates the handling of the RepeatabilityCreation header to the idempotent utility
class.
Defining Settings for Idempotent Services
You configure idempotent services by scheduling a background job that ensures that request
messages in SAP NetWeaver Gateway only occur once.
For this the SAP NetWeaver Gateway Implementation Guide (MG) has been enhanced. In
transaction SPRO open the SAP Reference IMG and navigate to SAP NetWeaver Gateway
Service Enablement Backend OData Channel Connection Settings to SAP NetWeaver
Gateway Define Settings for Idempotent Services .
To define settings for idempotent services, proceed as follows:
1. Click on the Activity icon of the above mentioned IMG activity.
2. Enter the following default values:
o For Period Hours in Document the typical value is 6.
o For Period Hours in Document ID the typical value is 12.
3. Choose Schedule.
A message displays confirming that the job has been scheduled.
4. Choose Continue.
56. SAP NetWeaver Gateway Configuration Guide
(C) SAP AG SAP NetWeaver Gateway 2.0 SPS08 56
Defining a Remote Function Call to SAP NetWeaver
Gateway
You create or define a background remote function call (bgRFC) destination, which is used for
communications in an outbound queue, and an inbound queue among SAP systems. This is
an activity that is done in the SAP Business Suite backend system, that is, the system where
software component IW_BEP is installed.
If you are using push from an SAP Business Suite backend system to an SAP NetWeaver
Gateway hub system, it is important not to have a trusted RFC connection. This is because
the WF-BATCH user which is the current user in the case of Workflow is not a dialog user and
therefore cannot be used for RFC. Instead a dedicated technical user like ALEREMOTE has to
be maintained in the RFC destination in the backend system.
Note
You can also use an existing bgRFC destination in your SAP system to the host of
SAP NetWeaver Gateway.
You can define this remote function call by using the implementation guide (IMG). In
transaction SPRO open the SAP Reference IMG and navigate to SAP NetWeaver Gateway
Service Enablement Backend OData Channel Connection Settings to SAP NetWeaver
Gateway Create RFC Destination for Outbound Queues .
Proceed as follows to create the bgRFC destination:
1. Click on the Activity icon.
2. Choose Create. The RFC Destination Window displays.
3. In RFC Destination specify a name for the RFC destination to be created. For
example, BEP_BGRFC_DEST.
4. In Connection Type enter 3, for ABAP connections.
5. In Description 1, enter an explanatory text.
6. Choose Enter, and select tab Technical Settings.
7. Enter the SAP NetWeaver Gateway host name in Target Host, and enter its
corresponding system number.
8. On tab Logon & Security enter the technical user and make sure that Current User is
not selected.
9. Choose Enter and select the Special Options tab.
10. Depending on the SAP NetWeaver version, do the following:
o For SAP NetWeaver 7.02, go to section Select Transfer Protocol and select 1
Classic with bgRFC from the list.
o For SAP NetWeaver 7.0, go to section Select qRFC Version and select
bgRFC from the list in qRFC Version.
11. Choose Save and Yes to close the warning message that displays.
12. Choose Remote Connection to test the connection. Information about the connection
type displays.
57. SAP NetWeaver Gateway Configuration Guide
(C) SAP AG SAP NetWeaver Gateway 2.0 SPS08 57
Connection Settings to SAP NetWeaver Gateway
The Business Enablement Provisioning (BEP) functionality can publish events to one or more
hosts running SAP NetWeaver Gateway. However, you must first identify the SAP NetWeaver
Gateway landscape to use with it. For OData Channel you also specify the SAP NetWeaver
Gateway landscape.
Prerequisites
Make sure that you have:
Defined an RFC destination to SAP NetWeaver Gateway to broadcast the events.
The system name, client ID, and a system alias of the host of the SAP NetWeaver
Gateway landscape to which you want to connect.
Specifying Connection Settings
You can specify settings for connecting to a SAP NetWeaver Gateway landscape by using
the implementation guide (IMG). In transaction SPRO open the SAP Reference IMG and
navigate to SAP NetWeaver Gateway Service Enablement Backend OData Channel
Connection Settings to SAP NetWeaver Gateway SAP NetWeaver Gateway Settings .
1. Click on the Activity icon.
2. Choose New Entries and enter the following:
o Destination System
Specify the system name of the host of SAP NetWeaver Gateway.
o Client
Specify the system client ID of the host of SAP NetWeaver Gateway. The
client ID you specify should be in the specified system.
o System Alias
Enter a unique name for the host of SAP NetWeaver Gateway.
o RFC Destination
Specify the name of the RFC destination to the host of SAP NetWeaver
Gateway. For example BEP_BRFC_DEST.
3. Save your settings.
58. SAP NetWeaver Gateway Configuration Guide
(C) SAP AG SAP NetWeaver Gateway 2.0 SPS08 58
Configure the bgRFC Supervisor Destination
You configure a supervisor destination for the bgRFC to receive the configuration settings for
the bgRFC scheduler. In addition, the supervisor starts or stops the schedulers as required.
Prerequisites
You have created a system user of type B called BGRFCSUPER. Use transaction SU01
to create the system user. This user is used for the bgRFC communication using the
destination you will create. For example, BGRFC_SUPERVISOR.
You have assigned role SAP_BC_BGRFC_SUPERVISOR to user BGRFCSUPER. Use
transaction SU01 to assign role to the user BGRFCSUPER.
For SAP NetWeaver 7.0, you have created a bgRFC destination as an ABAP
connection, using the RFC destination name BGRFC_SUPERVISOR, without load
balancing, target host, SAP NetWeaver Gateway host and service.
Specify the user, language and password. This ensures that the scheduler is
activated on the same application server as the specified user.
Later, you configure the supervisor destination for the bgRFC to receive the
configuration settings for the bgRFC scheduler.
Note
The bgRFC supervisor user you specify must have authorizations from authorization
object S_RFC. These are defined in role SAP_BC_BGRFC_SUPERVISOR. The
procedure you employ depends on the version of SAP NetWeaver in your system.
Configuring the bgRFC Supervisor Destination
You can configure this bgRFC supervisor destination by using the implementation guide
(IMG). In transaction SPRO open the SAP Reference IMG and navigate to SAP NetWeaver
Gateway Service Enablement Backend OData Channel Connection Settings to SAP
NetWeaver Gateway Create bgRFC Supervisor Destination .
Proceed as follows:
1. Click on the Activity icon.
2. Select tab Define Supervisor Dest.
3. Depending on the version of SAP NetWeaver, do the following:
o For SAP NetWeaver 7.02, choose Create. The Create bgRFC Destination for
Supervisor window is displayed.
1. Choose Create User. For example, BGRFCSUPER.
2. Save your settings.
o For SAP NetWeaver 7.0, make sure you have already created a separate
bgRFC destination for the supervisor using the name BGRFC_SUPERVISOR.
1. Enter the bgRFC supervisor destination name BGRFC_SUPERVISOR,
in Destination under New Supervisor Destination.
59. SAP NetWeaver Gateway Configuration Guide
(C) SAP AG SAP NetWeaver Gateway 2.0 SPS08 59
2. Choose Enter. The supervisor destination and the user details
display.
4. In the bgRFC Configuration window choose Save.
More Information
bgRFC (Background Remote Function Call) [External]
60. SAP NetWeaver Gateway Configuration Guide
(C) SAP AG SAP NetWeaver Gateway 2.0 SPS08 60
Monitoring bgRFC Queues
You can monitor and display items in the Background Remote Function Call (bgRFC) queue
to check for messages which the system failed to send.
All the messages are written in unit queues, which consist of function modules to be
processed as an indivisible unit. Find all the messages that failed to be transported from the
host of the Backend Event Publisher (BEP) or OData Channel to the consumer environment,
because of system fault exceptions.
System faults are all standard REST errors, for example: communication error, or other errors
that occurred during the activation and operations of Web services.
Note
Application fault exceptions are displayed in the application itself.
Prerequisites
Make sure that you have the authorization object S_BGRFC for monitoring or customizing
activities assigned to your user role.
Analyzing the Results of the Monitor
You analyze each error message and decide how best to correct the error.
If the error can be fixed, make the necessary corrections and then send it to the unit again,
otherwise delete the unit.
You can manually restart the unit even if the retry limit has been exceeded. You can go into
the code to debug the unit (this requires the appropriate authorization role), or delete all the
units inside the inbound destination.
You can monitor the bgRFC queues by using the implementation guide (IMG). In transaction
SPRO open the SAP Reference IMG and navigate to SAP NetWeaver Gateway Service
Enablement Backend OData Channel Connection Settings to SAP NetWeaver Gateway
Monitor bgRFC Queues .
Proceed as follows to monitor bgRFC queues:
1. Click on the Activity icon to open the bgRFC monitor.
Alternatively you can use transaction SBGRFCMON.
2. Select the option for the Outbound scenario and the Queued unit type. Select other
parameters of the monitor as required.
3. Choose Execute to run the monitor. The status of the queues is displayed.
4. Monitor the Queue with the Event ID and instance number for the messages which
were not sent.