onedevatlasBeta
Browse the atlas
AllBTPCAPUI5ABAP
SampleSampletypeA worked example you read or clone. Evidence: it demonstrates, it never provides.See every one →What this type is →independently maintainedindependently maintainedoriginPublished by one person or a small company outside SAP. Says nothing about quality; the readings say that.See every one →Starting point

scec

Docker Compose stacks for the edge side of an SAP BTP scenario: a ThingsBoard IoT stack with components added for an SAP Cloud landscape, and a template that builds a Cloud Connector image from SAP's own download.

The edge half of an IoT scenario, as Docker Compose stacks the maintainer calls the SAP Cloud Edge Connector. Its IoT stack takes the ThingsBoard compose template from the vendor's install guide and adds components for use with an SAP Cloud landscape, with the login on localhost:8080 and the product's predefined system administrator, tenant administrator and customer users. Beside it a template builds a Cloud Connector Docker image from the original SAP sources, with the Cloud Connector and SAP JVM versions set as build arguments in the Dockerfile and the administration UI on localhost:8443. The README marks the repository ALPHA with no security and says to use it locally only.

GitHub0 ★

Facts

Last pushLicenceMIT

Where it sits

Lives in
BTP/BAIP
Requires
DockerDockeroutside the atlasRunning the stacks, which are Docker Compose files, and building the Cloud Connector image.
Optional
Cloud ConnectorCloud ConnectorartifactThe template builds its image from SAP's own Cloud Connector download, with the version chosen as a build argument.ThingsBoardThingsBoardoutside the atlasThe IoT stack runs ThingsBoard from the vendor's own compose template, with components added for an SAP Cloud landscape.

Who is behind it

B-Tocs.org CommunityB-Tocs.org CommunityPersonMaintains this
In the atlas: maintains 6, contributes to 5@b-tocsmaintainerMDJoergPersonContributes to this
In the atlas: maintains 2, contributes to 3@MDJoerg1 contributor

What it declares

Every artifact

Type
Sample
Origin
Independently maintained

As a sample

Form
does not say

Connections3

Download
scec connectionsscecNEEDS→ needs1needs stated Running the stacks, which are Docker Compose files, and building the Cloud Connector image. b-tocs/scec — README: https://github.com/b-tocs/scecDocker→ optionally needs2optionally needs stated If: the Cloud Connector template is built The template builds its image from SAP's own Cloud Connector download, with the version chosen as a build argument. b-tocs/scec — SAP Cloud Connector Template: https://raw.githubusercontent.com/b-tocs/scec/main/templates/scc/README.mdCloud Connectorifoptionally needs stated If: the ThingsBoard stack is started The IoT stack runs ThingsBoard from the vendor's own compose template, with components added for an SAP Cloud landscape. b-tocs/scec — Thingsboard based IOT Stack for SAP: https://raw.githubusercontent.com/b-tocs/scec/main/stacks/thingsboard/README.mdThingsBoardif

README

quoted from b-tocs/scec under MIT, read
b-tocs/scec/README.mdOn GitHub

SAP Cloud Edge Connector

Simple IoT Stack for Docker Conpose to connect an edge scenario to SAP BTP.

Status ALPHA - no security. Use local only

Thank You!

This repository was inspired by:

Thank You!

MIT, read

Details

Sources3
GitHub APIdiscovered herechecked
github.com/b-tocs/scectree, pushes, contributors, CIchecked
README.mdquoted, and what the entry declareschecked

Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.

Compatibility and provenance
discovered viaGitHub API
first seen in the atlas
ecosystem and domainbtp, integration-and-messaging
Contributors1
MDJoerg

From the repository’s contributor list, .

History in the atlas1
  1. First seen.
For your agent
Ref
artifact:b-tocs-scec
JSON
/artifacts/b-tocs-scec.json
MCP
Connecting an agent