Hitachi Storage Plug-in for VMware vCenter User's Guideitdoc.hitachi.co.jp/manuals/st_adapter/dkc/MK-92ADPTR047-17.pdf · This guide explains how to install, configure and use Hitachi

Hitachi Storage Plug-in for VMware vCenter

User's Guide

v03.10.0

MK-92ADPTR047-17January 2019

© 2014, 2019 Hitachi, Ltd. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or by any means, electronic or mechanical, including copying andrecording, or stored in a database or retrieval system for commercial purposes without the express written permission of Hitachi, Ltd., orHitachi Vantara Corporation (collectively “Hitachi”). Licensee may make copies of the Materials provided that any such copy is: (i) created as anessential step in utilization of the Software as licensed and is used in no other manner; or (ii) used for archival purposes. Licensee may notmake any other copies of the Materials. “Materials” mean text, data, photographs, graphics, audio, video and documents.

Hitachi reserves the right to make changes to this Material at any time without notice and assumes no responsibility for its use. The Materialscontain the most current information available at the time of publication.

Some of the features described in the Materials might not be currently available. Refer to the most recent product announcement forinformation about feature and product availability, or contact Hitachi Vantara Corporation at https://support.hitachivantara.com/en_us/contact-us.html.

Notice: Hitachi products and services can be ordered only under the terms and conditions of the applicable Hitachi agreements. The use ofHitachi products is governed by the terms of your agreements with Hitachi Vantara Corporation.

By using this software, you agree that you are responsible for:

1. Acquiring the relevant consents as may be required under local privacy laws or otherwise from authorized employees and otherindividuals; and

2. Verifying that your data continues to be held, retrieved, deleted, or otherwise processed in accordance with relevant laws.

Notice on Export Controls. The technical data and technology inherent in this Document may be subject to U.S. export control laws, includingthe U.S. Export Administration Act and its associated regulations, and may be subject to export or import regulations in other countries. Readeragrees to comply strictly with all such regulations and acknowledges that Reader has the responsibility to obtain licenses to export, re-export, orimport the Document and any Compliant Products.

Hitachi is a registered trademark of Hitachi, Ltd., in the United States and other countries.

AIX, AS/400e, DB2, Domino, DS6000, DS8000, Enterprise Storage Server, eServer, FICON, FlashCopy, IBM, Lotus, MVS, OS/390, PowerPC, RS/6000,S/390, System z9, System z10, Tivoli, z/OS, z9, z10, z13, z/VM, and z/VSE are registered trademarks or trademarks of International BusinessMachines Corporation.

Active Directory, ActiveX, Bing, Excel, Hyper-V, Internet Explorer, the Internet Explorer logo, Microsoft, the Microsoft Corporate Logo, MS-DOS,Outlook, PowerPoint, SharePoint, Silverlight, SmartScreen, SQL Server, Visual Basic, Visual C++, Visual Studio, Windows, the Windows logo,Windows Azure, Windows PowerShell, Windows Server, the Windows start button, and Windows Vista are registered trademarks or trademarksof Microsoft Corporation. Microsoft product screen shots are reprinted with permission from Microsoft Corporation.

All other trademarks, service marks, and company names in this document or website are properties of their respective owners.

Hitachi Storage Plug-in for VMware vCenter User's Guide 2

https://support.hitachivantara.com/en_us/contact-us.html


Contents

Preface..................................................................................................... 7Intended audience............................................................................................... 7Release notes......................................................................................................7Referenced documents........................................................................................7Document conventions........................................................................................ 8Conventions for storage capacity values............................................................. 9Accessing product documentation.....................................................................10Getting help........................................................................................................10Comments..........................................................................................................10

Chapter 1: Overview of Hitachi Storage Plug-in for VMwarevCenter...................................................................................................11

Overview of Hitachi Storage Plug-in for VMware vCenter's functions............... 11Key terms and concepts.....................................................................................11

Chapter 2: System Requirements........................................................13Required system configuration for Hitachi Storage Plug-in for VMwarevCenter.............................................................................................................. 13Hardware requirements..................................................................................... 14Software requirements.......................................................................................15Supported operating systems............................................................................ 17Storage system requirements............................................................................17Restrictions and considerations ........................................................................18

Chapter 3: Setting up the Hitachi Storage Plug-in for VMwarevCenter...................................................................................................21

Installing the Hitachi Storage Plug-in.................................................................21Installation prerequisites...............................................................................21Installing the Windows version..................................................................... 21Installing the vCenter Server Appliance version ..........................................22

Uninstalling the Hitachi Storage Plug-in............................................................ 22Uninstalling the Windows version ................................................................23Uninstalling the Hitachi Storage Plug-in from the Control Panel.................. 23Uninstalling the Hitachi Storage Plug-in vCenter Server Applianceversion..........................................................................................................24

Repairing the Hitachi Storage Plug-in................................................................24

Contents


Repairing the Windows installation.............................................................. 24Repairing the vCenter Server Appliance version installation....................... 25

Starting and stopping services in Windows....................................................... 26Starting and stopping services in the vCenter Server Appliance.......................26Changing the configuration files........................................................................ 27

Log file size...................................................................................................27Number of log generations .......................................................................... 28LUN ID..........................................................................................................28

Chapter 4: Using the Hitachi Storage Plug-in for VMware vCenter..29Accessing the Hitachi Storage Plug-in...............................................................29Adding a storage system................................................................................... 29

Adding a VSP or HUS VM storage system.................................................. 29Adding a VSP F400, F600, F800, F1500 or VSP G200, G400, G600,G800, G1000, G1500 storage system (when Hitachi ConfigurationManager is used)..........................................................................................30Adding a VSP F400, F600, F800, F1500 or VSP G200, G400, G600,G800, G1000, G1500 storage system (when HDvM is used)...................... 31Adding a VSP F350, F370, F700, F900 or VSP G350, G370, G700,G900 storage system................................................................................... 32Adding a VSP Gx00 NAS module, VSP Fx00 NAS module, or HNAS asa file storage system.....................................................................................32

Removing a storage system.............................................................................. 33Refreshing storage system information ............................................................ 33

Refreshing all storage systems.................................................................... 34Refreshing selected storage systems.......................................................... 34

Provisioning datastores..................................................................................... 35Overview of Provision Datastore ................................................................. 35Creating a datastore.....................................................................................36

Creating VMFS datastores .....................................................................37Creating LUs for Raw Device Mapping (RDM)....................................... 39Creating NFS datastores.........................................................................40

Cancelling Provision Datastore.................................................................... 41Deleting datastores ...........................................................................................42

Deleting a VMFS datastore or LU................................................................ 42Deleting an NFS datastore........................................................................... 43

Chapter 5: Information Display............................................................44Datastores information.......................................................................................44Host information.................................................................................................44Virtual Machines information..............................................................................44

Contents


Chapter 6: Troubleshooting................................................................. 46Troubleshooting the Hitachi Storage Plug-in installation................................... 46Troubleshooting Hitachi Storage Plug-in operational errors.............................. 46Troubleshooting storage system errors............................................................. 46Troubleshooting Hitachi Configuration Manager and HDvM server errors........ 47Troubleshooting Provision Datastore function errors.........................................48

Retry of Provision Datastore.........................................................................48Rollback of Provision Datastore................................................................... 49Provision Datastore task stops before completing....................................... 49Stops while retrying NFS Export Creation....................................................50Stops while creating an NFS datastore........................................................ 50

Troubleshooting datastore deletion errors ........................................................ 50Retry of Delete Datastore.............................................................................50Delete Datastore stops before it has completed.......................................... 50

Chapter 7: Log files...............................................................................52HiAppServerModule.log.....................................................................................52Information Collected During Problem Occurrence .......................................... 52

Collect Windows Event Log information.......................................................52Collect Windows system information............................................................53Confirm vSphere Web Client version........................................................... 53Collect vSphere Web Client/vCenter Server logs ........................................53Collect log files from the Hitachi Storage Plug-in......................................... 53

Collect vCenter and ESXi information............................................................... 54Collect Windows Event Log information.......................................................54Collect Windows system information............................................................54Confirm the vCenter Server version............................................................. 54Collect ESXi information...............................................................................54Collect storage system information.............................................................. 54

How to collect Hitachi Configuration Manager and HDvM information.............. 55Collect Windows Event Log information.......................................................55Collect Windows system information............................................................55Collect Hitachi Configuration Manager maintenance information ............... 55Collect HDvM maintenance information....................................................... 55

Collect vCenter Server Appliance information................................................... 56

Chapter 8: Open source and third-party software licenses..............57Software and license information.......................................................................57Apache License, Version 2.0............................................................................. 58javax.activation:activation (1.1)..........................................................................58javax.annotation:javax.annotation-api (1.2) and org.glassfish.hk2:osgi-resource-locator (1.0.1)......................................................................................64

Contents


javax.ws.rs:javax.ws.rs-api (2.0.1).....................................................................75org.glassfish.hk2:hk2-locator (2.5.0-b30).......................................................... 87org.glassfish.hk2:hk2-api (2.5.0-b30)................................................................ 87org.glassfish.hk2:hk2-utils (2.5.0-b30)...............................................................87org.glassfish.hk2.external:aopalliance-repackaged (2.5.0-b30)........................ 88org.glassfish.hk2.external:javax.inject (2.5.0-b30).............................................88org.glassfish.jersey.bundles.repackaged:jersey-guava..................................... 88org.glassfish.jersey.core:jersey-client................................................................ 88org.glassfish.jersey.core:jersey-common...........................................................88org.glassfish.jersey.media:jersey-media-jaxb.................................................... 88VMware® vSphere Software Development Kit License Agreement.................. 89

Contents


Preface

This guide explains how to install, configure and use Hitachi Storage Plug-in for VMwarevCenter with supported storage systems.

Intended audience

This document is intended for operators (also called VM manager) of VMwaremanagement console (vSphere Web Client) to verify the configurations of the storagesystem and perform setting operations (creation of a datastore) using the storagesystem.

Readers of this document should be familiar with the following:■ Using Microsoft Windows Server family operating systems.■ Using the VMware vSphere Web Client.

Release notes

Read the release notes before installing and using this product. They may containrequirements or restrictions that are not fully described in this document or updates orcorrections to this document. Release notes are available on Hitachi Vantara SupportConnect: https://knowledge.hitachivantara.com/Documents.

Referenced documents

The documents below are either referenced by this document, or supply moreinformation related to this product's features.

Hitachi documents:■ Hitachi Command Suite Configuration Manager REST API Reference Guide,

MK-92HC229

■ Hitachi Command Suite User Guide, MK-90HC172

■ Metro REST API Specification

Preface


https://knowledge.hitachivantara.com/Documents

VMware documents:■ VMware vSphere ESXi and vCenter Server 6.0/6.5/6.7

Hitachi Vantara Support Connect, https://knowledge.hitachivantara.com/Documents

Document conventions

This document uses the following typographic conventions:

Convention Description

Bold ■ Indicates text in a window, including window titles, menus,menu options, buttons, fields, and labels. Example:

Click OK.■ Indicates emphasized words in list items.

Italic ■ Indicates a document title or emphasized words in text.■ Indicates a variable, which is a placeholder for actual text

provided by the user or for output by the system. Example:

pairdisplay -g group

(For exceptions to this convention for variables, see the entry forangle brackets.)

Monospace Indicates text that is displayed on screen or entered by the user.Example: pairdisplay -g oradb

< > anglebrackets

Indicates variables in the following scenarios:■ Variables are not clearly separated from the surrounding text or

from other variables. Example:

Status-<report-name><file-version>.csv

■ Variables in headings.

[ ] squarebrackets

Indicates optional values. Example: [ a | b ] indicates that you canchoose a, b, or nothing.

{ } braces Indicates required or expected values. Example: { a | b } indicatesthat you must choose either a or b.

| vertical bar Indicates that you have a choice between two or more options orarguments. Examples:

[ a | b ] indicates that you can choose a, b, or nothing.

{ a | b } indicates that you must choose either a or b.

Document conventions

Preface



This document uses the following icons to draw attention to information:

Icon Label Description

Note Calls attention to important or additional information.

Tip Provides helpful information, guidelines, or suggestions forperforming tasks more effectively.

Caution Warns the user of adverse conditions and/or consequences(for example, disruptive operations, data loss, or a systemcrash).

WARNING Warns the user of a hazardous situation which, if notavoided, could result in death or serious injury.

Conventions for storage capacity values

Physical storage capacity values (for example, disk drive capacity) are calculated basedon the following values:

Physical capacity unit Value

1 kilobyte (KB) 1,000 (103) bytes

1 megabyte (MB) 1,000 KB or 1,0002 bytes

1 gigabyte (GB) 1,000 MB or 1,0003 bytes

1 terabyte (TB) 1,000 GB or 1,0004 bytes

1 petabyte (PB) 1,000 TB or 1,0005 bytes

1 exabyte (EB) 1,000 PB or 1,0006 bytes

Logical capacity values (for example, logical device capacity, cache memory capacity) arecalculated based on the following values:

Logical capacity unit Value

1 block 512 bytes

1 cylinder Mainframe: 870 KB

Conventions for storage capacity values

Preface


Logical capacity unit Value

Open-systems:■ OPEN-V: 960 KB■ Others: 720 KB

1 KB 1,024 (210) bytes

1 MB 1,024 KB or 1,0242 bytes

1 GB 1,024 MB or 1,0243 bytes

1 TB 1,024 GB or 1,0244 bytes

1 PB 1,024 TB or 1,0245 bytes

1 EB 1,024 PB or 1,0246 bytes

Accessing product documentation

Product user documentation is available on Hitachi Vantara Support Connect: https://knowledge.hitachivantara.com/Documents. Check this site for the most currentdocumentation, including important updates that may have been made after the releaseof the product.

Getting help

Hitachi Vantara Support Connect is the destination for technical support of products andsolutions sold by Hitachi Vantara. To contact technical support, log on to Hitachi VantaraSupport Connect for contact information: https://support.hitachivantara.com/en_us/contact-us.html.

Hitachi Vantara Community is a global online community for Hitachi Vantara customers,partners, independent software vendors, employees, and prospects. It is the destinationto get answers, discover insights, and make connections. Join the conversation today!Go to community.hitachivantara.com, register, and complete your profile.

Comments

Please send us your comments on this document [email protected]. Include the document title and number, includingthe revision level (for example, -07), and refer to specific sections and paragraphswhenever possible. All comments become the property of Hitachi Vantara Corporation.

Thank you!

Accessing product documentation

Preface




https://knowledge.hitachivantara.com/



https://community.hitachivantara.com/welcome

https://community.hitachivantara.com/welcome

mailto:[email protected]

Chapter 1: Overview of Hitachi Storage Plug-infor VMware vCenter

Hitachi Storage Plug-in for VMware vCenter integrates Hitachi storage systeminformation and provisioning operations in to VMware vSphere Web Client.

This integration allows VMware product administrators to perform storage provisioningoperations from within the VMware user interface, which offers greater conveniencethan having to switch between VMware and Hitachi management software to performcommon operations involving both.

Overview of Hitachi Storage Plug-in for VMware vCenter'sfunctions

Hitachi Storage Plug-in for VMware vCenter provides functions to view storageinformation, provision datastores, and delete datastores.

ViewThe View function displays the storage system information registered in thestorage plug-in, the datastore on the ESXi host using the storage system, andvirtual machine information.

Provision DatastoreThe Provision Datastore function creates an LU used as a datastore for a VirtualMachine File System (VMFS), a Network File System (NFS) , and also for Raw DeviceMapping objects (RDMs) by a storage system registered in the Hitachi StoragePlug-in.

Delete Datastore/LUThe Delete Datastore function is a one-step operation that removes datastores orLUs from storage systems registered with the storage plug-in. It does not removedatastores or LUs that were created without using the storage plug-in.

Key terms and concepts

The term vSphere is a collective name for the VMware-based virtual environment, whichincludes the VMware vSphere software, VMware vCenter Server software, VMware ESXiclusters and hosts managed by the vCenter Server, and the virtual machines (VMs) andvApps hosted on those ESXi clusters.

Chapter 1: Overview of Hitachi Storage Plug-in for VMware vCenter


For details about these concepts, see the Hitachi Command Suite User Guide, the HitachiCommand Suite Configuration Manager REST API Reference Guide, and the VMwaredocumentation provided by VMware Inc.

Term Description

Datastore Virtual area used to store a virtual machine image on ESXi. The actualarea is created on a local disk or external storage system.

HDP Hitachi Dynamic Provisioning. An optional function of the storagesystem to reduce complicated design. Large volume of virtualcapacity eliminates reliance on device capacity.

HDvM Hitachi Device Manager. Software included in Hitachi CommandSuite, consolidating multiple Hitachi manufactured softwaremanagements.

HitachiCommandSuite

Storage management software suite, supporting storage resourceoperation in Enterprise environments.

HitachiConfigurationManager

Software included in Hitachi Command Suite. Hitachi ConfigurationManager REST API provides the Web API, which follows the principlesof Representational State Transfer (REST), for getting informationabout Hitachi storage systems or changing the configuration ofHitachi storage systems.

HNAS Hitachi NAS Platform is a network attached storage system whichallows storage capacity from back-end arrays to be accessed overTCP/IP, using SMB, NFS, iSCSI and FTP.

Host Group Host Groups represent storage array LU masking configurationswhich allow a set of HBA ports to access a set of LUs.

Metro Metro is a REST API which allows REST client applications to configureand collect information from Hitachi storage systems.

RDM Raw Device Mappings are VMware configuration objects which allowVMs to directly access LUs.

Key terms and concepts

Chapter 1: Overview of Hitachi Storage Plug-in for VMware vCenter


Chapter 2: System Requirements

Required system configuration for Hitachi Storage Plug-in forVMware vCenter

A typical system configuration for Hitachi Storage Plug-in contains the main componentsshown in the figure below.

