Jitterbit on Fedora Core 5

[aderrico]

Hi All,
I've designed a beautiful web based architecture, including Jitterbit on Fedora Core 5 but using this Linux OS, I can't install Jitterbit in sample way, cause there are dependecies base on HTTPD and so on...

Anyone has solved this problem? How? It's important for us to use Jitterbit and Fedora Core 5.

Please, help me.

Thanks in advance.



Angelo D'Errico

[emanuel]

Hi All,
I've designed a beautiful web based architecture, including Jitterbit on Fedora Core 5 but using this Linux OS, I can't install Jitterbit in sample way, cause there are dependecies base on HTTPD and so on...

Anyone has solved this problem? How? It's important for us to use Jitterbit and Fedora Core 5.

Please, help me.

Thanks in advance.



Angelo D'Errico

Hi,

the only problem with installing Jitterbit on Fedora Core 5 is that we don't support the Apache Httpd 2.2 plugin architecture (yet). What you can do however is install Apache Httpd 2.0 on your machine as well, then install jitterbit using our installer. You probably have to pass the --nodeps option to the installer so that the rpm dependencies are not enforced. But run it without the --nodeps option first and make sure the only unsatisfied dependency is httpd 2.0.

After installing jitterbit server you need to go in and edit the file

/usr/local/jitterbit/bin/Jitterbit.sh

and make sure it uses the correct httpd when starting http.

I should add that I have not tested this personally so please let me know if you have any problems and if you get it to work it would be great if you could share your solution with the community.

/Cheers
Emanuel

[aderrico]

Hi Emanuel,
I've installed again Fedora Core 5 and then I've followed these steps:

1. yum install unixODBC postgresql-server
2. I've started postgresql daemon;
3. I've executed "sh install.sh --nodeps'
4. Everything gone well, but... an error occured during installation process and final messages are:

A LOT OF...
warning: user jitterbit does not exist - using root
warning: group jitterbit does not exist - using root
warning: group jitterbit does not exist - using root

AND THEN...

########################################### [ 20%]
/usr/local/jitterbit/bin/JitterbitInstallConfigUtils: error while loading shared libraries: libkonga-utils.so: cannot open shared object file: No such file or directory
error: %post(jitterbit-server-1.1.0-1.i386) scriptlet failed, exit status 127
2:jitterbit-base ########################################### [ 40%]
3:jitterbit-xerces-c ########################################### [ 60%]
4:jitterbit-xalan-c ########################################### [ 80%]
5:jitterbit-ws-axis ########################################### [100%]

the installation can not continue
Please solve the reported errors, conflicts or missing dependencies
Installation failed, see INSTALL.txt for troubleshooting instructions.
Also visit our forum: http://www.jitterbit.com/forums.

Press any key to exit the installer



Could you help me please?

Thanks in advance for your prompt reply.


Angelo D'Errico

[emanuel]

Hi,

I am not sure why you would get those errors, I will install FC5 myself and try it out.

/Emanuel

[aderrico]

Hi Emanuel,
Thank you for your prompt reply.

I'm waiting your answer about it.


Angelo

[emanuel]

Hi,

there are quite a few problems with installing on FC 5. The highlights being that some newer versions of shared libraries are used, SELinux has tougher restrictions and it comes with Apache httpd 2.2 which is not supported by jitterbit server 1.1. These problems will be addressed in version 1.2, but since the release of this version is still a few weeks away I will outline what you need to do to get version 1.1 working on FC5. Follow these steps in this order and you should be fine.

Before running the installer some preparation of the system is needed:

FC5 comes with newer versions of openldap and openssl that are not backwards compatible. However, it seems to be enough to create links to the new versions like this:

ln -s /usr/lib/libldap-2.3.so.0 /usr/lib/libldap-2.2.so.7
ln -s /lib/libssl.so.6 /lib/libssl.so.4
ln -s /lib/libcrypto.so.6 /lib/libcrypto.so.4

Granted I have not tried LDAP on FC5 so it might not work but if you don't use it you should be fine.

And since FC5 comes with PostgreSQL 8.1 you need the 8.0 version of the driver:

rpm -Uvh jitterbit-psqlodbc-08.01.0102-1.i386.rpm
(this rpm is distributed with the installer)

In FC5 the SELinux configuration seems to be stricter and you need to do the following (as root):

Bring up the UI for configuring securitylevels (system-config-securitylevel) then change this:
Modify SELinux Policy -> Compatability -> Check "Allow the use of shared libraries with Text Relocation"

Now you can install jitterbit server. However, running the installer with the --nodeps flag changes the order in which the rpm packages are installed so you either have to run "sh install.sh --nodeps" twice (it will fail the first time) or install the support rpms by hand first, like so:

