First of all, SAP Business One Bundle Certification is not an interface certification Per se, it is a package which will provide a cost effective way for your certification if you have your add-on running on different SAP Business One platforms.

 

As a SAP Business One Partner, if you subscribe to SAP Business One Bundle Certification, you can certify your add on with one or all of below certification flavors :

 

  • SAP Business One Add-on Solution Certification (upon SAP Business One 9.0 for SQL with 32-bit and 64-bit)
  • SAP Business One Add-on Solution Certification for SAP HANA 1.0
  • SAP Business One in Cloud Certification 1.0

 

With SAP Business One Bundle Certification

 

  • Partner can still sign up individual certification program with 3,500 Euros
  • Partner can subscribe Bundle Certification program with 5,000 Euros
  • Partner has 9 months validation period to accomplish all certifications in the bundle.

 

Before we can offer you SAP Business One Bundle Certification, SAP ICC needs to make sure only the add-ons coming from the same product family shall be qualified for this certification. ICC consultant will make an assessment based on the information provided by partners by using the Questionnaire document from our ICC consultant.

 

SAP Business One Bundle Certification program will be amended according to SAP Business One Product release road map.

Workshop.gif

Are you looking to gain an in-depth understanding of the SAP HANA Platform?  Do you plan to build, integrate, and certify an application with SAP HANA?

 

SAP-Partners.gif

The SAP Integration and Certification Center (SAP ICC) will be offering partners and ISVs an SAP HANA Enablement Workshop.  This introductory 4-day workshop will take place on Monday, July 28, 2014 to Thursday, July 31, 2014 at SAP Labs in Palo Alto, California will facilitate a general understanding of SAP HANA.  After each training module, partners and ISVs will reinforce their skills via a series of hands-on exercises to demonstrate their knowledge of the various components for the SAP HANA Platform.  This enablement workshop will outline the underlying knowledge needed to allow for the development, integration, and certification of an application with SAP HANA.

 

By attending this enablement workshop, you'll be able to:

  • Understand the end-to-end native application development for SAP HANA
  • Reinforce knowledge with skill-builder modules via hands-on exercises
  • Understand the certification roadmap and process for application certification
  • Leverage a 30% discount for application certification to enable Go-to-Market
  • Engage with product experts and certification team via Q&A sessions

 

Registrations Fees and Deadlines:

 

Due to the popularity of this enablement workshop, seating will be limited and registration will be on a first-come, first-served basis.  If you would like to make a group booking, please submit separate registrations for each individual of your organization.

 

INDIVIDUAL REGISTRATION
REGISTRATION TYPESDATESFEESREGISTRATION
Early BirdBefore June 27, 2014$2,000.00 USDSign-up here!
RegularBefore July 28, 2014$3,000.00 USDSign-up here!
GROUP REGISTRATION - THIRD OR MORE GET A DISCOUNT
REGISTRATION TYPESDATESFEESREGISTRATION
Early BirdBefore June 27, 2014$1,500.00 USDSign-up here!
RegularBefore July 28, 2014$2,500.00 USDSign-up here!

 

Event Logistics and Agenda:


DATESMonday, July 28, 2014 to Thursday, July 31, 2014
TIME9:00 AM to 5:00 PM (Pacific)
LOCATION

SAP Labs

3410 Hillview Avenue

Palo Alto, CA 94304

Building 2 - Baltic Room

 

The agenda for this enablement workshop will highlight some of the following topics:

  • Introduction to SAP HANA Development Platform
  • SAP HANA Application Development Tools: SAP HANA Studio and Eclipse
  • Introduction to SQL Basics and Debugging
  • Introduction to SAP HANA Native Development
  • Introduction to Data Modeling with SAP HANA
  • Points of Integration with SAP HANA
  • SAP HANA Readiness Assessment
  • How to Certify your Application with SAP HANA
  • Q&A Session: SAP HANA Product Experts
  • Q&A Session: SAP Integration and Certification Center

 

Take advantage of this opportunity to plan, build, and explore the various certification programs for SAP HANA and leverage a 30% discount when submitting an application for certification with the SAP HANA Platform!  For any questions or inquiries relating to this enablement workshop, please contact icc-info@sap.com.

Dear Partners!

 

In order to facilitate seamless integration of third-party software and to ensure a high quality SAP ecosystem for increased customer satisfaction, SAP established an integration certification program back in 1996. The results of the certified integrations have been listed online in the SAP partner information center (PIC) 24/7 for public reference.

 

We now take the online listing to the next level, by joining the certification information with the SAP Application Development Partner Directory. The new tool has a simpler user interface, full-text search and better filtering capabilities. Just select the desired skills and experience areas on the left side of the screen to browse through our partner ecosystem.

 

For you the partner directory offers the opportunity to present your company as well as details of your certifications and solutions. You will learn more in the welcome email that you will receive shortly after the go live of the new version of the directory. Soon you will benefit from the additional traffic of potential customers and partners.

 

The current version of the Application Development Partner Directory is already available on SAP.COM, at the same location PIC is located http://www.sap.com/partners/overview/find.html. The new capabilities will become available next week.

 

