sivaguru-rajasekaran opened a new issue, #6319: URL: https://github.com/apache/hop/issues/6319
Hello Apache Hop Community, I am using Apache Hop 2.16.0 and facing an issue related to Hop Server Explorer in the Hop GUI. Environment Details Apache Hop version: 2.16.0 Hop GUI OS: Windows (local machine) Hop Server OS: Linux (headless server) Java version (server): OpenJDK 21 Hop Server startup command: ./hop-server.sh 0.0.0.0 8090 Hop Server status: Created listener for webserver @ address : 0.0.0.0:8090 Hop Server is running successfully and is reachable via: http://<server-ip>:8090 What I Have Done Started Hop Server successfully on port 8090 Opened Hop GUI (local machine) Added a Hop Server under metadata with: Hostname: <server-ip> Port: 8090 Username: cluster Password: cluster Web app name: (left empty) Saved the Hop Server metadata successfully Expected Behavior As per documentation and guidance, I expected to see: Tools → Hop Server → Hop Server Explorer or a similar option to: Connect to the remote Hop Server View server status Run pipelines remotely Actual Behavior I do not see “Hop Server Explorer” anywhere in the Hop GUI The Hop Server editor screen allows saving metadata, but: No Test Connection No Connect No Explorer / Runtime view Even after restarting Hop GUI, the option is still missing I have attached screenshots showing: Hop Server metadata editor Left navigation tree (no explorer visible) Questions Is Hop Server Explorer available in Apache Hop 2.16.0? Is it: Disabled by default? Removed or renamed in this version? Available only via a plugin or perspective? Is there a configuration or menu option required to enable it? Is Hop Server interaction in 2.16.0 expected to be done only via: hop-run.sh REST APIs Or metadata execution configurations? -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