■ VMware software components require access to storage systems using TCP/IP.■ ESXi must have Fibre Channel or TCP/IP connectivity to storage systems, for details,

see Storage system requirements (on page 17) .■ IPv4 TCP/IP connectivity (IPv6 is not supported).



■ Depending on the storage system you are using, you will need one of the followingsoftware products for managing storage systems. For details about storage systemsand management software, see Software requirements (on page 15) .● Hitachi Configuration Manager

When you register a storage system in Hitachi Configuration Manager, enable thesettings for receiving configuration change notifications from the storage system.

● HDvM● Metro

■ We recommend that users who will use the Hitachi Storage Plug-in be assigned theadministrator role. To create a role that has the minimum privileges necessary to usethe storage plug-in, select the following check boxes.● Extension > Register extension● Extension > Update extension● Global > Log event● Host > Configuration > Storage partition configuration● Tasks > Create task● Tasks > Update task

Note:

If you want to assign a role you created to a user or group, you must selectPropagate to children.

Hardware requirements

Item Description Notes

CPU 2.00 GHz or faster processor with fourcores or more.

None

Memory 8 GB or more RAM None

Hardware requirements



Item Description Notes

HDD freespace

Varies according to the requirements ofthe configuration file (the log file size andthe number of log generations can bemodified).■ 0.82 GB or more if the log file size is set

to the default value (10 MB) and thenumber of log generations is also set tothe default value (19 generations) wheninstalled.

■ 75 GB or more if the log file size is set tothe maximum (100 MB) and thenumber of log generations of thebackup file is also set to the maximum(255 generations).

Formula for calculating the requireddisk size:

Required disk size [GB]

= ((specified log file size [MB]) x (number oflog generations + 1) x 3(HiAppServerModule.log) + 110 [MB]) /1,024

110 MB or more requiredfor installation

LAN Gigabit Ethernet or faster isrecommended.

None

Software requirements

Caution: If the vSphere Web Client is not installed before the storage plug-inis installed, the storage plug-in will fail to install.

Software Version

VMware vCenter Server One of the following is required:

Windows version■ VMware vCenter Server 6.0 (Update 3)■ VMware vCenter Server 6.5 (Update 2)■ VMware vCenter Server 6.7 (Update 1)




Software Version

vCenter Server Appliance version■ VMware vCenter Server Appliance 6.0 (Update 3)■ VMware vCenter Server Appliance 6.5 (Update 2)■ VMware vCenter Server Appliance 6.7 (Update 1)

Tip:

The vSphere Web Client is included inVMware vCenter Server.

VMware ESXi One of the following is required:■ VMware ESXi 6.0 (Update 3)■ VMware ESXi 6.5 (Update 2)■ VMware ESXi 6.7 (Update 1)

Hitachi Configuration Manager(Hitachi Command SuiteComponent)

Storage systems and compatible versions:■ VSP F350, F370, F700, F900: 8.6.0 or later■ VSP G350, G370, G700, G900: 8.6.0 or later■ VSP G200, G400, G600, G800: 8.6.2 or later■ VSP F400, F600, F800: 8.6.2 or later■ VSP G1000: 8.6.2 or later■ VSP G1500: 8.6.2 or later■ VSP F1500: 8.6.2 or later

Hitachi Device Manager (HitachiCommand Suite Component)

Storage systems and compatible versions:■ VSP: 7.0 or later■ HUS VM: 7.3.1 or later■ VSP G1000: 8.0.0 or later■ VSP G1500: 8.5.0 or later■ VSP F1500: 8.5.0 or later■ VSP G200, G400, G600, G800: 8.1.3 or later■ VSP F400, F600, F800: 8.4.0 or later

Metro Server Version 3.0.0 or later required for managing NFSdatastore with the HNAS and Hitachi Storage Plug-in.

Microsoft Internet Explorer

Mozilla Firefox

Installed on the VMware Management client.




Software Version

Google Chrome

Supported operating systems

Operating system for vCenter Server Windows version:■ Microsoft Windows Server 2008 R2 Standard/Enterprise/Datacenter Edition SP1■ Microsoft Windows Server 2012 Standard/Datacenter Edition■ Microsoft Windows Server 2012 R2 Standard/Datacenter Edition■ Microsoft Windows Server 2016 Standard/Datacenter Edition

The following VMware Management Client operating systems are supported:■ Microsoft Windows 7 Home Premium/Professional/Ultimate/Enterprise SPI■ Microsoft Windows 8 Core/Pro/Enterprise■ Microsoft Windows 8.1 Core/Pro/Enterprise■ Microsoft Windows 10■ Microsoft Windows Server 2008 R2 Standard/Enterprise/Datacenter Edition SP1■ Microsoft Windows Server 2012 Standard/Datacenter Edition■ Microsoft Windows Server 2012 R2 Standard/Datacenter Edition■ Microsoft Windows Server 2016 Standard/Datacenter Edition■ Mac OS X

Storage system requirements

Storage system Firmware version Interface / Host port

VSP 70-03-01 or later Fibre Channel

HUS VM 73-03-01 or later Fibre Channel

VSP G1000 When HDvM is used: 80-01 orlater

When Hitachi ConfigurationManager is used: 80-06-61 orlater

Fibre Channel, iSCSI

VSP G1500 When HDvM is used: 80-05 orlater


Supported operating systems



Storage system Firmware version Interface / Host port

VSP F1500 When Hitachi ConfigurationManager is used: 80-06-61 orlater

VSP G200, G400, G600, G800 When HDvM is used: 83-01 orlater


Fibre Channel, iSCSI,NAS

VSP F400, F600, F800 When HDvM is used: 83-02 orlater


Fibre Channel, iSCSI,NAS

VSP F350, F370, F700, F900

VSP G350, G370, G700, G900

When Hitachi ConfigurationManager 8.6.0 or 8.6.1 isused: 88-01 or later

When Hitachi ConfigurationManager 8.6.2 or later is used:88-03-01 or later


HNAS 4000 12.6 or later NAS

Restrictions and considerations

The following restrictions and considerations apply when using the Hitachi Storage Plug-in for VMware vCenter.

User privilegesTo install and use the Windows version of the Hitachi Storage Plug-in, log in toWindows as a user with administrator privileges.

Capacity Saving setting in Provision DatastoreFor the following storage systems, if a dedupe and compression program productis installed, you can set up Capacity Saving: VSP F350, F370, F700, F900 storagesystems, and VSP G350, G370, G700, G900 storage systems. To check whether adedupe and compression program product is installed, contact your storagesystem administrator.

Communication port for the Configuration Manager serverThe storage plug-in uses TCP port number 23450 (http) or 23451 (https) tocommunicate with the Configuration Manager server by default. Confirm that TCPport number 23450 (http) or 23451 (https) is not being used by other software. If




the port number is used by other software, change the port number in theConfiguration Manager setting using Add Storage System. After installing thestorage plug-in, the port number that you want to use must be enabled tocommunicate with the Configuration Manager server.

Communication port for the HDvM serverThe storage plug-in uses TCP port number 2001 to communicate with the HDvMserver by default. Confirm that TCP port number 2001 is not being used by othersoftware.

If the port number is used by other software, change the port number in theHDvM setting using Add Storage System. After installing the storage plug-in, theport number that you want to use must be enabled to communicate with theHDvM server.

Confirmation at installationPrior to installing the Hitachi Storage Plug-in for VMware vCenter software,confirm that all monitoring, and virus monitoring services (such as daemonprocesses) are not activated. If such monitoring services are active, installationmay fail.

Installation folderThe installation folder of the storage plug-in differs according to the version of thevSphere Web Client.■ vSphere Web Client 6.0

<Installation folder of vCenter Server>\vCenter Server\WebClient\plugin-packages\HitachiStoragePlugin

■ vSphere Web Client 6.5/6.7

<Installation folder of vCenter Server>\vCenterServer\runtime\vsphere-client\plugin-packages\HitachiStoragePlugin

■ vCenter Server Appliance

/usr/lib/vmware-vsphere-client/plugin-packages/HitachiStoragePluginFirst confirm that sufficient free space to install the storage plug-in is availableon the drive where vSphere Web Client is installed.

RAID levelRAID0/1+0/1/5/6 are supported. VSP Gx00 and VSP Fx00 support RAID1, RAID5,and RAID6. Note: do not use RAID0 in the storage system because it does not havedata redundancy.

Registering multiple storage systems that have the same serial numberYou cannot register multiple storage systems that have the same serial number inthe Hitachi Storage Plug-in.

Restrictions of the host group name or iSCSI target nameHost group names or iSCSI target names may not include brackets ( [ ] ).




Resource groupThe Hitachi Storage Plug-in does not support resource group management. If youuse the Hitachi Storage Plug-in, please verify the following:■ Storage users and HDvM users registered with the Hitachi Storage Plug-in can

view all resource groups. If the user's view of resource groups is limited, theHitachi Storage Plug-in will not operate correctly.

■ The Hitachi Storage Plug-in does not support creation of LUs or Datastores bydesignating the resource groups.

SSL Communication with the HDvM serverNot supported.

SSL Communication with the Configuration Manager serverIn vSphere 6.0 environments, an SSL communication cannot be establishedbetween the Hitachi Storage Plug-in and Configuration Manager server.

Upgrading the vSphere Web ClientUninstall the Hitachi Storage Plug-in before upgrading the vSphere Web Client.Then reinstall or update installation of the Hitachi Storage Plug-in.

Caution: When upgrading the storage plug-in software, informationregistered in the current version of the vSphere Web Client is nottransferred to the upgraded version.




Chapter 3: Setting up the Hitachi Storage Plug-infor VMware vCenter

The procedures in this chapter guide you through the Hitachi Storage Plug-in installationand configuration processes. They also describe how to uninstall, update, and repair aninstallation and how to modify the configuration file.

Installing the Hitachi Storage Plug-in

Verify that your environment and storage systems meet the prerequisites describedbelow, then follow the appropriate procedure below to install your selected version ofthe storage plug-in.

Installation prerequisites

Set up the vSphere environment and confirm that the storage system is prepared to useHitachi Storage Plug-in.

Installing the Windows version

This procedure describes how to install the Hitachi Storage Plug-in for Windows. TheHitachi Storage Plug-in will renew if you have an older version. The installation processremains the same.

Procedure

1. After moving the installer file, Hitachi-StoragePlugin-setup(03.10.0)-01.exe to a newly created folder which does not have aninappropriate DLL, run the installer file.

2. Click Next.3. Click Next to start the installation process.4. Click Finish to complete.5. Restart the VMware vSphere Web Client service or VMware Service Lifecycle

Manager service.

For details about how to restart the service, see Starting and stopping services inWindows (on page 26) .

Chapter 3: Setting up the Hitachi Storage Plug-in for VMware vCenter


Installing the vCenter Server Appliance version

This procedure describes how to install the Hitachi Storage Plug-in for vCenter ServerAppliance version. The Hitachi Storage Plug-in replaces the older version. The installationprocess remains the same.

Before you begin■ Log in with root user credentials.■ Verify the installation of a vSphere Web Client that supports the Hitachi Storage Plug-

in.■ Confirm free disk space of 110 MB or more.

Procedure

1. Log in with root user credentials.2. Run the installer file:

# ./Hitachi-StoragePlugin-setup03.10.0-01.bin3. On the Welcome screen, press Enter.

Note: Warnings may be displayed if there is insufficient free space onthe install destination drive. Installation requires 100 MB or more of freespace. Confirm there is sufficient free space, then reinstall the product.

4. The default fixed installation path is displayed:/usr/lib/vmware-vsphere-client/plugin-packages

5. Press Enter to complete the installation.6. Restart the vSphere Web Client service.

For details about how to restart the service, see Starting and stopping services inthe vCenter Server Appliance (on page 26) .

Note:

■ SDK 6.0 will be installed.

■ For details about accessing the vCenter Server Appliance using ssh,see the documentation provided by VMware.

■ Verify the configuration files. The configuration file(hilogger.config) is created in the Hitachi Storage Plug-ininstallation folder, when the Hitachi Storage Plug-in is installed.

Uninstalling the Hitachi Storage Plug-in

Use one of the procedures listed below to uninstall your version of the Hitachi StoragePlug-in.

Installing the vCenter Server Appliance version



Uninstalling the Windows version

Procedure

1. Stop the VMware vSphere Web Client service or VMware Service Lifecycle Managerservice.

For details about how to stop the service, see Starting and stopping services inWindows (on page 26) .


3. On the Welcome screen, choose Remove, then click Next.4. Click Yes.5. The Uninstall Complete message informs you when Hitachi Storage Plug-in is

uninstalled. Click Finish.6. Confirm that Hitachi Storage Plug-in for VMware vCenter is removed from the

Programs and Features window.

Note: Files that are generated at installation and files you created in theinstalled folders remain even after the uninstallation is completed.Manually remove the folder and files if required.

7. Start the VMware vSphere Web Client service or VMware Service Lifecycle Managerservice, if necessary.

For details about how to start the service, see Starting and stopping services inWindows (on page 26) .

Uninstalling the Hitachi Storage Plug-in from the Control Panel

Procedure



2. In the Programs and Features list in the Control Panel, select Hitachi Storage Plug-in for VMware vCenter. Click Uninstall.

3. Click Yes.4. Click Finish.5. From the Program and Features window, confirm the removal of the Hitachi

Storage Plug-in for VMware vCenter. Even if the uninstallation is complete, somefiles are automatically created during installation. The files that the user created inthe installation folder are not removed. Manually remove the folder and files ifnecessary.

Uninstalling the Windows version



6. Start the VMware vSphere Web Client service or VMware Service Lifecycle Managerservice, if necessary.


Uninstalling the Hitachi Storage Plug-in vCenter Server Applianceversion

For details about the SSH/Bash shell connection to vCenter Server Appliance and fileforwarding, see the VMware documentation provided by VMware Inc.

Procedure

1. Log in as a root user to the vCenter Server Appliance with SSH.2. Stop the VMware vSphere Web Client service.

For details about how to stop the service, see Starting and stopping services in thevCenter Server Appliance (on page 26) .

3. Enter these commands:# cd /usr/lib/vmware-vsphere-client/plugin-packages/HitachiStoragePlugin/plugins# ./Uninstall.sh

4. Choose option Yes. Enter 1, then press Enter.5. Start the VMware vSphere Web Client service.

For details about how to start the service, see Starting and stopping services in thevCenter Server Appliance (on page 26) .

Repairing the Hitachi Storage Plug-in

Repairing the Windows installation

If you delete a file from the installation destination folder by mistake, you can restore itby repairing the installation. There are two ways you can repair the installation:■ Hitachi Storage Plug-in Installer■ Control Panel

Note: Whenever you repair an installation, registered storage systeminformation may be removed. If this happens, re-register the storage systeminformation using the Adding a storage system (on page 29) .

Uninstalling the Hitachi Storage Plug-in vCenter Server Appliance version



Procedure




3. On the Welcome screen, choose Repair, then click Next.4. If the vSphere Web Client service is running, a dialog box appears to show that the

service is running. Stop the vSphere Web Client service, then click Next.

Note: The message indicating that the service is running does notappear if the service has already stopped.

5. Click Finish.6. Start the VMware vSphere Web Client service or VMware Service Lifecycle Manager

service.


Repairing the vCenter Server Appliance version installation

If you have mistakenly deleted a file from the install folder, you can restore the file byrepairing the installation.

Note: Whenever you repair an installation, registered storage systeminformation may be removed. If this happens, re-register the storage systeminformation using the Adding a storage system (on page 29) .

The following two repair installation procedures are available.■ Run RepairInstall.sh in the installation folder.

■ Run repair in the <installation folder>:

/ChangeHitachiStoragePlugin/ChangeHitachiStoragePlugin -repair

Procedure

1. Log in with root user credentials.2. Stop the VMware vSphere Web Client service.

For details about how to stop the service, see Starting and stopping services in thevCenter Server Appliance (on page 26) .

3. Run RepairInstall.sh or ChangeHitachiStoragePlugin -repair

Note: For details about accessing the vCenter Server Appliance usingssh, see the documentation provided by VMware.

Repairing the vCenter Server Appliance version installation



4. On the Manage Instances screen, press Enter.5. Select option 1, press Enter.

Note: If you have not logged in with root credentials, an error messagemay be displayed: verify the prerequisites have been met, then retry therepair installation procedure.

6. Press Enter to exit the installer.7. Start the VMware vSphere Web Client service.

For details about how to start the service, see Starting and stopping services in thevCenter Server Appliance (on page 26) .

Starting and stopping services in Windows

In Windows, you can start and stop the service of the VMware vSphere Web Client orVMware Service Lifecycle Manager.

Procedure

1. Log in to Windows.2. Open Server Manager.3. Click Tools > Services.4. Right click the VMware vSphere Web Client or VMware Service Lifecycle

Manager.5. Click Start or Stop.

Starting and stopping services in the vCenter ServerAppliance

In the vCenter Server Appliance, you can start or stop the vSphere Web Client service.

Procedure

1. Log in as a root user to the vCenter Server Appliance.

Starting and stopping services in Windows



2. Enter the following commands:

■ For vSphere 6.5/6.7:

To start the service:

# service-control --start vsphere-clientTo stop the service:

# service-control --stop vsphere-client■ For vSphere 6.0:

To start the service:

# service vsphere-client startTo stop the service:

# service vsphere-client stop

Changing the configuration files

When the Hitachi Storage Plug-in is installed, configuration files (hilogger.config andhivcenter.config) are created in the Hitachi Storage Plug-in installation folder. Usehilogger.config to set the log output formats generated by Hitachi Storage Plug-in.Use hivcenter.config to set the values that can be specified as LUN IDs.

Note:■ If you change a configuration file, you will need to restart the service. For

