-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is it possible to add an AASX package via the API? #130
Comments
Hi @vChavezB , Thank you for your question. In current AasxServer/master, there are two kinds of APIs: one with Grapevine (mentioned in README) and one with Asp.Net core (new). The status of these APIs w.r.t. your question is as below: Question: Is it possible to upload a package to AasxServer via API? Status:
To connect to new APIs with Asp.Net core: The documentation of these new APIs will be released soon. |
Dear @juileetikekar thanks for the insightful answer. This definitely helps a lot. I will test the aforementioned APIs. |
Is this feature with ASP Net core enabled in the latest release binaries or do I have to use the source files ? I can access the endpoint http://localhost:51310/server/listaas but cannot connect to the server with package explorer ?asp.net URL at the end. |
Hi @vChavezB , The binaries have been now updated and the latest binaries now consist of the features mentioned in my earlier comment. |
Thanks for the update. I tried running
but I could not access the swagger API through http://localhost:5001/swagger/index.html Did I miss something on the command arguments? Thanks in advanced |
Update on this issue, it was not mentioned which variant has the port 5001 opened. After checking the source code I found that the BLAZOR variant should be used for the aforementioned new API |
I read the README.md file and saw the API for this project. Is it possible to upload a package to the server via the API or can it only be done via the package explorer?
Please correct me if I am wrong as I am new to the Asset administration shell.
The text was updated successfully, but these errors were encountered: