Difference between revisions of "Deploy Service"
| (4 intermediate revisions by 2 users not shown) | |||
| Line 11: | Line 11: | ||
** Pool Manager | ** Pool Manager | ||
** Concurrency handler | ** Concurrency handler | ||
| − | |||
| − | Clicking the service "TOUPPER" | + | 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 | + | 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]] |
| − | |||
| − | |||
| + | 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]] | ||
| − | |||
| + | {|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: | + | '''PoolManager:''' manages the configuration of the {{GVESB}} Core instances pools, organized by subsystems: |
| + | [[File:GVConsoleDeployServicePoolManager.jpg|none|thumb|Pool manager]] | ||
| − | + | '''Xpath:''' in this section will be defined the namespaces prefix to be used by {{GVESB}} XPath search framework: | |
| + | [[File:GVConsoleDeployServiceNamespaces.jpg|none|thumb|Namespaces]] | ||
| − | |||
| + | '''Task:''' manages the timer tasks configured on {{GVESB}}: | ||
| + | [[File:GVConsoleDeployServiceTask.jpg|none|thumb|Task]] | ||
| − | |||
| − | + | '''Concurrency handler:''' manages the max concurrency level for a given {{GVESB}} service: | |
| − | + | [[File:GVConsoleDeployServiceConcHandler.jpg|none|thumb|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".
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:
|
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:
Xpath: in this section will be defined the namespaces prefix to be used by GreenVulcano® ESB XPath search framework:
Task: manages the timer tasks configured on GreenVulcano® ESB:
Concurrency handler: manages the max concurrency level for a given GreenVulcano® ESB service:
