Reading Server

Purpose

In some environments, Application Server is overloaded due to requirements to read documents. As consequence server gets low because of transmission between server and some work stations.

After detailed survey, it was discovered that if there was one or more documents reading servers, slowness coming from diverse requirements to server for reading or by means of transmission server/station would end up.

Solution

Solution to read documents managed by Documents Control by means of configuration of SX5 - QX table is available. For documents in reading stage, concept of Documents Reading Server was implemented.

Concept of Documents Reading Server works as follows:

If key QX in table SX5 exists, System will check if there is Documents Reading Server destined to sub net where requesting machine is connected. Consider, for example:

Imagine client machine has IP 192.1.1.200. System will research Documents Reading Server in table SX5 with prefix 192.1.1.  If it does not find it, System will perform same procedure but will search for server with prefix 192,1.  If it does not find it, procedure will be performed again to search for server with prefix 192.

After trying three times, there are two situations:

If there is no Documents Reading Server, System will use server application file.
If there is Documents Reading Server, System will check and copy server application document to Documents Reading Server. Other procedures will be accomplished in network local server.

 

Applying the Functionality

Example: Company with branch in Manaus and Campinas and its headquarter in São Paulo. Link between Head Office and Campinas is made with Optical Fiber, speed of 1GB and connection with Manaus, state of Amazonas, is made via Satellite.

 

It was concluded, by analyzing net flow between Head Office and Branch, that in some periods System is slow. This slowness is because of excessive transfer of documents.        

Upon the resource Documents Reading Server, through the configuration of SX5 - Table – QX, the System administrator considerably decreases the flow of such documents between the Head Office and the Branches. Example of Table QX configuration:

 

X5_TABLE

X5_KEY

X5_DESCRIPTION

QX

001

\\192.1.1.1\docs

QX

002

\\192.1.2.1\documentos

QX

003

\\192.2.1.1\erp\docs

 

 

Important

This functionality can be used only in Reading documents.
In application server, Protheus users must have priority to write in reading servers.
Some systems are case sensitive, it must be regarded in the configuration of table QX.

 

Sharing

To enable this resource, in an environment in which table QDH (Documents) is used in exclusive mode and the table SX5 (Generic Tables) in shared mode, you must enable the parameter MV_QCOMPQX. This parameter enables you to check Document branch while generic table QX is loading.

 

Important

Whenever the table QDH (Documents) is set as exclusive, the parameter MV_QPATHW must be set per branch, pointing to different folders. If it directs to equal folders, document can be substituted by a document of other branch. For example:

Branch

Parameter

Type

Content

01

MV_QPATHW        

C

\SYSTEM\DOCS_01

02

MV_QPATHW        

C

\SYSTEM\DOCS_02