Pilih preferensi cookie Anda

Kami menggunakan cookie penting serta alat serupa yang diperlukan untuk menyediakan situs dan layanan. Kami menggunakan cookie performa untuk mengumpulkan statistik anonim sehingga kami dapat memahami cara pelanggan menggunakan situs dan melakukan perbaikan. Cookie penting tidak dapat dinonaktifkan, tetapi Anda dapat mengklik “Kustom” atau “Tolak” untuk menolak cookie performa.

Jika Anda setuju, AWS dan pihak ketiga yang disetujui juga akan menggunakan cookie untuk menyediakan fitur situs yang berguna, mengingat preferensi Anda, dan menampilkan konten yang relevan, termasuk iklan yang relevan. Untuk menerima atau menolak semua cookie yang tidak penting, klik “Terima” atau “Tolak”. Untuk membuat pilihan yang lebih detail, klik “Kustomisasi”.

IDs of Entities - Conductor Live
Halaman ini belum diterjemahkan ke dalam bahasa Anda. Minta terjemahan

IDs of Entities

When an entity is created, it is automatically assigned an ID that is stored in the <id></id> element.

These unique IDs are typically shown on the Conductor Live web interface under the “ID” column.

Obtaining an ID

The ID is shown in the POST response and can be obtained using GET List. To obtain an ID:

  • Obtain a list of IDs for an entity using a GET request.

  • Parse the response for the desired ID by looking for the ID that corresponds to a piece of data that you specified, such as the entity name.

The ID must be passed in any PUT, GET, and DELETE. In general, you cannot identify an entity using the name element.

Multiple Identities

Conductor systems and worker nodes within a cluster are assigned a node ID. Redundancy group membership assigns a redundancy member ID. It is important that you not conflate the node ID with the redundancy member ID; they are different IDs.

Any element that is a grouping of attributes is usually assigned a unique ID. The presence of this ID does not mean you can query this grouping by passing in this ID. You can only query the entities listed in Entities, Attributes, Elements, Properties, Parameters.

Uniqueness of IDs

Each type of entity has its own numbering scheme. For example, redundancy groups are numbered from 1 and channels are numbered separately, starting from 1.

Numbering increments indefinitely. If an entity is deleted, its number is not recycled.

Topik berikutnya:

Commands

Topik sebelumnya:

Responses
PrivasiSyarat situsPreferensi cookie
© 2025, Amazon Web Services, Inc. atau afiliasinya. Semua hak dilindungi undang-undang.