Skip to main content
Use the @bijection/connectors/hcl-domino entrypoint to declare HCL Domino resources.

​
Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

​
Resources and modes

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

​
Documents of one scope

​
modified: DQL windows of @ModifiedInThisFile halved until one answer holds each, read-only

The following example matches configuration standard.

​
Configuration: standard

Case: hcl-domino/documents/modified/standard. Connection and resource configuration are declared by this exact case. Credential kind: hcl_domino. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: documents
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

​
Provider guidance

hclDomino.documents.modified({ form?, items, pageSize?, overlapSeconds?, every? }) reads the documents of one Domino REST API scope (the binding’s dataSource) through POST /api/v1/query?action=execute, one DQL query per request. The scope must allow DQL (dqlAccess in its schema) and every form read must have a mode named dql listing the items to return; Domino leaves documents of a form without one out of every answer. items names the items published, as Domino writes them (text, numbers, date text, or arrays of them). DQL states no result order and pages only by an offset, so answers are not paged. Each request asks for one window of whole seconds of @ModifiedInThisFile (the document’s modification in this replica), at most pageSize documents (100 by default, 128 at most): Form = 'Customer' and @ModifiedInThisFile >= @dt('…') and @ModifiedInThisFile < @dt('…'). An answer holding pageSize documents may have left some out: it is published and the same window is read again at half the width. A one-second window that still fills a page fails the pass. A pass ends two seconds before it began; the next starts overlapSeconds (300) before that end. The first pass reads every document since 1970. A document is keyed by @meta.unid and versioned by @meta.revision; a document without either is refused. Deletions are not observed: the REST API exposes no deletion stubs, so a deleted document stays published. No command is declared. Bind an hcl_domino credential: a session_login envelope whose login is POST <baseUrl>/api/v1/auth with the JSON body {"username": {"$secret": "username"}, "password": {"$secret": "password"}}, token field bearer, and a lifetime below the server’s maxJwtDuration (expSeconds is 21,600 in HCL’s sample). The user needs an HTTP password and the $DATA scope. The REST API’s data port is 8880 and serves plain http unless the server is given TLS; a server on premises is reached through a network relay route, and a session login requires an https endpoint. No Domino server has been reached.

​
Provider references

Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.

​
Source and evidence

Canonical connector source, native analysis and check receipts. Connector artifact: 905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305. The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.