Update a Model in a Suite

When an author uses a provided tool to change a model and write it to disk, the updated model is no longer encrypted. To encrypt the new version of a model, the author uses the same technique as for adding a new model to the suite.

In the following example, the author adds a new version of a process model called supernet_v2 to the supernet suite by giving it the same protection as the supernet.pr.m model.

% op_manfile -protect -m supernet_v2 -from_mf supernet.pr.m

--- op_manfile issued the following command: ---
	/bin/cp ./supernet_v2.pr.m
	/usr/author/op_admin/bk/supernet_v2_v1.pr.m

Success.

And the client unlocks a new suite member with “op_manfile -register -m <target> -from_mf <source>”.

% op_manfile -register -m supernet_v2 -from_mf supernet.pr.m

--- op_manfile issued the following command: ---
	/bin/cp /usr/client/op_models/supernet_v2.pr.m
	/usr/client/op_admin/bk/supernet_v2_v2.pr.m

Success.

This copies the authorization record from the source model to the target model (assuming both models belong to the same suite) without requiring the client to call the author again.

If the author would like to replace the model with a model that has the same name, the author can remove the original, replace it with the new version that has the same name, and copy the authorization record from a different model in the suite. The client can register the model similarly. One useful technique is to distribute an “authorization control” model with the suite. The purpose of this model is to hold the authorization record. This model can be an empty process model, for example. The author and client can replace models in the suite and copy the authorization record from the control model.

% op_manfile -protect -m supernet -from_mf control.pr.m

--- op_manfile issued the following command: ---
	/bin/cp ./supernet.pr.m /usr/author/op_admin/bk/supernet_v1.pr.m

Success.