Hello again, Glad that worked Daniel.
For your next issue, it could be a variety of different things, but where you should start is looking at the browser network call being kicked off when you try to browse or run a query in sparky-fe. If everything looks ok there (ie, call is being made to the backend, looks right, response is a valid empty result, my guess is this is not the issue) , next look at the sparky-be call being triggered in the sparky-be logs (look in error.log) and what url/port its configured to call for resources/traversal. It's probably a config for sparky-be that its not calling the same mS uri that you are manually calling. Thanks, Bill -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#23723): https://lists.onap.org/g/onap-discuss/message/23723 Mute This Topic: https://lists.onap.org/mt/88109046/21656 Mute #aai:https://lists.onap.org/g/onap-discuss/mutehashtag/aai Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
