From the DSM Explorer a Deployment Wizard assists the administrator in deploying Agents.
The wizard guides you step-by-step through the process of creating a deployment job. You can choose from two job types: Deploy Software to Target Computers and Stage Packages at Scalability Server. You select the package to deploy from a list and specify whether it should be deployed to a specific computer or all computers in a specific domain, within an IP address range, or within a directory. The wizard then scans the target computers to find out if deployment is possible on all targets and if credentials are required for deployment.
The wizard provides you with on-screen descriptions for each step and a separate help system.
Figure 1: Deployment Wizard (1 of 8)
The Second screen for the wizard allows you to define what type of deployment job you are creating
Figure 2: Job Type (Step 2 of 8)
Once you have defined the type of job you have to specify what you actually want to deploy
Figure 3: Deployment Payload (3 of 8)
As you can see from this screenshot you can select all agents or just individual agents, Scalability Server and just the basic CAF agent.
If on the Job Type wizard page you selected to deploy to target computers, the Deployment Payload page has a checkbox that you select to transfer packages from the scalability server.
If you select the checkbox, the Configure button becomes available. If you click the Configure button a dialog appears, prompting you to enter the credentials for connecting to the scalability server. You need the scalability server details, name, username, and password.
Now you specify the criteria for the targets for deployment
Figure 4: Deployment Targets Options (4 of 8)
Figure 5: Deployment Targets Domain
Figure 6: Deployment Targets Computers
Figure 7 Deployment Targets IP Range
Figure 8: Deployment Targets Directory
If you click the Browse button you can select from any of the directories configured in Directory Integration (See Directory Integration in the DSM Explorer Help)
You can refine the directory deployment to include Organizational Units either via the browse or with standard LDAP notation
Next you scan the specified criteria to identify actual physical targets
Figure 9: Scanning for Deployment Targets
As you can see the scan detects machines in various states, use the context sensitive help (F1) to identify what each of these states indicates
Now you Select the target computers from the list of discovered computers
Figure 10: Target Selection (6 of 8)
When you select your targets you are prompted to provide an account that can be used to deploy the primer to these targets,
refer to the prerequisites document referenced in "before you begin" for details on what credentials are required
Figure 11: Deployment Credentials
You only have to specify these once if you tick the check box
The next screen depends on the version of DSM and the package you have selected.
Figure 12: Agent Configuration (Step 7 of 8)
Figure 13: Deployment Summary Step 8 of 8)
You are now presented with a Summary of what you have chosen
Once you click finish
The Deployment job is built and displayed in the Deployment Job Status Section, from where you can monitor the deployment job.
Configuring the Deployment Options
As with the rest of DSM the Deployment Manager is configured via the Configuration Policy.
Deployment Configuration Policies
AlwaysDeployPrimer - Set this to True Even if a version of the Primer installed, it will deploy a new one.
This can resolve issue if the primer is corrupt, you will get a fresh install.
The primer is essential to the whole deployment process but there are some considerations that you need to be aware of when using deployment.
- The Primer is only ever sent from the Deployment manager to the target computer. Even if you have chosen the option to have the package sent from a stage on a separate Scalability Server. The primer package is about 8MB so you need to be aware that this will be sent from the deployment manager to each target and that there must be a route between the deployment manager and the target computer.
- The mechanism used to transfer the primer depends on the target OS first and also on what the target will allow.
- If the target is a Windows based platform the default mechanism is to use a network share. The share used is configured in policy (see above). There are extra requirements for some of the lower windows variants which are detailed in the prerequisites documentation.
- If this fails the deployment will fail with no primer transport
- It is possible to install the primer manually on the target systems which then allows deployment of the DSM infrastructure without having to rely on the features of the underlying OS
Instructions for manual install of the primer can be found in docops.ca.com.
Deployment Manager Considerations
If you have selected to 'Transfer packages from scalability server' at Stage 3 (see figure 3) and the deployment will use FTP functionality then the username specified MUST be "anonymous" the password may be left blank.
There is a command line utility DMSWEEP which can be used for the deployment process but this is outside the scope of this document.