Issue with publishing schema as webservice using WCF-BasicHTTP two way channel

Here is my scenario:
I am trying to publish a Req-Resp schema which will be consumed by an orchestration and will return a response to me .When I invoke the WCF service end point it triggers the orchestration but the response never comes back to the SOAP UI. My orchestration
is completing and returning the response.
But in the SOAP UI I am instead getting : <Message>Root element is missing.
I am using WCF-BasicHTTP two way port. My app pool id under whcih the BT service is hosted is part of Administrator group on the server
My config file is as well updated with <trust level="Full" originUrl="" /> info.
What could be the reason for failure.

Hi,
Did you try checking your orchestration response xml against the schema definition WCF service is expecting to return.
Regards Pushpendra K Singh

Similar Messages

Error while posting to Webservice using WCF-BasicHttp adapter

Hi,
I am getting the below exception when i am posting a request to a .asmx webservice using the Wcf-BasicHttp adapter.
I am able to call the same service with the SOAP adapter successfully. Could you please let me know any resolutions for the same.
The adapter failed to transmit message going to send port "MySendPort" with URL "http://myservice.com/Web.Services/service1.asmx". It will be retransmitted after the retry interval specified for this Send Port. Details:"System.ServiceModel.ProtocolException:
The content type text/html; charset=utf-8 of the response message does not match the content type of the binding (text/xml; charset=utf-8). If using a custom encoder, be sure that the IsContentTypeSupported method is implemented properly. The first 1024 bytes
of the response were: '
<html>
    <head><link rel="alternate" type="text/xml" href="/Web.Services/Service1.asmx?disco" />
    <style type="text/css">
       BODY { color: #000000; background-color: white; font-family: Verdana; margin-left: 0px; margin-top: 0px; }
       #content { margin-left: 30px; font-size: .70em; padding-bottom: 2em; }
       A:link { color: #336699; font-weight: bold; text-decoration: underline; }
       A:visited { color: #6699cc; font-weight: bold; text-decoration: underline; }
       A:active { color: #336699; font-weight: bold; text-decoration: underline; }
       A:hover { color: cc3300; font-weight: bold; text-decoration: underline; }
       P { color: #000000; margin-top: 0px; margin-bottom: 12px; font-family: Verdana; }
       pre { background-color: #e5e5cc; padding: 5px; font-family: Courier New; font-size: x-small; margin-top: -5px; border: 1px #f0f0e0 solid; }
       td { color: #000000; font-family: Verdana; font-size: .7em; }
       h2 { font-size: 1.5em; font-weight: bold; margin-top: 25px; margin-bottom: 10px; border-to'.
Server stack trace:
   at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannel.SendAsyncResult.End(SendAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object[] outs, IAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannel.EndRequest(IAsyncResult result)
Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at System.ServiceModel.Channels.IRequestChannel.EndRequest(IAsyncResult result)
   at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfClient`2.RequestCallback(IAsyncResult result)".
Regards,
Ujjwal
-Ujjwal

Where does the HTML indicate that the Service is not running??
The error message " The content type text/html; charset=utf-8 of the response message does not match
the content type of the binding (text/xml; charset=utf-8)" points to a bug in the WCF-BasicHttp described here:
http://social.msdn.microsoft.com/Forums/en-US/11796bf5-ba6a-4878-977e-5c854642f67c/the-content-type-textxml-charsetiso88591-of-the-response-message-does-not-match-the-content?forum=biztalkgeneral
Although not 100% the same, the conclusion here was to still use the old Adapter :-(
Morten la Cour

My MacBook Pro 13" (2012) is running Windows 7 on Bootcamp and there is an issue with the headset I'm using.

My MacBook Pro 13" (2012) is running Windows 7 on Bootcamp and there is an issue with the headset I'm using. I use a cheap Logitech Stereo Headset H130, but since there is only on audio plugin on the computer, I purchased a 3.5 mm 4-pin smartphone audio adapter thingy. That allowed me to put both my the sound coming to my headset & the microphone on my headset onto one wire. Everything worked wonderfully when running the Mac OS since they probably have support for that kind of stuff. The problem is though that once I try to use the same method in Windows 7, the OS doesn't recognize my headset microphone at all, but, instead when recording my voice decides to use the built-in mac microphone. Using this adapter still allows me to hear from my headset, but not use the microphone and that becomes a problem. It might be so that Windows 7 doesn't have support\drivers for that... How should I continue from here on out? Any advice?

From what I have read from others on here you may be out of luck. You would need the appropriate Windows drivers for the Cirrus chip in the Mac and no one has been able to successfully locate them. Apple wouldn't support this since Windows is an optional install.
Sorry to bring the bad news.

Issue with PR conversion to PO using ME59 withqty of similar line items

Hi All,
I'm having an issue with PR conversion to PO using ME59
I have a PR with the following line items with all same details except quantity
ex 1
Mat Qty Unit Plant   St Loc
M1   1    EA   P1      S1
M1   29   EA   P1      S1
The PR brings in the Unit automatically
EA is Base Unit Of Measure -Material Master
BT is Order Unit           -Material Master
Conversion
30 EA = 1BT
When i convert this PR to PO using ME59N then i see 2 lines items
M1   1   BT
M2   1   BT
Its doubling the qty (2 BT = 60 EA)
ex 2
Mat Qty Unit Plant   St Loc
M1   1    EA   P1      S1
M1   2    EA   P1      S1
M1   27   EA   P1      S1
The PR brings in the Unit automatically
EA is Base Unit Of Measure -Material Master
BT is Order Unit           -Material Master
Conversion
30 EA = 1BT
When i convert this PR to PO using ME59N then i see 2 lines items
M1   1   BT
M1   1   BT
M1   1   BT
Its 3 times no
PR Qty = 30 EA
PO qty = 3 BT = 90 EA
I guess during conversion to PO
It sees PR Line item 1 and looks for another line items with similar fields ( in our case it sees line 2 in ex 1 and 2 and 3 in ex 2)
i adds the qty 1 and 29 in ex1 and converts the total 30 each to 1 BT and when it moves to 2 line it see item1 and again creates 1BT but the line item 2 was already considered and it should be ignored
Similarly if you see ex2 then it creates 3 limes with 1 BT each
Let me know how to resolve this issue
Thanks

As for std SAP ME59N - make sure there is not rounding value is activated in the Material master as well as info record
If this is not the case than check any custom code is activated for ME59N
becuase generally in many compnay when they use ME59n they don't want the same material from diff PR to create the diff line item in the PO so using the custom logic in the user exist they trick the code
it might be the case for you where you have issue.

Issue with SharePoint foundation 2010 to use Claims Based Auth with Certificate authentication method with ADFS 2.0

I would love some help with this issue. I have configured my SharePoint foundation 2010 site to use Claims Based Auth with Certificate authentication method with ADFS 2.0 I have a test account set up with lab.acme.com to use the ACS.
When I log into my site using Windows Auth, everything is great. However when I log in and select my ACS token issuer, I get sent, to the logon page of the ADFS, after selected the ADFS method. My browser prompt me which Certificate identity I want
to use to log in and after 3-5 second
and return me the logon page with error message “Authentication failed”
I base my setup on the technet article
http://blogs.technet.com/b/speschka/archive/2010/07/30/configuring-sharepoint-2010-and-adfs-v2-end-to-end.aspx
I validated than all my certificate are valid and able to retrieve the crl
I got in eventlog id 300
The Federation Service failed to issue a token as a result of an error during processing of the WS-Trust request.
Request type: http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Issue
Additional Data
Exception details:
Microsoft.IdentityModel.SecurityTokenService.FailedAuthenticationException: MSIS3019: Authentication failed. ---> System.IdentityModel.Tokens.SecurityTokenValidationException:
ID4070: The X.509 certificate 'CN=Me, OU=People, O=Acme., C=COM' chain building failed. The certificate that was used has a trust chain that cannot be verified. Replace the certificate or change the certificateValidationMode. 'A certification chain processed
correctly, but one of the CA certificates is not trusted by the policy provider.
at Microsoft.IdentityModel.X509CertificateChain.Build(X509Certificate2 certificate)
at Microsoft.IdentityModel.Tokens.X509NTAuthChainTrustValidator.Validate(X509Certificate2 certificate)
at Microsoft.IdentityModel.Tokens.X509SecurityTokenHandler.ValidateToken(SecurityToken token)
at Microsoft.IdentityModel.Tokens.SecurityTokenElement.GetSubject()
at Microsoft.IdentityServer.Service.SecurityTokenService.MSISSecurityTokenService.GetOnBehalfOfPrincipal(RequestSecurityToken request, IClaimsPrincipal callerPrincipal)
--- End of inner exception stack trace ---
at Microsoft.IdentityServer.Service.SecurityTokenService.MSISSecurityTokenService.GetOnBehalfOfPrincipal(RequestSecurityToken request, IClaimsPrincipal callerPrincipal)
at Microsoft.IdentityServer.Service.SecurityTokenService.MSISSecurityTokenService.BeginGetScope(IClaimsPrincipal principal, RequestSecurityToken request, AsyncCallback callback, Object state)
at Microsoft.IdentityModel.SecurityTokenService.SecurityTokenService.BeginIssue(IClaimsPrincipal principal, RequestSecurityToken request, AsyncCallback callback, Object state)
at Microsoft.IdentityModel.Protocols.WSTrust.WSTrustServiceContract.DispatchRequestAsyncResult..ctor(DispatchContext dispatchContext, AsyncCallback asyncCallback, Object asyncState)
at Microsoft.IdentityModel.Protocols.WSTrust.WSTrustServiceContract.BeginDispatchRequest(DispatchContext dispatchContext, AsyncCallback asyncCallback, Object asyncState)
at Microsoft.IdentityModel.Protocols.WSTrust.WSTrustServiceContract.ProcessCoreAsyncResult..ctor(WSTrustServiceContract contract, DispatchContext dispatchContext, MessageVersion messageVersion, WSTrustResponseSerializer responseSerializer, WSTrustSerializationContext
serializationContext, AsyncCallback asyncCallback, Object asyncState)
at Microsoft.IdentityModel.Protocols.WSTrust.WSTrustServiceContract.BeginProcessCore(Message requestMessage, WSTrustRequestSerializer requestSerializer, WSTrustResponseSerializer responseSerializer, String requestAction, String responseAction, String
trustNamespace, AsyncCallback callback, Object state)
System.IdentityModel.Tokens.SecurityTokenValidationException: ID4070: The X.509 certificate 'CN=Me, OU=People, O=acme., C=com' chain building
failed. The certificate that was used has a trust chain that cannot be verified. Replace the certificate or change the certificateValidationMode. 'A certification chain processed correctly, but one of the CA certificates is not trusted by the policy provider.
at Microsoft.IdentityModel.X509CertificateChain.Build(X509Certificate2 certificate)
at Microsoft.IdentityModel.Tokens.X509NTAuthChainTrustValidator.Validate(X509Certificate2 certificate)
at Microsoft.IdentityModel.Tokens.X509SecurityTokenHandler.ValidateToken(SecurityToken token)
at Microsoft.IdentityModel.Tokens.SecurityTokenElement.GetSubject()
at Microsoft.IdentityServer.Service.SecurityTokenService.MSISSecurityTokenService.GetOnBehalfOfPrincipal(RequestSecurityToken request, IClaimsPrincipal callerPrincipal)
thx
Stef71

This is perfectly correct on my case I was not adding the root properly you must add the CA and the ADFS as well, which is twice you can see below my results.
on my case was :
PS C:\Users\administrator.domain> $root = New-Object System.Security.Cryptography.X509Certificates.X509Certificate2("C:\
cer\SP2K10\ad0001.cer")
PS C:\Users\administrator.domain> New-SPTrustedRootAuthority -Name "domain.ad0001" -Certificate $root
Certificate : [Subject]
CN=domain.AD0001CA, DC=domain, DC=com
[Issuer]
CN=domain.AD0001CA, DC=portal, DC=com
[Serial Number]
blablabla
[Not Before]
22/07/2014 11:32:05
[Not After]
22/07/2024 11:42:00
[Thumbprint]
blablabla
Name : domain.ad0001
TypeName : Microsoft.SharePoint.Administration.SPTrustedRootAuthority
DisplayName : domain.ad0001
Id : blablabla
Status : Online
Parent : SPTrustedRootAuthorityManager
Version : 17164
Properties : {}
Farm : SPFarm Name=SharePoint_Config
UpgradedPersistedProperties : {}
PS C:\Users\administrator.domain> $cert = New-Object System.Security.Cryptography.X509Certificates.X509Certificate2("C:\
cer\SP2K10\ADFS_Signing.cer")
PS C:\Users\administrator.domain> New-SPTrustedRootAuthority -Name "Token Signing Cert" -Certificate $cert
Certificate : [Subject]
CN=ADFS Signing - adfs.domain
[Issuer]
CN=ADFS Signing - adfs.domain
[Serial Number]
blablabla
[Not Before]
23/07/2014 07:14:03
[Not After]
23/07/2015 07:14:03
[Thumbprint]
blablabla
Name : Token Signing Cert
TypeName : Microsoft.SharePoint.Administration.SPTrustedRootAuthority
DisplayName : Token Signing Cert
Id : blablabla
Status : Online
Parent : SPTrustedRootAuthorityManager
Version : 17184
Properties : {}
Farm : SPFarm Name=SharePoint_Config
UpgradedPersistedProperties : {}
PS C:\Users\administrator.PORTAL>

Issue with Opportunity schema contained in Opportunity.wsdl and Integration

There is Opportunity XML schema object defined for Siebel web-service with URI “urn:/crmondemand/xml/opportunity” in opportunity.wsdl and opportunity.xsd contained in integrationevent.zip. Please find attached the schema files.
If you check the diff, the opportunity schema is different, which is actually a conflict from Siebel side since it is the same object identified by URI “urn:/crmondemand/xml/opportunity”. Can we get some information about the discrepancy from Siebel OD team?
Following compiler error comes for the BPEL process, where both Opportunity wsdl and integration event being used:
Error:
[Error ORABPEL-10903]: failed to read wsdl
[Description]: in "bpel.xml", Global Type declaration/definition of name '{urn:/crmondemand/xml/opportunity}Opportunity' are duplicated at the following locations:
file:/C:/Bhavnesh/Work/SiebelPoll/SourceCode/SiebelPoll/JDSU_SiebelToODSOpportunityTransfer/bpel/opportunity.wsdl [line#: 89]
file:/C:/Bhavnesh/Work/SiebelPoll/SourceCode/SiebelPoll/JDSU_SiebelToODSOpportunityTransfer/bpel/opportunity.xsd [line#: 12]
There are at least two of them looking different:
file:/C:/Bhavnesh/Work/SiebelPoll/SourceCode/SiebelPoll/JDSU_SiebelToODSOpportunityTransfer/bpel/opportunity.wsdl [difference starting at line#:635]
file:/C:/Bhavnesh/Work/SiebelPoll/SourceCode/SiebelPoll/JDSU_SiebelToODSOpportunityTransfer/bpel/opportunity.xsd [difference starting at line#:558]
Global Type declaration/definition of name '{urn:/crmondemand/xml/opportunity}Team' are duplicated at the following locations:
file:/C:/Bhavnesh/Work/SiebelPoll/SourceCode/SiebelPoll/JDSU_SiebelToODSOpportunityTransfer/bpel/opportunity.wsdl [line#: 2602]
file:/C:/Bhavnesh/Work/SiebelPoll/SourceCode/SiebelPoll/JDSU_SiebelToODSOpportunityTransfer/bpel/opportunity.xsd [line#: 2524]
There are at least two of them looking different:
file:/C:/Bhavnesh/Work/SiebelPoll/SourceCode/SiebelPoll/JDSU_SiebelToODSOpportunityTransfer/bpel/opportunity.wsdl [difference starting at line#:2602]
file:/C:/Bhavnesh/Work/SiebelPoll/SourceCode/SiebelPoll/JDSU_SiebelToODSOpportunityTransfer/bpel/opportunity.xsd [difference starting at line#:2524]
[Potential fix]: If your site has a proxy server, then you may need to configure your BPEL Server, designer and browser with your proxy server configuration settings (see tech note on http://otn.oracle.com/bpel for instructions).
Following is the difference between two schema:
New line in opportunity.wsdl
<xsd:element name="ListOfOpportunityContactRole" maxOccurs="1" minOccurs="0" type="xsdLocal1:ListOfOpportunityContactRole"></xsd:element>
Difference between the sequence of elements in both schema:
<xsd:complexType name="Team"><xsd:sequence><xsd:element name="OpportunityAccessId" maxOccurs="1" minOccurs="0" type="xsdLocal1:string30"></xsd:element>
<xsd:element name="OpportunityTeamId" maxOccurs="1" minOccurs="0" type="xsd:string"></xsd:element>
Thanks and regards,
Bhavnesh Patel.
Edited by: bhavnesh_p on Oct 9, 2008 1:24 PM

Hello Bhavnesh,
we just got into the same issue with the differing Opportunity-XSD/WSDL you have mentioned in your posting.
Following is the difference between two schema:
New line in opportunity.wsdl
<xsd:element name="ListOfOpportunityContactRole" maxOccurs="1" minOccurs="0" type="xsdLocal1:ListOfOpportunityContactRole"></xsd:element>
Difference between the sequence of elements in both schema:
<xsd:complexType name="Team"><xsd:sequence><xsd:element name="OpportunityAccessId" maxOccurs="1" minOccurs="0" type="xsdLocal1:string30"></xsd:element>
<xsd:element name="OpportunityTeamId" maxOccurs="1" minOccurs="0" type="xsd:string"></xsd:element>Did you get any update on this problem?
Thanks in adavance & Best regards..
Andre

Performance issues with respect scheme registration,select & insert query

I am facing performance issues with respect to schema registration,Select & insert query towards 10.2.0.3 version.It is taking around 45 minutes to register schema and it is taking around 5 min to insert a single document into xml db where as it was taking less than min to insert a single document into xml db of 9.2.0.6 version.Would like to know the issue and solution to resolve this issue.Please help me out on this as it is very urgent for me

Since it appears that this is an XML DB specific question, you're probably better off posting in the XML DB. The folks over there have much more experience with the ins and outs of that particular product.
Justin

Issues with publishing my iWeb site to .MAC - Progress bar freezes at 100%

Well, as topic says, i'm having troubles publishing my iWeb site to .MAC now since upgrading to '08. The progress bar reaches full circle, but then nothing. Left it uploading to .Mac for well over 2 hours one time while out of the house...nada. Sometimes i get an error message, sometimes not and have to close iWeb while it's still publishing.
Any feedback regarding this?
Thanks in advance.
/Rich

Update: After 36 hours, I have successfully managed to upload my entire website via the "Publish All to .Mac" option. I now have blue indicators on the left side of my iWeb program in place of those pesky red ones. How did I do it? Well, I'm not sure. But on my last attempt I looked at the problem from a different perspective, so I took an alternate approach. I had a feeling that I was experiencing a network timeout issue caused by a 3rd party software, so I created a Whitelist entry on my website filtering software that allows unlimited access to "idisk.mac.com";; and "web.mac.com";; domains. I've got two kids at home, so I'm running the free OpenDNS Dashboard service on my network which provides content filtering (blocks adult site, phishing site, etc..). I started using this service two weeks ago. My last website update was a week before that. I figured I had nothing to loose by trying. To my surprise, it worked. Now, it took almost two hours to publish, of which the pie indicator was in the "filled" position for a nerve racking hour. To reconfirm, I then made a minor change to one of the pages on my website and re-published. This time using the "Publish to .Mac" option in place of the ALL option and once again it worked. It took less than 5 minutes. Now, I'm not sure if this is a coincidence, maybe Apple fixed the problem, or maybe my website filtering service was causing some type of time out issue all along?? Don't know.. But at least for now, I'm a happy camper since I have my site up.

Sateillite A200-1A9: Issue with sending/receiving E-mail using Windows Mail

Using Windows mail I have to close/open the programme to be able to send mails, they get stuck in the Outbox. By closing and reopening the programme the mail gets sent. Also the Blue figure 1 in brackets showning 1 unread mail in the Outbox is there all the time although there is no mails read or unread in the Outbox
Not a server problem as all mails are going/receiving fine on my desktop.
Pressing send and receive button does not help. although some of the time it will receive mails when pressing send/receive but will not send them
I do have Norton Internet security 2007 and am getting fed up with the continuing problems that this seems to cause over the period 2004-7.
Is there an issue with the Windows mail programme running with Vista that is known

I think I have found a solution
Please check this:
Windows Mail will not Send or Receive mails
http://support.toshiba-tro.de/kb0/TSB7701X30005R01.htm
It seems that the update of Software Desktop SMS to the newest version will help to sort out this problem.

Issues with a Credit Card Machine using a VG202

Has anyone run into any issues with using CC machines with using SCCP on a VG202?
Setup: 2 CC Machines--> VG202 --> connecting to Call Manager 8.6 using DHCP. Both of my CC machines work fine doing a normal CC transaction, but at the end of the day the client runs a batch report on the cc machine but the cc machine will time out after 1 min. The Batch report usually takes about 3 to 4 mins to complete.

Thank you!
Adding "network-clock-select 1 T1 0/0/0" to the config resolved the issue. No more slips and credit card machine runs smoothly now.
I very much appreciate your assistance.

Has anybody else been having issues with their home button after using assistive touch for a little while?

Me and my brother have been messing with Assistive Touch on and off since iOS 5 canme out. We been noticing that when we actually move to use the home button, sometimes it doesnt respond. Though I'm all for thinking my home button my be on the fritz, it wouldnt explain how mine and my brother suddenly have issues with our home buttons at the same time. Both of us had a time where the home button didnt respond at all. and its been intermittent ever since. Anybody that has an answer or another case like this I' d like some information

Reset Home button steps:
(1) Tap Settings App, when it is open:
(2) Hold Power button until "slide to power off" bar appears.
(3) Don't slide it, release power button.
(4) Gently, continuously press Home button for few seconds until home screen appears.
(5) Done.
If this does not help, further points to Hardware Problem.

Service Instance remains active when calling Web Service using WCF-BasicHttp binding

I am trying to call a web service using ESB ToolKit using a dynamic send port. The message went through all the pipeline components successfully. However, after the message is picked up by the WCF adapter, the service instance remains in "Active"
status, and then eventually it dehydrates itself. There's no error in the event log at all. Have anyone seen this problem before? If so, what is the solution?
I tried using a static send port with exactly the same configuration and the message reaches the web service successfully and got the response back.
Please note the web service is RPC-Style web service, not sure if it makes a difference.
Here is the configuration for the static send port
<Address>http://myserver:8088/mockLoadDataBinding</Address><TransportType Name="WCF-BasicHttp" Capabilities="899" ConfigurationClsid="467c1a52-373f-4f09-9008-27af6b985f14" />
<TransportTypeData>
<CustomProps>
<InboundNodeEncoding vt="8">String</InboundNodeEncoding>
<MessageEncoding vt="8">Text</MessageEncoding>
<ServiceCertificate vt="8" />
<InboundBodyPathExpression vt="8">//*[local-name()='return']/node() | //*[local-name()='SecurityException']</InboundBodyPathExpression>
<OutboundBodyLocation vt="8">UseTemplate</OutboundBodyLocation>
<StaticAction vt="8" />
<InboundBodyLocation vt="8">UseBodyPath</InboundBodyLocation>
<ProxyAddress vt="8" />
<MaxReceivedMessageSize vt="3">65536</MaxReceivedMessageSize>
<ClientCertificate vt="8" />
<AlgorithmSuite vt="8">Basic256</AlgorithmSuite>
<ProxyUserName vt="8" />
<OutboundXmlTemplate vt="8"><web:loadData soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:web="http://www.company.com/webservices" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><input xsi:type="xsd:string"><bts-msg-body xmlns="http://www.microsoft.com/schemas/bts2007" encoding="string"/></input></web:loadData></OutboundXmlTemplate>
<TextEncoding vt="8">utf-8</TextEncoding>
<PropagateFaultMessage vt="11">-1</PropagateFaultMessage>
<SecurityMode vt="8">None</SecurityMode>
<ProxyToUse vt="8">Default</ProxyToUse>
<TransportClientCredentialType vt="8">None</TransportClientCredentialType>
<OpenTimeout vt="8">00:01:00</OpenTimeout>
<UseAcsAuthentication vt="11">0</UseAcsAuthentication>
<MessageClientCredentialType vt="8">UserName</MessageClientCredentialType>
<UseSSO vt="11">0</UseSSO>
<CloseTimeout vt="8">00:01:00</CloseTimeout>
<SendTimeout vt="8">00:01:00</SendTimeout>
</CustomProps>
</TransportTypeData>
here is the configuration for the dynamic send port (using BRE Resolver)
Set Endpoint Outbound TransportType to WCF-BasicHttp
Set Endpoint Outbound TransportLocation to http://myserver:8088/mockLoadDataBinding
Set Endpoint Message Exchange Pattern to Solicit-Response
Set EndPoint WCF Action to <empty string>
Set Endpoint Config to InboundNodeEncoding=String&MessageEncoding=Text&InboundBodyPathExpression=//*[local-name()='return']/node() | //*[local-name()='SecurityException']&OutboundBodyLocation=UseTemplate&StaticAction=&InboundBodyLocation=UseBodyPath&MaxReceivedMessageSize=65536&AlgorithmSuite=Basic256&OutboundXmlTemplate=<web:loadData
soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:web="http://www.company.com/webservices" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><input xsi:type="xsd:string"><bts-msg-body xmlns="http://www.microsoft.com/schemas/bts2007"
encoding="string"/></input></web:loadData>&TextEncoding=utf-8&PropagateFaultMessage vt="11">-1&SecurityMode=None&ProxyToUse=Default&TransportClientCredentialType=None&OpenTimeout=00:01:00&UseAcsAuthentication=False&MessageClientCredentialType=UserName&UseSSO=False&CloseTimeout=00:01:00&SendTimeout=00:01:00
Set Endpoint Target Namespace to
http://www.company.com/webservices

Thanks Birdsven,
I updated the Resolver policy to as follows, and still I am getting the same result.
<then>
<function>
<vocabularylink uri="95dced57-5e9b-4dbe-9cd8-4b166853dd8a" element="4ad331d0-820c-41cb-a98e-7e1f5a9d5360" />
<classmember member="set_TransportType" sideeffects="true">
<classref ref="Resolution" />
<argument>
<constant>
<string>WCF-BasicHttp</string>
</constant>
</argument>
</classmember>
</function>
<function>
<vocabularylink uri="95dced57-5e9b-4dbe-9cd8-4b166853dd8a" element="20652bdd-c1f2-4b75-9e6b-7e20af98e66d" />
<classmember member="set_MessageExchangePattern" sideeffects="true">
<classref ref="Resolution" />
<argument>
<constant>
<string>Solicit-Response</string>
</constant>
</argument>
</classmember>
</function>
<function>
<vocabularylink uri="95dced57-5e9b-4dbe-9cd8-4b166853dd8a" element="9357b8ea-3663-4625-9681-a2fc2f423911" />
<classmember member="set_TransportLocation" sideeffects="true">
<classref ref="Resolution" />
<argument>
<constant>
<string>http://myservice.com:8089/loadDataService</string>
</constant>
</argument>
</classmember>
</function>
<function>
<vocabularylink uri="95dced57-5e9b-4dbe-9cd8-4b166853dd8a" element="9c97e7a0-d119-4b0d-8e39-2b281ae6ef8d" />
<classmember member="set_Action" sideeffects="true">
<classref ref="Resolution" />
<argument>
<constant>
<string>{loadData}</string>
</constant>
</argument>
</classmember>
</function>
<function>
<vocabularylink uri="95dced57-5e9b-4dbe-9cd8-4b166853dd8a" element="2829f1b7-09c0-4396-b82e-23fd65d8439c" />
<classmember member="set_EndpointConfig" sideeffects="true">
<classref ref="Resolution" />
<argument>
<constant>
<string>InboundNodeEncoding=String&MessageEncoding=Text&ServiceCertificate=&InboundBodyPathExpression=//*[local-name()='return']/node() | //*[local-name()='SecurityException']&OutboundBodyLocation=UseTemplate&StaticAction=&InboundBodyLocation=UseBodyPath&ProxyAddress=&MaxReceivedMessageSize=65536&ClientCertificate=&AlgorithmSuite=Basic256&ProxyUserName=&OutboundXmlTemplate=<web:loadData soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:web="http://www.mycompany.com/webservices" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><input xsi:type="xsd:string"><bts-msg-body xmlns="http://www.microsoft.com/schemas/bts2007" encoding="string"/></input></web:loadData>&TextEncoding=utf-8&PropagateFaultMessage=True&SecurityMode=None&ProxyToUse=Default&TransportClientCredentialType=None&OpenTimeout=00:01:00&UseAcsAuthentication=False&MessageClientCredentialType=UserName&UseSSO=False&CloseTimeout=00:01:00&SendTimeout=00:01:00</string>
</constant>
</argument>
</classmember>
</function>
<function>
<vocabularylink uri="95dced57-5e9b-4dbe-9cd8-4b166853dd8a" element="54624479-caea-4228-86b9-fbe188a8c64d" />
<classmember member="set_TargetNamespace" sideeffects="true">
<classref ref="Resolution" />
<argument>
<constant>
<string>http://www.mycompany.com/webservices</string>
</constant>
</argument>
</classmember>
</function>
</then>

Red Blue issue with published DeskI Report in InfoView

Hi everyone,
i'm expieriencing a strange behaviour with my published DeskI Reports.
I'm using logos in my report and they work just fine... in my full client. As soon as I publish them to InfoView and open them up in the browser, then somehow the color red and blue interchange. Red becomes blue and vice versa...
My System consists of:
BOE R 3.1 SP2
Win Server 2008
DeskI and WebI
Has anyone expirienced the same issues?
Thanks and kr,
Nils

Hi Stratos,
so far everything is just fine. Hope you are doing great too.
my IE version is: 7.0.5730.13
Tomcat version: 5.5.20
If I click on the logos in InfoView, nothing happens.
I tested 3 different ways to implement them:
1) via link; pictures shows up, but again with the red blue issue
2) as an object; pictures shows up; also w/ the red blue issue
3) inserted a cell, and pasted the picture in it, pictures shows up; also w/ the red blue issue
The strange thing is, that this issue only appears in the browser.
Thanks,
Nils

Issue with publishing an application that has been updated (application with multiple versions)

We are using App-V 5.0 SP1.
I have a package that will need to get patched whenever new security updates are released. The first version of the application always works fine, but when I update the application and re-publish it, a normal user is unable to pull down the new version.
When this occurs I am able to get everything going by logging into the server with an admin account and performing a sync (Get-AppvPublishingServer | Sync-AppvPublishingServer; Get-AppvClientApplication"). What is it about applications that
have been updated that would cause this behavior?
The issue is similar to what the hotfix below addresses, but since we are on 5.0 SP1 I am unsure if this applies still.
http://support.microsoft.com/kb/2799153?wa=wsignin1.0
You publish a Version 1 package of an application on a server
You log on to the client by using a user account
You confirm that the Version 1 package of Application Virtualization 5.0 is synched, and then you log off the client.
You publish a Version 2 package of an application, and then you remove the Version 1 application
You log on to the client by using a user account.
The application is not published to the user

Hello,
Have you verified the event-logs if the attempt to publish the package is visible there (successful or failed)?
Nicke Källén | The Knack| Twitter:
@Znackattack

Bpelc issues with WSDL schema definition

Hi,
I have been attempting to deploy a relative simple BPEL example, developed using the BPEL Designer Eclipse plugin and deployed on BPEL Process Manager.
The BPEL consists of receiving a SOAP message, copying variables using assign from the input message to a message defined in an external WSDL, invoking that WSDL's service and copying the results of that service into the output message.
To design the external service, I developed a simple Java class in Apache Axis and used the Java2WSDL tool to create all the interfaces. I then copied that WSDL to the BPEL designer and started to design the BPEL.
The problem is to do with the definition of messages within the WSDL, the following snippet is from the WSDL generated in Apache Axis:
<wsdl:types>
<schema xmlns="http://www.w3.org/2001/XMLSchema"
     targetNamespace="http://mdsuk.com/wsdl/example/PSP1">
<import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
<complexType name="OutputCT">
<sequence>
<element name="message" nillable="true" type="xsd:string"/>
<element name="paymentReference" nillable="true" type="xsd:string"/>
<element name="success" nillable="true" type="xsd:boolean"/>
</sequence>
</complexType>
</schema>
</wsdl:types>
I then tried to create the <assign> statement for the External Service Message -> BPEL Output Message using BPEL Designer using the visual editor, it generated the following code:
<assign name="assign-2">
<copy>
     <from variable="pspOutput" part="outputCT" query="/message"></from>
     <to variable="output" part="payload" query="/tns:OrderTestResponse/tns:result"/>
</copy>
<copy>
     <from variable="pspOutput" part="outputCT" query="/success"></from>
     <to variable="output" part="payload" query="/tns:OrderTestResponse/tns:success"/>
</copy>
</assign>
Trying to compile this generated code resulted in:
[bpelc] [Error ORABPEL-10057]: invalid query
[bpelc] [Description]: in line 94 of "D:\EclipseWorkspace\OrderTest\OrderTest.bpel", query "/message" is invalid, because step 'message' is not valid..
[bpelc] [Potential fix]: Check the XML schema and make sure your query string is valid.
[bpelc]
[bpelc] [Error ORABPEL-10057]: invalid query
[bpelc] [Description]: in line 98 of "D:\EclipseWorkspace\OrderTest\OrderTest.bpel", query "/success" is invalid, because step 'success' is not valid..
[bpelc] [Potential fix]: Check the XML schema and make sure your query string is valid.
So, the generated code from BPEL Designer was failing to compile. This resulted in a long check of the code, finally I realised that it expected the inputCT variable to be present in the XPath, so I manually changed the code to
<assign name="assign-2">
<copy>
     <from variable="pspOutput" part="outputCT" query="/outputCT/message"></from>
     <to variable="output" part="payload" query="/tns:OrderTestResponse/tns:result"/>
</copy>
<copy>
     <from variable="pspOutput" part="outputCT" query="/outputCT/success"></from>
     <to variable="output" part="payload" query="/tns:OrderTestResponse/tns:success"/>
</copy>
</assign>
This allowed to code to compile, so I deployed the BPEL to the Process Manager, and invoked a query using the Web Interface.
The BPEL started up fine, it invoked my external Axis Web Service, Axis produced the output (visible via debugging) however Process Manager tried to process the output, it crashed with the following exception:
06/01/19 16:29:11 com.oracle.bpel.client.BPELFault: faultName: {{http://schemas.xmlsoap.org/ws/2003/03/business-process/}selectionFailure}
messageType: {null}
parts: {{summary=<summary>empty variable/expression result.
xpath variable/expression expression "/outputCT/message" is empty at line 94, when attempting reading/copying it.
Please make sure the variable/expression result "/outputCT/message" is not empty.
</summary>}}
So, the compiled BPEL code, which had the WSDL schema to compare against was failing during execution, I inspected the output from the Axis Web Service, which was:
<?xml version="1.0" encoding="utf-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<processPaymentResponse xmlns="http://mdsuk.com/wsdl/example/PSP1">
<outputCT xmlns="">
<ns1:message xmlns:ns1="http://mdsuk.com/wsdl/example/PSP1">Payment Succesful</ns1:message>
<ns2:paymentReference xmlns:ns2="http://mdsuk.com/wsdl/example/PSP1">1137688175137</ns2:paymentReference>
<ns3:success xmlns:ns3="http://mdsuk.com/wsdl/example/PSP1">true</ns3:success>
</outputCT>
</processPaymentResponse>
</soapenv:Body>
</soapenv:Envelope>
The key difference was that the message / paymentReference and success attributes were prefixed with the namespace "http://mdsuk.com/wsdl/example/PSP1" , this makes sense as the schema has the attribute targetNamespace="http://mdsuk.com/wsdl/example/PSP1".
However, when I tried to modify the BPEL to read:
<assign name="assign-2">
<copy>
     <from variable="pspOutput" part="outputCT" query="/outputCT/nsxml1:message"></from>
     <to variable="output" part="payload" query="/tns:OrderTestResponse/tns:result"/>
</copy>
<copy>
     <from variable="pspOutput" part="outputCT" query="/outputCT/nsxml1:success"></from>
     <to variable="output" part="payload" query="/tns:OrderTestResponse/tns:success"/>
</copy>
</assign>
It complained:
[bpelc] [Error ORABPEL-10057]: invalid query
[bpelc] [Description]: in line 94 of "D:\EclipseWorkspace\OrderTest\OrderTest.bpel", query "/outputCT/nsxml1:message" is invalid, because step 'nsxml1:message' is not valid..
[bpelc] [Potential fix]: Check the XML schema and make sure your query string is valid.
[bpelc]
[bpelc] [Error ORABPEL-10057]: invalid query
[bpelc] [Description]: in line 98 of "D:\EclipseWorkspace\OrderTest\OrderTest.bpel", query "/outputCT/nsxml1:sucess" is invalid, because step 'nsxml1:sucess' is not valid..
[bpelc] [Potential fix]: Check the XML schema and make sure your query string is valid.
[bpelc] .
So, the BPEL would not validate against the WSDL schema that was being produced, I read up on the W3 Schema specification, and found that the schema can take the attribute elementFormDefault - this attribute takes the values 'qualified' or 'unqualified'. If qualified, then it explicitly states that all children elements should be beloning to the namespace of this element.
So, I changed the schema to read:
<wsdl:types>
<schema xmlns="http://www.w3.org/2001/XMLSchema"
     targetNamespace="http://mdsuk.com/wsdl/example/PSP1"
     elementFormDefault="qualified">
<import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
<complexType name="OutputCT">
<sequence>
<element name="message" nillable="true" type="xsd:string"/>
<element name="paymentReference" nillable="true" type="xsd:string"/>
<element name="success" nillable="true" type="xsd:boolean"/>
</sequence>
</complexType>
</schema>
</wsdl:types>
The BPEL compiled and ran succesfully.
However, the problem/issue here is, Oracle bpelc assumed that if the elementFormDefault attribute was missing from the schema definition, it defaulted to unqualified, even with the targetNamespace attribute present.
Axis and <oXygen/> XML Editors, in which I tested the WSDL code, assumed that if the elementFormDefault attribute was missing, it defaulted to qualified.
I cannot find anything in the Schema Specification to say which is correct - can anyone shed any light on this? I also want to make Oracle BPEL users aware of this issue.
Regards,
Peter Dolukhanov

I resolved this issue by adding the following to the 2nd schema in the wsdl
xmlns:xsdLocal1="urn:/crmondemand/xml/integrationevent"
inside the 2nd schema
<xsd:schema
elementFormDefault="qualified"
attributeFormDefault="unqualified"
xmlns:xsdLocal1="urn:/crmondemand/xml/integrationevent"
targetNamespace="urn:crmondemand/ws/integrationevent/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
and this line immediately below it
<xsd:import namespace="urn:/crmondemand/xml/integrationevent" />
I could then create a proxy class using wsdl.exe

Issue with publishing schema as webservice using WCF-BasicHTTP two way channel

Similar Messages

Maybe you are looking for