Show TOC

AS Java Resource AccessLocate this document in the navigation structure

Use

The Java Connector Architecture 1.5 provides the following functions:

  • Message inflow
  • Transaction management and inflow
  • Work management (multithreading)
  • Lifecycle management

The adapters of the Adapter Framework are based on JCA 1.0; the functions are not available there. All functions are necessary for the Adapter Framework since communication must be possible in the sender and receiver direction.

Features

Interface Overview

Characteristic Value

Name

AF resource service

Purpose

Access to the AS Java keystore and thread manager

Type

Java library in the facade com.sap.aii.af.svc.facade

Technical name

Com.sap.aii.af.service.resource

Certification

Optional

Syntax

JavaDoc package com.sap.aii.af.service.resource
  • Message inflow

    Instead of using message-driven beans and coupling them with the MessageEndpoint and ActivationSpec mechanism, the Adapter Framework defines the module processor session ejb, which implements the ModuleProcessor interface as the standard end point . Message inflow is described under Message Exchange.

    More information: Message Exchange .

  • Transaction management and inflow

    The Adapter Framework does not use local or global (XAResource) transaction management.

    JCA 1.0 does not specify the transactional procedure for the message inflow.

    Neither does it provide a transaction concept for extending LUWs from a service to a JCA adapter by using an ejb. However, you must use a transaction concept to implement 
    Exactly Once (In Order)
    .

    An adapter must access the transaction manager of AS Java (com.sap.transaction.TxManager) and control the transactions directly.

    The procedure is described in:

    Transactions for the Asynchronous Sender Direction

    Transactions for the Asynchronous Receiver Direction

  • Work management

    The message inbound channel needs a multithreading mechanism to make it possible to wait for incoming messages in multiple threads.

    In JCA 1.5 this mechanism is called work management. It is not available in JCA 1.0.

    The Adapter Framework provides access to the thread manager to enable adapters to generate their own threads.

    More information: Access to AS Java Thread Manager

  • Lifecycle management

    Lifecycle management is important for starting and stopping the inbound processing of adapters.

    More information: Managing the Lifecycle of a JCA Adapter