Publish a Management of Change (MoC) package

A local Management of Change (MoC) package will need to be published to the package store (managed by the MOCOrchestrator service) so it can be distributed to other systems.

To publish an MoC package

1. On the desktop, double-click the Windows PowerShell for DNA shortcut.

   Windows PowerShell for DNA opens.

2. Execute the following commands:

   set-silo RealTime

   dnapackage publish --package <package file path> [--emergency] [--dalfolder <DAL configuration folder> --username <remote username> --password <remote password>]

   Where:

   • --package <package file path> is the fully qualified path to the package file you want to apply to the system.

   • --emergency is an optional parameter to specify that the package being published is high priority and will be deployed through an emergency workflow as defined in AVEVA Workflow Management.

     Note: If this optional parameter is not specified it will be deployed through the standard workflow in AVEVA Workflow Management.

   • --dalfolder <DAL configuration folder> is the DAL configuration folder name on the remote system you are trying to connect to (for example, --dalfolder systemName\control_room).

   • --username <remote username> is the username of the user on the remote system you are trying to connect to.

   • --password <remote password> is the password of the user on the remote system you are trying to connect to.

     Note: The --dalfolder <DAL configuration folder>, --username <remote username>, and --password <remote password> parameters do not need to be included if you are publishing a package on the same server as the MOCOrchestrator service. These parameters are mandatory if you are publishing a package on any other server that does not have the MOCOrchestrator service. For example, publishing a package on the Production MoC zone would require remote DAL configuration to connect to the MOCOrchestrator service.

     For example:

     dnapackage publish --package C:\temp\package.pkg or dnapackage publish --package C:\temp\package.pkg [--emergency]

If the command was successful, a message similar to the following will appear:

Successfully published package C:\temp\package.pkg to myServer.org

Note: After a package is successfully published, the local package file (for example, C:\temp\package.pkg) is removed and will only remain in the package store.