This is a great opportunity to check if your certification is still up to date.


Keep your certification current – get it re-certified in time!

 

In case of further questions or comments, please contact us.

 

Sincerely,

SAP Integration and Certification Center (SAP ICC)
Homepage: SAP Integration and Certification Center

As part of the PartnerEdge program for Application Development, SAP is offering the application review in addition to the standard interface certification to help partners qualify their mobile app for listing on the SAP Store and ensure that customers receive high-quality, documented, and tested enterprise-class applications.


Since its release, there have been many questions from partners regarding the application review and its differences with the certification that many are already familiar with. The purpose of this blog is to provide a comparison of these two services so partners can have a better understanding of their options.

 

The comparison has been grouped into the following categories:

  • Integration scenario
  • Scope
  • Benefits


Please note that while both services are offered to partners enlisted in the PartnerEdge program for Application Development, the application review is exclusive to members of that program (contrary to the certification). Third-party vendors can sign up with ICC for the mobile app certification which is available to any ISV even those who are not members of the aforementioned program (more here).

 


Integration Scenario


The main difference between a review and a certification lies in the supported integration scenarios.  This is very important as the first order of business for partners when developing a mobile app on SMP is to decide which type of integration scenario they want to implement.

The diagram below (click to enlarge) provides an overview of the integration scenarios which are supported as part of a review or a certification. Please note that the certification covers a much broader scope and is required when developing custom ABAP code (add-on). If you are connecting SMP with a database, an external third-party system or using SAP delivered APIs such as BAPI or RFC as part of your integration scenario then the review will suffice.

 

integration scenarios 2.png

 

Scope


The certification is definitely a more elaborate, thorough and comprehensive approach when compared to the review. The difference between what is covered in each approach can be summarized in the subsequent table (click to enlarge).

 

table1.png

 

Benefits

 

Although the review can be seen as a lightweight certification, this is not exactly accurate as it does not offer the same benefits, nor level of service.  The table below illustrates this (click to enlarge).

 

table2.png

 

Conclusion

 

As you can see, the review is quite different from the certification and one cannot be easily substituted for the other as they are ultimately complementary offerings.

 

The review provides the simplest way to get partner applications released to the SAP Store while the certification offers a more thorough and comprehensive approach that provides value to the vendor and ensures that customers receive high-quality, documented, and tested enterprise-class applications. Certification comes with numerous benefits including the "SAP Certified" logo and certification documents (more here).


I hope you have found this comparison useful. I invite you to post your comments or questions below.


For questions related to certification or review, please contact us at cc@sap.com. If you have questions about the SAP PartnerEdge program for Application Development, please contact the partner center.

 

Thank you !

 

 

Related links


For more details, please consult the following links:

Business Objects Cluster in  best authentication procedure in XI 3.5

To set up  the BusinessObjects cluster, you install the BI platform servers on two machines and cluster them together. The following topics provide step-by-step instructions for setting up the cluster: Question -1

Any best procedure  for XI 3.5 build , release , deployment  .Regards Asish

Every year, a lot of solutions based on the RFC communication protocol are certified by the SAP Integration and Certification Center (SAP ICC). Companies that have an S-User can download the needed connectors to implement such an RFC integration from SAP Service Marketplace: http://service.sap.com/connectors. The most popular connectors are SAP Java Connector, SAP Connector for Microsoft .NET and SAP NetWeaver RFC Library.

 

Using these connectors, RFC clients can connect with a dedicated SAP Application Server to call BAPIs and RFC modules, or to send an IDOC message. However, if this contacted Application Server is down for some reason, the RFC call would fail, even if several other Application Servers would be up and running.

 

RFC Clients can easily make use of the Load Balancing mechanism of SAP NetWeaver; it’s only a matter of configuration. You just have to fill different connection parameters. Therefore, SAP ICC highly recommends supporting the following two methods to connect an RFC client with an SAP System:

 

  1. Connect to an SAP System through Group Logon via an SAP Message Server:
    This should be the preferred method, if the SAP landscape runs an SAP Message Server. With that, load balancing takes place, and calls are routed automatically to a running Application Server.

    The following RFC connection parameters must be filled: MSHOST, MSSERV, SYSID, GROUP
  2. Connect to an SAP System using a specific Application Server:
    If SAP Message Server is not available, then you have to connect to a specific Application Server.
    The following RFC connection parameters must be filled: ASHOST, SYSNR

 

So please make sure, that your RFC connection configuration screen / dialog supports all the parameters of the 2 connection methods mentioned above. Your customer would then tell you the appropriate connection method and parameters.

More details can be found in the documentation of the respective SAP connector:

 

  • SAP Java Connector:
    Open the included javadoc-documentation of the interface “DestinationDataProvider”.
    Check details of “Load balancing connection to a group of SAP application servers via a message server” and “Direct connection to an SAP application
    server instance”.
    Here, the parameter SYSID is called R3NAME.
  • SAP Connector for Microsoft .NET:
    Open the documentation “NCo_30_ProgrammingGuide.pdf” on page 46.
    Check details of “Group Logon” and “Application Service Logon”.
  • SAP NetWeaver RFC Library:
    Open the documentation “NW_RFC_SDK_Guide.pdf” on page 16 and 20.
    Check details of “SAP System using Load Balancing” and “SAP System using a specific application server”.

