Topic
  • 4 replies
  • Latest Post - ‏2011-05-30T19:07:58Z by WS7Newbie
WS7Newbie
WS7Newbie
5 Posts

Pinned topic Can't get Federation in WSRR SFM add-on to work

‏2011-05-25T14:49:06Z |
I was reading the IBM Redpaper entitled Exploiting IBM WebSphere Service Registry and Repository Feature Pack for Service Federation Management to Share Services Between Two Domains and I tried implementing SFM using the sample walk-through provided in it.

The only difference I made is that instead of Message Broker, I used ESB on both the Domains (see picture). I also did not make use of FQDNs and used static IPs instead. So my setup is as below:

System 1: WAS with Web Service ESB as proxy WSRR with SFM

System 2: ESB as proxy WSRR with SFM and test client application to connect to the web service

I was able to successfully follow the steps and successfully did the federation configurations in SFM with no errors. I checked all settings as described in pp.40-48 of the Redpaper and everything seems similar. Proxies seem ok as well.

However, when I installed the client app on the eBusiness domain and ran the sample test page, I keep encountering the error below:
Result
exception: javax.xml.ws.WebServiceException: com.ibm.websphere.sca.ServiceRuntimeException: CWSXM0202E: An unexpected exception occurred when processing mediation flow for component ScmProxy in module ScmProxy_v1_0_0_WESBConnectivityProvider-eBiz_ae04: CWSXM1025E: An unexpected exception occurred when the flow was called: CWSXM0111E: Service runtime exception calling an import from mediation component ScmProxy in module ScmProxy_v1_0_0_WESBConnectivityProvider-eBiz_ae04: CWSXM0205E: An unexpected business logic exception occurred.: CWSXM3300E: Fail primitive 'FailFlow', component 'ScmProxy', module 'ScmProxy_v1_0_0_WESBConnectivityProvider-eBiz_ae04', interface '{http://www.ibm.com/websphere/sibx/ServiceGateway}ServiceGateway', operation 'requestResponse', raised a FailFlowException. The user-supplied error message is 'CWSXM7007E: The following error occurred while attempting to invoke the target service 'http://10.10.10.2:9080/ibm/scm/connectivity-provider/WESBConnectivityProvider/group-proxy/uxhr/sca/ScmProxySoap11Export/fyza' for proxy target 'rz8j' on group proxy 'ae04': javax.xml.ws.WebServiceException: java.net.ConnectException: Connection refused: no further information': caused by: com.ibm.wsspi.sibx.mediation.flow.MediationRuntimeException: CWSXM1025E: An unexpected exception occurred when the flow was called: CWSXM0111E: Service runtime exception calling an import from mediation component ScmProxy in module ScmProxy_v1_0_0_WESBConnectivityProvider-eBiz_ae04: CWSXM0205E: An unexpected business logic exception occurred.: CWSXM3300E: Fail primitive 'FailFlow', component 'ScmProxy', module 'ScmProxy_v1_0_0_WESBConnectivityProvider-eBiz_ae04', interface '{http://www.ibm.com/websphere/sibx/ServiceGateway}ServiceGateway', operation 'requestResponse', raised a FailFlowException. The user-supplied error message is 'CWSXM7007E: The following error occurred while attempting to invoke the target service 'http://10.10.10.2:9080/ibm/scm/connectivity-provider/WESBConnectivityProvider/group-proxy/uxhr/sca/ScmProxySoap11Export/fyza' for proxy target 'rz8j' on group proxy 'ae04': javax.xml.ws.WebServiceException: java.net.ConnectException: Connection refused: no further information'

