Hide Forgot
Date of First Response: 2008-01-15 13:37:30 project_key: SOA A first comment comment on the Getting Started Guide - the Installing and Configuring the 32-bit Sun JDK on Linux section - RHEL users don't have to download the JDK from Sun, as of RHEL5, it's available via their RHN subscription. If they do this, they can avoid having to install the "compatibility" RPM from ftp://jpackage.hmdc.harvard.edu/JPackage/1.7/generic/RPMS.non-free I found the following text in the App Stack 2.0 release notes (https://rhstack.108.redhat.com/docs/Red_Hat_Application_Stack_V.2_Release_Notes.html#Installing_BEA_IBM_Sun_SDK). Maybe we can just re-use it (after removing the references to the BEA JDK? ---------------- 1. Install a Java SDK from RHN Java SDKs are provided by the Red Hat Enterprise Linux 5 Supplementary channel for your Linux variant and architecture. Depending on the architecture, the channel names are: rhel-i386-server-supplementary-5 and rhel-x86_64-server-supplementary-5 The java-1.5.0-bea, java-1.5.0-ibm and java-1.5.0-sun SDKs are available from these channels. Make sure you also install the -devel subpackages. 2. Selecting alternatives for java, javac and java_sdk_1.5.0 (setting java_sdk_1.5.0 is optional). This is only needed if you want to use the SysV service script and/or want this installed SDK to be the default java and javac in the system. This choice can often be overridden by setting the JAVA_HOME environment variable. The alternatives system allows different versions of Java, from different sources to co-exist on your system. You should make sure the desired one is selected so that the service script uses the one you want. As root, issue the following command: /usr/sbin/alternatives --config java and make sure the desired one is selected (marked with a '+'), or select it by entering its number as prompted. Make sure you do the same for javac and java_sdk_1.5.0. We recommend that all point to the same manufacturer and version.
Link: Added: This issue is a dependency of SOA-200
SOA-156 and SOA-157 referred to missing/incorrect user and roles files. These files are superceded by these - platform wide in that they cover all consoles - files as of IR8: [ldimaggi@ldimaggi jboss-as]$ find /opt/IR8 -name soa-roles.properties -print /opt/IR8/jboss-soa-p.4.2.0/jboss-as/server/production/conf/props/soa-roles.properties /opt/IR8/jboss-soa-p.4.2.0/jboss-as/server/all/conf/props/soa-roles.properties /opt/IR8/jboss-soa-p-standalone.4.2.0/server/default/conf/props/soa-roles.properties [ldimaggi@ldimaggi jboss-as]$ find /opt/IR8 -name soa-users.properties -print /opt/IR8/jboss-soa-p.4.2.0/jboss-as/server/production/conf/props/soa-users.properties /opt/IR8/jboss-soa-p.4.2.0/jboss-as/server/all/conf/props/soa-users.properties /opt/IR8/jboss-soa-p-standalone.4.2.0/server/default/conf/props/soa-users.properties We now keep the pre-SOA install version of the login configuration in a directory called conf/old/ in the profile.
Is this issue still needed?
Josh mentioned a couple of days ago that there will be a new version of the getting started guide (final draft) - we'll close this JIRA now and open up a new one to track doc comments in that final getting started guide...when it's ready for review.