Info | ||
---|---|---|
| ||
For both the an upgrade (from a previous version of FAB) and a clean / new installation, please follow the process below, including the 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 actual clients (development, testing, sandbox, quality and productive clients, i.e. not 000).
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 IQPK900588 - Config, Template Matrix, Layouts (FAB v3.1.0 - Config, Template Matrix, Layouts.zip)
• IQPK900443 IQPK900589 - Sample applications definition (FAB v3.1.0 - Sample applications definition.zip)
...
This transport request will then need to be moved to the subsequent systems after each installation (e.g. unit testing, quality and productive systems).
Info | ||
---|---|---|
| ||
Please do not execute step 3 (below) if you have imported the above-mentioned 3 transports into your actual clients. |
3. Alternatively, you can create the transport(s) yourself following the instructions below:
...
/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 request with (or add to the transport created in the previous step) the following objects (Table Names):
...
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):
...
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 requests request(s) using SCC1.
e. After the step above and still in the Development System, create a transport request 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 requestrequests, use the actual client number instead of * when supplying the table keys.