INTRODUCTION TO MOCA

 MOCA is the framework for Red Prairie products to allow 

the development of component based software products

> Similar in some ways to COM, CORBA, EJB and other 

component architectures.

> The main difference between other component architectures 

and MOCA is that MOCA is not Session based and not object 

oriented, although in some cases the underlying implementation 

may be object oriented.

> MOCA is a loosely coupled, thin-client, stateless architecture 

that puts most of the work on the Server side.

> Examples of a "client" in WMS could be a GUI form, a web 

page, a custom report, or a RF screen on a RF scanning device.

> The client does not have to know the implementation details, it 

simply needs to set the correct parameters to call the MOCA 

command and how to handle the results and return code that 

are returned.

> The MOCA component is called by sending a packet of data to 

the MOCA server that consists of the command and the 

parameters.

> The MOCA server then parses the command, executes the 

component and returns a result code and a dataset of one to 

many rows.

• MOCA verse MOCAng

> In the 2010.1 version of MOCA, a major rewrite of the architecture was 

released called MOCA Next Generation.

> Several new features were introduced into MOCAng to improve stability 

and performance.

> Multi-threading is now supported.

> Some of the legacy C code was rewritten in Java and the database 

access libraries are now Java using JDBC.

> C code is now executed inside its own process so a problem in the C 

code will not affect availability of the MOCA server.

> Jobs and Tasks were pulled into a table driven format and are now 

controlled via the GUI using Task Maintenance and Job Maintenance.