We are presently using WSO2 application server version 5.0.1 and rely on its web application url mapping feature to map our single web application to various client url's. e.g. an application running on http://mydomain.com:9763/example/ can be mapped to http://client1.mydomain.com:9763/ as well as http://client2.mydomain.com:9763/
In the new version 5.2.1 of WSO2 application server, I cant find the url mapping feature anywhere. I added the http://dist.wso2.org/p2/carbon/releases/4.2.0/features/ P2 repo and tried to search for the feature but is seems to be missing.
Has the feature been dropped? Is there a way we can have the same functionality on 5.2.1?
Yes we have removed URL mapping feature from WSO2 appserver
Related
our team is developing a web based system. we wish to use WSO2IS for user management. I installed WSO2IS as in its official site. Now I want to know how to use its features through API calls from my application
I have started the WSO2IS server locally
https://localhost:9443/carbon/admin/index.jsp?loginStatus=true.
I expect to communicate with WSO2IS through API call. But I have no idea how to do that
From this you will be able to get a basic idea on WSO2 IS related APIs.
I'm trying to build an application with a WSO2 Application server and Identity server.
the soap server which is based on Axis2 Framework needs to have WS-Trust based Authentication. For learning, I'm following this blog http://www.vitharana.org/2015/01/how-ws-trust-sts-works-in-wso2-identity.html
At the 14th steps, I have to click on security but In latest WSO2 Application server I'm not able to find how to enable the Security feature.
I'm using 5.3.0 Version of Application Server
As you can see there is no link on Unsecured for HelloWorld Service.
I'm I missing anything?
All the WSO2 products based on carbon kernel 4.4.x doesn't contain QoS features. WSO2 AS 5.3.0 is based on kernel version 4.4.x and therefore it is not supported. You can use WSO2 Developer Studio in order to apply QoS features
WSO2 experts
I downloaded the WSO2 AppFactory, but couldn't login into the web console with admin/admin. Has the default password changed?
Regards,
Terry
Please try with the following credentials
Username:admin#admin.com
password:admin
If you just tried with a downloaded 'binary' set-up of WSO2 App Factory; this will only allow you to log in to the Carbon admin console of the App Factory (If you just clicked on and visited the URL, that was printed on the server console). This Carbon admin console does not have any App Factory specific functionality which you might expect [WSO2 Carbon is the underlying platform which is used by all of the WSO2 products].
Since App Factory runs having few other servers alongside (such as WSO2 AS, WSO2 ELB, Jenkins, Redmine etc) this set up that you are running will not provide the same User interfaces or functionality which you have observed within the setup provided with https://appfactorypreview.wso2.com/samlsso .
I just thought to leave this answer, because; you would get disappointed after spending your time expecting the same Application (User Interfaces) available with the online setup (which I have mentioned with the hyperlink) by running the binary setup(wso2appfactory-1.0.0.zip) that you have downloaded from the WSO2 Web site.
We are working on a client app that should search and download directory information from Microsoft OCS server (OCS old as well as Lync).
Does OCS provide web services type api?
From what I understand, the client needs to do sip handshake before it can do directory related queries.
Having dependency on sip stack is not desirable.
So I am wondering if there is a way (like SOAP web service or something like that) to do it.
The client is a C++ client with access to gSoap or curl type library running on Linux platform.
Thanks for your help.
No, there is no web service out of the box that gives you what you need.
I thin your best bet would be to build a UCMA application that would sit on an application server inside your OCS/Lync infrastructure. You could then build a web service to access this.
For OCS 2007, you'd need to use UCMA 1.0. For OCS 2007 R2, UCMA 2.0 and for Lync, UCMA 3.0
We have finally upgraded our web services from .Net 1.1 to .Net 2.0/3.5. One of the clients that calls these web services is run as a windows service. It is probable that the windows service will not be upgraded until some time after upgrading the server at customer sites.
Is it possible to massage my .Net 2.0 web services so they will correctly service the calls from the .Net 1.1 client? In my test environment, I connect to the .Net 2.0 web service from a .Net 1.1 client and I receive a 401.1 error from IIS. The web service is set to anonymous access. The same credentials work when connecting to the .Net 2.0 web service from a .Net 2.0 client.
Thanks for your help,
-colin-
Web services are meant to be platform-neutral. If your web service was written properly, then any client, on any platform supporting SOAP 1.1, should be able to consume it.
One place where this can fall down is if your service is returning or receiving types specific to .NET. If you send or receive a DataSet, for instance, then there can be problems - DataSet is specific not only to .NET, but also to specific versions of .NET. There were many changes made in the area of XML and XML Serialization between .NET 1.1 and .NET 2.0, and you could eventually see one of those problems.
But I don't think any of those should get you a 401 error. Look into the event log and see if anything interesting was written about that error.
It depends on the service. If the .NET 2.0 service:
Is configured to support SOAP 1.1
Does not use WSE 3.0 (WSE 2.0 is OK)
Does not use any nullable types (not supported in .NET 1.1)
Accepts and returns only primitives or POCO classes (no DataSets, etc.)
Then it's compatible.
If you're getting a 401.1 error, but have no problem connecting with other clients from the same machine, then my guess is that the service is expecting something in the SOAP headers. What it's expecting, I can't tell you offhand; I'd have to see the service code/configuration.
Alternatively, it might just be a configuration issue on the web server. Without more details about the specific environments that can/cannot connect, it's hard to say.
As #Aaronaught wrote, The error can be that the service is expecting something in the SOAP headers. To analyse this, you could verify the wsdl generated (expand all files of web reference) or download the metadata via svcutil.exe. This will generate a proxy, that is used to call the web-service.
That way, you have more control over the proxy.
Example on how to use svcutil:
From command prompt:
svcutil
http://service/metadataEndpoint
Thank you for your responses. They were helpful in further diagnosing why it wasn't working. It turns out that everything does work and that the 401.1 response was misleading (but correct). Our problem was due to a change in the web services directory structure. Had I been paying better attention, I might have caught it before asking this question.
To answer my question: Yes. A .Net 1.1 client can call a .Net 2.0 web service and, in general, no additional configuration is necessary. Just make sure you're URI is correct.