Prime Systems OS Mobile integration through SAP NetWeaver Gateway
with Prime Systems [COIL São Paulo, June 2012]
Prime Systems has engaged with COIL to leverage the use of SAP NetWeaver Gateway and create a standard interface from their middleware product “OS Mobile” to SAP ECC. Prime Systems has created a plugin in their middleware product to consume OData services exposed via SAP NetWeaver Gateway.
Among the benefits recognized by Prime Systems are an acceleration in project implementations, performance improvement on integrations, cost reduction due to standardization, and online access to ECC data.
You can visit Prime Systems web site to learn more about the project (Portuguese only).
SAP NetWeaver Gateway Adoption for SAP Design Partners Council, SAP mentors, and strategic partners
with multiple partners [COIL Palo Alto, February 2012]
SAP NetWeaver Gateway offers a new approach for connecting to SAP applications via REST services and OData/ATOM protocols. With this project, COIL enabled the NetWeaver Gateway product team to reach out to our key partners and customers, and the feedback collected from the following groups has influenced multiple early releases of the product.
- Design Partner Council. Participating members of the council, including Capgemini, CompriseIT, IBM Enterprise Business Solutions, Software AG (IDS Scheer Consulting), and itelligence AG, were offered hands-on access to a comprehensive Gateway landscape at COIL to evaluate the product from both technical and business critical aspects. Contributions from the council have helped shape the product and its business model, and continue to influence future releases of SAP NetWeaver Gateway.
- SAP Mentors. These are the top community influencers of the SAP Ecosystem. Most of the mentors work for our customers or partners, and are domain experts of an SAP product or service. The mentors were offered access to early releases of the Gateway product at COIL from mid-2011 to first quarter of 2012 to get their hands dirty. Many of their feedbacks helped shape the product.
Teradata and SAP integration - integration, benchmark testing, and solution validation
In continuation of the 2009 project Teradata and SAP Integration - development landscape setup and hosting (see below), COIL and Teradata continued the overarching multiple-year project in 2010 to integrate SAP NetWeaver Business Warehouse with Teradata's database. Both teams of managers, engineers, and architects reached the next by successfully completing the second phase of the project - supporting the development, benchmark testing, and solution validation of the joint solution.
Interoperability of the IBM WebSphere Message Broker and SAP Process Integration
In larger enterprises, system landscapes comprise quite commonly SOA products from different vendors, in particular different service registries and Enterprise Service Buses (ESBs). When developing business scenarios that run across the entire enterprise, it is essential that the different registries and ESBs interoperate seamlessly.
Repository and Services Registry.
HP and SAP publish SPECjEnterprise2010 Benchmark of SAP NetWeaver CE on HP hardware
In 2009 COIL was asked by the NetWeaver development unit whether we could help to engage with a partner, with whom they could collaborate on the
SPECjEnterprise2010 benchmark. COIL initiated discussions locally with one of our sponsoring members, Hewlett-Packard. We were directly involved in the
Shortly thereafter, the HP experts and NetWeaver development jointly worked on the public benchmark from SPEC. The numbers were released in January by HP on http://www.spec.org/jEnterprise2010/results/jEnterprise2010.html, showing a world-record, single-node performance result on the SPECjEnterprise2010® benchmark.
ABAP Compiler Infrastructure Beta Program
Currently it is not straight forward to apply external code analysis tools to the ABAP programming language. With the new kernel version, ABAP sources can be represented as syntax trees, which can be accessed from external tools. One example of code analysis is the detection of dead code.
Teradata and SAP Integration - development landscape setup and hosting
In April 2009, Teradata and SAP announced an expanded, global strategic partnership. Among many other collaborations the two companies
agreed to define and facilitate engineering collaboration to enable SAP NetWeaver BW to run on the Teradata database. SAP Co-Innovation Lab in Palo
Alto, California was chosen as the place where Teradata and SAP engineers would architect and test the applications and database integration.
COIL. We successfully completed the first phase of this multiple phase project by the end of August 2009. With the completion of the first phase, COIL has
brought a comprehensive SAP and Teradata landscape up and running, including Teradata database, SAP Business Warehouse, and application servers for development and testing. The engineers are now at full speed in developing and testing the integration.
with Progress Actional [COIL Palo Alto, July 2009]
Progress Actional and SAP Co-innovation Lab have released a joint whitepaper on SOA Management and Business Transaction Assurance with combined solutions from both companies.
In addition to the SOA management capabilities provided by SAP Solution Manager and SAP NetWeaver Administrator, SAP works closely with industry-leading SOA management vendors to offer integrated management solutions that can effectively secure, manage, and monitor web services found in today's
heterogeneous enterprise environments. This paper offers a summary of the integrated SOA management and business transaction assurance solution developed and validated in the SAP Co-Innovation Lab by SAP and Progress Actional. You are welcome to check out the paper from SDN.
Application Class Loading on SAP NetWeaver
This project investigated the technical class loading of NetWeaver CE. The resulting best practices have been shared with the entire SDN community through a dedicated whitepaper. It discusses the basic concepts of the Application Class Loading on SAP NetWeaver Application Server - Java in the following often abbreviated as SAP NetWeaver Java Engine. It also exemplary describes how to run Hibernate using to so-called Heavy Resources of the Java Engine. This example will work with an arbitrary version of Hibernate and any version of the SAP NetWeaver Java Engine compliant with Java EE 5 and introducing the Heavy Resources, i.e. SAP NetWeaver Composition Environment 7.1 and above. This example is not Hibernate specific - the same pattern will work for any arbitrary Java static library set. The article is titled "Application Class Loading on SAP NetWeaver Explained - Running Hibernate Using the So-Called Heavy Resources".
Dealing with Heterogeneous SOA Landscapes
Developing enterprise applications following the service-oriented architecture (SOA) paradigm is not only popular, but almost common these days. Most sophisticated and complex enterprise application will leverage services that are either developed by customers, systems integrators or provided by multiple software and applications vendors. In larger companies with multiple lines of business or in case of mergers or acquisitions the resulting SOA system landscapes typically comprise multiple Enterprise Service Buses (ESB), service registries and repositories that need to interact with each other. With best-of-breed and multi-vendor strategies applied to the landscape the community members face a new set of integration challenges.
With their initiative on heterogeneous SOA landscapes the COIL Walldorf team addressed this set of challenges and provided practical hands-on guides in cooperation with partners. Further information can be found in Peter Kulka's blog on "How to deal with heterogeneous eSOA Landscapes", the project landscape setup, as well as in the published articles:
- Setting up a SOA landscape: Setting up a SAP SOA landscape using SAP NetWeaver Composition Environment 7.1, SAP NetWeaver Process Integration 7.1 integrating a 3rd party Enter Service Bus (ESB), in this particular case the IBM WebSphere ESB v6.1 and OpenSSL.
- How to set up an interoperable scenario with SAP NetWeaver Services Registry and HP SOA Governance Systinet Registry Foundation: This document is the outcome of SAP and HP combined working efforts supported by a reference setup between HP and SAP hosted in SAP Co-Innovation Lab. It describes an interoperable scenario between SAP NetWeaver Services Registry and the Hewlett Packard SOA Registry Foundation
- HP SOA Systinet Plug-In for SAP NetWeaver Developer Studio: The purpose of this document is to describe the installation and the basic operation of the HP BTO SOA Systinet Plug-In, which allows for connecting SAP NetWeaver Developer Studio to the HP BTO SOA Systinet Registry. Based on this integration a developer in an organization that uses both SAP NetWeaver and HP Systinet in their SOA environment can work with both products from SAP NetWeaver Developer Studio without having to switch tools.
Evaluating the Capabilities of Ruby for Enterprise Service Consumption
According to the service component architecture (SCA) specification, components may be implemented in Java, BPEL, C++ and PHP. Besides these implementation languages widely accepted in industry and open communities, there are additional dynamic programming languages such as Perl, Python, Ruby, and Groovy that are gaining more and more popularity in the developer community.
The COIL Walldorf team initiated a project on investigating the capabilities of Ruby. This resulted in two practical tutorials see below) as well as in the bachelor thesis of Tobias Braner on "Extending a Service Component Architecture with a Ruby plug-in". Code and documentation were handed over to SAP NetWeaver development for further research & development.