terminology

33
Solution Deployment Descriptor TC Profile Primer Draft v0.11 Working Draft, 10 May 2007 Artifact Identifier: Location: Artifact Type: Non-conformant information associated with the SDD specification Technical Committee: OASIS Solution Deployment Descriptor (SDD) TC Chair(s): Brent Miller Editor(s): Related work: None Abstract: Status: 4 April 2007 Copyright © OASIS Open 2005, 2007. All Rights Reserved. Page 1 of 33 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 1 2 3

Upload: cameroon45

Post on 26-May-2015

771 views

Category:

Documents


2 download

TRANSCRIPT

Page 1: Terminology

Solution Deployment Descriptor TC

Profile Primer Draft v0.11

Working Draft, 10 May 2007

Artifact Identifier:

Location:

Artifact Type:Non-conformant information associated with the SDD specification

Technical Committee:OASIS Solution Deployment Descriptor (SDD) TC

Chair(s):Brent Miller

Editor(s):Related work:

None

Abstract:Status:

4 April 2007 Copyright © OASIS Open 2005, 2007. All Rights Reserved. Page 1 of 30

1

2

3

4

5678

910

111213

1415

161718

192021

22

12

3

Page 2: Terminology

Notices

Copyright © OASIS® 1993–2007. All Rights Reserved. OASIS trademark, IPR and other policies apply.

All capitalized terms in the following text have the meanings assigned to them in the OASIS Intellectual Property Rights Policy (the “OASIS IPR Policy”). The full Policy may be found at the OASIS website.

This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published, and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this section are included on all such copies and derivative works. However, this document itself may not be modified in any way, including by removing the copyright notice or references to OASIS, except as needed for the purpose of developing any document or deliverable produced by an OASIS Technical Committee (in which case the rules applicable to copyrights, as set forth in the OASIS IPR Policy, must be followed) or as required to translate it into languages other than English.

The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors or assigns.

This document and the information contained herein is provided on an “AS IS” basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY OWNERSHIP RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

OASIS requests that any OASIS Party or any other party that believes it has patent claims that would necessarily be infringed by implementations of this OASIS Committee Specification or OASIS Standard, to notify OASIS TC Administrator and provide an indication of its willingness to grant patent licenses to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification.

OASIS invites any party to contact the OASIS TC Administrator if it is aware of a claim of ownership of any patent claims that would necessarily be infringed by implementations of this specification by a patent holder that is not willing to provide a license to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification. OASIS may include such claims on its website, but disclaims any obligation to do so.

OASIS takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on OASIS’ procedures with respect to rights in any document or deliverable produced by an OASIS Technical Committee can be found on the OASIS website. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this OASIS Committee Specification or OASIS Standard, can be obtained from the OASIS TC Administrator. OASIS makes no representation that any information or list of intellectual property rights will at any time be complete, or that any claims in such list are, in fact, Essential Claims.

4 April 2007 Copyright © OASIS Open 2005, 2007. All Rights Reserved. Page 2 of 30

23

24

2526

2728293031323334

3536

3738394041

4243444546

4748495051

5253545556575859606162

45

6

Page 3: Terminology

Table of Contents1 Introduction......................................................................................................................................... 5

1.1 Terminology....................................................................................................................................... 5

1.2 Purpose............................................................................................................................................. 5

1.3 Scope................................................................................................................................................ 5

1.4 Audience........................................................................................................................................... 5

1.5 Motivation.......................................................................................................................................... 5

1.6 Requirements.................................................................................................................................... 5

1.7 Notational Conventions..................................................................................................................... 6

1.8 Document Conventions.....................................................................................................................6

1.9 Normative References....................................................................................................................... 6

2 Profile Primer...................................................................................................................................... 7

2.1 Profile Classes.................................................................................................................................. 7

3 SDD Examples.................................................................................................................................. 15

3.1 Dell.................................................................................................................................................. 15

3.2 IBM.................................................................................................................................................. 15

3.2.1 JRE Example........................................................................................................................... 15

3.3 MacroVision..................................................................................................................................... 17

3.3.1 InstallAnywhere - MacOS.........................................................................................................17

3.3.2 InstallAnywhere - Windows......................................................................................................21

3.4 SAP................................................................................................................................................. 25

3.4.1.................................................................................................................................................. 25

3.5 SAS................................................................................................................................................. 25

3.5.1 SAS MC Example.................................................................................................................... 25

4 Profile Examples............................................................................................................................... 26

4.1 Dell.................................................................................................................................................. 26

4.2 IBM.................................................................................................................................................. 26

4.2.1 JRE – Profile Example.............................................................................................................26

4.3 MacroVision..................................................................................................................................... 27

4.3.1 InstallAnywhere - MacOS.........................................................................................................28

4.3.2 InstallAnywhere – Windows.....................................................................................................28

4.4 SAP................................................................................................................................................. 30

4.5 SAS................................................................................................................................................. 30

4 April 2007 Copyright © OASIS Open 2005, 2007. All Rights Reserved. Page 3 of 30

63

64

65

66

67

68

69

70

71

72

73

74

75

76

77

78

79

80

81

82

83

84

85

86

87

88

89

90

91

92

93

94

95

96

97

98

78

9

Page 4: Terminology

1 IntroductionThe Solution Deployment Descriptor (SDD) TC profile primer is derivative of the current specification and associated schema. The intent is to capture the knowledge of the SDD community to promote interoperability.

Profile shown here exploit and extend CIM models as necessary.

Profiles ought to exhibit consistency hierarchy within class, e.g.

o OS.ResourceType.HostResourceType

The profiles are non-normative.

Ontology is a data model that represents a set of concepts within a domain and the relationships between those concepts. It is used to reason about the objects within that domain.

An informal ontology may be specified by a catalog of types that are either undefined or defined only by statements in a natural language. An informal ontology may be specified by a collection of names for concept and relation types organized in a partial ordering by the type-subtype relation.

The profile primer presented here along with associated information presented here constitute an informal ontology that leverages natural language, partial ordering and provides a means of reasoning about objects within the domain.

1.1 Terminology

1.2 PurposeThe purpose of this document is to provide documentation on accepted dictionary terms, definition and the context in which the terms and definitions have meaning. The dictionary is to provide a root profile on which other profiles may be constructed.

1.3 ScopeThe scope of this document is definition of a dictionary and related profiles that are associated with the v1.0 specification.

1.4 AudienceThis document is intended to assist community of SDD producers and consumers.

1.5 MotivationThe motivation for producing this document is to promote interoperability and to engage the greater SDD technical community in the production and consumption of the SDD specification.

1.6 RequirementsThe dictionary is to provide a first reference source for producers of SDDs.

4 April 2007 Copyright © OASIS Open 2005, 2007. All Rights Reserved. Page 4 of 30

99

100101102

103

104

105

106107

108

109110

111112113

114115116

117

118

119

120121122

123

124125

126

127

128

129

130131

132

133

1011

12

Page 5: Terminology

