|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (27)
View Page History* The third for current server service assemblies.
* The fourth for current server shared libraries.
* The fourth for current server shared libraries.
* The fifth for current server properties/parameters.
!administration-tab-overview.png|thumbnail! !endpoints-tab.png|thumbnail!
(!) *Warning*: If Petals ESB don't correctly send back the wsdl file, it's sometimes possible
(!) *Warning*: If Petals ESB don't correctly send back the wsdl file, it's sometimes possible
associated component. It try to _force_ the uninstall \\
and unload action. \\ |
and unload action. \\ |
| !editlevellogger.png|thumbnail!\\ | Icon for performing a logger level modification, on the \\
component associated with the row. \\ |
component associated with the row. \\ |
| !application_form_edit.png|thumbnail!\\ !runtime-attributes-button.png|thumbnail!\\ | Access to runtime component attributes can be \\
allowed thank to this icon, but the component must be \\
previously started to return the runtime attributes. \\ |
previously started to return the runtime attributes. \\ |
(!) *Warning*: Only one action is performed for all components instead if you
haven't selected them: !bomb.png|thumbnail,width=16,height=16!
haven't selected them:
As its name indicates, this action aims to clean up the current server.
The following icon: !lightning_delete.png|thumbnail! provides the feature to unload specified installer, in
case of one component was wrongly installed or an installation isn't completed.
!unload_installer_1.png|thumbnail!
You can select all loaded component installers which you like to unload, click on _Unload_ button:
!petals-wconsole-administration-unload-installer-1.png|thumbnail!
Otherwise you can provide the component installer name and click on _Submit_ button:
!petals-wconsole-administration-unload-installer-2.png|thumbnail!
case of one component was wrongly installed or an installation isn't completed.
!unload_installer_1.png|thumbnail!
You can select all loaded component installers which you like to unload, click on _Unload_ button:
!petals-wconsole-administration-unload-installer-1.png|thumbnail!
Otherwise you can provide the component installer name and click on _Submit_ button:
!petals-wconsole-administration-unload-installer-2.png|thumbnail!
The following *gray* icons mean, that associated component isn't in _state_
The following *gray* icons mean, that associated component isn't in _state_
!start-off.png|thumbnail! !stop-off.png|thumbnail! !shutdown-off.png|thumbnail! !uninstalled-off.png|thumbnail!
+For example:+ For the _stop_ icon becomes *coloured*, the associated component must be in _start_ state
For associated informations, only shared library _name_ is displayed:
!sharedlibraries-tab.png|thumbnail!
\\ !bomb.png|thumbnail!: !clearall.png|thumbnail!: provides the same action as for component, but applied to shared libraries.
Following this action all shared libraries on the current server should be uninstalled.
!service-assembly-tab.png|thumbnail! !assemblies-tab.png|thumbnail!
Several informations like service assembly _name_ or the current service assembly _state_ are displayed.
!bomb.png|thumbnail! !clearall.png|thumbnail! : provides the same action as for component, but applied to service assemblies.
Following this action all service assemblies on the current server should be uninstalled
and unloaded.
h3. Server properties tab
h3.
This administrative view tab allows to display and set several properties/parameters for the
current server, for the time being just purge properties can be set.
!purge-function.png|thumbnail!
The following button !database_refresh.png|thumbnail! allow you to immediately purge all monitored exchanges, whereas
the form below allow you to set the parameter for automatic purge.
the form below allow you to set the parameter for automatic purge.
h3. Attributes configuration during component installation:
You can set the duration which exchanges is stored in database (the duration can be
expressed in minute, hour, day).
h3. Artefacts installation
On each *linked* tab, you can install service assembly, shared library and component,
the following screenshot can give you an idea of the installation page:
expressed in minute, hour, day).
h3. Artefacts installation
On each *linked* tab, you can install service assembly, shared library and component,
the following screenshot can give you an idea of the installation page:
!installation-component.png|thumbnail!
are only linked to the *petals-bc-soap* component installation.
After service assembly installation, the result is displayed:
!sa-installation.png|thumbnail!
The previous screenshot result mean that all *service units* of the current service assembly are correctly installed,
but sometimes the installation result can inform that +one or more service unit deployments+ have failed, during the
service assembly deployment on the current server.
The previous screenshot result mean that all *service units* of the current service assembly are correctly installed,
but sometimes the installation result can inform that +one or more service unit deployments+ have failed, during the
service assembly deployment on the current server.
h3. Runtime features
Two *runtime* features are provided thank to these following icon into component table:
Two *runtime* features are provided thank to these following icon into component table:
!editlevellogger.png|thumbnail!: allows modify the logger _level_ of the specified component.
!runtime.png|thumbnail!: allows to modify runtime component _attributes_ for the specified component.
!application_form_edit.png|thumbnail!: allows to modify runtime component _attributes_ for the specified component.
The following screenshot represent the page where you can modify the logger _level_
of a component:
!logger_level2.png|thumbnail!
(!) *Warning:* several values are available (ERROR, FATAL, WARN, INFO,
INHERIT, DEBUG) but you need to set it by paying attention to +the meaning+ of
each value, because the change will impact the component deployed into the
associated server.
You can access to changing component logger level functionnality by clicking
on the following button:
!logger_level1.png|thumbnail!
of a component:
!logger_level2.png|thumbnail!
(!) *Warning:* several values are available (ERROR, FATAL, WARN, INFO,
INHERIT, DEBUG) but you need to set it by paying attention to +the meaning+ of
each value, because the change will impact the component deployed into the
associated server.
You can access to changing component logger level functionnality by clicking
on the following button:
!logger_level1.png|thumbnail!
For the feature that allows to modify the *runtime* component attributes, the