Does anyone have any idea on what might probably be causing this error? Thanks a lot.
Updated on 2011-05-30T19:07:58Z at 2011-05-30T19:07:58Z by WS7Newbie
  • DaveRushall
    DaveRushall
    1 Post

    Re: Can't get Federation in WSRR SFM add-on to work

    ‏2011-05-25T16:27:50Z  
    I don't know this specific scenario very well but it should work with the modifications you describe; using WebSphere Enterprise Service Bus in both domains and using static IP addresses in a trial deployment rather than fully qualified host names.

    The exception suggests that it's the link between the two proxies that is the problem; the proxy deployed in the consumer domain was unable to connect to the endpoint of the proxy in the provider domain.

    I'm assuming that http://10.10.10.2:9080/... is the host and port of the ESB assigned to the Retail domain, and that it is still running.

    Are there any associated messages appearing in the log of the ESB in the eBusiness domain?

    It's not a network problem is it? - can you ping 10.10.10.2 from the host of the eBusiness ESB server?

    Regards, Dave.
  • WS7Newbie
    WS7Newbie
    5 Posts

    Re: Can't get Federation in WSRR SFM add-on to work

    ‏2011-05-25T16:50:45Z  
    I don't know this specific scenario very well but it should work with the modifications you describe; using WebSphere Enterprise Service Bus in both domains and using static IP addresses in a trial deployment rather than fully qualified host names.

    The exception suggests that it's the link between the two proxies that is the problem; the proxy deployed in the consumer domain was unable to connect to the endpoint of the proxy in the provider domain.

    I'm assuming that http://10.10.10.2:9080/... is the host and port of the ESB assigned to the Retail domain, and that it is still running.

    Are there any associated messages appearing in the log of the ESB in the eBusiness domain?

    It's not a network problem is it? - can you ping 10.10.10.2 from the host of the eBusiness ESB server?

    Regards, Dave.
    Thanks Dave for your reply. No there is network connectivity. I'm not only able to ping but I have successfully swapped SSL trust certificates and configured the SFM console settings.

    The SOAP address http://10.10.10.2:9080... is the host and port for the WAS in the Retail Domain and all servers are up. It was automatically generated by the SFM Federation Management when I linked the 2 domains. I believe I saw it conduct some tests and linking procedures in coming up with the screenshot I attached in my previous post and there were no errors encountered.

    If the SOAP address is not automatically configured then I might have had some wrong configurations that led to it not pointing to the ESB and to the WAS instead? Any suggestions on what I should be checking to troubleshoot this?

    Many Thanks.
  • WS7Newbie
    WS7Newbie
    5 Posts

    Re: Can't get Federation in WSRR SFM add-on to work

    ‏2011-05-25T21:15:02Z  
    • WS7Newbie
    • ‏2011-05-25T16:50:45Z
    Thanks Dave for your reply. No there is network connectivity. I'm not only able to ping but I have successfully swapped SSL trust certificates and configured the SFM console settings.

    The SOAP address http://10.10.10.2:9080... is the host and port for the WAS in the Retail Domain and all servers are up. It was automatically generated by the SFM Federation Management when I linked the 2 domains. I believe I saw it conduct some tests and linking procedures in coming up with the screenshot I attached in my previous post and there were no errors encountered.

    If the SOAP address is not automatically configured then I might have had some wrong configurations that led to it not pointing to the ESB and to the WAS instead? Any suggestions on what I should be checking to troubleshoot this?

    Many Thanks.
    I reviewed my SCM Connectivity settings and I found out that port 9080 is wrong and should be 9082, so I changed and rebuilt the federation but now the new error I get is below

    Result
    exception: javax.xml.ws.WebServiceException: com.ibm.websphere.sca.ServiceRuntimeException: CWSXM0201E: Exception returned by mediation flow for component ScmProxy in module ScmProxy_v1_0_0_WESBConnectivityProvider_8giw: CWSXM3300E: Fail primitive 'FailFlow', component 'ScmProxy', module 'ScmProxy_v1_0_0_WESBConnectivityProvider_8giw', interface '{http://www.ibm.com/websphere/sibx/ServiceGateway}ServiceGateway', operation 'requestResponse', raised a FailFlowException. The user-supplied error message is 'CWSXM7004E: The proxy target 'bbo7' on group proxy '8giw' received a request other than via HTTP or HTTPS.': caused by: com.ibm.ws.sibx.scax.mediation.engine.FailFlowException: CWSXM3300E: Fail primitive 'FailFlow', component 'ScmProxy', module 'ScmProxy_v1_0_0_WESBConnectivityProvider_8giw', interface '{http://www.ibm.com/websphere/sibx/ServiceGateway}ServiceGateway', operation 'requestResponse', raised a FailFlowException. The user-supplied error message is 'CWSXM7004E: The proxy target 'bbo7' on group proxy '8giw' received a request other than via HTTP or HTTPS.'

    I checked my connectivity settings and they are in http or https. Does anyone have an idea of what this error means?

    Thanks.
  • WS7Newbie
    WS7Newbie
    5 Posts

    Re: Can't get Federation in WSRR SFM add-on to work

    ‏2011-05-30T19:07:58Z  
    • WS7Newbie
    • ‏2011-05-25T21:15:02Z
    I reviewed my SCM Connectivity settings and I found out that port 9080 is wrong and should be 9082, so I changed and rebuilt the federation but now the new error I get is below

    Result
    exception: javax.xml.ws.WebServiceException: com.ibm.websphere.sca.ServiceRuntimeException: CWSXM0201E: Exception returned by mediation flow for component ScmProxy in module ScmProxy_v1_0_0_WESBConnectivityProvider_8giw: CWSXM3300E: Fail primitive 'FailFlow', component 'ScmProxy', module 'ScmProxy_v1_0_0_WESBConnectivityProvider_8giw', interface '{http://www.ibm.com/websphere/sibx/ServiceGateway}ServiceGateway', operation 'requestResponse', raised a FailFlowException. The user-supplied error message is 'CWSXM7004E: The proxy target 'bbo7' on group proxy '8giw' received a request other than via HTTP or HTTPS.': caused by: com.ibm.ws.sibx.scax.mediation.engine.FailFlowException: CWSXM3300E: Fail primitive 'FailFlow', component 'ScmProxy', module 'ScmProxy_v1_0_0_WESBConnectivityProvider_8giw', interface '{http://www.ibm.com/websphere/sibx/ServiceGateway}ServiceGateway', operation 'requestResponse', raised a FailFlowException. The user-supplied error message is 'CWSXM7004E: The proxy target 'bbo7' on group proxy '8giw' received a request other than via HTTP or HTTPS.'

    I checked my connectivity settings and they are in http or https. Does anyone have an idea of what this error means?

    Thanks.
    Resolved the issue and got federation to work. The problem was that the WSDL files provided in the lab contained the wrong SOAP addresses. Had to update these addresses to reflect the ones used in my setup and it worked. Federation creation did not detect any problems because there was nothing wrong with my setup. The problem was in the original WSDL which was being referenced by the proxy WSDLs.

    The Redpaper given that it provided a detailed step-by-step instruction should have mentioned that this needed to be done. However it did not, so I had to trace the problem and figure out the solution by myself since the error messages that were coming out were not helpful either and no useful troubleshooting information was coming up with my online searches.