User Tools

Site Tools


implementation:wms:app_config

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
implementation:wms:app_config [2018/03/26 09:17]
csuhaa
implementation:wms:app_config [2020/06/18 14:00] (current)
vise [Application configurations]
Line 1: Line 1:
-======10. Application ​configurations====== +======Application ​Configurations====== 
-=====10.1. General parameters=====+=====1. General parameters=====
 **Logging level** \\ **Logging level** \\
 The logging level defines the amount of logging done by the application. Each event that can be logged has a priority. The logging level defines which events will be added to the log file.  The logging level defines the amount of logging done by the application. Each event that can be logged has a priority. The logging level defines which events will be added to the log file. 
Line 21: Line 21:
 //​Notification Listener// {{ :​implementation:​wms:​config:​appconfig:​nl_log.png |}} //​Notification Listener// {{ :​implementation:​wms:​config:​appconfig:​nl_log.png |}}
  
-=====10.2. Add-On=====+=====2. Add-On=====
 The configuration file of the add-on loader will be used. The configuration file for the add-on loader application is located in the folder of the Add-On Loader, for examlpe: ​ The configuration file of the add-on loader will be used. The configuration file for the add-on loader application is located in the folder of the Add-On Loader, for examlpe: ​
 //​C:​\Program Files(x86)\SAP\SAP Business One\AddOns\PMX\Produmex AddOnLoader 7// \\ //​C:​\Program Files(x86)\SAP\SAP Business One\AddOns\PMX\Produmex AddOnLoader 7// \\
Line 50: Line 50:
 In order to export documents to the log file, the ’INFO’ level logging is required. Change all ’WARN’ levels to ’INFO’ in the configuration file. In order to export documents to the log file, the ’INFO’ level logging is required. Change all ’WARN’ levels to ’INFO’ in the configuration file.
  
-=====10.3. Fat Client=====+=====3. Fat Client=====
 The configuration file for the fat client application is located in the installation folder of the fat client, for example: //​C:​\Program Files (x86)\Produmex\Produmex Fat Client// \\ The configuration file for the fat client application is located in the installation folder of the fat client, for example: //​C:​\Program Files (x86)\Produmex\Produmex Fat Client// \\
 The file name is //​Produmex.Sbo.Logex.Execute.FatClient.exe.config//​ The file name is //​Produmex.Sbo.Logex.Execute.FatClient.exe.config//​
Line 123: Line 123:
  
  
-=====10.4. ScaleComm Service=====+=====4. ScaleComm Service=====
 The configuration file for the ScaleComm service is located in the installation folder of the ScaleComm service, for example: //​C:​\Program Files (x86)\Produmex\ProdumexScaneComm//​ \\ The configuration file for the ScaleComm service is located in the installation folder of the ScaleComm service, for example: //​C:​\Program Files (x86)\Produmex\ProdumexScaneComm//​ \\
 The file name is //​Produmex.Sbo.Logex.ScaleComm.Service.exe.config//​ The file name is //​Produmex.Sbo.Logex.ScaleComm.Service.exe.config//​
Line 164: Line 164:
 Default value = 1500 Default value = 1500
  
-=====10.5. Notification Listener Tool=====+=====5. Notification Listener Tool=====
 The configuration file for the Notification Listener tool is located in the installation folder of the Notification Listener, for example: // C:\Program Files (x86)\Produmex\Produmex SB1 Notification Listener (SboConnectionString)//​ \\ The configuration file for the Notification Listener tool is located in the installation folder of the Notification Listener, for example: // C:\Program Files (x86)\Produmex\Produmex SB1 Notification Listener (SboConnectionString)//​ \\
 The file name is //​Produmex.Foundation.SboNotification.ServiceHost.exe.config//​ The file name is //​Produmex.Foundation.SboNotification.ServiceHost.exe.config//​
Line 182: Line 182:
 Default value: 5000 Default value: 5000
  
-=====10.6. How to configure logging into database in the config file=====+=====6. How to configure logging into database in the config file=====
 This document describes how to set additional logging into a database/​schema by modifying the configuration file. This document describes how to set additional logging into a database/​schema by modifying the configuration file.
  
 It is possible to insert the logs into an UDT in the given database or into a manually created table in a separate database. It is possible to insert the logs into an UDT in the given database or into a manually created table in a separate database.
  
-====10.6.1. Logging into an UDT==== +====6.1. Logging into an UDT==== 
-===10.6.1.1. Create UDT===+===6.1.1. Create UDT===
 First create the user defined table in SAP Business One. First create the user defined table in SAP Business One.
  
Line 205: Line 205:
 |  SessionName ​ |  Alphanumeric ​ |  Regular ​ |  50  | |  SessionName ​ |  Alphanumeric ​ |  Regular ​ |  50  |
  
