For backward compatibility, all \verb'GLITE_WMS_*' variables can be prefixed by
\verb'EDG_WL_' instead, for example \verb'EDG_WL_LOG_DESTINATION'.
+\newpage
+\subsection{CREAM Job States Mapping}
+\label{a:creammapping}
+
+\begin{tabularx}{\textwidth}{>{\bfseries}lX}
+CREAM state & \LB state \\
+Registered & Submited \\
+Pending & Waiting \\
+Idle & Scheduled \\
+Running & Running \\
+Really Running & Running \\
+% Held
+Done OK & Done \\
+Done Failed & Done \\
+Aborted & Aborted \\
+Cancelled & Cancelled \\
+\end{tabularx}
when RB decides where jobs get submitted.
+\subsubsection{CREAM jobs}
+In \LB 2.1, the basic support for CREAM jobs is implemented. The \LB gather events from CREAM performing both mapping CREAM attributes to WMS attributes (if possible) and storing CREAM-specific atributes. Thus, the jobs submitted directly to computing element can be tracked by \LB as well as data from WMS are extended. The CREAM job states are mapped to \LB ones according to Appendix \ref{a:creammapping}.
+
+CREAM events are generated from CREAM executor and LRMS, the generic event CREAMStatus is generated when the CREAM notifies that the job status has been changed.
+
\subsubsection{Non-gLite event sources}
\label{sec:nonglite}