SAP_PI_KUT_03MessageConfiguration.ppt

1、,SAP PI Message Configuration,2014/12/16,课程目标,参加完该课程后，参与者需要掌握以下内容： 可以创建ID对象 理解消息转发规则 理解外围系统连接协议,目录,Two Main Phases on PI Implementation Integration Directory Overview and Concepts Configuration Scenarios Collaboration Profiles Routing Rules Collaboration Agreements Demo: Integration Builder The Step

2、s for Message Configuration Scenario R2D: Step by Step Scenario D2R: Step by Step Q & A,Two main phases: design time and configuration time,Message Definition and Mapping,Message Routing,目录,Two Main Phases on PI Implementation Integration Directory Overview and Concepts Configuration Scenarios Colla

3、boration Profiles Routing Rules Collaboration Agreements Demo: Integration Builder The Steps for Message Configuration Scenario R2D: Step by Step Scenario D2R: Step by Step Q & A,Overview,Integration Director用于将ESR设计阶段中创建的对象进行配置连接，从而完成整个集成场景。 在ID中进行配置的前置条件是相关内部系统已经在SLD中创建，场景/接口会使用到的设计阶段的对象已经在ESR中创建完

4、成。 Process Integration Scenarios在ESR中创建，在ID中配置，在IS（Integration Server）中执行。 ID在最开始时不包含任何内容，用户需要根据在SLD中配置的内容进行相关的内容的添加。同样，部分内容也可以由ESR添加进来。如，ESR中创建的Process Module等。 基于J2EE 的Adapter可以在ID中进行集中配置。 Advanced Adapter Engine （AAE）不使用Integration Engine进行消息处理。从而可以保证一个相对较高的性能表现。然而使用AAE也是受限的，例如，仅有部分Adapter支持AAE。,

5、Integration Directory: Overview,Integration Directory Adapt integration content to specific configuration Delivered empty, without predefined content all content is customer-specific Integration content derived from Enterprise Services Repository Open for Customer to add collaboration knowledge rele

6、vant to non-SAP components Home for centralized adapter configuration Data provider for IS runtime,Integration Builder,Integration Directory,Business Processes,Routing Rules,Business Scenarios,Receiver Determination Rules,Interface Determination Rules(including Mapping Assignment),Configuration Edit

7、ors,Configuration Wizards,Collaboration Profiles,Parties , Services & Channels,Collaboration Agreements,Sender & Receiver Agreements,Task Areas At Configuration Time,Collaboration Profile Objects,Logical Routing Objects,Collaboration Agreement Objects,目录,Two Main Phases on PI Implementation Integrat

8、ion Directory Overview and Concepts Configuration Scenarios Collaboration Profiles Routing Rules Collaboration Agreements Demo: Integration Builder The Steps for Message Configuration Scenario R2D: Step by Step Scenario D2R: Step by Step Q & A,Configuration Scenarios,Configuration Scenarios用于将接口配置相关

9、的对象分组，从而使得查找某个接口相关内容时候变得简单易见。 可以通过ESR中的Model Configurator来实现，这种方式可以尽可能的实现流程配置的自动化。 当传输Configuration Scenario时，其中包含的所有配置对象都会被一次性的传输，而不需要单个选择，从而使得传输更便捷。 Configuration Scenario提供了以下标签页方便理解。,目录,Two Main Phases on PI Implementation Integration Directory Overview and Concepts Configuration Scenarios Colla

10、boration Profiles Routing Rules Collaboration Agreements Demo: Integration Builder The Steps for Message Configuration Scenario R2D: Step by Step Scenario D2R: Step by Step Q & A,Collaboration Profile: Party (Partner),The optional object party facilitates the B2B functions of SAP Process Integration

11、 and contains the following information: A Name and a Description Additional identifiers (DUNS, DUNS+4, GLN) Assigned Communication Components,Collaboration Profile: Communication Component,Component Object : Business Component,是一个抽象的实体，用于标示消息的发送端或/和接收端系统。 可以用于跨公司的流程，如：一个公司只公开了其接口信息或者其系统信息部分。 可以在其中定

12、义其所属的物理系统或者其子系统并包含其相关的接口。 可以用于接口分组。 这是一个逻辑系统，没有对应物理系统。,Component Object : Business System,Business System直接来自于PI SLD中定义的系统。 因此，它包含了分配给它的SWCV以及SWCV中已经发布的接口信息。 可以作为消息的发送者或者接受者。 有所属的物理系统对应。,Collaboration Profile: Channel,Communication Channel 包含了连接发送或接收系统具体的信息，如：传输协议，消息协议，服务器信息, 登陆信息 ，以及相关Adapter特定的信息。

