Page Comparison

...

1. Package installation
   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. In SAP Backend, install the packages for both Backend and Gateway using SAINT in Client 000.
   3. Note - IQX Packages to be sent by IQX and designated as Front or Back end.
2. Post installation steps

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

a.  In the Development system and from Client 000, create a transport request with the following objects (Table Names):

/IQX/FAB_WB_CFG1

/IQX/FAB_ICONS

/IQX/FAB_WB_CFG2

/IQX/FAB_WB_CFG3

/IQX/FAB_WB_CFG4

/IQX/FAB_WB_CFG5

Image Added

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

Image Added

b.  In the Development system and from Client 000, create a transport request with 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

Image Added

c.  From the actual client in the Development System, perform a client copy for the created transport request using SCC1.

d.  After the step above and 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, quality and productive systems).

3.2.     IQX Services Activation

1. For Central Hub Deployment
   1. In SAP Gateway, go to transaction SICF and hit F8
   2. Enable all the nodes related to FAB including the sub nodes
   3. Go to transaction /IWFND/MAINT_SERVICE and add the services /IQX/FAB_SRV and /IQX/SERVICES_SRV
      • Select /IQX/FAB_SRV service and at the bottom left hand side, click the “ICF node” button and then “Activate”. The node for oData at the bottom should show as green:
      • Follow the same steps for /IQX/SERVICES_SRV
      • Enabling the services in the gateway requires an Alias setup from the gateway to the backend system with login Trusted Relationship. The alias should be generic and points to a generic ABAP RFC Connection. Then only the ABAP RFC Connection should be created and specifically pointed to the appropriate ECC backend system e.g. Dev, QA, PRD. The alias should be generic as to refrain from being changed when the alias configuration is moved into different systems.

      • Click the “Customizing” button to see the system alias configuration of the oData service:

      • The SAP System Alias should be generically named e.g. FAB and should be manually maintained in SM59 on each system e.g. Dev, QA, PRD.

      • Ensure that the SM59 RFC Connection (in Gateway) has the following settings in the “Logon & Security” tab:

        • Language = “EN”
        • Client = development client or the client where FAB is configured
        • User = BLANK
        • Current User = Ticked
        • PW Status = is initial
        • Trust Relationship = Yes
        • Click on “Connection Test” button and ensure that the connection works.

         If you have a separate client in the development system e.g. Unit Test, select the System Alias that points to the Unit Test client if you wish to perform testing on this client. Take note that you need to copy the FAB app that you created in the Development client into the Unit Test client. You can do this by either the FAB export/import functionality or by using SCC1 to copy the contents of your transport request.

      • In addition, users need to have login to the gateway system with role S_RFCACL included in their roles.
2. For Embedded Deployment

   1. The same steps mentioned in Central Hub deployment need to be done in the backend system.

3.3.     FAB Configuration

Depending on deployment model, the configuration needs to be done accordingly as following:

1. In ECC, go to transaction /IQX/FAB_CONFIG
   1. Click on General Configuration node
      1. Image Added
   2. Add a new record for “002” version with the following values:
      • + = Ticked
      • Version = “002”
      • RFC Destination = BLANK
      • RFC Destination of Back End = BLANK
      • UI5 Library Reference = refer to section 3.3.1
      • UI5 Theme = sap_belize
      • UI5 Libraries to Load = sap.m,sap.ui.layout
      • Run In Shell = X or <space>
      • Server for Workbench = refer to section 3.3.2
      • Server for Anonymous Forms = http:// <SAPNWGWServer:port>/sap/bc/bsp/iqx/fab_srv/index.html
      • Server for Email Links = http:// <SAPNWGWServer:port>/sap/bc/bsp/iqx/fab_srv/index.html
      • Server for Anonymous Forms Email Links = http:// <SAPNWGWServer:port>/sap/bc/bsp/iqx/fab_srv/index.html
2. In Gateway, go to transaction /IQX/FAB_CONFIG
   1. Add a new record for “002” version with the following values:
      • + = Ticked
      • Version = “002”
      • RFC Destination = <Trusted RFC Destination to Back-End server>
      • RFC Destination of Back End:
        • = BLANK for Central Hub Deployment with dev. on Back-End Server
        • = <Trusted RFC Destination to Back-End server> for Hub Deployment with dev. on the Front-End Server
        • = BLANK for Embedded Deployment
      • UI5 Library Reference = refer to section 3.3.1
      • UI5 Theme = sap_belize
      • UI5 Libraries to Load = sap.m,sap.ui.layout
      • Run In Shell = X or <space>
      • Server for Workbench = refer to section 3.3.2
      • Server for Anonymous Forms = http:// <SAPNWGWServer:port>/sap/bc/bsp/iqx/fab_bsp/index.html
      • Server for Email Links = http:// <SAPNWGWServer:port>/sap/bc/bsp/iqx/fab_bsp/index.html
      • Server for Anonymous Forms Email Links = http:// <SAPNWGWServer:port>/sap/bc/bsp/iqx/fab_bsp/index.html
3. FAB Initial Tests
   1. Go to transaction /IQX/FAB
   2. Click the “Create” button and enter Form ID = MYFORM1 as first FAB app
   3. Accept the changes and the initial form should load.

3.3.1.      UI5 Library Reference

This can be set either to a fixed version or the most recent version of SAPUI5 Library from the cloud (https://sapui5.hana.ondemand.com/versionoverview.html).

1.  Sample URL of fixed SAPUI5 library version
   https://sapui5.hana.ondemand.com/1.52.12/resources/sap-ui-core.js

Advantage:

This will avoid having unexpected changes happening or directly to be applied to the applications

Disadvantage: 

New functionalities or bug fixes will not be available

2.  URL pointing to the most recent SAPUI5 Library

https://sapui5.hana.ondemand.com/resources/sap-ui-core.js

Advantage:

Newest functionalities are readily available and accessible by the applications

Disadvantage:

No control over changes by SAP which will be applied directly to the applications (e.g. change in alignment or having some controls getting deprecated)

3.3.2.      Server for Workbench

Multiple options are available to set this configuration:

1. http://<SAPNWGWServer:port>/sap/bc/ui5_ui5/iqx/fab2/index.html

Setting to this URL will disregard the setting for the UI5 Library Reference and instead will use the SAPUI5 library installed in the SAP Gateway system.

2. http://<SAPNWGWServer:port>/sap/bc/bsp/iqx/fab_bsp/index.html

Setting to this URL will use the setting for the UI5 Library Reference. This will also use or load the additional JS Libraries and CSS classes maintained using TCODE /IQX/FORMS_CONFIG

Image Added

3. http:// <SAPNWGWServer:port>/sap/bc/ui5_ui5/iqx/fab2/index_latest.html

Setting to this URL will disregard the setting for the UI5 Library Reference and instead will use the most recent SAPUI5 library in the cloud. This has the same effect as setting the UI5 Library reference to point to “https://sapui5.hana.ondemand.com/resources/sap-ui-core.js”