3.1. IQX Add-On Installation

1. Package installation
   (Note - Installation Packages will be provided by IQX and designated as either "Frontend" or "Backend") 
   1. For Central Hub Deployment
      1. In SAP Backend, install the package for Backend using SAINT in Client 000
      2. In SAP Frontend Gateway, install the package for Frontend using SAINT in Client 000
   2. For Embedded Deployment
      1. Install the package for Backend using SAINT in Client 000 (only possible for 740 and higher).
         
2. Post installation steps

There are table entries that comes together with the package installation. Since the installation is in Client 000, these entries need to be moved to the actual and productive clients.  

These table entries are required for the FAB Workbench configuration and layout and they need to be imported and installed in ALL active clients i.e. anywhere that FAB development, demonstrations and testing will be performed, as well as the productive system(s). Also included are some sample applications to accelerate development - these will also need to be transported to the clients in which they will be executed.

The table entries and sample applications are delivered as 3 additional ZIP files that contain the following transport requests:

• IQPK900442 - Config, Template Matrix, Layouts (FAB v3.1.0 - Config, Template Matrix, Layouts.zip)

• IQPK900443 - Sample applications definition (FAB v3.1.0 - Sample applications definition.zip)

• IQXK902204 - FAB 2.4.0++ - BAPIF4T config for /IQX/BAPI_F4_AUTHORITY

The transport requests contains the following objects (table names):

/IQX/FAB_WB_CFG1

/IQX/FAB_WB_CFG2

/IQX/FAB_WB_CFG3

/IQX/FAB_WB_CFG4

/IQX/FAB_WB_CFG5

/IQX/FAB_WB_CFG6

/IQX/FAB_WB_CFG7

LTDX

LTDXD

LTDXT

BAPIF4T

Import the transport request to the Development System using the Transport Management System (STMS). Still in the Development System, create a transport request from the actual client.

This transport request will then need to be moved to the subsequent systems after each installation (e.g. unit testing, quality and productive systems).

3. Alternatively, you can create the transport(s) yourself following the instructions below:

a.  In the Development system and from Client 000, create a transport request with the following objects (R3TR/TABU - Table Contents):

/IQX/FAB_WB_CFG1

/IQX/FAB_ICONS

/IQX/FAB_WB_CFG2

/IQX/FAB_WB_CFG3

/IQX/FAB_WB_CFG4

/IQX/FAB_WB_CFG5

/IQX/FAB_WB_CFG6

/IQX/FAB_WB_CFG7

The Table Keys should contain the value * to fill the transport request with all the entries of the specified table

b.  In the Development system and from Client 000, create a transport request with (or add to the transport created in the previous step) the following objects (Table Names):

LTDX

LTDXD

LTDXT

Double click the line in Table Keys to display entry dialog.

The Table Keys should contain the value to fill the transport request with all the entries of the specified table as following

c.  In the Development system and from Client 000, create a transport request with (or add to the transport created in a previous step) the following objects (R3TR/TABU - Table Contents):

BAPIF4T

Click on the Table Key icon () to display the key for this line. 

Enter the value "*/IQX/FORM_NAME*" (without the quotes, but with the asterisks) to specify the key entry.

d.  From the configuration/development client in the Development System (i.e. NOT 000), perform a client copy for the created transport request(s) using SCC1.

e.  After the step above and still in the Development System, createone or more transport requests from the development / configuration client. This transport request(s) will then need to be moved to the subsequent systems after each installation (e.g. unit, quality and productive systems). 

Note: When creating the transport requests, use the actual client number instead of * when supplying the table keys.