1.7 Notational ConventionsTBD

1.8 Document ConventionsTBD

1.9 Normative References[RFC2119] S. Bradner, Key words for use in RFCs to Indicate Requirement Levels,

http://www.ietf.org/rfc/rfc2119.txt, IETF RFC 2119, March 1997.[XMLDSIG-CORE] Bartel et al., XML-Signature Syntax and Processing,

http://www.w3.org/TR/xmldsig-core/, W3C Recommendation, February 2002.[XSD] W3C Schema Working Group, XML Schema,

http://www.w3.org/TR/xmlschema-1/, W3C Recommendation, October 2004.[ISO639.2] Library of Congress, Codes for the Representation of Names of Languages,

http://www.loc.gov/standards/iso639-2/englangn.html.[ISO3166] International Organization for Standardization, English Country Names and Code

Elements, http://www.iso.ch/iso/en/prods-services/iso3166ma/02iso-3166-code-lists/list-en1.html.

[XPATH] Clark et al., XML Path Language (XPath) Version 1.0, http://www.w3.org/TR/xpath, W3C Recommendation, November 1999.

[IANA-CHARSET] Internet Assigned Numbers Authority, Character Sets, http://www.iana.org/assignments/character-sets, modified December 2006.

[CONFORM] OASIS, OASIS Conformance Requirements for Specifications 1.0, http://www.oasis-open.org/committees/download.php/305/conformance_requirements-v1.pdf.

4 April 2007 Copyright © OASIS Open 2005, 2007. All Rights Reserved. Page 5 of 30

134

135

136

137

138

139

140141142143144145146147148149150151152153154155156157

158

1314

15

Page 6: Terminology

2 Profile Primer

Profiles provide the means for communicating which resource types an implementation supports and on which the SDD depends. A core assumption is that an understanding of specific resource types and resource characteristics is shared by the deployment descriptor author and the deployment environment.

For example, if the deployment descriptor author declares a resource type for a particular operating system, deployment software operating on the SDD needs to understand how to discover operating systems of that type in order to honor the SDD author’s intent while deploying that SDD.

Assumption is that the profiles are:

Base on the CIMv2.1.5 model and associated classes Based on plausible extensions to the CIM Declarations based on the needs of the SDD specification.

2.1 Profile Classes

Class Name Source Description

ComputerSystem CIM Is derived from CIM_System and is a special class representing a special collection of managed elements and as an aggregation point for one or more elements such as file system, operating system, processor, memory, etc.

Processor CIM CIMv2.15 CIM_Processor

Virtualization CIM CIMv2.15 CIM_Virtualization

OperatingSystem CIM CIMv2.15 CIM_OperatingSystem

FileSystem CIM CIMv2.15 CIM_FileSystem

Directory CIM CIMv2.15 CIM_Directory

ApplicationSystem CIM CIMv2.15 CIM_ApplicationSystem.Application

Application software is software that has been operationalized and that has state. The CIM ApplicationSystem class represents an application or a software system that supports a particular business function and that can be managed as an independent unit. Needs SDD extensions.

InstalledSoftware SDD SDDv1.0 SDD_InstalledSoftware

DatabaseSystem CIM CIMv2.15 CIM_DatabaseSystem

4 April 2007 Copyright © OASIS Open 2005, 2007. All Rights Reserved. Page 6 of 30

159

160

161162163

164165166

167

168

169170171172173

174

175

176

177

178

1617

18

Page 7: Terminology

ComputerSystem

Class

Source: CIMv2.15 CIM_ComputerSystem

Processor

Class

Source: CIMv2.1.5 CIM_Processor

Relationship: derived from within ComputerSystem

Family

Attribute

Source: CIMv2.15 CIM_Processor.Family

SDD Usage: PropertyConstraint

Valid Values; e.g. Other, Unknown, 8086, 80286, 80386, 80486 , 8087, AMD Athlon(TM) Processor Family

Model

Attribute

Source: Extension to CIM, CIM_Processor.Model

SDD Usage: PropertyConstraint

Valid Values; TBD

Number of Processors

Attribute

Source: SDD ComputerSystem.NumberofProcessors

SDD Usage: PropertyConstraint

Valid Values; Values are numbers 1 to n

Virtualization

Class

Source: CIMv2.15 CIM_Virtualization

Relationship: derived from within ComputerSystem

VirtualSystemIdentifier

Attribute

Source: CIMv2.15 Virtualization.VirtualSystemIdentifier

SDD Usage: TBD

Valid Values; “String”

4 April 2007 Copyright © OASIS Open 2005, 2007. All Rights Reserved. Page 7 of 30

179

180

181182

183

184

185

186

187

188

189

190

191

192

193

194

195196

197

198

199

200

201

202

203

204

205

206

207

208

209

210

211

212

213

214

215

216

217

218

219

220

1920

21

Page 8: Terminology

VirtualSystemType

Attribute

Source: CIMv2.15 Virtualization.VirtualSystemType

SDD Usage: TBD

Valid Values; “String”

OperatingSystem

Class

Source: CIMv2.15 CIM_OperatingSystem

Relationship: derived from within ComputerSystem

consumesArtifacts SDD TargetResourceRef ArtifactType

hosts FileSystem, InstalledSoftware, DatabaseSystem, Application

completionActions Restart, Logout

SDD Usage: Resource.Type, requiredBase

OSType

Attribute

Source: CIMv2.15 CIM_OperatingSystem.OSType

SDD Usage: PropertyConstraint

Valid Values; e.g. “Unknown", "Other", "MACOS", "ATTUNIX", "DGUX","DECNT", "Tru64 UNIX", "OpenVMS", "HPUX", "AIX","MVS", "OS400", "OS/2", "JavaVM", "MSDOS", "WIN3x", "WIN95","WIN98", "WINNT", "WINCE","NCR3000", "NetWare", "OSF", "DC/OS", "Reliant UNIX","SCO UnixWare", "SCO OpenServer", "Sequent", "IRIX","Solaris","SunOS", "U6000", "ASERIES","HP NonStop OS" "HP NonStop OSS", "BS2000", "LINUX","Lynx", "XENIX", "VM","Interactive UNIX", "BSDUNIX", "FreeBSD", "NetBSD", "GNU Hurd", "OS9", "MACH Kernel", "Inferno", "QNX", "EPOC", "IxWorks", "VxWorks", "MiNT", "BeOS", "HP MPE", "NextStep", "PalmPilot", "Rhapsody", "Windows 2000", "Dedicated", "OS/390", "VSE", "TPF", "Windows (R) Me","Caldera Open UNIX", "OpenBSD", "Not Applicable", "Windows XP", "z/OS", "Microsoft Windows Server 2003", "Microsoft Windows Server 2003 64-Bit"

TotalVisibleMemorySize (aka “system memory”)

Attribute

Source: CIMv2.15 CIM_OperatingSystem.TotalVisibleMemorySize

SDD Usage: ConsumptionConstraint

Valid Values Values are numbers and units of measure.

