Page History

...

alsa-lib-devel

ant

ant-nodeps

boost-devel

device-mapper-multipath

dhcp

gcc-c++

gd

glibc-devel.i686

graphviz-perl

gzip

java-1.7.0-openjdk-devel

java-1.6.0-openjdk-devel

libaio-devel

libibcm.i686

libibumad-devel

libibumad-devel.i686

libiodbc

libiodbc-devel

librdmacm-devel

librdmacm-devel.i686

log4cxx

log4cxx-devel

lua-devel

lzo-minilzo

net-snmp-devel

net-snmp-perl

openldap-clients

openldap-devel.i686

openmotif

openssl-devel.i686

openssl-static

perl-Config-IniFiles

perl-DBD-SQLite

perl-Config-Tiny

perl-Expect

perl-IO-Tty

perl-Math-Calc-Units

perl-Params-Validate

perl-Parse-RecDescent

perl-TermReadKey

perl-Time-HiRes

protobuf-compiler

protobuf-devel

python-qpid

python-qpid-qmf

qpid-cpp-client

qpid-cpp-client-devel

qpid-cpp-client-ssl

qpid-cpp-server

qpid-cpp-server-ssl

qpid-qmf

qpid-tools

readline-devel

saslwrapper

sqlite-devel

tog-pegasus

libXext-devel 

libX11-devel  

libXau-devel

unixODBC

unixODBC-devel

uuid-perl

xinetd

xerces-c-devel

Note :

1.  The qpid-cpp-client-devel package is not in the latest CentOS distribution, you may need to enable an earlier repo using the following command

...

• The $MY_SQROOT/sqenv.sh file sources in the file sqenvcom.sh, where most of the Trafodion environment is set up: PATH, CLASSPATH, LD_LIBRARY_PATH, and so on.
• The sqgen command takes CLASSPATH and other environment variables and makes sure that they are used when starting Trafodion processes across the cluster. Therefore, it's very important that the correct CLASSPATH is set up before calling sqgen. Trafodion processes actually use the CLASSPATH that's defined in $MY_SQROOT/etc/ms.env, which should match what you get after sourcing sqenv.sh.
• The install_local_hadoop script copies jar files and executables for a single-node Hadoop install into your source tree: $MY_SQROOT/sql/local_hadoop. If you already have Hadoop running on the system and also want a sandbox version, install the sand-boxed Hadoop on non-standard ports:

  install_local_hadoop -p <start-port>
  <start-port> ... <start-port>+199 should be a range of unused ports.
  

• To run the software you built on a cluster, use the "package" make target instead of the "all" target above and use the built tar files to install on the cluster. Generally, most developers run on a single-node cluster, since a multi-node cluster requires more complex steps to deploy the built software. Here is how to modify software and run the modified objects on the local node (note there is no "make install"):

   sqstop
   # edit source files
   cd $MY_SQROOT/..
   make all
   sqstart
  

• Shutting Trafodion down. To do this, you would shut down Trafodion, then shut down the sand-boxed Hadoop that's used. The sw commands only apply if you are using the sandbox hadoop (install_local_hadoop).

   sqstop
   swstopall
  

  To start it up later, use the following commands:

   swstartall
   sqstart
  

  To check on the status, use these commands:

   sqcheck
   swstatus
  

• If you get rid of the entire source tree, all of the local Hadoop install will also be lost. Before removing these files, make sure to stop Hadoop. The easiest way to do that is with the swstopall or swuninstall_local_hadoop script (these are generated script in your path).