AD404 - Extend your Social Business by integrating SAP Solutions

AD404 - Extend your Social
Business by integrating SAP
Solutions

Christian Holsing

© 2012 IBM Corporation

IBM’s statements regarding its plans, directions, and intent are subject to change or withdrawal
without notice at IBM’s sole discretion.

Information regarding potential future products is intended to outline our general product direction
and it should not be relied on in making a purchasing decision.

The information mentioned regarding potential future products is not a commitment, promise, or
legal obligation to deliver any material, code or functionality. Information about potential future
products may not be incorporated into any contract. The development, release, and timing of any
future features or functionality described for our products remains at our sole discretion.

2 | © 2012 IBM Corporation

SAP Integration is in focus for Lotus since years
■ Overview of current offerings to integrate SAP® Business Suite with
IBM Collaboration Solutions offerings

IBM® Lotus Domino® IBM® WebSphere Portal® IBM® Connections®
Family
●Lotus® Connector for SAP ●IBM® Portlet Factory® ●JCo based integration
Solutions® based integration
●Alloy by IBM and SAPTM ● via JCo

(EOL announced in Oct ● via Webservices

2011 )
●WebService based ●UX based integration

integration
●JavaTM based integration

(via SAP® JCo®)

| © 2012 IBM Corporation

IBM and SAP joined forces to provide deeper
integration on UI Level for Portal
■ IBM is not only a SAP partner, IBM is also one of the largest SAP
customer.
■ IBM is currently running a huge SAP consolidation project where
specific requirements are addressed on interoperability
■ Out of this project a Integration asset for WebSphere Portal was
developed (available on the Catalogue) that provides integration on UX
level, incl embedded navigation
• New! - WebSphere Portal integration with SAP® NetWeaver Portal®
Services
– iView and Page: Supported through Portal Administration Tools
– Navigation: integration of role base SAP navigation into WebSphere Portal
– Session Management – navigate away and come back to where you left off
– Single Sign On (SAML 2.0, Basic Authentication)
– Corporate Branding – ability to align WebSphere Portal and SAP


Portal Landscape Interoperability and Openness -
Example

Blue Har mony
Key Capabilities
 Support of JSR 168/ 286,
WSRP 1.0
 Support of SAML 1.0 and 2.0
 JavaTM EE 5 and JavaTM SE 6
support
 Integration of SAP® Business
Objects® reports via the Portal
Integration Kit
 Exposing the portal navigation
structure via a dedicated Web
Service
 Advanced capabilities for
consuming SAP application
into 3rd party portals

(lab preview)


Typical requirements for Collaboration / Social
integration with ERP Systems (some IBM Examples)
■ Creating an RFP
─ Interim set of documents, people, notes, used to craft the RFP are not stored inside the ERP
system. However, the expertise location, rapid collaboration, etc could help reduce the response
time dramatically.

■ Stuck on assigning the proper account codes to a sales opportunity
─ Internal IBM example – a new hire in a growth market is struggling (real time) in completing a
task properly – the collaboration environment could be aware of others who are working on
similar activities, and make those people known (via ST, etc) to the struggling individual. Think
of the websites that notice lack of forward progress, and prompt the user with an offer of a live
chat to solve the problem. With so many people coming into IBM (50% of IBMers are < 5 years
with the company, and hypergrowth countries, expect even less so...) this could be a way to help
create community of people helping people globally...

■ Getting to the right pricer team for solution questions
─ Expertise location scenario – a bid team may need to quickly turn around the pricing on a
solution, and for corporations that don't have an IBM-style “deal hub” solution, using the
collaboration software to rapidly bring together the right knowledge for a spot/short question


SAP Data Interfaces / and how to address them from
Lotus Solutions
SAP Business Suite
ERP / CRM / SRM / PLM / HCM / ...

RFC / BAPI® WebServices

NetWeaver Java Soap
librfc
SDK Connector Toolkits

■ SAP Systems classically rely on the RFC / BAPI interfaces
■ Since the NetWeaver based system, external tools can also integrate to
SAP via WebServices
■ Lotus embraces both option throughout the stack
■ RFC / BAPI via JCo and Lotus Connector for SAP
■ Webservices via toolkits (e.g. Axis) or built in capabilities (IBM® Domino
Designer®)