Version

Attribute

Source: CIMv2.15 CIM_OperatingSystem.Version

SDD Usage: PropertyConstraint

Valid Values Values are numbers of form x.y.z

InstallArtifact

4 April 2007 Copyright © OASIS Open 2005, 2007. All Rights Reserved. Page 8 of 30

221

222

223

224

225

226

227

228

229

230

231

232

233

234

235

236

237

238

239

240

241

242243244245246247248249250

251

252

253

254

255

256

257

258

259

260

261

262

263

264

2223

24

Page 9: Terminology

Attribute

Source: SDD.Install.Artifact

SDD Usage: PropertyConstraint

Valid Values e.g. RPM, ZIP, JAR, TAR, installP, MSI, EXE, WAR, pkg, mpkg, gz

FileSystem

Class

Source: CIMv2.15 CIM_FileSystem

Relationship: hostedBy OperatingSystem

consumesArtifacts [N/A]

completionActions [N/A]

hosts Directory, Files

SDD Usage: Resource.Type

Root

Attribute

Source: CIMv2.15 CIM_FileSystem.Root

SDD Usage: PropertyConstraint

Valid Values: /usr, c:\, d:\ , “other”

AvailableSpace

Attribute

Source: CIMv2.15 CIM_FileSystem.AvailableSpace

SDD Usage: ConsumptionConstraint

Valid Values: Values are numbers and units of measure. Default is total number of free space for filesystem in bytes.

FileSystemType

Attribute

Source: CIMv2.15 CIM_FileSystem.FileSystemType

SDD Usage: PropertyConstraint

Valid Values Include: e.g. JFS, RAW, UFS, FFS, BSD, NTFS, FAT32, VxFS, OJFS, “other”

ReadOnly

Attribute

Source: CIMv2.15 CIM_FileSystem.ReadOnly

SDD Usage: PropertyConstraint

Valid Values: boolean

Directory

4 April 2007 Copyright © OASIS Open 2005, 2007. All Rights Reserved. Page 9 of 30

265

266

267

268

269

270

271

272

273

274

275

276

277

278

279

280

281

282

283

284

285

286

287

288

289

290291

292

293

294

295

296

297

298

299

300

301

302

303

304

305

306

2526

27

Page 10: Terminology

Class

Source: CIMv2.15 CIM_Directory

Definition:: “… Directory is a type of File that logically groups Files 'contained' in it, and provides path information for the grouped Files…”

Relationship: hostedBy Operating System, FileSystem

consumesArtifacts [N/A]

completionActions [N/A]

hosts Files

SDD Usage: Resource.Type

Type

Attribute

Source: CIMv2.15 CIM_Directory.Type

SDD Usage: PropertyConstraint

Valid Values Include: Windir, SystemRoot, TEMP, TMP,

ProgramFiles, /usr, /Tmp, /Var, /root, /swap , /home

ReadOnly

Attribute

Source: Extends CIMv2.15 CIM_Directory.ReadOnly

SDD Usage: PropertyConstraint

Valid Values: boolean

InstalledSoftware

Class

Source: SDD.InstalledSoftware

SDD Definition:: Installed software is software that has been operationalized within a computer

system, e.g. device driver, font, etc.

Relationship: hostedBy OperatingSystem

consumesArtifacts [N/A]

completionActions [N/A]

hosts Product, Feature, Component, KernelComponent, SupportPak

SDD Usage: Resource.Type

InstalledSoftwareType

Attribute

Source: SDD InstalledSoftware.InstalledSoftwareType

SDD Usage: PropertyConstraint

Valid Values Include: Product, Feature, Component, KernelComponent, SupportPak

InstallType

4 April 2007 Copyright © OASIS Open 2005, 2007. All Rights Reserved. Page 10 of 30

307

308

309310

311

312

313

314

315

316

317

318

319

320

321

322

323

324

325

326

327

328

329

330

331

332

333

334

335

336

337

338

339

340

341

342

343

344

345

346

347

348

2829

30

Page 11: Terminology

Attribute

Source: SDD InstalledSoftware.InstallType

SDD Usage: PropertyConstraint

Valid Values Include: base, updated, fix??

Vendor

Attribute

Source: SDD InstalledSoftware.Vendor

SDD Usage: PropertyConstraint

Valid Values Include: e.g. CA, IBM, Macrovision, SAP, SAS

Lang

Attribute

Source: ISO 639-1 Codes

SDD Usage: PropertyConstraint

Valid Values Include: “string” 2 characters, e.g. EN, DE,IT

Version

Attribute

Source: CIMv2.15 CIM_SoftwareIdentity.Version

SDD Usage: PropertyConstraint

Valid Values are numbers of form w.x.y.z

InstallArtifact

Attribute

Source: SDD.Install.Artifact

SDD Usage: PropertyConstraint

Valid Values e.g. RPM, ZIP, JAR, TAR, installP, MSI, EXE, WAR, pkg, mpkg, gz

Application

Class

Source: CIMv2.15 CIM_ApplicationSystem.Application

SDD Definition:: An application is software that has been operationalized and that has state. The CIM ApplicationSystem class represents an application or a software system that supports a particular business function and that can be managed as an independent unit.

Relationship: hostedBy OperatingSystem

consumesArtifacts [N/A]

4 April 2007 Copyright © OASIS Open 2005, 2007. All Rights Reserved. Page 11 of 30

349

350

351

352

353

354

355

356

357

358

359

360

361

362

363

364

365

366

367

368

369

370

371

372

373

374

375

376

377

378

379

380

381

382

383

384385386

387

388

389

390

3132

33

Page 12: Terminology

completionActions [N/A]

hosts

SDD Usage: Resource.Type

ApplicationType

Attribute

Source: SDD_Application.name

SDD Usage: PropertyConstraint

Valid Values “string”, e.g. JRE, InstallAnywhere

EnabledState

Attribute

Source: CIMv2.15 CIM_ApplicationSystem.EnabledState

SDD Usage: PropertyConstraint

Valid Values Include: e.g. Unknown, enabled, disabled, shutting down, starting, DMTF, Vendor Reserved (enum:: 0, 2, 3, 4, 10, 11..32767, 32768..65535)

Version

Attribute

Source: CIMv2.15 CIM_SoftwareIdentity.Version

SDD Usage: PropertyConstraint

Valid Values are numbers of the form w.x.y.z

InstallArtifact

Attribute

Source: SDD.Install.Artifact

SDD Usage: PropertyConstraint

Valid Values e.g. RPM, ZIP, JAR, TAR, installP, MSI, EXE, WAR, pkg, mpkg, gz

DatabaseSystem

Class

Source: CIMv2.15 CIM_DatabaseSystem (which extends CIM_ApplicationSystem)

Relationship: hostedBy OperatingSystem

consumesArtifacts [N/A]

completionActions [N/A]

hosts Applications, InstalledSoftware, CommonDatabase

4 April 2007 Copyright © OASIS Open 2005, 2007. All Rights Reserved. Page 12 of 30

