Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Add-on Installation Options

There are several possibilities to install the Int4 Suite Add-on depending on the client/project preferences.

Centralized installation on SAP Solution Manager or other SAP ABAP Application Server

In this scenario Int4 Suite Add-on is installed in SAP Solution Manager or a separate SAP ABAP Application Server. It would store and manage test cases for all non-production environments.

Such installation model requires either:

  • An Int4 Suite function modules Int4 Suite function module can be created in customer space and the source code is copy & pasted.

  • Full Int4 Suite Add-on deployment on each SAP ECC/S4HANA backend.

In case only the function modules are deployed, test types like IDocs, AIF and Proxies will not work.

Decentralized installation directly on SAP ECC/S4HANA Backend

In this scenario Int4 Suite Add-on is installed on the central SAP ECC instance.

Int4 Suite Add-on installation

  1. Login into client 000 with the DDIC user.

  2. In order to upload *.SAR file to your SAP system you need to enter SAINT transaction.  Make sure that the installed version of Add-on Installation Tool matches the one required for this particular add on release.

  3. Choose: Installation Package -> Load Packages -> From Front End

  4. Select .SAR file to be uploaded from your location, and click open:

  5. The *.SAR file has been successfully uploaded. Select Decompress.

  6. Click the Start button.

  7. Turn off the filter.

  8. Check available INT4 package, select those available and click Continue.

  9. Click on the Continue button without selecting any Support Package.

  10. Click on the Continue button.

  11. Do NOT add Modification Adjustment Transports.

  12. Click on the Accept Import button.

  13. Click on the Finish button.

  14. Int4 Suite Add-on has been installed successfully.

  15. Check it in System->Status->Component Information.

Support Packages files could be provided in You deployment package. They should be deployed afterwards. Please follow instructions in the next chapter.

Int4 Suite Support Package deployment

This section is optional and applicable if You received Support Package SAR files from Int4 team

  1. Log into client 000 as user with SAP_ALL authorization

  2. Update SPAM tool to the latest level.

  3. Enter SPAM transaction.

  4. In SPAM go to menu option Support Package  -> Load Packages -> From Front End And select you .SAR file location.

  5. Now the content of the .SAR compressed file is presented. Click Decompress to proceed.

  6. Click Display/Define button to display a list of Software Components.

  7. Select software component for which you want to import Support Packages

  8. Define the queue by choosing the appropriate Support Package

  9. When asked to add Modification Adjustment Transport to the queue click No.

  10. After defining the queue click import queue button

  11. Start options can be defined in this step. When done continue.

  12. After successfully accomplished Support Package import a following confirmation should be displayed.

  13. Support Package level is now visible in Installed Software Component Versions

  14. Finally after successful deployment in the SPAM transaction confirm imported queue by going to Go to Support Package 🡪 Confirm.

Deployment of Int4 IFTT Agent functions module in SAP S/4HANA or SAP ECC

To enable end to end testing of SAP Application Interface in SAP Backend special function modules are required. The source code of the module was delivered together with installation files or can be read from the system.

Together with the Int4 Suite package a function module: /INT4/IFTT_F_COLLECT_RESLT_RFC is deployed. It can to be copied as a Z module to both systems: the one that we deployed Int4 Suite Add-on and all other SAP S/4HANA or SAP ECC that we would like to test.

The same needs to be done for second function module: /INT4/IFTT_F_TRIGGER_MSG. This module is used by the Output Control test type.

It is important that all systems have the same function module – with exactly the same name and signature.

Please make sure that both function modules are set as a Remote-Enabled Module.

After creation the module name needs to be provided to Int4 Suite configuration int the Global Parameters section. Read here for more details about this configuration: https://int4support.atlassian.net/wiki/spaces/IUM/pages/2074083390/Int4+Suite+Configuration#Configure-Global-Parameters-activity. Set the following parameters:

  • RFC_DB_RES with the new name for /INT4/IFTT_F_COLLECT_RESLT_RFC module

  • RFC_MSGOUT with the new name for /INT4/IFTT_F_TRIGGER_MSG module

Finally, please also include the module names in the custom role for reading data from backend system.

Configuring of SAP PI/PO middleware platform

Int4 Suite virtualization ICOs

In order to send test messages by Int4 Suite to SAP PI/PO system a two technical ICOs must be created in the Integration Configuration Builder. Please import the .tpz archive from the installation package. The archive contains below objects:

Before activation, open the CC_RCV_SOAP and setup target URL as localhost.

Alternative - manual creation of Int4 Suite virtualization ICOs

  1. Create Business Component BC_IFTT with description ‘Int4 Suite Virtualization Component’

  2. Create two sender channels with following parameters:

    1. CC_SND_SOAP – Description: Int4 Suite virtualization sender channel for regular messages

    2. CC_SND_SOAP2 – Description: Int4 Suite virtualization sender channel for testing adapter modules


      Please double check that Message Protocol is XI3.0

  3. Create a receiver channel CC_RCV_SOAP with description ‘Int4 Suite Virtualization Receiver’ with following parameters:

  4. Create two Integrated configurations (ICOs):

    1. Comm. Comp: BC_IFTT

      1. Sender IF name: dummy

      2. Sender IF namespace: dummy

      3. Inbound Processing Communication Channel: BC IFTT | CC_SND_SOAP

      4. Receiver Communication Component: BC_IFTT

      5. Receiver IF name: dummy

      6. Receiver IF namespace: dummy

      7. Outbound Processing Communication Channel: BC_IFTT | CC_RCV_SOAP

    2. Comm. Comp: BC_IFTT

      1. Sender IF name: dummy2

      2. Sender IF namespace: dummy2

      3. Inbound Processing Communication Channel: BC IFTT | CC_SND_SOAP2

      4. Receiver Communication Component: BC_IFTT

      5. Receiver IF name: dummy

      6. Receiver IF namespace: dummy

      7. Outbound Processing Communication Channel: BC_IFTT | CC_RCV_SOAP

  5. Activate all the objects.

It is possible to name the above objects according to own naming convention. In such case, it is necessary to update default names in the Global Parameters configuration. Read more about it here:https://int4support.atlassian.net/wiki/spaces/IUM/pages/2074083390/Int4+Suite+Configuration#Configure-Global-Parameters-activity

  • No labels

© 2017 - 2022 Int4 AG All rights reserved