micro-integrator | native configuration driven runtime that helps developers | Microservice library
kandi X-RAY | micro-integrator Summary
kandi X-RAY | micro-integrator Summary
The cloud-native configuration driven runtime that helps developers implement composite microservices.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
- Get SQL for SQL properties .
- Modify servlet request .
- Add a user .
- Create user store data source .
- Handle the directory handling .
- Prints out the XSD
- Gets the properties .
- Build realm configuration object .
- Update the role list of a user .
- Initialize the microIntegration .
micro-integrator Key Features
micro-integrator Examples and Code Snippets
Community Discussions
Trending Discussions on micro-integrator
QUESTION
I created the sample micro-integrator project using integration studio which runs fine while running in Embedded Micro-Integrator. But when deployed the same via docker, the endpoint seems to be unreachable.
Deployment command:
...ANSWER
Answered 2022-Mar-20 at 09:31From the error logs, it seems that the micro integrator is unable to connect to localhost:9090. Is this service (http://localhost:9090/grandoaks/categories/{uri.var.category}/reserve) deployed within the micro integrator it self (the MI server in the docker container). If this endpoint is deployed in the host machine and not the MI in the docker container, you will not be able to use localhost to access it.
QUESTION
I have tried to create custom connector by following this WSO2 Documentation
Prerequisites of apache-maven-3.8.4-bin installation done.
maven build:
ERROR:
partial pom.xml:
...ANSWER
Answered 2022-Jan-19 at 17:26You need to change in pom.xml file, in the repository nodes, url adresses. You can use find/replace like below.
from: http://maven.wso2.
...
to: https://maven.wso2.
...
From the Maven 3.8.1, it is blocking http
mirror repositories, and uses only https adreses. More in this Release Notes – Maven 3.8.1
QUESTION
I am new to docker. I can create image using dockerfile and successfully call WSO2-API
I have hardcoded configuration in deployment.toml file I want to update this information at the docker runtime for different env - DEV,QA etc
deployment.toml file content -
...ANSWER
Answered 2021-Sep-12 at 14:51Define the Variable using ARG option in Dockerfile. Example:
ARG VariableName
Now the value can be given at runtime as below.
docker build --build-arg VariableName=0 .
For more details on how to use ARG in dockerfile, please refer https://docs.docker.com/engine/reference/builder/#arg
QUESTION
Hi there I want to make a consumer service on WSO2 and I found this documentation about the configuration of wso2 deploymnet.toml file documentation, But there is nothing about vhost parameter there and I have a vhost on the rabbitMQ clouster so I need to set this value, any one knows how to do it ? Thanks in advnace
I already tried this but it did no work
...ANSWER
Answered 2021-Apr-29 at 19:41Unfortunately, there is no parameter mapping for virtual host, in deployment.toml.
BUT you can set that, when you define RabbitMQ Inbound as rabbitmq.server.virtual.host
, like below:
QUESTION
How do I gracefully shutdown docker container running WSO2 ESB? At the moment, I have to just kill the container running which might harm ongoing transactions.
Edit
I am using the micro-integrator product.
...ANSWER
Answered 2020-Dec-23 at 10:26If you are using a container orchestration system such as Kubernetes, you can use prehooks for this. Please refer - https://github.com/wso2/kubernetes-apim/blob/master/advanced/am-pattern-1/templates/am/instance-1/wso2am-pattern-1-am-deployment.yaml#L78
QUESTION
When running WSO2 Micro-integrator inside a docker container as a task in AWS, I get an error in the logs about the hostname? In the Dockerfile I don't specifically set the hostname of the container in any way. I created the task using the Cloudformation tool and do not get this error when running the container locally. I tried running on a different VPC as well, without any result. The error remains.
FYI: It is supposed to accept traffic on port 8290 and allow it to send outbound to any IP in the world. Currently I have both inbound and outbound rules set to allow on 0.0.0.0/0 with all protocols.
The full error is as follows:
at org.eclipse.osgi.internal.framework.BundleContextImpl.registerService(BundleContextImpl.java:544) at org.wso2.micro.integrator.ntask.core.internal.TasksDSComponent.activate(TasksDSComponent.java:88) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260) at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146) at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:345) at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620) at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
In case anyone is wondering: I have setup a new VPC, complete with internet gateway, routes and route tables. The instance will run but I am unable to connect to it in any way.
The following script is run to get the task and make it available:
...ANSWER
Answered 2020-May-26 at 09:11Ultimately found the problem. The software could not identify itself because it used localhost instead of 127.0.0.1 for local loopback. Since I am not in control of the software I tried adding the following to the VPC:
QUESTION
I'm trying to run the WSO2 Micro integrator on docker. When not using any form of connector this seems to work. However I now have need for the amazon sqs connector.
When using the Intergration studio 7.0.0, I have successfully imported the connector from the store and used the in one of my sequences. It shows up in the Design-mode of the studio. I used the SQS version like so:
...ANSWER
Answered 2020-Apr-02 at 09:56Finally found it (after searching well over a day)....
The connector needs to be packaged within your project as well. You can do so by following this guide: WSO2 make CAR with connector
Now to figure out the next of the errors.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install micro-integrator
Install and setup the Micro integrator
Quick start guide
Developing your first integration
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page