FTM SWIFT commands and the configuration process

The life-cycle states allow you to make controlled changes to FTM SWIFT entities. You do this by entering FTM SWIFT commands on the command-line interface (CLI). You must also have the appropriate access rights to the commands. The commands that you can issue are dependent on the state of the entity. Table 1 shows the relationship between the stages, commands, and states. For example, you cannot deploy an entity before it was committed and approved. You use some commands only to update an entity. Others are required to move an entity from one state to another.

Table 1. FTM SWIFT commands and how they fit into the configuration process
Stage	Command	Description	Life-cycle state
Modification	cre	create	In process
	del	delete	In process
	mod	modify	In process
	add	add	In process
	rem	remove	In process
	com	commit	In process → Committed
	rej	reject	Committed → In process
Approval	app	approve	For configuration entities: Committed → Approved
	app	approve	For security entities: Committed → Approved and activated
	ra	reject approval	Approved → Committed
Activation	dep	deploy	For configuration entities: Approved → Deployed and activated

Issue the cre (create) command to create an FTM SWIFT entity. After you create and deploy the entity, you can issue the add command to create COs and specify their attributes. For example, after you create and deploy a CT, you can then add a CO of that type to an OU.

The rem (remove) command takes away something from an FTM SWIFT entity. For example, you can remove a configuration object from an OU. The CT still exists, and you can add it to another OU. You use the del (delete) command to erase an entity.

You use some of the commands, such as the app (approve) command, differently depending on whether you are working with a configuration entity or a security entity. These differences are described in more detail in Difference in the process flow for configuration entities and security entities.