SAP_PI_KUT_03MessageConfiguration

SAPPIMessageConfiguration2014/12/16©2012SAPAG.Allrightsreserved.2课程目标参加完该课程后，参与者需要掌握以下内容：•可以创建ID对象•理解消息转发规则•理解外围系统连接协议2©2012SAPAG.Allrightsreserved.33目录TwoMainPhasesonPIImplementationIntegrationDirectoryOverviewandConceptsConfigurationScenariosCollaborationProfilesRoutingRulesCollaborationAgreementsDemo:IntegrationBuilderTheStepsforMessageConfigurationScenarioR2D:StepbyStepScenarioD2R:StepbyStepQ&A©2012SAPAG.Allrightsreserved.44Twomainphases:designtimeandconfigurationtimeMessageDefinitionandMappingMessageRouting©2012SAPAG.Allrightsreserved.55目录TwoMainPhasesonPIImplementationIntegrationDirectoryOverviewandConceptsConfigurationScenariosCollaborationProfilesRoutingRulesCollaborationAgreementsDemo:IntegrationBuilderTheStepsforMessageConfigurationScenarioR2D:StepbyStepScenarioD2R:StepbyStepQ&A©2012SAPAG.Allrightsreserved.6OverviewIntegrationDirector用于将ESR设计阶段中创建的对象进行配置连接，从而完成整个集成场景。在ID中进行配置的前置条件是相关内部系统已经在SLD中创建，场景/接口会使用到的设计阶段的对象已经在ESR中创建完成。ProcessIntegrationScenarios在ESR中创建，在ID中配置，在IS（IntegrationServer）中执行。ID在最开始时不包含任何内容，用户需要根据在SLD中配置的内容进行相关的内容的添加。同样，部分内容也可以由ESR添加进来。如，ESR中创建的ProcessModule等。基于J2EE的Adapter可以在ID中进行集中配置。AdvancedAdapterEngine（AAE）不使用IntegrationEngine进行消息处理。从而可以保证一个相对较高的性能表现。然而使用AAE也是受限的，例如，仅有部分Adapter支持AAE。6©2012SAPAG.Allrightsreserved.77IntegrationDirectory:OverviewIntegrationDirectoryAdaptintegrationcontenttospecificconfigurationDeliveredempty,withoutpredefinedcontentallcontentiscustomer-specificIntegrationcontentderivedfromEnterpriseServicesRepositoryOpenforCustomertoaddcollaborationknowledgerelevanttonon-SAPcomponentsHomeforcentralizedadapterconfigurationDataproviderforISruntimeIntegrationBuilderIntegrationDirectoryBusinessProcessesRoutingRulesBusinessScenariosReceiverDeterminationRulesInterfaceDeterminationRules(includingMappingAssignment)ConfigurationEditorsConfigurationWizardsCollaborationProfilesParties,Services&ChannelsCollaborationAgreementsSender&ReceiverAgreements©2012SAPAG.Allrightsreserved.88TaskAreasAtConfigurationTimeIntegrationDirectory范围任务CollaborationProfile(包括：CommunicationParty,Service,CommunicationChannel)记录了消息交换涉及到的系统，以及与发送端，接收端系统连接的基本信息。LogicalRouting(包括：ReceiverDetermination,InterfaceDetermination)定义了消息在系统间的转发规则。CollaborationAgreement(包括：SenderAgreement,ReceiverAgreement)定义了消息处理的技术细节，数据有效性验证，HeaderMapping等，如：涉及的Adapter配置。©2012SAPAG.Allrightsreserved.99CollaborationProfileObjectsAcommunicationpartyrepresentsalargerunitwhichisinvolvedinacross-systemprocess(forexampleacompany).Servicesareusedto:•Representatechnicalorbusinessunit,whichistobeaddressedasthesenderorreceiverofmessages.•Groupinterfacestoexchangemessagesaccordingtoparticulartaskareas.•Addressbusinesssystemsandbusinessprocessesassendersorreceiversofmessages.CommunicationChannel定义了Adapter怎么传输消息，如此，该消息可以发送到IE进行处理或者由IE处理完后发出。©2012SAPAG.Allrightsreserved.1010LogicalRoutingObjectsReceiverDetermination定义了一个或多个接收端系统并且标明了发送端系统和接口InterfaceDetermination标明了哪个接收端接口被用来处理消息，同时OperationMapping也会在此处给出。©2012SAPAG.Allrightsreserved.1111CollaborationAgreementObjects在ReceiverAgreement中,定义了一个Message怎样被发送到接收端系统。在SenderAgreement中，定义了Message怎样被接收进入IE，并被IE处理。©2012SAPAG.Allrightsreserved.1212目录TwoMainPhasesonPIImplementationIntegrationDirectoryOverviewandConceptsConfigurationScenariosCollaborationProfilesRoutingRulesCollaborationAgreementsDemo:IntegrationBuilderTheStepsforMessageConfigurationScenarioR2D:StepbyStepScenarioD2R:StepbyStepQ&A©2012SAPAG.Allrightsreserved.13ConfigurationScenariosConfigurationScenarios用于将接口配置相关的对象分组，从而使得查找某个接口相关内容时候变得简单易见。可以通过ESR中的ModelConfigurator来实现，这种方式可以尽可能的实现流程配置的自动化。当传输ConfigurationScenario时，其中包含的所有配置对象都会被一次性的传输，而不需要单个选择，从而使得传输更便捷。ConfigurationScenario提供了以下标签页方便理解。13©2012SAPAG.Allrightsreserved.1414目录TwoMainPhasesonPIImplementationIntegrationDirectoryOverviewandConceptsConfigurationScenariosCollaborationProfilesRoutingRulesCollaborationAgreementsDemo:IntegrationBuilderTheStepsforMessageConfigurationScenarioR2D:StepbyStepScenarioD2R:StepbyStepQ&A©2012SAPAG.Allrightsreserved.1515CollaborationProfile:Party(Partner)•TheoptionalobjectpartyfacilitatestheB2BfunctionsofSAPProcessIntegrationandcontainsthefollowinginformation:•ANameandaDescription•Additionalidentifiers(DUNS,DUNS+4,GLN)•AssignedCommunicationComponents©2012SAPAG.Allrightsreserved.1616CollaborationProfile:CommunicationComponentCommunicationComponentObjects:将一个系统标注为消息发送系统或/和接收系统。接口分组的一种方式，CommunicationComponent可以包含多个属于该系统的接口。包含两部分内容:Interfaces(inbound/outbound)Communicationchannels(sender/receiver)3种类型:BusinessComponentBusinessSystemIntegrationProcess©2012SAPAG.Allrightsreserved.1717ComponentObject:BusinessComponent是一个抽象的实体，用于标示消息的发送端或/和接收端系统。可以用于跨公司的流程，如：一个公司只公开了其接口信息或者其系统信息部分。可以在其中定义其所属的物理系统或者其子系统并包含其相关的接口。可以用于接口分组。这是一个逻辑系统，没有对应物理系统。©2012SAPAG.Allrightsreserved.1818ComponentObject:BusinessSystemBusinessSystem直接来自于PISLD中定义的系统。因此，它包含了分配给它的SWCV以及SWCV中已经发布的接口信息。可以作为消息的发送者或者接受者。有所属的物理系统对应。©2012SAPAG.Allrightsreserved.1919CollaborationProfile:ChannelCommunicationChannel包含了连接发送或接收系统具体的信息，如：传输协议，消息协议，服务器信息,登陆信息，以及相关Adapter特定的信