Chapter 9. Rolling Out JBoss

---

Note: In this chapter:

---

JBoss comes in a state that is extremely developer friendly. JBoss doesn't use an installer and doesn't require any additional configuration to start. In most cases, your application won't require any JBoss-specific configuration to deploy and run. The default configuration comes with the services most commonly needed, already running and in a state that makes them easily accessible.

It is an ideal world for developers, but when the time comes to put your application in production, you really won't want your application server to be so friendly. You'll want to limit the services provided to just the ones you need, especially when those services offer entry points for the outside world to access the server, and you'll want to make sure the remaining services are configured in a production-friendly manner. In this chapter, we'll walk through the default JBoss installation and see what updates are needed to get a JBoss instance ready to be exposed to the outside world.

As we go through the services, keep in mind that although they require a bit of work, you'll need to do this work only once. You learned how to create a new server configuration in Chapter 1. We recommend that you create a server configuration for your deployment environment. You can use this configuration as the starting point for any installation you do, and you'll be sure that each machine has identically configured services.

---

Note: For consistency, we'll continue to work from the default configuration in these examples.

---