In your flexible
management environment, you can start
the administrative agent by using the startServer command. You can
stop the administrative agent by using the stopServer command.
Before you begin
Before you can start or stop the administrative
agent,
you must first install the product.
About this task
Start
the administrative agent so that you can manage
multiple application servers. Stop the administrative agent as needed,
such as when migrating to a new version of the product, when uninstalling
the product, and so on.
Procedure
- Start
the administrative agent.
Use one of
these methods to start the administrative agent:
- Use
the startServer command:
startServer <administrative_agent>
where administrative_agent is
name of the administrative agent that you want to start.
Use the startServer Qshell script.
![[Windows]](../images/windows.gif)
For example, from a command dialog at the
bin directory
of the administrative agent profile, run the
serverStatus
-all command. Suppose running the command shows that the
administrative agent profile is named
adminagent.
To start the administrative agent, run the following command from
a command dialog at the
bin directory of the
administrative agent profile:
startServer adminagent
Use the Submit Job (SBMJOB) CL command.You
can run the CL command from an IBM® i
command line:
SBMJOB CMD(CALL PGM(product_library/QWASSTRSVR) PARM('-profilePath'
'profile_root' '-server' 'administrative agent')) JOB(server)
JOBD(QWAS85/QWASJOBD) JOBQ(QWAS85/QWASJOBQ) USER(QEJBSVR) LANGID(*USRPRF)
CNTRYID(*USRPRF) CCSID(*USRPRF) OUTQ(QWAS85/QWASOUTQ) ALWMLTTHD(*YES)
- The profile_root element is the profile root of the administrative
agent.
- The administrative agent element is the name
of the administrative
agent server that you want to start.
Use the Windows operating system Taskbar.Click .
Use the administrative
agent First steps dialog.- Click .
- In the First
steps dialog, click Start the admin agent.
- Stop the administrative
agent.
Use one of
these methods to stop the administrative agent:
- Use
the stopServer command:
stopServer <administrative_agent>
where administrative_agent is
name of the administrative agent that you want to stop.
Use the stopServer Qshell script.
![[Windows]](../images/windows.gif)
For example, from a command dialog at the
bin directory
of the administrative agent profile, run the
serverStatus
-all command. Suppose running the command shows that the
administrative agent profile is named
adminagent.
To stop the administrative agent, run the following command from a
command dialog at the
bin directory of the administrative
agent profile:
stopServer adminagent
Use the end job (ENDJOB) CL command.To use
the ENDJOB CL command to end an administrative agent, enter this command
on an IBM i command line:
ENDJOB JOB(jobNumber/QEJBSVR/jobName) OPTION(*CNTRLD) DELAY(delayTime)
The
jobNumber element is the job number, the
jobName element
is the name of administrative agent job, and the
delayTime element
is the amount of time to wait for the job to end in seconds. Use a
value of
600 seconds initially. Read about the appropriate
delay time in the topic on shutting down the product subsystem.
Use the Windows operating system Taskbar.Click .
Use the administrative
agent First steps dialog.- Click .
- In the First
steps dialog, click Stop the admin agent.
Results
You
have started the administrative agent and have optionally
stopped it.
What to do next
Administer application servers
using the administrative
agent. You can do such tasks as configure the administrative agent,
view or change properties for a node registered to the administrative
agent, or view and change the job manager configuration for a registered
node.