Is it possible to add an AASX package via the API? about server HOT 6 CLOSED

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:

1. APIs with Asp.Net core: Yes
   API to upload new package: PostAASXPackage
   API to update existing (already loaded) package: PutAASXPackageById

2. APIs with Grapevine: Partially
   API to upload new package: NOT Possible
   API to update existing (already loaded) package: Possible, Api (HttpMethod = HttpMethod.PUT, PathInfo = @"^/server/getaasx/(\d+)(/|)$")

To connect to new APIs with Asp.Net core:
The new REST endpoint is : http:// <Host_Name> :5001/
Swagger documentation for these APIs can be found at : http://<Host_Name>:5001/swagger/index.html
Package explorer can be connected to Aasx-Server by: File -> AASX File Repository -> Connect HTTP/REST Repository and
appending "?asp.net" to the new REST endoint as shown in the screenshot.

The documentation of these new APIs will be released soon.

from server.

Dear @juileetikekar thanks for the insightful answer. This definitely helps a lot. I will test the aforementioned APIs.

from server.

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.

from server.

Hi @vChavezB ,

The binaries have been now updated and the latest binaries now consist of the features mentioned in my earlier comment.

from server.

Thanks for the update. I tried running

AasxServerCore --rest --no-security -p 5001

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

from server.

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

https://github.com/admin-shell-io/aasx-server/blob/a95e2da34dc866ff50a5bee2838aea36349fea48/src/AasxServerBlazor/Properties/launchSettings.json#L26

from server.