Q: What is this SDK about?

A: CSA Content SDK allows you to package your CSA/OO content in a standard and portable manner allowing you to move Content around from one environment to another.

It is also the preferred format and packaging for Content that will be pushed to ITOM Marketplace for customers, partners, and internal teams.


Q: What is the SDK compatibility matrix?

A: Please refer Compatibility Matrix section above.


Q: What Operating Systems (OS) are supported by SDK?

A: SDK supports Windows, Linux - openSUSE 42.1 and openSUSE 42.2, and RHEL/CentOS 7.x.


Q: Are we looking at a new installer to deploy the CSA capsules?

A: There are two separate installers bundled in the SDK. One is supported for CSA version 4.60 and lower versions and the other one is the same as the one available in the current CSA software distribution that supports CSA 4.70 and above.


Q: What content types do you support?

A: Content of different types can be embedded into the capsule including OO Content Pack, CloudSlang based Contents, Providers, Components, Service Designs (Sequence or Topology based), and Service Offering.


Q: Can I bundle a Resource Offering in a capsule?

A: If your artifacts contain Service Design also, however the service designs will contain the resource offerings in it. So, you need not to bundle the Resource offering separately.


Q: Where do I go for help during the Beta?

A: Visit the ITOM Marketplace Web site and the CSA Content SDK Forum


Organizing Usecase Directory

Q: Can I keep the auxiliary files randomly inside the use-case directory?

A: No, all the auxiliary files need to be kept in a sub-directory named "tools" inside the use-case directory.


Q: What are the PATH variables supported for "destinationPath" of "auxiliaryData" section?

A: CSA_HOME and CSA_JBOSS_HOME are supported here. The variables must not be pre/post-fixed by any special characters like % or $


Q: How can I package my dependent sequential Component Palette along with the Service Design?

A: Keep the dependent component palette archive along with the service design in the same directory. If you have multiple Service Designs and each have distinct component palette dependency, then create multiple service designs directories and store the combination of archives in the respective directories. If all the service designs depend on the same set of component palettes, then a single service design directory is sufficient to store the files.

Below is an example:

      <displayName>VMWare vCenter</displayName>
      <description>A short description about the provider type</description>
         <property name="proxyport" type="Integer" value="80"/>
         <property name="proxypassword" type="String" value="" confidential="true" encrypted="false"/>
         <property name="proxyuser" type="String" value=""/>
	  <property name="proxyhost" type="String" value=""/>
	  <property name="listItems" type="List" value="t1, t2, t3, t4"/>
         <property name="isDefault" type="Boolean" value="true"/>

Support Matrix

Q: What version of CSA/Codar and OO should be mentioned in the support matrix section?

A: It is recommended to provide the versions of HPE CSA/Codar and HPE OO Studio used to create the respective contents


Q: Can my capsule, with support matrix of CSA 4.2 be installed in CSA 4.5 or higher environment?

A: Yes.

Capsule Building

Q: While creating capsule, what should be done if it fails with an error message "Error while validating the UsecaseInfo document"

A: The usecaseInfo.xml file is not as per its schema definition. Please confirm that the usecase definition file (usecaseInfo.xml) is according to the usecaseInfo.xsd specifications


Q: How can I assign a version number to the capsule?

A: Use "-bv" switch to pass capsule version dynamically to the CapsulePackager. e.g. "java -jar CapsulePackeger.jar -i capsule.xml -bv 15.09". Default value if not provided is YY.MM


Q: How can I assign a build number to the capsule?

A: Use "-bn" switch to pass capsule build number dynamically to the CapsulePackager. e.g. "java -jar CapsulePackeger.jar -i capsule.xml -bn 123". Default value if not provided is 1


Q: How can I assign a source control revision number to the capsule?

A: Use "-br" switch to pass source control revision number dynamically to the CapsulePackager. e.g. "java -jar CapsulePackeger.jar -i capsule.xml -br 4567". Default value if not provided is 0