391

392

393

394

395

396

397

398

399

400

401

402

403

404

405

406

407

408

409410

411

412

413

414

415

416

417

418

419

420

421

422

423

424

425

426

427

428

429

430

431

432

3435

36

Page 13: Terminology

SDD Usage: Resource.Type

4 April 2007 Copyright © OASIS Open 2005, 2007. All Rights Reserved. Page 13 of 30

433

434

435

436

437

438

439

440

3738

39

Page 14: Terminology

3 SDD Examples

3.1 Dell

3.2 IBM

3.2.1 JRE Example  <?xml version="1.0" encoding="UTF-8" ?>

- <sdd-dd:DeploymentDescriptor xmlns:sdd-dd="urn:oasis:names:tc:SDD:1:0:deploymentDescriptor" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:oasis:names:tc:SDD:1:0:deploymentDescriptor wd-sdd-deploymentDescriptor-1.0.xsd" descriptorID="20101111111111111111111111111111" lastModified="2006-10-07T09:30:00.0Z" schemaVersion="1.0">

- <Topology>

- <Resource type="AIX" id="os">

- <HostedResource id="UsrFilesys" type="FileSystem">

  <Description>This is the /USR logical filesystem on AIX</Description>

- <Property>

  <PropertyName>Root</PropertyName>

  <Value>/usr</Value>

  </Property>

  </HostedResource>

- <HostedResource id="JRE" type="InstalledSoftware">

  <Name>Java(TM) Runtime Environment, Standard Edition</Name>

  </HostedResource>

  </Resource>

  </Topology>

- <InstallableUnit id="ID000026" targetResourceRef="os">

- <Identity softwareID="2000-123">

  <Name>Java Platform, Standard Edition Runtime Environment"</Name>

  <Version>1.5.0</Version>

  <BuildInformation buildID="1.5.0_0-b08" />

  <Description>Lets you develop and deploy Java applications on desktops and servers, as well as today's Embeded and Realtime environments. Java SE includes classes that support the development of Java Web Services and provides the foundation for Java Platform, Enterprise Edition (Java EE).</Description>

  <ShortDescription>Java Platform for software development</ShortDescription>

- <Manufacturer>

  <Name>Sun Microsystems, Inc.</Name>

- <Location>

- <Country>

  <Name>U.S.A.</Name>

  </Country>

- <Address>

4 April 2007 Copyright © OASIS Open 2005, 2007. All Rights Reserved. Page 14 of 30

441

442

443

444

445

446447

448449450451452

453

454

455

456

457

458

459

460

461

462

463

464

465

466

467

468

469

470

471

472473474

475

476

477

478

479

480

481

482

4041

42

Page 15: Terminology

  <Name>901 San Antonio Rd., Palo Alto, CA 94025</Name>

  </Address>

  </Location>

  </Manufacturer>

  </Identity>

- <Variables>

- <Parameter sensitive="false" id="logging.defaultlevel" defaultValue="Level.INFO">

  <Description>Default logging level for logging messages coming from JRE</Description>

  </Parameter>

  </Variables>

- <Requirements>

- <Requirement id="OSLevel">

  <Description>This JRE requires an AIX Operating System at a version of at least 5.1. Sun has certified all versions of AIX between 5.1 and 5.3</Description>

- <ResourceDeclaration id="osMinimumVersionCheck" resourceRef="os">

  <Description>This JRE requires a version of AIX or 5.1 or later. It has been certified on versions of AIX between 5.1 and 5.3.</Description>

- <Version>

  <MinVersion>5.1</MinVersion>

- <Certified>

  <MinVersion>5.1</MinVersion>

  <MaxVersion>5.3</MaxVersion>

  </Certified>

  </Version>

  </ResourceDeclaration>

  </Requirement>

- <Requirement id="UsrDiskSpace">

  <Description>This JRE requires 2688 512-byte blocks of available space on the /usr file system</Description>

- <ResourceDeclaration id="UsrDiskSpaceCheck" resourceRef="UsrFilesys">

- <Consumption>

  <PropertyName>AvailableSpace</PropertyName>

  <Value>2688</Value>

  </Consumption>

  </ResourceDeclaration>

  </Requirement>

  </Requirements>

- <ResultingResource resourceRef="JRE">

  <Description>An instance of Java(TM) Runtime Environment, Standard Edition Version 5.0 is installed as a result of this deployment</Description>

  <Name>Java(TM) Runtime Environment, Standard Edition</Name>

  <Version>1.5.0</Version>

  </ResultingResource>

- <Unit>

- <!--

This is not a relocatable RPM

  -->

  <InstallArtifact type="rpm" fileRef="jre-1_5_0_00-aix.rpm" />

  <UninstallArtifact />

4 April 2007 Copyright © OASIS Open 2005, 2007. All Rights Reserved. Page 15 of 30

483

484

485

486

487

488

489

490

491

492

493

494

495496

497

498499

500

501

502

503

504

505

506

507

508

509

510

511

512

513

514

515

516

517

518

519

520521

522

523

524

525

526

527

528529

530

4344

45

Page 16: Terminology

  </Unit>

  </InstallableUnit>

  </sdd-dd:DeploymentDescriptor>

3.3 MacroVision

3.3.1 InstallAnywhere - MacOS

<?xml version="1.0" encoding="UTF-8" ?>

- <sdd-dd:DeploymentDescriptor xmlns:sdd-dd="urn:oasis:names:tc:SDD:1:0:deploymentDescriptor" xmlns:sdd-common="urn:oasis:names:tc:SDD:1:0:common" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ibmbuild="http://www.ibm.com/xmlns/prod/autonomic/solutioninstall/build" xsi:schemaLocation="urn:oasis:names:tc:SDD:1:0:deploymentDescriptor wd-sdd-deploymentDescriptor-1.0.xsd" schemaVersion="1.0" lastModified="2006-10-13T09:30:47.0Z" descriptorID="60101111111111111111111111111111">

- <sdd-dd:Topology>

- <sdd-dd:Resource id="os" type="OperatingSystem">

- <sdd-dd:HostedResource id="JRE" type="InstalledSoftware">

- <!--

Does the JRE really need to specify that it hosts IA?

  -->

  <sdd-dd:HostedResource id="InstallAnywhere" type="Application" />

  </sdd-dd:HostedResource>

- <sdd-dd:HostedResource id="eclipseJRE" type="InstalledSoftware">

- <!--

Should I really care about the eclipse JRE?

  -->

- <sdd-dd:HostedResource id="eclipse" type="PluggableApplication">

- <!--

What should we call this type?

  -->

  <sdd-dd:HostedResource id="InstallAnywhereCollaboration" type="Application" />

  </sdd-dd:HostedResource>

  </sdd-dd:HostedResource>

  </sdd-dd:Resource>

  </sdd-dd:Topology>

- <sdd-dd:InstallableUnit id="ID000026" targetResourceRef="os">

