BAPI_ACC_DOCUMENT_POST on ABAP Cloud? - abap

On an on-premise we have option to call BAPI for CRUD operations. How can we achieve the same in SAP cloud environment. For example I am trying to find solution to post FI documents from external API into SAP Cloud, equivalent to bapi_acc_document_post in on-premise.
Thanks.

In Cloud Environment you can enable SAP API Business Hub to access APIs described in api.sap.com
There are several APIs available for different SAP Applications; for example check Journal Entry - Post (Asynchronous)
You can find a Business documentation describing the use cases from a functional perspective as well as technical informations (API Specs, WSDL, urls etc..)

Related

how to obtain Google Bigquery FQDN Project ID

I am working with a customer who is using Google BigQuery, and we are attempting to reverse-engineer their model. The problem is that the connection requires the Project Id in a FQDN form, which usually comes to mydomain.com:myProject
I am not familiar at all with BigQuery, is there a place in the users dashboard i can find this? Everything we have browsed through only seems to give us the Project ID.
GCP Bigquery represents a concept of Enterprise data warehouse, which is isolated and GCP fully-managed environment for high-scalable operations addressing data analytics tasks. Although GCP Bigquery conceptually built as serverless platform Software as a Service (SaaS) providing an execution environment for customer analytics purposes, infrastructure and hardware components are self managed by Google cloud computing inventory, that means that Bigquery service doesn't offer any regular hosting endpoint for external visitors.
The interaction with GCP Bigquery can be only established in the following ways:
BigQuery web UI in the Cloud Console;
Using BigQuery command-line tool;
Bigquery REST API through service endpoint:
https://bigquery.googleapis.com;
Using programming language specific Cloud Client Libraries for
the BigQuery API.

Integrate WSO2 API Manager with third party api gateway like kong

I´m interested in using the store and the developer portal. In some cases I want to integrate third-party gateway like kong.
The documentation from WSO2 API Manager 2.x says:
- Components usable separately: developer portal can be used to catalog
APIs deployed in third-party gateways
(https://wso2.com/api-management/features/)
Do you have more information about that feature and how to configure it?
Technical this is feasible but requires some work. I've found that someone did it with Intel Expressway Service Gateway.
You would need to implement a custom handler in WSO2 and connect it with Kong. But as the features might differ, the UI may not perfectly fit.
Besides than offering extension points, WSO2 has no real interest in supporting this as the API Gateway is the core component and all of their business models are based on it.

What are feature not supported by Apache Metamodel Salesforce conenctor

I had gone through the API provided by Apache metamodel to connect Salesforce.com, most of API are there which can help perform CURD operation. But, i am unable to find the features which are not supported by Apache metamodel API's.
Is there any document reference for complete API guide and feature document for Apache metamodel Salesforce.com connector ?
Only direct documentation I can find is on MetaModel's Wiki.
To answer this question from a Salesforce side: the most obvious caveat is that Salesforce isn't an ACID or SQL compliant database. The source for the Salesforce connector is the best place to see how everything is translated. The data context is a wrapper around Salesforce's Partner API, so you run the risk of no SQL to API translation being available.

Wso2 API orchestration requirement for API Management

We successfully launch Wso2 API management solution. One of the main functionality of our project is to orchestrate several simple API and make one Meta API. Then we want to publish this Meta API into Wso2 API Management Publisher and make it available to use.
Is any solution to this requirement?
You can do this. If I understand you correct, you only want to publish the meta api as a managed api. Other simple apis won't be published. If so, things are pretty easy.
WSO2 API Manager uses Apache Synapse as the mediation engine (which is used by WSO2 ESB too). This allows to do the chaining. Please go through the following articles.
http://wso2.com/library/articles/2014/03/batch-api-api-chaining-scenario/
https://docs.wso2.com/display/ESB470/Service+Chaining+Example
http://wso2.com/library/articles/2012/09/get-cup-coffee-wso2-way/

API Management in Bluemix and API Management on Cloud

My question is really about the difference between API Management in Bluemix and API Management on Cloud?
In the docs on Bluemix I can see
"This service includes API versioning, lifecycle management, and API usage analytics."
In the knowledge center about the Cloud version is says
"The API Management environment provides the following functions:
Manages the operations of the various servers in the API Management environment.
Provides the tools to interface with the various servers.
Provides analytic functions that collect and store information about APIs and API users.
Processes and manages security protocols and stores relevant user and appliance authentication data.
Provides assembly functions that enable APIs to integrate with various endpoints, such as databases or HTTP-based endpoints.".
So, is this the same?
according to the documentation it is the same service. The differences should be related to available pricing plans, on Bluemix there is just one pricing plan.