Here you will find the post-installation steps, which are mandatory to finalize the installation and make the Int4 IFTT up and running.

Initial customizing is done in /int4/iftt_img t-code.

Step 1. Add environments that Int4 IFTT will test

/n/int4/iftt_img → Int4 IFTT Configuration → Landscape Configuration → Define Environments

1. Add your non-productive environments by specifying the environment name and description.

2. Mark SAP PI/PO checkbox if the environment has corresponding SAP PI/PO box

3. Mark SAP CPI checkbox if the environment has corresponding SAP CPI box

Example:

Open

Step 2. Run configuration wizard

Among others, the wizard will allow to create/select respective RFC connections, generate logical ports to SAP PO API and install a license. The wizard requires authorizations described in the initial customizing section. Some of the settings are common, and others are repeated for each environment.

Common Part:

2.1 In a wizard, select each row and press customize button. Then follow the screen instructions.

The expected status:

Open

‘Install IFTT license’ is a mandatory step. Here you upload a license file received from Int4:

Environment specific steps for SAP PI/PO:

For each environment, you need to set up the connection to SAP PI/PO. This section is available after specifying that landscape is connected to SAP PI/PO in the environment definition.

2.2 Maintain PI/PO RFC destination. You can create a new destination or use an existing one:

On next screen provide:

• Destination Name (HTTP connection in SM59)

• Target Host

• Port - do not leave empty. Even if the port is 80, then type 80.

• User and Password

This destination is used for SAP PI/PO Java stack communication.

2.3 Create the logical ports for each below row. The logical ports are used for SOAP communication with SAP PI/PO API. The wizard will automate the steps that generally might be conducted in transaction SOA_MANAGER. For each port, the procedure is following:

is the name of the environment for which the logical port is created.

The expected results:

The user's password is automatically copied from the RFC connection and placed in a logical port. However, suppose in the future, the SAP PI/PO communication user is changed. In that case, you need to generate new logical points using the same procedure.

The last step: PIT Message Injector is available from SAP PO SP14. So you don't need to generate it or leave an error status after generation.

In case of trouble, please refer to Solving errors during the SAP PO ports creation section.

Environment specific steps for SAP CPI:

The CPI steps are visible only if the CPI checkbox was marked during the creation of the environment.

2.4 Maintain SAP CPI RFC destinations.

In the same way to SAP PI/PO HTTP destinations, select the below roles and create the destinations. 

The first connection points to the address of the tenant management node on SAP CPI. This destination is used for accessing CPI OData API. The management target URL is following: https://<yourinstance>-tmn.hci.<region>.hana.ondemand.com

The second connection points to the address of the run-time URL on SAP CPI. This RFC destination is used for calling IFlows tested with IFTT. The runtime target URL: https://<yourinstance>-iflmap.hcisbp.<region>.hana.ondemand.com

The expected results:

The status message might show a 404 error, and this is normal behavior that can be ignored.

2.5 Adding RFC connection for SAP PI ABAP stack (Dual Stack). Optional step for Dual Stack installations

Create RFC type 3 (ABAP) connection to SAP PI ABAP stack in SM59. Manually add this parameter to the Int4 IFTT configuration:

/n/int4/iftt_img → Landscape Configuration → Configure environment parameters: On next screen select environment.

Choose parameter: RFC_DEST: SAP PI/PO ABAP stack destination
Put the RFC connection name in the parameter value.

After running the wizard, the Int4 IFTT is ready for the creation of the first test cases.