Web services in SAP are available by default? - web-services

I need to integrate data from the SAP in .NET Core application. Standard SAP .NET connector doesn't support .NET Core, so the only way to connect seems to be consuming web services published by SAP.
I have heard somewhere, that web services are not standard SAP feature and only some instances has the ability to publish ABAP web services. Is it true?
Is .NET Core web service client able co consume SAP web service?

If we speak about SAP ERP (ECC) they are practically standard. REST services are available since SAP Netweaver 7.40 and SOAP services are available since ancient times.
Generally, SAP Netweaver Gateway contains full OData implementation and is used for exposing SAP data to external systems, however REST can be used without GW too.
If we speaking about SAP Cloud solutions and other products even more integration options are available many of which are more advanced than services. For example, SAP Cloud Connector

Related

Gogle Cloud alternative to Microsoft Azure Device Provisioning Service

I am already experienced with the Microsoft Azure Device Provisioning Service, which enables my devices to register themselfes through e.g. Certificates in the Microsoft Azure IoT Hub. That makes of course enrollment of thousand of devices easier.
I have no experience in Google Cloud Platform and i have seen that there is MQTT Broker and an IOT Core Service within GCP.
But i didnt get it and it does not seem to be, that the IOT Core Service offers a similar functionality to the Microsoft Azure Device Provisioning Service.
Is this correct? Or how could i enroll lots of devices in an GCP IoT Architecture with automatic device registry and "distribution" over multiple IoT Core Services?
You could take a look at the Registeries and Device APIs to do the same. Having said that, one api call equals creation of one device.

Micro service management

We are developing a merchant application in that we have various modules like Schedule, Booking, Invoice e.t.c, each of this module are runs in different server, those are exposed through as RESTful granular services. UI layer will communicate with these granular service accordingly. To identify the request and redirect to specific micro service runs in service layer of various sever we have created a service gateway. Some of the service required data manipulation on the go which is presently accomplished through Mule ESB and some routing activities are also managed through it.
Actual purpose of the Service gateway is to match the request with service dictionary available and redirect to the respective micro service, at present its been developed in j2ee framework and runs in wildfly server. So to achieve the same process in light weight manner we come across a micro service manager like"getKong" and Customising "nginx" server to manage microservices, Mule ESB.
Along with Service Bus management is it advisable to use the Mule ESB as MicroService maanager as like getKong or any other valuable suggestion ?
In my personal opinion, you have three options:
If you don't need to perform authentication/authorization or/and
Throttling and your routing can be quite complex/complicated than is
completely fine to do it in Mule ESB.
If you do just URL rewrite nginx is probally the best choice for
minimum overhead and maximum performances.
If you really need an API manager with all the rich features than is
fine getKong or, if you want to stay in the MuleSoft
world and your are willing to pay, you can have a look at API
Gateway.
Hope this helps

the wso2 soa security gateway solution

I found a white paper the wso2 soa security gateway solution that builds a security gateway for SOA.
and in WSO2 API Manager Home page it says that:
It leverages proven, production-ready integration, security, and
governance components from the WSO2 Enterprise Service Bus, WSO2
Identity Server, and WSO2 Governance Registry. In addition, it
leverages the WSO2 Business Activity Monitor for Big Data analytics,
giving you instant insight into APIs behavior.
my question is: Does WSO2 API Manager do every thing mentioned in whitepaper document? if yes why the whitepaper is written? can we use WSO2 API Manager as an XML Gateway?
Given white paper has been published in 2011 and WSO2 API manger is resealed later 2012 and it is improving with the industry standards. All most all the aspects were covered in latest WSO2 API manger (v 1.7).
You can make use of WSO2 API manger or WSO2 ESB for XML Gateway.

Does CF provide any support for SSO applications?

Just wanted to understand if CF provides any support for SSO applications? If yes then how?
One of the use cases supported by the UAA is SSO. From the CF.org blog:
Because it is centralized, the UAA can provide a Single Sign On (SSO) service for applications in the Cloud Foundry platform. The cloudfoundry.com platform has several UI components and where they need to be secure they delegate to the UAA for authentication. Examples are the support site and the Micro Cloud Foundry site. (There are no other components in the core Cloud Foundry open source platform that have a UI, so it’s not really necessary to have an SSO feature until you grow the platform beyond the core use cases.)
The UI components that need SSO use the /userinfo endpoint in the UAA, which is just a regular OAuth2 protected resource (an example of the UAA acting as a Resource Server).

how to expose oracle pl/sql api's as web services in oracle ebs 11.5.10?

how to expose oracle pl/sql api's as web services in oracle ebs 11.5.10? i've read that in oracle ebs r12 there is soa gateway. unfortunately my client will be sticking with 11i version for a couple more years so i'm stuck with it.
does anyone have any suggestions or recommendations?
I'm not sure if this is available for your version of EBS but
The Oracle Integration Repository is a compilation of information
about the numerous service endpoints exposed by the Oracle E-Business
Suite of applications. It provides a complete catalog of Oracle
E-Business Suite's business service interfaces. The tool lets users
easily discover and deploy the appropriate business service interface
for integration with any system, application, or business partner.
I think you can do it by following the steps below:
Use the tools like jDeveloper to expose the API as a web-service
and then register it in EBS to use it.