The Windows common tasks page enables you to view and create components for the following Windows 2000 entities:
Windows applications, separated into three types:
COM+ applications
COM objects
Microsoft Windows installer files (.msi)
Internet Information Server (IIS) applications and support files, separated into five types:
IIS applications
IIS web sites or virtual directory settings
IIS global settings
ISAPI global filter settings
ISAPI web site filter settings
Other common Windows files, separated into five types:
Registry keys
Registry files
Data source names
Batch files
Scripting host scripts
Before you can deploy a file or application across systems, you have to make the file or application known to the N1 Grid Service Provisioning System software and wrap it into a component.
Although the general approach that you follow is the same for all component types, details differ depending on the actual types that you need to use.
Select the Windows icon under the Common Tasks section of the left control panel.
Click the Create New link next to the component type you need to create.
For example, to create a component that contains a batch file, follow these steps:
On the Components Details Edit page, fill in the appropriate information.
For example, for a batch file, fill in this information:
Click Check in Selected Item.
You can also create a component through the command line. For more information about commands, see cdb.rsrc: Managing Components in N1 Grid Service Provisioning System 5.0 Command-Line Interface Reference Manual.
For a simple file, such as a batch file, a command file, or a dynamic linked library file, use the following command:cr_cli -cmd cdb.rsrc.ci -src filename -dst component-name -u username -p password
where:
filename is the name of the file that you want to check in.
component-name is the name that you want to use for the component
For files that you have to browse, such as COM+ applications, registry keys, or data source names, the command is more complex. If you have exported the file, you can use an “Exported File Browser” to check in the file. In the command, you have to specify the sourcePath. The sourcePath is the path that you would see when you browse for a file of this component type in the browser interface.
The following example checks in a data source name from a file dsn.n1test.
%> cr_cli -cmd cdb.rsrc.ci -src exported/dsn.n1test -dst dsn.n1test -type 'com.sun.windows#data source name' -platform 'NM:system#Windows 2000 Server' -pickerName 'Exported File Browser' -extraOpts sourcePath='System DSNn\\1test\\' -u **** -p **** |
Capture the component as described above.
Go to the Components section of the N1 Grid Service Provisioning System application.
Choose the component to deploy.
Depending on the type of component that you choose to deploy, you might have to define variables or to perform other steps. At a minimum, you perform the rest of the steps listed here.
Click Run in the Actions column next to the Default:Install procedure.
A plan details page appears for running the installation procedure.
Choose a target host.
The target host should be a host for which the component that you are deploying applies. For example, deploying a Microsoft Windows IIS application to a non-Windows host would not be appropriate.
Click Run Plan.