[
https://issues.apache.org/jira/browse/STREAMPIPES-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17423716#comment-17423716
]
Dominik Riemer commented on STREAMPIPES-387:
--------------------------------------------
Ok, let's try to fix this problem ;)
0.69.0 uses a service discovery approach so that a pipeline element which you
start in your IDE should be available in the "Install Pipeline Elements"
section immediately.
When starting your greetings pipeline element, can you check the IP chosen upon
startup? There should be some line such as
21:45:37.793 SP [main] INFO o.a.s.commons.networking.Networking - Using
auto-discovered IP: IP
21:45:37.803 SP [main] INFO o.a.s.commons.networking.Networking - Using default
port: PORT
Then you can check if a simple web page of the pipeline element service is
accessible in the browser under this IP and port.
If this is the case, the element should be available under "Install pipeline
elements".
If you don't see anything under this IP, you can set the IP manually by
providing an "SP_HOST" environment variable. The host should be accessible from
inside the Docker container (assuming you're running the backend in Docker) and
from the host system (where the Greetings PE is running in the IDE).
> Split StreamPipes Connect worker into two different services
> ------------------------------------------------------------
>
> Key: STREAMPIPES-387
> URL: https://issues.apache.org/jira/browse/STREAMPIPES-387
> Project: StreamPipes
> Issue Type: Improvement
> Components: Connect
> Reporter: Dominik Riemer
> Priority: Major
> Fix For: 0.69.0
>
>
> Currently, all adapters that are included in StreamPipes are served from a
> single service. Besides IIoT adapters, there are several adapters that are
> not directly related to IIoT data ingestion, but other sources.
> By splitting the connect modules into an "iiot" module and another module
> that includes all other adapters, users can better decide which adapters are
> relevant for their use case.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)