CPA Cache

Learning Objectives

As a result of this document, you will:

Understand the basics of CPA Cache, including:

z Configuration
z Monitoring
z Troubleshooting
z Manual refresh

SAP AG 2004, Adapters: CPA Cache

 Cache overview

Integration Builder Business system

Activate Changelist SLD Cache Own Business system
Import
Request Cache update again
Integration Server
Business
Process
Cache
Engine
TA: SXI_CACHE
Delta
Full (only

Update
Integration
Business Business on request)
Engine
Processes

Runtime Access
Process
Mappings Configuration
Adaptermetad Routing Rules Cache

Cache
ata Collaboration J2EE: CPACache Central Adapter
Agreements Delta Engine
Collaboration Full via URL
Profiles
SLD Cache
Software SLD Cache Own Business system
components
versions Based
On SLD Cache
Business
systems

Repository Local Adapter Engine

Cache Update

Cache
Adapter Meta
data Cache
J2EE: CPACache Adapter
Delta Framework
Integration Integration Full via URL
Repository Directory

SAP AG 2004, Adapters: CPA Cache

 CPA Cache in general

cache for Directory & Repository data (CPACache)

cache is filled during activation within directory

(process described at the end of the document)

contains objects from directory

services
parties
bindings (inbound/outbound; sender/receiver
agreements)
channels
adapter metadata
module configuration

used in adapter framework during runtime

SAP AG 2004, Adapters: CPA Cache

 CPA Cache display content

data can be seen in the CPACache Monitor

(not accessible per default)

http://<host>:<J2EEport>/CPACache

SAP AG 2004, Adapters: CPA Cache

Per default no user has access to the CPACache display tool

You get an 403 Unauthorized Error when trying to access the URL
 CPA Cache display content (2)

displays objects relevant for adapter framework during

runtime

SAP AG 2004, Adapters: CPA Cache

Shows all CPA Cache content objects

E.g. bindings (inbound/outbound), channels, adapter metadata, services, parties,
module configuration
Note: a binding corresponds to a sender or receiver agreement in the Integration
Directory. The direction will be inbound (I) or outbound (O), respectively.
 CPA Cache: Registration/Push vs. Pull

Registration/Push Mode PULL-Mode (Delta or Full Refresh)

(automatically or manual) http://<host>:<port>/CPACache/refresh?mode=
delta|full

SAP AG 2004, Adapters: CPA Cache

Integration Directory => Environment => Cache Notifications

The AE Java Cache will execute a full cache refresh, the first time the engine gets
started
Pull-Mode: use XIDIRUSER
 CPA Cache refresh

manual refresh via URL with user XIDIRUSER

http://<host>:<J2EEport>/CPACache/refresh?mode=full

SAP AG 2004, Adapters: CPA Cache

 CPA Cache refresh in detail

Adapter Engine Directory Repository

XIAFuser XIDIRuser

Adapter Runtime Notification Notif Changelist Directory Repository

Notif
Engine Cache handler error handler Object Object

Update
running

Get object ids

Get Object

Get object from repository

Update

General
OK / OK with errors status

Error Status
of single objects

SAP AG 2004, Adapters: CPA Cache

- after AE Runtime got the notification it starts the update asynchronously

- via JMS an update notification is written to the notification table
can be seen in Directory Environment Cache Notifications
- the update of CPACache is done using the user XIAFUSER
- the objects from repository (metadata) are accessed from directory using user
XIDIRUSER
- after update the success or failure is written to the notification table
 CPA Cache - Registration

SLD

Change
in XI ID
3

2 4 5

AE CPA Cache

SAP AG 2004, Adapters: CPA Cache

Enables decentral AE with central configuration

Current Registration Mode (alternative: pull from Adapter Engine)
All parties are loaded; communication channel objects only for the related AE
Step 1: ID contacts SLD to find out which adapter engines are registered, and the
URL where the trigger should be sent.
Step 2: ID sends a trigger to the respective adapter engines.
Step 3: adapter engine contacts the SLD to find out the address of the Integration
Directory
Step 4: cache refresh occurs between the ID and the AE.
Step 5: Cache status and detailed problem description can be seen in the
Integration directory: Environment => Cache Notifications (positive and negative
confirmations)
 CPA Cache: Schema Upload

SAP AG 2004, Adapters: CPA Cache

Information on available adapter schemas

Important for customer and partner solutions with the PCK; it is checked if the
cacheType is PCK: then one can upload schema with
http://<host>:<port>/CPACache/schemaupload.jsp
This is not necessary for standard SAP (technical) adapters shipped with the PCK
It is planned for the future that partners deliver and deploy their metadata with the
sda-file