details about how to restart the service, see Starting and stopping servicesin Windows (on page 26) or Starting and stopping services in the vCenterServer Appliance (on page 26) .

■ Edit the file with a text editor using alphanumeric characters. While editingthis file, be sure to press <Enter> at the end of each line, including the file'sfinal line (the file should end with a blank line).

Log file size

To specify the maximum size of logs files, edit [MaxFileSize=<size>] in thehilogger.config file.

■ For <size>, specify a value in megabytes.

■ Specify between 1 and 100.■ Specify <size> in single-byte decimal numbers.

■ Insert a line feed after [MaxFileSize=<size>].

■ If the omitted or non-allowed values (outside the maximum and minimum values orother than single byte values) are used, the default value of 10 MB is used.

Changing the configuration files



Number of log generations

To specify the maximum number of log generations to keep, edit[MaxBackupIndex=<number-of-generations>] in the hilogger.config file.

■ Specify between 1 and 255.■ Specify <number-of-generations> in single-byte decimal numbers.

■ Insert a line feed after [MaxBackupIndex=<number-of-generations>].

■ If the omitted or non-allowed values (outside the maximum and minimum values orother than one-byte values) are used, the default value of 19 generations is used.

■ When a log file's size exceeds the specified maximum size, the log files will rotate (i.e.log.0.txt will become log.1.txt).

LUN ID

On the Storage Configuration screen of the Provision Datastore wizard, you can specifyLUN IDs. You can change the range of LUN IDs that can be specified on this screen byediting the hivcenter.config file to set the maximum and minimum values of therange.■ Specify values for <minimum-LUN-ID> and <maximum-LUN-ID> in

[MinLUNID=<minimum-LUN-ID>] and [MaxLUNID=<maximum-LUN-ID>],respectively.

■ Specify values that are equal to or greater than 0.■ The maximum value that can be specified as a LUN ID for storage systems is different

from that which can be specified for ESXi hosts. Be sure to check the specifications ofthe storage system or ESXi host that you are using.

■ If no values are specified or an invalid value (a value outside the valid range, a valueincluding a multi-byte character, or a minimum value that is greater than themaximum value) is specified, the default values of 0 and 1023 are used for theminimum value and maximum value, respectively.

Note: If you do not specify a value for LUN ID on the Storage Configurationscreen of the Provision Datastore wizard, a value (which might be outside ofthe range defined by <minimum-LUN-ID> and <maximum-LUN-ID>) will beautomatically assigned.

Number of log generations



Chapter 4: Using the Hitachi Storage Plug-in forVMware vCenter

This chapter explains how to access the plug-in, add and remove storage systems, andperform storage provisioning operations from within the VMware vSphere Web Client.

Accessing the Hitachi Storage Plug-in

When the storage plug-in is installed, the Hitachi Storage Plug-in icon is added to thevSphere Web Client window.

Procedure

1. Log in to the vSphere Web Client from a browser.2. Move to the vSphere Web Client home screen.3. Click the Hitachi Storage Plug-in icon.

Adding a storage system

Use Add Storage System to register storage systems to be monitored by the storageplug-in. The registration procedure differs slightly according to the type of storagesystem you want to add.

Note:■ For Hitachi Storage Plug-in, you cannot use both HDvM and Hitachi

Configuration Manager to manage storage systems that have the sameserial number.

■ To correctly display global-active device (GAD) volumes with HitachiStorage Plug-in, you will need to use either HDvM or Hitachi ConfigurationManager to manage both the primary storage system and the secondarystorage system.

Adding a VSP or HUS VM storage system

Procedure

1. In the Hitachi Storage Plug-in window, click Add Storage System.2. On Model, select VSP and HUS VM; click Next.

Chapter 4: Using the Hitachi Storage Plug-in for VMware vCenter


3. On Information, enter the following information for the HDvM server:

■ IP Address

■ Port Number

■ User ID

■ Password

4. Click Next.5. On Discovery, select a storage system that you want to register from the list. You

can add only one storage system at a time. Click Next.6. On Summary, confirm the model and other information for the storage system you

selected.7. Click Finish.

Note: If connection fails (for example, a communication error occurs, therequired storage systems are not displayed, or the user ID or passwordis incorrect), troubleshoot the issue or contact your storage systemadministrator to verify that your user account settings are correct.

Adding a VSP F400, F600, F800, F1500 or VSP G200, G400, G600,G800, G1000, G1500 storage system (when Hitachi ConfigurationManager is used)

Procedure

1. In the Hitachi Storage Plug-in window, click Add Storage System.2. On Model, select VSP F400, F600, F800, F1500 and VSP G200, G400, G600, G800,

G1000, G1500. Select REST from the Select an API list.3. Click Next.4. On Information, enter the following information for the Configuration Manager

server:

■ IP Address

■ Port Number

In a vSphere 6.5/6.7 environment, if you want to use SSL communication betweenHitachi Storage Plug-in and the Configuration Manager server, select Use SSL.

5. Click Next.6. On Physical Storage Discovery, select all physical storage systems to be registered

and all physical storage systems on which the virtual storage systems to beregistered exist. (You can select multiple physical storage systems at the same time.)Click Next.

7. On Authorization, enter the user ID and password for each of the selected physicalstorage systems.Click Next.

Adding a VSP F400, F600, F800, F1500 or VSP G200, G400, G600, G800, G1000, G1500 storage system(when Hitachi Configuration Manager is used)



8. On Virtual Storage Discovery, select all physical storage systems and virtualstorage systems to be registered. (You can select multiple storage systems at thesame time.)

9. On Summary, confirm the model and other information for the storage system youselected.

10. Click Finish.

Note:

If connection fails (for example, a communication error occurs, therequired storage systems are not displayed, or the user ID or passwordis incorrect), troubleshoot the issue or contact your storage systemadministrator to verify that your user account settings are correct.

Adding a VSP F400, F600, F800, F1500 or VSP G200, G400, G600,G800, G1000, G1500 storage system (when HDvM is used)

Procedure

1. In the Hitachi Storage Plug-in window, click Add Storage System.2. On Model, select VSP F400, F600, F800, F1500 and VSP G200, G400, G600, G800,

G1000, G1500. Select HDvM from the Select an API list.3. Click Next.4. On Information, enter the following information for the HDvM server:

■ IP Address

■ Port Number

■ User ID

■ Password

5. Click Next.6. On Discovery, select a storage system that you want to register from the list. You

can add only one storage system at a time. Click Next.7. On Summary, confirm the model and other information for the storage system you

selected.8. Click Finish.

Note: If connection fails (for example, a communication error occurs, therequired storage systems are not displayed, or the user ID or passwordis incorrect), troubleshoot the issue or contact your storage systemadministrator to verify that your user account settings are correct.

Adding a VSP F400, F600, F800, F1500 or VSP G200, G400, G600, G800, G1000, G1500 storage system(when HDvM is used)



Adding a VSP F350, F370, F700, F900 or VSP G350, G370, G700, G900storage system

Before you begin

In Hitachi Configuration Manager, you can set which of the storage system's controllers(controller 1 or controller 2) you want to use.

Procedure

1. In the Hitachi Storage Plug-in window, click Add Storage System.2. On Model, select VSP F350, F370, F700, F900 and VSP G350, G370, G700, G900;

click Next.3. On Information, enter the following information for the Configuration Manager

server:

■ IP Address

■ Port Number

In a vSphere 6.5/6.7 environment, if you want to use SSL communication betweenHitachi Storage Plug-in and the Configuration Manager server, select Use SSL.

4. Click Next.5. On Physical Storage Discovery, select all physical storage systems to be registered

and all physical storage systems on which the virtual storage systems to beregistered exist. (You can select multiple physical storage systems at the same time.)Click Next.

6. On Authorization, enter the user ID and password for each of the selected physicalstorage systems.Click Next.

7. On Virtual Storage Discovery, select all physical storage systems and virtualstorage systems to be registered. (You can select multiple storage systems at thesame time.)

8. On Summary, confirm the model and other information for the storage system youselected.

9. Click Finish.

Note:

If connection fails (for example, a communication error occurs, therequired storage systems are not displayed, or the user ID or passwordis incorrect), troubleshoot the issue or contact your storage systemadministrator to verify that your user account settings are correct.

Adding a VSP Gx00 NAS module, VSP Fx00 NAS module, or HNAS asa file storage system

Procedure

1. In the Hitachi Storage Plug-in window, click Add Storage System.

Adding a VSP F350, F370, F700, F900 or VSP G350, G370, G700, G900 storage system



2. On Model, select VSP Gx00 NAS module / VSP Fx00 NAS module / HNAS; clickNext.

3. On Management Server Information, enter the IP address and port number forthe Metro server or for one of the storage controllers; click Next.

4. On Admin EVS, enter the IP address, user ID, and password for the EVS server. Ifyou entered the IP address of one of the storage controllers on the ManagementServer Information, enter that same IP address here; click Next.

5. On Summary, verify the settings. Use the Back button to modify any of thesettings.

6. Click Finish.7. Refresh the storage system, see Refreshing storage system information (on

page 33) .

Removing a storage system

Use Remove Storage System to remove a storage system from being monitored by thestorage plug-in.■ Using the icon in the Storage Systems List window.

■ From the Actions list in the Storage Systems List window.

Note: Even if you remove storage systems using Remove Storage System,datastores or LUs created by using the Hitachi Storage Plug-in remain. If youwant to remove those datastores or LUs, register the storage systems again,and then use Deleting datastores (on page 42) .

Procedure

1. In the Navigator pane, click Storage Systems.2. Select the storage system you want to remove from the Storage Systems list.3. Click Remove Storage System.4. Click Yes.

Refreshing storage system information

Use Refresh Storage System to update the information for all or selected storagesystems. Refreshing the storage systems from the Home screen updates the informationfor all storage systems while refreshing from the Storage Systems list screen updates theinformation for selected storage systems only.

Removing a storage system



Note:■ When you use the following file storage systems, always refresh the

storage system information after adding a storage system, provisioning adatastore, or deleting a datastore.● VSP Gx00 NAS module● VSP Fx00 NAS module● HNAS 4000

■ If you change the storage system configuration by using other tools,refresh the applicable storage system information before provisioning ordeleting a datastore.

You can run Refresh Storage System from the Objects screen or under Actions.

Refreshing all storage systems

When all registered storage systems have not been refreshed recently, you may beprompted to refresh. Refreshing storage systems from the Home window refreshes theinformation for all registered storage systems. To refresh information for a single storagesystem, run Refresh from the Storage Systems list screen.

Procedure

1. Go to the Home screen of the Hitachi Storage Plug-in.2. In the message, click Yes.3. Click OK.

All registered storage systems information will be refreshed. If you like to selectindividual storage systems, run refresh from the Storage Systems screen.The progress of the refresh is shown in the Recent Tasks pane.Refreshing the storage task completes.

4. Click the Refresh icon in the vSphere Web Client title bar to display the refreshedinformation.

Refreshing selected storage systems

Refreshing storage systems from the Storage Systems list screen refreshes theinformation for only the storage systems selected in the Storage Systems list.

Before you begin

You must refresh storage systems before the following actions to avoid error displaysand un-registration of the storages systems occur. If any of the following settings for the

Refreshing all storage systems



selected storage system have been changed before refreshing any storage systems, anerror appears, then the selected storage system is removed from the window.■ The password is changed.■ The account is removed.■ The View authority of the target storage system is removed from the account.

Note: To display the correct information, register the storage systems again.

Procedure

1. On the Hitachi Storage Plug-in screen, click the Storage Systems.2. Select the Storage Systems.3. In the Actions drop down, choose Refresh Storage System.4. In the verifying message, click Yes.5. If a second confirmation message appears, click OK.

The progress of the refresh is shown in the Recent Tasks pane.

The Refresh Storage task completes.

6. Click the Refresh icon in the vSphere Web Client title bar to display the refreshedinformation.

Provisioning datastores

The Provision Datastore command enables you to create LUs for use as VMFSdatastores/RDMs and enables you to create an export for use as NFS datastores by astorage system registered in the Hitachi Storage Plug-in.

Overview of Provision Datastore

Before you begin

Create the host group or iSCSI target in which the WWN for the ESXi HBA is registered.Otherwise, the host group or iSCSI target will not appear on the selection screen.

An example of the host group used to assign the LU:

Provisioning datastores



Example of host group: *1 Logical unit and datastore are created in the ProvisionDatastore.

Host group 1 Name BL360-B0-9

Port 0A

WWN Storage adapter 1

Logical unit Logical unit 1 *1

The Provision Datastore is available in the following screens:■ Storage Devices list screen (Provision Datastore icon)■ Datastores list screen (Provision Datastore icon)■ Datastores list screen (Actions menu)

Creating a datastore

This feature allows VMware datastores to be created, including the storage objectsnecessary to support them. Both VMFS and NFS datastores and Raw Device Mappingsare supported.

Creating a datastore



Creating VMFS datastores

Before you begin■ Verify that all involved ESXi hosts have Fibre Channel connectivity to the storage

system.■ Choose a storage system upon which to create an LU.■ Verify the DP pool that creates the LU used in the VMFS datastore.■ Verify the Host group or iSCSI target of the storage system in which the WWN or iSCSI

name of the storage adapter (HBA ESXi host) is set.■ Make sure that the storage system information and vSphere environment information

are current. If the information is not up to date, run Refresh Storage System.

Procedure

1. In the Hitachi Storage Plug-in navigator, click Storage Devices.2. Click the Provision Datastore icon to start the Provision Datastore.3. On the Type screen, choose VMFS datastore, click Next.4. On the VMFS Version screen, choose the VMFS version.5. Click Next.6. On the Name and Capacity screen, determine how many datastores you want to

create (single or multiple).

To create a single datastore To create multiple datastores

1. Select Single Datastore creation. 1. Choose Multiple Datastorecreation.

2. Enter a name (3-42 characters) forthe datastore. Acceptable characters:alphanumeric, space, ! # ( ) + - , . = @ _

2. Enter a name (3-42 characters) for thedatastore. Acceptable characters:alphanumeric, space, ! # ( ) + - , . = @ _

3. Enter a value for the datastorecapacity as allowed by the ESXi serveryou are using (2-65,535 GB). The totalcapacity of the datastore is displayedon the Total column.

3. In Number of datastores, enter thenumber of the datastores you want tocreate. You can create up to 256datastores.

4. For the Starting Number, enter astarting number (0-999) for thedatastores. The datastore name isdisplayed on the datastore Namecolumn.




To create a single datastore To create multiple datastores

5. In Datastore Capacity, enter acapacity value for each datastore (2GB-65,535 GB). The total capacity of thedatastore is displayed on the Totalcolumn.

7. Click Next.8. On the Storage Adapter screen, select the storage adapter for the datastores.

a. From Select Cluster or Host, select the cluster or ESXi host.b. Select the storage adapter.c. Click Next.

9. On the Storage Configuration screen, configure the storage system for thedatastore(s).

a. Select Storage System.

For virtual storage systems, the serial numbers for the virtual storage andphysical storage systems are displayed together in Storage System.

<Storage model>_<Virtual storage serial number>(<Physicalstorage serial number>)

b. Select Storage Pool / RAID Group.c. Select Capacity Saving if you chose VSP F350, F370, F700, F900 or VSP G350,

G370, G700, G900.d. Specify a value for LUN ID.

You can specify this item if you selected Single Datastore creation on theName and Capacity screen and selected a storage system that is managed byHitachi Configuration Manager. You can specify a value in the range from 0 to1023. If you do not specify a value for LUN ID, a value will be automatically set.

Tip: You can change the range of LUN IDs that can be specified byediting the hivcenter.config file. For details, see Changing theconfiguration files (on page 27) .

e. Select Host Group/Target.f. Click Next.

10. On the Summary screen, confirm the settings for the datastore. Click a screenname to modify any settings.

11. Click Finish. The datastore creation progress and results can be viewed in theRecent Tasks of the vSphere Web Client.

Note: You can cancel the Provision Datastore after the datastorecreation process has started; however, rollback is not enabled. Any LUsalready created will remain on the storage system and must be deletedmanually.




Creating LUs for Raw Device Mapping (RDM)

Before you begin■ Verify that the storage adapter is connected to the storage system (HBA ESXi host).■ Choose the storage system for creating the LU used for RDM.■ Verify the DP pool that creates the LU used for RDM.■ Verify the Host group or iSCSI target of the storage system in which the WWN or iSCSI

name of the storage adapter (HBA ESXi host) is set.■ Make sure that the storage system information and vSphere environment information

are current. If the information is not up to date, run Refresh Storage System.

Procedure

1. From the Inventory list in the Navigator, click Storage Devices.2. To start the Provision Datastore wizard, click the Provision Datastore icon.3. On the Type screen, select LUN for Raw Device Mapping, click Next.4. On the Capacity screen, choose Single LUN creation or Multiple LUN creation.

For Single LUN creation For Multiple LUN creation

1. Choose Single LUN creation. 1. Choose Multiple LUN creation.

2. Enter a value for the LUN capacity (2GB-65,535 GB).

2. Enter the number of LUs (256maximum) you want to create.

3. Click Next. 3. Enter a capacity value for each LU(2-65,535 GB). The total capacity for themultiple LUs is displayed on the Total.

4. Click Next.

5. On the Storage Adapter screen, select the storage adapter for the LUs.a. From Select Cluster or Host, select the virtual machine on which the LUs are

to be created.b. Select the storage adapter for the LUs.c. Click Next.

6. On the Storage Configuration screen, configure the storage system for the LUs.a. Select Storage System.

For virtual storage systems, the serial numbers for the virtual storage andphysical storage systems are displayed together in Storage System.

<Storage model>_<Virtual storage serial number>(<Physicalstorage serial number>)

b. Select Storage Pool.c. Select Capacity Saving if you chose VSP F350, F370, F700, F900 or VSP G350,

G370, G700, G900.

Creating LUs for Raw Device Mapping (RDM)



