Linha Microsiga Protheus - Inglês

Páginas filhas
  • uMov.me (FINA560 - SIGAFIN)

It is possible to render accounts of an advance by mobile integrated with Protheus. Therefore, it is necessary configure the routines Start Configuration and Application Configuration on TotvsTWS.

Totvs TWS will be the platform responsible for making the communication link between ERPs and the back office of uMov.me applications.

TWS will not, in any moment, create a new application in the mobile platform. It will only connect and make the mapping of applications already existent in uMov.me, therefore, in order to work the structure of the application in TWS, the application must have defined import structures (for information on the creation of application on uMov.me, the knowledge base of the platform must be accessed:  http://kb.umov.me ).


Requirements

Start Configuration on TWS

It is necessary field out the fields according to the following example:

    • Product: Protheus.
    • WS Url: URL from TWS service that makes the integrations from datasSets between TOTVS products and the platform uMov.me. Exemple: http://localhost:9090/TWSSERVICE.APW.
    • EAI Url: URL of the EAI service for Integrations via XML. Example: http://localhost:9090/EAISERVICE.APW.
    • Host: Host server DbAcess in which the TWS is being run. Example: localhost.
    • Door: TWS communication door with the DbAcess server. Example: 7890
    • Database: Database server being used for data integration on TWS x uMov.me. Example: DB2
    • Alias: ODBC Identification with database. Example: P1190.

Application Configuration

It is necessary fill out the fields according to the following example:

    • Code: Mobile application identification code to be integrated to Protheus. example: PRCAIX
    • Tenant: Mobile application description to be integrated with Protheus. Example: totvs06des1000
    • FTP integration address: DbAcess Host Server where TWS is run. Example: files.umov.me
    • FTP User: TWS Communication with DbAccess Server.