- <sdd-dd:Identity softwareID="2000-123">

  <sdd-dd:Name>InstallAnywhere Enterprise Mac Bundle"</sdd-dd:Name>

- <!--

should this be in common?

  -->

  <sdd-dd:Version>8.0</sdd-dd:Version>

  <sdd-dd:BuildInformation buildID="8.0.1000" />

  <sdd-dd:Description>Fooooo</sdd-dd:Description>

- <!--

should this be in common?

4 April 2007 Copyright © OASIS Open 2005, 2007. All Rights Reserved. Page 16 of 30

531

532

533

534

535

536

537538

539540541542543544

545

546

547

548

549

550551

552

553

554

555

556557

558

559

560561

562

563

564

565

566

567

568

569

570

571572

573

574

575

576

4647

48

Page 17: Terminology

  -->

  <sdd-dd:ShortDescription>Foo</sdd-dd:ShortDescription>

- <sdd-dd:Manufacturer>

  <sdd-dd:Name>Macrovision</sdd-dd:Name>

- <sdd-dd:Location>

- <sdd-dd:Country>

  <sdd-dd:Name>U.S.A.</sdd-dd:Name>

  </sdd-dd:Country>

- <sdd-dd:Address>

  <sdd-dd:Name>900 National Parkway</sdd-dd:Name>

  </sdd-dd:Address>

  </sdd-dd:Location>

  </sdd-dd:Manufacturer>

  </sdd-dd:Identity>

- <sdd-dd:Variables>

- <sdd-dd:Parameter id="IAInstallLocation">

  <sdd-dd:DisplayName>Select the folder where would you like to install InstallAnywhere.</sdd-dd:DisplayName>

  </sdd-dd:Parameter>

- <sdd-dd:Parameter id="getInstallIACollaboration" defaultValue="FALSE">

  <sdd-dd:DisplayName>Would you like to Install IA Collaboration?</sdd-dd:DisplayName>

  </sdd-dd:Parameter>

- <sdd-dd:Parameter id="EclipseLocation">

- <!--

I'd like to be able to prompt for this value only if getInstallIACollaboration is true. Is it possible to tell the runtime to do that?

  -->

  <sdd-dd:DisplayName>Specify the location of your Eclipse environment</sdd-dd:DisplayName>

  </sdd-dd:Parameter>

  </sdd-dd:Variables>

- <sdd-dd:Requirements>

- <sdd-dd:Requirement id="OSLevel">

  <sdd-common:Description>The Mac bundle requires OS X.3</sdd-common:Description>

- <!--

should this be in common?

  -->

- <sdd-dd:ResourceConstraint id="osMinimumVersionCheck" resourceRef="os">

  <sdd-common:Description>Checking for Mac 10.3</sdd-common:Description>

- <sdd-dd:VersionConstraint>

- <!--

<sdd-dd:Supported> Change Randy proposed 4/30

  -->

- <sdd-dd:Range>

  <sdd-dd:MinVersion>10.3</sdd-dd:MinVersion>

  </sdd-dd:Range>

- <!--

</sdd-dd:Supported>

4 April 2007 Copyright © OASIS Open 2005, 2007. All Rights Reserved. Page 17 of 30

577578

579

580

581

582

583

584

585

586

587

588

589

590

591

592

593594

595

596

597

598

599

600

601602

603604

605

606

607

608

609

610

611

612613

614

615

616

617

618619

620

621

622

623

4950

51

Page 18: Terminology

  -->

- <sdd-dd:Certified>

- <sdd-dd:Range>

  <sdd-dd:MinVersion>10.3</sdd-dd:MinVersion>

  <sdd-dd:MaxVersion>10.5</sdd-dd:MaxVersion>

  </sdd-dd:Range>

  </sdd-dd:Certified>

  </sdd-dd:VersionConstraint>

  </sdd-dd:ResourceConstraint>

  </sdd-dd:Requirement>

- <sdd-dd:Requirement id="EclipseLevel">

  <sdd-common:Description>IA Collaboration reqiures Eclipse 3.1.2 or greater</sdd-common:Description>

- <sdd-dd:ResourceConstraint id="eclipseMinimimVersionCheck" resourceRef="eclipse">

- <sdd-dd:VersionConstraint>

- <!--

<sdd-dd:Supported> Change Randy proposed 4/30

  -->

- <sdd-dd:Range>

  <sdd-dd:MinVersion>3.1.2</sdd-dd:MinVersion>

  </sdd-dd:Range>

- <!--

</sdd-dd:Supported>

  -->

- <sdd-dd:Certified>

- <sdd-dd:Value>

  <sdd-dd:Version>3.1.2</sdd-dd:Version>

  </sdd-dd:Value>

  </sdd-dd:Certified>

  </sdd-dd:VersionConstraint>

  </sdd-dd:ResourceConstraint>

  </sdd-dd:Requirement>

- <sdd-dd:Requirement id="JRELevel">

  <sdd-common:Description>IA Requires Java 1.5 or greater</sdd-common:Description>

- <sdd-dd:ResourceConstraint id="jreMinimimVersionCheck" resourceRef="JRE">

- <sdd-dd:VersionConstraint>

- <!--

<sdd-dd:Supported> Change Randy proposed 4/30

  -->

- <sdd-dd:Range>

  <sdd-dd:MinVersion>1.5</sdd-dd:MinVersion>

  </sdd-dd:Range>

- <!--

</sdd-dd:Supported>

  -->

- <sdd-dd:Certified>

- <sdd-dd:Range>

4 April 2007 Copyright © OASIS Open 2005, 2007. All Rights Reserved. Page 18 of 30

624625

626

627

628

629

630

631

632

633

634

635

636

637

638

639

640641

642

643

644

645

646647

648

649

650

651

652

653

654

655

656

657

658

659

660

661662

663

664

665

666

667668

669

5253

54

Page 19: Terminology

  <sdd-dd:MinVersion>1.5</sdd-dd:MinVersion>

  <sdd-dd:MaxVersion>1.5</sdd-dd:MaxVersion>

  </sdd-dd:Range>

  </sdd-dd:Certified>

  </sdd-dd:VersionConstraint>

  </sdd-dd:ResourceConstraint>

  </sdd-dd:Requirement>

  </sdd-dd:Requirements>

- <sdd-dd:ResultingResource resourceRef="InstallAnywhere">

  <sdd-common:Description>This is all of the IA files</sdd-common:Description>

  <sdd-common:ShortDescription>InstallAnywhere Enterprise</sdd-common:ShortDescription>

  <sdd-dd:Version>8.0</sdd-dd:Version>

  </sdd-dd:ResultingResource>

- <sdd-dd:ResultingResource resourceRef="InstallAnywhereCollaboration">

  <sdd-common:Description>This is the IA Collaboration Plugin</sdd-common:Description>

  <sdd-common:ShortDescription>InstallAnywhere Collaboration</sdd-common:ShortDescription>

  <sdd-dd:Version>1.0</sdd-dd:Version>

  </sdd-dd:ResultingResource>

