implementation:wms:install_generaltab
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
implementation:wms:install_generaltab [2019/01/14 15:00] vise |
implementation:wms:install_generaltab [2019/02/08 11:39] (current) vise maintenance v18.4 |
||
|---|---|---|---|
| Line 5: | Line 5: | ||
| === 3.1.1.1. System/server related fields === | === 3.1.1.1. System/server related fields === | ||
| - | 1. Shows the name of the server we are currently running the SuiteInstaller on. It’s recommended to start the installation on the SAP server. In the example, our SAP server name is DEV_SAP9_FR. | + | 1. Shows the name of the server we are currently running the SuiteInstaller on. It is recommended to start the installation on the SAP server. In the example, our SAP server name is DEV_SAP9_FR. |
| - | 2. Fill the domain name of the server where the SAP license service is installed. This should be exactly the same as what has been configured in SLD. | + | 2. Provide the domain name of the server where the SAP license service is installed. This should be exactly the same as the one configured in SLD. |
| This should include the port number of the SAP license server. On MSSQL, the port number is typically 30000, and on HANA the port number is typically 40000. | This should include the port number of the SAP license server. On MSSQL, the port number is typically 30000, and on HANA the port number is typically 40000. | ||
| - | 3. Fill the domain name of the server where the database is installed. | + | 3. Provide the domain name of the server where the database is installed. |
| On HANA, the port number of the database server should also be included. The default port number is usually 30015. | On HANA, the port number of the database server should also be included. The default port number is usually 30015. | ||
| 4. Select the type of the database management system installed on the server. | 4. Select the type of the database management system installed on the server. | ||
| - | 5. Fill the database username that has dbo rights on the SBO company database(s). | + | 5. Provide the database username that has dbo rights on the SBO company database(s). |
| - | 6. Fill the Database user password. | + | 6. Provide the Database user password. |
| - | 7. Fill the database culture. | + | 7. Provide the database culture. |
| Line 25: | Line 25: | ||
| 8. Select Production or Test environment. | 8. Select Production or Test environment. | ||
| - | This field corresponds with the Target Environment that is selected on top of the Produmex SuiteInstaller. This feature can be used to install 2 different versions of the Produmex Suite on 1 server. One version can be the TEST version, and the other version can be the PRODUCTION version. In this field, we will tell the system which database/company will be part of the production environment, and which database/company will be used as a test database. | + | This field corresponds with the Target Environment that is selected on top of the Produmex SuiteInstaller. This feature can be used to install 2 different versions of the Produmex Suite on 1 server. One version can be the TEST version, and the other version can be the PRODUCTION version. This field will inform the system about the database/company which will be part of the production environment and about the database/company which will be used as a test database. |
| - | When doing an initial demo installation, you can leave it as is on production. | + | When doing an initial demo installation, you can leave it as it is on production. |
| - | 9. Fill the Alias for the so-called “ConnectionString”. This will be the name we will use troughout the rest of the installation and configuration. It’s highly recommended to use the database name as your alias. This to avoid any confusion. | + | 9. Provide the Alias for the so-called “ConnectionString”. This will be the name you will use throughout the rest of the installation and configuration. It is highly recommended to use the database name as your alias to avoid any confusion. |
| - | 10. Fill the name of the company database. In the given example it is “SBODemo_US”. | + | 10. Provide the name of the company database. In the given example it is “SBODemo_US”. |
| - | 11. Fill the name of the Produmex database. When doing an initial installation, the Produmex database does not exist yet. So it will be created based on the name we give here. It’s recommended to use the company database name, with a PMX_ prefix. So in the given example is becomes “PMX_SBODemo_US”. | + | 11. Provide the name of the Produmex database. When doing a fresh installation, the Produmex database does not exist yet; it will be created based on the name you give here. It is recommended to use the company database name with a PMX_ prefix. In the given example it will be “PMX_SBODemo_US”. |
| - | 12. Fill the SAP User name. Typically the manager user is used here. | + | 12. Provide the SAP User name. Typically the manager user is used here. |
| - | 13. Fill the SAP User password. | + | 13. Provide the SAP User password. |
| - | After this data has all been filled, we can test the connections. | + | |
| - | For this we have 2 buttons saying “…test…” for each database/company we have added. | + | |
| - | 14. This button will test the SBO connection trough DI-API – click it to start the test. | + | After all the necessary data has been provided, you can test the connections. |
| + | For this purpose there are two buttons named ''…test…'' for each database/company you have added. | ||
| - | 15. This button will test the direct SQL connection trough SQL Native Client – click to test. | + | 14. This button will test the SBO connection trough DI-API. Click on it to start the test and once the test is done, click ''OK''. |
| + | |||
| + | 15. This button will test the direct SQL connection trough SQL Native Client. Click on it to start the test and once the test is done, click ''OK''. | ||
| {{ :implementation:wms:installation:2.suite_tests_ok.png |Testing SBO and Direct Connection}} | {{ :implementation:wms:installation:2.suite_tests_ok.png |Testing SBO and Direct Connection}} | ||
| - | When these tests have succeeded, make sure to hit the Save button on the bottom right corner. When saving this configuration, the system will create a .config file that we will re-use later for potential upgrades. | + | When these tests have succeeded, make sure to hit the ''Save'' button on the bottom right corner. When saving this configuration, the system will create a .config file that you will re-use later for potential upgrades. |
implementation/wms/install_generaltab.txt · Last modified: 2019/02/08 11:39 by vise
