Skip to main content
Use the @bijection/connectors/sap-businessobjects entrypoint to declare SAP BusinessObjects BI Platform 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.

​
Repository objects: documents, universes and scheduled instances

​
cms: Whole CMS query walked by SI_ID every pass, keyed by SI_CUID, read-only

The following example matches configuration instances.

​
Configuration: documents

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

​
Configuration: universes

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

​
Configuration: instances

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

​
Provider guidance

sapBusinessObjects.objects.cms({ objects, kinds?, properties?, pageSize?, every? }) reads repository objects through the BI Platform RESTful web services, one CMS query per page: documents (CI_INFOOBJECTS, SI_INSTANCE = 0, kinds Webi and CrystalReport by default), universes (CI_APPOBJECTS, kinds Universe and DSL.Universe) or instances (CI_INFOOBJECTS, SI_INSTANCE = 1: the outputs of scheduled runs; add SI_SCHEDULE_STATUS, whose codes are 0 running, 1 success, 3 failed, 8 paused, 9 pending, 12 recurring, 13 expired and 14 warning). Each page is POST v1/cmsquery?page=1&pagesize=n with SELECT TOP n SI_ID, SI_CUID, SI_NAME, SI_KIND, SI_PARENTID, SI_OWNER, SI_UPDATE_TS, … FROM … WHERE … AND SI_ID > k ORDER BY SI_ID. SAP’s REST guide documents neither the WHERE literal of a time nor ordering by SI_UPDATE_TS, which it prints in the server’s local zone at whole seconds, so passes are not incremental: every pass walks the whole set by SI_ID (assigned once, increasing), pageSize objects a page (100, at most 128), and ends on a shorter page. An object is keyed by SI_CUID and versioned by SI_UPDATE_TS as printed, so an unchanged object is not republished. properties adds CMS properties published as the CMS states them. Limits: deleted objects are not observed (an object missing from a later walk stays published); report data inside documents is not read; no command is declared. Unconfirmed from SAP’s guide: that cmsquery accepts a JSON {"query"} body (the guide shows XML), that its JSON answer lists entries with the selected properties as members, and the TOP and ORDER BY clauses, which the CMS query language documents for the Java SDK. Bind a sap_businessobjects credential: a session_login envelope whose login is POST <baseUrl>logon/long with the JSON body {"userName": {"$secret": "username"}, "password": {"$secret": "password"}, "auth": "secEnterprise"} (or secLDAP, secWinAD), token field logonToken, quoted: true, bearer_header: "x-sap-logontoken", and a lifetime under the server’s idle timeout (an hour by default). The web services listen on http://<server>:6405/biprws/ by default. A server on premises is reached through a network relay route, the only route that admits plain http; the login is then sent to the same origin through the relay. No BI Platform 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.