SAP NetWeaver Gateway – a new opportunity for
integration with SAP Solutions
■ SAP® NetWeaver Gateway® is a
new integration layer on the SAP
stack intended to simplify access
to SAP data
■ Provides SAP Data as restful
services
─ Based on OData protocol
─ Focused on lightweight consumers
─ Foundation for mobility (Sybase®,
Apple® XCode Generators®, RIM
BlackBerry® Toolkit, Duet
Enterprise®)
■ Introduces new licensing model

■ In general availability (GA) since
Q3/2011


Why is NetWeaver Gateway significant for Lotus
Customer?
SAP NetWeaver Gateway offers a set of benefits for the joint Lotus SAP Customer
base above the former APIs (which continue to exist)

■ Technical Aspects
─ Simplified API
– easier to consume than other Interface layers before. Literally no need to understand SAP
deeply
─ Openness
– Open Standard based layer, no need for specific SAP toolkits or APIs, broadly applicable
beyond SAP
─ In line w/ ICS Strategy
– Both companies look at simpler to use Rest-based APIs
■ Fiscal aspects
─ More appealing licensing
– NetWeaver Gateway introduces a new licensing model for access from 3rd party tools that
removes the need to license the full SAP CAL that corresponds to the Integration purpose
Example: Alloy Workflow approval did require a limited Professional SAP CAL


SAP NetWeaver Gateway licensing example
■ NetWeaver Gateway introduces a new licensing consists of 2 components:
─ CAL
─ Transaction based Fee (per 75000 calls)
■ SAP has various levels of CAL's available, Gateway introduces a new backend
CAL for access only through Gateway, excluding SAP UI's
─ Removes commercial boundary IBM saw w/ Alloy and Portal Deals where a limited professional
User was needed for Workflow approvals
─ Gartner Report on indirect Access Fee
■ Sample calculation (Workflow approvals) for 1,000 user and 10,000 workflows
per year
─ Regular usage
16 call / day * 200 days * 1000 User = 3,200,000
– 2500€ per User x 1000 User = 2,500,000 € 10000 Approvals x 5 calls = 50,000
─ Gateway access
Overall 3,250,000 Cals => 44 packages
– 500€ per User x 1000 User = 500,000 €
– 500€ per GW package x 44 = 22,000 €
522,000 €
Note:
Prices are assumptions only, real license fee are subject to SAP's commercial offers

