02 Bimal Mehta SAP

8/13/2019 02 Bimal Mehta SAP

1/33

Bimal MehtaSr. Solutions Manager, SAP

SAP Adaptive Manufacturing Summit

September 27, 2006

SAP xMII 12.0Preview


2/33

SAP AG 2006, xMII Next Generation Sneak Peak. Bimal Mehta / 2

Agenda

RoadmapRoadmapRoadmapRoadmap From CMS to xMII.

Next GenerationNext GenerationNext GenerationNext Generation - Features and Functionality:

Composites / TemplatesComposites / TemplatesComposites / TemplatesComposites / Templates


3/33


Key Customer Questions Answered

How does NW play a role in xMII?

Is the footprint bigger for 12.0 than 11.5?

Can I still install it at the plant site?

What new functions are in 12.0 andhow will this benefit me?

Core

Integration

Intelligence

What about migration?

If I am starting to implement now howdo I plan for the next release?

How is Security handled, is itdifferent?


4/33


Roadmap ..


5/33


Future xMII

Comprehensive ESAIntegration

Publish / Consumeservices into the ESR

Additional composites

Extended manufacturingexecution capabilities

Integration

Expanded support for

industry standards Integration with SAP mid-market solutions

Intelligence

Deep integration withVisual Composer

Unified UI architecture Enhanced performancemanagement framework

SAP xMIIProduct Roadmap Overview and Evolution

2005 2006

SAP xMII 11.5

Lighthammer CMS re-branded as SAP xMII

100% Java technology

Comprehensivelocalization capabilities

Updated connectorframework

Integration

Infrastructure for supportof B2MML and most otherstandards

Intelligence

Analytics andvisualization services fordashboards, decision

support, and plant dataentry applications

SAP xMII 12.0

Leverage Web AScapabilities

Supportability

Unified security

Content Management

Data buffering

Integration

Enhanced JCO capabilitiesfor session support, caching

XI-Integration

Intelligence

Minitab export, linearregression, SPC calculations

Development

Unified DevelopmentWorkbench

Connectors

OPC UA and Event Support

2007 and beyond

SAP xMII 11.5 SR1

JCO Interface

PDF output for reporting

PDF document

generation

Integration

Standards based (S95,OAGIS, etc) integrationtemplates

Visual Composer

connector

Intelligence

mySAP ERP PlantManager DashboardIntegration

NetWeaver Alerts

Enhanced SPC/SQCcapabilities

Q1 2007

Detailed roadmap will bepresented on Thursday

morning by Rick Bullotta


6/33


UME

WEbAS

Clustering

Database Managed Content

XI Action blocks

JRA / JCO integration

DataSource v/s IDBC connection with full functional pooling J2EE pooling

Message Queing 0 incoming IDOC, RFCs, WebService calls

Data Buffering in and out xMII asynchronous call - guaranteed writes to ext systems

Project Management

Workbench Single editor for , drag and drop capabilities

JRE 1.5 support

Full Accessbility No applets on admin sideLanguage support EN, DE, Japanese, Chinese, Spanish, French, Portuguese


7/33


SAP xMII 11.5 SR2

On Service Marketplace Oct 2006.

Functional Enhancements include:

Enhanced JCO Action blocks

Full transaction (commit/rollback) support for JCO interface

Minitab Export

Capability to export SAP xMII Analytics data to Minitab formatted data for

Multivariate Analysis

Linear Regression

Support for JRE 1.5

In addition to JRE 1.4.X

Enhancements to SPC


8/33


And NowAnd NowAnd NowAnd Now. SAP. SAP. SAP. SAP xMIIxMIIxMIIxMII 12.012.012.012.0

NetWeaverization of SAP xMII

Enhanced Integration Functionality

Enhanced Intelligence Functionality

Composites / Templates

Migration Considerations


9/33


NetWeaverization of SAP xMII 12.0

SAP Web Application Server (Web AS) / J2EE Architecture

Scalability

NetWeaver Database backend (incl. Quality Portal)

WebAS Datasources for JDBC connection pools

What this will enable:

Built in cluster support

Better tools for monitoring and administration

managing change history and configuration promotion (~12.5)

Other

Localization English, German, Japanese, Chinese, Spanish, French, Portuguese

Accessibility for Editors


10/33


NW Visual Admin Tool

Web Version Available

Look at several SAP xMII status values

These values can be monitored by

