The following diagram shows the overall flow of software parameters management.
Collection of software installation statuses is performed in coordination with the software (patch) management tools provided by the respective software vendors. Refer to "1.1.4 Software Patch Management". However, parameter setting and collection for managed Solaris servers is not supported.
Figure 1.7 Overview of Software Parameter Management
Collect the software installation status [performed using Systemwalker Software Configuration Manager]
Systemwalker Software Configuration Manager collects the software installation status from each business server.
Register the parameters to set [operation by an infrastructure administrator]
Infrastructure administrators define the parameters to set in the software. Specify the list of parameters, and the scripts to set the parameters, using the parameter setting definition. Use commands to register the parameter setting definition.
This step is not required if using the parameter setting definition pre-registered in this product.
Register the parameters to be collected [operation by an infrastructure administrator]
Infrastructure administrators define the parameters to be collected from the software. Specify the list of parameters, and the scripts to collect the parameters, using the parameter collection definition. Use a command to register the parameter collection definition.
This step is not required if using the parameter collection definitions pre-registered in this product.
Associate the software with the parameters [operation by an infrastructure administrator]
Infrastructure administrators associate the parameter setting definitions and the parameter collection definitions with the software. The software is associated with the parameters using a command.
This step is not required if using the software definitions pre-registered in this product.
Register the parameter values [operation by an infrastructure administrator]
Infrastructure administrators can define the values to be set in the parameters as predefined parameters. Predefined parameters are convenient to use when the user needs to configure the same value numerous times, or when a set of values to configure has been predetermined. Files, as well as values, can be specified in parameters. Use a command to register predefined parameters. Note that files can also be registered as packages.
Request parameter settings [operation by an infrastructure administrator, tenant administrator or tenant user]
Tenant administrators or tenant users log in to the management console and request parameter settings. Notifications that requests have been received, completed, or have ended in an error, are received by email.
Infrastructure administrators can request the setting of parameters using the command on the admin server.
Set the parameters [processing by Systemwalker Software Configuration Manager]
Systemwalker Software Configuration Manager configures the specified parameters in the managed servers.
Check execution status [operation by an infrastructure administrator, tenant administrator, or tenant user]
Check the parameter setting status using the management console or the command on the admin server.
Collect the parameters [processing by Systemwalker Software Configuration Manager]
Perform discovery on the managed servers to collect the software parameters. Files, as well as parameter values, can be collected.
Check the parameters [operation by an infrastructure administrator, tenant administrator or tenant user]
Infrastructure administrators, tenant users, or tenant administrators log in to the management console to check the parameters. Infrastructure administrators can check parameter values using the command on the admin server.
The following table explains the operation flow for each role.
Operation flow | User roles | Reference | ||||
|---|---|---|---|---|---|---|
Infrastructure administrator | Dual-Role administrator | Tenant administrator | Tenant user | |||
1 | Collect the software installation status | Y | Y | - | - | "Information Collection Source Management Command" in the Developer's Guide "Patch Information Update Command" in the Reference Guide |
2 | Register the parameters to set | Y | Y | - | - | "Definition of Parameters to be Set" under "Definition of Parameter Information" in the Developer's Guide "Parameter Settings Definition Management Command" in the Developer's Guide |
3 | Register the parameters to be collected | Y | Y | - | - | "Definition of Parameters to be Collected" under "Definition of Parameter Information" in the Developer's Guide "Parameter Collection Definition Management Command" in the Developer's Guide |
4 | Associate the software with the parameters | Y | Y | - | - | "Association with the Software" under " Definition of Parameter Information" in the Developer's Guide "Command to Associate Software and Parameter Definitions" in the Developer's Guide |
5 | Register the parameters values | Y | Y | - | - | "Predefined Parameter Management Command" in the Reference Guide |
6 | Request parameter settings | Y(*1) | Y | Y (*2) | Y (*2) | "Parameter Settings Wizard" in "Resources" in the Operator's Guide "Parameter Setting Command " in the Reference Guide |
7 | Set the parameters | - | - | - | - | - |
8 | Check execution status | Y | Y | Y(*2) | Y(*2) | "Job Management" in the Operator's Guide "Job Information Management Command" in the Reference Guide |
9 | Collect the parameters | Y | Y | - | - | "Parameter Information Update Command" in the Reference Guide |
10 | Check the parameters | Y | Y | Y(*2) | Y(*2) | "Resources" in the Operator's Guide "Parameter Export Command" in the Reference Guide |
Y: Implement the task
-: Do not implement the task
*1: Only commands can be executed.
*2: Only the management console can be operated.