- <sdd-dd:Artifacts>

- <sdd-dd:InstallArtifact type="MacAppBundle" fileRef="mac_bundle">

- <!--

I'm guessing that "MacAppBundle" is part of the profile/dictionary discussion?

  -->

- <sdd-dd:Parameters>

- <!--

I don't think we need to worry about ordering the parameters here. Here, I have a parameter based on the Install location. I'm not prompting the user for it, but I'm basing it on the InstallLocation. The installer should be able to handle this

  -->

- <!--

If I wanted to pass a parameter to the installer (i.e. telling it a logfile location), I think I'd just do it here like this

  -->

  <sdd-dd:Parameter name="LOG_FILE" value="$(InstallLocation)/out.log" />

  <sdd-dd:Parameter name="USER_INSTALL_DIR" value="$(InstallLocation)" />

  <sdd-dd:Parameter name="INSTALL_COLLAB" value="$(getInstallIACollaboration)" />

  <sdd-dd:Parameter name="ECLIPSE_DIR" value="$(EclipseLocation)" />

- <!--

If order was really that important, we could support an unnamed parameter, and one could just have on parameter...

  -->

- <!--

<Parameter name="" value="USER_INSTALL_DIR=$(InstallLocation) LOG_FILE=$(InstallLocation)/out.log INSTALL_COLLAB=FALSE"/>

  -->

- <!--

We'd have to worry about long paths. How do you escape quotes??

  -->

  </sdd-dd:Parameters>

4 April 2007 Copyright © OASIS Open 2005, 2007. All Rights Reserved. Page 19 of 30

670

671

672

673

674

675

676

677

678

679

680

681

682

683

684

685

686

687

688

689

690

691

692693

694

695696697

698699

700

701702

703

704

705

706

707

708709

710711

712713

714

715716

5556

57

Page 20: Terminology

  </sdd-dd:InstallArtifact>

  <sdd-dd:UninstallArtifact />

- <!--

For InstallAnywhere, and most installers, this is installed on the system. Should it be a resulting resource that's referenced here?

  -->

  </sdd-dd:Artifacts>

  </sdd-dd:InstallableUnit>

  </sdd-dd:DeploymentDescriptor>

3.3.2 InstallAnywhere - Windows

<?xml version="1.0" encoding="UTF-8" ?>

- <sdd-dd:DeploymentDescriptor xmlns:sdd-dd="urn:oasis:names:tc:SDD:1:0:deploymentDescriptor" xmlns:sdd-common="urn:oasis:names:tc:SDD:1:0:common" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ibmbuild="http://www.ibm.com/xmlns/prod/autonomic/solutioninstall/build" xsi:schemaLocation="urn:oasis:names:tc:SDD:1:0:deploymentDescriptor wd-sdd-deploymentDescriptor-1.0.xsd" schemaVersion="1.0" lastModified="2006-10-13T09:30:47.0Z" descriptorID="60101111111111111111111111111111">

- <sdd-dd:Topology>

- <sdd-dd:Resource id="os" type="OperatingSystem">

- <sdd-dd:HostedResource id="JRE" type="InstalledSoftware">

- <!--

Does the JRE really need to specify that it hosts IA?

  -->

  <sdd-dd:HostedResource id="InstallAnywhere" type="Application" />

  </sdd-dd:HostedResource>

- <sdd-dd:HostedResource id="eclipseJRE" type="InstalledSoftware">

- <!--

Should I really care about the eclipse JRE?

  -->

- <sdd-dd:HostedResource id="eclipse" type="PluggableApplication">

- <!--

What should we call this type?

  -->

  <sdd-dd:HostedResource id="InstallAnywhereCollaboration" type="Application" />

  </sdd-dd:HostedResource>

  </sdd-dd:HostedResource>

  </sdd-dd:Resource>

  </sdd-dd:Topology>

- <sdd-dd:InstallableUnit id="ID000026" targetResourceRef="os">

- <sdd-dd:Identity softwareID="2000-123">

  <sdd-dd:Name>InstallAnywhere Enterprise Windows Bundle"</sdd-dd:Name>

4 April 2007 Copyright © OASIS Open 2005, 2007. All Rights Reserved. Page 20 of 30

717

718

719

720721

722723

724

725

726

727

728

729

730

731732

733734735736737738

739

740

741

742

743

744745

746

747

748

749

750751

752

753

754755

756

757

758

759

760

761

762

5859

60

Page 21: Terminology

  <sdd-dd:Version>8.0</sdd-dd:Version>

  <sdd-dd:BuildInformation buildID="8.0.1000" />

  <sdd-dd:Description>Fooooo</sdd-dd:Description>

  <sdd-dd:ShortDescription>Foo</sdd-dd:ShortDescription>

- <sdd-dd:Manufacturer>

  <sdd-dd:Name>Macrovision</sdd-dd:Name>

- <sdd-dd:Location>

- <sdd-dd:Country>

  <sdd-dd:Name>U.S.A.</sdd-dd:Name>

  </sdd-dd:Country>

- <sdd-dd:Address>

  <sdd-dd:Name>900 National Parkway</sdd-dd:Name>

  </sdd-dd:Address>

  </sdd-dd:Location>

  </sdd-dd:Manufacturer>

  </sdd-dd:Identity>

- <sdd-dd:Variables>

- <sdd-dd:Parameter id="IAInstallLocation">

  <sdd-dd:DisplayName>Select the folder where would you like to install InstallAnywhere.</sdd-dd:DisplayName>

  </sdd-dd:Parameter>

- <sdd-dd:Parameter id="getInstallIACollaboration" defaultValue="FALSE">

  <sdd-dd:DisplayName>Would you like to Install IA Collaboration?</sdd-dd:DisplayName>

  </sdd-dd:Parameter>

- <sdd-dd:Parameter id="EclipseLocation">

- <!--

I'd like to be able to prompt for this value only if getInstallIACollaboration is true. Is it possible to tell the runtime to do that?

  -->

  <sdd-dd:DisplayName>Specify the location of your Eclipse environment</sdd-dd:DisplayName>

  </sdd-dd:Parameter>

  </sdd-dd:Variables>

- <sdd-dd:Requirements>

- <sdd-dd:Requirement id="OSLevel">

  <sdd-common:Description>The Windows bundle requires WinNT4</sdd-common:Description>

- <sdd-dd:ResourceConstraint id="osMinimumVersionCheck" resourceRef="os">

  <sdd-common:Description>Checking for NT4, verified on versions up to XP</sdd-common:Description>

- <sdd-dd:VersionConstraint>

- <!--

<sdd-dd:Supported> Change Randy proposed 4/30

  -->

- <sdd-dd:Range>

  <sdd-dd:MinVersion>4.0</sdd-dd:MinVersion>

  </sdd-dd:Range>

- <!--

</sdd-dd:Supported>

  -->

4 April 2007 Copyright © OASIS Open 2005, 2007. All Rights Reserved. Page 21 of 30

763

764

765

766

767

768

769

