Re: [basyx-dev] Basyx WEB referencing default exposed port instead of th

[Srinidhi Kalpathy Sundaram <srinidhi.kalpathy-sundaram@xxxxxxxxxxxx>]

Hello Aaron,

Thanks for the response.

The urls are now redirected correctly, it was the second reason it was still pointing to old urls that were cached in the settings. 

Br,

Sri

---

From: Zielstorff, Aaron <aaron.zielstorff@xxxxxxxxxxxxxxxxxx>
Sent: Thursday, August 22, 2024 8:32 AM
To: basyx developer discussions <basyx-dev@xxxxxxxxxxx>
Cc: Srinidhi Kalpathy Sundaram <srinidhi.kalpathy-sundaram@xxxxxxxxxxxx>
Subject: RE: Basyx WEB referencing default exposed port instead of the one configured.

 

Hello Sri,

 

I have two guesses what could be wrong in the config.

 

1. The registry integration feature is configured in the wrong way. You can check this in the aas-env.properties file. Verify that the basyx.externalurl is the to the URL the AAS Environment is configured to (for example localhost:9091).
2. The UI has old URLs cached in its settings. Check the burger menu to the top left and verify that the URLs are correct.

 

Hope that helps.

 

PS: for creating valid BaSyx configurations you could also use the BaSyx Starter Kit. It also supports changing the external ports. There you don’t have to worry about missing a related setting.

Here is the link: https://basyx.org/

 

Best regards,

Aaron

 

--

Aaron Zielstorff

Scientist

Dept. Digital Twin Engineering

 

Fraunhofer Institute for Experimental Software Engineering IESE

Fraunhofer-Platz 1 | 67663 Kaiserslautern | Germany

+49 160 97506280

aaron.zielstorff@xxxxxxxxxxxxxxxxxx

www.iese.fraunhofer.de

 

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

>>  Stay connected via LinkedIn: www.linkedin.com/in/aaron-zielstorff/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

 

From: basyx-dev <basyx-dev-bounces@xxxxxxxxxxx> On Behalf Of Srinidhi Kalpathy Sundaram via basyx-dev
Sent: Mittwoch, 21. August 2024 16:45
To: basyx-dev@xxxxxxxxxxx
Cc: Srinidhi Kalpathy Sundaram <srinidhi.kalpathy-sundaram@xxxxxxxxxxxx>
Subject: [basyx-dev] Basyx WEB referencing default exposed port instead of the one configured.

 

Hello,

 

I'm trying to set up 2 instances of Basyx Minimal set up ( imitating one for provider and consumer ). The first  Basyx works fine whereas the second one where I had changed all the exposed ports to avoid conflict with the first.  I was able to successfully upload a submodel but while clicking on the submodel the web ui continues to reference the old exposed port even though that was changed in the env variable configuration of the basyx ui component.

 

Instead of calling localhost:9091/shell, the UI continues to reference localhost:8081.

The references to aas-registry seems to be working with the new exposed port.

 

Can you please help in understanding if I might have missed something ?

 

Best Regards,

Sri