Difference between revisions of "Deploy Service"

From GreenVulcano Wiki
Jump to: navigation, search
 
(4 intermediate revisions by 2 users not shown)
Line 11: Line 11:
 
** Pool Manager
 
** Pool Manager
 
** Concurrency handler
 
** Concurrency handler
** CryptoHelper
 
  
  
Clicking the service "TOUPPER", as example, it is possible to compare both files, that present in local "XLM NEW", and the preceding server version "XML SERVER".  
+
Clicking the service name, "TOUPPER" as example, the user can see a XML comparison of the service and support element configuration both on the server side and in the zip side.  
The box into the right evidences if the service already exits.
+
The text box into the right evidences if the service already exits on the server and if is different from the zip file version.
  
  
After analysing the files it is possible to ''deploy'' clicking "Deploy" task, or returning to the main menu pressing "Cancel".  
+
After analysing the XML documents it is possible to ''deploy'' clicking "Deploy" button, or return to the main menu clicking "Cancel". [[File:GVConsoleDeployServiceCompareFiles.jpg|none|thumb|Comparison of both files]]
 
  
[[File:GVConsoleDeployServiceCompareFiles.jpg|center|thumb|600px|Comparison of both files]]
 
  
 +
Clicking "Deploy", the user is redirect to another page for saving the new version of the configuration file. Pressing "Save" or "Cancel" saves or or aborts the modifications:[[File:GVConsoleDeployServiceSaveDoc.jpg|none|thumb|Saving a document]]
  
Clicking "Deploy" another page is open for saving the document new version. Pressing "Save" or "Cancel" saves or returns respectively:
 
  
 +
{|class="note" 
 +
|[[File:info.png]]
 +
|These saving procedure must be repeated every time is deployed a service. It is valid for every section of the Deploy New Services area.
 +
|}
  
[[File:GVConsoleDeployServiceSaveDoc.jpg|center|thumb|600px|Saving a document]]
+
'''PoolManager:''' manages the configuration of the {{GVESB}} Core instances pools, organized by subsystems:
 +
[[File:GVConsoleDeployServicePoolManager.jpg|none|thumb|Pool manager]]
  
  
Clicking on "Save" the parameter definition section in open automatically.
+
'''Xpath:''' in this section will be defined the namespaces prefix to be used by {{GVESB}} XPath search framework:
 +
[[File:GVConsoleDeployServiceNamespaces.jpg|none|thumb|Namespaces]]
  
These saving procedure must be repeated every time a deploy is done. It is valid for every section relative to the Deploy New Services area:
 
  
 +
'''Task:''' manages the timer tasks configured on {{GVESB}}:
 +
[[File:GVConsoleDeployServiceTask.jpg|none|thumb|Task]]
  
:'''PoolManager:''' manages the pools of objects that can invokes the {{GVESB}} Core:
 
  
:[[File:GVConsoleDeployServicePoolManager.jpg|center|thumb|600px|Pool manager]]
+
'''Concurrency handler:''' manages the max concurrency level for a given {{GVESB}} service:
 
+
[[File:GVConsoleDeployServiceConcHandler.jpg|none|thumb|Concurrency handler]]
 
 
 
 
:'''Xpath:''' in this section the namespaces will be prefixed for been used by {{GVESB}}:
 
 
 
:[[File:GVConsoleDeployServiceNamespaces.jpg|center|thumb|600px|Namespaces]]
 
 
 
 
 
 
 
:'''Task:''' defines the elaboration tasks, processes, and instruction sequences to be followed in specific time, eventually to be iterated more times:
 
 
 
:[[File:GVConsoleDeployServiceTask.jpg|center|thumb|600px|Task]]
 
 
 
 
 
:'''Concurrency handler:''' manages the service occurrence number that can be contemporaneously elaborated:
 
 
 
:[[File:GVConsoleDeployServiceConcHandler.jpg|center|thumb|600px|Concurrency handler]]
 

Latest revision as of 19:42, 25 January 2012

Deploy Service has the following sections:

  • Services
    • TOUPPER (service name)
    • TOUPPER_A (service name)
    • ...
  • Parameter:
    • Xpath
    • Task
    • Pool Manager
    • Concurrency handler


Clicking the service name, "TOUPPER" as example, the user can see a XML comparison of the service and support element configuration both on the server side and in the zip side. The text box into the right evidences if the service already exits on the server and if is different from the zip file version.


After analysing the XML documents it is possible to deploy clicking "Deploy" button, or return to the main menu clicking "Cancel".

Comparison of both files


Clicking "Deploy", the user is redirect to another page for saving the new version of the configuration file. Pressing "Save" or "Cancel" saves or or aborts the modifications:

Saving a document


Info.png These saving procedure must be repeated every time is deployed a service. It is valid for every section of the Deploy New Services area.

PoolManager: manages the configuration of the GreenVulcano® ESB Core instances pools, organized by subsystems:

Pool manager


Xpath: in this section will be defined the namespaces prefix to be used by GreenVulcano® ESB XPath search framework:

Namespaces


Task: manages the timer tasks configured on GreenVulcano® ESB:

Task


Concurrency handler: manages the max concurrency level for a given GreenVulcano® ESB service:

Concurrency handler