SAP AG 1

SAP AG 2005

Installation Details

SAP AG 2

SAP AG 2005

Optional:SCM 5.0 Event

Management

SAP SCM 5.0

Database

SAP Event Management

SAP WCL 5.0

Database

JavaSchema

SAP NetWeaver 2004s UsageType AS-Java

RFID-enabled processeswithout backend integration

Core Environment

Database

JavaSchema

ABAPSchema

SAP Net-Weaver2004s

Usage Type AS-ABAP

SAP Net-Weaver2004s

Usage Type AS-Java

Add-On SAP Auto-ID

Infrastructure 4.0

Optional:SAP NetWeaver

Business Intelligence(BI) with BI Content

Add-On 2

Systems withUsage Types

Standalone Engines

LiveCache

Search and Classification

(TREX)

Pre-calculation Server (BI)

AS-Java

EP

BI-Java

AS-ABAP

BI

IGS comprised

Adobe document services

comprised

Clients/Tools

Web Browser SAP GUI

Visual Composer

BI Add-On, Business Explorer

comprised

Technical Infrastructure of SAP AII 4.0 w/o Backend System

SAP AG 3

SAP AG 2005

Technical Infrastructure of SAP AII 4.0 with Backend System

RFID-enabled processeswith backend integration

Core Environment

Database

JavaSchema

ABAPSchema

SAP NetWeaver 2004s ProcessIntegration (PI/XI)

Integration Server

Integration Builder(Integration Directory & Integration Repository)

XI Content AUTOID 4.0

RFID-enabled processes with backend integration -

Backend Environment

Backend options:

SAP R/3 4.6C

SAP R/3 Enterprise 4.7 Extension Set 200

SAP ECC 5.0

SAP ECC 6.0

Database

Optional:SCM 5.0 Event

Management

SAP SCM 5.0

Database

SAP Event Management

SAP WCL 5.0

Database

JavaSchema

SAP NetWeaver 2004s AS-Java

SAP Basis Plug-In for SAP SCM 5.0

(optional)

XI Content for Backend

AUTO-ID Add-On

Database

JavaSchema

ABAPSchema

SAP Net-Weaver2004s AS-ABAP

SAP Net-Weaver2004s AS-Java

Add-On SAP Auto-ID Infrastructure 4.0

SAP Net-Weaver2004s AS-Java

SAP Net-Weaver2004s AS-ABAP

Optional:SAP NetWeaver

Business Intelligence(BI) with BI Content

Add-On 2

Systems withUsage Types

Standalone Engines

LiveCache

Search and Classification

(TREX)

Pre-calculation Server (BI)

AS-Java

EP

BI-Java

AS-ABAP

BI

IGS comprised

Adobe document services

comprised

Clients/Tools

Web Browser SAP GUI

Visual Composer

BI Add-On, Business Explorer

comprised

SAP AG 4

SAP AG 2005

Installation of AII 4.0 Option 1

Following Note 867167 and the additional documentation attached to that note

1. Installation of Database Software if Required2. Installation of SAP NetWeaver 2004s ABAP System3. Apply Patches (Kernel, SPAM, BASIS/ABA, PI_BASIS, BW)4. Installation of AUTO-ID 4.0 Add-On on the ABAP Stack5. Apply Patches for AUTO-ID 4.0 Add-On6. Client Copy from Client 000 to a Productive Client7. Installation of SAP NetWeaver 2004s Java Add-In to the Productive Client8. Apply J2EE Patches9. Register ABAP+Java System in the System Landscape Directory (SLD)10. Installation of SAP AUTO-ID 4.0 UI on the Java Stack11. Apply Patches for AUTO-ID 4.0 UI12. Follow Attachment of Note 867167 for Post-Installation Steps13. Configure the System for RFID-Enabled Slap & Ship Outbound Processing

The following slides provide information of how to install a complete SAP AII 4.0 system for RFID-Enabled Slap & Ship Outbound Processing.

For certain platforms, database software installation is integrated into the SAPinst installation process.

SAP AG 5

SAP AG 2005

Installation of AII 4.0 Option 2