770

771

772

773

774

775

776

777

778

779

780

781782

783

784

785

786

787

788

789790

791792

793

794

795

796

797

798

799

800

801

802

803804

805

806

807

808

809

6162

63

Page 22: Terminology

- <sdd-dd:Certified>

- <sdd-dd:Range>

  <sdd-dd:MinVersion>4.0</sdd-dd:MinVersion>

  <sdd-dd:MaxVersion>5.0</sdd-dd:MaxVersion>

- <!--

I don't know the exact version, but bear with me

  -->

  </sdd-dd:Range>

  </sdd-dd:Certified>

  </sdd-dd:VersionConstraint>

  </sdd-dd:ResourceConstraint>

  </sdd-dd:Requirement>

- <sdd-dd:Requirement id="EclipseLevel">

  <sdd-common:Description>IA Collaboration reqiures Eclipse 3.1.2 or greater</sdd-common:Description>

- <sdd-dd:ResourceConstraint id="eclipseMinimimVersionCheck" resourceRef="eclipse">

- <sdd-dd:VersionConstraint>

- <!--

<sdd-dd:Supported> Change Randy proposed 4/30

  -->

- <sdd-dd:Range>

  <sdd-dd:MinVersion>3.1.2</sdd-dd:MinVersion>

  </sdd-dd:Range>

- <!--

</sdd-dd:Supported>

  -->

- <sdd-dd:Certified>

- <sdd-dd:Value>

  <sdd-dd:Version>3.1.2</sdd-dd:Version>

  </sdd-dd:Value>

  </sdd-dd:Certified>

  </sdd-dd:VersionConstraint>

  </sdd-dd:ResourceConstraint>

  </sdd-dd:Requirement>

  </sdd-dd:Requirements>

- <sdd-dd:ResultingResource resourceRef="JRE">

  <sdd-common:Description>This is the JRE required to run IA.</sdd-common:Description>

  <sdd-common:ShortDescription>Java(TM) Runtime Environment, Standard Edition</sdd-common:ShortDescription>

  <sdd-dd:Version>1.5.0</sdd-dd:Version>

  </sdd-dd:ResultingResource>

- <sdd-dd:ResultingResource resourceRef="InstallAnywhere">

  <sdd-common:Description>This is all of the IA files</sdd-common:Description>

  <sdd-common:ShortDescription>InstallAnywhere Enterprise</sdd-common:ShortDescription>

  <sdd-dd:Version>8.0</sdd-dd:Version>

  </sdd-dd:ResultingResource>

- <sdd-dd:ResultingResource resourceRef="InstallAnywhereCollaboration">

4 April 2007 Copyright © OASIS Open 2005, 2007. All Rights Reserved. Page 22 of 30

810

811

812

813

814

815

816817

818

819

820

821

822

823

824

825

826

827

828829

830

831

832

833

834835

836

837

838

839

840

841

842

843

844

845

846847

848

849

850

851

852

853

854

855

6465

66

Page 23: Terminology

  <sdd-common:Description>This is the IA Collaboration Plugin</sdd-common:Description>

  <sdd-common:ShortDescription>InstallAnywhere Collaboration</sdd-common:ShortDescription>

  <sdd-dd:Version>1.0</sdd-dd:Version>

  </sdd-dd:ResultingResource>

- <sdd-dd:Artifacts>

- <sdd-dd:InstallArtifact type="WindowsExecutable" fileRef="win_bundle">

- <!--

I'm guessing that "WindowsExecutable" is part of the profile/dictionary discussion?

  -->

- <sdd-dd:Parameters>

- <!--

I don't think we need to worry about ordering the parameters here. Here, I have a parameter based on the Install location. I'm not prompting the user for it, but I'm basing it on the InstallLocation. The installer should be able to handle this

  -->

- <!--

If I wanted to pass a parameter to the installer (i.e. telling it a logfile location), I think I'd just do it here like this

  -->

  <sdd-dd:Parameter name="LOG_FILE" value="$(InstallLocation)/out.log" />

  <sdd-dd:Parameter name="USER_INSTALL_DIR" value="$(InstallLocation)" />

  <sdd-dd:Parameter name="INSTALL_COLLAB" value="$(getInstallIACollaboration)" />

  <sdd-dd:Parameter name="ECLIPSE_DIR" value="$(EclipseLocation)" />

- <!--

If order was really that important, we could support an unnamed parameter, and one could just have on parameter...

  -->

- <!--

<Parameter name="" value="USER_INSTALL_DIR=$(InstallLocation) LOG_FILE=$(InstallLocation)/out.log INSTALL_COLLAB=TRUE ECLIPSE_DIR=c:\eclipse"/>

  -->

- <!--

We'd have to worry about long paths. How do you escape quotes??

  -->

  </sdd-dd:Parameters>

  </sdd-dd:InstallArtifact>

  <sdd-dd:UninstallArtifact />

- <!--

For InstallAnywhere, and most installers, this is installed on the system. Should it be a resulting resource that's referenced here?

  -->

  </sdd-dd:Artifacts>

  </sdd-dd:InstallableUnit>

  </sdd-dd:DeploymentDescriptor>

4 April 2007 Copyright © OASIS Open 2005, 2007. All Rights Reserved. Page 23 of 30

856

857

858

859

860

861

862

863

864865

866

867868869

870871

872

873874

875

876

877

878

879

880881

882883

884885

886

887888

889

890

891

892893

894895

896

897

898

899

6768

69

Page 24: Terminology

3.4 SAP

3.4.1

3.5 SAS

3.5.1 SAS MC Example

<Merri’s Note 5/9>

<sdd-dd:Alternative id="solaris.alt"> <sdd-common:Description>Requirements on Solaris 64</sdd- common:Description> <sdd-dd:ResourceConstraint id="Solaris64.requirement" resourceRef="os"> <sdd-dd:PropertyConstraint> <sdd-dd:PropertyName>OSType</sdd-dd:PropertyName> <sdd-dd:Value>Solaris</sdd-dd:Value> </sdd-dd:PropertyConstraint> <sdd-dd:PropertyConstraint> <sdd-dd:PropertyName>Processor.Family</sdd-dd:PropertyName> <sdd-dd:Value>SPARC Family</sdd-dd:Value> </sdd-dd:PropertyConstraint> <sdd-dd:VersionConstraint> <sdd-dd:Supported> <sdd-dd:Range> <sdd-dd:MinVersion>10.0</sdd-dd:MinVersion> </sdd-dd:Range> </sdd-dd:Supported> </sdd-dd:VersionConstraint> </sdd-dd:ResourceConstraint> </sdd-dd:Alternative>

</Merri’s Note 5/9>

4 April 2007 Copyright © OASIS Open 2005, 2007. All Rights Reserved. Page 24 of 30

900

901

902

903

904

905

906

907908909910911912913914915916917918919920921922923924925926927

928

929

930

7071

72

Page 25: Terminology

4 Profile Examples

4.1 Dell

4.2 IBM

