I created a simple CAR project that contains Proxy Service, WSDL and 2 XSDs. Proxy Service is marked with EnterpriseServiceBus server role, while WSDL and XSDs - with GovernanceRegistry role.
I am able to upload this CAR to ESB and it deploys Proxy Service as expected.
However when I try to upload the same CAR to a standalone GReg, it shows "Succesfully uploaded CAR" message but does not deploy any of the artifacts. I have the following path configured for my artifacts in artifact.xml: "/_system/governance/services/cqproxy".
Please let me know what I am missing.
Thank you!
The default configuration in Governance Registry (G-Reg) has a WSDL handler that deploys all WSDL files into /_system/governance/trunk/wsdls/..... Pls check if your WSDL is deployed into this location.
To deploy the WSDL in the registry path defined in your artifact.xml you will need to disable the handler function. This can be done in repository/conf/registry.xml file of your G-Reg distribution. Comment out the WSDL handler section that commences with
Hope this helps!
Regards,
Gillian
Related
We have to publish an API and configuring a SAP WSDL inside.
When we test the connection, we have a time out.
Is there any spécial settings to configure publish an API with a SAP WSDL?
Thanks in advance for your help.
Regards.
There shouldn't be any special settings to publish a SAP-generated WSDL, but have you confirmed that your WSDL is 100% correct?
If your WSO2 installation is external (ie outside your firewall or if you're accessing WSO2 in the cloud), make sure that the URL in your WSDL is the external one and not the internal one. In particular, check the location in the port definitions for all of your services.
I have a question regarding the WSO2 ESB callout mediator using an individual Axis2 configuration file. I would like to have the individual Axis2 configuration to be deployed using a carbon application. Unfortunately the callout mediator doesn't seem to be able to read the Axis2 configuration from the registry. I'm getting an error that the file axis2_blocking_client_proxy.xml can't be resolved when I deploy the carbon application that contains the mediation with my callout mediator.
The deployment works when I Quote a relative file path that points to the configuration file. Does anybody know if there is a way to tweak carbon application files so that distinct resources will be written to a dedicated directory on the WSO2 ESB Server?
Best regards,
Heiko
AFAIU, your requirement is to deploy an axis2 configuration file using a CAR (carbon application) file. This is not a recommended approach. If you need to deploy a configuration file in to the ESB, you can deploy that during the server creation time. CAR files are used to deploy the actual implementation code rather than the static configuration files.
I am trying to deploy carbon archieve file (*.car) in wso2 ESB server.For this purpose First I am creating carbon application project in my wso2 dev studio.Then after selecting this project tried to create a web application(war file).But not able to see in the context menu options either to create a new war file or to import an existing war file.
Can somebody clarify me is it possible to deploy .war file (packaged as .car file) in the wso2 ESB server? (After configuring the server role for Application Server in the WSO2 ESB).
WSO2 ESB (Enterprise Service Bus ) is middle-ware product which is used for message routing , mediation and transformation etc. I think you can use WSO2 Application Server for deploying WAR file and use as Web/application server in your back-end.
You can download WSO2AS from http://wso2.com/products/application-server/
Also how to deploy WAR file in WSO2AS is explained here.
http://wso2.com/library/articles/2012/09/develop-deploy-web-applications-using-wso2-developer-studio/
I have a .war file which was created from a soapui mock service via the 'deployaswar' option and deployed to Tomcat 5.5. I can successfully view the WSDL in firefox but noticed the the schemaLocation attribute for my xsd import is invalid. Here is the current URL format:
http://localhost:8080/?WSDL&interface=UserServicePortBinding&part=User.xsd
It's missing the web application name in tomcat. I verified this by constructing the correct URL and viewing the xsd:
http://localhost:8080/wartest?WSDL&interface=UserServicePortBinding&part=User.xsd
I also noticed the other references in the xsd have the same issue. How can I correct this?
thanks.
I figured this out for myself. It was a matter of using "Deploy directory or WAR file located on server" to deploy the war and setting the context path to: /
That allowed everything to work correctly.
Could anyone point me to the steps to host/publish the webservice/wcf service in sitecore/shell/webservice folder.
I have created the service and published to /sitecore/shell/webservice folder it throws authentication error and after that service host error. The need is to deploy the service in a folder where all the sitecore contents are accessible.
Two good resources for this:
http://adeneys.wordpress.com/2008/10/17/make-sitecore-host-wcf/
http://sitecoreblog.alexshyba.com/2009/03/attach-wcf-services-to-sitecore-context.html