Following Note 867167 and the additional documentation attached to that note

1. Installation of Database Software if Required2. Installation of SAP NetWeaver 2004s ABAP+Java System3. Apply Patches (Kernel, SPAM, BASIS/ABA, PI_BASIS, BW, J2EE)4. Installation of AUTO-ID 4.0 Add-On on the ABAP Stack5. Apply Patches for AUTO-ID 4.0 Add-On6. Client Copy from Client 000 to a Productive Client with User Master from 0017. Post Processing of the Client Copy8. Register ABAP+Java System in the System Landscape Directory (SLD)9. Installation of SAP Auto-ID 4.0 UI on the Java Stack10. Apply Patches for AUTO-ID 4.0 UI11. Follow Attachment of Note 867167 for Post-Installation Steps12. Configure the System for RFID-Enabled Slap & Ship Outbound Processing

The following slides provide information of how to install a complete SAP AII 4.0 system for RFID-Enabled Slap & Ship Outbound Processing.

For certain platforms, database software installation is integrated into the SAPinst installation process.

SAP AG 6

SAP AG 2005

Starting Installation of ABAP + Java System

SAP AG 7

SAP AG 2005

Selecting the Relevant Usage Types

SAP AG 8

SAP AG 2005

Specify SLD Configuration

Since AUTO-ID UI requires the use of SLD, if there is no central SLD available, select option 2: Configure local SLD.

SAP AG 9

SAP AG 2005

Progress of Installation of ABAP + Java System

SAP AG 10

SAP AG 2005

Applying Patches and Installing AUTO-ID 4.0 Add-On

Perform SPAM Update beforehand Apply ABAP Kernel Patches and J2EE Patches as well.

SAP AG 11

SAP AG 2005

Client Copy from Client 000 with User Master from 001

J2EE Add-In by default is connected to Client 001 AUTO-ID 4.0 Add-In brings certain customizing settings into Client 000 (Note 867167).

SAP AG 12

SAP AG 2005

Post Processing After Client Copy J2EE UME Connection Adjustment

Start Visual Administrator and go to the Service Node

Navigate to Services Configuration Adapter Cluster Data Server cfg Services Propertysheet com.sap.security.core.ume.service

Adjust The parameter ume.r3.connection.master.client which determines the client where the j2ee is connected

SAP AG 13

SAP AG 2005

SLD Data Supplier in the ABAP Stack

The installation program might create this for you automatically, but should double check its accuracy.

SAP AG 14

SAP AG 2005

Define SLD Data Supplier from J2EE Engine

The information entered here not only is used for SLD Data Supplier, for Web Dynpro Content Administration, the connection to SLD server is retried from here as well. Otherwise, you will fail to maintain JCo Connections (part of AII 4.0 Java installation), because there is no SLD connection.

SAP AG 15

SAP AG 2005

Setup RFC Destination LCRSAPRFC

Setup LCRSAPRFC_XI in J2EE if not there. For Integrated Scenario, use XIs J2EE instead.

SAP AG 16

SAP AG 2005

Setup RFC Destination SAPSLDAPI

Setup SAPSLDAPI_XI in J2EE if not there. For Integrated Scenario, use XIs J2EE instead.

SAP AG 17

SAP AG 2005

Define SLD Server Destination

SAP AG 18

SAP AG 2005

Define Business System for AII in SLD

For standalone scenario, leave the field (Related Integration Server) empty.

SAP AG 19

SAP AG 2005

Check SLD Configuration (Transaction: SLDCHECK)

SAP AG 20

SAP AG 2005

Install Auto-ID 4.0 UI Using JSPM

JSPM: Java SP Manager in /j2ee/JSPM/go.bat Copy AINUI00_0.SCA into /usr/sap/trans/EPS/in from the directory AINUI on CD51031273

SAP AG 21

SAP AG 2005

Maintaining JCo Connections

This will be done with the Web Dynpro Content Administrator by typing theURL http://:/webdynpro/dispatcher/sap.com/tc~wd~tools/Explorer.Logon with user J2EE_ADMIN.