rpm -Uvh data_files/jitterbit-base-VERSION.i386.rpm
rpm -Uvh data_files/jitterbit-xerces-c-VERSION.i386.rpm
rpm -Uvh data_files/jitterbit-xalan-c-VERSION.i386.rpm
rpm -Uvh data_files/jitterbit-ws-axis-VERSION-5.i386.rpm

and then run "sh install.sh --nodeps"

You can ignore the errors about apache at this point since you will run apache separately if you follow these instructions.

Then you need to install Apache Httpd 2.0:

Download apache httpd 2.0.59 from http://www.apache.org
unpack and cd to src directory and compile from source:

tar -xzf httpd-2.0.59.tar.gz
cd httpd-2.0.59
./configure
make
su root
make install

This installs httpd 2.0 in /usr/local/apache2

Then modify the file
/usr/local/apache2/conf/httpd.conf in the following way:

Line 219: Change "Listen 80" to "Listen *:46908"

Line 267-268: Change the lines that say User and Group to:
User jitterbit
Group jitterbit

Then add this to the end of the file:
# For handling web service calls from the Jitterbit client.
LoadModule axis_module /usr/local/jitterbit/lib/libaxiscpp_mod2.so
<Location /axis>
SetHandler axis
</Location>

# For handling web service calls to hosted web services.
LoadModule konga_ws_module /usr/local/jitterbit/lib/mod_konga_ws.so
<Location /jitterbit_ws>
SetHandler konga_ws

AuthType Basic
AuthName "Restricted Web Service"

# Anonymous access is allowed and is handled by the module.
</Location>

Start Apache 2.0 like this:

export AXISCPP_DEPLOY=/usr/local/jitterbit/axis
export JITTERBIT_HOME=/usr/local/jitterbit
/usr/local/apache2/bin/apachectl start

and stop it with "/usr/local/apache2/bin/apachectl stop"

If you want jitterbit server to start when the system starts you need to add the following commands to /etc/rc.local:

export AXISCPP_DEPLOY=/usr/local/jitterbit/axis
export JITTERBIT_HOME=/usr/local/jitterbit
/usr/local/apache2/bin/apachectl start
/usr/local/jitterbit/bin/Jitterbit.sh start

If you want to run the Jitterbit client on FC 5 you need to install the latest Java JRE from sun (this applies to all versions of Fedora Core).

Download "Java Runtime Environment (JRE) 5.0 Update 9" from http://java.sun.com. After installing you need to make sure that the new "java" command is in your PATH. The easiest way to accomplish this is by creating a link:

ln -s /usr/java/jre1.5.0_09/bin/java /usr/bin/java

I hope I didn't miss anything. Let me know how it works out for you.

/Cheers
Emanuel

[stevew_ttc]

thanks for the how to. I got real close but ended up getting:

/usr/local/apache2/bin/apachectl start
Syntax error on line 1044 of /usr/local/apache2/conf/httpd.conf:
Cannot load /usr/local/jitterbit/lib/mod_konga_ws.so into server: libcrypto.so.4: cannot open shared object file: No such file or directory


But everything is there, link is there, etc.

I SO want this to work on linux. (I tried Fedora Core 4, but there is no support for my HP SATA RAID array, so I couldnt use it).
So I guess I will buy a windows license for this server. It will be nice if it works out, and more linux support gets added.

Thanks!

[stevew_ttc]

Quick follow up. I re-ran installer to see where the error was:

Do you want to use the normal install mode? [y]

Using normal install mode.

An old installation was found in /usr/local/jitterbit

The software will be installed in /usr/local/jitterbit

Warning: OpenSSL does not seem to be installed correctly.

Checking for required software and libraries...warning: data_files/jitterbit-base-1.1.0-1.i386.rpm: Header V3 DSA signature: NOKEY, key ID 089ae198
done

Now we need to collect some information about your setup.

Found old installation, trying to connect to backend database.../usr/local/jitterbit/bin/JitterbitDbInstallUtils: error while loading shared libraries: libcrypto.so.4: cannot open shared object file: No such file or directory

Failed to connect to the backend database.
Continuing the installation anyway.

Do you want to set the PostgreSQL administrative password? [y]


No biggie. Going to windows for now. It will be the only windows server in the data center.

[emanuel]

thanks for the how to. I got real close but ended up getting:

/usr/local/apache2/bin/apachectl start
Syntax error on line 1044 of /usr/local/apache2/conf/httpd.conf:
Cannot load /usr/local/jitterbit/lib/mod_konga_ws.so into server: libcrypto.so.4: cannot open shared object file: No such file or directory


But everything is there, link is there, etc.

I SO want this to work on linux. (I tried Fedora Core 4, but there is no support for my HP SATA RAID array, so I couldnt use it).
So I guess I will buy a windows license for this server. It will be nice if it works out, and more linux support gets added.

Thanks!

When you created the link for libcrypto did you by any chance link on libcrypt instead? It is easy to confuse the two. What is the result if you do a "ls -la /lib/libcrypto.so.*"?

