红帽全球峰会此内容没有您所选择的语言版本。
Chapter 19. Running the JBoss Enterprise SOA Platform in a Production Environment
19.1. Server Profiles
复制链接链接已复制到粘贴板!
| Profile | Description |
|---|---|
| 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. |
19.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. | ./run.sh -c production |
| -b | Bind the server to a specific IP address. If none is specified, the default (127.0.0.1) is used. | ./run.sh -b 10.34.5.2 |
Procedure 19.1. Start the JBoss Enterprise SOA Platform in a Production Environment
Navigate to the bin Directory
Open a terminal and input this command:cd SOA_ROOT/jboss-as/bin(orchdir SOA_Root\jboss-as\binin Microsoft Windows).Note
It is required that you have set up an administration username and password before proceeding.Launch the JBoss Enterprise SOA Server on Red Hat Enterprise Linux
To start the product, run this command:./run.sh -c productionLaunch the JBoss Enterprise SOA Server on Microsoft Windows
To start the product, run this command:run.bat -c production
Result
The server starts. Note that this may up to around two minutes, depending on the speed of your hardware.
Note
To verify that there have been no errors, check the server log:
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.
19.4. Server Installation
复制链接链接已复制到粘贴板!
A server installation is a way of configuring the JBoss Enterprise SOA Platform on your system. When the software is installed in this way, it can be launched and shutdown with the host operating system. It is set up just like any other service (or daemon in Linux/Unix terminology) on your operating system.
Procedure 19.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.
19.6. Start a Server Installation
复制链接链接已复制到粘贴板!
Prerequisites
- The JBoss Enterprise SOA Platform must be pre-configured to run as a service.
Note
This example assumes the service was installed using the name jboss_soa
Procedure 19.3. Task
- To start the JBoss Enterprise SOA Platform as a service, issue this command:
service jboss_soa startNote
If the JBoss user was created as a system account (using the-Rswitch) then a warning message is displayed. You can safely ignore this.
19.7. Stop a Server Installation
复制链接链接已复制到粘贴板!
This example assumes the service was installed using the name jboss_soa
Procedure 19.4. Task
- To stop the JBoss Enterprise SOA Platform when it is running as a service, issue this command:
service jboss_soa stop
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}