d. Specify a value for LUN ID.You can specify this item if you selected Single LUN creation on the Capacityscreen and selected a storage system that is managed by Hitachi ConfigurationManager. You can specify a value in the range from 0 to 1023. If you do notspecify a value for LUN ID, a value will be automatically set.

Tip: You can change the range of LUN IDs that can be specified byediting the hivcenter.config file. For details, see Changing theconfiguration files (on page 27) .

e. Select Host Group/Target.f. Click Next.

7. On the Summary screen, confirm the settings for the LUs. Click a screen name tomodify any settings.

8. Click Finish. The datastore creation progress and results can be viewed in theRecent Tasks pane of the vSphere Web Client.

Note: You can cancel the LU creation process after the datastorecreation process has started; however, any LUs already created willremain on the storage system and must be deleted manually. Deletethem manually using Delete Datastore. Contact your storage systemadministrator for additional assistance.

Creating NFS datastores

Use the Provision Datastore wizard to create an NFS Datastore. The Metro ServerInformation page is accessible only at the time of NFS Datastore creation. Apply MetroServer information to the Metro Server Information page.

Note: Only the storage manager can view an LDEV-labeled creation.

Before you begin■ If a file system is not created on the HNAS storage system prior to datastore creation,

the file system is not displayed at the time of selection in the Provision Datastoreprocedure. You need to set the following:● The NFS export and the storage system for the connection.● The NAS storage system for NFS datastore.● File systems and folders for NFS datastore.● The ESXi for datastore creation.

Also, verify the created file system and availability on the HNAS storage system.

■ Make sure that the storage system information and vSphere environment informationare current. If the information is not up to date, run Refresh Storage System.

Procedure

1. On the Hitachi Storage Plug-in screen, click Storage Devices.

Creating NFS datastores



2. Click Provision Datastore to start the Provision Datastore wizard.3. On the Type screen, select NFS datastore, click Next.4. On the Storage Information screen, select Storage System from the drop-down

menu. Click Next.5. On the File System screen, select File System. Click Next.

Caution: Only file systems from Admin EVS-targeted user accounts aredisplayed in the list. If no file systems are displayed, ask your storagesystem administrator to verify your user account settings.

6. On the NFS Export Configuration, choose NFS export or check Create NewExport box.To create an NFS Export: Select NFS Export, click Next.To create new export:

a. Check Create New Export box.b. Enter the NFS Export Name.c. Enter the Directory Path to the ESXi host.d. Enter the host IP address.e. Select a Snapshot option.f. Select a Local Read Cache.g. Select a Transfer to Replication Target.h. Click Next.

7. On the Datastore Configuration, enter a name for the datastore. The export pathwill be displayed after entering a name.

■ Acceptable characters (3-42 characters) are alphanumeric, space, ! # ( ) + - , . = @_

■ If you do not want to edit the datastore, check the Mount NFS as Read Only.

8. Click Next.9. On the Host Configuration screen, select NFS datastore host. Click Next.

10. On the Summary screen, confirm the settings. Click a screen name to go back andmodify settings.

11. Click Finish. The datastore creation progress and results can be viewed in theRecent Tasks pane of the vSphere Web Client.After the datastore is created, Click Refresh Storage System to update the storagesystem information. Then the LU appears in the Storage Devices list.

Note: You can cancel the Provision Datastore; however, the NFS exportalready created will remain in the HNAS. To delete an NFS export, contactyour storage system administrator for assistance.

Cancelling Provision Datastore

You can cancel Provision Datastore after the datastore creation process is started;however, rollback is not enabled. Any LUs already created remain on the storage systemand must be deleted manually.

Cancelling Provision Datastore



When you cancel Provision Datastore, rollback is disabled. Created LUs on the storagesystem remain. Delete LUs accordingly.

Procedure

1. Click Refresh Storage System.2. Click Delete datastore, then manually delete any LUs remaining on the storage

system. See Deleting datastores (on page 42) or ask the storage administrator fordeletion of Storage LUN output in the message.

3. Verify that all LUs have been deleted.If the target storage system model is the VSP Gx00 NAS module, the VSP Fx00 NASmodule, or HNAS 4000, click Refresh Storage System and then verify that the LUshave been deleted.

Deleting datastores

Use Delete datastore to delete datastores or LUs on storage systems that are registeredwith the Hitachi Storage Plug-in.

Some datastores cannot be deleted using the deleting datastore command. Use vSphereWeb Client to delete the following:■ VVol Datastore■ Datastores with a virtual machine or virtual machine template■ Datastores with multiple LUs■ Datastores with pair-configured LUs■ Datastores with LUs used in a Raw Device Mapping (RDM)

If you are still unable to delete a datastore, ask your storage administrator to delete it foryou.

Deleting a VMFS datastore or LU

You can delete the VMFS datastores or LUs that are registered in Hitachi Storage Plug-inon storage systems.

Caution:

Even after datastores or LUs that were created by selecting Deduplication AndCompression have been deleted from the Plug-in screen, it might take sometime before the LUs in the storage system are completely deleted. For thisreason, free space in the pool might not increase immediately after thedeletion.

Before you begin

Make sure that the storage system information and vSphere environment informationare up to date. If the information is not up to date, run Refresh Storage System.

Deleting datastores



Procedure

1. On the Hitachi Storage Plug-in window, click Storage Devices.2. Under Datastore, on Storage Devices, select the datastore or LU you want to

delete. You can delete only one datastore at a time.3. Click Delete Datastore icon.4. Click Yes to confirm deletion.

Note: You can cancel the task execution by clicking the Cancel. Whenyou cancel Delete Datastore, the LUN that is not deleted remains.Delete unnecessary LUN.

The results of the Delete Datastore appear in the vSphere Web Client task. Whenyou click Refresh icon, Recent Tasks pane displays the Delete Datastore task.

Deleting an NFS datastore

Before you begin

Make sure that the storage system information and vSphere environment informationare up to date. If the information is not up to date, run Refresh Storage System.

Procedure

1. On the Hitachi Storage Plug-in window, Click Storage Devices.2. Select the NFS datastore you want to delete.3. Click Actions menu.4. Select All Hitachi Storage Plug-in Actions.5. Click Delete Datastore.6. Click Yes.

The results of the Delete Datastore appear in the vSphere Web Client task.7. Run Refresh Storage System to retrieve the latest storage system and vSphere

environment information.

Deleting an NFS datastore



Chapter 5: Information Display

Hitachi Storage Plug-in for VMware vCenter displays Hitachi storage system informationin VMware vSphere Web Client. This information includes views of storage systemproperties and related objects, and lists of storage devices, ESXi hosts, datastores andvirtual machines.

Datastores information

Once a Hitachi storage system has been registered with the Hitachi Storage Plug-in,datastores backed by that storage system will appear on this screen. Only datastorescreated by using the Hitachi Storage Plug-in will appear.

If you select a datastore from the list, a Hitachi Storage Information area will appear onthe Summary tab.

This area displays Hitachi storage system configuration objects associated with thedatastore. For example, if a datastore is backed by a LU, information identifying the LU'sstorage system and LUN will appear in this area.

To display this information, first select a datastore, then click Summary.

Host information

The host list screen displays the ESXi hosted registered storage system in Hitachi StoragePlug-in.

Once a storage system has been registered with the Hitachi Storage Plug-in, ESXi hostswhich consume resources from that storage system will appear on the Hosts screen.

When an ESXi host is selected from this screen, a Hitachi Storage Information area willappear under Summary. This area displays information about the storage systemsassociated with the selected ESXi host.

To display this information, first select an ESXi host, then click Summary.

Virtual Machines information

The Virtual Machines list displays the virtual machines list of the registered datastores inthe Hitachi Storage Plug-in.

Once a Hitachi storage system is registered with the Hitachi Storage Plug-in, virtualmachines which consume resources from that storage system will appear on this screen.



If you select a virtual machine from the list, a Hitachi Storage Information area willappear on the Summary.

This area displays Hitachi storage system configuration objects associated with thevirtual machine. For example, if a virtual machine resides on a VMFS filesystem backedby a Hitachi LU, information identifying the LU's storage system and LUN will appear inthis area.

To display this information follow the procedure below.

Procedure

1. Select a virtual machine.2. click Summary.

Virtual Machines information



Chapter 6: Troubleshooting

Troubleshooting the Hitachi Storage Plug-in installation

If problems occur when you use the installer of the storage plug-in, an error message isdisplayed. Follow the error message for further directions.

If you cannot identify the problem, verify the following:■ All requirements are met.■ Compare settings against restrictions and considerations.■ View the Log Files chapter and Collecting information topics.

If none of the above solves the problem, contact Support.

Troubleshooting Hitachi Storage Plug-in operational errors

If problems occur while using the Hitachi Storage Plug-in, error information is displayedand output to a log file. Follow the error message for further directions.

If you cannot identify the problem, verify the following:■ All requirements are met.■ Review the operating environment and Errors Occurring in Storage Systems topic.

Note:

If you are using Hitachi Configuration Manager, the status of the task torefresh configuration information might not be "Succeeded". To check thestatus of the task to refresh the configuration information of a storage systemmanaged by Hitachi Configuration Manager, contact your storage systemadministrator.

If none of the above solves the problem, contact Support.

Troubleshooting storage system errors

When errors occur within a storage system, the Hitachi Storage Plug-in may propagateup through the and/or ESXi, and appear in the corresponding component's logs.

The following procedures explain how to investigate storage system errors.



Procedure

1. Check the storage system environment.Confirm that the storage system is online and healthy.

Also, confirm that the storage system requirements are fulfilled, and that thestorage system's configuration complies with what's described in Restrictions andconsiderations (on page 18) . Even if these requirements were met at the timeHitachi Storage Plug-in for VMware vCenter was installed, changes to the storagesystem made thereafter may have yielded an unsupported configuration.

2. Confirm Ethernet connections.Confirm that the storage system is attached to the LAN with a network cable.

3. Confirm the IP address.Confirm that the IP address being used to access the storage system matches the IPaddress displayed in its management interface.

4. Confirm the TCP port number.Verify that the TCP port number used to access the storage system has notchanged.

If the TCP port number has changed, add df-damp-snm <storage system portnumber>/tcp to the VMware management client's Services file.

5. Confirm firewall settings.Verify that the storage system's accessible using TCP/IP. Depending on specificswhich will vary between environments, it may be necessary to adjust firewallsettings to allow this access.

6. Confirm ESXi connectivity.

Verify the following:

a. Whether Fibre Channel and TCP/IP connectivity between the ESXi host and thestorage system is healthy.

b. Whether LU masking is configured correctly on the storage system. For FibreChannel access, LU masking is represented by host group objects. For iSCSIaccess, it's represented by iSCSI target objects.

Troubleshooting Hitachi Configuration Manager and HDvMserver errors

If a problem occurs while you are using the storage plug-in, a failure may have occurredon the Hitachi Configuration Manager and HDvM server. Verify the following:

Procedure

1. Confirm items of the Hitachi Configuration Manager and HDvM server environment.Verify that the Hitachi Configuration Manager and HDvM server started withoutproblems. Also, verify that Hitachi Configuration Manager and HDvM's Windowsservice has not stopped.

Troubleshooting Hitachi Configuration Manager and HDvM server errors



2. Confirm TCP/IP connectivity.Verify that the Hitachi Configuration Manager and HDvM server is attached to theLAN with a network cable.

3. Confirm the IP address.Verify that the IP address used to access Hitachi Configuration Manager and HDvMmatches the IP address it's configured to use.

4. Confirm the TCP port number.Verify that the TCP port number used for the Hitachi Configuration Manager andHDvM server is correct. Register the new number if the TCP port number isdifferent.

5. Confirm firewall settings.Verify that Hitachi Configuration Manager and HDvM is accessible using TCP/IP.

If it's inaccessible, a firewall configuration change may be required to allow access.

6. Resources managed by Hitachi Configuration Manager and HDvM.a. Ensure that the desired storage system is registered with Hitachi Configuration

Manager and HDvM.b. If a resource group lock is preventing Hitachi Configuration Manager and HDvM

from collecting information from the storage system, it may be necessary toremove the lock.

c. Verify that Hitachi Configuration Manager and HDvM is able to retrieveinformation from and configure the storage system.

d. Verify that the storage system information gotten by Hitachi ConfigurationManager and HDvM is consistent with the information displayed using morelow-level Hitachi management interfaces, such as Storage Navigator or CCI.

7. Confirm the storage system and HDvM user account.a. Verify that the storage system and HDvM account is valid and enabled.b. Verify that the storage system and HDvM account password is correct.c. Verify that the storage system and HDvM account is configured with view and

modify privileges.

Troubleshooting Provision Datastore function errors

Retry of Provision Datastore

LUs created by the Provision Datastore may not appear immediately in vSphere WebClient. If this occurs, either retry the operation, or use the rollback feature (describedbelow) to revert storage objects created by this to their state prior to its use.

It may also be necessary to run Refresh Storage System after using the ProvisionDatastore, before newly created storage objects will appear in vSphere Web Client'sStorage Devices list.

Troubleshooting Provision Datastore function errors



Procedure

1. Verify the failure message shown in the Recent Tasks.2. Click the Provision Datastore icon.3. Click Yes on the warning message.4. Try the Provision Datastore again.

The Provision Datastore task on the Recent Tasks pane will be marked completewhen the retry is finished.

5. Refresh the storage system.

Rollback of Provision Datastore

Procedure

1. Verify the failure message shown in Recent Tasks when Provision Datastore fails.2. Click the Provision Datastore icon.3. Click No on the warning.4. Click Yes on the next warning message to continue the rollback of Provision

Datastore.5. Click the Refresh icon to display the rollback progress status on the Recent tasks.

Once Recent Tasks has been refreshed, the task should appear to have beencompleted.

Note: The information displayed in Recent Tasks may not update itselfautomatically. To update Recent Tasks, click the Refresh icon.

Provision Datastore task stops before completing

If you did not run the Retry or Rollback, the task remains in-process and the created LUsremain on the server. Verify the following:

If the task stops while creating storage system LUs.1. Display the event of the task.2. Delete the storage array LU created by the partially completed task.3. Run Refresh Storage System to retrieve the latest information.

If the task stops after creating an LU, yet before performing target LU masking(the host group operation), or if the task stops after LU masking and before ESXihas detected the LU.

1. Display the event task.2. Remove the LU created by the task which did not complete from the host

group object, if applicable.3. Delete the LU created by the incomplete task.4. Run Refresh Storage System to retrieve the latest information.

Rollback of Provision Datastore



If the task stops during datastore creation.1. Run Refresh Storage System to retrieve the latest information.2. Delete LU using the Delete Datastore.3. Run Refresh Storage System a second time, to ensure that the latest

information is displayed.

Stops while retrying NFS Export Creation

Procedure

1. Vies the task event.2. Report the error message to Support.3. Run Refresh Storage System.

Stops while creating an NFS datastore

Procedure

1. Refresh the storage system.2. Report the error message for Support.3. Run Refresh Storage System again.

Troubleshooting datastore deletion errors

This section describes how to retry Delete Datastore operations and how to recoverwhen Delete Datastore stops prematurely.

Retry of Delete Datastore

Procedure

1. View the error message shown in the Recent Tasks pane.2. Click the Delete Datastore icon when a related failure message appears in Recent

Tasks.3. Click Yes on the warning message.4. Watch Recent Tasks to observe the Delete Datastore task. If the Delete

Datastore operation is successful, it will display in Recent Tasks as complete.5. Run the Refresh Storage System after using Delete Datastore.

Delete Datastore stops before it has completed

If the vSphere Web Client service stops while a Delete Datastore task is running, it mayleave a partial storage configuration in place. These procedures describe how to recoverfrom this situation.

Stops while retrying NFS Export Creation



If the task stops during the confirmation of LU usage status or datastore deletion.1. Run Refresh Storage System to retrieve the latest information.2. Observe the Datastores list to determine whether the LU being deleted

remains in the list. If it remains, try Delete Datastore again.3. Delete the LU.4. Run Refresh Storage System to retrieve the latest information.

If the task stops while unmapping or deleting the LU.1. Verify that the LU has been deleted from the storage system.2. Run Refresh Storage System to retrieve the latest information.

Delete Datastore stops before it has completed



Chapter 7: Log files

Hitachi Storage Plug-in for VMware vCenter logs messages to several different log files.This chapter explains which log file(s) correspond to each component included with andrelated to this product, and how to collect them while receiving technical support.

HiAppServerModule.log

Hitachi Storage Plug-in for VMware vCenter's plug-in component logs messages to thisfile. An example log message is shown below.

An output example of a log file error message is shown below. Search that the log type isERROR (1), and then confirm the content of the message (2) with the Error Message list.

A severity level's associated with each log message, and those with severity level "ERROR"(1) tend to be of greatest value for debugging.

By cross-referencing an "ERROR" severity log message's value (2) against the ErrorMessage list, additional insight in to symptom's cause may be found.

Information Collected During Problem Occurrence

When a problem cannot be solved by troubleshooting, provide the following to Support.

Collect Windows Event Log information

Procedure

1. Open Windows Event Viewer.2. In Event Viewer, right click on the event log category (at least Application and

System), and click Save All Events As.3. Input a file name for the export file in the File name box.4. Click the appropriate file format in the File type box, click Save.



Collect Windows system information

Procedure

1. Open Microsoft System Information.If an icon for this does not appear in Administrative Tools, it can be started from acmd or PowerShell command prompt by entering msinfo32.

2. Click Export from the File menu.3. Input the file name in the File name field.4. Click Save.

Confirm vSphere Web Client version

Procedure

1. From the Menu in vSphere Web Client, select Help -> About VMware vSphere.2. Confirm the vSphere Web Client version displayed in the dialog box.

Collect vSphere Web Client/vCenter Server logs

Create a zip file with everything located in the following directory:

