Currently, I am learning SOA and come across UDDI. I have several questions around this and hope someone can help:
By searching in the Internet I come across some interesting products e.g. WSO2 Governance Registry. Is it an UDDI if I only deploy SOAP services to it? How do people find the services then?
I have also come across a product called WSO2 API Manager. It looks like a tool for publishing API/web services. If someone can already find the web services using Governance Registry, what is the use of API Manager?
WSO2 Governance Registry is more about service metadata management. It is much about design time governance and not much about runtime governance. It is a SOA tool. It supports UDDI through JUDDI but that is not a first class support. WSO2 Governance Registry defines its own database based meta model.
WSO2 API Management is about runtime management of APIs. It comes with design time tools, to help wrap services as APIs to be exposed to the outside world. However, the key functionality is about the runtime monitoring, management, and security of the API calls via the API Gateway.
Related
I have a service fabric application that hosts api’s with app insights enabled. The api services are .Net framework 4.8 webapi projects and they are native fabric stateless and stateful services. I don’t use the app insights service fabric specific packages, but do have the standard app insights for webapi packages. I have always been in Azure commercial and logs have worked just fine there.
Now that we are in azure gov, the only way to point a .Net Framework app to the gov app insights endpoints is by modifying the ApplicationInsights.config file.
So I’ve modified the file as per msdn, verified it is deployed with the fabric deploy package and its there next to the rest of the dlls on the vms. Yet my services still won’t log to azure gov app insight instances. Nothing is coming through. We set the instrumentation key programmatically, not in applicationinsights.config, could that be an issue? I noticed some of the msdn examples showed instrumentationkey being included in the config file, but would think that is optional.
Had anyone had experience pointing .net 4.8 fabric services to gov app insights?
When using a government cloud, you need to use a connection string instead of an instrumentation key.
Important
Sovereign clouds, such as Azure Government, require the use of the
Application Insights connection string
(APPLICATIONINSIGHTS_CONNECTION_STRING) instead of the instrumentation
key. To learn more, see the APPLICATIONINSIGHTS_CONNECTION_STRING
reference.
More info here and here.
This ended up being an issue with my gov configuration file. The MSDN document wasn't very clear on where the new config sections go. It made it look like they are all nested under the top level node of the config file. Turns out the TelementyChannel override has to go inside the default TelemenySinks node. I contacted microsoft on github about clarifying this in their docs.
Link to the unclear documentation
https://learn.microsoft.com/en-us/azure/azure-monitor/app/custom-endpoints?tabs=net
Link to github issue to get it fixed
https://github.com/MicrosoftDocs/azure-docs/issues/80066
With Hyperledger composer deprecated and fabric-rest-api (https://github.com/hyperledger-archives/fabric-sdk-rest) archived, what is the future roadmap of REST API for Hyperledger fabric? What is recommended way to expose rest APIs with Hyperledger Fabric 1.4.x? The documentation (https://hyperledger-fabric.readthedocs.io/en/release-1.4/fabric-sdks.html) mentions that REST SDK will be provided in subsequent releases - but cannot find a roadmap.
When you say REST api, I assume you mean a REST api to access your hyperledger fabric application ? If so then you would need to implement that yourself. As far as I know there is no plan to provide any sort of generic rest server that can access smart contracts hosted in fabric.
There were plans to build a Hyperledger Fabric REST SDK on top of the Node.js SDK, and work was started on this. The FABR key tracks all related stories to it on the Hyperledger Jira tracker (see https://jira.hyperledger.org/projects/FABR).
The related repository is https://github.com/hyperledger-archives/fabric-sdk-rest
However as you can see the project has been archived. Many people have made their own REST APIs which exposes the internal Fabric functionality through REST, including myself. Another example might be one made by Altoros (see https://github.com/Altoros/fabric-rest). The problem is that these are not always kept up to date and have questionable authentication (if any).
It's sad to say but the first thing you would have to develop to work with Hyperledger Fabric is your own set of tools.
For a very basic example of a REST API implementation for Hyperledger Fabric with the Node.js SDK, I would like to refer to https://medium.com/#kctheservant/an-implementation-of-api-server-for-hyperledger-fabric-network-8764c79f1a87.
Using Mule ESB I noticed that you can connect (via anypoint connectors) applications, databases, web services etc.
Since I am making a comparison between different ESB (Enterprise Service Bus) I ran into WSO2 ESB and reading the documentation it seems that allows to interact only web services (through SOAP communications).
Someone confirms what I wrote? Or WSO2 ESB is flexible as Mule ESB and I'm wrong (if so what are the differences)?
WSO2 ESB also has the concept of connectors which you can use to connect to external applications, databases, file systems and web services hosted in cloud or in internal networks. Here is a webinar which you can follow to get more information.
http://wso2.com/library/webinars/2014/09/esb-connectors-for-on-premise-and-cloud-integration-solutions/
I can't help as my knowledge of WSO2 is limited. What I could do is to recommend you the book open source ESB in action, although outdated its data, the introduction is amazing and the comparison methodology is also good. You could follow the same approach with the state of the art today.
Most of the connectivity to applications, databases, different protocols are already available with wso2 ESB and wso2 product stack out of the box. However there are some connectors that will support integration with on-premises legacy systems and additional protocols. eg: ejb, is08583, kafka, etc.
I want to build REST-based web services on Microsoft Azure. I want to define my web service APIs using some kind of IDL from which client SDKs for various programming languages can be generated. Ideally, even client documentation, test code, and client sample code could be generated.
Outside the Azure world, there are tools like Swagger and RAML that attempt to do this. Does anyone know of an equivalent, existing or planned, in the Azure space?
Yes, this is coming very soon - http://blogs.msdn.com/b/windowsazure/archive/2013/10/23/microsoft-acquires-apiphany.aspx.
I'm currently assessing ways to impelement authentication&authorzation in a .NET SOA environment(ASP.NET MVC, WCF).
I have concluded that using Windows Identity Foundation with a STS should fullfill our criteria.
I'm having hard time finding any suitable STS to work with WIF other than ADFS. I know there are multiple options, but there is no documentation/experience available how well these play together with WIF.
Summa summarum, multiple questions:
Is this dumb idea?
Is there any STS product that plays together with WIF smoothly? Any resources on this?
Are there products that allows me to implement centralized(yet scalable) authorization(even with XACML support)?
What is your experience using WSO2 Identity Server with ADFS/WIF?
WSO2 Identity Server has some XACML capabilities but how can these be used in authorization with WCF services?
There is Starter STS
http://startersts.codeplex.com/
which has lately been replaced by the IdentityServer:
http://identityserver.codeplex.com/
It's been for a while and has some features ADFS lacks (like the ability to use a MembershipProvider to authenticate users).
Also, crafting your own STS is relatively easy. There are some good tutorials around, I've also written few posts on this:
http://netpl.blogspot.com/2011/08/quest-for-customizing-adfs-sign-in-web.html
WSO2 Identity Server can be integrated with ADFS. Also it can be run as an XACML engine. XACML engine is exposed to out side as a SOAP end point as well as a Thrift end point.
Disclaimer : I am an architect at WSO2.
No experience of WSO2 but if you don't want to use ADFS you'll have no problems with Identity Server. Both ADFS and Identity Server and more commercial products such as Ping Identity play very nicely with WIF.