简体繁体 English

在APIC上运行自定义策略时，如何解决“ CALL规则无法运行”错误？

[英]How can I resolve “CALL rule is not operational” error when running custom policy on APIC?

原文 2018-09-25 16:51:11 1 1 policy/ ibm-datapower/ apiconnect/ apic

我从DataPower导出了一个策略，并将其导入APIC ，它成功导入，但是在运行它时，出现以下错误：

1,20180917T153109.216Z,APIMgmt_863A6BF796,multistep,error,mpgw,webapi,63241538,63241538,10.68.128.47,0x80c00009,,request,"request webapi-policy-step-fw-invoke-rule #2 Calling rule var://context/policy/exec with input NULL and output policy-output-temp. failed: CALL rule is not operational" 1,20180917T153109.220Z,APIMgmt_863A6BF796,xslt,error,mpgw,webapi,63241538,63241538,10.68.128.47,0x80c00010,,request,"Processing of 'local:///isp/policy/apim.policy.end.xsl' stopped: CALL rule is not operational" 1,20180917T153109.221Z,APIMgmt_863A6BF796,multistep,error,mpgw,webapi,63241538,63241538,10.68.128.47,0x80c00009,,request,"request webapi-policy-end #1 xform: Transforming the content of NULL. The transformation local:///isp/policy/apim.policy.end.xsl is applied. The results are stored in NULL. failed: CALL rule is not operational" 1,20180917T153109.221Z,APIMgmt_863A6BF796,multistep,error,mpgw,webapi,63241538,63241538,10.68.128.47,0x80c00009,,request,"request webapi-policy-step-fw-invoke-rule #5 Calling rule var://context/policy/fw/call-rule with input NULL and output NULL. failed: CALL rule is not operational" 1,20180917T153109.221Z,APIMgmt_863A6BF796,multistep,error,mpgw,webapi,63241538,63241538,10.68.128.47,0x80c00009,,request,"request webapi-mpgw-request-fw #9 Calling rule var://context/policy/fw/call-rule with input NULL and output NULL. failed: CALL rule is not operational" 1,20180917T153109.221Z,APIMgmt_863A6BF796,mpgw,error,mpgw,webapi,63241538,63241538,10.68.128.47,0xd30003,,error,"Rejected by filter; SOAP fault sent" 1,20180917T153109.223Z,APIMgmt_863A6BF796,xsltmsg,error,mpgw,webapi,63241538,63241538,10.68.128.47,0x80000001,,error,"api-error-response multistep error"

1 个解决方案

Error code 0x80c00009 is unfortunately a quite "broad" topic but it all boils down to some problem within your rule making it invalid or to crash when running. 不幸的是，错误代码0x80c00009是一个“广泛的”主题，但是所有这些归结为您的规则中的某个问题，使其无效或在运行时崩溃。 My guess is that the Rule is invalid... 我的猜测是该规则无效...

Make sure the scripts (XSLT and/or GWS) compiles and that all INPUT, OUTPUT, PIPE, NULL are properly configured. 确保脚本（XSLT和/或GWS）已编译，并且所有INPUT，OUTPUT，PIPE，NULL均已正确配置。

If you have access to the DataPower instance (or run a Docker instance on your local laptop) you can export the Processing Policy and import it and run it "stand alone" to make sure it works and no syntax/config errors occurs in it. 如果您有权访问DataPower实例（或在本地便携式计算机上运行Docker实例），则可以导出处理策略并将其导入并“独立运行”以确保其有效，并且其中不会发生语法/配置错误。

If you are running large messages you might need to tune the XML Manager as well. 如果您正在运行大型消息，则可能还需要调整XML Manager。