A.13.3 CONFIGURERECORD

Configures the parameters associated with the recording of events for a stage of an Oracle Stream Analytics application. Use this command to configure a stage for the first time for event recording or to change the data set name or provider name.

Syntax

java wlevs.Admin 
    [ Connection Arguments ]
    [ User Credentials Arguments ]
    [ Common Arguments ] 
    CONFIGURERECORD -application application -stage stage
        [-datasetName datasetname] 
        [-storeProvider storeprovidername] 
        [-eventTypes eventtypes] 
        [-scheduleStartTime startime] 
        [-scheduleEndTime endtime | -scheduleDuration duration]

Table A-22 CONFIGURERECORD Arguments

Argument Definition 
-application application

Specifies the name of the Oracle Stream Analytics application whose event record and playback you want to manage.

To get the exact name of your application, you can:

  • Use wlevs.Admin to query for the name (see Query for Application and Processor Names).

  • Use the Oracle Stream Analytics Visualizer: Start the Oracle Stream Analytics Visualizer (see Using Visualizer for Oracle Stream Analytics). In the left pane, navigate to and expand the Applications node of the Oracle Stream Analytics instance to which the application is deployed. Each node under the Applications node is named with the exact application name.

  • Look at the MANIFEST.MF file of the application; the application name is specified by the Bundle-SymbolicName header.

 
-stage stage

Specifies the name of the particular stage, attached to the Oracle Stream Analytics application specified with the -application argument, whose event record and playback you want to manage.

 
-datasetName datasetname

Specifies the name of the dataset in which events are recorded.

 
-storeProvider storeprovidername

Specifies a valid data-source name defined in the Oracle Stream Analytics server config.xml file.

To select the default BDB provider, leave this argument empty or specify an argument value of default-provider.

For more information, see Schema Reference for Oracle Stream Analytics.

 
-eventTypes eventtypes

Specifies the comma-separated list of valid event type names to be recorded. Event types must be defined in the event type repository.

 
-scheduleStartTime starttime

Specifies the time when the recording should start.

Express the start time as an XMLSchema dateTime value of the form:

mm-dd-yyyy:hh:mm:ss

For example, to specify that recording should start on October 20, 2013, at 11:22:07 am, use the following value:

10-20-2013:11:22:07

For complete details of the XMLSchema dateTime format, see http://www.w3.org/TR/xmlschema-2/#dateTime-lexical-representation.

 
-scheduleEndTime endtime

Specifies the actual time when the recording should end.

Express the end time as an XMLSchema dateTime value of the form:

mm-dd-yyyy:hh:mm:ss

For example, to specify that recording should end on October 20, 2013, at 6:00pm, use the following value:

10-20-2013:18:00:00

For complete details of the XMLSchema dateTime format, see http://www.w3.org/TR/xmlschema-2/#dateTime-lexical-representation.

Specify null if you want the recording to run forever.

You can specify either -scheduleEndTime or -scheduleDuration, but not both.

 
-scheduleDuration duration

Specifies the duration of time after which event recording for this stage ends. Specify null if you want the recording to run forever.

The format is HH:mm:ss, such as 01:00:00.

You can specify either -scheduleEndTime or -scheduleDuration, but not both.

Example

The examples in this section show how to configure the recording of events of the helloworldAdapter of the helloworld application deployed to the specified Oracle Stream Analytics instance.

The following example specifies a start and end time for recording:

java wlevs.Admin 
     -url service:jmx:msarmi://localhost:9002/jndi/jmxconnector 
     -username wlevs -password wlevs 
     CONFIGURERECORD -application helloworld -stage helloworldAdapter 
     -datasetName myds -storeProvider mysp
     -scheduleStartTime 10-20-2013:11:22:07 -scheduleEndTime 10-20-2013:18:00:00

The following example specifies a start time and a duration for recording:

java wlevs.Admin 
     -url service:jmx:msarmi://localhost:9002/jndi/jmxconnector 
     -username wlevs -password wlevs 
     CONFIGURERECORD -application helloworld -stage helloworldAdapter
     -datasetName myds -storeProvider mysp
     -scheduleStartTime 10-20-2013:11:22:07 -scheduleDuration 01:00:00

The following example specifies a start time and a duration of null, which means recording runs forever:

java wlevs.Admin 
     -url service:jmx:msarmi://localhost:9002/jndi/jmxconnector 
     -username wlevs -password wlevs 
     CONFIGURERECORD -application helloworld -stage helloworldAdapter 
     -datasetName myds -storeProvider mysp
     -scheduleStartTime 10-20-2013:11:22:07 -scheduleDuration null