Getting Started with WebSphere Application Server
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
178 <strong>Getting</strong> <strong>Started</strong> <strong>with</strong> <strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> Community Edition<br />
Procedure<br />
1. Open a command window and go to the directory /bin.<br />
2. Use this syntax to shutdown the server:<br />
./shutdown --port 1109 --user system --password manager<br />
9.11 Summary<br />
In this chapter you have learned the basics to administer a Community Edition server. Most<br />
administering tasks can be performed from the administrative console, including<br />
configuration changes for parameters such as port numbers, user names and passwords.<br />
Community Edition also enables you to create multiple server instances and repositories so<br />
that applications can be deployed to different instances or targets.<br />
9.12 Review questions<br />
1. What are the steps to start the Community Edition server on Linux?<br />
2. How can you override all the default port numbers in a Community Edition server?<br />
3. What are the steps to add Java libraries into the Community Edition server<br />
repository?<br />
4. Which file has all the user names for a Community Edition server?<br />
5. On a Community Edition installation, which directories should be created for a new<br />
server instance?<br />
6. Which command is used to list all available modules on the server?<br />
A. deploy deploy<br />
B. startup<br />
C. deploy list-modules<br />
D. deploy list-targets<br />
E. None of the above<br />
7. What's the name of the deployment plan for a Web application in Community<br />
Edition?<br />
A. geronimo-application.xml<br />
B. web.xml<br />
C. application.xml<br />
D. geronimo-web.xml<br />
E. None of the above
Change language