If you have any questions or need further assistance, please contact your SAP ICC Integration Consultant at icc@sap.com.

 

B1 OnDemand Certification_032013 - processmapv02.png

The SAP Integration and Certification Center (SAP ICC) will be offering a webinar: Winning in the Five Markets: SAP Integration Certification Opportunities for ISVs and Partners during the month of February 2013.  This informative virtual session will provide a general overview of new certification programs available to partners and ISVs, which align with SAP’s five markets: Applications, Analytics, Mobile, Database & Technology and Cloud.

 

Align and form part of SAP’s strategic growth in these markets, which directly support integration opportunities with SAP Mobile Platform, SAP NetWeaver Gateway, SAP BusinessObjects and other new game-changing initiatives.

 

If you are interested in learning more, please join Alejandro Barajas, Program Recruitment Lead - Americas from SAP ICC by registering for the session below:

 

DateTimeLanguageRegistration
February 1, 20138:00 AM (Pacific)SpanishSAP Partners: Go here.Non-SAP Partners: Go here.

 

If you are ready to certify your solution with SAP ICC, please contact us at icc@sap.com to have an in-depth discussion and scope out your certification project with SAP.  For future certification webinars, please reference the SAP Integration and Certification Webinar Series.

This session will cover an overview of certification options for Mobile applications created by SAP Partners on Sybase Unwired Platform and SAP NetWeaver Gateway. A thorough understanding of the underlying technical framework is required to enable mobile platform adoption, outline the mobile strategy and finally, develop the mobile applications.

 

December 5th APJ : 14:00 PM SGT (11:30 AM IST) Register here; Mark your Calendar

 

Presenter  :-  Vikas Marwaha, SAP Integration and Certification Center (SAP ICC).

000_2319.jpg

 

I look forward for your registration and participation in the sessions.

 

Registration Note
Please be aware that if you are registering from the Service Market Place you must update your profile so that it has your current email address in order to receive the Login mails for this session. You will receive the login mail about 2 days before the session.

Disclaimer: The information presented here may be subject to change. Please contact a SAP ICC representative to discuss about the integration certification.

 

 

partnerguidelogo.png

 

 

Last Update: April 2014

 

Following the launch of the SAP Mobile Apps Partner Center, an increasing number of software vendors are engaging with SAP’s Integration and Certification Center (ICC) to get their mobile apps certified. 

 

The purpose of this blog is to provide some guidelines on how partners can get through this process with ease while avoiding along the way some of the most commonly encountered challenges.  It should serve first and foremost as a complement to the existing set of resources, namely the following SCN pages where you can find information on the certifications related to mobile app development at SAP:

 

 

 

 

Content

__________________________________

 

 

 

 

Who is this for?

 

The information presented here is explicitly catered towards the SAP Partners & ISVs who have signed up for the SAP Mobile Apps Partner Program with the intention of distributing their packaged app on the SAP Store.  I will not discuss about the program itself but you can learn more about this exciting program and register directly on the SAP Mobile Apps Partner Center or contact your SAP Partner manager for more information.


For those who want to benefit from the certification but do not wish to participate in the SAP Mobile Apps Partner Program, you can sign up for certification with SAP ICC directly simply by contacting us on our SMP Mobile App Certification page.


Finally, if you are new and unfamiliar with SAP ICC's services altogether, I invite you to get acquainted with us. More information is available regarding our role and the benefits of certification.

 

 

 

How to start certification?


Certification of your mobile app starts once the certification request that you have submitted on the partner center is processed and assigned to an ICC consultant who will contact you to kick-off the process.

 

In order to ensure a timely start, make sure to submit your certification request as early as possible since the processing of your request is not instantaneous given the volume of partners.
          

The collaborative effort between partners and ICC consultants really begins here.

 

The role of ICC is to certify solutions that integrate with SAP from a business process and a technical point of view by facilitating seamless integration, ensuring quality and promoting tested enterprise-class apps, all of which is well-suited for the SAP Store - a curated environment focused on providing quality content. 


 

 

What are the prerequisites?

 

Before you request the certification of your mobile app, please consider the following prerequisites in order to ensure a swift and smooth process:

  • Agreement has been signed with SAP ICC or the SAP Mobile Apps Partner Center and all appropriate licenses have been provided

  • Your mobile app has been built using the SAP Mobile Platform and comprises at least one of the following component:
  • SMP 2.3 or SUP 2.2 (we do not support any other version for now)
  • SAP NetWeaver Gateway
  • Development and testing of your mobile app has been completed

  • Your mobile app is ready for general release and a set of relevant documentation has been made available (i.e. installation and configuration guide)
  • You have consulted the information on the certification:

    • The scope and requirements are clear

    • The integration scenario that best suits your mobile solution has been identified and the associated certification criteria are clear (more below)

    • The device(s) that you wish to certify your mobile app on is available with the ICC consultant

    • You have set up the system landscape for testing of your mobile solution:

      • Mobile device used for testing is provided by ICC

      • Unwired server is usually provided by the partner

      • SAP system (or 3rd party system) is provided by the partner

    

