8.2 cepconfigeng

Name: cepconfigeng - CEP engine configuration

Format

cepconfigeng -f XMLfilePath

Function description

This command configures a CEP engine.

It compares the content of the specified engine configuration file with that of a current CEP engine that has been configured, and then creates, changes the settings of, or deletes the CEP engine according to the differences between them.

Always save the engine configuration file for the next time the configuration content is to be changed.

When the command is executed, the prompt below is displayed - type "y" and press the Enter key to execute the change. Execution can be canceled by typing "n" or "q" and pressing the Enter key.

Are you sure you want to change the CEP Engine configuration? [y,n,q]:

Creating a CEP engine

This command creates a new CEP engine.

After the CEP engine is created, it must be started separately.

Changing CEP engine settings

This command changes the settings (Items other than CEP engine name) of a CEP engine that has been configured.

The CEP engine that is to be changed must be stopped beforehand. After this command is executed, the CEP engine must be started separately.

Deleting a CEP engine

This command deletes a CEP engine that has been configured.

The CEP engine that is to be deleted must be stopped beforehand.

If development assets have been deployed to the CEP engine that is to be deleted, the CEP engine can be deleted even if the development assets are not undeployed beforehand.

See

Refer to "8.9 cepstarteng" and "8.11 cepstopeng" for information on starting and stopping a CEP engine.

Arguments

-f XMLfilePath: Specify the engine configuration file that describes the definition content of the CEP engine. We recommend specifying an absolute path to avoid specification error.
See
Refer to "9.1.1 Engine Configuration File" for details.

End status

The following status codes are returned:

0: Normal end

8: Abnormal end

Note

A maximum of five CEP engines can be created. If six or more CEP engines are defined, this command ends abnormally.
Specify the CEP engine name so as not to be confused with other CEP engine names. If the CEP engine in the CEP configuration file has the same name, this command will end abnormally.
When creating a new CEP engine, always include in the engine configuration file the configured content of the CEP engine that has already been configured in order to retain that CEP engine. If this content is not included, the CEP engine that has been configured will be deleted.
Similarly, when changing CEP engine settings, always change the target settings only, and be sure to leave the other settings in the engine configuration file.
If this command ends abnormally due to an error, it is possible that the CEP engine configuration has an inconsistency. To complete changing the CEP engine settings, remove the cause of the error and then execute the command again.
If a CEP engine is deleted, development assets that have been deployed are undeployed automatically.
If this command ends abnormally due to an error during execution, the status of the development asset which was undeployed prior to the error is returned to the one before execution of this command, however there may be a CEP engine configuration inconsistency.
To complete the deletion of the CEP engine, remove the cause of the error and then execute the command again.
If this command is executed while sending an event, it may end abnormally. After stopping all CEP Server event senders, execute the command again.

Example

Example of output at normal end

When CEP engines (CepEngine1 and CepEngine2) are created:

/etc/opt/FJSVcep/Engine.xml:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<subSystemConfig xmlns="urn:xmlns-fujitsu-com:cspf:bdcep:v1">
    <engineConfig id="CepEngine1">
        <logging>
            <type>bdpp</type>
            <directory>hadoop</directory>
            <loggingMaxOpenFile>6</loggingMaxOpenFile>
            <loggingRotationCycle>300</loggingRotationCycle>
        </logging>
        <socketAdapterPort>9600</socketAdapterPort>
    </engineConfig>
    <engineConfig id="CepEngine2">
        <logging>
            <type>file</type>
        </logging>
        <socketAdapterPort>9601</socketAdapterPort>
    </engineConfig>
</subSystemConfig>

Command execution result:

# cepconfigeng -f /etc/opt/FJSVcep/Engine.xml <ENTER>
Are you sure you want to change the CEP Engine configuration? [y,n,q]:y <ENTER>
Command cepconfigeng executed successfully.

When CepEngine1 is deleted from the CEP engines that have been configured (leaving CepEngine2):

/etc/opt/FJSVcep/Engine.xml:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<subSystemConfig xmlns="urn:xmlns-fujitsu-com:cspf:bdcep:v1">
<!--
    <engineConfig id="CepEngine1">
        <logging>
            <type>bdpp</type>
            <directory>hadoop</directory>
            <loggingMaxOpenFile>6</loggingMaxOpenFile>
            <loggingRotationCycle>300</loggingRotationCycle>
        </logging>
        <socketAdapterPort>9600</socketAdapterPort>
    </engineConfig>
-->
    <engineConfig id="CepEngine2">
        <logging>
            <type>file</type>
        </logging>
        <socketAdapterPort>9601</socketAdapterPort>
    </engineConfig>
</subSystemConfig>

Command execution result:

# cepconfigeng -f /etc/opt/FJSVcep/Engine.xml <ENTER>
Are you sure you want to change the CEP Engine configuration? [y,n,q]:y <ENTER>
Command cepconfigeng executed successfully.

Example of output at abnormal end

When an attempt is made to delete a CEP engine that is running.

# cepconfigeng -f /etc/opt/FJSVcep/Engine.xml <ENTER>
Are you sure you want to change the CEP Engine configuration? [y,n,q]:y <ENTER>
The setup processing failed. EngineId=(CepEngine) Reason=(The job is already running.)
Command cepconfigeng execution failed.