Support for additional platforms

by **vernon** on Fri May 26, 2006 7:23 am

Is there any reason not to support other platforms, such as OS X and other versions of Linux that use the apt-get package manager such as Debian and Ubuntu?

by **Henrik Nordberg** on Fri May 26, 2006 10:44 am

We constantly prioritize feature requests from the community and our customers. If we see there is a clear demand for a feature or a new platform, we will do that sooner.

Cheers
- Henrik

by **torevg** on Thu Jun 08, 2006 11:49 am

Is there a roadmap foreseen for supporting other linux distributions than Fedora ?

I tested your product (first impressions were quit impressive) on Windows but would prefer to use server and client on Linux.

I, for myself, use Ubuntu.

Kind regards

Tore

by **dgoran** on Wed Jul 26, 2006 6:18 am

Any company that is serious about penetration in corporate market has to support at least debs or apt-get package manager such as Debian and Ubuntu as the poster above said.
I am willing to bet that if you could count all those servers that are supposed to be windows server boxes for various political reasons but are in fact debian boxes you would get your "priorities" realigned.

-G

by **emanuel** on Fri Jul 28, 2006 11:37 am

Hi,

right now the lack of support beyond rpm is purely due to lack of resources. If someone from the community would like to help out in packaging the Jitterbit software for Suse, Debian or anything else, then that would be greatly appreciated. Another solution that we have been contemplating is using a "universal" installer like BitRock (http://www.bitrock.com). Would this be acceptable for the majority of users in the Linux community? Any comments on this subject are welcome.

/Cheers
Emanuel

by **rpnowak** on Tue Jul 31, 2007 2:03 am

DEB is probably second most popular packaging format, right after RPM, so IMHO you should speed up work on this kind of package to make Jitterbit available for big group of users. All application servers in my company use Debian and I've been working to run Jitterbit from RPM's on them, still no results.

My vote on DEB :)

by **emanuel** on Tue Aug 21, 2007 2:47 pm

Hi,

have you tried converting the rpm files to deb packages with Alien, http://kitenet.net/~joey/code/alien/ ? The install script would have to be changed slightly to install the deb packages instead of the rpm packages.

/Cheers
Emanuel

by **jemmasta** on Sat Jan 12, 2008 11:38 pm

I tried to run first install.sh after installing rpm into Debian Etch. Not a chance, just shows error like this even if dependencies are met:

Code: Select all: Checking for required software and libraries...warning: data_files/jitterbit-base-1.3.0-2.i386.rpm: Header V3 DSA signature: NOKEY, key ID 089ae198 error: Failed dependencies: /bin/sh is needed by jitterbit-base-1.3.0-2.i386 /usr/sbin/groupadd is needed by jitterbit-base-1.3.0-2.i386 /usr/sbin/useradd is needed by jitterbit-base-1.3.0-2.i386 /usr/sbin/usermod is needed by jitterbit-base-1.3.0-2.i386 libc.so.6 is needed by jitterbit-base-1.3.0-2.i386 libc.so.6(GLIBC_2.0) is needed by jitterbit-base-1.3.0-2.i386 libc.so.6(GLIBC_2.1) is needed by jitterbit-base-1.3.0-2.i386 libc.so.6(GLIBC_2.1.2) is needed by jitterbit-base-1.3.0-2.i386 libc.so.6(GLIBC_2.1.3) is needed by jitterbit-base-1.3.0-2.i386 libc.so.6(GLIBC_2.2) is needed by jitterbit-base-1.3.0-2.i386 libc.so.6(GLIBC_2.2.3) is needed by jitterbit-base-1.3.0-2.i386 libc.so.6(GLIBC_2.3) is needed by jitterbit-base-1.3.0-2.i386 libc.so.6(GLIBC_2.3.4) is needed by jitterbit-base-1.3.0-2.i386 libcrypt.so.1 is needed by jitterbit-base-1.3.0-2.i386 libdl.so.2 is needed by jitterbit-base-1.3.0-2.i386 libdl.so.2(GLIBC_2.0) is needed by jitterbit-base-1.3.0-2.i386 libdl.so.2(GLIBC_2.1) is needed by jitterbit-base-1.3.0-2.i386 libidn.so.11 is needed by jitterbit-base-1.3.0-2.i386 libnsl.so.1 is needed by jitterbit-base-1.3.0-2.i386

