Before you begin
To use administrative commands, you must use the wsadmin client. See Starting the wsadmin client
About this task
Administrative commands interact with the Communities application and its resources through scripts. These scripts use the AdminControl object available in the IBM WebSphere
® Application Server wsadmin tool to interact with the Communities server. Each script uses managed Java
™ beans (MBeans) to perform administrative tasks.
If an error occurs when you are executing the MBean commands, you can examine the SystemOut.log
file to determine what went wrong.
Unlike with configuration properties, when you use administrative commands you do not have to check out any files or restart the server. The commands are executed and take effect immediately.
To run Communities administrative commands, complete the following steps:
Parent topic: Administering Communities
- Start the wsadmin client from the following directory of the system on which you installed the Deployment Manager:
is the WebSphere
Application Server installation directory and dm_profile_root
is the Deployment Manager profile directory, typically dmgr01.
You must start the client from this directory or subsequent commands that you enter do not execute correctly. For more information, see Starting the wsadmin client
- Start the Communities Jython script interpreter using the following command:
If prompted to specify a service to connect to, type 1 to pick the first node in the list. Most commands can run on any node. If the command writes or reads information to or from a file using a local file path, you must pick the node where the file is stored.
- See Communities administrative commands for a complete list of administrative commands for the Communities application.
Communities administrative commands
Use the commands listed to perform administrative tasks for Communities. No file checkout or server restart is needed when using these commands.