Changing the execution privileges for the service [Windows]
If the linked Systemwalker Centric Manager server is running V13.2.0 or earlier, change the service execution privileges for the Agent to either the Systemwalker Centric Manager account or an account for a user with administrator privileges. For V13.3.0 or later, there is no need to make a change.
Stop the Agent:
"%F4AN_INSTALL_PATH%\F4ANswnc\bin\swncctrl" stop |
Open the Windows Services dialog box.
Open the Properties window for the "Systemwalker Jservlet (SWNET)" service.
Select This account in the Log On tab of the Properties window, and set it to either the Systemwalker administrator account, or an account with administrator privileges.
Executing the setup command
[Windows]
Stop the Agent:
"%F4AN_INSTALL_PATH%\F4ANswnc\bin\swncctrl" stop |
Set up the environment by issuing the commands below:
<Agent installation directory>\CMDB\FJSVcmdba\bin\cmdbsetupenv.bat -k AGT_CENTINV |
Note
The Agent (AGT_CENTINV) that collects inventory information for Systemwalker Centric Manager must be set up in an environment where the Resource Distribution function has been installed on the Systemwalker Centric Manager Operation Management Server and an inventory database has been created. If an inventory database has not been created, there is no need to set up AGT_CENTINV.
Modify the Definition File for Collection of Configuration Information
In agent with setting up, it collects information at the following time everyday as a default.
AGT_CENTREP(Agent for collecting Systemwalker Centric Manager node information)
2.00 AM
AGT_CENTINV(Agent for collecting Systemwalker Centric Manager Inventory Information)
3.00 AM
Refer to the Definition File for Collection of Configuration Information in the Systemwalker Runbook Automation Reference Guide and change to collecting schedule to any date.
Note that if you do not need to execute automated collect routinely, Add "#" to the first letter of following line with comment out.
AGT_CENTREP 0 2 * * * AGT_CENTINV 0 3 * * *
Start the Agent:
"%F4AN_INSTALL_PATH%\F4ANswnc\bin\swncctrl" start |
Collect information from Systemwalker Centric Manager:
<Agent installation directory>\CMDB\FJSVcmdba\bin\cmdbrefresh.exe -q |
As a result of this command, the information collected will be registered with the CMDB Manager, which will recognize the existence of the Agent.
Point
Refer to "cmdbrefresh (Observed Record Collection Request Command)" in the Systemwalker Runbook Automation Reference Guide for details on the cmdbrefresh command. Check the following messages in the event log to check when the collection processing completes.
FCMDB: INFO: [10004] Update check processing has started. '<Agent service type>'
FCMDB: INFO: [10005] Update check processing has completed. '<Agent service type>'
[Linux]
Stop the Agent:
/opt/FJSVswnc/bin/swncctrl stop |
Set up the environment:
/opt/FJSVcmdba/bin/cmdbsetupenv.sh -k AGT_CENTINV |
Start the Agent:
/opt/FJSVswnc/bin/swncctrl start |
Modify the Definition File for Collection of Configuration Information
In agent with setting up, it collects information at the following time every day as a default.
AGT_CENTREP(Agent for collecting Systemwalker Centric Manager node information)
2.00 AM
AGT_CENTINV(Agent for collecting Systemwalker Centric Manager Inventory Information)
3.00 AM
Refer to the Definition File for Collection of Configuration Information in the Systemwalker Runbook Automation Reference Guide and change to collecting schedule to any date.
Note that if you do not need to execute automated collect routinely, Add "#" to the first letter of following line with comment out.
AGT_CENTREP 0 2 * * * AGT_CENTINV 0 3 * * *
:
Collect information from Systemwalker Centric Manager
/opt/FJSVcmdba/bin/cmdbrefresh.sh -q |
As a result of this command, the information collected will be registered with the CMDB Manager, which will recognize the existence of the Agent.
Point
Refer to "cmdbrefresh (Observed Record Collection Request Command)" in the Systemwalker Runbook Automation Reference Guide for details on the cmdbrefresh command. Check the messages in the syslog to check when the collection processing completes.
