Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • FE refers to Front end server
  • BE refers to Back end server

...

4.1.     Installation Packages

The FAB Product is deployed in the development packages /IQX/FAB, /IQX/FAB_COMMON, /IQX/FAB_NON_GW, /IQX/FAB_APP_GEN, /IQX/FAB_INTERACTIVE (only available for SAP NW 7.4 and above).  Regardless of the selected deployment option as described in section 1 (see above), FAB is always delivered in targeted packages for the Backend or Frontend servers.

...

  • BE Installation Package contains all of the Backend objects in the /IQX/FAB package.

                    ECC_K-240COINIQX.SARYYYCOINIQX.SAR              where YYY = FAB Version
                                   
  • FE Installation Package contains all of the Front end objects in the /IQX/FAB package.

                    GW_K-240COINIQXYYYCOINIQX.SAR

...

4.2.     Customer Specific Development Object

It is recommended that a new package is created for customer specific FAB development.   This will be required when the FAB provided super class is extended (inherited).  

...

The package will also hold any additional gateway services that you may require for your custom app development.

...

4.3.     Users, roles and authorization objects

Certain authorisation objects are required on the Backend and Frontend servers in addition to the application roles required for the specific FAB app.  IQX has documented these for your reference.  The authorisations may be implemented as recommended below or to your own role and naming convention using PFCG. 

...

4.3.1.             Implementing App Specific FAB Authorisation /IQX/FAB

App specific authorisation can be invoked by the selection of the Authorization Checkbox on the Properties screen and providing a value in the Auth. Group field in the FAB Workbench.

...

from the workbench (TCODE /IQX/FAB). This is implemented in the role /IQX/CONFIG (Section
4.3.3)

...

4.3.2.             FAB Generic User Roles

Assign to who: All users that will use the applications generated by FAB

Where to assign: All systems installed with FAB

...

4.3.2.1.           Backend

Role Name: /IQX/END_USER

Authorisation Objects defined for the role are:

...

Role template/upload file: https://bit.ly/2tzoGEf

...


4.3.2.2.           Frontend

Role Name: /IQX/END_USER_GW

...

Role template/upload file: https://bit.ly/2yFTZTD

...

4.3.3.             FAB Developer / Cutover Roles

Assign to who: Developers and consultants who will perform the configuration

...

Role template/upload file: https://bit.ly/2Iowq1e

...

4.3.4.             FAB Support Roles

Assign to who: Users, usually developers/consultants, that will provide support in the Production environment

...

Role template/upload file: https://bit.ly/2twlvNy

 

...

4.4.     Trust relationship, set up and testing using SM59.

For a Hub deployment a trust relationship is required between the BE and FE servers. This enables communication between the two servers. The trust relationship is achieved by setting up the same user in both the BE and FE servers and then testing the connection using SM59. Refer to section 4.3.2.1 for details on the authorisation/role implementation related to trusted RFC.

...