GateManager API access for directory creation is not confirmed by the available evidence. The supported automation path described here provisions future B&R SiteManager devices through Automation Studio, while API endpoints and authentication remain items to verify with Secomea.
Separate Confirmed Capabilities from Open API Questions
| Requirement | Evidence status | Engineering decision |
|---|---|---|
| Create GateManager directories by external script | Not confirmed | Request an official API capability statement from Secomea before designing the integration. |
| Manage or organize devices through an API | Not confirmed | Do not assume that directory and device-management endpoints exist. |
| API authentication and documentation | Not provided | Obtain supported authentication methods, endpoint documentation, and sample code from Secomea. |
| Provision future devices | Supported through Automation Studio | Specify Domain tokens and Appliance Names before devices are first powered on. |
| Modify settings later | ArSrm library and SiteManager factory reset are identified | Plan and validate the runtime modification and reset workflow before deployment. |
Configure Future SiteManager Provisioning
If Automation Studio is available, configure Domain tokens and Appliance Names that will be applied when future devices are first powered on. This provides a defined provisioning route for new devices, but the evidence does not establish that it creates an arbitrary GateManager directory hierarchy.
- Define the required Domain tokens and Appliance Names in Automation Studio.
- Apply the configuration before each future SiteManager is first powered on.
- Confirm after initial power-up that the expected domain assignment and appliance name appear in GateManager.
Handle Existing Devices and Runtime Changes
The available evidence identifies the ArSrm library and a factory reset of the SiteManager as the route for further runtime modification. Because a factory reset is disruptive, record the current configuration and determine the recovery and recommissioning procedure before using this method. The evidence does not define which settings ArSrm can change or whether it can create directories.
For a scripted GateManager integration, ask Secomea to confirm directory-creation support, device-management scope, authentication methods, endpoint definitions, permissions, and sample requests. Do not select an API architecture until those product-specific details are documented.
FAQ
Does GateManager provide an API for creating directories?
The available evidence does not confirm an API or directory-creation endpoint. Obtain an official capability statement and API documentation from Secomea before implementation.
How can I provision new B&R SiteManager devices automatically?
In Automation Studio, specify Domain tokens and Appliance Names before future devices are first powered on, then verify the resulting assignment in GateManager.
Can I change SiteManager provisioning settings after deployment?
The evidence identifies the ArSrm library together with a SiteManager factory reset for further modification. Validate the supported settings and recovery procedure before resetting a deployed device.