The following steps describe one way to secure the WebSphere® Application Server using IBM® i as
the security provider.
Note: Your WebSphere Application
Server must be running to complete these steps. The steps in this
example are for WebSphere Application
Server V6.1, for WebSphere Application
Server V7.0 the paths are slightly different.
- Navigate to the WebSphere Application
Server administration directory using the cd command. For example: cd
/QIBM/UserData/WebSphere/AppServer/V61/Base/profiles/<yourWASInstanceName>/bin.
- Use the wsadmin command to start the WebSphere Application Server administration
tool. For example:
./wsadmin
WASX7209I: Connected to process "server1" on node LOTI19 using
SOAP connector ; The type of process is: UnManagedProcess
WASX7029I: For help, enter: "$Help help"
wsadmin>
- Secure the WebSphere Application
Server profile with a valid user ID and password by entering the following
command: securityon <yourUserID> <yourPassword>.
This user ID and password will be used to access the secure WebSphere Application Server
administrative console, and has authority to stop the application
server after it is secured.
- Use the quit command to stop the WebSphere Application Server administration
tool.
- For the changes to take effect, you must stop the server using
the ./stopServer command and restart it using the ./startServer command
in /QIBM/UserData/WebSphere/AppServer/V61/Base/profiles/<yourWASInstanceName>/bin.
When the server has restarted, a message displays that is similar
to:
CPC1221: Job 107206/QEJBSVR/SERVER1 submitted to job queue QWASJOBQ in
library QWAS61.
CWNATV00I: Application server server1 in profile default has started and is
ready to accept connections on admin port 9060.