Custom ABAP development:

  • All custom ABAP development that you have implemented for your mobile solution must be done using a partner-registered development namespace

  • All custom Add-on must be packaged using the Add-on Assembly Kit (AAK). Contact your partner manager or ICC to obtain the AAK tool.

 

 

 

Choosing the right integration certification scenario

 

Certification is a mandatory requirement for listing on the SAP Store for Mobile Apps.

Partners can fulfill this obligation by completing any single one of the following integration certification scenarios offered by SAP ICC that relates to the SAP Mobile Platform:

 

Here is a comparison of these 2 integration scenarios (click to enlarge):

 

2scenarios_fixed.png

 

 

The Integration Certification

 

Once all the prerequisites have been met, contact your designated ICC consultant to initiate certification of your mobile app. When certification is completed, handover will be made to the SAP Mobile Apps Partner Center for listing on the SAP Store.

 

Here is an overview of this process (click to enlarge):

 

certprocess_.png

 

As every mobile app is unique and distinct in itself, the integration testing and validation is also specific to each mobile solution.  Therefore, it is essential to discuss your mobile solution with an ICC consultant as early on as possible to allow the consultant to assess your solution correctly and define an adequate test plan that is specifically catered to your mobile solution, however complex it is. 

 

Here are some aspects of the certification to consider:

  • Appropriate use of standard SAP-endorsed technologies or APIs
  • End-to-end validation of mobile solution from device to backend with a focus on functionality and more importantly, the technical integration.
  • Packaging and deployment of software components included in the mobile solution.

 

Again, please consult the specific integration scenarios listed above to get a full understanding of the certification criteria.

If we consider the certification in abstraction from its specific criteria, this process is relatively straightforward. It is worth highlighting that in most cases, its duration, complexity and success are determined by the partner’s level of readiness. The next section will provide you with an overview on how to achieve this.

 

 

 

Best Practices

 

For a smooth and successful certification, please consider the following guidelines:

  • Make sure you have met all the prerequisites listed above before requesting the certification of your mobile solution.
  • Ensure that your mobile solution is ready as the purpose of the certification is not to conduct unit testing for your solution
  • Allocate the necessary resources to support the certification effort (i.e. fixing issues, configuring systems, setting device/user registration, providing documentation, etc…)
  • Prepare adequately by contacting ICC to discuss about your mobile solution with an integration consultant as earliest as possible. This will ensure that the scope and requirements of the certification are clear. Typically, it is recommended to do so once the agreement has been signed with the SAP Mobile Apps Partner Center but if required, you may contact ICC as early as during the development cycle.
  • Plan accordingly. If you have any time constraints (or deadlines) due to a marketing campaign for example, it is important to communicate this information to the ICC consultant to make sure that the appropriate priority is assigned to your project. Furthermore, there is an important activity that most partners neglect to factor into their schedule:
    • The time is takes to receive the AAK and use it to package the custom add-on (applicable only if there is custom ABAP development in the SAP backend system). Please note that the AAK is not available for download as a software package.
  • As a general rule of thumb, please follow SAP’s programming guidelines and best practices based on your choice of architecture. More specifically, it is important for the partner to understand:
    • Registration of a development namespace
    • Usage of Add-on Assembly Kit for packaging the custom Add-on*

* This resource can be provided by ICC if needed.

 

 

 

Common Mistakes

 

Please avoid the following common missteps which may slow down the certification process quite considerably and yield unnecessary delay and effort:

  • Beginning the certification too early with an unfinished mobile solution.
  • Missing documents. Integration certification is meant for released products not demo apps
  • Testing was not conducted thoroughly on the various devices chosen for certification
  • Not allocating enough resources to support the certification effort
  • Omitting to consider shipping & handling time for the delivery of the AAK tool if you have custom development in the SAP backend (anticipate 1-3 weeks depending on your location). Also, please advise ICC consultant of any change of address.
  • Developing custom ABAP code using the customer namespace or temporary ($tmp) namespace instead of a partner-registered development namespace.
  • Single component was used for packaging several ABAP Add-ons. For every ABAP Add-on, a separate component is required.
  • Lack of appropriate test system for custom Add-on verification. It is recommended to have at least a 2-system landscape approach when developing custom ABAP add-ons: one development system and one consolidation system. More information is provided hereICC may be able to provide a sandbox system for testing & verifying add-on if available.
  • Licenses are provided by the SAP Mobile Apps Partner Center. Please make sure you have appropriate and complete licensing before initiating the certification.

     

 

 

 

SAP Store considerations:

 

Once the certification is completed, you will be all set to publish and sell your mobile solution on the SAP Store. In preparation for this next step, please consider the following requirement from the SAP Store prior to certification:

  • In order to showcase the functionality of your app to potential customers who will download it from the SAP Store, it is a requirement that you provide a demo mode within your app. A demo mode is essentially a way of enabling end-users to explore the functionality of your app without the need of having a backend connection or the complete infrastructure in place (using dummy data if needed).

 

