Configuration
Learn all steps to configure SIGASGI environment in Microsiga Protheus®. Remind that, as previously explained, SIGASGI is a web environment, thus, it cannot be accessed through remote of Microsiga Protheus ®, as in other environments.
To configure SIGASGI, you must run the additional program of Microsiga Protheus®: Configuration Wizard.
Configuring by Wizard
SIGASGI requires the configuration of Protheus Server AppServer.Ini file. This configuration must be performed in wizard.exe program, in smartclient directory of Protheus®.
Configuration procedures are:
Environments
Create a new environment for SIGASGI. TOTVS | DbAccess configuration for this environment must be related to the database created specifically for SIGASGI.
Do not forget to create a connection in TOTVS | DbAccess for the new database.
TOTVS | DbAccess connections must be associated to databases that worked as data sources for SIGASGI.
Internet server (http/ftp):
You must enable http service of Protheus®, as SIGASGI is a web tool.
Web Modules
SIGASGI is configured in this item. Follow these procedures:
1. Click New Module, to add a new web module.
2. Select the SGI module - Indicator Management System.
3. In the box Instance Name, type a name to identify this instance. Root Directory of Images is filled out automatically.
This directory will contain the SIGASGI website (HTML pages, images, etc.), which will be installed after a question. This website must be updated regularly, after the application of any tool patch.
4. Select the environment created specially for SIGASGI. To start SIGASGI service together with Microsiga Protheus® server, select option 'Enables process in Server startup'. Otherwise, the service is enabled only in the first call to SIGASGI via browser.
5. Click Next.
6. On the next screen, enter the host (preferably, the host must be composed by the name or IP of the server and a virtual directory. Ex.: server/SGI).
7. Select to which companies and branches the host is valid and then click Relate. The host is added to the host.
Do not use the Default Host as host of SIGASGI. |
8. Click Next.
9. Enter the minimum and maximum number of users to access SIGASGI simultaneously.
10. Click Finish.
Done! SIGASGI is ready to use.
Follow steps below to use SIGASGI:
1. Create a database exclusively for SIGASGI in the database server.
2. Create a connection TOTVS | DbAccess (Top Connect) for this database. Also, there must be Top Connect connections for the database to work as data source for SIGASGI.
3. In wizard.exe progam:
a. Create an environment for SIGASGI.
b. Enable http service of Microsiga Protheus®
c. Define settings for SIGASGI website.
d. Enter the maximum and minimum number of simultaneous users
To run SIGASGI, open the Internet browser and enter the host defined (for example http://meuServidor/SGI).
3. The default administrator user is SGIADMIN and his password is SGI. For your security, change this password.
In case of problems in the execution, review steps below.
Appserver.ini file
With SIGASGI configuration process, the AppServer.ini file, which is the configuration file of Microsiga Protheus® server, would be modified with the configuration for SIGASGI.
This edition of AppServer.ini file is automatically performed by the installation wizard and it must be configured exclusively by the Wizard.
| • | The environment section where SIGASGI works must point to the database (through standard Top configuration) that contains the SGI. In other words, in the Database, an exclusive database for SIGASGI and a TOTVS | DbAccess connection (indicating this database) must be created. |
| • | In addition, environments must indicate databases which are source for SIGASGI. |
| • | The configuration to enable Microsiga Protheus® 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 SIGASGI to be run properly. Sections and/or keys not included in this example must not be changed. |
Note that this environment description section is used in other sections of AppServer.ini file. Adjust them so that they indicate this section.
Example of AppServer.ini:
[HTTP]
ENABLE=1
PORT=81
[SGI]
Comment – Inform directories according to your installation of Microsiga Protheus®.
SourcePath=C:\Protheus11\apo\
RootPath=C:\ Protheus11\protheus_data
StartPath=\SYSTEM\
RpoDb=TOP
RpoLanguage=English
RpoVersion=110
LocalFiles=ADS
dbServer= <Servidor TOP Connect>
dbDatabase= <Tipo da base de dados. (MSSQL, DB2, etc.) >
dbAlias= <Alias definido no Top Connect>
HELPSERVER=C:\ Protheus11\protheus10HELP\PORTUGUESE
[<MyServer>:<HTTPPort>/SIGASGI]
ENABLE=1
PATH=C:\ Protheus11\protheus_data\web\SGI
ENVIRONMENT= SGI
INSTANCENAME=SGI
RESPONSEJOB=JOB_SGI
DEFAULTPAGE=default.htm
[JOB_SGI]
TYPE=WEBEX
ENVIRONMENT= SGI
INSTANCES= 1,1
SIGAWEB=SGI
INSTANCENAME=SGI
ONSTART=STARTWEBEX
ONCONNECT=CONNECTWEBEX
ONEXIT=FINISHWEBEX
SGIPATH=\web\SGI
SCHEDINIT= <1 enables and 0 disables SGI scheduler>
[ONSTART]
Comment – Inform directories according to your installation of Microsiga Protheus®.
JOBS=JOB_SGI
Recommendation is for configuration of SIGASGI initial load and scheduling of the service startup, in order to improve performance in the first connection with SIGASGI.