- 浏览: 494431 次
- 性别:
- 来自: 北京
-
文章分类
最新评论
-
cloudfile:
谢谢分享!
MyEclipse配置Tomcat(图解) -
dotjar:
有效没?
治咳嗽秘方 -
jyslb:
设置密码长度大于10位,其中包含%$#&等符号,你这个 ...
奶瓶无线破解介绍 -
廖乐逍遥:
还是不行。。
eclipse里不支持泛型的解决方法 -
cue2008:
http://backtrack.unixheads.org/ ...
Intel 3945ABG无线网卡破解无线路由器密码 BT3
Service Interfaces
Problem
You are sending a message to an integration process component. The message is set to error status with the error code BPE_ADAPTER UNKNOWN_MESSAGE.
A transformation step or synchronous send step fails with the error message "No definition exists for <Interface Namespace> <Interface Name>" (SWF_XMP 021)."
Analysis
Service interfaces have been introduced in SAP NetWeaver PI 7.1 which support multiple operations. The message interfaces known from prior releases are still supported by creating service interfaces of category "XI 3.0 compatible" which restricts them to only provide a single operation, the so-called default operation.
Operations are distinguishable by the underlying message type, which in turn has to be defined by a unique root tag and its namespace. Integration processes accessing service interfaces having multiple operations enforce using the correct operation by checking the name and namespace of the payload's root element (root tag). When new messages enter the Business Process Engine (BPE), that is, if a message is received (using a receive step or synchronous send step) or created (using a transformation step), its root tag has to match the operation's message type - otherwise the respective step fails.
If messages are not accepted by the BPE with the aforementioned error messages, check whether the actual payload matches the definition of the message type of the operation. With respect to the namespace, the subtle differences between the default namespace (<root xmlns="urn:example:com">), an explicit namespace (<ns1:root xmlns:ns1="urn:example:com">), an empty namespace (<ns1:root xmlns:ns1="">), or a tag without an associated namespace (<root>) are a typical source of error.
The requirement of the root tag matching the definition in the Enterprise Service Repository is not enforced for of category "XI 3.0 compatible" service interfaces. This includes scenarios upgraded from SAP NetWeaver '04 or SAP NetWeaver 7.0. On the other hand, in scenarios using service interfaces with multiple operations, the root tag of the payload must adhere to the definition in the ES Repository.
Generic User Decisions - Work Item Title
Problem
In the work item list in the Business Workplace, some, or all, of the user decision work items have "generic decision task" as the title instead of the title configured in the process definition.
The title of a user decision work item is displayed in a language different from the user's logon language.
Analysis
The user's logon language differs from the language with which the work item was created or the title has not been translated into the user's logon language. Due to performance reasons, the work item titles are not translated into the user's logon language by default when viewing the list of work items. Instead, the title is displayed in the language the work item was created with or, if it has not been translated to this language, the default title for user decisions is displayed.
Make sure that all necessary translations of the title were provided in the process definition and have been activated. In the Business Workplace, use the menu path Settings ' Workflow Settings ' Personal Settings and select the setting Display Work Item Texts in Logon Language. To change the default for all users, use the SAP reference IMG in transaction SPRO, path Application Server ' Business Management ' SAP Business Workflow ' Basic Settings (Workflow System) ' Change Defaults for Personal Workflow Settings.
Generic User Decisions - Options of the User Decision
Problem
In the user decision work item in the inbox, the options are all labeled with the same text so that users do not know which one to choose.
Analysis
The user decision texts have not been translated into the language the user is logged on in. Translate the texts of the relevant integration process in the Enterprise Services Builder and activate the changes.
Message Packaging - Reconfiguration
Problem
The reconfiguration of one of the integration processes has been started using transaction SWF_INB_CONF. However, the reconfiguration does not finish although no hanging queues are to be found in transaction SMQ2. ccBPM Message Packaging is in use in the system.
Analysis
There are still messages to be delivered with the previous configuration. Use transaction SWF_INB_ADM to check for messages in error, suspended messages, or messages with scheduled status. If these messages are no longer deliverable, for example, due to the errors not being recoverable, or because no more delivery attempts are to be made, logically delete them using the relevant administration function. As soon as all pending messages for the previous configuration have reached a final status (either delivered or cancelled), the reconfiguration is processed.
Principal Propagation - Enabling Principal Propagation for a Process
Problem
Principal propagation shall be enabled for one of the integration processes. However, in transaction SWF_INB_CONF, the checkbox is missing for this integration process but it is shown for others.
Analysis
Integration processes can only propagate the principal of the message starting the process instance. To avoid ambiguity at runtime, principal propagation can only be enabled for processes that do not use correlations (that is, there are no inbound messages besides the starting message). If your process requires using correlations, principal propagation cannot be enabled for this process.
If your process has only a single inbound message, but you are still not able to activate principal propagation, check that no correlations are defined or used in the process definition. Remove any correlation definition, usage, or activation and activate the changes made to the process definition. You should now be able to configure principal propagation for this process in transaction SWF_INB_CONF.
Problem
You are sending a message to an integration process component. The message is set to error status with the error code BPE_ADAPTER UNKNOWN_MESSAGE.
A transformation step or synchronous send step fails with the error message "No definition exists for <Interface Namespace> <Interface Name>" (SWF_XMP 021)."
Analysis
Service interfaces have been introduced in SAP NetWeaver PI 7.1 which support multiple operations. The message interfaces known from prior releases are still supported by creating service interfaces of category "XI 3.0 compatible" which restricts them to only provide a single operation, the so-called default operation.
Operations are distinguishable by the underlying message type, which in turn has to be defined by a unique root tag and its namespace. Integration processes accessing service interfaces having multiple operations enforce using the correct operation by checking the name and namespace of the payload's root element (root tag). When new messages enter the Business Process Engine (BPE), that is, if a message is received (using a receive step or synchronous send step) or created (using a transformation step), its root tag has to match the operation's message type - otherwise the respective step fails.
If messages are not accepted by the BPE with the aforementioned error messages, check whether the actual payload matches the definition of the message type of the operation. With respect to the namespace, the subtle differences between the default namespace (<root xmlns="urn:example:com">), an explicit namespace (<ns1:root xmlns:ns1="urn:example:com">), an empty namespace (<ns1:root xmlns:ns1="">), or a tag without an associated namespace (<root>) are a typical source of error.
The requirement of the root tag matching the definition in the Enterprise Service Repository is not enforced for of category "XI 3.0 compatible" service interfaces. This includes scenarios upgraded from SAP NetWeaver '04 or SAP NetWeaver 7.0. On the other hand, in scenarios using service interfaces with multiple operations, the root tag of the payload must adhere to the definition in the ES Repository.
Generic User Decisions - Work Item Title
Problem
In the work item list in the Business Workplace, some, or all, of the user decision work items have "generic decision task" as the title instead of the title configured in the process definition.
The title of a user decision work item is displayed in a language different from the user's logon language.
Analysis
The user's logon language differs from the language with which the work item was created or the title has not been translated into the user's logon language. Due to performance reasons, the work item titles are not translated into the user's logon language by default when viewing the list of work items. Instead, the title is displayed in the language the work item was created with or, if it has not been translated to this language, the default title for user decisions is displayed.
Make sure that all necessary translations of the title were provided in the process definition and have been activated. In the Business Workplace, use the menu path Settings ' Workflow Settings ' Personal Settings and select the setting Display Work Item Texts in Logon Language. To change the default for all users, use the SAP reference IMG in transaction SPRO, path Application Server ' Business Management ' SAP Business Workflow ' Basic Settings (Workflow System) ' Change Defaults for Personal Workflow Settings.
Generic User Decisions - Options of the User Decision
Problem
In the user decision work item in the inbox, the options are all labeled with the same text so that users do not know which one to choose.
Analysis
The user decision texts have not been translated into the language the user is logged on in. Translate the texts of the relevant integration process in the Enterprise Services Builder and activate the changes.
Message Packaging - Reconfiguration
Problem
The reconfiguration of one of the integration processes has been started using transaction SWF_INB_CONF. However, the reconfiguration does not finish although no hanging queues are to be found in transaction SMQ2. ccBPM Message Packaging is in use in the system.
Analysis
There are still messages to be delivered with the previous configuration. Use transaction SWF_INB_ADM to check for messages in error, suspended messages, or messages with scheduled status. If these messages are no longer deliverable, for example, due to the errors not being recoverable, or because no more delivery attempts are to be made, logically delete them using the relevant administration function. As soon as all pending messages for the previous configuration have reached a final status (either delivered or cancelled), the reconfiguration is processed.
Principal Propagation - Enabling Principal Propagation for a Process
Problem
Principal propagation shall be enabled for one of the integration processes. However, in transaction SWF_INB_CONF, the checkbox is missing for this integration process but it is shown for others.
Analysis
Integration processes can only propagate the principal of the message starting the process instance. To avoid ambiguity at runtime, principal propagation can only be enabled for processes that do not use correlations (that is, there are no inbound messages besides the starting message). If your process requires using correlations, principal propagation cannot be enabled for this process.
If your process has only a single inbound message, but you are still not able to activate principal propagation, check that no correlations are defined or used in the process definition. Remove any correlation definition, usage, or activation and activate the changes made to the process definition. You should now be able to configure principal propagation for this process in transaction SWF_INB_CONF.
发表评论
-
Gateway Access Control Lists
2015-10-12 11:34 1229Source:http://wiki.scn.sap.com ... -
SLD_UC registration failes with return code 748
2015-10-12 09:44 2210The managed ABAP systems shoul ... -
SLD Related Gateway Serivces Unavaliable
2015-10-12 09:01 773转自:http://www.sapnew.com/212. ... -
JDBC/JMS driver deployment - now more forceMode=true
2012-11-07 19:36 1257转自:http://scn.sap.com/people ... -
JDBC Receiver Adatper的同步场景设计
2012-10-18 15:15 1112转自:http://scnblogs.techweb. ... -
XML Anonymizer Bean in Communication Channel to remove namespace prefix in XML P
2012-07-24 16:14 1444转:http://www.saptechnical.com/T ... -
Step-by-Step Guides - Connectivity > CIDX Message eStandards
2012-05-29 11:36 1356http://wiki.sdn.sap.com/wiki/di ... -
Chem XML Message eStandards and CIDX Scenario Part III
2012-05-25 00:32 964http://scn.sap.com/people/suraj ... -
Chem XML Message eStandards and CIDX Scenario development – Part II
2012-05-25 00:30 1118http://scn.sap.com/people/suraj ... -
Chem XML Message eStandards and CIDX Scenario – Part I
2012-05-25 00:28 1124http://scn.sap.com/people/suraj ... -
SLDDSUSER in SLD is getting Locked
2012-05-24 17:59 1242******* LOCAL to Solution Manag ... -
How to Start the Visual Administrator
2012-05-22 16:24 981http://help.sap.com/saphelp_nw7 ... -
利用XI同步调用(JDBC)oracle数据库的返回值。
2012-02-13 18:03 1166今天用CCBPM做一串业务操作,具体的操作是:我先异步更 ... -
XI/PI Tables LIST
2012-02-09 15:28 1108ABAP ABAP schema Database Trans ... -
(MID)com.sap.SOA.apt_rfc.0303
2012-02-02 11:51 871MessageID com.sap.SOA.apt_rfc.0 ... -
FAQ XI 3.0/ PI 7.0/ PI 7.1 RFC Adapter
2012-02-01 16:52 2464转自:http://www.saptechies.com/fa ... -
如何排查mapping报错。
2012-01-18 15:50 992XI/PI在开发过程中最容易也是出错最多的地位就是map ... -
RFC Sender to JDBC receiver scenario中值得注意的三个问题
2012-01-17 17:09 1497转自:http://scnblogs.techweb.com. ... -
copyValue用法
2012-01-05 15:24 1201copyValue目的就是实现可以取到一个LIST的任意值。 ... -
PI动态生成字段方法
2011-12-28 18:48 1103今天遇到这样一种情况,PI更新数据库时,有的字段是动态更新 ...
相关推荐
SAP Process Orchestration The Comprehensive Guide, 2nd Edition SAP流程编制综合指南 ...16 Migrating ccBPM from SAP PI to SAP PO 16.1 Motivation for Migration 16.2 Migration Approach ...
内容概要:本文详细介绍了如何利用Matlab构建、优化和应用决策分类树。首先,讲解了数据准备阶段,将数据与程序分离,确保灵活性。接着,通过具体实例展示了如何使用Matlab内置函数如fitctree快速构建决策树模型,并通过可视化工具直观呈现决策树结构。针对可能出现的过拟合问题,提出了基于成本复杂度的剪枝方法,以提高模型的泛化能力。此外,还分享了一些实用技巧,如处理连续特征、保存模型、并行计算等,帮助用户更好地理解和应用决策树。 适合人群:具有一定编程基础的数据分析师、机器学习爱好者及科研工作者。 使用场景及目标:适用于需要进行数据分类任务的场景,特别是当需要解释性强的模型时。主要目标是教会读者如何在Matlab环境中高效地构建和优化决策分类树,从而应用于实际项目中。 其他说明:文中不仅提供了完整的代码示例,还强调了代码模块化的重要性,便于后续维护和扩展。同时,对于初学者来说,建议从简单的鸢尾花数据集开始练习,逐步掌握决策树的各项技能。
《营销调研》第7章-探索性调研数据采集.pptx
Assignment1_search_final(1).ipynb
美团优惠券小程序带举牌小人带菜谱+流量主模式,挺多外卖小程序的,但是都没有搭建教程 搭建: 1、下载源码,去微信公众平台注册自己的账号 2、解压到桌面 3、打开微信开发者工具添加小程序-把解压的源码添加进去-appid改成自己小程序的 4、在pages/index/index.js文件搜流量主广告改成自己的广告ID 5、到微信公众平台登陆自己的小程序-开发管理-开发设置-服务器域名修改成
《计算机录入技术》第十八章-常用外文输入法.pptx
基于Andorid的跨屏拖动应用设计实现源码,主要针对计算机相关专业的正在做毕设的学生和需要项目实战练习的学习者,也可作为课程设计、期末大作业。
《网站建设与维护》项目4-在线购物商城用户管理功能.pptx
区块链_房屋转租系统_去中心化存储_数据防篡改_智能合约_S_1744435730
《计算机应用基础实训指导》实训五-Word-2010的文字编辑操作.pptx
《移动通信(第4版)》第5章-组网技术.ppt
ABB机器人基础.pdf
《综合布线施工技术》第9章-综合布线实训指导.ppt
很不错的一套站群系统源码,后台配置采集节点,输入目标站地址即可全自动智能转换自动全站采集!支持 https、支持 POST 获取、支持搜索、支持 cookie、支持代理、支持破解防盗链、支持破解防采集 全自动分析,内外链接自动转换、图片地址、css、js,自动分析 CSS 内的图片使得页面风格不丢失: 广告标签,方便在规则里直接替换广告代码 支持自定义标签,标签可自定义内容、自由截取、内容正则截取。可以放在模板里,也可以在规则里替换 支持自定义模板,可使用标签 diy 个性模板,真正做到内容上移花接木 调试模式,可观察采集性能,便于发现和解决各种错误 多条采集规则一键切换,支持导入导出 内置强大替换和过滤功能,标签过滤、站内外过滤、字符串替换、等等 IP 屏蔽功能,屏蔽想要屏蔽 IP 地址让它无法访问 ****高级功能*****· url 过滤功能,可过滤屏蔽不采集指定链接· 伪原创,近义词替换有利于 seo· 伪静态,url 伪静态化,有利于 seo· 自动缓存自动更新,可设置缓存时间达到自动更新,css 缓存· 支持演示有阿三源码简繁体互转· 代理 IP、伪造 IP、随机 IP、伪造 user-agent、伪造 referer 来路、自定义 cookie,以便应对防采集措施· url 地址加密转换,个性化 url,让你的 url 地址与众不同· 关键词内链功能· 还有更多功能等你发现…… 程序使用非常简单,仅需在后台输入一个域名即可建站,不限子域名,站群利器,无授权,无绑定限制,使用后台功能可对页面进行自定义修改,在程序后台开启生 成功能,只要访问页面就会生成一个本地文件。当用户再次访问的时候就直接访问网站本地的页面,所以目标站点无法访问了也没关系,我们的站点依然可以访问, 支持伪静态、伪原创、生成静态文件、自定义替换、广告管理、友情链接管理、自动下载 CSS 内的图。
【自然语言处理】文本分类方法综述:从基础模型到深度学习的情感分析系统设计
基于Andorid的下拉浏览应用设计实现源码,主要针对计算机相关专业的正在做毕设的学生和需要项目实战练习的学习者,也可作为课程设计、期末大作业。
内容概要:本文详细介绍了一个原创的P2插电式混合动力系统Simulink模型,该模型基于逻辑门限值控制策略,涵盖了多个关键模块如工况输入、驾驶员模型、发动机模型、电机模型、制动能量回收模型、转矩分配模型、运行模式切换模型、档位切换模型以及纵向动力学模型。模型支持多种标准工况(WLTC、UDDS、EUDC、NEDC)和自定义工况,并展示了丰富的仿真结果,包括发动机和电机转矩变化、工作模式切换、档位变化、电池SOC变化、燃油消耗量、速度跟随和最大爬坡度等。此外,文章还深入探讨了逻辑门限值控制策略的具体实现及其效果,提供了详细的代码示例和技术细节。 适合人群:汽车工程专业学生、研究人员、混动汽车开发者及爱好者。 使用场景及目标:①用于教学和科研,帮助理解和掌握P2混动系统的原理和控制策略;②作为开发工具,辅助设计和优化混动汽车控制系统;③提供仿真平台,评估不同工况下的混动系统性能。 其他说明:文中不仅介绍了模型的整体架构和各模块的功能,还分享了许多实用的调试技巧和优化方法,使读者能够更好地理解和应用该模型。
内容概要:本文详细介绍了基于ADMM(交替方向乘子法)算法在电力系统分布式调度中的应用,特别是并行(Jacobi)和串行(Gauss-Seidel)两种不同更新模式的实现。文中通过MATLAB代码展示了这两种模式的具体实现方法,并比较了它们的优劣。并行模式适用于多核计算环境,能够充分利用硬件资源,尽管迭代次数较多,但总体计算时间较短;串行模式则由于“接力式”更新机制,通常收敛更快,但在计算资源有限的情况下可能会形成瓶颈。此外,文章还讨论了惩罚系数rho的自适应调整策略以及在电-气耦合系统优化中的应用实例。 适合人群:从事电力系统优化、分布式计算研究的专业人士,尤其是有一定MATLAB编程基础的研究人员和技术人员。 使用场景及目标:①理解和实现ADMM算法在电力系统分布式调度中的应用;②评估并行和串行模式在不同应用场景下的性能表现;③掌握惩罚系数rho的自适应调整技巧,提高算法收敛速度和稳定性。 其他说明:文章提供了详细的MATLAB代码示例,帮助读者更好地理解和实践ADMM算法。同时,强调了在实际工程应用中需要注意的关键技术和优化策略。
内容概要:本文深入研究了交错并联Buck变换器的工作原理、性能优势及其具体实现。文章首先介绍了交错并联Buck变换器相较于传统Buck变换器的优势,包括减小输出电流和电压纹波、降低开关管和二极管的电流应力、减小输出滤波电容容量等。接着,文章详细展示了如何通过MATLAB/Simulink建立该变换器的仿真模型,包括参数设置、电路元件添加、PWM信号生成及连接、电压电流测量模块的添加等。此外,还探讨了PID控制器的设计与实现,通过理论分析和仿真验证了其有效性。最后,文章通过多个仿真实验验证了交错并联Buck变换器在纹波性能、器件应力等方面的优势,并分析了不同控制策略的效果,如P、PI、PID控制等。 适合人群:具备一定电力电子基础,对DC-DC变换器特别是交错并联Buck变换器感兴趣的工程师和技术人员。 使用场景及目标:①理解交错并联Buck变换器的工作原理及其相对于传统Buck变换器的优势;②掌握使用MATLAB/Simulink搭建交错并联Buck变换器仿真模型的方法;③学习PID控制器的设计与实现,了解其在电源系统中的应用;④通过仿真实验验证交错并联Buck变换器的性能,评估不同控制策略的效果。 其他说明:本文不仅提供了详细的理论分析,还给出了大量可运行的MATLAB代码,帮助读者更好地理解和实践交错并联Buck变换器的设计与实现。同时,通过对不同控制策略的对比分析,为实际工程应用提供了有价值的参考。
《综合布线施工技术》第8章-综合布线工程案例.ppt