Then tried to convert all rpms into debs and install them in order that I spied from the install.sh. works ok at to a point where the actual server should be installed. I realized that install.sh consists configuration info etc. that is not carried over to the install with debs. To here my knowledge ends. Is there any roadmap on the .deb packages publication as I understood that your plan IS to make those at some point even if the community isn't able to?

Would love to test this tool out, but access is only to Debian servers so... :(

by **emanuel** on Tue Jan 15, 2008 12:41 pm

Hi,

try to run the install script with --nodeps which skips the check for dependencies.

/Cheers
Emanuel

by **jemmasta** on Tue Jan 15, 2008 4:11 pm

Ok, did that and got further. But... :)

Now I get this error:

Code: Select all: You seem to have unixODBC installed in /usr. You need to pick a driver to use for PostgreSQL. Available drivers are: odbcinst: SQLGetPrivateProfileString failed with . Please pick the driver to use for PostgreSQL [PostgreSQL] /etc/init.d/postgresql does not exist, you need to manually make sure that PostgreSQL is running. Please wait... Database operation failed: [unixODBC][Driver Manager]Data source name not found, and no default driver specified Details: Exception type: DBException Method: DBConnection::Connect(const TCHAR *DSN) Error Message: Unable to connect to database using DSN UID=postgres;PWD=<REMOVED>;SERVER=127.0.0.1;DRIVER={PostgreSQL};DATABASE=template1;Port=5432;! SQL Errors: (0) SQL Error! SQLSTATE = IM002 Native err = 0 msg = [unixODBC][Driver Manager]Data source name not found, and no default driver specified

I've updated unixODBC and I'm sure my PostgreSQL is installed correctly since other software is running on it. It also accepts tcp connections. As it seems all that is missing now for installation to be succesful on Debian is to have the installation set up databases for Jitterbit.

Edit: Oh yeah and yes PostgreSQL 8.2 was running at that time and port was correct. :)

by **emanuel** on Tue Jan 15, 2008 5:11 pm

The problem is that the PostgreSQL driver is not registered with unixODBC. What is the output of the command

odbcinst -q -d ?

If you get an error when executing this command, most likely there is something wrong with the unixODBC installation.

/Emanuel

by **jemmasta** on Tue Jan 15, 2008 11:56 pm

This command gives reply of:

Code: Select all: odbcinst: SQLGetPrivateProfileString failed with .

And the search continues... :)

Edit:

Configured unixodbc and now the error is:

Code: Select all: Database operation failed: [unixODBC]Unknown authentication type Details: Exception type: DBException Method: DBConnection::Connect(const TCHAR *DSN) Error Message: Unable to connect to database using DSN UID=postgres;PWD=<REMOVED>;SERVER=127.0.0.1;DRIVER={PostgreSQL};DATABASE=template1;Port=5432;! SQL Errors: (0) SQL Error! SQLSTATE = 28000 Native err = 211 msg = [unixODBC]Unknown authentication type

I've tried with several configurations to unixodbc but error doesn't change. unixODBC version is 2.2.11-16.

Edit2:

Now I found info regarding the correct driver to use with PostgreSQL 8.2. But still not working although error changed again. :)

Code: Select all: Please wait... ./install.sh: line 1153: 13361 Segmentation fault $JITTERBIT_HOME/bin/JitterbitDbInstallUtils $opts Failed to install databases.

Now my knowledge ended here again. :)

Using odbcdriver:

Code: Select all: [PostgreSQL] Description = PostgreSQL driver for Linux & Win32 Driver = /usr/lib/odbc/psqlodbcw.so FileUsage = 1

by **emanuel** on Fri Jan 18, 2008 6:11 pm

Hi,

hard to say what the problem is in this case. I have seen this happen with some PostgreSQL drivers. Have you tried to install the PostgreSQL driver that is distributed with Jitterbit? The package is called jitterbit-psqlodbc-08.02.0400-1.fc7.i386.rpm.

If you have gdb installed you can try to edit install.sh to call "gdb JitterbitDbInstallUtils" instead of just JitterbitDbInstallUtils, then maybe we can get some more information about exactly what is crashing.

Do you get a core file in the current directory when you run this?

/Cheers
Emanuel