Cisco Cisco Configuration Engine 3.5 Entwickleranleitung

6-29

Cisco Configuration Engine Software Development Kit API Reference and Programmer Guide 3.5

OL-17661-02

Chapter 6 Namespace Administration, Group Administration, and Notification APIs

Group Administration API

Figure 6-5

Rename Group /config/G1/G2

Example:

Given

Figure 6-5

(a), renaming group /config/G1/G2 to /config/G1/G3 using the renameGroup operation

renameGroup (“/config/G1/G2”,”G3”) will throw a MemberAlreadyExistsException because group
/config/G1/G3 already existed.

absGroupId

This is the absolute group ID of the group to be renamed.

newGroupId

This is the new group name to be used.

Return

None.

Exceptions

This method could throw one of the following exceptions:

•

DatastoreAccessException – Data-store connection problem or problem
not described below.

•

OperationTimeoutException – The current operation is not able to
acquire a file lock within the time limit (for synchronizing data-store
access), because other administration operation is currently in process.

•

InvalidInputException

–

See

Table 6-2

for basic rules.

–

After renaming, the resulting absolute group ID cannot violate the
absolute-group-ID string-length restriction.

–

newGroupId cannot contain a slash “/”, because it is used as a
delimiter for group hierarchy.

•

MemberAlreadyExistsException – Member already existed; in other
words, there exists a group with name newGroupId in the same parent
group of absGroupId.

•

ParentNotFoundException – Cannot locate group specified by
absGroupId.

•

MessageFormatException – Problem with message syntax.

Additional exception that can be thrown by the remote API:

CommunicationException – General server access problem.

(a)