Update: It is no longer a requirement that mobile apps built on Apple’s iOS platform be approved by Apple and made available for download on Apple’s App Store prior to the certification. Although it is recommended to have your iOS app approved by Apple, SAP ICC will conduct the integration certification activity independently from now on.

 

 

 

Feedback

 

The success of our partners is paramount at SAP ICC so I hope that this blog has shed some light on the certification process and given you a clear idea on how to navigate through the process as effortlessly as possible within the context of the SAP Mobile Apps Partner Program.

 

Please provide your comments regarding this blog in the comments below.

 

Thank you !

 

 

The SAP Integration and Certification Center (SAP ICC) will be offering a webinar: Partner and ISV Update: New Certification Programs for Game-Changer Initiatives during the month of October 2012.  This informative virtual session will provide a general overview of new certification programs available to partners and ISVs, which align with SAP’s five markets: Applications, Analytics, Mobile, Database & Technology and Cloud.

 

Align and form part of SAP’s strategic growth in these markets, which directly support integration opportunities with SAP Mobile Platform, SAP NetWeaver Gateway, SAP BusinessObjects and other new game-changing initiatives.

 

If you are interested in learning more, please join Alejandro Barajas, Program Recruitment Lead - Americas from SAP ICC in one of the following webinar sessions:

 

DateTimeLanguageRegistration
October 2, 20128:00 AM (Pacific)EnglishSAP Partners: Go here.Non-SAP Partners: Go here.
October 3, 20128:00 AM (Pacific)SpanishSAP Partners: Go here.Non-SAP Partners: Go here.
October 9, 201210:00 AM (Pacific)PortugueseSAP Partners: Go here.Non-SAP Partners: Go here.

 

If you are ready to certify your solution with SAP ICC, please contact us at icc@sap.com to have an in-depth discussion and scope out your certification project with SAP.  For future certification webinars, please reference the SAP Integration and Certification Webinar Series.

The SAP Integration and Certification Center (SAP ICC) would like to inform partners and ISVs that the classic RFC library librfc32(.dll) will no longer be supported after March 31, 2016 and should immediately start to transition to the new SAP NetWeaver RFC Library now.  SAP Integration Certification for solutions integrating via the old RFC library will no longer be possible starting April 2013 and onwards because certifications are valid for 3 years.

 

In order to help, SAP ICC has provided the following frequently asked questions (FAQ) by partners and ISVs to help during this transition:

  • What SAP note provides further details?
    • SAP note: 1025361 - Support and Availability of the SAP NetWeaver RFC Library.
    • SAP note: 1005832 - Overview of RFC Libraries and SDK.
  • What SAP product releases are these related to?
    SAP no longer supports the classic RFC SDK or the classic RFC library after the maintenance end of SAP Release 7.10 (March 31, 2016).  This end of maintenance also applies to SAP Releases 7.11 and 7.20.
  • Why am I informed that early?
    SAP Integration Certifications are valid for 3 years, i.e. the last certification of solutions with the classic RFC library (librfc32) can be done in March 2013 in order not to exceed the maintenance date of the classic RFC library until March 31, 2016.  After that date, we cannot accept solutions using librfc32, since the validity date of the certification would exceed the support for librfc32.
  • What alternative tools am I supposed to use instead?
    SAP ICC recommends the use of more recent tools – such as the SAP NetWeaver RFC Library, SAP Java Connector, SAP Connector for Microsoft .NET.  For more details, please visit: http://service.sap.com/connectors.
  • How can I get the new SAP NetWeaver RFC Library?
    It can be downloaded from SAP Service Marketplace, please visit: http://service.sap.com/connectors.
  • Can I simply compile my program with the new SAP NetWeaver RFC Library?
    No, this is not possible, since the new lib has a new API.  You have to rewrite your interface program and use the new functions.  The new lib is very easy to use, and supports Unicode and non-Unicode.
  • Do programs built with the new SAP NetWeaver RFC Lib run with older versions of SAP solutions?
    Yes, the new lib supports all SAP NetWeaver and R/3 systems, back to 4.0.
  • What are the limitations of the new SAP NetWeaver RFC Lib?
    It does not support communication between two external systems.  For example, it is no longer possible to connect an external program with SAP Process Integration (PI) by using the PI RFC Adapter.

 

If you have any questions or need further assistance, please contact your SAP ICC Integration Consultant at icc@sap.com.

If we want to better understand the Industry focused solutions but if miss or avoid to understand the latest innovations with HANA, we will definitely not have the total picture of SAP's vision for innovative integrated architecture and our next steps.

HANA is not just the database/platform/applience/in-memory fast reporting tool, but it is the Integrated Innovator for leading our Industries to the next step in their future growth and development while reducing the cost and broadening the designing opportunities. 

Allowing the creative architecture to start its course, we will see that from multi-tier architecture we are now transitioning to the capable control of integrated single-tier oriented architecture with fully orchestrated industry focused or line of business focused process execution.

