Hello Stackoverflow & WSO2 community,
I want to thank you for the ongoing support from the beginning of my architecture building. I'm not much skilled at creating SOA solutions, and your support has been, is and will be much important.
While trying to solve the ESB problem, I was trying to connect BAM and ESB following the tutorial I found in wso2bam-1.3.2\samples\eventing-mode-mediation-monitoring.
My steps has been:
Adding the repository in WSO2 ESB;
Adding the "BAM Mediation Statistics Data Publisher" feature;
Enabling statistics on a simple service;
Adding the ESB server in the WSO2 BAM as: https://<ip-address>:9443/carbon/ or https://<ip-address>:9443/carbon/services, with
Data Collection Method: Eventing
Type of Data: Mediation;
Running the proxy service from an external client (Netbeans java application) - note that statistics were reported into the graphic near the proxy service of the ESB
Checking the BAM - but, for instance, the Service Calls gadget says:
No services found for the server https://<ip-address>:9443
I deduce something went wrong.
If you can help me again, I'm going to begin thinking about a way to give you some kind of useful feedback!
It seems BAM 1.3.2 seems to have an issue with the ESB. Could you try with BAM 1.3.0? It should just work.
Related
I have developed a Django app which hosts a bunch of forms that collect information about issues and I want to use this data to create Jira issues programmatically.
I have a conceptual idea of how that can be achieved but my problem is that I am a complete software development newbie and also have never used Jira to this date, hence googling stuff is quite hard as I have an almost non-existent vocabulary in these regards and things get quite overwhelming really fast. I want to know if what I have in mind even makes sense before I delve deeper into documentations and figuring out how to implement stuff.
So I'm going to send POST requests from my Django app containing the issue information in JSON format. These POST requests would then be handled by some Java service which in turn uses the JRJC to create issues on Jira. In my head this implies that I have to develop a whole server (or use some kind of framework for that matter) for django to send its requests to and handle them. Would it be possible to write a plugin for JIRA that bypasses the need for such a server so I could just write the service for handling the requests and expose it on some URL based on the domain of my Jira instance?
I apologize if my question appears vague or ill-structured. Any attempts to shine light on my incompetence or pointing fingers in some direction will be greatly appreciated!
I assume that you're talking about Jira Server (hosted by you) rather than Jira Cloud (hosted by Atlassian).
A Jira plugin can expose a REST endpoint, so yes, you can write such a plugin and POST to an endpoint you define, which then uses the Jira Java API to create issues.
See https://developer.atlassian.com/server/framework/atlassian-sdk/rest-plugin-module/ for information on putting REST endpoints in your plugin.
How can I expose the wsdl through WSO2 governance registry. I have promoted the service lifecylce through to production and was hoping to get an URL some which I can share with the service consumers for discovering the service and the contract. Any pointers are appreciated.
Update: "URL some " is a typo.. apologies. In a nutshell I am unable to comprehend how to accomplish UDDI / WS-Discovery aspects with instructions in the document. I am simply looking to expose the wsdl through a url such as this "host:port/services/environment/myservice?wsdl" and would like to have the flexibility of managing service endpoints for each environment. I have a client which has to discover the wsdl's dynamically and i am figuring out ways to expose it to them. In the process, stumbled upon the wso2 product and trying to figure out.
You can use ws-discovery
another option is , you can use UDDI registry to find your services..
I have already checked the information related to WSO2 ESB SAP Adapter from this link:
http://wso2.org/premium/summer-school-2011-session4-enterprise-integration-with-sap-and-wso2-esb
Is this the only information i can found about it?
I didn't find anything related to it in the official documentation of WSO2 ESB...
An example showing how to configure this adapter in the ESB will be very helpfull!
Thanks in advance,
Santiago.
You can refer following documentation for more info about WSO2 ESB integration with SAP.
http://docs.wso2.org/wiki/display/ESB460/Enterprise+Integration+with+SAP+and+WSO2+ESB
This documentation was added recently and I hope you will be able to find the information you are looking for.
WSO2 ESB comes with a variety of adapters to connect to all sorts of different systems. One of these adapters is the SAP adapter.
The WSO2 SAP adapter has full iDOC and experimental BAPI support. It used the SAP JCO library as underlying framework to communicate with SAP.
Installing the adapter couldn’t be easier. Its shipped with WSO2 ESB and the WSO2 ESB documentation website describes the installation procedure from the WSO2 perspective.
The installation procedure however does not guide you on how to find the settings you need in SAP.
That’s where this blogpost steps in. It is actually the first in a series of three. I’ll first take you through setting up the SAP connection. Then the next blogpost will introduce sending iDOCs and the last post will take you through invoking BAPIs at SAP.
So, let’s start off with some SAP adapter knowledge. I’ll refer to the WSO2 ESB SAP adapter as ‘SA’ in the following guide.
The SA is capable to be used as a Client as well as a Server. To setup the SA as client to a SAP system you’ll need to setup a client-side configuration fle. This file should be named [SAP-GWHOST].dest and must be placed in the [WSO2_HOME]/repository/conf/sap folder. This folder does not exist per default so make sure you create it and provide enough access rights for the WSO2 user to read the files within it.
To setup the WSO2 as an idoc server you must create a configuration file named [SAP-GWHOST].server.
Let’s first handle the client configuration file. There might be some differences based on your SAP system but the following settings should cover a lot of installations. The screenshots are based on SAP ECC version 6.0
In the examples here the SAP gateway is known as SAPSYS01.
I have implemented SignalR support for web application. It works great. The problem I'm dealing now is make it work in non-Azure web farm environment. SignalR supports Windows Azure Service Bus and Redis out of the box. Also there is RabbitMQ implementation on GitHub. All these solutions implement IMessageBus interface.
Based on our current situation we can't use Redis or RabbitMQ. So I have few questions:
1) Is there any alternative solution that uses SQL Server or MSMQ?
2) Is it difficult (possible) to implement your own solution for SQL Server or MSMQ? David's post on SignalR 0.5 (http://weblogs.asp.net/davidfowler/archive/2012/05/02/signalr-0-5.aspx) says they are going to support SQL Server QNS or Service Broker (not SQL Server DB itself) so maybe it's a wrong way at all?
3) Is there a way to work around until this support is implemented? For example, it sounds like the we need to handle state of the connections list between servers. If we know number of nodes and their IPs we can share this information between servers via Web Service calls instead. Does it make any sense?
Damian Edwards appears to have just started working on the SQL scaleout implementation. You can find the details of that implementation here on GitHub and the issue tracking this work can be followed here.
I am new to blackberry app development and was wondering if someone could point me in the right direction(and may be a sample application) of how to consume web service in native apps. I'm using Blackberry JDE plugin for Eclipse.
I am able to consume a restful webservice, but now I want to consume a SOAP service. I am new to eclipse , so I would require in detail information.
Thanks,
I followed this none-ksoap2 route and it worked well for me:
http://www.johnwargo.com/index.php/blackberry/dbja2.html
This series of articles explains how to utilise the support the BlackBerry Platform has built in for JSR 172, the J2ME Web Services Specification, by creating a java stub class through the use of a utility in the Sun Java Wireless Toolkit for CLDC and the wsdl for your web service.
The articles give a very thorough and detailed explanation of the steps required to achieve the objective, so I would not wish to repeat them here in full, nor paraphrase them at the risk of my debased shorter version being quoted later. I understand the risk of answering in this way, and I realise that my short explanation above will in no way compensate should the original articles disappear from the internet.
Hey thanks for all the help. Figured it out. The problem was wcf service. When I tried with a simple web service(.asmx), it worked like charm and all the stubs were generated correctly. Probably wcf uses Soap 1.2 default and asmx service SOAP 1.1.
I even tried using KSOAP2 for calling wcf service with little success. Again switching back to asmx instead of wcf, solved the issue.
Now I have problem of plenty, which method to use(KSOAP or Stub) :)
I am all for non KSOAP method, but the only thing that is stopping me is I have to generated stub files everytime a introduce a new method.
Anyways +1 for all the help