Skip to content

Configuration Decisions in the Wizard

What this page helps with

The Tenant Wizard asks for the decisions that define a new monitoring configuration. This page explains those decisions from a product point of view:

  • what each step is for
  • which entries are mandatory
  • which choices affect later monitoring behavior
  • where mistakes usually cause follow-up work

1. Basic identity

At the beginning, you define the baseline of the tenant:

  • tenant name
  • operating mode
  • data directory

Use a name that clearly identifies landscape and purpose, for example by region, environment, and system role. This helps later when multiple tenants exist side by side.

2. Setup type

The most important early decision is the setup type:

  • CPI only
  • Edge Hybrid

Choose CPI only when IntegraMon should monitor the SAP CPI tenant without additional edge-specific runtime access.

Choose Edge Hybrid when you also need edge-related connectivity, certificates, or hybrid operating information.

This decision affects:

  • which wizard steps appear
  • which connection data is required
  • which later jobs and checks can run

3. SAP CPI connection

This step defines how IntegraMon reaches the CPI tenant.

Important entries are usually:

  • CPI URL
  • UI URL
  • platform
  • authentication method

Typical guidance:

  • use the productive URL of the tenant you really want to monitor
  • make sure the UI URL matches what users should open later
  • verify credentials before finishing the wizard

4. Edge connection

This step only matters for hybrid setups.

Typical entries include:

  • Edge URL
  • authentication details
  • client certificate or key material
  • optional CA information

This step should only be filled when edge connectivity is really part of the monitoring scope. If not, a simpler CPI-only setup is easier to maintain.

5. Monitoring scope

This area defines what IntegraMon should collect and prioritize.

Typical decisions:

  • message filter query
  • initial start time
  • download behavior
  • hot window or priority window
  • attachment handling
  • visibility through access groups

These settings directly influence:

  • how much data is collected
  • how quickly relevant messages become visible
  • how much API load and storage usage the tenant creates

6. Jobs, archive, and AI defaults

Later wizard steps define default operating behavior for the tenant.

Typical topics:

  • which background jobs should start enabled
  • which intervals make sense
  • how archive handling should begin
  • whether tenant-specific AI settings should start enabled or cautious

Good practice:

  • start with conservative intervals
  • enable only what is needed
  • expand later in Tenant Settings once the tenant runs reliably

Practical examples

Small productive CPI tenant

Typical choices:

  • CPI only
  • narrow message query
  • moderate message interval
  • limited attachment fetching

This keeps load small while still giving useful operational insight.

Hybrid landscape with edge relevance

Typical choices:

  • Edge Hybrid
  • complete connection test for both CPI and Edge
  • careful certificate handling
  • explicit review of job sources before finishing

This reduces surprises after go-live.

Common mistakes

  • entering URLs that belong to the wrong tenant or environment
  • choosing Edge Hybrid although no edge data is needed
  • starting with very aggressive intervals
  • forgetting to review access groups and visibility
  • finishing the wizard without running the available connection tests

Recommendation before saving

Before you complete the wizard, verify:

  • the tenant name is unambiguous
  • the setup type matches the real landscape
  • CPI and Edge tests succeed where applicable
  • the monitoring scope is realistic
  • initial jobs are not more aggressive than necessary