Managing packages and deployment
Managing packages and deployment comprises the following activities:
- Creating a package
- Defining references
- Using analysers
- Adding properties
- Creating instance
- Creating a repository
- Creating a repository
- Adding properties
- Creating instance
- Deploying a package
- Deploying package to environment
- Promoting along route
- Deploying a repository
- Deploying repository to environment
- Promoting along route
Defining the application package (what you will deploy)
- Add a server definition for each computer in the network (see Managing-servers).
Server definitions connect the deployment server to the target computers that provide the components for package instances and to the computers that deploy package instances. For each server, specify the host name and select the NSH agent for communication. - Define a package, which is the container for your application (see Packages and Creating-and-viewing-package-or-repository-instances):
- Give the package an appropriate name (such as "New Web App").
- To the new package, add a reference for each application component. The reference defines the server name and path to each component (in this case, the WAR file and the SQL file). When you enter the URI, use the appropriate format for your platform (for example, file:///tmp/sample.htm for UNIX or file:///C:\Temp\sample.htm for Windows).
- Configure analysers to perform specific actions and identify modules that break down fetched content. Invoke them after a URI has been fetched into the package instance. See Using-analyzers.
- Add the appropriate package properties.
- Create an instance from the new package (see Creating-and-viewing-package-or-repository-instances ).
Creating a repository
- Add a repository. See Managing-repositories-and-instances.
- Add the appropriate repository properties.
- Create a repository instance. See Creating-and-viewing-package-or-repository-instances.
Deploying a package
- Deploy a package to environment. See Creating-and-managing-deployments.
- Deploy the package to the route. In the deployment launchpad, drag and drop the package onto the route to create an instance and then deploy it automatically. See Using-the-launchpad.
- Examine the logs (red and green lights) to find any deployment problems. For more information, see Viewing-deployment-results.
- When you are satisfied with that step, you can promote the deployment to the next environment (for example, from testing to staging).
When you are satisfied that everything works as planned, you can create a schedule to run the deployment step on a regular basis. For more information, see Creating-and-using-deploy-schedules.
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*