Designing HANA, Cloud, and Mobility uniquely on a single integrated platform, based on industry models and for their lines of business, would allow our customers to use their existing and updated Business Suite as part of the composite SOA and real-time data integration will finally deliver that ultimate customer's dream.

By using such modalities where HANA leads the Industry's focus and its change, we can now achieve our orchestrated delivery by re-using components or building On Demand or By Design next to our already RDS based offerings for those business that are just starting to grow.

Our methodology focus will harmonize the same-like elements and re-use the common repeatable business practices, yet it will expand the broader view of its governance and directive for future development based on HANA's models tailored to each industr's generic LOB functionality to be developed.

Architecture scenarios will include but not be limited to our current HANA offerings as the future customer needs will further dictate our innovative focus and requirements.  However, HANA will bridge any existing gaps between existing ERP and BI / BOBJ development and therefore lead each industry towards its ultimate innovation.  No any other product on the market had done so with such huge impact over the entire enterprise framework, architecture applications, and latest services on the market.

Let's recognize this lead and embrace the opportunities.

Thank you.

Alexandra Weber

Senior SAP IBC Delivery Consultant

Certified Business Process Expert and Integration Techno-Functional Architect since 1994

The SAP Integration and Certification Center (SAP ICC) will be offering two webinars: Mobile App Certification for Sybase Unwired Platform and SAP NetWeaver Gateway Certification during the month of February 2012.  Each webinar will provide a general high-level overview of the respective solution, the requirements for certification, along with benefits and associated cost.

If you are interested in learning more, please find additional information on each respective certification webinar: 

 

  • Webinar: SAP NetWeaver Gateway Certification
  • Date: February 22, 2012
  • Time: 8:00 AM – 8:30 AM (PST)
  • Language: English
  • Description: During this virtual session, you will learn about the certification for SAP NetWeaver Gateway.  In its current version: 2.0, a development framework offers connectivity to SAP applications using any programming language or model by leveraging REST services and OData/ATOM protocols.  The integration happens on two levels: providing Gateway content, and consuming this Gateway content. Certification is offered for end-to-end scenarios covering both content and consumption, or may focus on consumption or content only.
  • Registration:
    • SAP Partners can register here.
    • Non-SAP Partners can register here

 

  • Webinar: Sybase Unwired Platform – Mobile App Certification
  • Date: February 29, 2012
  • Time: 8:00 AM – 8:30 AM (PST)
  • Language: English
  • Description: During this virtual session, you will learn about Mobile App Certification for Sybase Unwired Platform (SUP).  In its current versions: 2.0 & 2.1, it ensures customers obtain robust and tested enterprise-class applications.  Certified, pre-packaged and downloadable mobile apps deployed on mobile devices and SUP server can qualify for listing on SAP Store, along with testing for SAP back-end connectivity, if applicable. 
  • Registration:
    • SAP Partners can register here.
    • Non-SAP Partners can register here.

 

If you are ready to certify your solution with SAP ICC, please contact us at icc@sap.com to have an in-depth discussion and scope out your certification project with SAP.  For future certification webinars, please reference the SAP Integration and Certification Webinar Series.

Disclaimer: Views expressed here are strictly personal and present only one approach for mobile app development using Sybase Unwired Platform (SUP)  and SAP NetWeaver Gateway (GW). Please consult with the SAP Integration and Certification Center (ICC) to learn more about other available integration scenarios.

Picture1.png

This blog describes the integration scenario when developing mobile apps using GW 2.0 and SUP 2.1.

Sybase Unwired Platform is at the heart of SAP’s mobile strategy. It has seen tremendous growth and just recently, the company announced an impressive milestone as it hit the €500M mark in mobile pipeline with more than 350 new customers and 17.5 million total seats in 2011.

With the recent release of SUP 2.1, SAP and Sybase are promoting seamless integration and closer alignment of their technology stacks with the introduction of SAP NetWeaver Gateway integration. This new architecture of combining SUP and GW promises not only to ease but accelerate the development cycle of mobile apps and facilitate integration to the SAP back-end by exposing processes as easily consumable OData services. For mobile app developers who have experienced first-hand the challenges of interfacing with SAP back-end processes, this comes as a welcomed addition to an already impressive platform.

With such promises and encouraging claims, many are eager to jump onboard and be part of the burgeoning ecosystem which by SAP’s estimate, should contribute upwards of 80% to future SAP-related mobile app development.  As often the case with anything new, there’s some confusion on this new approach and many are wondering how it works and more precisely what this architecture translates to in terms of development effort when compared to the current main approach for integrating backend SAP processes with Mobile Business Objects (MBOs).  Certainly, there’s a lot of information on the respective websites of SUP and Gateway yet there is little information generally available on the integration of these two components (at the time of writing in January 2012).  This state of affairs combined with the launch of the Mobile App Certification for partners and ISVs by ICC has compelled me to shed some light on this new approach and share my experience.

In this blog, I will introduce mobile app development using SUP 2.1 and Gateway 2.0* by providing an overview of this architecture and more importantly, how to enable the integration between these two components.

*restricted to online native apps only, hybrid apps will not be discussed here.

 

THE BASICS

