I have downloaded and installed the 3.0.5 package onto my windows machine and have that up and running great. I'm trying to get a version up and running on Mac OS.
I have a few questions:
In the windows version, how does the war file get deployed to Tomcat? I don't see the webapps directory of Tomcat, nor do I see a .war file anywhere.
When following the default install, I have found what I believe to be the contents of the .war file located at:
C:\Program Files\Jive SBS Public 3.0\applications\sbs
Is this a correct assessment?
How is JIVE_HOME set (directory containing jive_startup.xml)? In 2.5.5, the previous version we were using, this is set via a jive_init.xml file, which is within our the war files /WEB-INF/classes directory. This is criticial to getting jive up and running in the Mac OS.
Where are the logs in 3.0.5? I'm looking in the default install location of:
C:\Program Files\Jive SBS Public 3.0\tomcat\logs
for them, but they're nowhere to be found. I'm trying to verify that we can sync up with JNDI and Oracle 10 correctly, but I'm getting an error yet don't have any logs to review to get to the bottom of this.
Please address these questions ASAP. We're very interested in upgrading to version 3 but we need to iron out a few details first.
Thanks,
Dan
Dan,
As of 3.0.x we no longer support running in a Windows / Mac environment for production environments. But I can provide some tips for getting things running.
The windows installer you used was probably our .exe package, which uses the Jetty application sever and is great for testing puposes. This installer will create C:\Documents and Settings\LocalService\Local Settings\Application Data\Jive Software\Clearspace 2.5\jiveHome for your jiveHome directory as well as C:\Program Files\Jive* for all of the installation files + Jetty application server.
While you might still be able to get the application to run on a Mac, we no longer test or have any installs readily available to debug outside of our RPM installations for Redhat / CentOS / SUSE and recently Solaris. Part of this decisions was due to the Mac Java environment falling way behind the curve in the JRE / JDK version, as well as the simplicity and power of an RPM install that controls the entire install stack.
Since these changes were made a few 'assumptions' were made on our end. If you check your Mac, you may now have a file structure set up in /usr/local/jive/ (where the jiveHome and /var/logs/ will reside) and this is no longer stored in a jive_init.xml file - it is now coded into our application. So I have no idea where the windows installation will try to create the log files, but on the Mac you should be able to locate some of the information you want within the jive directory.
The big caveat is that I have yet to see 3.0.x work 100% correctly on my Mac, so I would recommend using a VM of CentOS 5 to test / Dev.
-Curtis
The big caveat is that I have yet to see 3.0.x work 100% correctly on my Mac, so I would recommend using a VM of CentOS 5 to test / Dev.
I've been doing SBS plugin development on my Mac and it's been working great so far...as long as I run it with JDK 1.6.
wolfpack wrote:
The big caveat is that I have yet to see 3.0.x work 100% correctly on my Mac, so I would recommend using a VM of CentOS 5 to test / Dev.
I've been doing SBS plugin development on my Mac and it's been working great so far...as long as I run it with JDK 1.6.
I can do the same. Was it as simple as unzipping the .rpm or did you use the ported RPM application for Mac?
Thanks,
Dan
I actually use Maven to do everything as described in the Developers area.
We only have a 2.5.5 repository thus far. Will this prevent me from going with 3.0? I've done the evaluation version in Windows but want to get a dev environment set-up for 3.0 so we can get rocking and rolling on that.
Thanks,
Dan
I've gotten to the point where I can compile code, etc using maven for 3.0.4.
Have you been able to compile a stand alone war and deploy it in Mac OS? When I attempt this it begins looking for system files /usr/local/jive/ that get installed on a linux box via the .rpm installer.
Thanks,
Dan
Sounds good. Cool! Thanks,
Dan