Hu-WF commented on issue #6004:
URL: https://github.com/apache/seatunnel/issues/6004#issuecomment-1876436177

   I have solved this problem:
   Firstly, if you deploy SeaTunnel and SeaTunnel-Web on different nodes, when 
copying apache-seatunnel-2.3.3-bin.tar.gz as a client to the node where the 
SeaTunnel-Web service is located, you must ensure that the datasource is also 
in the client.
   Then, it is necessary to configure the environment variable SEATUNNEL_ HOME, 
SEATUNNEL_ WEB_ HOME, ST_ WEB_ BASEDIR_ PATH in the SeaTunnel-Web service, as 
shown below:
   
![image](https://github.com/apache/seatunnel/assets/30825060/98e99f47-29d4-4988-a19d-3895f6af9111)
   As follows:
   
![image](https://github.com/apache/seatunnel/assets/30825060/543b0fcc-7ff9-4331-a1f9-61dc60b92296)
   
   
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscr...@seatunnel.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to