First, let’s start with the basics. Prior knowledge of mobile app development using SUP is clearly indispensable in understanding the topics discussed here and how this new approach differs from current standards.  Before I proceed, I invite you to review some basic concepts of mobile app development with SUP (including MBO) and SAP NetWeaver Gateway (including OData) if you are not familiar with them. Here are a few links to help you get started on the right track.

If you’re new to developing on SUP altogether, there is a nice starter page on SDN compiled by Stan Stadelman, Product Manager for SUP:

To that, I would add the following compilation of resources:

 

In a nutshell, SUP is an integrated platform that enables mobile devices to access back-end enterprise data. Prior to version 2.1 of SUP, the primary development approach for creating native mobile apps with SUP to connect to SAP systems was through MBOs. MBOs encapsulate back-end business logic which is made accessible on mobile devices. When integrating to an SAP back-end, MBOs are usually derived from a BAPI (via WS or JCO). Consequently, the integration scenario that I present here will be compared to what I refer to as the “MBO approach” since it’s the most common one and it provides a good point of reference.  As for SAP NetWeaver Gateway, it is essentially a component that exposes SAP Business Suite processes as OData services (OData & Generic channels will not be discussed here). This is perhaps an oversimplified summary so please take a look at the resources mentioned above for more information.

 

UNDERSTANDING THE NEW ARCHITECTURE

Let’s now discuss this new architecture in comparison to the previous model of MBOs and highlight some key differences. First off, when developing a mobile app using SUP you have the choice to adopt (or not) SAP NetWeaver Gateway, in case this was not clear. MBOs have always been at the core of SUP and they still have their merits. They remain an interesting option, even a better choice for some scenarios.  With SUP 2.1, SAP is proposing a complementary approach to ease the development effort but furthermore, SUP and GW tackles the challenges posed by a specific class of application defined as “online apps” (as opposed to offline apps). This approach is specific to this class of application (in this release anyhow).

“Online apps” are defined as lightweight apps with rather simple business use cases or processes that are almost always connected and store little or no data on the device. Technically speaking, this category of applications usually relies on synchronous messaging based on the request-response pattern. If your application fits this model than the general consensus is to use SUP in conjunction with SAP NetWeaver Gateway as a scalable and viable mobile strategy. If you want to know more about which mobile architecture to use, take a look at this blog from Sybase.

The SUP and Gateway integration is enabled by the Online Data Proxy.  The primary focus of this blog is highlighted in blue.

 

image

 

BENEFITS

Surprising claims aside, the integration of SAP NetWeaver Gateway does provide some very interesting benefits. First of all, it should be stated that the vast majority of mobile development projects at SAP rest on Gateway. The slew of SAP-delivered mobile apps out there (or upcoming) is based on this architecture so there is most certainly merits to this manner. Simply, I would say that the best reason for adopting this approach is OData and how it can easily allow information from SAP systems to be easily consumed on a variety of devices. This protocol is extremely appealing as it is based on open standards, it’s easy to consume  and simple to use (think in terms of http). Since OData is meant for all types of clients (not specifically mobile apps), nothing prevents your gateway services to be reused and consumed by a variety of other devices or applications if engineered properly.

Another good reason to favor this approach is the fact that all the data modeling is encapsulated at one level, the backend (contrary to the MBO approach where business logic also resides on the middleware). Needless to say, if your company is already a SAP Services Partner then you are better off investing in the in-house ABAP skills and perform all the programming in the back-end vs. having to program custom Java code (such is the case with SUP’s result set filters).

Finally, one common issue that developers encounter most when modeling MBOs to interface with the SAP back-end is that MBOs are generated based on existing BAPIs and this can pose quite a challenge. The inherent problem with this method is that existing BAPIs are not necessarily best suited for the purpose at hand as they have been designed for desktop-grade applications with different requirements in mind (think heavy and complex processes). This makes the modeling task far more complex than the trivial exercise it is supposed to be.  Indeed, in this particular case the modeling task is neither straightforward nor confined to using the MBO generation tool.  Linking MBOs and mapping attributes is now a tricky exercise.  And so more often than not, developers decide to implement custom ABAP code to meet the specific needs of their mobile application. I think this is one of the most compelling reasons for adopting GW. If there is a clear requirement to develop your own BAPI then it’s easy to see why it makes a lot of sense to implement them in the back-end within the context of Gateway services and benefit from reusability, extensibility and scalability.

Now that you understand the benefits of using SUP and GW, let’s take a look at how to enable the integration between both.

 

HOW TO GET SAP NETWEAVER GATEWAY

A complete pre-packaged SAP NetWeaver Gateway Trial version is available in the Downloads section of SDN (note that Linux or Windows Server 2008 is required). Or, you can proceed with the easy route and opt for the SAP NetWeaver Gateway Demo system. This is more than enough if your goal is to understand the basics.

 

HOW TO GET SYBASE UNWIRED PLATFORM 2.1

At the time of writing, a trial version of SUP 2.1 is only offered to Sybase partners or customers.  SAP partners should consult the SAP Service Marketplace or their partner manager.

