Get Mojo

To get Mojo, simply Download it from HERE.

Get the full Online Mojo Documentation Here

Mojo Download Checklist - Before you Install

The following information and software should be collected and verified before initiating an install.

  • Java Runtime Environment installed, any version from 1.5.0_01 through 1.6.0_40
  • Perl 5.6.0, 5.6.1, 5.8.6 or 5.8.8 installed
  • Operating System
    • Windows XP,  2000, 2003, Vista
    • AIX 5.2, 5.3
    • Sun Solaris 9.0, 10.0
    • HP-UNIX 11.0, 11.11, 11i
    • LINUX Red Hat 9.0, Enterprise 2.1, 3.0, 4.0, 4.7, 5.1
    • LINUX SUSE 9.0, 10.0
  • Mozilla or Netscape installed for AIX, HP-UNIX, and Sun Solaris. Mozilla or Netscape install directory must be listed in the PATH environment variable.
  • 100 Megabytes of hard disk space
  • 512 Megabytes of me mory is recommended
  • DNS Host Name of installation machine
  • Available Port Number for the KB Server.  The installer defaults to 58080
  • Available Port Number for the Build Manager Server, which runs as part of the KB Server.  The installer defaults to 58585
  • Information for the configuration of the SMTP mail server for integrated email functionality, including:
    • SMTP Server Name
    • SMTP Server Port Number
    • Email address available for use with Openmake emails
    • Does the SMTP Server require login?
    • If login is required then you will also need a login name and password
    • Does the SMTP Server use SSL?


Did you know that you can sign-up for enterprise level technical support for Mojo?  You get:

  • Access to the OpenMake Software Support Center to post, track and view issue status.
  • Phone support between 8 AM to 6 PM CST with our Meister Support Staff
  • Access to 2nd level support technicians to discuss enhancements and product direction.

Contact us at (800) 359-8049 or (312) 440-9545 (International) and ask for Technical Support Sales.


Requirements, Static Code Analysis and Testing Tool Integration

IBM ClearQuest
IBM Tivoli

Customer Success Stories

Major Health Care Provider Centralizes enterprise builds with Meiter

See how a Major Health Insurance Provider implemented a centralized build process using Meister.


100% Build to Deploy automation that is Developer Driven

See how a Major Insurance Company implemented a secure, developer driven, build to deploy process using OpenMake Deploy+ and CA SCM r12. This demo has an excellent example of how Deploy+ with Remote Agents can parallelize the build to deploy process.


Meister added Transparency to the process...

"The implementation of Openmake Meister for build management allowed  BNSF to directly address one of their biggest challenges in the area of IT controls. This technology automated the team’s build processes, providing a  complete audit trail of changes, progression and approvals through each lifecycle stage. Finally, the implementation team used MKS Integrity Manager’s capabilities to manage the implementation itself." BNSF Technology Services Division - Learn More

Meister Standardized the compile process across the enterprise at UCLA ...

"UCLA's challenge was to standardize how builds and releases were processed, regardless of the development language used. OpenMake Meister provided this across the enterprise." University of Southern California, Production Control Team Lead - Learn More


Meister allowed developers to be more efficient saving money and time...

"As a company who specializes in process improvement we look for the most efficient ways to manage changing resources and requirements. We found this quality in Openmake Meister. Meister has allowed us to improve our development process by providing a streamlined, agile and 100% transparent build environment across the application lifecycle." Chris Lank, Ivis President and CEO, VP Worldwide Sales, Togethersoft

Meister accelerated builds across multiple remote machines...

"OpenMake Meister drastically reduced the cost of supporting our builds.  Meister allowed our build team to increase the number of builds supported using only 1/2 the staff, configured across 100 remote build agents."   Production Control, Major US Bank

Meister added consistency across multiple languages...

"Meister provides us a standard rules-driven build process regardless of platform, compiler and operating system. We selected Meister because it is the only enterprise-wide build tool that can thoroughly support our mission-critical Java, C/C++, and .NET applications.”   Todd Athorp, Sr Programmer, FIS

Meister allowed for more control in a 'fast evolving' development environment...

"Meister offers us increased productivity and quality  compared to manually controlled builds. Meister also completes the configuration management process through it's central build capabilities allowing Fortis to fully control all internal and external software assets within our fast evolving J2EE world.”  Matthias Pyck, Fortis Bank - Learn More