HP VAN SDN Controller Software Products 1.3 Application and zip file signing, 1.4 Use of encryption technologies, 1.5 Icon requirements

•Can contain numbers, letters, and the dot (.) character.

•Follows the OSGi standard for version numbering: major[.minor[.micro]]

Recommended form

_vmajor[.minor[.micro]]

For example: _v1.0.0

1.3 Application and zip file signing

For applications that are installed on the controller, the application zip file and the application JAR, PAR, or WAR file must be signed as described in the HP VAN SDN Controller Administrator Guide. By default, the controller ships with signature validation enabled, but the user can disable this feature.

1.4 Use of encryption technologies

You are responsible that your application complies with all applicable laws and regulations.

Many governments, including the U.S. government, restrict the export of cryptography. The level of government control on encryption can depend upon such factors as the purpose for which the encryption will be used, the encryption algorithm, the key length and the method of key management, and the country to which the product is exported.

Products whose use of encryption technologies is limited to encrypting passwords and PINS or authenticating messages are generally exportable without prior government authorization. Products that can encrypt the contents of messages, files, or databases are subject to more stringent controls and prior government authorization may be required to export/reexport/import these products depending upon the strength of the encryption program.

When considering whether or not your application includes encryption technologies, consider any code libraries, utilities, or components that your application links to or includes.

In the U.S. the export of cryptography and encryption technologies is controlled by the United States Bureau of Industry and Security Export Administration Regulations (EAR). If your application is subject to export restrictions, you must enter the ERN (Encryption Registration Number) or CCATS (Commodity Classification Automated Tracking System) number for this application when you submit it.

1.5 Icon requirements

Each catalog item requires two icons:

•A small icon that is used in the category listing for the catalog item that is displayed in the App Store.

•A large icon that is used in the application page for the item in the App Store and in the management portal you use to submit applications.

You can use the same file for both icons, but the file must conform to the dimensions permitted for the large icon.

For best results, use a square shape for your icon.

Icons must meet the following requirements:

Attribute	Requirement
File format	PNG or JPG
Maximum file size	2 GB

1.3 Application and zip file signing 5