No Mac version for 5.0?

[sstillwell]

I saw that v5 has been released...congratulations!

I wanted to download a non-beta copy and requested the download link for my Mac...which gave me a 4.5 download. Drat.

Will v5 make its way to OS X eventually?

[Hovik]

Apologies for that. We've not created a Mac version of Ebase V5 yet.

We will have a Mac version by the end of the week. I will confirm it in a post here.

[sstillwell]

Thank you! I'll be looking forward to it!

[sstillwell]

For the moment, it appears to be working if I use the 64-bit Linux .tar.gz version and replace the provided JRE with the system JRE,thus:

Code: Select all

cd ebaseXi
rm -rf jre/
ln -s `/usr/libexec/java_home`/jre jre

at that point I can launch the designer and it APPEARS to work

The Server will also launch, but the syntax for the 'tail' command is evidently slightly different on OS X ( -n <number> vs --lines <number> ) which yields an error trying to display the logs. Tomcat fires up, though. Editing the script to replace

Code: Select all

--lines=500

with

Code: Select all

-n 500

fixes that as well.

This is using most current Oracle JRE 8.

Code: Select all

➜  UfsServer  java -version
java version "1.8.0_45"
Java(TM) SE Runtime Environment (build 1.8.0_45-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.45-b02, mixed mode)

FYI

[Steve]

Thanks for the info.

[Hovik]

Mac installer now available to download:

http://www.ebaseftp.com/download/ebase_ ... _5_0_1.dmg

[sstillwell]

Downloaded, thanks! Will test later today.

Lots of learning to do...looking forward to it.

Scott

[sstillwell]

For future Mac users' reference, I also used Automator to create a clickable application for the Ebase Xi client - just create an Application type Automator document that has a single action "Shell script" that does...

cd /Applications/ebaseXi/UfsClient
./start_ebase_designer.sh

Works just fine - you can optionally then add an appropriate icon image using Finder if you wish.

Same thing goes if you want to create applications to start or kill the server process...but maybe I'm just being lazy then

I should probably write a LaunchDaemon .xml file so that the server can be started by default using standard OS X methods. I'll update here if I do.

Scott

[sstillwell]

Okay, this seems to work, with a caveat (explained later)...

Create the file /Library/LaunchDaemons/com.ebasetech.ebaseXi.plist as follows:

Code: Select all

<xml>
<DOCTYPE>
<plist>
<dict>
	<key>Disabled</key>
	<false>
	<key>EnvironmentVariables</key>
	<dict>
		<key>TERM</key>
		<string>dumb</string>
	</dict>
	<key>KeepAlive</key>
	<false>
	<key>Label</key>
	<string>com.ebasetech.ebaseXi</string>
	<key>ProgramArguments</key>
	<array>
		<string>/bin/sh</string>
		<string>./ebase-Xi</string>
		<string>start</string>
	</array>
	<key>QueueDirectories</key>
	<array>
	<key>RunAtLoad</key>
	<true>
	<key>StandardErrorPath</key>
	<string>/tmp/com.ebasetech.ebaseXi.err</string>
	<key>StandardOutPath</key>
	<string>/tmp/com.ebasetech.ebaseXi.out</string>
	<key>WatchPaths</key>
	<array>
	<key>WorkingDirectory</key>
	<string>/Applications/ebaseXi/UfsServer</string>
	<key>inetdCompatibility</key>
	<dict>
		<key>Wait</key>
		<true>
	</dict>
</dict>
</plist>

Output will be logged as indicated to /tmp/com.ebasetech.ebaseXi.[out|err], and setting TERM=dumb just avoids a warning that would otherwise go to stderr when launched.

When the LaunchDaemon loads at boot (or with launchctl load), ebaseXi Server starts up just fine.

Here's the caveat: Unloading the LaunchDaemon does NOT kill ebaseXi, it just kills the script that started it. The java process keeps going, just as it would when started manually from the command line. LaunchDaemons do not provide a way to run a separate command at unload (such as ./ebase-Xi stop), so you'll have to stop it via command line.

At least it DOES give you a OS X-friendly way of starting the service at boot. Hope it helps.

Scott