You are on page 1of 1

Product Version:

V200R15 and later


Document Version: 02

CME Script Executor


WOFD-186000: CME Basic Services (basic feature)

Why is the script executor


required?
If no script executor exists:
BSC1

Activating scripts
one by one

NodeB1

eNodeB1

Activate data

If the script executor exists:


BSC1

Activating scripts
in batches

NodeB1

eNodeB1

Activate data

What is the script executor?


The script executor is used for activating NE configuration scripts on
NEs.
After finishing data configuration in a planned data area, users can
generate a configuration script in XML or MML format for all
configuration modifications. Users can view or edit the script using the
script executor and remotely activate the script on NEs to make the
modifications take effect. Scripts can be activated on multiple NEs
concurrently.
The script executor allows users to activate and manage configuration
scripts. Users can perform operations such as activate and cancel by
project or task, and monitor the execution status in real time and
query the activation report.
Difference between script project and script task:
All scripts in a folder map a project, and each script file maps a task.

What is the operating principle


of the script executor?

2
3

Import and upload script


Start the script activation task

Start script executor

Script

Script

CME client

Activate scripts

CME server
Forward activation log

NE

Report activation log

Importing a script is a process of uploading the script to the CME client. Uploading a script is a
process of uploading a script from the CME client to the CME server. After the upload is complete,
the CME creates a script project. If the uploaded script files contain a rollback script, the CME
automatically creates a rollback project when creating a project to be activated.
Users are advised to modify the script task description, suspension status, and dependencies
after importing scripts. The information cannot be modified after the scripts are uploaded.
After uploading a script, users can view or edit the script in the script executor.
The script executor provides only a channel for delivering data from the CME to NEs. NEs are
responsible for data check and processing, and then report the result to the CME. The result is
finally displayed in the script executor interface.
Before activating data, users can preactivate the script project to check script validity so as to
solve script problems in advance and prevent activation failure. After the CME issues the
preactivation command to NEs and NEs run the command, data does not take effect on the live
network.

Which activation methods does


the script executor provide?
Manual Activation
Select a specified script project or script task to activate.
After being activated, data takes effect on the live network.

Scheduled Activation
Users specify execution time for a script project in
advance. Then, the CME automatically activates the
script project on the specified time. After being activated,
data takes effect on the live network.

Data processing methods for handling data errors vary with script types:
Break on Failure

Best Efforts

If an error occurs when users are executing an


XML script, all configuration data will roll back to
the pre-activation state.
If an error occurs when users are executing an
MML script, the executed commands before the
erroneous command can be executed
successfully.

Only the MML script supports best efforts. If an error


occurs when users activate a configuration script, the
script executor will skip the erroneous command and
continue. Except the erroneous command, the other
commands can be executed successfully.

Error

Manual/Scheduled
activation of XML script
(Break on failure)

XML

Error

Error

Manual/Scheduled
activation of MML script
(Break on failure)

MML

Error
Error

Manual activation of
MML script
(Best efforts)

MML

NE script types
NE Type

Script Type
Incremental/full script

Controller

Scenario script

Reparenting script

Base station

All

Version

Script Format

Version earlier than


SRAN9.0

MML

SRAN9.0 and later

XML

Version earlier than


SRAN9.0

MML

SRAN9.0 and later

XML or MML, which can


be specified by users

Version earlier than


SRAN9.0

MML

SRAN9.0 and later

XML or MML, which can


be specified by users

All

XML

Copyright Huawei Technologies Co., Ltd.