pre-bundled OAT vs OAT community edition
I'm installing a new instance on a Centos 6.4 server (dedicated database server). Initially, I included the OAT package in the install, but then I noticed that it includes a full apache and php install, and even after that has some missing library dependencies. The readme file mentions a manually installed OAT Community Edition, which seems to be to be a better option since I can use the already-installed apache and php (and have the RPM's deal with dependencies). My question is, what is the difference between the OAT bundled in the CSDK and OAT Community Edition? Will I be missing any features/functionality if I use the community edition? Thanks, -Justin
The features are exactly the same, the community edition requires a manual install of apache, php, pdo.. John F. Miller III ids-bounces@iiug.org wrote on 05/21/2013 03:12:05 PM: > From: "Justin Killen" <jkillen@allamericanasphalt.com> > To: ids@iiug.org, > Date: 05/21/2013 03:13 PM > Subject: pre-bundled OAT vs OAT community edition [30314] > Sent by: ids-bounces@iiug.org > > I'm installing a new instance on a Centos 6.4 server (dedicated database > server). Initially, I included the OAT package in the install, but then I > noticed that it includes a full apache and php install, and even after that > has some missing library dependencies. The readme file mentions a manually > installed OAT Community Edition, which seems to be to be a better > option since > I can use the already-installed apache and php (and have the RPM's deal with > dependencies). > > My question is, what is the difference between the OAT bundled in > the CSDK and > OAT Community Edition? Will I be missing any features/functionality if I use > the community edition? > > Thanks, > -Justin > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. >
Justin Getting OAT to run in an existing apache install can be a PITA as you have to find the 'OAT' bits within the httpd.conf that is shipped, they do not supply a separate config that drops in the conf.d directory (like most other people do :-) ) You are correct there are lot of missing dependencies and/or library name version issues even when you install the full package, they are very irritating but easily fixed. CentOS and OAT seems to work well together, as does Redhat and OAT, but Fedora and OAT is the easiest way I have found to take the engine out :) Cheers Paul -----Original Message----- From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of Justin Killen Sent: Tuesday, May 21, 2013 5:12 PM To: ids@iiug.org Subject: pre-bundled OAT vs OAT community edition [30314] I'm installing a new instance on a Centos 6.4 server (dedicated database server). Initially, I included the OAT package in the install, but then I noticed that it includes a full apache and php install, and even after that has some missing library dependencies. The readme file mentions a manually installed OAT Community Edition, which seems to be to be a better option since I can use the already-installed apache and php (and have the RPM's deal with dependencies). My question is, what is the difference between the OAT bundled in the CSDK and OAT Community Edition? Will I be missing any features/functionality if I use the community edition? Thanks, -Justin **************************************************************************** *** Forum Note: Use "Reply" to post a response in the discussion forum.