Most of the application options and administration tasks need to be performed by using a command line interface called "wsadmin". You use wsadmin to start the command interface and then attach to each application to issue application-specific commands.
To run wsadmin, you always do the same thing, although it exists in the \bin directory under every server profile. In an IBM Connections environment, you usually run the command from the deployment manager’s profile because your deployment manager handles the configuration of all other servers and applications. wsadmin is extremely case sensitive regardless of your platform. To start, use the following commands:
wsadmin -lang jython -username -password -port 8879
wsadmin.sh -lang jython -username -password -port 8879
This is run from \dmgr01\bin.
If you are prompted for which server to connect to, choose server 1. Once you have connected to the wsadmin command window, you can work with the applications by choosing which application you want to issue commands to and you do this by running the following command command:
For example, the Profiles application would be execfile(“profilesAdmin.py”). Each application has its own command lines that are specific to its functionality. It is important to review the documentation and options for the application you want to work with.
After you have made changes or issued commands through the wsadmin interface, you must type "quit" to terminate it and write the changes back to the application itself.
One of the most common uses of wsadmin is to retrieve and edit the XML files that define how IBM Connections looks and behaves. Although it is possible to make changes to the XML files directly if you find them on the file system, using wsadmin is a best practice method for working with these files because it validates the changed XML before overwriting the configuration. Attempting to change XML files manually outside of wsadmin could result in faulty XML causing the application to fail completely.