SAP is embracing OData as the Protocol for
NetWeaver Gateway <atom:entry>
<atom:content type="application/xml">
<m:properties>
<d:value>000000899757</d:value>
■ OData is a protocol extending <d:scheme_id>IWF_USER_DECISION_TASK_GW</d:scheme_id>
<d:scheme_agency_id>ECC6</d:scheme_agency_id>
AtomPub Standard <d:status_txt>Ready</d:status_txt>
<d:type>W</d:type>
■ Literally data is made available <d:note_count m:Type="Edm.Int16">0</d:note_count>
<d:created_at m:Type="Edm.DateTime">2011-09-15T00:00:00</d:created_at>
as a feed <d:gui_link/>
<d:priority>5</d:priority>
<d:start_dl m:Type="Edm.DateTime">0000-00-00T00:00:00</d:start_dl>
■ Every base service has a <d:act_dec/>
<d:reassign_by/>
metadata object (/$metadata) <d:actual_owner/>
<d:reassign_to/>
<d:language>E</d:language>
■ Base URL points to additional <d:subject>Please approve/reject Purchase Order 4500017247</d:subject>
data feeds (nested feeds) <d:task_name>WS99900236_0000000004</d:task_name>
<d:act_dec_agent/>
<d:created_by>SUPER</d:created_by>
<d:status>READY</d:status>
<d:end_dl m:Type="Edm.DateTime">0000-00-00T00:00:00</d:end_dl>
<d:reserved_by/>
■ Data is pretty self explaining, </m:properties>
</atom:content>
SAP has added minor <atom:id>http://gateway.isicc.de.ibm.com:8000/sap/opu/sdata/sap/WFDECISIONTASKPROCESS
ING/WorkflowTaskCollection(value='000000899757',scheme_id='IWF_USER_DECISION_TASK_
extensions to OData standard GW',scheme_agency_id='ECC6')</atom:id>
<atom:link
to reflect specific requirements href="WorkflowTaskCollection(value='000000899757',scheme_id='IWF_USER_DECISION_TASK
_GW',scheme_agency_id='ECC6')" rel="self" type="application/atom+xml;type=entry"/>
■ Common OData toolkits handle <atom:link href="SubscriptionCollection"
rel="http://www.sap.com/Protocols/SAPData/rel#subscribe"/>
SAP extensions without <atom:link href="WorkflowTask_ApplyRelease?
value=000000899757&scheme_id=IWF_USER_DECISION_TASK_GW&scheme_agency_id=EC
problems C6" rel="http://www.sap.com/Protocols/SAPData/rel#action" sap:semantics="action"/>
<atom:link href="WorkflowTask_ApplyReserve?
value=000000899757&scheme_id=IWF_USER_DECISION_TASK_GW&scheme_agency_id=EC
C6" rel="http://www.sap.com/Protocols/SAPData/rel#action" sap:semantics="action">

OData knows currently 2 main toolkits for Java
Development
■ http://www.OData.org is the website that describs the OData standard, provides
link to development libraries and has sample code / test environments
■ For Java Development there are 2 main libraries available:
─ Restlet API ( http://www.restlet.org/ )
Restlet API generates static proxy classes based on the “$metadata” Information to access
OData streams that are included in Java code
─ OData4J ( http://code.google.com/p/odata4j/ )
OData4J is a dynamic toolkit that provides access in a dynamic way, allows query of
specific properties from OData stream directly from source code
■ Initial versions of SAP NetWeaver Gateway had certain issues with the Restlet
API due to some minor version incompatibilities of the OData Stream
─ OData4J has proven to be the easier and more robust solution w/ SAP NetWeaver Gateway
─ OData4J also supports various authentication types towards SAP NetWeaver Gateway which
will be a requirement in Production environments
■ There is also a variety of other Libraries for JavaScriptTM, PHPTM, ....
( http://www.odata.org/developers/odata-sdk )


Integration of Domino with Gateway
■ Domino can leverage Gateway best way through Java Code

■ Integrating XPages w/ NetWeaver Gateway is easy and a great fit

■ XPages Integration consists of 2 main components:
─ JavaBean that handles communication w/ SAP (using e.g. OData4J Toolkit)
─ JavaScript in XPages App to retrieve data

■ Also, OData Access can be used in core Domino Apps or Sidebar components,
as JCo was before
─ Java agents can easily use OData toolkits
─ Example: Sidebar Component from IBM Blue Harmony project that provide SAP Workflow
approvals from IBM® Lotus Notes® Client


Integration of SAP NetWeaver Gateway with Lotus
Domino
■ Domino Apps can integrate via Java
Agents or XPages Apps with
NetWeaver Gateway
■ XPages provide Extension Libraries
since 8.5.2 which allow to integrate
new data sources such as SAP
OData streams
■ Integration via Java Code and
OData4J library is simple and
requires only few lines of code to be
written
■ Simple XPages app can be created in
less than 30 minutes from scratch


Java Code for Integration Bean
package com.ibm.chi;
import org.odata4j.consumer.ODataConsumer;
import org.odata4j.consumer.behaviors.BasicAuthenticationBehavior;
import org.odata4j.core.OEntity;
import java.util.Collection;
import java.util.List;
import java.util.ArrayList;

public class GWWorkflow {
private ArrayList<OEntity> WorkflowSet = null;
public ArrayList<OEntity> getWorkflows() {
ODataConsumer c =
ODataConsumer.create("http://9.153.165.205:8000/sap/opu/sdata/sap/WFDECISIONTASKPRO
CESSING/",new BasicAuthenticationBehavior("super","password"));
this.WorkflowSet = new ArrayList<OEntity>();
for(OEntity workflow : c.getEntities("WorkflowTaskCollection/?$format=xml").execute()){
this.WorkflowSet.add(workflow);
}
return this.WorkflowSet;
}
}


Three simple steps are required to access the
JavaBean in the XPage
■ Java Bean needs to be added to “faces-config.xml” in NSF file

■ On the Xpage a DataTable with following settings is added

■ Which then allows access to the bean with the following JavaScript
Statement


Blue Harmony Workflow integration Project
■ IBM in it's BlueHarmony SAP
consolidation project was one
of the first customers to
leverage SAP NetWeaver
Gateway
■ Simple Notes plugin that
communicates directly with
SAP system
■ SAP NetWeaver Gateway
provides access into SAP
Backend systems
■ Users can review their work
items in Notes, review details
and take their decisions from
within their Notes Client
■ Experience similar to Alloy


Integration of SAP NetWeaver Gateway with
WebSphere Portal
■ IBM® WebExperience Factory® (aka
Portlet Factory) has a REST builder
available today, which can be used
against the SAP NetWeaver Gateway
services

■ Process of creating new portlet is the
same as for BAPIs, just that the initial
builder is the REST Builder

■ Existing Portlets can be migrated to
new NetWeaver Gateway Interfaces
easily


A Central Component of Social Apps is the Activity
Stream – which can contain SAP Events


SAP NetWeaver Gateway is an easy enabler for SAP
Events in the Activity Stream
■ Activity Streams provide a simple
API that can be used for external
systems to create events and
assign them to a user / group
■ The aggregation of the events
happen on the IBM Connections
server
■ Users see the high-level details
of the event, and can drill into the
event through an embedded
experience (OpenSocial Gadget)
─ Gadget can come from various
sources
─ Can be reused e.g. within mail


Technical Integration Options
■ SAP NetWeaver Gateway provides Interfaces for both push and pull
communication
─ Pull: OData Stream
─ Push: Event driven push of OData Element to receiving URL

■ To address the integration between SAP NetWeaver Gateway and the
Connections API, 3 main options are available:
─ Servlet on Connections Server to receive events from Gateway
─ IBM® Cast Iron® to query Gateway / receive push messages
─ Custom Java code to connect both APIs

■ Choice of integration model has influence in license cost for Gateway
─ Push model is cheaper than a pull model
─ Each transaction on Gateway increases the counter


Cast Iron enables easy integration also for other
products in the Lotus Stack
■ Cast Iron is an integration Appliance that allows integration orchestrations based
on assembling connectors and translation components
■ To integrate Gateway with connections, only http connectors are required

Receive http Push event
call from GW Login Login
into C4 API


OpenSocial is the standard for the Embedded
Experience
■ ICS is introducing the concept of embedded experiences using OpenSocial
gadgets in key products
─ Allows direct access to Information within another container such as
– Events in activity stream
– Emails
– Web-based UIs
■ OpenSocial defines a common API for social applications across multiple
websites. With standard JavaScript and HTML, developers can create apps that
access a social network
■ A common API means you have less to learn to build for multiple websites
─ Includes Common API model to access external systems from Gadget
■ OpenSocial is currently being developed by a broad set of members of the web
community
■ The ultimate goal is for any social website to be able to implement the API and
host 3rd party social applications


IBM Collaboration Solutions View on Enterprise / SAP
Integration
■ Social Business can only work and
provide the most benefit if events
from all parts of an enterprise are
aggregated in the activity stream
■ The architecture provides out of the
box the required connectivity to have
3rd party tools publish into the activity
stream – and call back to them
■ There are 2 key aspects why 3rd party
integration in Social Business is
important:
─ Not aggregating all events holistically
leads pretty much to a second activity
stream in the enterprise
─ Having all events in one place allows
aggregation of events into clusters /
analytics to be applied holistically on
problems


Social Business scenarios for Enterprise Integration –
the Vision
■ The idea of an activity stream as the aggregation for enterprise events resonates
very well with customers and partners – it introduces a new interaction model
that is much easier to consume and use than traditional systems like eMail
■ As stated before, it is critical to integrate the key events from all relevant systems
in a company into the activity stream to provide the most value
■ The solution design for SAP integration is totally repeatable for any other system
– in the easiest way through Cast Iron, but both other options are also possible
■ IBM Collaboration Solutions provide the respective and open APIs
─ Intend is to provide sample configurations as whitepaper or through OpenNTF

■ Social Business Toolkit on Lotus Greenhouse will demonstrate more examples
over time
─ Team has e.g. also worked on the integration of Microsoft® Sharepoint® events into the activity
stream


Other Business Systems like BPM Systems can be
integrated into the activity Stream as well
■ Lombardi Screenshot
■ ECM Activities


Mobility aspects around SAP Integration
■ One of the key focus areas for both IBM and SAP is mobility

■ SAP has acquired Sybase and is aggressively pushing that technology into their
customer base

■ IBM is working on a similar system for on-device Apps which is available as
technical preview on Developer works now

■ IBM Collaboration Solution technology also supports mobile devices through a
server based approach – which is very often an alternative to a Sybase based
approach – and much more cost effective

■ New area of opportunity for partner / developer


OpenOffice and SAP
■ IBM is working w/ SAP on a proof of concept to integrate OpenOffice with SAP
NetWeaver Gateway
■ Idea is to provide a direct communication from an OpenOffice document to a
SAP system through the NetWeaver Gateway
─ Initially focus on invoice / quotation documents
─ Direct read / write interaction with SAP system to retrieve details
■ Potential expansion to broader scenarios, such as
─ Service browser
─ BI scenarios
─ Presentations

■ Discussing w/ SAP about potential contribution to OpenOffice Apache project


ICS story for SAP Integration is better than ever before
■ Even if ICS together with SAP decided to End of Life Alloy as a productized
offering, the integration options are better than ever before – and very
competitive to other offerings
■ IBM and SAP are following similar strategies in their portfolio, the fit is better than
ever before
─ SAP is forced to become more open by their customers, changes in the licensing strategy on the
SAP side
─ SAP is starting to embrace Industry standards broader to enable integration to their software
stack
■ ICS addresses a set of key focus areas for clients with the existing solutions
─ Mobile
─ Social Business
■ New business opportunities for partner ecosystem to broaden scope and deliver
new value to clients through IBM technology
─ Provide mobile apps
─ Social Business integrating broad range of applications


Call to Action

■ Get familiar w/ the extensibility / development options that are coming forth

■ Get familiar w/ OpenSocial and the activity stream APIs

■ Understand the Social Business idea and think about how you can deliver social
Apps using your existing knowledge and skill set

■ Understand the mobile aspects of the Lotus portfolio and how to utilize them –
IBM / Lotus has a lot to offer in this area


ICS SAP general Integration Overview


Questions?


Contact

Christian Holsing
IBM Collaboration Solutions – Business and Technical Strategy Team
Product Manager "Alloy by IBM and SAP" and "Lotus Connector for SAP Solutions"

IBM SAP International Competence Center
Altrottstrasse 31
69190 Walldorf
- Germany -

Phone: +49-7034-64-31021 | WalldorfOffice: +49 6227 73 1234 | Mobile: +49 160 96 93 69 01
Email: holsing@de.ibm.com
Tungle: www.tungle.me/cholsing


Legal disclaimer
© IBM Corporation 2012. All Rights Reserved.

The information contained in this publication is provided for informational purposes only. While efforts were made to verify the completeness and accuracy of the information contained in this publication,
it is provided AS IS without warranty of any kind, express or implied. In addition, this information is based on IBM’s current product plans and strategy, which are subject to change by IBM without notice.
IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, this publication or any other materials. Nothing contained in this publication is intended to, nor shall have
the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software.

References in this presentation to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and/or capabilities referenced
in this presentation may change at any time at IBM’s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or feature availability in any
way. Nothing contained in these materials is intended to, nor shall have the effect of, stating or implying that any activities undertaken by you will result in any specific sales, revenue growth or other
results.

All customer examples described are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual environmental costs and performance
characteristics may vary by customer.

IBM, the IBM logo, Lotus, Lotus Notes, Notes, Domino, Quickr, Sametime, WebSphere, UC2, PartnerWorld and Lotusphere are trademarks of International Business Machines Corporation in the United
States, other countries, or both. Unyte is a trademark of WebDialogs, Inc., in the United States, other countries, or both.

Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both.

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

SAP, SAP Business Suite, SAP NetWeaver Portal and SAP NetWeaver Gateway are the trademarks or registered trademarks of SAP AG in Germany and in several other countries.


AD404 - Extend your Social Business by integrating SAP Solutions

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Viewers also liked

Viewers also liked (16)

Similar to AD404 - Extend your Social Business by integrating SAP Solutions

Similar to AD404 - Extend your Social Business by integrating SAP Solutions (20)

Recently uploaded

Recently uploaded (20)

AD404 - Extend your Social Business by integrating SAP Solutions