The source file location is defined within the definition by the source element

The source file location is defined within the

This preview shows page 25 - 27 out of 193 pages.

The source file location is defined within the definition by the sourceelement, and its fileSystem(for deployments originating from a file system directory) and iwStore(for deployment originating from a TeamSite area) child elements. Within the fileSystemor iwStoreelement is the element specifying the deployment type:lremoteDiff- a deployment based on the comparison of files residing on the source and the target host orlareaDiff- a deployment based on the comparion of files between two TeamSite areas on the source host orlfilelist- a deployment based on preconfigured list of files orlpayloada deployment based on a query made of files using an adapter.Associated with each of these deployment type elements is the areaattribute. The areaattribute specifies the full path to the source file location. This can either be a file system path (when the fileSystemelement has been specified) or a TeamSite path (when the iwStoreelement has been specified. For example:<definition name="webfiles"><source><fileSystem><remoteDiff area="/dev/website/files">...</remoteDif></fileSystem></source>...</definition>or<definition name="webfiles"><source><iwStore><areaDiff area="/default/main/dev/EDITION"previousArea="/default/main/dev/EDITION/IW_PREV">...OpenDeploy Deployment Configuration Guide25
Background image
Chapter1Deployment Types26OpenDeploy Deployment Configuration Guide</areaDiff></iwStore></source>...</definition>In addition to specifying the areaattribute, different deployment types require the configuration of additional attributes. The configuration for each deployment type is described later in this chapter.Specifying Particular Subdirectories within the Source File LocationYou can specify one or more subdirectories within the area attribute as the source file location. This feature is useful if you want to deploy from some subdirectories within the location specified by the areaattribute, but not others. For example, if the following subdirectories reside within the areaattribute value of /dev/website/files:ldailylweeklylmonthlyyou might only want to deploy files from the dailyand monthlysubdirectories, but not weekly.You can specify the subdirectories you want to include in a deployment using the pathSpecificationelement, where you can specify a subdirectory within the source file location determined by the area attribute value. Each element specifying the deployment type, such as remoteDiffor filelist, must include at least one occurrence of the pathSpecificationelement. Each pathSpecificationelement has an associated pathelement. This pathelement contains a nameattribute whose value is a path relative to the areaattribute, where the files participating in the deployment reside. For example:<remoteDiff area="/dev/website/files"><pathSpecification><path name="daily"></pathSpecification></remoteDif>The pathelement’s nameattribute value can be the name of a directory directly within the specified area attribute value, or a path several levels of directories deep:<path name="daily">or <path name="daily/external/Q104">
Background image
Image of page 27

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture