Changes for page Datenaustausch mit ACMP über die Public API
Last modified by Sabrina V. on 2025/11/25 08:30
From version 2.1
edited by Sabrina V.
on 2025/11/25 08:30
on 2025/11/25 08:30
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki.S V1 +XWiki.SF - Content
-
... ... @@ -20,7 +20,7 @@ 20 20 == Verbindungsaufbau vom ACMP zum AESB == 21 21 22 22 If you are already working with the AESB, you have likely established a connection from the ACMP to the AESB via the SICS. You can verify this in the ACMP console by navigating to System > Settings > ACMP Server > SICS Connection. 23 -If you have not entered any information about the AESB yet, you can read [[here>>doc:ACMP.6 9.ACMP-Solutions.System.Einstellungen.ACMP Server.WebHome||anchor="#HSICS-Verbindung"]] how to set up the connection.23 +If you have not entered any information about the AESB yet, you can read [[here>>doc:ACMP.68.ACMP-Solutions.System.Einstellungen.ACMP Server.WebHome||anchor="#HSICS-Verbindung"]] how to set up the connection. 24 24 25 25 {{aagon.infobox}} 26 26 Please note the public API access rights setting in the SICS connection settings. Enabling access by checking the box will allow SICS users to execute public API commands. On the ACMP Server, every message from an unknown user will be interpreted as a SICS user and assigned administrative permissions. In this case, no permission check will be performed! ... ... @@ -103,6 +103,7 @@ 103 103 104 104 = Create Asset = 105 105 106 +(% class="wikigeneratedid" %) 106 106 107 107 4. After creating a CallbackTarget in a separate VirtualRouter, you can create an Asset. Select the Publish command to do this. 108 108 5. Enter the Base64-encoded ICQL message from SaveAssets in the body, then customize the parameters.