I have a situation where in need to integrate a system which creates general ledger files with NetSuite.
The "Source" System basically dumps the General Ledger feed in a file at a defined location and i am able to transform this file into the format that NetSuite expects.
I read that Mule ESB can communicate with NetSuite either through the NetSuite Cloud connector or a web service channel.
So far i am mapping the file content to a web-service ("Add-List" operation) and i am also aware of the Cloud Connector for NetSuite that Mule provides.
Apart from these two i.e. web-service channel and NetSuite cloud connector, is there any other mechanism using which Mule can communicate with Netsuite? Does netsuite expose any API that would help me export batch requests in CSVs or any other file format?
Netsuite does support CSV Import/Export. There are several options listed.
From NS Navigation menu go to Setup -> Import/Export
It is possible, you can download the NetSuite user guide HERE>
If you need help, let me know. We even have an ex-NASA scientist on staff who now does NetSuite Integrations. And as you know, most of the old-school legacy desktop applications can be integrated.
www.sererra.com
Related
I have an use case to fetch number of issues created and fixed by each user in Jira on a daily basis. The plan is to fetch this once a day and not in real-time. We may also need to do some processing on data retrieved from Jira and then store the data in Microsoft SQL Server. The peak number of records for issues created/ fixed can be assumed to be in range of 10K/ day.
AFAIK, there is no Mule Jira connector capability that allows this. However, questions are:
Is there any Jira API that allows us to achieve the use case?
Is this capability supported by Mule Jira connector?
Assuming that you can create that query in JIRA, then JIRA provides a REST API that will allow you to execute it. You could call the API using the Mule HTTP connector to make the requests, process them and insert into SQL Server through the Mule Database connector.
There is a JIRA REST API connector for Mule 4 that uses above mentioned JIRA REST API. It might simplify the usage but you will have to investigate it to see if it matches your needs. Check the documentation link for licensing information.
Is there a way to get details of all the apps in an Anypoint Platform Business Group. For example, if there are 3 apps available in the RunTime Manager, I am looking at details like below:
I know there are cloudhub APIs which can get the details, but is there a custom API? If yes, can it be integrated with a reporting tool like PowerBI to create a live dashboard?
Please advise.
All or nearly all REST APIs provided by Anypoint Platform return JSON, including the CloudHub REST API. You can check the platform APIs in MuleSoft Dev Portal.
You can use the cloudhub/api/v2/applications/{domain} endpoint to get details of an application: https://anypoint.mulesoft.com/exchange/portals/anypoint-platform/f1e97bc6-315a-4490-82a7-23abe036327a.anypoint-platform/cloudhub-api/minor/1.0/console/method/%231839/
To get the schedulers information the endpoint there is a cloudhub/api/applications/{domain}/schedules endpoint: https://anypoint.mulesoft.com/exchange/portals/anypoint-platform/f1e97bc6-315a-4490-82a7-23abe036327a.anypoint-platform/cloudhub-api/minor/1.0/console/method/%233128/
Both return JSON responses with the information described in above links.
I don't know if that is useful for PowerBI. If not, you can develop your own custom application to query above information and return it in a suitable format. Your application can implement an API of your design if needed.
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/
I have a requirement to connect Mule ESB with Hybris. I didnt find Hybris connector provided by Mule( Also didnt find sample examples as well). This is the 1st time going to try Mule with Hybris..Please let me know the steps or efficient procedural way to connect Hybris.
Is the hybris URL enough to connect?. Please suggest me with your thoughts to implement. Thanks in advance.
Hybris has many ways to integrate with their platform. If you have a login you can access their docs which details examples of integration with the platform including JMS and the Platform Web Services.
There is no connector supplied by Mule, but you can access their Platform Web Services which are implemented with a HTTP Restful API using the Mule http transport or by building your own connector using the Mule DevKit.
The hybris wiki has pages dedicated to most of the endpoints and the request/response formats. You can view this here if you have a login: https://wiki.hybris.com/display/release5/WebService+API+-+Reference
Also, in your hybris installation there are a bunch of examples in /bin/ext-platform-optional/platformwebservices/src...
and /bin/ext-platform-optional/platformwebservices/testsrc which show the actual web service implementations and their test cases using Jersey client.
I'm exploring the use of the WSO2 API Manager for our legacy API, which is currently SOAP based. IDeally, I'd like to expose a RESTful interface to our customers and have API Manager convert that to a SOAP request that gets passed to our legacy system. Searching the WSO2 site, I see there's some way to do this using XSLT transformations, but only when using the WSo2 ESB product.
Is there a way to handle this transformation in the API Manager? How? If not, could I somehow take advantage of the ESB product and combine it with the API Manager product? Or is that overkill?
Thanks!
REST to SOAP conversion is a standout feature of the WSO2 ESB. To learn more about it look at the sample given at [1]. The Payload Factory Mediator used in this sample is a much newer type of mediator than the XSLT Mediator and is also more efficient in handling SOAP messages than XSLT Mediator.
The WSO2 API Manager is a platform for publishing, managing and governing APIs. The WSO2 API Manager is built using the componentalized Carbon framework, for which almost all components of the WSO2 ESB are utilized. Therefore technically all that can be done with the WSO2 ESB can be done by the WSO2 API Manager; however without the help of the GUI found in the WSO2 ESB; you will have to use the source view of the configuration which is xml based. But ofcourse to navigate around this obstacle you can always download the WSO2 ESB product (which is also free and open-source) and create all the necessary mediation sequences using the GUI and copy-n-paste the configuration from the WSO2 ESB to the WSO2 API Manager and you are done.
In my opinion it is the WSO2 ESB that you need. In your case I presume you just have one or a few SOAP APIs which you need to expose as REST APIs; you are looking more at the REST-SOAP conversion feature rather than the ability to manage hundreds of APIs. If you do not need the core functionalities of the API Manager such as publishing APIs, versioning, authenticating consumers, throttling based on policies, and monitoring API usage (for a complete list of features look at the product homepage at [2]), then you really do not want the API Manager. But if you have the API Management requirements you can go with WSO2 API Manager. I don't think you should go with the WSO2 API Manager just because you foresee some kind of API Management requirements coming ahead.
Using both the WSO2 ESB fronted by the WSO2 API Manager is also a solution. WSO2 even recommends this architecture if you are performing heavy mediation in the mediation layer. You can even start with the WSO2 ESB alone and later when the proper requirements come, decide to front it with the WSO2 API Manager. Fronting the WSO2 ESB with the WSO2 API Manager is a breeze.
[1] http://docs.wso2.org/wiki/display/ESB403/Sample+800+Introduction+to+REST+API
[2] http://wso2.com/products/api-manager/