Walk-through → Step 11: Designing the Application Process
While application processes consist of steps configured with the process editor, like component processes, they are primarily intended to direct underlying component processes and orchestrate multi-component deployments. The Install Component step, which we will use here, enables you to select a component process from among those defined for each component. Remember that a component can have more than one process defined for it.
You might be wondering why you need to create an application-level process when the process you created for the component should be able to perform the deployment by itself. While individual component processes can be run outside an application process, an environment must still be mapped to it and an agent associated with it, which are done at the application level. For a single-component deployment like helloWorld, an application-level process might not be required. You might also want to skip an application-level process when you are testing or patching a component. But for non-trivial deployments, and especially for deployments that have more than one component, you will want to create one or more application-level processes.
To create an application-level process, you define the individual steps as you did earlier when you created the helloWorld component process.
Figure 1. Item Properties tab
Select the helloWorld component from the Component drop-down menu.
If we wanted this application to install multiple components, we could add a separate Install Component step for each one.
Accept the default values for the other fields.
Figure 2. Finished Application Process
Copyright © 2011–2016 Serena Software, Inc. All rights reserved.