I use Liferay 7.1.1 GA2. Currently this version of Liferay does not support a HDFS as a document repository, as described in https://dev.liferay.com/discover/deployment/-/knowledge_base/7-1/document-repository-configuration
Is there a possibility of using HDFS as a Liferay document repository? In older version of liferay it is possible using hook plugin mechanism, which mechanism can use to implement this functionality in Liferay 7.1?
Related
We need to create the openapi v2.0 specification documents for APIs. We are using spring mvc (version 4) framework and build restful web services using JAX-RS. Need to create the openapi.yaml file to upload to Google Cloud Platform to configure Google Cloud Endpoints
I found the solution with this tutorial
http://mrbool.com/use-case-documenting-a-jax-rs-api-with-swagger/36735
In Liferay 7, JournalArticleSoapService is no longer part of the portal and we need to deploy a service-wsdd.jar to access SOAP services regarding JournalArticle.
However, I can't find any documentation which described the way to load the service. In 6.2, I use JournalArticleServiceSoapServiceLocator but this not available in com.liferay.journal.service.jar nor in com.liferay.journal.api.jar
The given example Liferay's documentation (https://dev.liferay.com/es/develop/tutorials/-/knowledge_base/7-0/soap-web-services) is about Company, User and UserGroup. But all those are part of Liferay Portal and the Locator is available without including additional jar file.
Clearly, how should I load a SOAP service that is in a plugin?
Finally I figured this out using WSDL2Java which generates the needed locator services then I generated a jar file from those classes; as described here
I've been looking at WSO2 Carbon as an OSGi application platform providing the following functionality:
Services can be deployed as OSGi components (backend and frontend/UI)
A Service UI components can be hosted (snapped) into the Carbon UI
A Service can use Carbon User Management database for authentication and authorization
Does fuseesb have a similar UI concept?
Using fuse ESB for about 6 months, I'm very happy with it.
Services are easily deployed as OSGi components - these are quite easily configured and deployed as fuse features. Fuse profiles then contain property files that define which features are deployed to your OSGi containers.
Although I haven't used every feature, I haven't seen a similar UI concept for hosting / snapping.
For authentication and authorization there are various approaches - one nice solution is to use Apache zookeeper (a key/value store) as a basis for a simple user management component that can be available to all your services.
I've been testing WSO2 BRS and WSO2 Data Services separately and working properly. The next step was to add in the WSO2 ESB the features that provide these capabilities, but they have bugs that keep the deployment of services.
BRS Feature: Can't upload the . jar with the class model for rules. (Rule Service - 3.2.0)
Data Services Feature: Various failures to create new services, not looking tables of datasource and can't upload the services created previously. (Data Service Hosting - 3.2.0)
Has anyone done these features work properly?
What is the ESB version you are using? If it is ESB 4.0.3, please install the latest versions of Rule Service and Data Services features.
Rule Service and Data Services versions: 3.2.2
Thanks
Thilini
The installation instructions are clear how to download a .zip for an individual product (e.g. ESB, Application Server, Mashup Server). But based on the OSGi component architecture, I thought it would be possible to, for example, add Mashup Server functionality to an existing install of the ESB. I've looked at the Feature Manager, and tried adding a repository (http://dist.wso2.org/p2/carbon/releases/3.2.4/), but have not had success.
Any guidance appreciated.
It's possible to install different features via the feature manager, but you have to determine the correct version of the feature compliant with the target server. For example, to install BPEL features to WSO2 ESB 4.0.2, first find the related WSO2 Carbon platform version. This can be determined by the version of $ESB-HOME/repository/components/plugins/org.wso2.carbon.core-x.x.x.jar. So if WSO2 ESB 4.0.2 is the target server, then the version of org.wso2.carbon.core jar would be 3.2.2. So the relevant BPEL feature version is 3.2.2.
You can read more about Installing+Features and How install the BPEL features via Feature Manager.
Please refer to WSO2 release matrix [1] in order to match the correct version
By looking at it, you can easily find the Carbon version of any product version.
For example ESB 4.0.2 has the carbon version 3.2.2
[1] http://wso2.com/products/carbon/release-matrix/