If the links are indeed correct you can try to run ldconfig (or reboot your machine...) and then try to start apache again.

/Emanuel

[sdudley]

We are building up our first test bed Jitterbit server using the Fedora Core 6 as this is the stage (from a package perspective) for the upcoming RHEL 5 series of offerings from Red Hat. This is not a dedicated server and we wanted the newer versions of PHP/Apache and MySQL for our Sugar CRM install. I followed your instructions for Core 5 on our Core6 box and while the Jitterbit startup process complained about a few entries in the apache configuration it seems to work... at least the client can connect. I've included the message below if it helps the development effort of 1.2. I also disabled SELinux to eliminate the additional 'variable' consideration. We are hoping to use Jitterbit in production next year to tie various database systems together and look forward to Jitterbit 1.2 hitting production. Ideally we'd like to see a version of Jitterbit that uses the newer versions of Apache so that we don't have to spend as much time on the SysAdmin side getting the back end configured. It appears to be a great product and we will definitely be contributing to the project.
Shaun

Here's the error message. Is this specific syntax normal given the installation of an additional Apache service outside of the Apache 2.2.3-5 version that ships with Core6?

Starting Jitterbit Apache...httpd: Syntax error on line 138 of /usr/local/jitterbit/apache/conf/httpd.conf: Syntax error on line 3 of /usr/local/jitterbit/apache/conf.d/jitterbit.conf: API module structure `axis_module' in file /usr/local/jitterbit/lib/libaxiscpp_mod2.so is garbled - perhaps this is not an Apache module DSO?

[emanuel]

Hi Shaun,

thanks for your input, the errors you get are because the startup script is trying to start apache 2.2 but using the modules compiled for 2.0. We are considering distributing a private version of apache 2.0 which would simplify the installation on distributions that don't include apache 2.0. We are already running a dedicated instance of apache, but it is the one already installed on the system so the only difference would be that the Jitterbit installation increases with a few MB. Would that be an acceptable solution in your case?

/Cheers
Emanuel

[sdudley]

I think packaging Apache with the Jitterbit server would be a great idea. It would be self contained meaning I wouldn't need to alter my choice of a distro based on the requirements of one app versus another and more importantly, I could spend less time with the sysadmin side and more time with Jitterbit. I would think that the embedded Apache approach would be well received from a development perspective as their Apache environment would be defined from a control point of view. Are there any drawbacks to using an embedded version of Apache? Are there modules that you would include with an embedded version that might conflict with the default O/S installation of Apache?

Shaun

[emanuel]

I think packaging Apache with the Jitterbit server would be a great idea. It would be self contained meaning I wouldn't need to alter my choice of a distro based on the requirements of one app versus another and more importantly, I could spend less time with the sysadmin side and more time with Jitterbit. I would think that the embedded Apache approach would be well received from a development perspective as their Apache environment would be defined from a control point of view. Are there any drawbacks to using an embedded version of Apache? Are there modules that you would include with an embedded version that might conflict with the default O/S installation of Apache?

Shaun

Jitterbit Server 1.2.0-RC1 now distributes a minimal version of apache httpd 2.0.59, compiled with a minimal number of modules, so there will be no conflicts with what is already installed. It only loades the modules needed for the operation of the Jitteribt server. I have tested this installer on Fedora Core 5. All the issues mentioned in this thread should be fixed. Please give it a try and report back to this thread with any problems you might have.

You can get RC1 from Source Forge:

http://sourceforge.net/project/showfile ... _id=209475

/Cheers
Emanuel

[sdudley]

With SELinux disabled and as root I'm getting the following errors halfway through the install process. (This is on a fully updated Core 6 box)
Any ideas?

Shaun

Preparing... ########################################### [100%]
1:jitterbit-base ########################################### [ 17%]
2:jitterbit-xerces-c ########################################### [ 33%]
3:jitterbit-xalan-c ########################################### [ 50%]
4:jitterbit-ws-axis ########################################### [ 67%]
5:jitterbit-apache-httpd ########################################### [ 83%]
6:jitterbit-server ########################################### [100%]
/usr/bin/chcon: can't apply partial context to unlabeled file /usr/local/jitterbit/lib/libkonga-crypto.so
/usr/bin/chcon: can't apply partial context to unlabeled file /usr/local/jitterbit/lib/libkonga-dtldbutils.so
/usr/bin/chcon: can't apply partial context to unlabeled file /usr/local/jitterbit/lib/libkonga-mailclient.so
/usr/bin/chcon: can't apply partial context to unlabeled file /usr/local/jitterbit/lib/libkonga-utils.so

[emanuel]

Hi,

these are just warnings and should not cause the installation to fail, I tested it on FC5 where I got those warnings but the installation continued successfully. Does the installation fail for this reason on FC6? I will modify the script to check if SELinux is enabled before running chcon on the files.

/Cheers
Emanuel