For vCenter Server running in Windows:C:\ProgramData\VMware\vCenterServer\logs\vsphere-client\logs

For the Appliance version of vCenter Server:/var/log/vmware/vsphere-client/logs

Collect log files from the Hitachi Storage Plug-in

Collect the files for Hitachi Storage Plug-in in the installation folder of VMware vCenter,and then archive the collected files into a ZIP file. For details about the installation folder,see Restrictions and considerations (on page 18) .

Procedure

1. Check the following files in the folder <installation-folder>\plugins.

■ version.txt■ multiaccount.xml (if it exists as an intermediate file)

■ HNAS_multiaccount.xml (if it exists as an intermediate file)

■ modelname.config (if it exists as an intermediate file)

2. Check the log files in the folder <installation-folder>\plugins\log.

3. Archive the files that were found in steps 1 and 2 into a ZIP file.




Collect vCenter and ESXi information


Procedure




Procedure



Confirm the vCenter Server version

Procedure

1. From the home screen of vSphere Web Client, select Hosts and Clusters.2. From the tree view, select vCenter Server, and then confirm the version displayed in

Summary screen.

Collect ESXi information

Procedure

1. Go to the Home screen of vSphere Web Client.2. Select Hosts and Clusters.3. Select ESXi to see the version in Summary.

Collect storage system information

Collect logs and trace files (if available) using Storage Navigator.

Collect vCenter and ESXi information



How to collect Hitachi Configuration Manager and HDvMinformation


Procedure




Procedure



Collect Hitachi Configuration Manager maintenance information

Hitachi Configuration Manager includes a feature which allows its maintenanceinformation to be collected.

See Hitachi Command Suite Configuration Manager REST API Reference Guide for moreinformation.

Collect HDvM maintenance information

HDvM includes a feature which allows its maintenance information to be collected.

See Hitachi Command Suite User Guide for more information.

How to collect Hitachi Configuration Manager and HDvM information



Collect vCenter Server Appliance information

See, VMware vCenter Server documentation. Collect the Support Bundle. For example,from the vCenter Server Appliance Management Interface, run Summary > CreateSupport Bundle.

Note: See VMware vCenter Server documentation for steps to create aVMware Support Bundle.

Depending on the version being used, it may be possible to generate this by running:

Procedure

1. Go to Summary.2. In the vCenter Server Appliance management interface, select Create Support

Bundle.

Collect vCenter Server Appliance information



Chapter 8: Open source and third-party softwarelicenses

Software and license information

Hitachi Storage Plug-in for VMware vCenter contains software in the table below.

Software License

org.javassist:javassist (3.20.0-GA) Apache License, Version 2.0

javax.activation:activation (1.1) COMMON DEVELOPMENT ANDDISTRIBUTION LICENSE Version 1.0governed by the laws of the State ofCalifornia

javax.annotation:javax.annotation-api(1.2)

org.glassfish.hk2:osgi-resource-locator(1.0.1)

javax.ws.rs:javax.ws.rs-api (2.0.1) COMMON DEVELOPMENT ANDDISTRIBUTION LICENSE Version 1.1

org.glassfish.hk2:hk2-api (2.5.0-b30)

org.glassfish.hk2:hk2-locator (2.5.0-b30)

org.glassfish.hk2:hk2-utils (2.5.0-b30)

org.glassfish.hk2.external:aopalliance-repackaged (2.5.0-b30)

org.glassfish.hk2.external:javax.inject(2.5.0-b30)

org.glassfish.jersey.bundles.repackaged:jersey-guava (2.25)

org.glassfish.jersey.core:jersey-client (2.25)

org.glassfish.jersey.core:jersey-common(2.25)

org.glassfish.jersey.media:jersey-media-jaxb (2.25)

Chapter 8: Open source and third-party software licenses


Software License

vSphere Management SDK(6.7.0-7970399)

VMware® vSphere Software DevelopmentKit License Agreement

Apache License, Version 2.0

this is the license under which javassist is usually distributed

MPL 1.1

http://www.mozilla.org/MPL/MPL-1.1.html

this is the license under which javassist is distributed when it is bundled with JBoss

LGPL 2.1

http://www.gnu.org/licenses/lgpl-2.1.html

this is the license under which javassist can be distributed.

Apache License 2.0

http://www.apache.org/licenses/

javax.activation:activation (1.1)

COMMON DEVELOPMENT AND DISTRIBUTION LICENSE (CDDL) Version 1.0

1. Definitions.

1.1. Contributor means each individual or entity that creates or contributes to thecreation of Modifications.

1.2. Contributor Version means the combination of the Original Software, priorModifications used by a Contributor (if any), and the Modifications made by thatparticular Contributor.

1.3. Covered Software means (a) the Original Software, or (b) Modifications, or (c) thecombination of files containing Original Software with files containing Modifications, ineach case including portions thereof.

1.4. Executable means the Covered Software in any form other than Source Code.

1.5. Initial Developer means the individual or entity that first makes Original Softwareavailable under this License.

1.6. Larger Work means a work which combines Covered Software or portions thereofwith code not governed by the terms of this License.

1.7. License means this document.

1.8. Licensable means having the right to grant, to the maximum extent possible,whether at the time of the initial grant or subsequently acquired, any and all of the rightsconveyed herein.

Apache License, Version 2.0



http://www.mozilla.org/MPL/MPL-1.1.html

http://www.gnu.org/licenses/lgpl-2.1.html

http://www.apache.org/licenses/

1.9. Modifications means the Source Code and Executable form of any of the following:

A. Any file that results from an addition to, deletion from or modification of the contentsof a file containing Original Software or previous Modifications;

B. Any new file that contains any part of the Original Software or previous Modification;or

C. Any new file that is contributed or otherwise made available under the terms of thisLicense.

1.10. Original Software means the Source Code and Executable form of computersoftware code that is originally released under this License.

1.11. Patent Claims means any patent claim(s), now owned or hereafter acquired,including without limitation, method, process, and apparatus claims, in any patentLicensable by grantor.

1.12. Source Code means (a) the common form of computer software code in whichmodifications are made and (b) associated documentation included in or with such code.

1.13. You (or Your) means an individual or a legal entity exercising rights under, andcomplying with all of the terms of, this License. For legal entities, You includes any entitywhich controls, is controlled by, or is under common control with You. For purposes ofthis definition, control means (a) the power, direct or indirect, to cause the direction ormanagement of such entity, whether by contract or otherwise, or (b) ownership of morethan fifty percent (50%) of the outstanding shares or beneficial ownership of such entity.

2. License Grants.

2.1. The Initial Developer Grant.

Conditioned upon Your compliance with Section 3.1 below and subject to third partyintellectual property claims, the Initial Developer hereby grants You a world-wide, royalty-free, non-exclusive license:

(a) under intellectual property rights (other than patent or trademark) Licensable byInitial Developer, to use, reproduce, modify, display, perform, sublicense and distributethe Original Software (or portions thereof), with or without Modifications, and/or as partof a Larger Work; and

(b) under Patent Claims infringed by the making, using or selling of Original Software, tomake, have made, use, practice, sell, and offer for sale, and/or otherwise dispose of theOriginal Software (or portions thereof).

(c) The licenses granted in Sections 2.1(a) and (b) are effective on the date InitialDeveloper first distributes or otherwise makes the Original Software available to a thirdparty under the terms of this License.

(d) Notwithstanding Section 2.1(b) above, no patent license is granted: (1) for code thatYou delete from the Original Software, or (2) for infringements caused by: (i) themodification of the Original Software, or (ii) the combination of the Original Softwarewith other software or devices.

2.2. Contributor Grant.

Conditioned upon Your compliance with Section 3.1 below and subject to third partyintellectual property claims, each Contributor hereby grants You a world-wide, royalty-free, non-exclusive license:




(a) under intellectual property rights (other than patent or trademark) Licensable byContributor to use, reproduce, modify, display, perform, sublicense and distribute theModifications created by such Contributor (or portions thereof), either on an unmodifiedbasis, with other Modifications, as Covered Software and/or as part of a Larger Work;and

(b) under Patent Claims infringed by the making, using, or selling of Modifications madeby that Contributor either alone and/or in combination with its Contributor Version (orportions of such combination), to make, use, sell, offer for sale, have made, and/orotherwise dispose of: (1) Modifications made by that Contributor (or portions thereof);and (2) the combination of Modifications made by that Contributor with its ContributorVersion (or portions of such combination).

(c) The licenses granted in Sections 2.2(a) and 2.2(b) are effective on the date Contributorfirst distributes or otherwise makes the Modifications available to a third party.

(d) Notwithstanding Section 2.2(b) above, no patent license is granted: (1) for any codethat Contributor has deleted from the Contributor Version; (2) for infringements causedby: (i) third party modifications of Contributor Version, or (ii) the combination ofModifications made by that Contributor with other software (except as part of theContributor Version) or other devices; or (3) under Patent Claims infringed by CoveredSoftware in the absence of Modifications made by that Contributor.

3. Distribution Obligations.

3.1. Availability of Source Code.

Any Covered Software that You distribute or otherwise make available in Executableform must also be made available in Source Code form and that Source Code form mustbe distributed only under the terms of this License. You must include a copy of thisLicense with every copy of the Source Code form of the Covered Software You distributeor otherwise make available. You must inform recipients of any such Covered Software inExecutable form as to how they can obtain such Covered Software in Source Code formin a reasonable manner on or through a medium customarily used for softwareexchange.

3.2. Modifications.

The Modifications that You create or to which You contribute are governed by the termsof this License. You represent that You believe Your Modifications are Your originalcreation(s) and/or You have sufficient rights to grant the rights conveyed by this License.

3.3. Required Notices.

You must include a notice in each of Your Modifications that identifies You as theContributor of the Modification. You may not remove or alter any copyright, patent ortrademark notices contained within the Covered Software, or any notices of licensing orany descriptive text giving attribution to any Contributor or the Initial Developer.

3.4. Application of Additional Terms.




You may not offer or impose any terms on any Covered Software in Source Code formthat alters or restricts the applicable version of this License or the recipients rightshereunder. You may choose to offer, and to charge a fee for, warranty, support,indemnity or liability obligations to one or more recipients of Covered Software.However, you may do so only on Your own behalf, and not on behalf of the InitialDeveloper or any Contributor. You must make it absolutely clear that any such warranty,support, indemnity or liability obligation is offered by You alone, and You hereby agree toindemnify the Initial Developer and every Contributor for any liability incurred by theInitial Developer or such Contributor as a result of warranty, support, indemnity orliability terms You offer.

3.5. Distribution of Executable Versions.

You may distribute the Executable form of the Covered Software under the terms of thisLicense or under the terms of a license of Your choice, which may contain terms differentfrom this License, provided that You are in compliance with the terms of this License andthat the license for the Executable form does not attempt to limit or alter the recipientsrights in the Source Code form from the rights set forth in this License. If You distributethe Covered Software in Executable form under a different license, You must make itabsolutely clear that any terms which differ from this License are offered by You alone,not by the Initial Developer or Contributor. You hereby agree to indemnify the InitialDeveloper and every Contributor for any liability incurred by the Initial Developer or suchContributor as a result of any such terms You offer.

3.6. Larger Works.

You may create a Larger Work by combining Covered Software with other code notgoverned by the terms of this License and distribute the Larger Work as a single product.In such a case, You must make sure the requirements of this License are fulfilled for theCovered Software.

4. Versions of the License.

4.1. New Versions.

Sun Microsystems, Inc. is the initial license steward and may publish revised and/or newversions of this License from time to time. Each version will be given a distinguishingversion number. Except as provided in Section 4.3, no one other than the license stewardhas the right to modify this License.

4.2. Effect of New Versions.

You may always continue to use, distribute or otherwise make the Covered Softwareavailable under the terms of the version of the License under which You originallyreceived the Covered Software. If the Initial Developer includes a notice in the OriginalSoftware prohibiting it from being distributed or otherwise made available under anysubsequent version of the License, You must distribute and make the Covered Softwareavailable under the terms of the version of the License under which You originallyreceived the Covered Software. Otherwise, You may also choose to use, distribute orotherwise make the Covered Software available under the terms of any subsequentversion of the License published by the license steward.

4.3. Modified Versions.




When You are an Initial Developer and You want to create a new license for Your OriginalSoftware, You may create and use a modified version of this License if You: (a) renamethe license and remove any references to the name of the license steward (except tonote that the license differs from this License); and (b) otherwise make it clear that thelicense contains terms which differ from this License.

5. DISCLAIMER OF WARRANTY.

COVERED SOFTWARE IS PROVIDED UNDER THIS LICENSE ON AN AS IS BASIS, WITHOUTWARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, WITHOUTLIMITATION, WARRANTIES THAT THE COVERED SOFTWARE IS FREE OF DEFECTS,MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR NON-INFRINGING. THE ENTIRERISK AS TO THE QUALITY AND PERFORMANCE OF THE COVERED SOFTWARE IS WITH YOU.SHOULD ANY COVERED SOFTWARE PROVE DEFECTIVE IN ANY RESPECT, YOU (NOT THEINITIAL DEVELOPER OR ANY OTHER CONTRIBUTOR) ASSUME THE COST OF ANYNECESSARY SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER OF WARRANTYCONSTITUTES AN ESSENTIAL PART OF THIS LICENSE. NO USE OF ANY COVEREDSOFTWARE IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER.

6. TERMINATION.

6.1. This License and the rights granted hereunder will terminate automatically if You failto comply with terms herein and fail to cure such breach within 30 days of becomingaware of the breach. Provisions which, by their nature, must remain in effect beyond thetermination of this License shall survive.

6.2. If You assert a patent infringement claim (excluding declaratory judgment actions)against Initial Developer or a Contributor (the Initial Developer or Contributor againstwhom You assert such claim is referred to as Participant) alleging that the ParticipantSoftware (meaning the Contributor Version where the Participant is a Contributor or theOriginal Software where the Participant is the Initial Developer) directly or indirectlyinfringes any patent, then any and all rights granted directly or indirectly to You by suchParticipant, the Initial Developer (if the Initial Developer is not the Participant) and allContributors under Sections 2.1 and/or 2.2 of this License shall, upon 60 days noticefrom Participant terminate prospectively and automatically at the expiration of such 60day notice period, unless if within such 60 day period You withdraw Your claim withrespect to the Participant Software against such Participant either unilaterally orpursuant to a written agreement with Participant.

6.3. In the event of termination under Sections 6.1 or 6.2 above, all end user licenses thathave been validly granted by You or any distributor hereunder prior to termination(excluding licenses granted to You by any distributor) shall survive termination.

7. LIMITATION OF LIABILITY.




UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER TORT(INCLUDING NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL YOU, THE INITIALDEVELOPER, ANY OTHER CONTRIBUTOR, OR ANY DISTRIBUTOR OF COVERED SOFTWARE,OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO ANY PERSON FOR ANYINDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY CHARACTERINCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOST PROFITS, LOSS OF GOODWILL,WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHERCOMMERCIAL DAMAGES OR LOSSES, EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMEDOF THE POSSIBILITY OF SUCH DAMAGES. THIS LIMITATION OF LIABILITY SHALL NOTAPPLY TO LIABILITY FOR DEATH OR PERSONAL INJURY RESULTING FROM SUCH PARTYSNEGLIGENCE TO THE EXTENT APPLICABLE LAW PROHIBITS SUCH LIMITATION. SOMEJURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF INCIDENTAL ORCONSEQUENTIAL DAMAGES, SO THIS EXCLUSION AND LIMITATION MAY NOT APPLY TOYOU.

8. U.S. GOVERNMENT END USERS.

The Covered Software is a commercial item, as that term is defined in 48 C.F.R. 2.101(Oct. 1995), consisting of commercial computer software (as that term is defined at 48C.F.R. ? 252.227-7014(a)(1)) and commercial computer software documentation as suchterms are used in 48 C.F.R. 12.212 (Sept. 1995). Consistent with 48 C.F.R. 12.212 and 48C.F.R. 227.7202-1 through 227.7202-4 (June 1995), all U.S. Government End Users acquireCovered Software with only those rights set forth herein. This U.S. Government Rightsclause is in lieu of, and supersedes, any other FAR, DFAR, or other clause or provisionthat addresses Government rights in computer software under this License.

9. MISCELLANEOUS.

This License represents the complete agreement concerning subject matter hereof. Ifany provision of this License is held to be unenforceable, such provision shall bereformed only to the extent necessary to make it enforceable. This License shall begoverned by the law of the jurisdiction specified in a notice contained within the OriginalSoftware (except to the extent applicable law, if any, provides otherwise), excluding suchjurisdictions conflict-of-law provisions. Any litigation relating to this License shall besubject to the jurisdiction of the courts located in the jurisdiction and venue specified ina notice contained within the Original Software, with the losing party responsible forcosts, including, without limitation, court costs and reasonable attorneys fees andexpenses. The application of the United Nations Convention on Contracts for theInternational Sale of Goods is expressly excluded. Any law or regulation which providesthat the language of a contract shall be construed against the drafter shall not apply tothis License. You agree that You alone are responsible for compliance with the UnitedStates export administration regulations (and the export control laws and regulation ofany other countries) when You use, distribute or otherwise make available any CoveredSoftware.

10. RESPONSIBILITY FOR CLAIMS.

As between Initial Developer and the Contributors, each party is responsible for claimsand damages arising, directly or indirectly, out of its utilization of rights under thisLicense and You agree to work with Initial Developer and Contributors to distribute suchresponsibility on an equitable basis. Nothing herein is intended or shall be deemed toconstitute any admission of liability.

NOTICE PURSUANT TO SECTION 9 OF THE COMMON DEVELOPMENT AND DISTRIBUTIONLICENSE (CDDL)




The GlassFish code released under the CDDL shall be governed by the laws of the Stateof California (excluding conflict-of-law provisions). Any litigation relating to this Licenseshall be subject to the jurisdiction of the Federal Courts of the Northern District ofCalifornia and the state courts of the State of California, with venue lying in Santa ClaraCounty, California.

javax.annotation:javax.annotation-api (1.2) andorg.glassfish.hk2:osgi-resource-locator (1.0.1)

COMMON DEVELOPMENT AND DISTRIBUTION LICENSE (CDDL) Version 1.0

1. Definitions.

1.1. "Contributor" means each individual or entity that creates or contributes to thecreation of Modifications.

1.2. "Contributor Version" means the combination of the Original Software, priorModifications used by a Contributor (if any), and the Modifications made by thatparticular Contributor.

1.3. "Covered Software" means (a) the Original Software, or (b) Modifications, or (c) thecombination of files containing Original Software with files containing Modifications, ineach case including portions thereof.

1.4. "Executable" means the Covered Software in any form other than Source Code.

1.5. "Initial Developer" means the individual or entity that first makes Original Softwareavailable under this License.

1.6. "Larger Work" means a work which combines Covered Software or portions thereofwith code not governed by the terms of this License.

1.7. "License" means this document.

1.8. "Licensable" means having the right to grant, to the maximum extent possible,whether at the time of the initial grant or subsequently acquired, any and all of the rightsconveyed herein.

1.9. "Modifications" means the Source Code and Executable form of any of the following:




1.10. "Original Software" means the Source Code and Executable form of computersoftware code that is originally released under this License.

1.11. "Patent Claims" means any patent claim(s), now owned or hereafter acquired,including without limitation, method, process, and apparatus claims, in any patentLicensable by grantor.

javax.annotation:javax.annotation-api (1.2) and org.glassfish.hk2:osgi-resource-locator (1.0.1)



1.12. "Source Code" means (a) the common form of computer software code in whichmodifications are made and (b) associated documentation included in or with such code.

1.13. "You" (or "Your") means an individual or a legal entity exercising rights under, andcomplying with all of the terms of, this License. For legal entities, "You" includes anyentity which controls, is controlled by, or is under common control with You. Forpurposes of this definition, "control" means (a) the power, direct or indirect, to cause thedirection or management of such entity, whether by contract or otherwise, or (b)ownership of more than fifty percent (50%) of the outstanding shares or beneficialownership of such entity.

2. License Grants.



















3.2. Modifications.





You may not offer or impose any terms on any Covered Software in Source Code formthat alters or restricts the applicable version of this License or the recipients’ rightshereunder. You may choose to offer, and to charge a fee for, warranty, support,indemnity or liability obligations to one or more recipients of Covered Software.However, you may do so only on Your own behalf, and not on behalf of the InitialDeveloper or any Contributor. You must make it absolutely clear that any such warranty,support, indemnity or liability obligation is offered by You alone, and You hereby agree toindemnify the Initial Developer and every Contributor for any liability incurred by theInitial Developer or such Contributor as a result of warranty, support, indemnity orliability terms You offer.





You may distribute the Executable form of the Covered Software under the terms of thisLicense or under the terms of a license of Your choice, which may contain terms differentfrom this License, provided that You are in compliance with the terms of this License andthat the license for the Executable form does not attempt to limit or alter the recipient’srights in the Source Code form from the rights set forth in this License. If You distributethe Covered Software in Executable form under a different license, You must make itabsolutely clear that any terms which differ from this License are offered by You alone,not by the Initial Developer or Contributor. You hereby agree to indemnify the InitialDeveloper and every Contributor for any liability incurred by the Initial Developer or suchContributor as a result of any such terms You offer.

3.6. Larger Works.



4.1. New Versions.

Sun Microsystems, Inc. is the initial license steward and may publish revised and/or newversions of this License from time to time. Each version will be given a distinguishingversion number. Except as provided in Section 4.3, no one other than the license stewardhas the right to modify this License.









COVERED SOFTWARE IS PROVIDED UNDER THIS LICENSE ON AN "AS IS" BASIS, WITHOUTWARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, WITHOUTLIMITATION, WARRANTIES THAT THE COVERED SOFTWARE IS FREE OF DEFECTS,MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR NON-INFRINGING. THE ENTIRERISK AS TO THE QUALITY AND PERFORMANCE OF THE COVERED SOFTWARE IS WITH YOU.SHOULD ANY COVERED SOFTWARE PROVE DEFECTIVE IN ANY RESPECT, YOU (NOT THEINITIAL DEVELOPER OR ANY OTHER CONTRIBUTOR) ASSUME THE COST OF ANYNECESSARY SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER OF WARRANTYCONSTITUTES AN ESSENTIAL PART OF THIS LICENSE. NO USE OF ANY COVEREDSOFTWARE IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER.

6. TERMINATION.


6.2. If You assert a patent infringement claim (excluding declaratory judgment actions)against Initial Developer or a Contributor (the Initial Developer or Contributor againstwhom You assert such claim is referred to as "Participant") alleging that the ParticipantSoftware (meaning the Contributor Version where the Participant is a Contributor or theOriginal Software where the Participant is the Initial Developer) directly or indirectlyinfringes any patent, then any and all rights granted directly or indirectly to You by suchParticipant, the Initial Developer (if the Initial Developer is not the Participant) and allContributors under Sections 2.1 and/or 2.2 of this License shall, upon 60 days noticefrom Participant terminate prospectively and automatically at the expiration of such 60day notice period, unless if within such 60 day period You withdraw Your claim withrespect to the Participant Software against such Participant either unilaterally orpursuant to a written agreement with Participant.



UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER TORT(INCLUDING NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL YOU, THE INITIALDEVELOPER, ANY OTHER CONTRIBUTOR, OR ANY DISTRIBUTOR OF COVERED SOFTWARE,OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO ANY PERSON FOR ANYINDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY CHARACTERINCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOST PROFITS, LOSS OF GOODWILL,WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHERCOMMERCIAL DAMAGES OR LOSSES, EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMEDOF THE POSSIBILITY OF SUCH DAMAGES. THIS LIMITATION OF LIABILITY SHALL NOTAPPLY TO LIABILITY FOR DEATH OR PERSONAL INJURY RESULTING FROM SUCH PARTY’SNEGLIGENCE TO THE EXTENT APPLICABLE LAW PROHIBITS SUCH LIMITATION. SOMEJURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF INCIDENTAL ORCONSEQUENTIAL DAMAGES, SO THIS EXCLUSION AND LIMITATION MAY NOT APPLY TOYOU.





The Covered Software is a "commercial item," as that term is defined in 48 C.F.R. 2.101(Oct. 1995), consisting of "commercial computer software" (as that term is defined at 48C.F.R. § 252.227-7014(a)(1)) and "commercial computer software documentation" as suchterms are used in 48 C.F.R. 12.212 (Sept. 1995). Consistent with 48 C.F.R. 12.212 and 48C.F.R. 227.7202-1 through 227.7202-4 (June 1995), all U.S. Government End Users acquireCovered Software with only those rights set forth herein. This U.S. Government Rightsclause is in lieu of, and supersedes, any other FAR, DFAR, or other clause or provisionthat addresses Government rights in computer software under this License.

9. MISCELLANEOUS.

This License represents the complete agreement concerning subject matter hereof. Ifany provision of this License is held to be unenforceable, such provision shall bereformed only to the extent necessary to make it enforceable. This License shall begoverned by the law of the jurisdiction specified in a notice contained within the OriginalSoftware (except to the extent applicable law, if any, provides otherwise), excluding suchjurisdiction’s conflict-of-law provisions. Any litigation relating to this License shall besubject to the jurisdiction of the courts located in the jurisdiction and venue specified ina notice contained within the Original Software, with the losing party responsible forcosts, including, without limitation, court costs and reasonable attorneys’ fees andexpenses. The application of the United Nations Convention on Contracts for theInternational Sale of Goods is expressly excluded. Any law or regulation which providesthat the language of a contract shall be construed against the drafter shall not apply tothis License. You agree that You alone are responsible for compliance with the UnitedStates export administration regulations (and the export control laws and regulation ofany other countries) when You use, distribute or otherwise make available any CoveredSoftware.




The code released under the CDDL shall be governed by the laws of the State ofCalifornia (excluding conflict-of-law provisions). Any litigation relating to this License shallbe subject to the jurisdiction of the Federal Courts of the Northern District of Californiaand the state courts of the State of California, with venue lying in Santa Clara County,California.

The GNU General Public License (GPL) Version 2, June 1991

Copyright (C) 1989, 1991 Free Software Foundation, Inc. 59 Temple Place, Suite 330,Boston, MA 02111-1307 USA

Everyone is permitted to copy and distribute verbatim copies of this license document,but changing it is not allowed.

Preamble




The licenses for most software are designed to take away your freedom to share andchange it. By contrast, the GNU General Public License is intended to guarantee yourfreedom to share and change free software--to make sure the software is free for all itsusers. This General Public License applies to most of the Free Software Foundation'ssoftware and to any other program whose authors commit to using it. (Some other FreeSoftware Foundation software is covered by the GNU Library General Public Licenseinstead.) You can apply it to your programs, too.

When we speak of free software, we are referring to freedom, not price. Our GeneralPublic Licenses are designed to make sure that you have the freedom to distributecopies of free software (and charge for this service if you wish), that you receive sourcecode or can get it if you want it, that you can change the software or use pieces of it innew free programs; and that you know you can do these things.

To protect your rights, we need to make restrictions that forbid anyone to deny youthese rights or to ask you to surrender the rights. These restrictions translate to certainresponsibilities for you if you distribute copies of the software, or if you modify it.

For example, if you distribute copies of such a program, whether gratis or for a fee, youmust give the recipients all the rights that you have. You must make sure that they, too,receive or can get the source code. And you must show them these terms so they knowtheir rights.

We protect your rights with two steps: (1) copyright the software, and (2) offer you thislicense which gives you legal permission to copy, distribute and/or modify the software.

Also, for each author's protection and ours, we want to make certain that everyoneunderstands that there is no warranty for this free software. If the software is modifiedby someone else and passed on, we want its recipients to know that what they have isnot the original, so that any problems introduced by others will not reflect on the originalauthors' reputations.

Finally, any free program is threatened constantly by software patents. We wish to avoidthe danger that redistributors of a free program will individually obtain patent licenses,in effect making the program proprietary. To prevent this, we have made it clear that anypatent must be licensed for everyone's free use or not licensed at all.

The precise terms and conditions for copying, distribution and modification follow.

TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

0. This License applies to any program or other work which contains a notice placed bythe copyright holder saying it may be distributed under the terms of this General PublicLicense. The "Program", below, refers to any such program or work, and a "work basedon the Program" means either the Program or any derivative work under copyright law:that is to say, a work containing the Program or a portion of it, either verbatim or withmodifications and/or translated into another language. (Hereinafter, translation isincluded without limitation in the term "modification".) Each licensee is addressed as"you".

Activities other than copying, distribution and modification are not covered by thisLicense; they are outside its scope. The act of running the Program is not restricted, andthe output from the Program is covered only if its contents constitute a work based onthe Program (independent of having been made by running the Program). Whether thatis true depends on what the Program does.




1. You may copy and distribute verbatim copies of the Program's source code as youreceive it, in any medium, provided that you conspicuously and appropriately publish oneach copy an appropriate copyright notice and disclaimer of warranty; keep intact all thenotices that refer to this License and to the absence of any warranty; and give any otherrecipients of the Program a copy of this License along with the Program.

You may charge a fee for the physical act of transferring a copy, and you may at youroption offer warranty protection in exchange for a fee.

2. You may modify your copy or copies of the Program or any portion of it, thus forminga work based on the Program, and copy and distribute such modifications or work underthe terms of Section 1 above, provided that you also meet all of these conditions:

a) You must cause the modified files to carry prominent notices stating that you changedthe files and the date of any change.

b) You must cause any work that you distribute or publish, that in whole or in partcontains or is derived from the Program or any part thereof, to be licensed as a whole atno charge to all third parties under the terms of this License.

c) If the modified program normally reads commands interactively when run, you mustcause it, when started running for such interactive use in the most ordinary way, to printor display an announcement including an appropriate copyright notice and a notice thatthere is no warranty (or else, saying that you provide a warranty) and that users mayredistribute the program under these conditions, and telling the user how to view a copyof this License. (Exception: if the Program itself is interactive but does not normally printsuch an announcement, your work based on the Program is not required to print anannouncement.)

These requirements apply to the modified work as a whole. If identifiable sections of thatwork are not derived from the Program, and can be reasonably considered independentand separate works in themselves, then this License, and its terms, do not apply to thosesections when you distribute them as separate works. But when you distribute the samesections as part of a whole which is a work based on the Program, the distribution of thewhole must be on the terms of this License, whose permissions for other licenseesextend to the entire whole, and thus to each and every part regardless of who wrote it.

Thus, it is not the intent of this section to claim rights or contest your rights to workwritten entirely by you; rather, the intent is to exercise the right to control thedistribution of derivative or collective works based on the Program.

In addition, mere aggregation of another work not based on the Program with theProgram (or with a work based on the Program) on a volume of a storage or distributionmedium does not bring the other work under the scope of this License.

3. You may copy and distribute the Program (or a work based on it, under Section 2) inobject code or executable form under the terms of Sections 1 and 2 above provided thatyou also do one of the following:

a) Accompany it with the complete corresponding machine-readable source code, whichmust be distributed under the terms of Sections 1 and 2 above on a medium customarilyused for software interchange; or,




b) Accompany it with a written offer, valid for at least three years, to give any third party,for a charge no more than your cost of physically performing source distribution, acomplete machine-readable copy of the corresponding source code, to be distributedunder the terms of Sections 1 and 2 above on a medium customarily used for softwareinterchange; or,

c) Accompany it with the information you received as to the offer to distributecorresponding source code. (This alternative is allowed only for noncommercialdistribution and only if you received the program in object code or executable form withsuch an offer, in accord with Subsection b above.)

The source code for a work means the preferred form of the work for makingmodifications to it. For an executable work, complete source code means all the sourcecode for all modules it contains, plus any associated interface definition files, plus thescripts used to control compilation and installation of the executable. However, as aspecial exception, the source code distributed need not include anything that is normallydistributed (in either source or binary form) with the major components (compiler,kernel, and so on) of the operating system on which the executable runs, unless thatcomponent itself accompanies the executable.

If distribution of executable or object code is made by offering access to copy from adesignated place, then offering equivalent access to copy the source code from the sameplace counts as distribution of the source code, even though third parties are notcompelled to copy the source along with the object code.

4. You may not copy, modify, sublicense, or distribute the Program except as expresslyprovided under this License. Any attempt otherwise to copy, modify, sublicense ordistribute the Program is void, and will automatically terminate your rights under thisLicense. However, parties who have received copies, or rights, from you under thisLicense will not have their licenses terminated so long as such parties remain in fullcompliance.

5. You are not required to accept this License, since you have not signed it. However,nothing else grants you permission to modify or distribute the Program or its derivativeworks. These actions are prohibited by law if you do not accept this License. Therefore,by modifying or distributing the Program (or any work based on the Program), youindicate your acceptance of this License to do so, and all its terms and conditions forcopying, distributing or modifying the Program or works based on it.

6. Each time you redistribute the Program (or any work based on the Program), therecipient automatically receives a license from the original licensor to copy, distribute ormodify the Program subject to these terms and conditions. You may not impose anyfurther restrictions on the recipients' exercise of the rights granted herein. You are notresponsible for enforcing compliance by third parties to this License.

7. If, as a consequence of a court judgment or allegation of patent infringement or forany other reason (not limited to patent issues), conditions are imposed on you (whetherby court order, agreement or otherwise) that contradict the conditions of this License,they do not excuse you from the conditions of this License. If you cannot distribute so asto satisfy simultaneously your obligations under this License and any other pertinentobligations, then as a consequence you may not distribute the Program at all. Forexample, if a patent license would not permit royalty-free redistribution of the Programby all those who receive copies directly or indirectly through you, then the only way youcould satisfy both it and this License would be to refrain entirely from distribution of theProgram.




If any portion of this section is held invalid or unenforceable under any particularcircumstance, the balance of the section is intended to apply and the section as a wholeis intended to apply in other circumstances.

It is not the purpose of this section to induce you to infringe any patents or otherproperty right claims or to contest validity of any such claims; this section has the solepurpose of protecting the integrity of the free software distribution system, which isimplemented by public license practices. Many people have made generouscontributions to the wide range of software distributed through that system in relianceon consistent application of that system; it is up to the author/donor to decide if he orshe is willing to distribute software through any other system and a licensee cannotimpose that choice.

This section is intended to make thoroughly clear what is believed to be a consequenceof the rest of this License.

8. If the distribution and/or use of the Program is restricted in certain countries either bypatents or by copyrighted interfaces, the original copyright holder who places theProgram under this License may add an explicit geographical distribution limitationexcluding those countries, so that distribution is permitted only in or among countriesnot thus excluded. In such case, this License incorporates the limitation as if written inthe body of this License.

9. The Free Software Foundation may publish revised and/or new versions of the GeneralPublic License from time to time. Such new versions will be similar in spirit to the presentversion, but may differ in detail to address new problems or concerns.

Each version is given a distinguishing version number. If the Program specifies a versionnumber of this License which applies to it and "any later version", you have the option offollowing the terms and conditions either of that version or of any later versionpublished by the Free Software Foundation. If the Program does not specify a versionnumber of this License, you may choose any version ever published by the Free SoftwareFoundation.

10. If you wish to incorporate parts of the Program into other free programs whosedistribution conditions are different, write to the author to ask for permission. Forsoftware which is copyrighted by the Free Software Foundation, write to the FreeSoftware Foundation; we sometimes make exceptions for this. Our decision will beguided by the two goals of preserving the free status of all derivatives of our freesoftware and of promoting the sharing and reuse of software generally.

