(PEtALS, etc.), an Application Server (Jonas, JBoss, etc.).
\\
In this chapter you will heard about Runtime Manager, Processor, Execution Environment, Environment Federation. Here are the description of each concepts :
\\
• *Runtime manager* : this entity is an agent that have a high level vision of a Service Execution Platform or a group of Service Execution Platform (Federation, Grid, etc.). It is the communication intermediate between Petals Master and the Service Execution Platform(s). It implements a connection interface provided by the Petals Master project.
\\
• *Processor* : this entity is a server that host Service Execution Platform. For exemple it could be an IBM Server.
\\
• *Execution* *Environment* : this entity is a Service Execution Platform like an ESB node (PEtALS single node, etc.), an Application Server (Jonas server, etc.). For the moment, Petals Master connection API is only implemented by Petals ESB.
\\

\\
To add a runtime manager to Petals Master registry, you just have to provide the address of the manager connection service :

!addRuntimeManager.png|thumbnail!


The manager connection service must be a Web Service that implements the WSDL connection interface provided by the
Petals Master project. An implementation of this interface is already available for the PEtALS Service Platform.
\\
Once you have successfuly added a new Runtime Manager, you are redirected to the edition page of the newly imported
Runtime Manager.
\\

h1. {color:#003f80}{*}Edit{*}{color} {color:#003f80}{*}a{*}{color} {color:#003f80}{*}Runtime{*}{color} {color:#003f80}{*}Manager{*}{color} {color:#003f80}{*}and{*}{color} {color:#003f80}{*}Synchronize{*}{color} {color:#003f80}{*}Execution{*}{color} {color:#003f80}{*}Environment{*}{color} {color:#003f80}{*}with{*}{color} {color:#003f80}{*}Petals{*}{color} {color:#003f80}{*}Master Registry{*}{color}

\\
• The first tab, "Identity Card", provides information about the Runtime manager itself like its name and address. Here you could remove a runtime manager by clicking the delete button.

!viewRuntimeManager.png|thumbnail!\\

• The second tab, "Execution Environments", show the list of Execution Environments managed by this Runtime Manager. The first time you show this tab, no execution environments are available.
\\

\\ !viewRuntimeManagerExecEnv.png|thumbnail!\\
You must synchronize your manager with the Petals Master registry to see managed execution environments. Simply push the "Synchronize Execution Environments" button.

!viewRuntimeManagerExecEnvSynchro.png|thumbnail!\\

All managed execution environments are synchronized, but also linked endpoints with their descriptions (so related
Services, Interface, etc.), host processors (Servers, Mainframes, etc.) and environment federations. You can click on the execution environment name to see all information about it.

h1. {color:#003f80}{*}Edit{*}{color} {color:#003f80}{*}an{*}{color} {color:#003f80}{*}Execution{*}{color} {color:#003f80}{*}Environment{*}{color}

\\
• The first tab of the Execution Environment editor provides identity information like its name, type (ESB, Application Server, etc.), address (host address), host processor (the server that host the exec env) and parent federation if the exec env is member of a group of exec envs (in case of federation, distribution, grid, etc.). Here you could remove an execution environment by clicking the delete button.

!viewExecEnv.png|thumbnail!\\

If you click on the host processor "view details" link, you are redirected to the Processor editor page.
If you click on the parent federation "view details" link, you are redirected to the Environment Federation editor page.

• The second tab of the Execution Environment editor provides the list of all endpoints hosted on this execution environment.
\\
\\ !viewExecEnvEndpoint.png|thumbnail!\\

h1. {color:#003f80}{*}Edit{*}{color} {color:#003f80}{*}a{*}{color} {color:#003f80}{*}Processor{*}{color}

\\
• The first tab of the Processor editor provides identity information like its name and address (IP v4 address). Here you could remove a processor by clicking the delete button.

!viewProcessor.png|thumbnail!\\

• The second tab of the Processor editor provides the list of all Execution Environments hosted on this processor.

!viewProcessorExecEnv.png|thumbnail!\\

• The third tab of the Processor editor provides the list of all endpoints hosted on the processor. This list contains all endpoints hosted on all execution environments hosted on this processor.

!viewProcessorEndpoint.png|thumbnail!
 
\\

h1. {color:#003f80}{*}Edit{*}{color} {color:#003f80}{*}an{*}{color} {color:#003f80}{*}Environment{*}{color} {color:#003f80}{*}Federation{*}{color}

\\
• The first tab of the Processor editor provides identity information like its name and federation pattern (Distributed, Federated, Grid, etc.). Here you could remove a federation by clicking the delete button.

!viewEnvFede.png|thumbnail!\\

• The second tab of the Processor editor provides the list of all Execution Environments that are members of this federation.

!viewEnvFedeExecEnv.png|thumbnail!\\

h1. {color:#003f80}{*}Search{*}{color} {color:#003f80}{*}Runtime{*}{color} {color:#003f80}{*}Manager,*{color} {color:#003f80}{*}Processor,*{color} {color:#003f80}{*}Execution{*}{color} {color:#003f80}{*}Environments{*}{color} {color:#003f80}{*}and{*}{color} {color:#003f80}{*}Environment Federations{*}{color}

\\
Petals Master GUI provides search interfaces for Runtime Manager, Processor, Execution Environement and Environment
Federations. These search capabilities are similar to the other search capability of the Petals Master GUI.
\\
\\
\\