13、,Sender or Receiver channel,Adapter Types,目录,Two Main Phases on PI Implementation Integration Directory Overview and Concepts Configuration Scenarios Collaboration Profiles Routing Rules Collaboration Agreements Demo: Integration Builder The Steps for Message Configuration Scenario R2D: Step by Step

14、 Scenario D2R: Step by Step Q & A,Routing Rule: Receiver Determination,通过条件设定决定消息转发方向,分配一个或者多个系统给指定的发送端系统和接口的组合 基于内容定义接收系统是可行的（通过Xpath等实现） 接收端系统应该是一个切实存在的系统。,Routing Rule: Interface Determination,Interface Determination帮忙确定消息应该被发送到前一步骤（Receiver Determination）中指定的接收端系统中的哪个接口，并且同时定义了哪个Operation Mappin

15、g会被用于消息转换。 帮助确定消息将被发送到哪个接口的条件会在消息文本中提及。 Interface Determination可以用于配置基于Mapping的消息分离。,Routing Rule: Interface Determination,Assign one or more inbound interfaces to be used for the inbound processing of a message (after the receiver determination). Assign an Operation Mapping for each outbound-inboun

16、d interface pair,目录,Two Main Phases on PI Implementation Integration Directory Overview and Concepts Configuration Scenarios Collaboration Profiles Routing Rules Collaboration Agreements Demo: Integration Builder The Steps for Message Configuration Scenario R2D: Step by Step Scenario D2R: Step by St

17、ep Q & A,Collaboration Agreement,The objects Sender Agreement and Receiver Agreement 指定Interface和Channel间的绑定关系 包含了额外的安全性验证，如证书等。 Sender Agreement用在消息发送端 ，Receiver Agreement用在消息接收端。,目录,Two Main Phases on PI Implementation Integration Directory Overview and Concepts Configuration Scenarios Collaborati

18、on Profiles Routing Rules Collaboration Agreements Demo: Integration Builder The Steps for Message Configuration Scenario R2D: Step by Step Scenario D2R: Step by Step Q & A,Enter Integration Builder,PI DEV website: :50000/dir/start/index.jsp,Click the Integration Builder,Integration Builder Overview

19、,Menu bar,Tool bar,Objects list,Object editor,Create New Objects,Two ways to create Objects: On menu bar, Object-New Right click when you click some Objects.,目录,Two Main Phases on PI Implementation Integration Directory Overview and Concepts Configuration Scenarios Collaboration Profiles Routing Rul

20、es Collaboration Agreements Demo: Integration Builder The Steps for Message Configuration Scenario R2D: Step by Step Scenario D2R: Step by Step Q & A,The steps for message configuration,Create Configuration Scenario Create Business Component Create Sender/Receiver Communication Channel Create Sender

21、/Receiver Agreement Create Receiver Determination Create Interface Determination Check,目录,Two Main Phases on PI Implementation Integration Directory Overview and Concepts Configuration Scenarios Collaboration Profiles Routing Rules Collaboration Agreements Demo: Integration Builder The Steps for Mes

22、sage Configuration Scenario R2D: Step by Step Scenario D2R: Step by Step Q & A,Step 1: Create Configuration Scenario,Configuration Scenario can be used to group all the settings of the same message scenario Naming Rule: MM/PP/SD/FI/CO_D2R/R2D_xxx,Step 2: Create Business Component,A Business Componen

23、t represents an abstract entity for addressing the senders and receivers of messages Create the Business Component under the Party Naming Rule: MM/PP/SD/FI/CO_D2R/R2D_xxx,Scenario would be assigned automatically,Step 3: Create Communication Channel - Sender,The sender is RFC in scenario R2D Naming R

24、ule: _Sender/Receiver_Additional Description,應與SAP ECC sm59的設定相同, 此設定也應該用在該RFC的outbound destination上,連上ERP, 帳號:RFCUSER 密碼:Eagles,Step 3: Create Communication Channel - Receiver,The receiver is the Data Center in scenario R2D Naming Rule: _Sender/Receiver_Additional Description,設定JDBC的連線資訊,Transactio

25、n Isolation Level: read_commited Click “Disconnection.”,Step 4: Create Collaboration Agreement - Sender,The sender is RFC in scenario R2D Binding the sender communication channel into sender agreement,Step 4: Create Collaboration Agreement - Receiver,The receiver is the Data Center in scenario R2D B

26、inding the receiver communication channel into receiver agreement,Step 5: Create Interface Determination,Choice one Operation Mapping that created in Enterprise Services Repository to be the bridge of Sender interface and Receiver interface,BC:1000-MM_R2D_xxx,Receiver Agreement,Additional Step: repe

27、at Step 2 Step 5,If the destination has many, for example company 1000, 8000 and 8100, we would repeat step 2 5 to create some objects of need.,CC:JDBC,BS:SAP DEV060,Sender Agreement,CC:RFC,Interface Determination,BC:8000-MM_R2D_xxx,Receiver Agreement,CC:JDBC,BC:8100-MM_R2D_xxx,Receiver Agreement,CC

28、:JDBC,Receiver Determination,Step 6: Create Receiver Determination,Giving the communication component of destination for outbound interface If the outbound message would be routed according to some rules, we can assign Condition for it,Step 7: Check (I),Check if the configuration is miss or not on t

29、he Receiver Determination,假若設定不正確或不完全，此處則有Object為空值,Step 7: Check (II),In the scenario that created on Step 1 all the configurations of this R2D scenario should be included on it.,目录,Two Main Phases on PI Implementation Integration Directory Overview and Concepts Configuration Scenarios Collaboratio

30、n Profiles Routing Rules Collaboration Agreements Demo: Integration Builder The Steps for Message Configuration Scenario R2D: Step by Step Scenario D2R: Step by Step Q & A,Step 1: Create Configuration Scenario,Configuration Scenario can be used to group all the settings of the same message scenario

31、Naming Rule: MM/PP/SD/FI/CO_D2R/R2D_xxx,Step 2: Create Business Component,A Business Component represents an abstract entity for addressing the senders and receivers of messages Create the Business Component under the Party Naming Rule: MM/PP/SD/FI/CO_D2R/R2D_xxx,Scenario would be assigned automatic

32、ally,Step 3: Create Communication Channel Sender (I),The sender is the Data Center in scenario D2R Naming Rule: _Sender/Receiver_Additional Description,設定JDBC的連線資訊 康舒科技: jdbc:oracle:thin:10.10.30.19:1521:TMRP3 康舒電子: jdbc:oracle:thin:192.168.125.17:1521:BMRP2 康展電子: jdbc:oracle:thin:192.168.125.17:152

33、1:EMRPTEST,Transaction Isolation Level: read_commited Click “Disconnection.”,Step 3: Create Communication Channel Sender (II),Query SQL Statement: select fields should be matched with data structure in Enterprise Services Repository Document Name is message type in Enterprise Services Repository Upd

34、ate SQL Statement: where condition should be consistent in Query SQL Statement,Step 3: Create Communication Channel Sender (III),Assigned Modules and its parameters to make asynchronous adapter to be synchronous Remember the name of receiverChannel. We will create it on next step,AF_Modules/RequestR

35、esponseBean AF_Modules/ResponseOnewayBean,passThrough : true receiverChannel : JDBC_Receiver_PUBLIC receiverParty: Company_1000 receiverService : PUBLIC,Step 3: Create Communication Channel - Receiver (I),There are two receiver channel in scenario D2R. One is RFC. The other is JDBC receiver (RFC res

36、ponse) Naming Rule: _Sender/Receiver_Additional Description,設定JDBC的連線資訊 jdbc:oracle:thin:10.10.30.19:1521:TMRP3,Step 3: Create Communication Channel - Receiver (II),Only have one communication channel of RFC receiver for public using. So dont need to create communication channel of RFC receiver,Step

37、 4: Create Collaboration Agreement - Sender,The sender is the Data Center in scenario D2R Binding the sender communication channel into sender agreement,Step 4: Create Collaboration Agreement - Receiver,The receiver is the RFC in scenario D2R Binding the receiver communication channel into receiver

38、agreement,Step 5: Create Interface Determination,Choice one Operation Mapping that created in Enterprise Services Repository to be the bridge of Sender interface and Receiver interface,Step 6: Create Receiver Determination,Giving the communication component of destination for outbound interface If the outbound message would be routed according to some rules, we can assign Condition for it,BC:1000-MM_R2D_xxx,Sender Agreement,Additional Step: repeat Step 2 Step 6 (I),If the source has many, for example from company 1000