The first thing you will notice if you are familiar with SUP 2.0 is that the software installation package for SUP 2.1 has been split into two 2 distinct components: SUP Platform Runtime and Mobile SDK. This is a good thing since it is purposely addressing the needs of deployment vs. development. You will need to install both packages.

 

INSTALLING THE SOFTWARE

The focus of this blog is really about the technical aspects of the integration scenario. Personally, I did not encounter any major issues by following the installation guides and so I will not cover the installation process. There’s already some good sources of information on this topic, check them out:

-          SAP Developer Network: Installing Gateway

-          Sybase Online Documentation: Installing SUP 2.1

 

DEVELOPMENT FLOW

A typical development flow can be initiated using a top-down or bottom-up approach (in the same way as MBO design). This is still true when developing online apps using GW and SUP. Actually, the development flow does not differ much from the standard way but you have to keep in mind that all the modeling and adaptation tasks that were required for SUP have now been moved to GW.  Essentially, you will develop your client code, expose Gateway services and configure your SUP server to allow your device to consume OData services. Since, we do not have any MBOs with this approach, there’s no modeling, mapping of attributes or generation of device-specific client code to interface with the MBOs.

 

image

 

EXPOSING ODATA SERVICES

SAP NetWeaver Gateway is an OData provider meaning it exposes existing SAP Business Suite processes as OData services.  Simply put, it takes RFC data from SAP back-end and “adapts” it into OData. For developers familiar with MBOs, this implies that your business logic will reside solely on the back-end and not on the SUP server. For the purpose of this blog and to showcase an end-to-end scenario, I invite you to use the SAP NetWeaver Gateway demo system.  Most development projects will probably require creating your own Gateway services and in this case, the how-to guides on SDN cover a wide range of possibilities on how this can be achieved.

 

DEVELOPING THE CLIENT APPLICATION

On the client side, you must develop your client code using the OData SDK in order to enable your mobile device to consume OData services (OData SDK is shipped with SUP 2.1). The OData SDK currently supports iOS, Android and Blackberry platforms. The installation steps are described on the Sybase documentation websitehttp://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc01708.0210/doc/html/title.html (see the OData SDK Developer Guide).

It is also worth noting that as of SUP 2.1, the OData SDK only supports native mobile application development. This is certainly a deal breaker if you are building apps using the mobile workflow package (hybrid apps running on the hybrid web container).

 

CONFIGURING SUP

Once OData services are exposed and provide access to back-end SAP processes, the remaining step is to enable the client application to access them by configuring SUP via the Sybase Control Center (SCC). When used in conjunction with Gateway, the SUP server is no longer a container for business logic but acts as a dispatcher of requests from mobile devices located outside the corporate firewall to Gateway and provides more infrastructure-centric functionalities, such as user handling, security and so forth. To give you a clear idea of how this is done, here is a step-by-step guide:

Open SCC (https://localhost:8283/scc/)

Sybase Control Center Welcome Page:

image

Select Applications à Select Application Connections tab à Press button Register…

Applications Connections:

image

Fill in information specific to your app to register a new application connection (*pre-requisite: your application has already been created/defined in the “Applications” tab of SCC)

New Application Connection Registration:

image

Select the newly created item and press button Properties à Select Proxy à Enter value for field “Application endpoint” to direct to your OData service (for GW demo system, simply fill in the URL of the sample consumption model here).

Application Connection Properties:

image

Click OK and we are done configuring the connection to the Gateway OData provider in SCC.

 

As you can see, once the client code has been implemented using the OData SDK and the OData service has been made available from Gateway, integrating GW and SUP is simply configuration work.  This is quite different from the MBO approach as there’s little development effort required on SUP.  With this approach, there’s essentially no more business logic residing on this component (tasks such as managing devices/users and security remain).    

 

CONCLUSION

With the release of SUP 2.1, SAP is offering a compelling integration scenario to easily access complex SAP processes and help mobilize the workforce. Developing mobile solutions using SAP NetWeaver Gateway and SUP offers many benefits such as the ability to leverage existing ABAP skills and confine the complexity of business logic in the back-end layer.  More importantly, the main advantage of this approach and key differentiator is the ability to expose information using the OData protocol.

A few years ago, SAP established a bold strategic goal of reaching a billion people by 2015 and this release is a step in that direction. It provides scalability in distributing critical business information stored in SAP systems across multiple devices and platforms.  Furthermore, the recent launch of the SAP Store for Mobile Apps illustrates the ambitions of the company in promoting a rich and vibrant ecosystem for enterprise mobile apps. And ICC is certainly aligned with this effort as it rolls out the Mobile App certification for partners and ISVs.

The New Year is off to a great start and should be a thrilling one for mobile app developers as news of new developer resources have already been announced.  Decidedly, it’s a great time to build enterprise mobile apps. Get started now by getting in touch with ICC and learn how simple it is to get your mobile app certified and on the SAP Store!

 

NEXT STEPS

Allow me to reiterate that the approach discussed here is only one of many integration scenarios available to partners and ISVs. If you are interested in learning more about the Mobile App certification, please contact SAP ICC at icc@sap.com to discuss your interest more in-depth.

Actions

Filter Blog

By author: By date:
By tag: