2016-08-30 99 views
1

我正在将WSO2 ESB 4.8.1与SFDC集成。与SFDC的Wso2 ESB集成

使用SFDC连接器1.0

在WSO2我所编写的代码<salesforce.logout/>,根据WSO2文档他们说,它关闭当前连接。

<salesforce.logout/>产生下面是我在WSO2 ESB日志

TID: [0] [ESB] [2016-08-30 07:55:39,442] DEBUG {org.apache.synapse.transport.http.wire} -  << "<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:partner.soap.sforce.com"><soapenv:Header><urn:SessionHeader><urn:sessionId>00D17000000BPGr!AQcAQDIggW.ikXtsb0Ckm8c8pKKDlF_8QN42jL31WUa6hDLOdEeNIjrYsevKW0FeZLDzlrjcDLwMni_7gYaZgNfdN4zv9Cgj</urn:sessionId></urn:SessionHeader></soapenv:Header><soapenv:Body><urn:logout></urn:logout></soapenv:Body></soapenv:Envelope>[\r][\n]" {org.apache.synapse.transport.http.wire} 

确定SOAP消息,但几次我得到以下错误(INVALID_SESSION_ID AM:无效的会话ID在SessionHeader发现:非法的会话的会话没有找到,缺少会话哈希:)<salesforce.logout/>执行

TID: [0] [ESB] [2016-08-30 07:55:39,529] DEBUG {org.apache.synapse.transport.http.wire} -  >> "<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:sf="urn:fault.partner.soap.sforce.com" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Body><soapenv:Fault><faultcode>sf:INVALID_SESSION_ID</faultcode><faultstring>INVALID_SESSION_ID: Invalid Session ID found in SessionHeader: Illegal Session. Session not found, missing session hash: je59etMAEPM+m9VdYJb0AW==[\n]" {org.apache.synapse.transport.http.wire} 
TID: [0] [ESB] [2016-08-30 07:55:39,529] DEBUG {org.apache.synapse.transport.http.wire} -  >> "This is expected, it can happen if the session has expired and swept away, or if the user logs out, or if its just someone trying to hack in. </faultstring><detail><sf:UnexpectedErrorFault xsi:type="sf:UnexpectedErrorFault"><sf:exceptionCode>INVALID_SESSION_ID</sf:exceptionCode><sf:exceptionMessage>Invalid Session ID found in SessionHeader: Illegal Session. Session not found, missing session hash: je59etMAEPM+m9VdYJb0AW==[\n]" {org.apache.synapse.transport.http.wire} 
TID: [0] [ESB] [2016-08-30 07:55:39,529] DEBUG {org.apache.synapse.transport.http.wire} -  >> "This is expected, it can happen if the session has expired and swept away, or if the user logs out, or if its just someone trying to hack in. </sf:exceptionMessage></sf:UnexpectedErrorFault></detail></soapenv:Fault></soapenv:Body></soapenv:Envelope>[\r][\n]" {org.apache.synapse.transport.http.wire} 

它是SFDC问题/ WSO2 SFDC连接器问题/ WSO2 ESB配置问题。

对于更新插入操作,我们使用configkey属性在整个项目中,下面是代码

<salesforce.upsert configKey="sfdc_connection_dtls"> 
          <allOrNone>0</allOrNone> 
          <allowFieldTruncate>0</allowFieldTruncate> 
          <sobjects xmlns:sfdc="sfdc">{//sfdc:sObjects}</sobjects> 
        </salesforce.upsert> 

所以,当我在各自的顺序使用<salesforce.logout/>,不是仅关闭当前连接,也就是按顺序使用。 ?或者关闭所有现有的连接。

我在哪里使用salesforce.upsert(以下是框架代码),我可以在salesforce.upsert调用后使用<salesforce.logout/>

<salesforce.upsert configKey="sfdc_connection_dtls"> 
     <!-- sobject goes here --> 
</salesforce.upsert> 

期待您的帮助

感谢, Tejas的

回答

1

在WSO2 SFDC连接器,还有每初始化配置流程创建一个单一的SF连接。因此,如果您发出注销,您的后续请求将失败。没有必要发出注销,因为无论如何都会在流程结束时终止连接。