server to ensure that the camel id is cached and we can process the
incoming metrics from the metrics-collector.

the metricVariable in the CP model.  It tests if the former contains the
metricVariable id and component name.  This method is experimental as we
don't have precise information on what the metrics-collector is going to
send.

port used in the deployed platform.
2) updated handling of metricVariableMetrics in Mapper and CpModelTool:
There could be more than 1 metricVariable with the same name in a CP
Model.

messages.  3.  Updated logging level from DEBUG TO INFO for some
messages to facilitate debugging.

message by topic and is throwing exception on messages not intended for
it.

2) redo error message in line with Etienne's required format
3) Mapper now get metricVariables from the Solution in line with CP
Generator changes. 

reflect the change.

orchestrator's cdo view active longer

added Javadoc markups and some cosmetic changes.

one port.  Updated relevant artifacts to support the modification.

Also added properties definition for the solvers in the properties file.

it).  I only need to add call to 0MQ publisher to call solvers.

model rather than create a new version.  Also Junit'ed the updated code.