CCMS to generate alert when specificthresholds have been passed.


11/33


NW DataSources

can be used insteadof the IDBCconnections for server

central databaseconnections

provides morecontrol over theconnections

ability to monitor

connections


12/33


User Management in SAP xMII 12.0

Full User Management Engine (UME) integration

LDAP Support

Database Support

Local UME user support

Kerberos Support

SAP Single Sign-On (SSO)


13/33


UME

User management and LDAP configurations are managed through theNetWeaver web administrator

http://help.sap.com/saphelp_nw04/helpdata/en/c2/f4e73ee7442e5ae10000000a114084/content.htm


14/33


UME

http://help.sap.com/saphelp_nw04/helpdata/en/7e/a2d475e5384335a2b1b2d80e1a3a20/frameset.htm


15/33


Supportability

1. Supportability

Central Alert Monitoring System (CCMS) integration

Solution Manager Diagnostics For remote diagnostics/troubleshooting.

Heartbeat Check

The heartbeat will be visualized as a single alert ("traffic light") in the CCMS

System Landscape Directory links

Standard SAP Logging/Tracing

Java Application Response Measurement (JARM) similar to existing trace timer

JMX Monitor System Stats

2. Documentation

Broken down into installation, administration, configuration, etc.


16/33


Supportability

1. Supportability

Central Alert Monitoring System (CCMS) integration

Heartbeat Check

The heartbeat will be visualized as a single alert ("traffic light") in the CCMS

System Landscape Directory links

System Landscape Directory is an SAP NetWeaver component. It is completely implemented with Javatechnology and deployed as a Java component on the SAP Web Application Server. As System LandscapeDirectory is already contained in the installation of every SAP Web Application Server Java 6.40 or higher,no further installation is required you only have to perform the easy and quick configuration to activate it.

Standard SAP Logging/Tracing

Java Application Response Measurement (JARM) similar to existing trace timer

The concept of JARM is based on a request. A request is defined as a set of operations and consists of

components. JARM measures the overall run time (optionally the amount of transferred data and the user) ofa request and its associated JARM-components.

JMX Monitor System Stats

the JMX (Java Management Extensions) is used to manage and monitor all server components (services,interfaces, libraries). The Java Application Monitoring API gives programmers a high-level interface toattach to the central monitoring infrastructure

2. Documentation Broken down into installation, administration, configuration, etc.


17/33


SAP xMII 12New Integration Functionality

Expanded JCO/ JRA and XI capabilities including session support,caching

Local queuing / monitoring services plus CCMS link for centralmonitoring

Comprehensive application queuing and monitoring services of incoming IDOC,RFCs, WebService calls

Data Buffering in and out SAP xMII asynchronous call - guaranteed writesto ext systems

Unified security model including SAP single-sign-on

Core manufacturing services and scenarios

DataSource v/s IDBC connection with full functional pooling J2EEpooling


18/33


SAP ERP 2005

BAPI / RFC / IDoc

Solution Proposal: SAP ERP 2005 & SAP xMII 12.0

SAP xMII 12.0

Enterprise Portal

xMIIiViews

VisualComposer

JCO

Non-SAP Apps (MES, SFC, SFA)

Role-based

dashboards

XI

xMIIJCO

Interface

xMIIXI

Interface

xMIIOLAP

Connector

xMIIKPIs &

Alerts

xMIIVC

Adapter

xMIIVisual

Content

xMIIVisuali-zation

Web

Services

IDOC or RFC Adapter

xMIIWAS

Interface

BW

All described scenarios require at least an SAP ERP 2005 or any other SAP software component that runs on the on 7.00 basis component.

JRA

xMII

JRAInterface


19/33


SAP xMII 12.0New Developer Functionality

Workbench Single editor for transactions, templates, animated objects, reference

documents and user content.

Passwords encrypted (wherever passwords are stored)

drag and drop capabilities

Dreamweaver and FrontPage plugins supported.

Project Management Import and Export of Projects

Transactions, templates, and WebPages into Projects.

Dynamic mapping for xml queries and transforms

e.g. server:\\..\

(allows for portability across machines)

JRE 1.5 support

Full Accessibility No applets on admin / config side


20/33


SAP xMII Publish Assistant

The Frontpage and DreamWeaver plugins have been updated with aPublish Assistant to get and put content into the SAP xMII content

management structure.


21/33


xMII SAP Function Best Practices Templates

xMII SAP Function Best Practice templates:

