Content Server Manual / Version 2512.0
Table Of Contents
The events utility supports two modes for printing events.
If the option
-cis given, the utility prints the events for a single content and exits immediately.Otherwise, the utility prints all events generated by the Content Management Server or the Workflow Server until it is terminated explicitly. At the user's option, a time stamp can be provided for replaying historic events previously to entering the live event stream.
usage: cm events -u <user> [other options]
available options:
Options Description
-c, --content-id <content id> content id for which the
history is shown
-d, --domain <domain name> domain for login
(default=<builtin>)
-g, --grpc-endpoint <gRPC endpoint> gRPC endpoint to connect to
--grpc-wfs-endpoint <WFS gRPC endpoint> gRPC endpoint of Workflow
Server to connect to
--http-base-uri <HTTP base URI> HTTP base URI of Content
Server where HTTP servlets
are provided (e.g. blob
servlet)
-p, --password <password> password for login; you will
be prompted for password if
not given
-t, --timestamp <timestamp> content timestamp
-u, --user <user name> user for login (required)
--url <ior url> url to connect to
Example 3.34. Usage of the events utility
The events utility has the following options:
| Parameter | Description |
|---|---|
-c | The id of the content whose history is to be printed. Omit this option, if
you want to print events for the entire repository. This option cannot be combined
with the -t option. |
-t | Timestamp, this option gives the date of the last synchronization with
events. If you restart the utility, all events which happened after the moment
given with the option -t will be reprocessed (that is printed to the
console), so -t should be omitted when the events utility is used for
the first time. If you start events without the option -t, all events
from now on will be printed. A timestamp has the format
<seq_no>:<sub_no>:<id_tag> and is printed out
before the event. See Javadoc of
com.coremedia.cap.content.Timestamp#fromNumbers(int,int,int) for
further details. Note that session events don't provide timestamps. |
Table 3.34. Options of the events utility
Listening from 2147483647:2147483647:0
2005-10-19T11:47:04+02:00: 2224:1:-1057456870: content checked out
on coremedia:///cap/content/1468 by user
coremedia:///cap/user/5 (version coremedia:///cap/version/1468/2)
2005-10-19T11:47:05+02:00: session opened on
coremedia:///cap/session/1268 by coremedia:///cap/user/1 from
armadillo (10.1.4.111) for coremedia:///cap/service/feeder
2005-10-19T11:47:05+02:00: session closed on
coremedia:///cap/session/1268 by coremedia:///cap/user/1 from
armadillo (10.1.4.111) for coremedia:///cap/service/feeder
2005-10-19T11:47:47+02:00: 2225:1:-1057456870: version created on
coremedia:///cap/content/1468 by user
coremedia:///cap/user/5 (version coremedia:///cap/version/1468/2)
2005-10-19T11:47:47+02:00: 2225:2:-1057456870: content checked in
on coremedia:///cap/content/1468 by user
coremedia:///cap/user/5 (version coremedia:///cap/version/1468/2)
Example 3.35. Output of events
