Chapter 5. Running the JBoss Enterprise SOA Platform in a Production Environment
5.1. Server Profiles
Table 5.1. Server Profiles
|default||Use this profile for development and testing. This profile uses less memory than the production profile but clustering is not enabled in this mode. In addition, this profile provides more verbose logging than the "all" and "production" profiles. This verbose logging provides you with additional information, but adversely affects server performance. Unless you explicitly specify a different profile, this profile is used when the server is started.|
|production||Use this profile on production servers. This profile provides clustering and maximizes performance by using more memory and providing less verbose logging and screen console output than the "all" or "default" profiles. Note that output (such as the message from the "Hello World" quick start) does not appear on the console screen in this mode. It is written to the log only.|
|minimal||Enables the minimum features needed for a functioning system. No archives are deployed. No ESB or SOA features are enabled. The BPEL Engine is not available.|
|standard||This provides standard functionality for testing. No web, ESB, or SOA features are enabled. The BPEL Engine is not available.|
|web||The jbossweb.sar archives are deployed when this profile is run. No ESB, or SOA features are enabled. The BPEL Engine is not available.|
|all||All of the pre-packaged ESB archives are deployed when this profile is run. This profile offers less performance and scalability than the "production" profile, but requires less memory to run.|
5.2. run.sh Optional Switches
Table 5.2. ./run.sh Optional Switches
|Switch||Purpose||Example of Use|
|-c||Make the server use a specific profile. If none is specified, "default" is used.|| |
|-b||Bind the server to a specific IP address. If none is specified, the default (127.0.0.1) is used.|| |
5.3. Start the JBoss Enterprise SOA Platform in a Production Environment
Procedure 5.1. Start the JBoss Enterprise SOA Platform in a Production Environment
Navigate to the bin DirectoryOpen a terminal and input this command:
chdir SOA_Root\jboss-as\binin Microsoft Windows).
NoteIt is required that you have set up an administration username and password before proceeding.
Launch the JBoss Enterprise SOA Server on Red Hat Enterprise LinuxTo start the product, run this command:
./run.sh -c production
Launch the JBoss Enterprise SOA Server on Microsoft WindowsTo start the product, run this command:
run.bat -c production
The server starts. Note that this may up to around two minutes, depending on the speed of your hardware.
less SOA_ROOT/jboss-as/server/PROFILE/log/server.log. As another check, open a web browser and go to http://localhost:8080. Make sure you can log into the admin console with the username and password you have set.
5.4. Server Installation
5.5. Configure the JBoss Enterprise SOA Platform to Run as a Red Hat Enterprise Linux Daemon
Procedure 5.2. Task
- To make the JBoss Enterprise SOA Platform run as a background daemon (service), you will have to create your own shell script. Red Hat does not supply any scripts to do this.
5.6. Start a Server Installation
- The JBoss Enterprise SOA Platform must be pre-configured to run as a service.
Procedure 5.3. Task
- To start the JBoss Enterprise SOA Platform as a service, issue this command:
service jboss_soa start
NoteIf the JBoss user was created as a system account (using the
-Rswitch) then a warning message is displayed. You can safely ignore this.
5.7. Stop a Server Installation
Procedure 5.4. Task
- To stop the JBoss Enterprise SOA Platform when it is running as a service, issue this command:
service jboss_soa stop