Skip to Content
author's profile photo Former Member
Former Member

block and control

Hi XI Professionals,

Can anyone briefly explain about

1 block and control step?

2 what is pmi and ccms what is the use of them?

3 what is the need of JCA?

4 what exactly difference between FTP and NFS?

Thanks in advance,



Add comment
10|10000 characters needed characters exceeded

4 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Apr 16, 2008 at 08:01 AM


    > 1 block and control step?

    A lot questions about general questions are already asked in this forum, so if you search a little bit you will find almost every information you need.

    Here somebody asked for example what ccms is:


    And please only one question per thread:

    Deadline Branch not working



    Add comment
    10|10000 characters needed characters exceeded

  • Posted on Apr 16, 2008 at 08:22 AM

    Hello Chandu,

    1) block and control step?

    Ans: You use a block ( ) to combine steps that you want to execute one after the other and which are to access the same local data (see also: Containers). You can also use a block to combine steps that you want to have the same deadline or exception handler, or to define a local correlation.

    You can define the mode Parallel For Each(ParForEach) for a block or Dynamic Sequence (ForEach). This means that the block is executed for all elements of a multi-line container element.

    You use a control step ( ) to do the following:

    • Terminate the current process

    • Trigger an exception

    • Trigger an alert for Alert Management (see also: Triggering an Alert)


    Terminate the Current Process

    Choose Terminate Process.

    At runtime, the system terminates the current process instance, including all active steps, and sets the status for the process to logically deleted.

    Trigger an Exception

    Choose Trigger Exception and specify the triggering exception (see also: Exception Handling). The relevant exception handler must be defined in the same block or a superordinate block.

    The system triggers the specified exception at runtime

    2 what is pmi and ccms what is the use of them?



    You have the option of connecting your adapter to the Process Monitoring Infrastructure (PMI). In the SAP environment, technical processes often extend beyond system boundaries (as is the case in Business Process Management, for instance). By connecting to PMI, you have the ability to monitor such processes.

    PMI collects data from various different systems by means of PMI agents, which make their data available centrally for evaluation purposes.


    The PMI trace data is initially collected in the memory before being loaded asynchronously to the PMI server. Consequently, the effect on the monitored system and its performance is kept to a minimum.

    SAP systems that exchange messages with other systems (for example, tRFC or the Runtime Workbench) are connected to PMI automatically.

    PMI is integrated with SAP Solution Manager. SAP Solution Manager joins the business process view with technical tracing that extends beyond system boundaries.

    For more information about process monitoring with PMI, see: Process Monitoring with PMI (Process Monitoring Infrastructure)

    Interface Overview




    AF PMI Access


    Create PMI Data


    Java library

    Technical name




    See under path: JavaDoc (.index) package


    ● Use the PMIAccess class to set PMI events. The Adapter Framework calls the PMIAccess class.

    ● Adapters can implement the following PMIAccess methods to monitor message processing overall:

    PMIAccess Methods

    Method Name



    Can be used by the adapter in the sender/inbound direction to report the arrival of a new message as soon as possible.

    The method requires a message ID. It does not necessarily have to be an XI message ID if the MessageIDMapper is then used to map the message ID to an XI message ID.

    See also: Generating, Persisting, and Mapping a Message ID


    Records the address information for a given message ID.

    The method must be called for the adapter in the sender/inbound direction if invokeAdapterInboundAgent was called previously.


    Must be implemented in the adapter to make PMI aware of the mapping between the external ID and the XI message ID.

    You must implement this method if invokeAdapterInboundAgent is called using an external message ID and the MessageIDMapper service is not used.


    Can be called in receiver/outbound direction to report the exit of the message.

    If you call the method by using an external message ID, the adapter must call either invokeIDMappingAgent or use the MessageIDMapper to make PMI aware of the ID mapping.

    ● You do not need to include any other PMIAccess methods.

    ● If the XI message ID is set in one of the methods listed above, it must be a hexadecimal string if you use callPMIAgent() and this is set to TRUE.


    The CCMS Monitoring Infrastructure locally monitors a component using data collectors and stores the monitoring data in the main memory of the component. A central monitoring system can request this data over the network and therefore provide you with a central overview of your system landscape.

    With the CCMS Monitoring Infrastructure, you can also set alerts to be triggered when certain threshold value conditions are met. You can set an auto-reaction to notify you as a result of the alert.

    The CCMS monitoring infrastructure is used as a data platform by:

    Transaction RZ22

    The CCMS Alert Monitor

    The Solution Manager

    Various system management partner products

    Back to top

    Which of my SAP systems should I use as the central CCMS monitoring system?

    The central monitoring system should fulfill the following criteria:

    It should have as high a release status for SAP Basis as possible. As the agent SAPCCM4X is only available as of a central system release status of SAP Basis 4.6C, monitoring larger system landscapes is only possible as of this release.

    It should have as high an availability as possible. You will find central monitoring of limited use if the system is not constantly available, you must fall back on the local administration functions, and the notification from the central system if errors occur is also not functioning.

    In large system landscapes, it can be useful to set up a separate, purely SAP Basis system for central monitoring. You could also use this system for other central tasks (such as the Solution Manager, Central User Administration, Transport Domain Controller, and so on). For the central monitoring system, a status of SAP Web Application Server 6.10 or 6.20 is ideal.

    3 what is the need of JCA?



    The adapters that you are developing for the Adapter Framework of SAP Exchange Infrastructure must be implemented as resource adapters of the Java Connector Architecture (JCA) 1.0. Adapters do not have to meet all the requirements that are specified as mandatory in the JCA, since some aspects are not relevant to the Adapter Framework.

    On the other hand, some requirements are optional in the JCA, but must be met since they are mandatory in SAP XI.


    The references in the following descriptions refer to the document J2EE Connector Architecture Specification, Final Version 1.0.

    You can download this document at


    · Adapters run on the J2EE server of the SAP Web Application Server 6.40, which contains a JCA 1.0 framework. The J2EE server thus meets all the requirements set out in the J2EE Connector Architecture Specification, Version 1.0.

    · Adapters for the Adapter Framework are usually able to act as sender and receiver adapters. JCA 1.0 does not provide any mechanisms for the sender/inbound direction of the adapter. These mechanisms are provided by the Adapter Framework interfaces. See: Message Exchange

    · JCA 1.0 does not provide any mechanisms for adapter lifecycle management, that is, adapters do not contain any information about UNDEPLOY, RESTART, REDEPLOY, or changing ManagedConnectionFactory properties. These mechanisms are also provided by the Adapter Framework interfaces. See also: Managing the Lifecycle of a JCA Adapter


    The following documentation describes the requirements that you must meet in relation to JCA and SAP XI during adapter development:

    · Connector Architecture, Roles and Scenarios, Lifecycle

    · Connection Management

    · Transaction Management

    · Security Architecture and Security Contract

    · Common Client Interface (CCI)

    · Packaging and Deployment of Adapters

    4 what exactly difference between FTP and NFS?

    Ans: If the file you are picking up is on the an FTP server then u need to use FTP protocol(in this case you will give FTP server name or IP address in sender file communication channel),

    but if the file is on NFS server(meaning on XI server itself) then u can use NFS protocol.

    All these information is really useful to you..


    Satya Kumar..

    Reward POints If it is useful...

    Add comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Apr 16, 2008 at 08:42 AM

     Block

    Block hierarchy is basis for visibility of container elements (local variables)

    Deadline can be defined for block

    Exception handling – multiple exception handlers (branches) possible

    Dynamic modes: dynamic parallel (ParForEach), dynamic sequential (ForEach)

    Control: To Terminate process / Trigger exception /Trigger alert

    The J2EE Connector Architecture (JCA) technology provides a unified architecture for connecting the AS Java to heterogeneous Enterprise Information Systems (EIS). The adapters are modules that are deployed on the application server and provide unified access to the EIS for any application components that are also installed on the server.

    JCA involves integration of three underlying mechanisms:

    ● Connection pooling

    The Connector Container Service in the AS Java provides support for pooling EIS connections, which can be reused.

    You can configure the connection pooling for each ManagedConnectionFactory at deployment time.

    ● Transaction management

    ● Security management

    These system-level contracts enable the communication between the deployed resource adapter and the application server. They also define a close relation between the connector services and the AS Java Transaction Service and Security Provider Service.

    JCA in the AS Java enables easy and uniform connectivity to external resources using resource adapters or the interfaces that the connector services provide.

    The Connector Container Service enables the deployment of resource archives (RAR files) on the AS Java. It also provides overall connection management by registering all client requests for connections. The Connector Container Service offers support for connection pooling. You can use the functions this service provides to develop and deploy a resource adapter following the requirements of the JCA 1.5 standard.

    NFS: network file sharing

    FTP: File transport protocol


    Go through thes blogs.




    Add comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Apr 16, 2008 at 08:48 AM


    > Hi XI Professionals,


    > Can anyone briefly explain about


    > 1 block and control step?

    Block is used for Deadline, Exception etc

    where control is used to tell procces "what it will goes in some wront Error, Exception etc."

    > 3 what is the need of JCA?

    > 4 what exactly difference between FTP and NFS?

    File Transfer Protocol (FTP) is used when you need to transer the FIle on network from one server to another.

    Network File System : WHen file is already in the same operating system and FIle adapter need to pick it then NFS is used.



    Add comment
    10|10000 characters needed characters exceeded