4.2.1 JRE – Profile Example

NameValue Type Definition

Class Attribute Source (CIM2.15 or SDD1.0)

OperatingSystem:

AIX OSType CIM_OperatingSystem.OSType

5.1 | 5.2 | 5.3 Version CIM_OperatingSystem.Version

rpm InstallArtifact SDD_InstallArtifact

/usr HostedResourceType CIM_FileSystem

JRE HostedResourceType

SDD_InstalledSoftware

FileSystem: /usr

/usr Root CIM_FileSystem.Root

JFS FileSystemType CIM_FileSystem.FileSystemType

2688, 512-byte blocks AvailableSpace CIM_FileSystem.AvailableSpace

InstalledSoftware: JRE

component Type SDD_InstalledSoftware.Type

4 April 2007 Copyright © OASIS Open 2005, 2007. All Rights Reserved. Page 25 of 30

931

932

933

934

935

936

937

938

939

940

941

7374

75

Page 26: Terminology

4.3 MacroVision<Rich’s Note 5/9>

Here's a first stab at an InstallAnywhere "dictionary" (I know it could be better from an object-oriented standpoint)...Class: ArchitectureValues: Intel 32-bit, Intel 64-bit, AMD 64-bit, MIPS, HP PA-RISC, SPARC, PowerPC, DEC Alpha, Power, Motorola 68k Class: PlatformValues: Windows (95, 98, NT, Me, 2000, XP, 2003, Vista), Mac OS X, OS/2, Solaris, SunOS, HP-UX, Linux, AIX, Irix, DG-UX, Compaq's Digital UNIX, FreeBSD, Rhapsody, NetWare, z/OS, OS/390, OS/400 Class: LanguageValues: Several Class: PermissionsValues: Owner (Read, Write, Execute), Group (Read, Write, Execute) Class: JavaValues: Version, Publisher Class: FolderGeneric Values: InstallerTemp, Temp, Programs (any, 32-bit-only, 64-bit-only), Shortcut, SystemDriveRoot, InstallDriveRoot, InstallFolder, JavaHome, UserHome, Fonts, Desktop, Startup,Windows Values: Windows, System (any, 32-bit-only, 64-bit-only), QuickLaunch, StartMenu, ProgramsMenu, All Users (desktop, shortcut, programs, start)Mac Values: User Application, Clean-Up at Startup, PreferencesUnix Values: /usr/local/bin, /opt, /usr/bin I'm not sure we need to get as low-level as folder so I'll stop there. But here are other classes we have in IA that someone might want:File, Windows Registry, Font, Windows Service, Property file (XML, text), Shortcut, Archive (zip, jar, ear, war), HP-UX Depot, Linux RPM, IA Package, IA Merge Module, ISMP Package, Solaris Package, Environment Variable, I talked to the Engineering Manager on the Windows side. He brought up things like .NET, and COM. I think they're on par with Java (i.e. maybe we group them in a class called "RuntimeEnvironment"). He also mentioned that several customers have requirements on IE (i.e. maybe we create a class called Browser). I had brought up Plugins and Pluggable Apps. I'm guessing that you just haven't gotten around to WebServer. He also pointed me to these MSI properties...http://msdn2.microsoft.com/en-us/library/aa370554.aspxhttp://msdn2.microsoft.com/en-us/library/aa370554.aspxFor our purposes, besides what I've already mentioned, I found these interesting:Computer Name, Terminal Server, ScreenX/Y, Virtual/Physical memory.

</Rich’s Note 5/9>

4 April 2007 Copyright © OASIS Open 2005, 2007. All Rights Reserved. Page 26 of 30

942

943

944945946947948

949950951952953

954955956

957958959

960961962

963964965966967968969970971972973974975976977

978979980981982983984985986987988989

990

991

992

7677

78

Page 27: Terminology

4.3.1 InstallAnywhere - MacOS

<first pass at published example>

NameValue Type Definition

Class Attribute Source (CIM2.15 or SDD1.0)

OperatingSystem:

MacOS OSType CIM_OperatingSystem.OSType

10.3 | 10.4 | 10.5 Version CIM_OperatingSystem.Version

.pkg | .mpkg InstallArtifact SDD_InstallArtifact

?? HostedResourceType CIM_FileSystem

JRE HostedResourceType

SDD_InstalledSoftware

InstallAnywhere HostedResourceType

CIM_ApplicationSystem.Application

FileSystem: ??

Root CIM_FileSystem.Root

FileSystemType CIM_FileSystem.FileSystemType

AvailableSpace CIM_FileSystem.AvailableSpace

InstalledSoftware: JRE

component Type SDD.InstalledSoftware.Type

Application InstallAnywhere

InstallAnywhere Name

4 April 2007 Copyright © OASIS Open 2005, 2007. All Rights Reserved. Page 27 of 30

993

994

995

996

997

998

999

1000

7980

81

Page 28: Terminology

4.3.2 InstallAnywhere – Windows

NameValue Type Definition

Class Attribute Source (CIM2.15 or SDD1.0)

OperatingSystem:

OSType CIM_OperatingSystem.OSType

Version CIM_OperatingSystem.Version

InstallArtifact SDD_InstallArtifact

?? HostedResourceType CIM_FileSystem

JRE HostedResourceType

SDD_InstalledSoftware

InstallAnywhere HostedResourceType

CIM_ApplicationSystem.Application

FileSystem: ??

Root CIM_FileSystem.Root

FileSystemType CIM_FileSystem.FileSystemType

AvailableSpace CIM_FileSystem.AvailableSpace

InstalledSoftware: JRE

component Type SDD.InstalledSoftware.Type

Application InstallAnywhere

InstallAnywhere Name

4 April 2007 Copyright © OASIS Open 2005, 2007. All Rights Reserved. Page 28 of 30

1001

1002

1003

1004

1005

1006

1007

8283

84

Page 29: Terminology

4.4 SAP

4.5 SAS

4.5.1 SAS MC

NameValue Type Definition

Class Attribute Source (CIM2.15 or SDD1.0)

Processor:

SPARC Family CIM_Processor.Family

OperatingSystem:

Solaris OSType CIM_OperatingSystem.OSType

10.0 | * Version CIM_OperatingSystem.Version

??? InstallArtifact SDD_InstallArtifact

??? HostedResourceType CIM_FileSystem

MC HostedResourceType

SDD_InstalledSoftware

FileSystem: ???

Root CIM_FileSystem.Root

FileSystemType CIM_FileSystem.FileSystemType

AvailableSpace CIM_FileSystem.AvailableSpace

InstalledSoftware: MC

??? Type SDD_InstalledSoftware.Type

4 April 2007 Copyright © OASIS Open 2005, 2007. All Rights Reserved. Page 29 of 30

1008

1009

1010

1011

1012

1013

1014

1015

1016

1017

8586

87

Page 30: Terminology

4 April 2007 Copyright © OASIS Open 2005, 2007. All Rights Reserved. Page 30 of 30

1018

1019

8889

90