I am planning to consume a WCF Service from an SSIS Package, get the data and dump it to a table. Am planning to write the WCF Consumption part in the Script component part of the Data Control Flow Task, is that the best way to do things?
Any advice would be greatly appreciated as i am totally new to SSIS
Regards,
Dinesh
Here is a link that shows How to Configure an SSIS Package to Access a Web Service using WCF. Hope that gives you an idea.
Related
We have exposed a BizTalk Schema as a WCF service for a third party vendor so that they can push messages onto our ESB. The WCF service has a single function which accepts and returns messages of that schema type. The issue is that if a response is not made in a timely manner or another message e.g. an error is generated by the ESB the third party app fails/crashes.
It doesn't really matter what is in the message as long as it is in the correct format and the data in the returned message is not used by the vendor or ourselves. The vendor also supplies its own WCF service which we can use to pass back messages should we wish to do so. I would like to modify the existing WCF service or manually create an new one which immediately returns a response but also passes the message onto the ESB for further processing.
I have created an interface from the WSDL using svcutil but cannot find any code examples of how manually create a WCF service to expose a BizTalk schema. All examples point to the wizard.
What is the code that the wizard creates? Is there an example? Thank you.
EDIT 23/08/2013
So it would appear that changing a wcf service created by the wizard is not an option nor is creating a new service manually. I have tried creating an orchestration which consumes the service and sends a response then binding that to the same receive port which works if the itinerary works but doesn't run if there is an error. Plus it only runs after the itinerary is complete which is no good. I need an immediate response.
You can change a wcf service created by the wizard, but it is generally better to use the Wizard to re-publish it using the below from the command line.
BtsWcfServicePublishingWizard -WcfServiceDescription=C:\..\WcfServiceDescription.xml
The WcfServiceDescription.xml will be under under the folder where you published the web service in \App_Data\Temp\ e.g. C:\Inetpub\wwwroot\BizTalkWcfService\App_Data\Temp\WcfServiceDescription.xml
Keeping a copy of this xml file in your source control is a good idea. Running the wizard against the one under the web service is not a good idea as it deletes and re-creates everything in the folder and so you might manage to corrupt it, so copy it out first and run against the copy.
I've configured a WCF web service (.NET 3.5) to monitor counters using sitescope. This creates a warning when the main service call exceeds some predefined threshold.
I'm trying to figure out the best way to log the service with greater granularity. By this I mean I need some way to save the timing of each of the calls within the web service to see what may be causing a problem.
One way of doing this is to use log4net to log the timing of each call (e.g. database) that is used in the web service. Or maybe I should output the timing to a database? Whatever the solution I don't want it to greatly affect the timing of the web service itself.
Has anyone had to implement a similar solution? How should I design it so it only log/saves a sample of detailed web service calls rather than every call?
Thanks for your time.
Can anyone give me some information on consuming a WCF service from ILERPG? I have the service written and running, but the only info I can find dates back to 2008. Thanks.
Scott Klement has a presentation and examples: http://www.scottklement.com/presentations/#HTTPAPI
Hey all, I have one WCF project which creates an instance of a workflow, the workflow after created is persisted and unloaded (then I can resume it using bookmarks). I am using WorkflowApplication.
In the database I can see the record but AppFabric doesn't show me the persisted instance.
Does AppFabric only works for WF xalmx services???
Any help will be appreciated :)
Thanks
Paúl.
Yes AppFabric only shows you information about workflow services it manages. By using the WorkflowApplication you are basically doing all workflow management yourself and keeping AppFabric completely out of the loop. If you want your workflows to show up in AppFabric you should use a workflow service, ie XAMLX file, and use the Receive activity and WCF to work with it.
I'm trying to publish some HL7 schemas (with quite a few ) as wcf services using the "WCF Service Publishing Wizard". The wizard seemingly runs and completes just fine, creating a service that exposes the schemas I want. But when I try to browse the newly created service, I get "Server Application Unavailable"... I looked in the eventviewer and noticed the error message: "System.OutOfMemoryException". I tested once more while having a look in "Task Manager", and i noticed that the aspnet_wp.exe was consuming more than 1 GB of RAM before it was terminated (application pool probably recycled after reaching maximum memory consumption allowed).
I was quite puzzled as to why this happened, so I decided to publish the same schema as a ASMX webservice using the "Web Services Publishing Wizard", to see if it would make any difference. After running the wizard I tried to browse the service, and it worked out just fine with no problmes whatsoever. I looked at the generated WSDL definition, which was huge, and all the referenced schemas was added as inline schemas, and not as include or import.
This left me to believe that it could be an issue with the generation of the WSDL, having so many includes in the published schema, but im not at all sure yet as to if this could be the case...
Is there anyone who have experienced similar problems trying to publish schemas as wcf services?
I welcome all suggestions that could lead me in the right direction in this issue.
Thanks.
-M.Papas
This problem is definitely a memory issue with the WSDL generation tool. Publishing complex or even semi-complex schemas as Web Services or WCF Services usually ends in out of memory exceptions. I've ran into this a few times doing a SAP iDoc demo and its just that the schema is too complex for the WSDL tool. Hope that helps.