agentleFS
williamcorrea23williamcorrea23/sap-router-skill/.agents/skills/btp-cias/SKILL.md

btp-cias

Skill1 starsChanged 4 months agoMITView on GitHub

BTP Cloud Integration Automation Service (CIAS) — automated setup of on-premise-to-BTP integration

The file

Files
SKILL.md

Cloud Integration Automation Service (CIAS)

Automates trust, Cloud Connector, destination, and principal propagation setup between on-premise SAP and BTP.

Quick Start

# 1. Enable CIAS in BTP Cockpit → Services → Integration Automation
# 2. Download CIAS agent from SAP Support Portal
# 3. Install agent on Cloud Connector host:
cias-agent --register \
  --tenant <subaccount-subdomain> \
  --user <btp-email> \
  --region us10

# 4. Run task chain (auto-approve):
cias-agent execute-chain \
  --tasks CONFIG_TRUST_ONPREME,CONFIG_CC,CONFIG_DEST_BASIC \
  --auto-approve

# 5. Verify trust:
curl -s -o /dev/null -w "%{http_code}" \
  "https://<system>.abap.cloud.sap/sap/bc/adt/cts"
# Expect: 200

Task Catalog

Task IDWhat It Does~Time
CONFIG_TRUST_ONPREMESTRUST certificate exchange + SICF5 min
CONFIG_CCCloud Connector install + access control10 min
CONFIG_DEST_BASICHTTP destination to ABAP backend2 min
CONFIG_DEST_MAILMail destination1 min
CONFIG_DEST_RFCRFC destination (for RFC_READ_TABLE, BAPI)3 min
CONFIG_SSO_CERTSSO certificate exchange2 min
CONFIG_PRINCIPAL_PROPPrincipal propagation setup5 min

Web UI Alternative

BTP Cockpit → Integration Automation → Select landscape template (e.g. S/4HANA + BTP) → Execute → Monitor → Download audit report.

ZROUTER Integration

# Via sap-router-skill dispatcher:
python scripts/sap_router.py route --action BASIS_CIAS_CONFIG_TRUST

Pitfalls

  • CIAS agent blocked by firewall → Cause: inbound rules not defined. Solution: agent needs OUTBOUND-only HTTPS (443); no inbound required.
  • ABAP ADT unavailable → Cause: /sap/bc/adt not active. Solution: activate SICF service /sap/bc/adt and ensure SAP_BC_ADT_ROLE is assigned.
  • Task returns "already configured" → Cause: CIAS tasks are idempotent. Solution: re-run safely — CIAS checks current state before applying changes.
  • Agent can't reach BTP → Cause: outbound proxy or DNS issue. Solution: configure HTTP_PROXY env var on agent VM, test with curl https://cias.cfapps.<region>.hana.ondemand.com.
  • One CIAS agent per subaccount → Cause: multiple agents conflict. Solution: register one agent per subaccount; for multi-region, use separate agents.

Verification

# Check agent status
cias-agent status

# List completed tasks
cias-agent list-executions --status completed

# Test destination from BTP cockpit
# Cockpit → Connectivity → Destinations → Check Connectivity (HTTP 200)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.