User manual REDHAT APPLICATION STACK 2.2 RELEASE NOTES

[. . . ] Red Hat Application Stack 2. 2 Release Notes for Use with Red Hat Application Stack 2. 2 Release Notes Red Hat Application Stack 2. 2 Release Notes for Use with Red Hat Application Stack 2. 2 Edition 1. 0 Copyright © 2008 Red Hat 1. Overview of This Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Package-specific Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [. . . ] Run as root: mysqldump --all-databases -p > /tmp/mysqldumpfile. sql 2. Stop the daemons: /sbin/service httpd stop · To shut down MySQL: /sbin/service mysqld stop · To shut down PostgreSQL: /sbin/service postgresql stop 3. Install the software: · Option 1. To install from RHN, which is the preferable option to avoid dependency issues: · Subscribe to the Red Hat Application Stack child channel: e. g: rhel-x86_64-5-appstk-2 or rhel-i386-5-appstk-2 · Subscribe to the Enterprise Application Platfrom child channel: e. g: jbappplatform-4-i386-as-5-rpm or jbappplatform-4-x86_64-as-5-rpm · Run as root: yum update · Run as root: yum groupinstall stacks 5 Chapter 3. Installing Red Hat Application Stack · Option 2. To install from RPMs on Disk: Follow the instructions in Section 2. 2. 2, "Using yum / DVD" to mount the DVD and set up the local RHN channel (steps 1-3). Then as root run: yum update Followed by: yum groupinstall stacks After the installation is complete, remove the file you added in /etc/yum. repos. d/ (or set enabled=0 in that file). Failure to do this will result in yum exiting with an error whenever it is run again without mounting the Red Hat Application Stack V. 2. 2 DVD. Note You may need to install the following packages to satisfy dependencies before executing the above command, if they are not already installed: · apr-devel · apr-util-devel · libc-client · mx · pcre-devel Note You can also install specific components of the stack via the yum groupinstall directive specified in Section 3. In addition to "stacks", the following groups are defined: j2ee - Installs jbossas, jboss-seam, mod_jk and database jdbc drivers lamp - Installs httpd, mysql, php and all components related to mysql lapp - Installs httpd, postgresql, php and all components related to postgresql docs - Installs documentation for various components When using the groupinstall directive, you can specify multiple groups at the same time (even if they share packages). Analogous to groupinstall, you can use the "groupremove" directive to remove all the packages in a group. The groupremove directive will only remove packages in the group; not the dependencies that the package install may have brought in. Restore your database: · For PostgreSQL: 6 · Move (or remove) the database directory: mv /var/lib/pgsql/data /var/lib/pgsql/data. backup · Initialize the database: /sbin/service postgresql initdb · Start the new PostgreSQL service: /sbin/service postgresql start · Restore your data from back-up psql -U username < /tmp/pg. backup · Start the http daemon: /sbin/service httpd start · For MySQL: · Start MySQL: /sbin/service mysqld start · Update MySQL: mysql_upgrade · Restore your data: mysql -p < /tmp/mysqldumpfile. sql 5. Start the remaining daemons: · Start the http daemon: /sbin/service httpd start The installation is now complete. 7 8 Chapter 4. Using JBoss Application Server 4. 1. Using the Linux service (production) JBoss Application Server can be started, stopped, and configured to start automatically at boot time either from the command line or using a graphical tool. You can start and stop the jbossas service using the service command as root on a console window (as is typical of a network service): service jbossas start . . . service jbossas stop The behavior at boot can be controlled with the chkconfig command, as any other Linux service (see chkconfig man page). Alternatively, you can issue the command system-config-services to activate the graphical Red Hat Service Configuration Tool, which can also be activated from the main menu. Select: System Settings > Server Settings > Services Note For security purposes, beginning with Red Hat Application Stack V. 1. 1, authentication for the jmx-console, web-console, jmx-invoker and http-invoker is turned on. Additionally, no user accounts are active by default, so as to prevent default user / password based attacks. · Accounts for the jmx-console and the invokers can be set up by modifying: $JBOSS_HOME/server/$CONFIG/conf/props/jmx-consoleusers. properties · Accounts for the web-console users can be set up by modifying: $JBOSS_HOME/server/$CONFIG/deploy/management/console-mgr. sar /web-console. war/WEB-INF/classes/web-consoleusers. properties Please note that the file name above has been split onto two lines for readability. It should be understood and entered as one continuous line. If you create custom configurations, you will manually have to port files / changes from a new update to that configuration. 4. 2. [. . . ] Create a new config file for service-name, /etc/sysconfig/service-name. The contents of this file should be similar to /etc/sysconfig/jbossas, except with instance specific values uncommented and updated, e. g: cp /etc/sysconfig/jbossas /etc/sysconfig/jbossas-ports-01. Uncomment and update JBOSSCONF to ports-01 in /etc/sysconfig/jbossas-ports-01. Then add service-name for management by chkconfig, e. g: chkconfig --add jbossas-ports-01 4. [. . . ]