NO WARRANTY

11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTYFOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHENOTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIESPROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSEDOR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OFMERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TOTHE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THEPROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,REPAIR OR CORRECTION.




12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITINGWILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/ORREDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGESARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOTLIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSESSUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATEWITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEENADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

END OF TERMS AND CONDITIONS

How to Apply These Terms to Your New Programs

If you develop a new program, and you want it to be of the greatest possible use to thepublic, the best way to achieve this is to make it free software which everyone canredistribute and change under these terms.

To do so, attach the following notices to the program. It is safest to attach them to thestart of each source file to most effectively convey the exclusion of warranty; and eachfile should have at least the "copyright" line and a pointer to where the full notice isfound.

One line to give the program's name and a brief idea of what it does.

Copyright (C)

This program is free software; you can redistribute it and/or modify it under the terms ofthe GNU General Public License as published by the Free Software Foundation; eitherversion 2 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANYWARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR APARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with thisprogram; if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330,Boston, MA 02111-1307 USA

Also add information on how to contact you by electronic and paper mail.

If the program is interactive, make it output a short notice like this when it starts in aninteractive mode:

Gnomovision version 69, Copyright (C) year name of author

Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type 'show w'. This isfree software, and you are welcome to redistribute it under certain conditions; type'show c' for details.

The hypothetical commands 'show w' and 'show c' should show the appropriate parts ofthe General Public License. Of course, the commands you use may be called somethingother than 'show w' and 'show c'; they could even be mouse-clicks or menu items--whatever suits your program.

You should also get your employer (if you work as a programmer) or your school, if any,to sign a "copyright disclaimer" for the program, if necessary. Here is a sample; alter thenames:




Yoyodyne, Inc., hereby disclaims all copyright interest in the program 'Gnomovision'(which makes passes at compilers) written by James Hacker.

signature of Ty Coon, 1 April 1989

Ty Coon, President of Vice

This General Public License does not permit incorporating your program into proprietaryprograms. If your program is a subroutine library, you may consider it more useful topermit linking proprietary applications with the library. If this is what you want to do, usethe GNU Library General Public License instead of this License.

"CLASSPATH" EXCEPTION TO THE GPL VERSION 2

Certain source files distributed by Sun Microsystems, Inc. are subject to the followingclarification and special exception to the GPL Version 2, but only where Sun has expresslyincluded in the particular source file's header the words "Sun designates this particularfile as subject to the "Classpath" exception as provided by Sun in the License file thataccompanied this code."

Linking this library statically or dynamically with other modules is making a combinedwork based on this library. Thus, the terms and conditions of the GNU General PublicLicense Version 2 cover the whole combination.

As a special exception, the copyright holders of this library give you permission to linkthis library with independent modules to produce an executable, regardless of thelicense terms of these independent modules, and to copy and distribute the resultingexecutable under terms of your choice, provided that you also meet, for each linkedindependent module, the terms and conditions of the license of that module.? Anindependent module is a module which is not derived from or based on this library.? Ifyou modify this library, you may extend this exception to your version of the library, butyou are not obligated to do so.? If you do not wish to do so, delete this exceptionstatement from your version.

javax.ws.rs:javax.ws.rs-api (2.0.1)

COMMON DEVELOPMENT AND DISTRIBUTION LICENSE (CDDL)Version 1.1

1. Definitions.

1.1. "Contributor" means each individual or entity that creates or contributes to thecreation of Modifications.

1.2. "Contributor Version" means the combination of the Original Software, priorModifications used by a Contributor (if any), and the Modifications made by thatparticular Contributor.

1.3. "Covered Software" means (a) the Original Software, or (b) Modifications, or (c) thecombination of files containing Original Software with files containing Modifications, ineach case including portions thereof.

1.4. "Executable" means the Covered Software in any form other than Source Code.

1.5. "Initial Developer" means the individual or entity that first makes Original Softwareavailable under this License.




1.6. "Larger Work" means a work which combines Covered Software or portions thereofwith code not governed by the terms of this License.

1.7. "License" means this document.

1.8. "Licensable" means having the right to grant, to the maximum extent possible,whether at the time of the initial grant or subsequently acquired, any and all of the rightsconveyed herein.

1.9. "Modifications" means the Source Code and Executable form of any of the following:




1.10. "Original Software" means the Source Code and Executable form of computersoftware code that is originally released under this License.

1.11. "Patent Claims" means any patent claim(s), now owned or hereafter acquired,including without limitation, method, process, and apparatus claims, in any patentLicensable by grantor.

1.12. "Source Code" means (a) the common form of computer software code in whichmodifications are made and (b) associated documentation included in or with such code.

1.13. "You" (or "Your") means an individual or a legal entity exercising rights under, andcomplying with all of the terms of, this License. For legal entities, "You" includes anyentity which controls, is controlled by, or is under common control with You. Forpurposes of this definition, "control" means (a) the power, direct or indirect, to cause thedirection or management of such entity, whether by contract or otherwise, or (b)ownership of more than fifty percent (50%) of the outstanding shares or beneficialownership of such entity.

2. License Grants.



















3.2. Modifications.








You may not offer or impose any terms on any Covered Software in Source Code formthat alters or restricts the applicable version of this License or the recipients' rightshereunder. You may choose to offer, and to charge a fee for, warranty, support,indemnity or liability obligations to one or more recipients of Covered Software.However, you may do so only on Your own behalf, and not on behalf of the InitialDeveloper or any Contributor. You must make it absolutely clear that any such warranty,support, indemnity or liability obligation is offered by You alone, and You hereby agree toindemnify the Initial Developer and every Contributor for any liability incurred by theInitial Developer or such Contributor as a result of warranty, support, indemnity orliability terms You offer.


You may distribute the Executable form of the Covered Software under the terms of thisLicense or under the terms of a license of Your choice, which may contain terms differentfrom this License, provided that You are in compliance with the terms of this License andthat the license for the Executable form does not attempt to limit or alter the recipient'srights in the Source Code form from the rights set forth in this License. If You distributethe Covered Software in Executable form under a different license, You must make itabsolutely clear that any terms which differ from this License are offered by You alone,not by the Initial Developer or Contributor. You hereby agree to indemnify the InitialDeveloper and every Contributor for any liability incurred by the Initial Developer or suchContributor as a result of any such terms You offer.

3.6. Larger Works.



4.1. New Versions.

Oracle is the initial license steward and may publish revised and/or new versions of thisLicense from time to time. Each version will be given a distinguishing version number.Except as provided in Section 4.3, no one other than the license steward has the right tomodify this License.









COVERED SOFTWARE IS PROVIDED UNDER THIS LICENSE ON AN "AS IS" BASIS, WITHOUTWARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, WITHOUTLIMITATION, WARRANTIES THAT THE COVERED SOFTWARE IS FREE OF DEFECTS,MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR NON-INFRINGING. THE ENTIRERISK AS TO THE QUALITY AND PERFORMANCE OF THE COVERED SOFTWARE IS WITH YOU.SHOULD ANY COVERED SOFTWARE PROVE DEFECTIVE IN ANY RESPECT, YOU (NOT THEINITIAL DEVELOPER OR ANY OTHER CONTRIBUTOR) ASSUME THE COST OF ANYNECESSARY SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER OF WARRANTYCONSTITUTES AN ESSENTIAL PART OF THIS LICENSE. NO USE OF ANY COVEREDSOFTWARE IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER.

6. TERMINATION.


6.2. If You assert a patent infringement claim (excluding declaratory judgment actions)against Initial Developer or a Contributor (the Initial Developer or Contributor againstwhom You assert such claim is referred to as "Participant") alleging that the ParticipantSoftware (meaning the Contributor Version where the Participant is a Contributor or theOriginal Software where the Participant is the Initial Developer) directly or indirectlyinfringes any patent, then any and all rights granted directly or indirectly to You by suchParticipant, the Initial Developer (if the Initial Developer is not the Participant) and allContributors under Sections 2.1 and/or 2.2 of this License shall, upon 60 days noticefrom Participant terminate prospectively and automatically at the expiration of such 60day notice period, unless if within such 60 day period You withdraw Your claim withrespect to the Participant Software against such Participant either unilaterally orpursuant to a written agreement with Participant.




6.3. If You assert a patent infringement claim against Participant alleging that theParticipant Software directly or indirectly infringes any patent where such claim isresolved (such as by license or settlement) prior to the initiation of patent infringementlitigation, then the reasonable value of the licenses granted by such Participant underSections 2.1 or 2.2 shall be taken into account in determining the amount or value of anypayment or license.



UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER TORT(INCLUDING NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL YOU, THE INITIALDEVELOPER, ANY OTHER CONTRIBUTOR, OR ANY DISTRIBUTOR OF COVERED SOFTWARE,OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO ANY PERSON FOR ANYINDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY CHARACTERINCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL, WORKSTOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHERCOMMERCIAL DAMAGES OR LOSSES, EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMEDOF THE POSSIBILITY OF SUCH DAMAGES. THIS LIMITATION OF LIABILITY SHALL NOTAPPLY TO LIABILITY FOR DEATH OR PERSONAL INJURY RESULTING FROM SUCH PARTY'SNEGLIGENCE TO THE EXTENT APPLICABLE LAW PROHIBITS SUCH LIMITATION. SOMEJURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF INCIDENTAL ORCONSEQUENTIAL DAMAGES, SO THIS EXCLUSION AND LIMITATION MAY NOT APPLY TOYOU.


The Covered Software is a "commercial item," as that term is defined in 48 C.F.R. 2.101(Oct. 1995), consisting of "commercial computer software" (as that term is defined at 48C.F.R. § 252.227-7014(a)(1)) and "commercial computer software documentation" as suchterms are used in 48 C.F.R. 12.212 (Sept. 1995). Consistent with 48 C.F.R. 12.212 and 48C.F.R. 227.7202-1 through 227.7202-4 (June 1995), all U.S. Government End Users acquireCovered Software with only those rights set forth herein. This U.S. Government Rightsclause is in lieu of, and supersedes, any other FAR, DFAR, or other clause or provisionthat addresses Government rights in computer software under this License.

9. MISCELLANEOUS.




This License represents the complete agreement concerning subject matter hereof. Ifany provision of this License is held to be unenforceable, such provision shall bereformed only to the extent necessary to make it enforceable. This License shall begoverned by the law of the jurisdiction specified in a notice contained within the OriginalSoftware (except to the extent applicable law, if any, provides otherwise), excluding suchjurisdiction's conflict-of-law provisions. Any litigation relating to this License shall besubject to the jurisdiction of the courts located in the jurisdiction and venue specified ina notice contained within the Original Software, with the losing party responsible forcosts, including, without limitation, court costs and reasonable attorneys' fees andexpenses. The application of the United Nations Convention on Contracts for theInternational Sale of Goods is expressly excluded. Any law or regulation which providesthat the language of a contract shall be construed against the drafter shall not apply tothis License. You agree that You alone are responsible for compliance with the UnitedStates export administration regulations (and the export control laws and regulation ofany other countries) when You use, distribute or otherwise make available any CoveredSoftware.




The code released under the CDDL shall be governed by the laws of the State ofCalifornia (excluding conflict-of-law provisions). Any litigation relating to this License shallbe subject to the jurisdiction of the Federal Courts of the Northern District of Californiaand the state courts of the State of California, with venue lying in Santa Clara County,California.

The GNU General Public License (GPL) Version 2, June 1991

Copyright (C) 1989, 1991 Free Software Foundation, Inc.

59 Temple Place, Suite 330, Boston, MA 02111-1307 USA

Everyone is permitted to copy and distribute verbatim copies

of this license document, but changing it is not allowed.

Preamble

The licenses for most software are designed to take away your freedom to share andchange it. By contrast, the GNU General Public License is intended to guarantee yourfreedom to share and change free software--to make sure the software is free for all itsusers. This General Public License applies to most of the Free Software Foundation'ssoftware and to any other program whose authors commit to using it. (Some other FreeSoftware Foundation software is covered by the GNU Library General Public Licenseinstead.) You can apply it to your programs, too.




When we speak of free software, we are referring to freedom, not price. Our GeneralPublic Licenses are designed to make sure that you have the freedom to distributecopies of free software (and charge for this service if you wish), that you receive sourcecode or can get it if you want it, that you can change the software or use pieces of it innew free programs; and that you know you can do these things.

To protect your rights, we need to make restrictions that forbid anyone to deny youthese rights or to ask you to surrender the rights. These restrictions translate to certainresponsibilities for you if you distribute copies of the software, or if you modify it.

For example, if you distribute copies of such a program, whether gratis or for a fee, youmust give the recipients all the rights that you have. You must make sure that they, too,receive or can get the source code. And you must show them these terms so they knowtheir rights.

We protect your rights with two steps: (1) copyright the software, and (2) offer you thislicense which gives you legal permission to copy, distribute and/or modify the software.

Also, for each author's protection and ours, we want to make certain that everyoneunderstands that there is no warranty for this free software. If the software is modifiedby someone else and passed on, we want its recipients to know that what they have isnot the original, so that any problems introduced by others will not reflect on the originalauthors' reputations.

Finally, any free program is threatened constantly by software patents. We wish to avoidthe danger that redistributors of a free program will individually obtain patent licenses,in effect making the program proprietary. To prevent this, we have made it clear that anypatent must be licensed for everyone's free use or not licensed at all.

The precise terms and conditions for copying, distribution and modification follow.

TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

0. This License applies to any program or other work which contains a notice placed bythe copyright holder saying it may be distributed under the terms of this General PublicLicense. The "Program", below, refers to any such program or work, and a "work basedon the Program" means either the Program or any derivative work under copyright law:that is to say, a work containing the Program or a portion of it, either verbatim or withmodifications and/or translated into another language. (Hereinafter, translation isincluded without limitation in the term "modification".) Each licensee is addressed as"you".

Activities other than copying, distribution and modification are not covered by thisLicense; they are outside its scope. The act of running the Program is not restricted, andthe output from the Program is covered only if its contents constitute a work based onthe Program (independent of having been made by running the Program). Whether thatis true depends on what the Program does.

1. You may copy and distribute verbatim copies of the Program's source code as youreceive it, in any medium, provided that you conspicuously and appropriately publish oneach copy an appropriate copyright notice and disclaimer of warranty; keep intact all thenotices that refer to this License and to the absence of any warranty; and give any otherrecipients of the Program a copy of this License along with the Program.

You may charge a fee for the physical act of transferring a copy, and you may at youroption offer warranty protection in exchange for a fee.




2. You may modify your copy or copies of the Program or any portion of it, thus forminga work based on the Program, and copy and distribute such modifications or work underthe terms of Section 1 above, provided that you also meet all of these conditions:

a) You must cause the modified files to carry prominent notices stating that you changedthe files and the date of any change.

b) You must cause any work that you distribute or publish, that in whole or in partcontains or is derived from the Program or any part thereof, to be licensed as a whole atno charge to all third parties under the terms of this License.

c) If the modified program normally reads commands interactively when run, you mustcause it, when started running for such interactive use in the most ordinary way, to printor display an announcement including an appropriate copyright notice and a notice thatthere is no warranty (or else, saying that you provide a warranty) and that users mayredistribute the program under these conditions, and telling the user how to view a copyof this License. (Exception: if the Program itself is interactive but does not normally printsuch an announcement, your work based on the Program is not required to print anannouncement.)

These requirements apply to the modified work as a whole. If identifiable sections of thatwork are not derived from the Program, and can be reasonably considered independentand separate works in themselves, then this License, and its terms, do not apply to thosesections when you distribute them as separate works. But when you distribute the samesections as part of a whole which is a work based on the Program, the distribution of thewhole must be on the terms of this License, whose permissions for other licenseesextend to the entire whole, and thus to each and every part regardless of who wrote it.

Thus, it is not the intent of this section to claim rights or contest your rights to workwritten entirely by you; rather, the intent is to exercise the right to control thedistribution of derivative or collective works based on the Program.

In addition, mere aggregation of another work not based on the Program with theProgram (or with a work based on the Program) on a volume of a storage or distributionmedium does not bring the other work under the scope of this License.

3. You may copy and distribute the Program (or a work based on it, under Section 2) inobject code or executable form under the terms of Sections 1 and 2 above provided thatyou also do one of the following:

a) Accompany it with the complete corresponding machine-readable source code, whichmust be distributed under the terms of Sections 1 and 2 above on a medium customarilyused for software interchange; or,

b) Accompany it with a written offer, valid for at least three years, to give any third party,for a charge no more than your cost of physically performing source distribution, acomplete machine-readable copy of the corresponding source code, to be distributedunder the terms of Sections 1 and 2 above on a medium customarily used for softwareinterchange; or,

c) Accompany it with the information you received as to the offer to distributecorresponding source code. (This alternative is allowed only for noncommercialdistribution and only if you received the program in object code or executable form withsuch an offer, in accord with Subsection b above.)




The source code for a work means the preferred form of the work for makingmodifications to it. For an executable work, complete source code means all the sourcecode for all modules it contains, plus any associated interface definition files, plus thescripts used to control compilation and installation of the executable. However, as aspecial exception, the source code distributed need not include anything that is normallydistributed (in either source or binary form) with the major components (compiler,kernel, and so on) of the operating system on which the executable runs, unless thatcomponent itself accompanies the executable.

If distribution of executable or object code is made by offering access to copy from adesignated place, then offering equivalent access to copy the source code from the sameplace counts as distribution of the source code, even though third parties are notcompelled to copy the source along with the object code.

4. You may not copy, modify, sublicense, or distribute the Program except as expresslyprovided under this License. Any attempt otherwise to copy, modify, sublicense ordistribute the Program is void, and will automatically terminate your rights under thisLicense. However, parties who have received copies, or rights, from you under thisLicense will not have their licenses terminated so long as such parties remain in fullcompliance.

