PANTHEON™ Help

 Toc
 Primjer Office 365
 Početna stranica
 Plan računa
[Collapse]PANTHEON
 [Collapse]PANTHEON priručnici
  [Expand]Vodič kroz Datalab PANTHEON Farming
  [Expand]Vodič za mobilni POS
  [Expand]Vodič po PANTHEON Vet
  [Collapse]Vodič po DataLab PANTHEON™-u
   [Expand]Pomoć
   [Expand]Postavke
   [Expand]Narudžbe
   [Expand]Roba
   [Expand]Proizvodnja
   [Expand]Servis
   [Expand]POS
   [Expand]Novac
   [Expand]Kadrovi
   [Expand]Radna površina
   [Expand]Analize
   [Expand]Plansko-analitički alati ZEUS
   [Expand]Poruke programa
   [Expand]Dodatni programi
   [Expand]Sistemska okolina
   [Collapse]Dodatni programi
    [Expand]Pantheon LX/LT
    [Collapse]Pantheon server za automatizaciju (PAAS)
     [Expand]PAAS instalacija i testiranje
     [Expand]Značenje i funkcionalnost PAAS-a
     [Expand]Opis REST metode za procesiranje zadatka
      PAAS Multi server podrška
    [Expand]DataLab ATENA
    [Expand]DataLab CHRONOS
    [Expand]DataLab OTOS
    [Expand]DataLab Migrator
     Post migration wizard
   [Expand]Stari proizvodi
    Riječnik pojmova
 [Collapse]PANTHEON korisnički priručnici
  [Expand]Korisnički priručnik za DataLab PANTHEON™
  [Expand]Kor korisnički priručnik za PANTHEON Vet
  [Expand]Korisnički priručnik za PANTHEON maloprodaju
 Kako RLS funkcionira u praksi
[Collapse]Bilance
  Prenos bilance na druga poduzeća
  Uvoz/Izvoz bilanc
 Unaprijediti
[Collapse]PANTHEON Web
 [Collapse]Vodiči po PANTHEON Web
  [Expand]Vodič po PANTHEON Web Light-u
  [Expand]Vodič za PANTHEON Web Terminal
  [Expand]Arhiva starih proizvoda
  [Expand]Vodič po PANTHEON Web Legal
 [Collapse]Korisnički priručnici za PANTHEON Web
  [Expand]Početak rada s PANTHEON Web-om
  [Expand]Korisnički priručnik za PANTHEON Web Light
  [Expand]Korisnički priručnik za PANTHEON Web Terminal
  [Expand]Korisnički priručnik za PANTHEON Web Legal
  [Expand]Arhiva starih proizvoda
[Collapse]PANTHEON Granule
 [Collapse]Vodič po PANTHEON Granulama
  [Expand]Granule za Servis na terenu
  [Expand]Granula Kadrovi
  [Expand]Granula Putni nalozi
  [Expand]Granula Dokumenti i Zadaci
  [Expand]Granula Kontrolna tabla
  [Expand]Granula B2B narudžbe
  [Expand]Inventar Fiksne Imovine Granula
  [Expand]Inventar Skladišta Granula
 [Collapse]Korisnički priručnik za PANTHEON Granule
   Početak
   Korištenje PANTHEON Granula u imaginarnom poduzeću Tecta
  [Expand]PANTHEON Granule i aktivacija
  [Expand]Granula Kadrovi
  [Expand]Granula Putni nalozi
  [Expand]Granula Dokumenti i zadaci
  [Expand]Granula B2B narudžbe
  [Expand]Granula Nadzorna ploča
  [Expand]Granula Servis na terenu
   Česta pitanja i odgovori
  [Expand]Inventar dugotrajne imovine
  [Expand]Granula Inventura skladišta
   Arhiva
 Baza podataka
 Promjene koda
 Otklanjanje poteškoća
 ARES - RLS Kompatibilni Mod
 RLS Pitanja i Odgovori

Load Time: 428,5437 ms
"
   1000001544 | 221205 | 374091 | Localized
Label

PAAS Multi server support

89213.gif010380.gif010379.gif010381.gif010411.gif010382.gif010383.gif

 

In this chapter we are going to check options for PAAS multi server support.

 

PAAS can run Automation tasks on any accessible server. It accepts a list of servers to access and process tasks on each server.

Table of contents

            1. Implementation for processing automation server using API (for PAW)
            2. Implementation for scheduling automation server using API

 

1. Implementation for processing automation server using API (for PAW)

This type of multi-server support is implemented for PAW clients, and requires tRA_MasterComSite  table in database set as Master in PAAS.ini configuration file.

Config for multi-server to work it needs:
 

PAAS.ini:

    [PAAS]
    Master=MasterDatabase
    …

 

Table MasterDatabase.dbo. tRA_MasterComSite must exist, with string fields:
 

domain_name string name of domain referenced in API calls
server_name SQL server instance name, in HOSTNAME\INSTANCE format
databse_name name of Pantheon database
user_name SQL Server username
user_password SQL Server password
Country Pantheon localization (‘RS’, ‘HR’, …)

 

 

Warning

PAW installation always contains tRA_MasterComSite table in PAW master database. The name of PAW master database could be PAW_Master, PantheonRA_Master, etc. For PAW integration, only setting required is the name of Master database PAAS.ini config.

 

Warning

For custom API clients, database and table can be created with those fields, and set in PAAS.ini

 

PAAS processing API calls are always in format:

    <paas_hostname>/api/v1/<domain>/process/<command>?param1=v1&param2=v2…

Authorization is Basic, with Pantheon username and password.

When <domain> refers to domain_name from Master database, PAAS service will start Pantheon connecting to server and database referred in Master database, and track jobs directly from that SQL server.

If the country matches subfolder from PAAS installation, Pantheon from that subfolder will be started. That way PAAS supports multi-localization on single PAAS instance.

2. Implementation for scheduling automation server using API

 

Autorun requires one PAAS service per one SQL server instance.

Scheduling PAAS service connects to all Pantheon databases on SQL Server instance, and checks tasks required for autorun. This limits autorun PAAS service to that one SQL server instance.

PAAS installation reads settings from PAAS.ini, where windows service name and description, port, SQL server instance can be specified. That way installation of different PAAS services can be installed on single server.

 

Related topics:

  Meaning and operation of PAAS

  PAAS installation and testing

Description of REST methods for processing tasks

Default values and options for PAAS.exe

Upgrading PAAS

PANTHEON Automation Server


 

Rate this topic
Was this topic usefull?
Comments
Comment will also bo visible in forum!