Appserver.ini file
With SIGADW configuration process, the AppServer.ini file, which is the configuration file of the System server, would be modified with the configuration for SIGADW. This edition of AppServer.ini file is automatically performed by the installation Wizard and it must be configured exclusively by the Wizard.
| • | The Section of the environment in which SIGADW is run must show the database (through default Top configuration) in which the Data Warehouse is in. In other words, in the Database, an exclusive database for SIGADW and a TOTVS | DbAccess connection (indicating this database) must be created. |
| • | There must also be environments showing database (s) that is (are) the source (s) of data warehouse. |
| • | The configuration to enable the System HTTP service must be created. Refer to TOTVS support on how to enable this server. |
See below an example of a AppServer.ini file for SIGADW to be run properly:
Sessions and/or keys that are not in this example must not be changed.
Note that this environment description session is used in other sessions of this file. Adjust them to make them show this session.
[EnvDBDW]
Enter directories according to the installation:
StartPath=\SYSTEM\
RpoDb=top
RpoLanguage=Portuguese
RpoVersion=110
AdsShare=
LocalFiles=ADS
localdbextension=.dbf
Cisasync=0
Trace=0
FilesOnDemand=0
JumpSenhap=0
PictFormat=DEFAULT
WSplServer=,,
WSPLReldir=
theme=Classic
Enter help server name:
HelpServer=<help server name>
Enter parameters of TOTVS | DbAccess connection to be used by SIGADW:
dbDatpastase=<base type, for example, MSSQL7 | Oracle | and the other ones homologated by DbAccess>
dbServer=<TOTVS | DbAccess server name>
dbAlias=<alias in TOTVS | DbAccess, for example, SIGADW>
[HTTP]
It enables System webServer.
Enable=1
Port=80
It enables SIGADW to be run by the url Http://<my server>/sigadw If HTTP port is not the default one (80), it must be entered together with the access URL, in the format <my server>:<port>/sigadw.
[localhost:8088/dw]
ENABLE=1
PATH=c:\MP11\web\DW <DW portal path>
ENVIRONMENT = SQLDW <DW environment>
INSTANCENAME=DW <Instance name>
RESPONSEJOB=JOB_DW <JOB responsible for DW instance>
DEFAULTPAGE=default.htm <Default page>
[JOB_DW]
TYPE=WEBEX <Access type>
ENVIRONMENT = SQLDW <DW environment>
INSTANCES=1,2 <Minimum and maximum number of instances>
SIGAWEB=DW <Instance>
INSTANCENAME=SIGADW <Instance name>
ONSTART=STARTWEBEX <Where the instance will start>
ONCONNECT=CONNECTWEBEX <Connection type>
ONEXIT=FINISHWEBEX <Close webex>
DEBUG=1 <Debug mode enabled>
EMPFIL=01/01 <Comp / branch>
DIRINCLUDE= <Directory of includes>
[GENERAL]
You should save Protheus log (if it is a service).
ConsoleLog=1
ConsoleFile=E:\MP11\ap_data\
ConsoleMaxSize=120000
You should have the configuration for initial load of SIGADW and the scheduling in the service startup (performance improvement in the first connection to SIGADW).
Procedures
For scheduling, the following procedures are also necessary:
| 1. | Create the file scheduler.wf in <startPath>, containing a row with Company, Branch, NameofSigaDWEnvironment, f |
where:
| • | Company and branch are the company and branch code associated with SIGADW (see key EmpFil of SIGADW session). |
| • | NameOfSigaDWEnvironment is the name of SIGADW execution environment (see environment key of SIGADW session) and. |
| • | f is fixed. |
Example: 01,01,envDW,f
2. Create WFONStart session as follows:
[ONSTART]
JOBS=schedulerwf?
[schedulerwf]
Main=WFONSTART
Environment=<environment>
nParms=4
parm1=<company>
parm2=<branch>
parm3=<environment>
parm4=<reactivate processes? T or F>