Pre-configured xMII transactions that execute one or more remote-enabledfunction in R/3 or ECC for a specific business or data scenario.

Content includes xMII intellectual property gained over years of use thatsimplifies or accelerates the use of the function in a customer application.

Content is specifically oriented to using the SAP functions in the shop flooroperations environment.

Access to the best practice processes are immediately web serviceenabled.

Plan:

Create a collection of building block transactions that expose many of thebasic functions through xMII

Create 2nd & 3rd level transactions using the building blocks for more advancedor industry specific processes.

Higher level transactions can then be used as the basis for sophisticatedcomposite applications.

100 templates available by year-end

Templates will be delivered via SAP Developer Network (SDN)


22/33


Template Categories

The current categories for the building block transactions are:

Materials Data

Material Movements

Batches

Production OrdersProcess Orders

Plant Maintenance Notifications

Plant Maintenance Work Orders

Quality

Planned Orders

Repetitive Manufacturing

IDOCs

The collection of xMII transactions will be continuously evolve withall content posted and maintained on SDN.


23/33


Material


24/33


OutputResult


25/33


2nd Level Transaction Production Schedule

Uses Order List & Order Details Building BlocksDebug data capture

Error detection and key data captureSpecialized output document generation

All based on the specific business scenario data

requirements


26/33


Production Schedule 2nd Level Template

SelectTRX

SpecifyMaterial


27/33


Production Schedule 2nd Level Template

SpecifyMaterial


28/33


Migration What to do?


29/33


Migration

From 11.5 to 12.0

Remote Server

doesnt have to be on the same server;

migrate to multiple servers

Content

Data servers, navigation trees, system properties, SVG objects,transactions, templates, webpages - html into new project structures.

XML Users will not be migrated


30/33


Planning for SAP xMII 12.0 DOs and DONTs

DOs: Do Use IRPT, HTML, JSP

Do Use Xacute .NET full compatibility to Java version on upgrade (withexception of MSMQ Action)

Do Use LDAP integration relatively seamless transition

Do Continue to expand your applications all content will be migrated andsupported.

Map your content into projects i.e. create root folder structures for templates, trx,etc.

E.g. Transactions\Demo\; Templates\Demo\.....

Do Continue Applet usage

Do Start a plan to migrate to database or LDAP user management

Get use to using authentication on an individual basis, bypassing authentication will nolonger work

Passing Login Name and Password on URL still works if you need that functionality.

Do Build content using RELATIVE URLs whenever possible to make migrationeasier.

Remember all Lighthammer URLs are changing to SAP xMII and user content willbe accessed relative to that. Most bookmarks will not work!


31/33


Planning for SAP xMII 12.0 DOs and DONTs

DONTs: Dont Use Active Server Pages (ASP) if you want multi-platform

capabilities inherent with Web AS

Dont Create 1000s of local XML users

If you have, we will help you we do expect a programmatic solution (SDNcontent)

If you havent, dont start now

Dont Have Users rely only on bookmarks as navigation tools

Dont Be afraid please ask questions


32/33


Questions

Thank You


33/33


No part of this publication may be reproduced or transmitted in any form or for any purpose without the expresspermission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors.

Microsoft, WINDOWS, NT, EXCEL, Word, PowerPointand SQL Serverare registered trademarks ofMicrosoft Corporation.

IBM

, DB2

, DB2 Universal Database, OS/2

, Parallel Sysplex

, MVS/ESA, AIX

, S/390

, AS/400

, OS/390

,OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informixand InformixDynamic ServerTM are trademarks of IBM Corporation in USA and/or other countries.

ORACLE is a registered trademark of ORACLE Corporation.

UNIX, X/Open, OSF/1, and Motifare registered trademarks of the Open Group.

Citrix, the Citrix logo, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, MultiWinand

other Citrix product names referenced herein are trademarks of Citrix Systems, Inc. HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C, World Wide Web Consortium,

Massachusetts Institute of Technology.

JAVA is a registered trademark of Sun Microsystems, Inc.

JAVASCRIPT is a registered trademark of Sun Microsystems, Inc., used under license for technology inventedand implemented by Netscape.

MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver and other SAP products and services mentionedherein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and inseveral other countries all over the world. All other product and service names mentioned are the trademarks oftheir respective companies.

Copyright 2006 SAP AG. All Rights Reserved

Documents

02 Bimal Mehta SAP