Attention: Before we can maintain the JCo Connections we have to create a Logon Groupin ABAP part with transaction SMLG and then add this Logon Group in theMessage Server details in SLD !

After calling the Web Dynpro Content Administrator and selecting a connectionyou have to scroll down your screen to give the needed entries !

SAP AG 22

SAP AG 2005

Testing the Web UI

To run the WebDynpro UI launch the following URL in your browser:http://:/webdynpro/dispatcher/sap.com/ain~so~desktop/DesktopApp.You need a user with role SAP_AIN_ADMINISTRATOR.

Attention: Dont forget to apply Java Web Dynpro Support Package (Web UI for AIN400)with the SDM before you call the WebDynpro UI !

The support package level for Web UI has to match with the support package level for AUTO-ID Add-On in the ABAP Stack.

SAP AG 23

SAP AG 2005

Configuration of SAP Auto-ID 4.0

For this please use relevant configuration guides for your scenario.

SAP AG 24

SAP AG 2005

Make Shortcuts on Desktop

Tip: Create shortcuts on your desktop to the most important Java administration tools likeVisual Administrator, SDM, SLD, J2EE Configuration Tool, ...

SAP AG 25

SAP AG 2005

Connecting to Integration Server

SAP AG 26

SAP AG 2005

Activating SICF Services for XI (Especially the Service Engine)

SAP AG 27

SAP AG 2005

Register qRFC Queues

SAP AG 28

SAP AG 2005

Sequence for Implementing R/3 4.6C and EM 4.1

Implementation sequence for Backend Option SAP R/3 4.6C (example)

1. Installation of SAP R/3 4.6C following the corresponding InstGuide SAP R/3 4.6C

2. Apply at least Basis / ABA / APPL Support Package 47

3. Install Add-On AUTOID_INT_200_46C on R/3 server follow note 725064 and apply note 689793

4. Install SAP XI 7.0 SP4

5. Install XI Content AUTOID on XI server

6. Install XI Content AUTOID_INT_200_46C on XI server follow note 705541

7. Install AII 4.0 Connected to XI Server

Optional: Implementation sequence SAP SCM Event Management1. Install SAP R/3 Plug-In 2004.1 on the R/3 backend follow note 704564

2. Install SAP SCM server 4.1 following the corresponding Installation Guide SAP SCM server 4.1

3. Install XI Content for SAP SCM 4.1 on XI server follow note 705541

4. Install SAP SCM WCL 4.1 following the corresponding Installation Guide SAP WCL

XI is Unicode Only.

SAP AG 29

SAP AG 2005

Error Messages Not Reach XI

Symptom: The message is sent from R/3 successfully. we05 shows no error in IDoc generation. But message never arrives at XI.

Diagnose: Check sm58; could be RFC not working, such as wrong password or user is locked.

SAP AG 30

SAP AG 2005

Error AII Throws Exceptions

Symptom: When sending material from R/3 to AII, AII throws exceptions on incoming message.

Diagnose: Value mapping is not maintained in XI.

http://iwdf1222.wdf.sap.corp:8015/sap/xi/docu_apperror?ID=NA&OBJECT=COM_PRODUCT503&LANGUAGE=E&MSGV1=COMM_PR_SHTEXT 503(COM_PRODUCT) + error Data cannot be maintained for set type COMM_PR_GTIN http://iwdf1222.wdf.sap.corp:8015/sap/xi/docu_apperror?ID=NA&OBJECT=COM_PRODUCT503&LANGUAGE=E&MSGV1=COMM_PR_GTIN 503(COM_PRODUCT) - error Internal error in /AIN/DM_PROD_COMMIT

SAP AG 31

SAP AG 2005

Error Web GUI Cannot Logon

Symptom: Cannot logon from Web UI, even there is no problem at ABAP GUI.

Diagnose: Jco Connection.

SAP AG 32

SAP AG 2005

Copyright 2005 SAP AG. All Rights Reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission 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 other software vendors. Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft 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, and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C 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 invented and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos are

trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG.

This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice.

SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.

SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence.

The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.