Show Table of Contents
Chapter 5. Installation
5.1. Variable Name: SOA_ROOT Directory
SOA Root (often written as SOA_ROOT) is the term given to the directory that contains the application server files. In the standard version of the JBoss Enterprise SOA Platform package, SOA root is the
jboss-soa-p-5 directory. In the Standalone edition, though, it is the jboss-soa-p-standalone-5 directory.
Throughout the documentation, this directory is frequently referred to as
SOA_ROOT. Substitute either jboss-soa-p-5 or jboss-soa-p-standalone-5 as appropriate whenever you see this name.
5.2. Variable Name: PROFILE
PROFILE can be any one of the server profiles that come with the JBoss Enterprise SOA Platform product: default, production, all, minimal, standard or web. Substitute one of these that you are using whenever you see "PROFILE" in a file path in this documentation.
5.3. Install the JBoss Enterprise SOA Platform on Red Hat Enterprise Linux
Prerequisites
- a Java Development Kit (Red Hat recommends OpenJDK)
- a database server
- Apache Ant 1.7 or later
- an archiving tool that can open ZIP files
Warning
These instructions explain how to install and configure the product on a test system only. These defaults will not result in the level of security needed for a production system. Please read the full Installation Guide for information on installing and configuring this product for production use.
Follow these steps after you have downloaded either the Standalone or full SOA package from the Red Hat Customer Portal and verified its integrity.
Procedure 5.1. Installation
- Extract the installation directory by running
unzip soa-p-VERSION.zip. - Open the user account settings file in your text editor:
vi SOA_ROOT/jboss-as/server/default/conf/props/soa-users.properties.The contents of this file using the following syntax:username=password.#admin=admin
Confirm that the security roles for your admin account are enabled by removing a leading hash character, if it is present.Warning
Because this account is not secure and the password can be easily guessed, use admin=admin for test purposes only. Do not useadminas a password on production systems as this may compromise security. - Save the file and exit vi.
- Open the security permissions file in your text editor:
vi SOA_ROOT/jboss-as/server/default/conf/props/soa-roles.properties.#admin=JBossAdmin,HttpInvoker,user,admin
Confirm that the security roles for your admin account are enabled by removing a leading hash character, if it is present. - Save the changes to the file and exit vi.
Result
The JBoss Enterprise SOA Platform is now installed and configured for basic use.
5.4. Install the JBoss Enterprise SOA Platform on Microsoft Windows
Prerequisites
- a Java Development Kit
- a database server
- Apache Ant 1.7 or later
- an archiving tool that can open ZIP files
Warning
These instructions explain how to install and configure the product on a test system only. These defaults will not result in the level of security needed for a production system. Please read the full Installation Guide for information on installing and configuring this product for production use.
Follow these steps after you have downloaded either the Standalone or full SOA package from the Red Hat Customer Portal and verified its integrity.
Procedure 5.2. Installation
- Extract the
soa-p-VERSION.zipusing the ZIP tool of your choice. - Confirm that the security roles for your admin account are enabled by removing a leading hash character, if it is present.
Warning
Because this account is not secure and the password can be easily guessed, use admin=admin for test purposes only. Do not useadminas a password on production systems as this may compromise security. - Save the file and exit Notepad.
- Open
SOA_ROOT\jboss-as\server\default\conf\props\soa-roles.propertiesin Notepad.#admin=JBossAdmin,HttpInvoker,user,admin
Remove the hash to enable the security permissions for your admin account. - Save the file and exit Notepad.
Result
The JBoss Enterprise SOA Platform is now installed and configured for basic use.
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.