Link packages to create dependencies

You can use the Management of Change (MoC) Package tool (dnapackage) to create dependencies between two or more existing MoC packages.

Note: The package store (managed by the MOCOrchestrator service) must be available to successfully execute this command.

To link MoC packages to create dependencies

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 link --title <package title> --dependency <package title> [--dalfolder <DAL configuration folder> --username <remote username> --password <remote password>]

   Where:

   • --title <package title> is the title of the dependent (child) package.

   • --dependency <package title> is the title of the antecedent (parent) package.

   • --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 linking packages on the same server as the MOCOrchestrator service. These parameters are mandatory if you are linking packages on any other server that does not have the MOCOrchestrator service. For example, linking packages on the Production MoC zone would require remote DAL configuration to connect to the MOCOrchestrator service.

     For example, to make the package titled "PackageB" depend on the package titled "PackageA" (i.e., "PackageA" needs to be deployed before "PackageB"), the command would be as follows:

     dnapackage link --title "PackageB" --dependency "PackageA"

     Note: Linking packages creates a dependency on one package to another. This will prevent a dependent (child) package from being installed unless the antecedent (parent) package is installed. In the previous example, PackageB could not be installed on a system until PackageA is installed.