Cisco Application Networking for SAP Design Guide. Table Of Contents. Cisco Application Networking for SAP Design Guide. Introduction. SAP Application Overview. SAP Business Suite. Pre- Net. Weaver—Standalone Middleware Applications. Net. Weaver 2. 00. Integration Platform. Net. Weaver 7. 0 /Net. Weaver 2. 00. 4s—Composition Platform. Net. Weaver 7. 1—Business Process Platform. Summary. SAP Server Technology and Data Flows. SAP Web Application Server. Client- Server Flows. Server- to- Server Flows. SAP Server Scaling. Server Load- Balancing with Cisco ACEData Center Design. SAP Portal Design. Infrastructure Consolidation with Virtualization. Security and Server Load- Balancing Integration.
Segmenting Security and Load Balancing with Roles- Based Access Control. Segmenting Content Owners with Roles- Based Access Control. Virtualization Design Considerations. Cisco ACE Module Implementation and Configuration. Admin Context Setup. Baseline User Context Configuration. Security. Server Farms. Basic Load Balancing. Health Monitoring. Health Monitoring for Web Services. Session Persistence. Source IP Persistence. Cookie Persistence. Dynamic Cookie Learning. Tuning the HTTP Header Parsing. SSL Termination. HTTP Header Rewrite (Cisco ACE 2. HTTP Header Insert. Persistence Rebalance. Redirect Server. Impact of TCP Reuse and SSL Termination on Server CPUBackend Encryption. SSL Reuse (Cisco ACE 2. TCP Reuse. Source NAT for TCP Reuse. Monitoring TCP Reuse. WAN Tuning with Cisco ACEOptimization Summary. Application Security and Monitoring. Application Security with the Cisco ACE XML Gateway. Server Monitoring and Troubleshooting. Cisco NAM Setup—Initial Cisco NAM Configuration. WAN Optimization for SAPSAP Application Performance Analysis. Cisco WAAS Testing with SAPTest 1: Login- Logout. Test 2: Knowledge Management. Test 3: Technical Document Management. Test 4. Customer Fact Sheet. ABAP ADD-ON DEPLOYMENT - TEST REPORT FOR INTERFACE. 1 Data transfer of large volume through synchronous mode (RFC). RFC CallReceive error Function /BODS/RFC. XML Spy is a free tool, at least the trial version. It's possible to use a full version of. WAN Testing Summary. WAAS Configuration Summary. SAP Solution Summary and Conclusions. Cisco Validated Design Cisco Application Networking for SAP Design Guide Cisco Validated Design February 1. Introduction To enable business network transformation, a globally connected real- time business that accelerates business innovation across the borderless enterprise, Cisco, in collaboration with SAP, offers the Cisco Application Networking for SAP solutions. As a foundation for transforming the business, this solution is an enterprise network architecture, that optimizes application availability, performance, and security and lowers application ownership costs. It is organized as follows: . The Cisco ACE software was A1. On the data center side, the change might be a new portal deployment that requires a load- balancer or a security policy requiring Secure Socket Layer (SSL) support. The WAN is also a consideration when applications change. Moving from a SAPGUI interface to a web browser, for example, can increase bandwidth usage ten- fold. To understand the kinds of changes and upgrades taking place with SAP deployments, this section provides an overview of the SAP application suite and how it has evolved over the years. It originated in the 1. R/1, where the R stands for real- time data processing. By the 1. 98. 0s, SAP released its second generation mainframe software R/2 which achieved broad market acceptance for business process automation. Then came the third generation of software, R/3, which provided a client- server approach using a three- tiered architecture of database, application, and user interface. This introduced relational databases, a graphical user interface, and the ability to run on many different platforms. These solutions have been further customized across various industry verticals, such as Education, Finance, Manufacturing, and the like. This was later renamed Process Integration (PI) toward the end of 2. Each of the middleware applications listed above had its own release cycle and interdependencies creating a cost of ownership issue. To improve this SAP took all of the above components (Web. AS, ME, EP, BI, and XI) and integrated them into Net. Weaver 2. 00. 4. This package also introduced new technology including: . This is the first tool for building composites. Note Each of these functions—while integrated into Net. Weaver 2. 00. 4—is still a standalone application. There might be an entire farm of servers just for BI, for example. It includes tools for provisioning web services, either to generate web services within applications or to provide interfaces to older systems that cannot support web services natively. It also includes Enterprise Service Repository (ESR) for storing services and a composition tool so you can take those services and compose applications from them. As such, Net. Weaver 7. Apps, which are SAP composite applications that combine web services and data from multiple systems. SOA by itself could theoretically mean exposing every program as services, but this would be unwieldy and difficult to use. The services must be exposed at the correct level to a business process architect who might not understand the program underneath. Thus Net. Weaver 7. Over the last several years, Net. Weaver has evolved from the integration of middleware applications to an enterprise SOA platform that provides for rapid development of composite applications. These composite applications armed with right- sized enterprise services make it possible to rapidly improve business processes and be more responsive to market demands. The following topics are addressed: . It is the set of programs and tools which interface with the operating system, database, communication protocols and presentation interfaces. This software enables SAP applications to have the same functionality and work the same way no matter what operating system is installed and whatever database is used. The web server is also integrated into the application server so SAP does not rely on other web servers such as IIS or Apache. Web. AS runs on most operating systems such as Windows, Linux, and AIX. It maintains database independence by using Open SQL/SQLJ to interface with various databases such as Microsoft SQL Server, My. SQL, IBM DB2, and Oracle. Also note that each SAP application generally has its own database. For example, a production system landscape composed of SAP ERP, BI, and CRM would consist of three separate databases. ABAP is the original programming language created by SAP and is similar to COBOL. Java was introduced more recently. ABAP tends to be used more on the business applications, like ERP, while Java is typical for middleware components like the SAP Enterprise Portal. ABAP and J2. EE can be installed alone or together as a dual stack. Figure 2 illustrates the components of a dual- stack SAP Web AS and some of the common data flows with typical clients and application servers. The dispatcher then forwards the request to the best available ABAP work process. ABAP- based web requests are first received by the Internet Communication Manager (ICM)—which listens for HTTP on port 8. The ICM then parses the URL to determine if the session should be routed to the ABAP or Java dispatcher. While Java web sessions can also be routed through the ICM, in other cases—particularly in Java only servers like the SAP EP—the web sessions connect directly to the Java Dispatcher, which is listening on 5. XX0. 0 for HTTP and 5. XX0. 1 for SSL. The RFCs enable you to call and execute predefined functions in a remote system, or in the same system. The RFCs manage the communication process, parameter transfer, and error handling. In the J2. EE Engine the RFC functions are implemented by the JCo RFC Provider service, which is used for processing ABAP- to- Java requests. A feature is also provided for receiving calls from the SAP systems. This is done by registering the J2. EE Engine as a RFC destination. This is currently an area of growth for SAP as core processes are exposed as web services and leveraged in new ways with composite applications like the SAP x. Apps family. The CI contains the message and enqueue servers and is responsible for queuing and database locks, while the DIs perform the actual processing of the application. For high availability, it is deployed in active/standby mode using the clustering software of the underlying platform. Processing capacity is increased by adding DIs and this is where load- balancing applies. Figure 4 illustrates the SAP server farm—multiple business and middleware applications, each with their own CI cluster, DI servers and database servers. Each of these are separate entities where various application and security optimizations may apply. The process proceeds as follows: 1. For client- server traffic, the client DNS request resolves to a virtual IP (VIP) address located on the Cisco ACE rather than the real server itself. The Cisco ACE then distributes the load to real servers using a configured server selection method such as weighted round robin. In most cases once a client session is directed to a server, ACE sticks all subsequent requests to that same server, typically using a cookie. Health probes are used to take non- responsive servers out of rotation. For application- to- application web services traffic, the application first generates a request for the web services definition language (WSDL). This request is load balanced to a server, either the real server itself or on a central repository such as SAP's ESR. When the application receives the WSDL, it locates the URL to the service and generates a new request using that URL. This URL resolves to a VIP address on the Cisco ACE which in turn load- balances the request to a real server. Typically this web services request is a single request and therefore persistence is not required. If necessary, persistence can be provisioned in the same way as client- to- server sessions—the HTTP header for web services requests contains the saplb. Instead, it is load- balanced by the message server itself using a redirect approach. A typical process proceeds as follows: 1.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2016
Categories |