5. You are not required to accept this License, since you have not signed it. However,nothing else grants you permission to modify or distribute the Program or its derivativeworks. These actions are prohibited by law if you do not accept this License. Therefore,by modifying or distributing the Program (or any work based on the Program), youindicate your acceptance of this License to do so, and all its terms and conditions forcopying, distributing or modifying the Program or works based on it.

6. Each time you redistribute the Program (or any work based on the Program), therecipient automatically receives a license from the original licensor to copy, distribute ormodify the Program subject to these terms and conditions. You may not impose anyfurther restrictions on the recipients' exercise of the rights granted herein. You are notresponsible for enforcing compliance by third parties to this License.

7. If, as a consequence of a court judgment or allegation of patent infringement or forany other reason (not limited to patent issues), conditions are imposed on you (whetherby court order, agreement or otherwise) that contradict the conditions of this License,they do not excuse you from the conditions of this License. If you cannot distribute so asto satisfy simultaneously your obligations under this License and any other pertinentobligations, then as a consequence you may not distribute the Program at all. Forexample, if a patent license would not permit royalty-free redistribution of the Programby all those who receive copies directly or indirectly through you, then the only way youcould satisfy both it and this License would be to refrain entirely from distribution of theProgram.

If any portion of this section is held invalid or unenforceable under any particularcircumstance, the balance of the section is intended to apply and the section as a wholeis intended to apply in other circumstances.




It is not the purpose of this section to induce you to infringe any patents or otherproperty right claims or to contest validity of any such claims; this section has the solepurpose of protecting the integrity of the free software distribution system, which isimplemented by public license practices. Many people have made generouscontributions to the wide range of software distributed through that system in relianceon consistent application of that system; it is up to the author/donor to decide if he orshe is willing to distribute software through any other system and a licensee cannotimpose that choice.

This section is intended to make thoroughly clear what is believed to be a consequenceof the rest of this License.

8. If the distribution and/or use of the Program is restricted in certain countries either bypatents or by copyrighted interfaces, the original copyright holder who places theProgram under this License may add an explicit geographical distribution limitationexcluding those countries, so that distribution is permitted only in or among countriesnot thus excluded. In such case, this License incorporates the limitation as if written inthe body of this License.

9. The Free Software Foundation may publish revised and/or new versions of the GeneralPublic License from time to time. Such new versions will be similar in spirit to the presentversion, but may differ in detail to address new problems or concerns.

Each version is given a distinguishing version number. If the Program specifies a versionnumber of this License which applies to it and "any later version", you have the option offollowing the terms and conditions either of that version or of any later versionpublished by the Free Software Foundation. If the Program does not specify a versionnumber of this License, you may choose any version ever published by the Free SoftwareFoundation.

10. If you wish to incorporate parts of the Program into other free programs whosedistribution conditions are different, write to the author to ask for permission. Forsoftware which is copyrighted by the Free Software Foundation, write to the FreeSoftware Foundation; we sometimes make exceptions for this. Our decision will beguided by the two goals of preserving the free status of all derivatives of our freesoftware and of promoting the sharing and reuse of software generally.

NO WARRANTY

11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTYFOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHENOTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIESPROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSEDOR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OFMERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TOTHE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THEPROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,REPAIR OR CORRECTION.




12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITINGWILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/ORREDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGESARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOTLIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSESSUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATEWITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEENADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

END OF TERMS AND CONDITIONS

How to Apply These Terms to Your New Programs

If you develop a new program, and you want it to be of the greatest possible use to thepublic, the best way to achieve this is to make it free software which everyone canredistribute and change under these terms.

To do so, attach the following notices to the program. It is safest to attach them to thestart of each source file to most effectively convey the exclusion of warranty; and eachfile should have at least the "copyright" line and a pointer to where the full notice isfound.

One line to give the program's name and a brief idea of what it does.

Copyright (C) <year> <name of author>

This program is free software; you can redistribute it and/or modify it under the terms ofthe GNU General Public License as published by the Free Software Foundation; eitherversion 2 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANYWARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR APARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with thisprogram; if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330,Boston, MA 02111-1307 USA

Also add information on how to contact you by electronic and paper mail.

If the program is interactive, make it output a short notice like this when it starts in aninteractive mode:

Gnomovision version 69, Copyright (C) year name of author Gnomovision comes withABSOLUTELY NO WARRANTY; for details type 'show w'. This is free software, and you arewelcome to redistribute it under certain conditions; type 'show c' for details.

The hypothetical commands 'show w' and 'show c' should show the appropriate parts ofthe General Public License. Of course, the commands you use may be called somethingother than 'show w' and 'show c'; they could even be mouse-clicks or menu items--whatever suits your program.

You should also get your employer (if you work as a programmer) or your school, if any,to sign a "copyright disclaimer" for the program, if necessary. Here is a sample; alter thenames:

Yoyodyne, Inc., hereby disclaims all copyright interest in the program 'Gnomovision'(which makes passes at compilers) written by James Hacker.




signature of Ty Coon, 1 April 1989

Ty Coon, President of Vice

This General Public License does not permit incorporating your program into proprietaryprograms. If your program is a subroutine library, you may consider it more useful topermit linking proprietary applications with the library. If this is what you want to do, usethe GNU Library General Public License instead of this License.

•"CLASSPATH" EXCEPTION TO THE GPL VERSION 2

Certain source files distributed by Oracle are subject to the following clarification andspecial exception to the GPL Version 2, but only where Oracle has expressly included inthe particular source file's header the words "Oracle designates this particular file assubject to the "Classpath" exception as provided by Oracle in the License file thataccompanied this code."

Linking this library statically or dynamically with other modules is making a combinedwork based on this library. Thus, the terms and conditions of the GNU General PublicLicense Version 2 cover the whole combination.

As a special exception, the copyright holders of this library give you permission to linkthis library with independent modules to produce an executable, regardless of thelicense terms of these independent modules, and to copy and distribute the resultingexecutable under terms of your choice, provided that you also meet, for each linkedindependent module, the terms and conditions of the license of that module. Anindependent module is a module which is not derived from or based on this library. Ifyou modify this library, you may extend this exception to your version of the library, butyou are not obligated to do so. If you do not wish to do so, delete this exceptionstatement from your version.


Bundle-License: https://glassfish.java.net/nonav/public/CDDL+GPL_1_1.html

Bundle-Description: ServiceLocator Default Implementation

org.glassfish.hk2:hk2-api (2.5.0-b30)


Bundle-Description: HK2 API module

org.glassfish.hk2:hk2-utils (2.5.0-b30)


Bundle-Description: HK2 Implementation Utilities




https://glassfish.java.net/nonav/public/CDDL+GPL_1_1.html





Bundle-Description: Dependency Injection Kernel

org.glassfish.hk2.external:javax.inject (2.5.0-b30)


Bundle-Description: Injection API ( JSR 330) version ${javax.inject.version} repackaged asOSGi bundle

org.glassfish.jersey.bundles.repackaged:jersey-guava

Bundle-Description: Jersey Guava Repackaged

Bundle-DocURL: http://www.oracle.com/

Bundle-License: http://glassfish.java.net/public/CDDL+GPL_1_1.html

org.glassfish.jersey.core:jersey-client

Bundle-Description: Jersey core client implementation



org.glassfish.jersey.core:jersey-common

Bundle-Description: Jersey core common packages



org.glassfish.jersey.media:jersey-media-jaxb

Bundle-Description: JAX-RS features based upon JAX-B.








http://www.oracle.com/

http://glassfish.java.net/public/CDDL+GPL_1_1.html







VMware® vSphere Software Development Kit LicenseAgreement

VMware® vSphere Software Development Kit License Agreement

VMware, Inc. ("VMware") provides the VMware vSphere Software Development Kit(collectively the "Software") to you subject to the following terms and conditions.By downloading, installing, or using the Software, you (the individual or legalentity) agree to be bound by the terms of this license agreement (the"Agreement"). If you disagree with any of the following terms, then do not use theSoftware.

1. The Software contains a variety of materials, interface definitions, documentation,sample utility applications and sample code regarding programming interfaces to one ormore VMware products that are referenced in such materials (the referenced products,"VMware Products"). This Software is intended to be used to develop software thatinteracts with the VMware Products.

2. Use Rights: Subject to the restrictions below, you may download and make areasonable number of copies of the Software for your use solely for the purpose ofcreating software that communicates with VMware Products (your software, "DeveloperSoftware"). Some code may be designated as "distributable code" and/or "modifiablecode" at http://www.vmware.com/go/vwssdk-redistribution-info . You may use andmerge all or portions of the "distributable code" with your Developer Software. Anymerged portion of any "distributable code" is subject to this Agreement. Additionally, youmay modify or create derivative works of all or portions of the "modifiable code." You arepermitted to re-distribute the "distributable code" and the modified or derivative worksof the "modifiable code" only as part of your Developer Software for non-commercial orcommercial use; provided that you shall only distribute such code subject to a licenseagreement that protects VMware's and its licensors' interests consistent with the termscontained in this Agreement. Open source software components provided with theSoftware are licensed to you under the terms of the applicable license agreementsincluded with such open source software components. The open source softwarelicenses can be found in the open_source_licenses.txt file, other materials accompanyingthe Software, the documentation or corresponding source files available at http://www.vmware.com/download/open_source.html.




http://www.vmware.com/go/vwssdk-redistribution-info

http://www.vmware.com/download/open_source.html

http://www.vmware.com/download/open_source.html

3. Restrictions: You agree that you will not (1) use the Software to create, design ordevelop anything other than Developer Software; (2) make any more copies of theSoftware than are reasonably necessary for the authorized use and backup and archivalpurposes; (3) modify, create derivative works of, reverse engineer, reverse compile, ordisassemble the Software except as expressly permitted in Section 2; (4) distribute, sell,lease, rent, lend, or sublicense any part of the Software to any third party except asexpressly permitted in Section 2; or (5) use the Software in any manner to (a) circumventany technical restrictions of VMware Products or violate any additional licensing termsapplicable to VMware Products that VMware provides through product documentation,email notification on the VMware website or in the terms of the End User LicenseAgreements; (b) disable, remove, over-ride or modify the display of any VMware ProductEnd User License Agreements that the VMware Products present to the end customers;or (c) upload or otherwise transmit any material containing software viruses or othercomputer code, files or programs designed to interrupt, destroy, or limit the functionalityof any software or hardware.

The restrictions in this Section 3 shall not apply if and to the extent they contradictmandatory local law (including, but not limited to, law implementing the EC SoftwareDirective).

4. VMware retains ownership of the Software and all intellectual property rightsembodied in the Software, including without limitation all copyrights, trade secrets andpatents. You may not remove, delete or modify any of VMware copyright statements inthe Software. ALL RIGHTS NOT EXPRESSLY GRANTED HEREUNDER ARE RESERVED TOVMWARE.

5. You may not use VMware's name, trademarks or service marks in connection withyour Developer Software in a way that suggests your Developer Software is certified orendorsed by VMware.

6. You are not entitled under this Agreement to receive any VMware support orsubscription services for the Software or any other services from VMware in connectionwith the Software. If you have purchased support and/or subscription services for aVMware product, such support and/or subscription services shall not apply to theSoftware or your use of the Software.

7. Term, Termination and Changes: This Agreement shall continue as long as you are incompliance with the terms specified herein or until otherwise terminated. You orVMware each may terminate this Agreement for any reason at any time. You agree, upontermination, to destroy all copies of the Software within your possession or control. TheConfidential Information, Limitations of Warranties and Liability, and Indemnificationsections set out in this Agreement shall survive any termination or expiration of thisAgreement.




8. Confidential Information: "Confidential Information" means any informationdisclosed by VMware to you pursuant to this Agreement that is marked "Confidential,""Proprietary," or in some similar manner and any information which you knew orreasonably should have known to be confidential. You shall treat as confidential allConfidential Information of VMware and shall not use such Confidential Informationexcept to exercise your rights or perform your obligations under this Agreement. You willprotect Confidential Information from unauthorized use, access, or disclosure in thesame manner as you protect your own confidential or proprietary information of asimilar nature but with no less than reasonable care. You shall not disclose suchConfidential Information to any third party during or after the term of this Agreement.This paragraph will not apply to any Confidential Information that: (a) was rightfully inyour possession prior to receipt of such Confidential Information from VMware; (b) is orbecomes a matter of public knowledge through no fault of you; (c) is rightfully receivedfrom a third party without a duty of confidentiality; (d) is independently developed byyou without breach of any confidentiality obligations; (e) is disclosed by you withVMware's prior written approval; or (f) you are required to disclose by applicable law orcourt order, provided that you notify VMware of such required disclosure promptly inwriting and cooperate with VMware in any lawful action to contest or limit the scope ofsuch required disclosure. You acknowledge that breach of this Section 8 will causeirreparable damage to VMware for which monetary damages will be an inadequateremedy. Accordingly, VMware will be entitled to seek and obtain injunctive and any otherrelief (legal or equitable) to restrain any breach or anticipated breach of this Section 8.

9. Limitations of Warranties and Liability: THE SOFTWARE IS PROVIDED "AS IS"WITHOUT ANY WARRANTIES OF ANY KIND. TO THE MAXIMUM EXTENT PERMITTED BYAPPLICABLE LAW, VMWARE DISCLAIMS ANY IMPLIED WARRANTIES, INCLUDING,WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR APARTICULAR PURPOSE AND NON-INFRINGEMENT OF INTELLECTUAL PROPERTY RIGHTS.

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT WILL VMWAREBE LIABLE FOR ANY LOST PROFITS OR BUSINESS OPPORTUNITIES, LOSS OF USE,BUSINESS INTERRUPTION, LOSS OF DATA, OR ANY OTHER INDIRECT, SPECIAL,INCIDENTAL, OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE SOFTWARE OR YOURUSE OF THE SOFTWARE, UNDER ANY THEORY OF LIABILITY, WHETHER BASED INCONTRACT, TORT, NEGLIGENCE, PRODUCT LIABILITY, OR OTHERWISE. BECAUSE SOMEJURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FORCONSEQUENTIAL OR INCIDENTAL DAMAGES, THE PRECEDING LIMITATION MAY NOTAPPLY TO YOU.

VMWARE'S LIABILITY ARISING OUT OF THIS AGREEMENT AND THE SOFTWARE PROVIDEDHEREUNDER WILL NOT, IN ANY EVENT, EXCEED US$100.00.

THE FOREGOING LIMITATIONS SHALL APPLY TO THE MAXIMUM EXTENT PERMITTED BYAPPLICABLE LAW, REGARDLESS OF WHETHER VMWARE HAS BEEN ADVISED OF THEPOSSIBILITY OF SUCH DAMAGES AND REGARDLESS OF WHETHER ANY REMEDY FAILS OFITS ESSENTIAL PURPOSE.

10. Indemnification: You agree to defend, indemnify and hold harmless VMware, andany of its directors, officers, employees, affiliates and agents, from and against any andall claims, losses, damages, liabilities and other expenses (including reasonableattorneys' fees), arising from your modification of the "modifiable code," the distributionor use of your Developer Software by you or anyone else, and your breach of thisAgreement.




11. Export Control: You acknowledge that the Software is of United States origin, isprovided subject to the U.S. Export Administration Regulations, may be subject to theexport control laws of the applicable territory, and that diversion contrary to applicableexport control laws is prohibited. You represent, warrant and covenant that (1) you arenot, and are not acting on behalf of, (a) any person who is a citizen, national, or residentof, or who is controlled by the government of any country to which the United States hasprohibited export transactions; or (b) any person or entity listed on the U.S. TreasuryDepartment list of Specially Designated Nationals and Blocked Persons, or the U.S.Commerce Department Denied Persons List or Entity List; and (2) you will not permit theSoftware to be used for any purposes prohibited by law, including, any prohibiteddevelopment, design, manufacture or production of missiles or nuclear, chemical orbiological weapons.

12. Data Privacy:

(a)_Consent for Collection and Use of Technical Data. You agree that VMware mayperiodically collect, process and store technical and related information about yourdevice, system, application, peripherals and your use of the Software, including withoutlimitation: internet protocol address, hardware identification, operating system,application software, peripheral hardware, number of active plugins and softwaredevelopment kits, the successful installation and launch of Software, and Software usagestatistics (collectively, "Technical Data"). VMware will use Technical Data for internalstatistical and analytical purposes to facilitate support, invoicing or online services, theprovisioning of updates, and the development of VMware products and services. VMwaremay transfer Technical Data to other companies in the VMware worldwide group ofcompanies from time to time.

(b) Log Files. You acknowledge that correspondence and log files generated inconjunction with a request for support services may contain sensitive, confidential orpersonal information. You are solely responsible for taking the steps necessary toprotect such data, including obfuscating the logs or otherwise guarding such informationprior to sending it to VMware.

13. These terms are governed by the laws of the State of California and the United Statesof America without regard to conflict of laws principles. The United Nations Conventionfor the International Sale of Goods shall not apply. You may not assign this Agreement.Any attempted assignment by you shall be void. These terms constitute the entireagreement between you and VMware with respect to the Software and supersede allprior written or oral communications, understandings and agreements. Any waiver ofthese terms must be in writing and signed by the waiving party to be effective. If anyprovision of these terms is found to be invalid or unenforceable, the remaining terms willcontinue to be valid and enforceable to the fullest extent permitted by law.




Hitachi Vantara

Corporate Headquarters

2845 Lafayette Street

Santa Clara, CA 95050-2639 USA

HitachiVantara.com | community.HitachiVantara.com

Contact Information

USA: 1-800-446-0744

Global: 1-858-547-4526

HitachiVantara.com/contact

https://www.linkedin.com/company/hitachi-vantara

https://twitter.com/hitachivantara

https://www.facebook.com/HitachiVantara

https://www.youtube.com/user/HDScorp