-===10.6.1.2. Modify config file===+===6.1.2. Modify config file===
 Download an example for the fat client config file from here: Download an example for the fat client config file from here:
   * MSSQL: {{:​implementation:​wms:​config:​appconfig:​produmex.sbo.logex.execute.fatclient.exe_with_sql_log_1.zip|Produmex.Sbo.Logex.Execute.FatClient.exe_WITH SQL Log_1.config}}   * MSSQL: {{:​implementation:​wms:​config:​appconfig:​produmex.sbo.logex.execute.fatclient.exe_with_sql_log_1.zip|Produmex.Sbo.Logex.Execute.FatClient.exe_WITH SQL Log_1.config}}
   * HANA: {{:​implementation:​wms:​config:​appconfig:​produmex.sbo.logex.execute.fatclient.exe_with_hana_log_1.zip|Produmex.Sbo.Logex.Execute.FatClient.exe_WITH HANA Log_1.config}}   * HANA: {{:​implementation:​wms:​config:​appconfig:​produmex.sbo.logex.execute.fatclient.exe_with_hana_log_1.zip|Produmex.Sbo.Logex.Execute.FatClient.exe_WITH HANA Log_1.config}}
  
-==10.6.1.2.1. Trigger Ado Net Appender==+==6.1.2.1. Trigger Ado Net Appender==
 In order to trigger the Ado Net Appender, add the following to the root tag:  In order to trigger the Ado Net Appender, add the following to the root tag: 
 <​code><​appender-ref ref="​AdoNetAppender"​ /></​code>​ <​code><​appender-ref ref="​AdoNetAppender"​ /></​code>​
Line 224: Line 224:
 {{ :​implementation:​wms:​config:​appconfig:​root1.png |}} {{ :​implementation:​wms:​config:​appconfig:​root1.png |}}
  
-==10.6.1.2.2. Edit appender tag==+==6.1.2.2. Edit appender tag==
 Then insert the following before the <​root>​ tag:  Then insert the following before the <​root>​ tag: 
  
Line 385: Line 385:
 </​code>​ </​code>​
  
-==10.6.1.2.3. Adjust the log4net connection string==+==6.1.2.3. Adjust the log4net connection string==
 Adjust the dummy connection string in the log4net part to point to your database/​schema. Adjust the dummy connection string in the log4net part to point to your database/​schema.
  
Line 405: Line 405:
 {{ :​implementation:​wms:​config:​appconfig:​connection_string_hana.png |}} {{ :​implementation:​wms:​config:​appconfig:​connection_string_hana.png |}}
  
-====10.6.2. Logging into a separate database==== +====6.2. Logging into a separate database==== 
-===10.6.2.1. Create the log table=== ​+===6.2.1. Create the log table=== ​
 First create a new database/​schema for the log table. Then run the following query on the database/​schema:​ First create a new database/​schema for the log table. Then run the following query on the database/​schema:​
  
Line 439: Line 439:
 Where the //schema// is the new schema and the //PMX_log// is the name of the table where the log entries will be inserted. Where the //schema// is the new schema and the //PMX_log// is the name of the table where the log entries will be inserted.
  
-===10.6.2.2. Modify config file===+===6.2.2. Modify config file===
 Download an example for the fat client config file from here: Download an example for the fat client config file from here:
   * MSSQL: {{:​implementation:​wms:​config:​appconfig:​produmex.sbo.logex.execute.fatclient.exe_with_sql_log_2.zip|Produmex.Sbo.Logex.Execute.FatClient.exe_WITH SQL Log_2.config}}   * MSSQL: {{:​implementation:​wms:​config:​appconfig:​produmex.sbo.logex.execute.fatclient.exe_with_sql_log_2.zip|Produmex.Sbo.Logex.Execute.FatClient.exe_WITH SQL Log_2.config}}
   * HANA: {{:​implementation:​wms:​config:​appconfig:​produmex.sbo.logex.execute.fatclient.exe_with_hana_log_2.zip|Produmex.Sbo.Logex.Execute.FatClient.exe_WITH HANA Log_2.config}}   * HANA: {{:​implementation:​wms:​config:​appconfig:​produmex.sbo.logex.execute.fatclient.exe_with_hana_log_2.zip|Produmex.Sbo.Logex.Execute.FatClient.exe_WITH HANA Log_2.config}}
  
-==10.6.2.2.1. Edit appender tag==+==6.2.2.1. Edit appender tag==
 Insert the following before the <​root>​ tag:  Insert the following before the <​root>​ tag: 
  
Line 604: Line 604:
 </​code>​ </​code>​
  
-==10.6.2.2.2. Trigger Ado Net Appender==+==6.2.2.2. Trigger Ado Net Appender==
 Please see: //​10.6.1.2.1. Trigger Ado Net Appender// Please see: //​10.6.1.2.1. Trigger Ado Net Appender//
  
-==10.6.2.2.3. Adjust the log4net connection string==+==6.2.2.3. Adjust the log4net connection string==
 Adjust the dummy connection string in the log4net part to point to the extra database/​schema where the created log table is located. Adjust the dummy connection string in the log4net part to point to the extra database/​schema where the created log table is located.
  
implementation/wms/app_config.1522055849.txt.gz · Last modified: 2018/03/26 09:17 (external edit)