CA Unicenter Service Catalog - Note di rilascio

Transcription

CA Unicenter Service Catalog
Note di rilascio
Versione 12.6
La presente documentazione, che include il sistema di guida in linea integrato e materiale distribuibile elettronicamente (d'ora
in avanti indicata come "Documentazione"), viene fornita all'utente finale a scopo puramente informativo e può essere
modificata o ritirata da CA in qualsiasi momento.
Questa Documentazione non può essere copiata, trasmessa, riprodotta, divulgata, modificata o duplicata per intero o in parte,
senza la preventiva autorizzazione scritta di CA. Questa Documentazione è di proprietà di CA e non potrà essere divulgata o
utilizzata se non per gli scopi previsti in (i) uno specifico contratto tra l'utente e CA in merito all'uso del software CA cui la
Documentazione attiene o in (ii) un determinato accordo di confidenzialità tra l'utente e CA.
Fermo restando quanto enunciato sopra, se l'utente dispone di una licenza per l'utilizzo dei software a cui fa riferimento la
Documentazione avrà diritto ad effettuare copie della suddetta Documentazione in un numero ragionevole per uso personale e
dei propri impiegati, a condizione che su ogni copia riprodotta siano apposti tutti gli avvisi e le note sul copyright di CA.
Il diritto a stampare copie della presente Documentazione è limitato al periodo di validità della licenza per il prodotto. Qualora
e per qualunque motivo la licenza dovesse cessare o giungere a scadenza, l'utente avrà la responsabilità di certificare a CA per
iscritto che tutte le copie anche parziali del prodotto sono state restituite a CA o distrutte.
NEI LIMITI CONSENTITI DALLA LEGGE VIGENTE, LA DOCUMENTAZIONE VIENE FORNITA "COSÌ COM'È" SENZA GARANZIE DI
ALCUN TIPO, INCLUSE, IN VIA ESEMPLIFICATIVA, LE GARANZIE IMPLICITE DI COMMERCIABILITÀ, IDONEITÀ A UN DETERMINATO
SCOPO O DI NON VIOLAZIONE DEI DIRITTI ALTRUI. IN NESSUN CASO CA SARÀ RITENUTA RESPONSABILE DA PARTE DELL'UTENTE
FINALE O DA TERZE PARTI PER PERDITE O DANNI, DIRETTI O INDIRETTI, DERIVANTI DALL'UTILIZZO DELLA DOCUMENTAZIONE,
INCLUSI, IN VIA ESEMPLICATIVA E NON ESAUSTIVA, PERDITE DI PROFITTI, INTERRUZIONI DELL'ATTIVITÀ, PERDITA DEL
GOODWILL O DI DATI, ANCHE NEL CASO IN CUI CA VENGA ESPRESSAMENTE INFORMATA IN ANTICIPO DI TALI PERDITE O
DANNI.
L'utilizzo di qualsiasi altro prodotto software citato nella Documentazione è soggetto ai termini di cui al contratto di licenza
applicabile, il quale non viene in alcun modo modificato dalle previsioni del presente avviso.
Il produttore di questa Documentazione è CA.
Questa Documentazione è fornita con "Diritti limitati". L'uso, la duplicazione o la divulgazione da parte del governo degli Stati
Uniti è soggetto alle restrizioni elencate nella normativa FAR, sezioni 12.212, 52.227-14 e 52.227-19(c)(1) - (2) e nella normativa
DFARS, sezione 252.227-7014(b)(3), se applicabile, o successive.
Copyright © 2010 CA. Tutti i diritti riservati. Tutti i marchi, i nomi commerciali, i marchi di servizio e i loghi citati nel presente
documento sono di proprietà delle rispettive aziende.
Riferimenti ai prodotti CA
Questo documento può fare riferimento ai seguenti prodotti o componenti CA:
■
CA Service Accounting
■
CA Unicenter Service Catalog
■
CA Embedded Entitlements Manager (Embedded Entitlements Manager)
■
CA CMDB
■
CA Service Desk Manager
■
CA SiteMinder®
■
CA Asset Portfolio Management (CA APM)
■
CA MICS® Resource Management
■
CA JARS®
■
CA Storage Resource Manager (CA SRM)
■
CA Service Assure
■
CA Service Metric Analysis (CA SMA)
■
CA Workflow
■
Dashboard Guida introduttiva™ ad Administration®
■
CA IT Process Automation Manager™ (CA IT PAM)
■
CA Business Intelligence
Contattare il servizio di Supporto tecnico
Per l'assistenza tecnica in linea e un elenco completo delle sedi, degli orari del
servizio di assistenza e dei numeri di telefono, contattare il Supporto tecnico
visitando il sito Web all'indirizzo http://www.ca.com/worldwide.
Sommario
Capitolo 1: Nuove funzionalità e miglioramenti
9
Integrazione con CA Oblicore Guarantee ........................................................ 10
Integrazione con Reservation Manager ......................................................... 12
Approvazione e rifiuto delle richieste con un PDA ................................................ 14
Delega dei cataloghi .......................................................................... 15
Ciclo di vita della richiesta separato per servizi e opzioni di servizio ................................ 16
Gestione di richieste basate su criteri ........................................................... 17
Pagine di elenco delle richieste configurabili .................................................... 18
Nuove funzionalità di ricerca avanzate .......................................................... 19
Miglioramenti apportati all'installazione ........................................................ 20
Eventi, regole e azioni nuovi e aggiornati........................................................ 20
Capitolo 2: Funzioni eliminate
23
Integrazione con CA Service Assure ............................................................. 23
Utilizzo di WebLogic come server Web .......................................................... 24
Lingue localizzate ............................................................................. 24
Funzionalità di ricerca avanzata precedente ..................................................... 24
Capitolo 3: Funzionalità modificate
25
Configurazione dell'opzione denominata Utilizza solo il catalogo del fornitore di servizio ............ 26
Capitolo 4: Documentazione
27
Documentazione ............................................................................. 27
CA Bookshelf ................................................................................. 28
File Leggimi .................................................................................. 29
Numeri di versione sulla documentazione ....................................................... 29
Capitolo 5: Informazioni di sistema
31
Supporto del sistema operativo ................................................................ 31
Requisiti di sistema ........................................................................... 31
Browser .................................................................................. 32
Database ................................................................................. 33
Sommario 5
Requisiti hardware ............................................................................ 33
Requisiti hardware per l'installazione standalone ............................................ 34
Requisiti hardware per l'installazione distribuita ............................................. 34
Requisiti hardware per server DBMS ........................................................ 35
Requisiti software ............................................................................ 35
Requisiti software per server Web .......................................................... 35
Bilanciatori di carico ....................................................................... 36
Requisiti software per il server del database ................................................. 36
Requisiti software per l'ambiente Runtime .................................................. 36
Requisiti software per i componenti CA comuni .............................................. 37
Integrazioni facoltative con altri prodotti CA .................................................... 38
Requisiti del client ............................................................................ 39
Capitolo 6: Considerazioni e requisiti per installazioni e aggiornamenti
41
Considerazioni generali e requisiti .............................................................. 41
Considerazioni e requisiti di distribuzione ....................................................... 43
Considerazioni e requisiti di condivisione di rete ................................................. 43
Capitolo 7: Considerazioni generali
45
Supporto internazionale ....................................................................... 45
Considerazioni per prevenire la duplicazione di eventi, regole e azioni ............................. 47
Considerazioni sulla localizzazione.............................................................. 49
Localizzare l'elenco dei prompt relativi a valori e dati dei report ............................... 49
Localizzare i nomi di utenti, gruppi e report ................................................. 50
Correzioni pubblicate ......................................................................... 50
Capitolo 8: Aggiornamenti della documentazione
51
Capitolo 9: Problemi noti
53
Restituzione di dati corrotti da parte di Oracle DBMS ............................................ 54
Impedire la visualizzazione di messaggi di avviso falsi correlati al ruolo di Gestione servizio .......... 54
Riavvio del computer dopo la migrazione ....................................................... 55
Azioni disabilitate dopo l'aggiornamento ........................................................ 55
Azione CA IT PAM disattivata .................................................................. 55
Impossibile accedere a CA EEM dopo l'aggiornamento ........................................... 56
Impossibile installare l'applicazione CA EEM ..................................................... 56
Impossibile assegnare modelli CA AMP ......................................................... 57
6 Note di rilascio
Integrazione con CA APM utilizzando Oracle .................................................... 58
Impossibile creare ordini di cambiamento quando Multi-Tenancy è attivo ......................... 58
Non spostare i titolari ......................................................................... 59
Valori mancanti dai report ..................................................................... 59
Ricreare periodi di anni fiscali dopo la migrazione................................................ 59
Campi numerici nei sistemi operativi localizzati .................................................. 59
Non è possibile installare Service View e il server Oracle insieme .................................. 60
Stato di disponibilità delle cartelle .............................................................. 60
Campi nvarchar nei rapporti ................................................................... 60
Cartelle rimanenti al termine della disintallazione ............................................... 60
Distinzione tra maiuscole e minuscole per CA MDB su Oracle ..................................... 61
Impossibile generare rapporti non in linea in formato PDF ........................................ 61
Problemi con la sospensione di un servizio sottoscritto ........................................... 61
I collegamenti ipertestuali ai siti Web non CA potrebbero non funzionare .......................... 61
Può apparire il sommario della guida al posto dell'argomento specifico della guida.................. 62
Le richieste completate e annullate possono essere bloccate ..................................... 62
L'aggiornamento MDB potrebbe non riuscire durante l'aggiornamento di Service View ............. 62
L'esecuzione di ulteriori tentativi per le azioni non riuscite non funziona ........................... 63
Campi mancanti nell'IDE di CA Workflow con JNLP su Macintosh .................................. 63
Messaggi di avviso del sistema sempre in lingua inglese .......................................... 63
La stampa batch non va a buon fine con Mozilla Firefox .......................................... 64
Le celle appaiono di grandi dimensioni con Apple Safari .......................................... 64
Decidere come elaborare le cifre per lo Yen ..................................................... 64
Appendice A: Riconoscimenti delle licenze di terze parti
65
Dipendenze da prodotti software di terze parti .................................................. 66
Apache License Version 2.0 .................................................................... 67
Apache License Version 1.1 .................................................................... 75
Apache CXF 2.2.8 ............................................................................. 79
Apache mod_jk 1.2.30........................................................................ 123
Apache Tomcat 5.5.29 ....................................................................... 132
EclipseLink 1.1.2 ............................................................................. 198
iquery 1.3.2 ................................................................................. 207
Java Persistence API v.1 ...................................................................... 208
Java Service Wrapper (JSW) Standard 3.3.9 .................................................... 209
JAXB ........................................................................................ 211
Mozilla Rhino 1.5R4.1 ........................................................................ 224
Open Message Queue 4.1 .................................................................... 242
Sommario 7
Oracle 11G JDBC Driver....................................................................... 243
Saxon 8.53 .................................................................................. 243
SourceForge Dom4j 1.6.1 ..................................................................... 244
SourceForge ANT-CONTRIB v.1.0b3 ............................................................ 246
Sun JRE 1.6.0_14............................................................................. 250
Unzip 5.42 .................................................................................. 263
8 Note di rilascio
Capitolo 1: Nuove funzionalità e
miglioramenti
Questa sezione contiene i seguenti argomenti:
Integrazione con CA Oblicore Guarantee (a pagina 10)
Integrazione con Reservation Manager (a pagina 12)
Approvazione e rifiuto delle richieste con un PDA (a pagina 14)
Delega dei cataloghi (a pagina 15)
Ciclo di vita della richiesta separato per servizi e opzioni di servizio (a pagina 16)
Gestione di richieste basate su criteri (a pagina 17)
Pagine di elenco delle richieste configurabili (a pagina 18)
Nuove funzionalità di ricerca avanzate (a pagina 19)
Miglioramenti apportati all'installazione (a pagina 20)
Eventi, regole e azioni nuovi e aggiornati (a pagina 20)
Capitolo 1: Nuove funzionalità e miglioramenti 9
Integrazione con CA Oblicore Guarantee
CA Oblicore Guarantee consente di automatizzare, attivare ed accelerare la
gestione, il monitoraggio e la creazione di report degli accordi sui livelli di
servizio (SLA) di attività di business e tecnologiche, nonché di accordi di
distribuzione del servizio per aziende e fornitori di servizi. CA Oblicore
Guarantee favorisce una comprensione in tempo reale delle implicazioni
determinate dalle prestazioni ed i costi di tali accordi. CA Oblicore Guarantee
fornisce alle aziende ed ai fornitori di servizi un'unica soluzione efficace e
trasparente per la gestione della distribuzione dei servizi tra infrastrutture di
business e tecnologiche.
La metodologia top-down di <obc> per la gestione dei livelli di servizio inizia con
contratti che utilizzano il linguaggio e le metriche di business. Tali contratti
vengono integrati con fonti di dati tecnici in modo da garantire una valutazione
continua delle prestazioni di servizio in relazione ai termini ed alle condizioni di
contratto. La trasparenza ed il controllo che ne derivano consentono di gestire
in maniera efficace le aspettative tra l'IT e le attività di business ed i contratti
con fornitori di servizi esterni, ad esempio CA Unicenter Service Catalog.
Oltre ai vantaggi offerti da CA Unicenter Service Catalog e CA Oblicore
Guarantee a livello individuale, l'integrazione dei due prodotti consente i
seguenti ulteriori vantaggi:
■
[UPDATED...ok??] Quando si definisce un'opzione di servizio,
l'amministratore di CA Unicenter Service Catalog può eseguire ricerche in un
elenco di contratti di CA Oblicore Guarantee, selezionarne uno ed associarlo
all'opzione di servizio. È inoltre possibile selezionare un componente di
servizio, metriche contrattuali e metriche di incentivo da tale contratto per
associarlo all'opzione di servizio.
Tali elementi consentono di specificare la qualità del servizio prevista per
l'opzione di servizio. Il componente di servizio consente di specificare quali
elementi monitorare (un componente relativo all'opzione di servizio),
mentre le metriche consentono di specificare quali dati monitorare (ad
esempio kilobyte al secondo o violazioni per mese). È possibile selezionare
una metrica contrattuale con un livello di qualità del servizio più elevato ed
un costo superiore, oppure selezionare una metrica contrattuale con un
livello di qualità del servizio inferiore ed un costo minore.
■
10 Note di rilascio
[NEW...ok??] L'utilizzo dell'integrazione descritto nella presente
documentazione consente di valutare la conformità ai contratti CA Oblicore
Guarantee in base ai servizi a livello generale, ovvero tutte le richieste di
servizio per il periodo di tempo specificato dalle metriche selezionate.
■
L'associazione di un'opzione di servizio ad un contratto ed il monitoraggio
fornito da entrambi i prodotti supporta la trasparenza della qualità del
servizio, a partire dalla richiesta fino all'esecuzione e dalla fatturazione fino
all'addebito.
■
Inoltre, l'associazione del servizio ad un contratto ed il monitoraggio fornito
da entrambi i prodotti consente inoltre di rettifiche finanziarie in base
quanto specificato nel contratto. Ad esempio, le rettifiche possono
includere costi ridotti se il servizio non soddisfa le condizioni del contratto o
costi maggiori se il servizio supera i termini del contratto.
■
È possibile utilizzare CA Oblicore Guarantee o CA Unicenter Service Catalog
per visualizzare il livello di conformità di un servizio CA Unicenter Service
Catalog in base alle condizioni dei contratti CA Oblicore Guarantee
corrispondenti.
È inoltre possibile utilizzare le funzionalità di fatturazione di CA Service
Accounting per determinare le rettifiche finanziarie necessarie per un servizio
che non soddisfa o supera le condizioni specificate nel contratto corrispondente.
Nota: per ulteriori dettagli sull'integrazione con CA Oblicore Guarantee,
consultare la Integration Guide.
Integrazione con Reservation Manager
È possibile utilizzare Reservation Manager per prenotare sistemi da un pool di
risorse disponibili nel centro dati. Reservation Manager consente la
prenotazione su richiesta dell'accesso alle risorse condivise per un determinato
periodo di tempo. Reservation Manager è integrato con CA Spectrum
Automation Manager e ne utilizza la tecnologia di fornitura per fornire all'utente
i sistemi con le funzionalità richieste per il periodo di tempo indicato.
Reservation Manager è un'utilità indipendente la cui interfaccia utente è
integrata con CA Spectrum Automation Manager per fornire agli utenti risorse
su richiesta per la prenotazione di sistemi Windows, Linux, AIX e Solaris. Quando
si crea una prenotazione, è possibile specificare quali software, hardware ed
immagini del sistema operativo sono richiesti dal sistema. Una prenotazione
consente di richiedere sistemi fisici o di creare computer virtuali.
Nota: per ulteriori informazioni sull'impostazione e la configurazione di
Reservation Manager, consultare la Guida all'amministrazione e
l'Implementation Guide di CA Spectrum Automation Manager. Per ulteriori
informazioni sull'utilizzo di Reservation Manager, consultare la Reservation
Manager user Guide di CA Spectrum Automation Manager.
Oltre ai vantaggi offerti da CA Unicenter Service Catalog e Reservation Manager
a livello individuale, l'integrazione dei due prodotti consente i seguenti ulteriori
vantaggi:
12 Note di rilascio
■
L'aggiunta a Reservation Manager di un ciclo di vita della richiesta,
compresa la registrazione dei costi, l'utilizzo ed il riaddebito
■
Un unico punto di contatto che consente agli utenti del catalogo di creare,
estendere e restituire (annullare) le prenotazioni di risorse fisiche e virtuali
in maniera illimitata, efficace e trasparente
■
L'aggiunta a CA Unicenter Service Catalog di servizi e gruppi di opzione di
servizio predefiniti che consentono agli utenti del catalogo di eseguire
richieste di prenotazione.
■
Flessibilità per gli amministratori nell'utilizzo di questi servizi e gruppi di
opzione di servizio predefiniti. Tali servizi possono essere utilizzati così come
vengono distribuiti o personalizzati in base alle esigenze di business
■
Un unico punto di contatto che consente agli amministratori di tenere
traccia, contabilizzare ed eseguire report relativi a tali richieste in maniera
automatica, efficace e trasparente
■
Miglioramento della governance e della gestione di richieste e
dell'esecuzione di risorse fisiche e virtuali
■
Contabilizzazione della fornitura basata sull'utilizzo mediante CA Service
Accounting
Nota: per ulteriori dettagli sull'integrazione con Reservation Manager,
consultare la Integration Guide.
Approvazione e rifiuto delle richieste con un PDA
Approvazione e rifiuto delle richieste con un PDA
Quando gli amministratori ed i manager aziendali sono in trasferta per motivi di
lavoro, utilizzano solitamente un dispositivo mobile denominato PDA (Personal
Digital Assistant) che consente la comunicazione mediante chiamate e messaggi
di posta elettronica e la connessione ad internet attraverso uno speciale
browser Web. In tal modo, i processi di business non vengono interrotti.
In qualità di amministratore di CA Unicenter Service Catalog, è possibile
configurare l'implementazione di CA Unicenter Service Catalog ed i relativi
servizi affinché gli utenti possano approvare e rifiutare le richieste mediante un
PDA. Questi utenti ricevono una notifica automatica tramite posta elettronica
sui rispettivi PDA per indicare che una richiesta è in attesa di approvazione (un
messaggio di posta elettronica di richiesta di conferma).
A seconda di come è impostata l'approvazione PDA, gli utenti PDA possono
utilizzare facoltativamente i collegamenti forniti nella richiesta di approvazione
inviata tramite posta elettronica per eseguire una o più delle seguenti azioni:
■
Accedere a CA Unicenter Service Catalog, visualizzare i dettagli della
richiesta, quindi approvare o rifiutare la richiesta
■
Approvare o rifiutare la richiesta, il servizio o le opzioni di servizio senza
visualizzarne i dettagli
Gli utenti devono immettere le credenziali di accesso manualmente
■
Approvare o rifiutare la richiesta, il servizio o le opzioni di servizio senza
accedere a CA Unicenter Service Catalog; questa azione è l'approvazione
tramite mailing diretto
L'utilizzo dei dispositivi palmari garantisce, pertanto, il funzionamento del ciclo
di vita della richiesta anche a distanza.
Il processo di approvazione o rifiuto di una richiesta mediante un PDA
(Approvazione PDA) è simile a quello che prevede l'utilizzo di un computer fisso
o portatile. L'approvazione PDA si distingue tuttavia per alcune impostazioni
aggiuntive e comporta alcune limitazioni da tenere in considerazione rispetto al
processo standard mediante computer fisso o portatile.
Nota: per ulteriori dettagli sull'approvazione PDA, consultare la Guida
all'amministrazione.
14 Note di rilascio
Delega dei cataloghi
Delega dei cataloghi
La delega dell'utilizzo del catalogo ad un altro utente (un delegato) consente al
delegato di sfogliare il catalogo e di creare ed inviare le richieste per conto
dell'utente in questione (il delegante). Il catalogo di un delegante solitamente
contiene servizi non disponibili nel catalogo del delegato.
La figura del delegante corrisponde solitamente a quella di un dirigente o di un
manager; può, tuttavia, trattarsi anche di un utente il cui ruolo consente la
creazione e l'invio di richieste. I delegati sono solitamente assistenti di direzione
o altri dipendenti che rispondono al delegante o un qualsiasi utente il cui ruolo
consente la creazione e l'invio di richieste.
In genere, un delegato crea ed invia le richieste per un delegante dal catalogo
del delegante. Quando un delegato crea una richiesta dal catalogo del
delegante, il campo Richiesto per mostra il nome del delegante; tale campo non
può essere modificato.
Quando possibile, la cronologia, il controllo e la registrazione dei record
contengono il nome del delegato che ha creato ed inviato la richiesta per conto
del delegante.
Nota: per maggiori dettagli sulla delega dei cataloghi, consultare la Guida
Ciclo di vita della richiesta separato per servizi e opzioni di servizio
Ciclo di vita della richiesta separato per servizi e opzioni di
servizio
Gli amministratori possono specificare impostazioni separate per il ciclo di vita
della richiesta per le singole unità di business, come indicato di seguito:
■
in base alla configurazione selezionata, è possibile specificare lo stato a
partire dal quale i manager della richiesta (responsabili dell'approvazione e
dell'esecuzione) possono approvare, rifiutare o eseguire separatamente
ogni opzione di servizio in ciascun servizio presente nella richiesta.
L'impostazione specificata si applica alla richiesta dallo stato iniziale
specificato attraverso il resto del ciclo di vita della richiesta.
■
È possibile specificare in modo indipendente lo stato in cui le singole opzioni
all'interno di un servizio e i singoli servizi all'interno di una richiesta passano
allo stato successivo del ciclo di vita della richiesta. In modo indipendente
significa senza richiedere o attendere altre opzioni all'interno dello stesso
servizio o altri servizi all'interno della stessa richiesta per passare a stati
successivi. L'impostazione specificata si applica alla richiesta dallo stato
iniziale specificato attraverso il resto del ciclo di vita della richiesta.
■
È possibile specificare l'effetto del rifiuto di un singolo servizio o opzione di
servizio su altri servizi e opzioni di servizio all'interno della stessa richiesta:
–
Se l'opzione è impostata su Sì, quando si rifiuta un servizio o un'opzione
di servizio, i servizi o le opzioni rimanenti possono avanzare se vengono
approvati.
–
Se l'opzione è impostata su No, quando si rifiuta un servizio o
un'opzione di servizio, viene rifiutata l'intera richiesta. Lo stato degli
altri servizi o opzioni di servizio precedentemente approvati viene
modificato in Rifiutato e non possono avanzare nel ciclo di vita della
richiesta.
Per tutti questi parametri, le impostazioni predefinite mantengono la
compatibilità con le versioni precedenti, pertanto il ciclo di vita della richiesta
funziona allo stesso modo delle release precedenti prima dell'implementazione
di tale parametro.
Nota: per ulteriori informazioni sul ciclo di vita della richiesta separato,
consultare la Guida all' amministrazione.
16 Note di rilascio
Gestione di richieste basate su criteri
Gestione di richieste basate su criteri
Se l'implementazione di CA Unicenter Service Catalog utilizza CA IT PAM per
l'approvazione e l'esecuzione delle richieste, gli amministratori di CA Unicenter
Service Catalog possono creare criteri per definire le condizioni per la
designazione automatica di utenti specifici come assegnatari di un'attività
durante il ciclo di vita della richiesta. La pratica più comune è la creazione di
criteri per definire le condizioni di assegnazione automatica di utenti specifici
come responsabili dell'approvazione per i servizi e le opzioni di servizio in una
richiesta inviata (una richiesta in sospeso).
Questa funzionalità offre la flessibilità di assegnare attività (ad esempio di
approvazione o rifiuto delle richieste in sospeso) ad utenti diversi dai manager
presenti nella gerarchia organizzativa del richiedente. Ad ogni modo, è possibile
includere il manager dell'utente oppure la gerarchia dei manager nell'elenco
degli assegnatari.
Il criterio creato si basa sui seguenti componenti principali:
■
La condizione in cui si applica il criterio. Se la condizione non viene
soddisfatta, il criterio non può essere attivato
■
L'assegnazione da effettuare se la condizione viene soddisfatta. In tal caso,
all'utente o agli utenti specificati viene assegnata un'azione in sospeso, ad
esempio di approvazione o di esecuzione
È possibile, inoltre, specificare l'elenco degli assegnatari in base ad uno dei
tanti attributi, inclusi, fra gli altri, i seguenti:
■
ID utente
■
Appartenenza a un gruppo di utenti
■
Gerarchia di gestione (manager dell'utente, manager del manager, e
così via)
■
Un'impostazione attiva/inattiva
■
Descrizione e campi relativi alla priorità
Nota: CA Workflow non supporta la gestione di richieste basata sui criteri.
Nota: per ulteriori informazioni sulla gestione di richiesta basate sui criteri
consultare la Guida all' amministrazione.
Pagine di elenco delle richieste configurabili
Pagine di elenco delle richieste configurabili
Gli amministratori il cui ruolo corrisponde a Fornitore di servizio (per
impostazione predefinita, spadmin) possono configurare la visualizzazione delle
colonne delle pagine di elenco delle richieste. Le pagine di elenco della richieste
visualizzano tutte le richieste o un sottoinsieme di richieste filtrate, come ad
esempio le richieste aperte, in sospeso e completate.
Per visualizzare una pagina di elenco delle richieste, fare clic su Pagina iniziale,
Richieste oppure selezionare una delle seguenti opzioni dalla pagina Richieste:
■
Richieste aperte
■
Richieste personali recenti
■
Richieste completate
■
Azione personale in sospeso
■
Ricerca avanzata – in seguito alla ricerca di richieste e la visualizzazione dei
risultati
Quando viene selezionata una delle opzioni descritte precedentemente, il
sistema del catalogo apre una pagina di elenco delle richieste in formato tabella;
ad ogni riga corrisponde una richiesta. Ciascuna colonna della tabella mostra un
attributo della richiesta, come ad esempio l'ID della richiesta, il nome, la priorità
o lo stato.
È possibile ordinare le colonne, configurarne la larghezza, includere od
escludere una colonna dalla visualizzazione ed impostare il numero predefinito
di richieste elencate per pagina. Le impostazioni specificate vengono applicate a
tutti gli utenti di CA Unicenter Service Catalog per tutte le unità di business.
18 Note di rilascio
Nuove funzionalità di ricerca avanzate
Nuove funzionalità di ricerca avanzate
CA Unicenter Service Catalog 12.6 contiene alcuni aggiornamenti che
semplificano la creazione, il salvataggio, il riutilizzo e la condivisione delle
ricerche avanzate.
Gli utenti con ruolo di amministratore di Service Delivery possono salvare e
condividere query di ricerca avanzate. Quando gli amministratori di Service
Delivery condividono query di ricerca avanzate, tali query saranno disponibili
per tutti gli utenti di tutte le Unità di business, a prescindere dai ruoli.
Gli utenti che dispongono di un ruolo diverso da quello di amministratore di
Service Delivery possono salvare le proprie query di ricerca avanzate ma non le
possono condividere. Tali utenti possono caricare ed eseguire le query salvate
da loro stessi o le query condivise dall'amministratore di Service Delivery.
La presente versione contiene una funzionalità di ricerca avanzata semplice da
usare e funzionalità di condivisione migliorata grazie alle seguenti opzioni
disponibili facendo clic su Ricerca avanzata della pagina principale, Richieste:
■
L'opzione Cerca (per impostazione predefinita, una lente di ingrandimento)
che consente di digitare una nuova query di ricerca avanzata.
■
L'opzione Salva (per impostazione predefinita, una cartella con la freccia
verso il basso) consente di salvare le query di ricerca avanzate immesse e, se
possibile, di condividerle. Tutti gli utenti possono salvare query per uso
personale. Soltanto gli amministratori di Service Delivery possono
condividere query con altri utenti.
■
L'opzione Carica (per impostazione predefinita, una cartella aperta
contenente dei fogli) consente di caricare le query di ricerca avanzate in
modo da poterle eseguire nuovamente. È inoltre possibile filtrare le query in
base al tipo (query condivise o query personali).
Se un amministratore ha salvato le query delle versioni precedenti prima di
eseguire l'aggiornamento a CA Unicenter Service Catalog 12.6, dovrà verificare
che le richieste salvate nella versione corrente siano in funzionamento. In caso
contrario, potrebbe essere necessario aggiornare o sostituire le query salvate
dalle versioni precedenti.
Per ulteriori dettagli sulle ricerche, comprese le ricerche avanzate, consultare la
Guida all'amministrazione.
Miglioramenti apportati all'installazione
Miglioramenti apportati all'installazione
CA Unicenter Service Catalog 12.6 rimuove le seguenti restrizioni relative alle
versioni precedenti:
■
È stato possibile installare CA Service Accounting sullo stesso computer su
cui è stato installato soltanto CA Workflow.
■
Se CA Service Accounting e CA Workflow sono installati sullo stesso
computer, all'utente viene richiesto di installare anche Service View sullo
stesso computer.
Eventi, regole e azioni nuovi e aggiornati
CA Unicenter Service Catalog 12.6 include un nuovo evento denominato
Cambiamento della richiesta in attesa di azione. L'evento contiene la regola
esistente denominata Quando lo stato è In attesa di approvazione e le azioni
corrispondenti.
Questa regola è stata spostata dall'evento esistente denominato Cambiamento
elemento Richiesta/Sottoscrizione al nuovo evento.
L'evento Cambiamento della richiesta in attesa di azione costituisce
un'ubicazione più intuitiva per la regola Quando lo stato è In attesa di
approvazione poiché lo scopo e le azioni della regola riguardano principalmente
le modifiche apportate alle richieste in attesa di azione e non le modifiche
apportate alle opzioni di servizio. In tal modo, la modifica consente agli
amministratori di gestire le regole e le azioni in maniera più modulare. Tale
spostamento consente inoltre al sistema del catalogo di elaborare il ciclo di vita
della richiesta in maniera più efficace, specialmente nel caso di notifiche e
assegnazioni di richieste in attesa di azione, come ad esempio trasferimenti,
deleghe, accettazioni e restituzioni.
La regola aggiornata Quando lo stato è In attesa di approvazione contenuta
nell'evento Cambiamento della richiesta in attesa di azione contiene una nuova
azione di approvazione denominata Notifica responsabile dell'approvazione Approvazione mediante posta elettronica. Si tratta di un'azione necessaria per
abilitare l'approvazione e il rifiuto delle richieste direttamente mediante posta
elettronica (approvazione diretta tramite posta elettronica). Se vengono abilitati
l'approvazione o il rifiuto delle richieste con un PDA (a pagina 14), sarà possibile
implementare anche l'approvazione tramite posta elettronica diretta.
20 Note di rilascio
Eventi, regole e azioni nuovi e aggiornati
Spostamento di altre regole
Le seguenti regole sono state spostate dall'evento Cambiamento elemento
Richiesta/Sottoscrizione all'evento Cambiamento della richiesta in attesa di
azione per gli stessi motivi specificati precedentemente relativi allo
spostamento della regola Quando lo stato è In attesa di approvazione.
■
Quando le azioni in attesa di esecuzione vengono assegnate
■
Quando le azioni in attesa di esecuzione vengono completate
■
Quando lo stato è Approvato
■
Quando lo stato è Esecuzione annullata
■
Quando lo stato è In attesa di approvazione
■
Quando lo stato è Rifiutato
Informazioni solo per gli aggiornamenti
Se viene eseguito l'aggiornamento da una versione precedente di CA Unicenter
Service Catalog, tutte le regole e le azioni abilitate precedentemente rimarranno
attive all'interno degli eventi che le contengono. Le regole e le azioni dell'evento
Cambiamento della richiesta in attesa di azione resteranno disattivate fino
all'attivazione. Al momento dell'attivazione, disattivare le regole e le azioni con
lo stesso nome dell'evento Cambiamento elemento Richiesta/Sottoscrizione in
modo da evitare la duplicazione di regole ed eventi. Ad esempio, se viene
abilitata la regola Quando lo stato è In attesa di approvazione per entrambi gli
eventi, il sistema rileverà la duplicazione delle azioni Notifica responsabile
dell'approvazione ed invierà messaggi di posta elettronica duplicati di
approvazione della richiesta.
Capitolo 2: Funzioni eliminate
Integrazione con CA Service Assure (a pagina 23)
Utilizzo di WebLogic come server Web (a pagina 24)
Lingue localizzate (a pagina 24)
Funzionalità di ricerca avanzata precedente (a pagina 24)
Integrazione con CA Service Assure
CA Service Assure è stato pianificato per raggiungere la fine del ciclo di vita il 31
marzo del 2011. Per ulteriori dettagli, contattare il CA Support all'indirizzo
http://ca.com/support. Pertanto, l'integrazione con CA Service Assure non è più
supportata da CA Unicenter Service Catalog r12.6.
Se si sta utilizzando l'integrazione e viene eseguito l'aggiornamento a CA
Unicenter Service Catalog r12.6, l'integrazione verrà disattivata durante
l'aggiornamento. In CA Unicenter Service Catalog r12.6, i servizi esistenti che
utilizzavano l'integrazione continueranno a funzionare nello stesso modo, fatta
eccezione per tutti gli elementi dell'opzione di servizio (precedentemente
denominati elementi del tasso). Tali elementi, il cui tipo corrisponde a Contratto,
vengono ignorati per tutto l'intero ciclo di vita della richiesta e non vengono
utilizzati per la fatturazione.
Si consiglia di eseguire l'implementazione di CA Oblicore Guarantee (come
alternativa a CA Service Assure) e di integrarlo con CA Unicenter Service Catalog
(a pagina 10). CA Oblicore Guarantee consente di automatizzare, attivare ed
accelerare la gestione, il monitoraggio e la creazione di report degli accordi sui
livelli di servizio (SLA) di attività di business e tecnologiche, nonché di accordi di
distribuzione del servizio per aziende e fornitori di servizi.
È possibile ottenere un valore aggiunto associando le opzioni di servizio di CA
Unicenter Service Catalog alle metriche SLA dei contratti CA Unicenter Service
Catalog. È possibile visualizzare i dati aggregati per stabilire la qualità dei servizi
forniti. È inoltre possibile utilizzare le funzionalità di fatturazione di CA Service
Accounting per determinare le rettifiche finanziarie necessarie per un servizio
che non soddisfa o supera le condizioni specificate nel contratto corrispondente.
Nota: per ulteriori informazioni sull'integrazione di CA Unicenter Service Catalog
e CA Oblicore Guarantee, consultare la Integration Guide.
Capitolo 2: Funzioni eliminate 23
Utilizzo di WebLogic come server Web
Utilizzo di WebLogic come server Web
CA Unicenter Service Catalog non consente più la configurazione di WebLogic
come server Web.
Il nuovo server Web per CA Unicenter Service Catalog è Apache Tomcat (a
pagina 35).
Lingue localizzate
CA Unicenter Service Catalog non è più localizzato in cinese semplificato e in
coreano.
CA Unicenter Service Catalog continua a fornire supporto internazionale (a
pagina 45) per le altre lingue.
Funzionalità di ricerca avanzata precedente
La funzionalità di ricerca avanzata della versione precedente potrebbe non
funzionare con la nuova funzionalità di ricerca avanzata (a pagina 19) fornita con
CA Unicenter Service Catalog 12.6. Si consiglia, pertanto, di iniziare ad utilizzare
la nuova funzionalità di ricerca subito dopo l'installazione.
24 Note di rilascio
Capitolo 3: Funzionalità modificate
Configurazione dell'opzione denominata Utilizza solo il catalogo del fornitore di
servizio (a pagina 26)
Capitolo 3: Funzionalità modificate 25
Configurazione dell'opzione denominata Utilizza solo il catalogo del fornitore di servizio
Configurazione dell'opzione denominata Utilizza solo il
catalogo del fornitore di servizio
Nelle versioni precedenti di CA Unicenter Service Catalog, l'opzione Utilizza solo
il catalogo del fornitore di servizio della configurazione era disponibile per
l'Unità di business principale (livello più alto) e per tutte le Unità di business
secondarie.
Con CA Unicenter Service Catalog 12.6, l'opzione Utilizza solo il catalogo del
fornitore di servizio è disponibile soltanto per l'Unità di business principale e
non per le Unità di business secondarie.
Per impostare questa opzione, eseguire l'accesso in qualità di amministratore di
Service Delivery (denominato, per impostazione predefinita, spadmin). È
possibile impostare l'opzione facendo clic su Generatore di servizi,
Configurazione, quindi sull'opzione Configurazione di sistema.
Prima di eseguire l'aggiornamento a CA Unicenter Service Catalog 12.6,
accedere a tutte le Unità di business principali per verificare se l'opzione Utilizza
solo il catalogo del fornitore di servizio è impostata su Sì o su No. Registrare le
impostazioni come riferimento, quindi stabilire quale valore utilizzare come
impostazione da applicare a tutto il sistema al fine di soddisfare le esigenze della
propria azienda. Nelle versioni precedenti, il parametro veniva visualizzato e
impostato facendo clic su Generatore di servizi, Configurazione, Configurazione
catalogo.
Dopo aver eseguito l'aggiornamento a CA Unicenter Service Catalog 12.6,
eseguire l'accesso come amministratore di Service Delivery e impostare il valore
facendo clic su Generatore di servizi, Configurazione, Sistema. Il valore
impostato viene applicato all'intero sistema di catalogo, ovvero a tutte le Unità
di business.
Per ulteriori informazioni sulle opzioni di configurazione, compresa l'opzione
Utilizza solo il catalogo del fornitore di servizio, consultare la Implementation
Guide.
26 Note di rilascio
Capitolo 4: Documentazione
Documentazione (a pagina 27)
CA Bookshelf (a pagina 28)
File Leggimi (a pagina 29)
Numeri di versione sulla documentazione (a pagina 29)
Documentazione
CA Unicenter Service Catalog fornisce le seguenti guide in formato HTML e PDF:
■
Implementation Guide (Guida all'implementazione)
■
Guida all'amministrazione
■
Integration Guide (Guida all'integrazione)
■
Note di rilascio
■
Reference Guide (Guida di riferimento)
■
File leggimi (se necessario)
■
CA MDB Overview (Panoramica di CA MDB)
■
CA Business Intelligence Implementation Guide (Guida all'implementazione
di CA Business Intelligence)
■
CA Workflow API Reference Guide (Guida di riferimento di CA Workflow
API).
Per ottenere i migliori risultati, accedere alla guida tramite CA Bookshelf (a
pagina 28).
Nota: CA Oblicore Guarantee e Reservation Manager sono due nuove
integrazioni aggiuntive di CA Unicenter Service Catalog. Per ottenere
informazioni sull'integrazione tra CA Unicenter Service Catalog e i prodotti in
questione, consultare la Integration Guide. Per ulteriori dettagli su CA Oblicore
Guarantee e Reservation Manager, consultare la relativa documentazione.
Capitolo 4: Documentazione 27
CA Bookshelf
CA Bookshelf
CA Bookshelf fornisce tutta la documentazione (a pagina 27)del prodotto sia in
formato PDF che HTML, conformemente alla sezione 508. Utilizzando CA
Bookshelf è possibile:
■
Visualizzare e ricercare le singole guide in formato HTML o PDF.
■
Utilizzare il campo Ricerca in alto a destra di CA Bookshelf per ricercare
tutte le guide in formato HTML.
Nota: questa opzione è applicabile esclusivamente alle guide in lingua
inglese, non a quelle localizzate.
■
Utilizzare Versione per la stampa per visualizzare, ricercare e stampare le
singole guide tramite Adobe Reader. Se Adobe Reader non è installato,
utilizzare il collegamento per il download di Adobe Reader nella sezione
Altre informazioni di CA Bookshelf per eseguire il download e installare
Adobe Reader.
Per ottenere CA Bookshelf, effettuare una delle seguenti operazioni:
■
Installare CA Unicenter Service Catalog. Il supporto di installazione di CA
Unicenter Service Catalog consente di installare CA Bookshelf
automaticamente.
■
Copiare l'intera sottocartella \locale dal supporto di installazione oppure
dall'installazione del prodotto sul proprio computer locale.
■
Eseguire il download ed estrarre la versione compressa (WinZip) di CA
Bookshelf dal supporto online CA.
Per aprire il Bookshelf dalla GUI di CA Unicenter Service Catalog, selezionare
Amministrazione, Strumenti. Nella pagina Strumenti, fare clic su Collegamenti
(in Menu). Nella pagina Collegamenti, selezionare Richieste, Bookshelf.
Per aprire il Bookshelf al di fuori dalla GUI di CA Unicenter Service Catalog,
eseguire una delle seguenti operazioni:
■
Se si utilizza il browser Microsoft Internet Explorer, fare doppio clic sul file
Bookshelf.hta.
■
Se si utilizza il browser Mozilla Firefox o Safari, fare doppio clic sul file
Bookshelf.hml.
■
Fare clic sul collegamento CA Bookshelf nella sezione CA Unicenter Service
Catalog del menu Start di Windows.
La documentazione aggiornata di CA Unicenter Service Catalog è disponibile
all'indirizzo http://ca.com/smb/support.
28 Note di rilascio
File Leggimi
File Leggimi
La documentazione di CA Unicenter Service Catalog include sempre un file delle
Note di rilascio.
Tuttavia, un file Leggimi è facoltativo e viene incluso solo se è necessario
apportare modifiche dell'ultimo minuto.
Al momento della pubblicazione, CA Unicenter Service Catalog non richiede né
include nessun file Leggimi.
Numeri di versione sulla documentazione
Il numero di versione sulla pagina iniziale del documento potrebbe non
corrispondere al numero di versione del prodotto corrente, tuttavia tutta la
documentazione fornita con il prodotto, indipendentemente dal
numero indicato sulla pagina del titolo è compatibile con l'utilizzo della versione
del prodotto corrente. Il numero di versione viene modificato solamente
quando si apportano cambi significativi alla documentazione, validi per l'uso di
una versione di un prodotto nuovo o aggiornato. Quando non vengono
apportati cambi significativi, il numero di versione non viene modificato. Ad
esempio, un documento utilizzato per la versione r12 può essere valido anche
per le versioni r12.5 o r12.6. I bookshelf della documentazione riportano
sempre il numero di versione del prodotto corrente.
A volte è necessario aggiornare la documentazione in un momento successivo
ad un rilascio o un aggiornamento. Per indicare una modifica minore apportata
alla documentazione valida per tutte la versioni supportate,viene aggiornato il
numero di edizione riportato sulla copertina. La prima edizione non riporta
alcun numero.
Capitolo 4: Documentazione 29
Capitolo 5: Informazioni di sistema
Supporto del sistema operativo (a pagina 31)
Requisiti di sistema (a pagina 31)
Requisiti hardware (a pagina 33)
Requisiti software (a pagina 35)
Integrazioni facoltative con altri prodotti CA (a pagina 38)
Requisiti del client (a pagina 39)
Supporto del sistema operativo
CA Unicenter Service Catalog supporta i seguenti sistemi operativi per i
componenti di applicazione e i sistemi di gestione del database:
■
Microsoft Windows Server 2008 – Standard e Enterprise
■
Microsoft Windows Server 2008 R2 - Standard e Enterprise
Nota: per ulteriori informazioni su sistemi operativi o service pack aggiuntivi
supportati dopo GA, consultare la Matrice di certificazione per CA Unicenter
Service Catalog alla pagina http://ca.com/it/support.
Requisiti di sistema
Per l'installazione e l'esecuzione di CA Unicenter Service Catalog è necessario
soddisfare tali requisiti.
Capitolo 5: Informazioni di sistema 31
Requisiti di sistema
Browser
I seguenti browser consentono l'accesso a CA Unicenter Service Catalog da
computer desktop e laptop:
■
Microsoft Internet Explorer 7.0 o 8.0 con la versione di service pack più
recente
■
Mozilla Firefox 3.5
■
Apple Safari 3.5 su Windows.
L'accesso a CA Unicenter Service Catalog mediante dispositivi palmari è
disponibile con i seguenti browser:
32 Note di rilascio
■
Browser Blackberry su smartphone Blackberry
■
Browser Safari su iPhones
Requisiti hardware
Database
Al momento della pubblicazione, CA Unicenter Service Catalog supporta i
seguenti software DBMS.
Importante Se si sta utilizzando una versione di Oracle o SQL Server non
supportata dalla versione r12.6 di CA Unicenter Service Catalog, è necessario
eseguire il back up del database ed installare una versione supportata del
software DBMS prima di installare la versione r12.6 di CA Unicenter Service
Catalog. In alcuni casi, invece di eseguire l'aggiornamento della vecchia versione
DBMS direttamente a una versione supportata, è necessario disinstallare
l'attuale versione DBMS e installare quella nuova come installazione
completamente nuova. Per ulteriori informazioni, consultare la documentazione
di DBMS.
■
MS SQL Server Enterprise Edition 2005
■
MS SQL Server Enterprise Edition 2008
■
Oracle 10g R2 o 11g R2 in esecuzione su server Windows, Solaris o Linux:
–
Oracle 10g R2 o 11g R2 (32 bit) su un server Windows
–
Oracle 10g R2 o 11g R2 (64 bit) su un server Windows
–
Oracle 10g R2 o 11g R2 (32 bit) in esecuzione su RedHat Linux 4.0
Advanced Server (32 bit)
–
Oracle 10g R2 o 11g R2 (64 bit) in esecuzione su RedHat Linux 4.0
Advanced Server (64 bit)
–
Oracle 10g R2 (64 bit) in esecuzione su Solaris SPARC (64 bit)
–
Oracle 11g R2 (64 bit) in esecuzione su Solaris SPARC (64 bit)
Nota: per ulteriori informazioni su versioni o service pack aggiuntivi supportati
dopo GA, consultare la Matrice di certificazione per CA Unicenter Service
Catalog alla pagina http://ca.com/it/support.
Requisiti hardware
Prima di installare CA Unicenter Service Catalog, i relativi componenti e il
software DBMS, verificare i requisiti hardware del proprio computer.
Requisiti hardware
Requisiti hardware per l'installazione standalone
Importante In un'installazione standalone, CA Unicenter Service Catalog, CA
Service Accounting e CA Workflow vengono installati su un unico computer.
Eseguire un'installazione standalone è possibile, ma non consigliato.
Un'installazione standalone è adatta solo ai seguenti scopi: gestione
temporanea, sviluppo, prova di concetti e verifica. Un'installazione standalone
non è consigliata per la produzione.
Requisiti hardware per un'installazione autonoma:
■
CPU: Intel Platform, processore 3 GHz o superiore, consigliato Multiprocessor
■
Memoria: consigliati 4 GB o superiore
■
Disco rigido: minimo da 80 GB con almeno 4 GB di spazio libero. La quantità
di spazio libero richiesto dipende dal numero di file di registro e dalla
quantità di dati da memorizzare nel database.
Preferita unità disco rigido SCSI ad alta velocità (Ultra 3 SCSI)
Requisiti hardware per l'installazione distribuita
Importante Per la produzione, è fortemente consigliato eseguire
un'installazione distribuita. In un'installazione distribuita, si installano tutti i
server delle applicazioni CA richiesti su un computer diverso. Ad esempio, si
installa CA Unicenter Service Catalog sul server 1, CA Workflow o CA IT PAM sul
server 2 e CA Service Accounting sul server 3. Si installa il software del server
DBMS sul server 4.
Requisiti hardware per ogni computer in un'installazione distribuita:
■
CPU: Intel Platform, processore 3 GHz o superiore, consigliato Multiprocessor
■
Memoria: almeno 2 GB, consigliati 4 GB o un valore superiore
■
Disco rigido: almeno da 40 GB con 4 GB o un valore superiore di spazio
libero. La quantità di spazio libero richiesto dipende dal numero di file di
registro.
Preferita unità disco rigido SCSI ad alta velocità (Ultra 3 SCSI)
Nota: per la tolleranza di errore e la scalabilità, è possibile installare
facoltativamente più server Service View.
34 Note di rilascio
Requisiti software
Ulteriori informazioni:
Considerazioni e requisiti di distribuzione (a pagina 43)
Requisiti hardware per server DBMS
Vengono applicati i seguenti requisiti hardware al computer sui cui si installa il
server software DBMS.
Installare il server software DBMS sul proprio server, non sullo stesso computer
dei server applicazioni CA richiesti.
Per la tolleranza di errore, si consiglia di configurare il server del database in un
ambiente cluster.
■
CPU: Intel Platform, processore 3 GHz o superiore, fortemente consigliato
Multi-processor
■
Memoria: almeno 4 GB RAM, consigliati 8 GB o un valore superiore
■
Disco rigido: almeno 80 GB. La quantità di spazio libero richiesta dipende
dalla quantità di dati da memorizzare.
■
Preferita unità disco rigido SCSI ad alta velocità (Ultra 3 SCSI). Preferita
configurazione di array RAID 5
Requisiti software
Prima di installare CA Unicenter Service Cataloge i relativi componenti,
verificare i requisiti software del proprio computer.
Requisiti software per server Web
Il software del server Web per CA Unicenter Service Catalog corrisponde a
Apache Tomcat, versione 5.5.29, contenuto in CA Unicenter Service Catalog.
Requisiti software
Bilanciatori di carico
CA Unicenter Service Catalog consente l'uso di un bilanciatore di carico.
Il bilanciatore di carico fornito con CA Unicenter Service Catalog è il server Web
Apache per la versione 2.2.16 di Windows.
CA Unicenter Service Catalog consente l'uso di questo bilanciatore o di un altro.
Se si usa un altro bilanciatore di carico, è necessario che venga supportata
l'affinità di sessione (sessioni associate).
Requisiti software per il server del database
I requisiti software per il componente server del database sono inclusi in
Database (a pagina 33).
Ulteriori informazioni:
Requisiti hardware per server DBMS (a pagina 35)
Requisiti software per l'ambiente Runtime
Requisiti software per l'ambiente runtime:
36 Note di rilascio
■
Java Runtime Environment (JRE) 1.6.0_20 (incluso con CA Unicenter Service
Catalog)
■
Open Message Queue versione 4.1 (inclusa con CA Unicenter Service
Catalog)
Requisiti software
Requisiti software per i componenti CA comuni
Sono richiesti i seguenti componenti CA comuni, inclusi nel supporto di
installazione di CA Unicenter Service Catalog:
■
CA Management Database (CA MDB) r1.5 SP2
■
CA EEM r8.4 SP4
Importante CA Unicenter Service Catalog richiede CA EEM
(precedentemente denominato eIAM) r8.4 SP4. Per le ultime informazioni di
certificazione per CA Unicenter Service Catalog, CA Service Accounting, CA
EEM, e relativi prodotti e componenti CA, consultare la matrice di
certificazione per ciascun prodotto o componente sul sito Web
http://ca.com/support.
Il seguente componente comune CA è facoltativo ed è incluso nel supporto di
installazione di CA Unicenter Service Catalog:
■
CA Workflow 1.1.5 SP6
Importante L'aggiornamento di CA Unicenter Service Catalog richiede anche
l'aggiornamento di CA Workflow se è stato utilizzato nella versione
precedente. L'aggiornamento di CA Workflow consente di continuare ad
utilizzarlo con CA Unicenter Service Catalog e facilita il trasferimento da CA
Workflow allo strumento di automatizzazione di processo consigliato, CA IT
PAM.
Nota: per ulteriori informazioni sull'installazione di CA EEM, CA MDB e CA
Workflow, consultare la Implementation Guide.
Integrazioni facoltative con altri prodotti CA
Integrazioni facoltative con altri prodotti CA
È inoltre possibile integrare CA Unicenter Service Catalog con i seguenti prodotti
CA:
■
■
I prodotti CA forniti con il proprio supporto di installazione e con quello di
CA Unicenter Service Catalog sono i seguenti:
–
BusinessObjects Enterprise 3.2
–
CA IT PAM 3.0, aggiornato al livello di patch corrente
I prodotti CA forniti con il proprio supporto di installazione e non inclusi con
quello di CA Unicenter Service Catalog sono i seguenti:
–
CA CMDB r12.1
–
CA Service Desk Manager r11.2, r12,1
–
CA Service Desk Manager r12.5, che include CA CMDB
–
CA APM r11.3.4 CP8
–
CA Oblicore Guarantee 7
–
Reservation Manager: componente Reservation Manager di CA
Spectrum Automation Manager r12
–
CA SiteMinder r12 SP1
–
CA Storage Resource Manager
–
CA MICS o JARS
Nota: per istruzioni relative all'installazione di tali prodotti, consultare la
documentazione del prodotto. Per istruzioni relative alle modalità di
configurazione e di utilizzo di tali prodotti con CA Unicenter Service Catalog,
consultare la Integration Guide e la Implementation Guide.
38 Note di rilascio
Requisiti del client
I client CA Unicenter Service Catalog devono soddisfare i seguenti requisiti:
■
Se, quando la si visita, non vengono visualizzati gli aggiornamenti su una
pagina Web, sarà necessario verificare e configurare le impostazioni della
memoria cache del browser affinché ogni volta che si visita la pagina Web
vengano visualizzati gli aggiornamenti dal server.
■
Su Windows 2003, l'impostazione di protezione predefinita di Internet
Explorer (IE) per la zona di contenuto Internet è impostata su Alta. Per
aprire Service View, è necessario modificare l'impostazione di protezione
per IE su Media e aggiungere il sito all'elenco dei siti attendibili.
■
Per visualizzare i report contenenti grafici ed avviare lo strumento di
progettazione del flusso di lavoro a partire dall'interfaccia Web è necessario
disporre di Java Runtime Environment. (a pagina 36) In entrambi i casi, se
JRE non è installato, verrà richiesto di scaricarlo.
Se si desidera installare Java Runtime Environment manualmente su un
computer client, andare all'URL:
http://<hostname>:<portnumber>/usm/jreinst/install.htm (dove hostname
indica il nome di qualsiasi server Service View).
■
È richiesto OpenViz Viewer nel caso in cui il client sia impostato per
visualizzare rapporti con grafici. Qualora non sia installato, verrà scaricato
automaticamente sul sistema client.
■
È richiesto Microsoft Outlook View Control nel caso in cui un portale si
connetta a MS Outlook da un sistema client.
Nota: per ulteriori informazioni, visitare il sito Web
http://activex.microsoft.com
■
È richiesto Microsoft Office Web Components nel caso in cui un portale si
connetta a MS Office da un sistema client.
Nota: per ulteriori informazioni, visitare il sito Web
http://office.microsoft.com
■
Per visualizzare correttamente i simboli e i caratteri a doppio byte mentre si
utilizza Microsoft Internet Explorer 6.0 SP2 o versione successiva, impostare
il browser su Unicode UTF8. Dal browser di IE, selezionare Visualizza,
Codifica caratteri, Unicode (UTF8)
■
Per visualizzare alcuni simboli di valuta (ad esempio, lo Won coreano), è
necessario installare le seguenti famiglie di caratteri sul computer client:
■
Arial Unicode MS
■
Tahoma
■
Vengono utilizzati diversi controlli con firma, impiegati nelle seguenti aree:
■
Dashboard.cab – Contiene i componenti per gli elementi relativi a
dashboard/portale (per IE).
■
Print.cab – Contiene il componente della stampa (per IE).
■
Print.jar - Contiene il componente della stampa (per browser non di IE).
■
Chart.jar - Utilizzato dal componente del reporting
I file jar in %USM_HOME%\fulfillment\webapps\usm_idews vengono
utilizzati dall'avvio JPNL dello strumento di definizione del processo di
CA Workflow
■
40 Note di rilascio
Vengono utilizzati i seguenti controlli con firma per richiamare lo strumento
di definizione del processo utilizzando l'avvio Web:
■
Safe.jar
■
axis.jar
■
IDEHelp.jar
■
branding.jar
■
jaxrpc.jar
■
commons-discovery.jar
■
jhall.jar
■
commons-logging.jar
■
log4j-1.2.8.jar
■
DefaultIcons.jar
■
saaj.jar
■
dom4j-full.jar
■
xercesImpl.jar
■
IDE.jar
■
xml-apis.jar
Capitolo 6: Considerazioni e requisiti per
installazioni e aggiornamenti
La presente sezione contiene importanti informazioni relative a nuove
installazioni e aggiornamenti.
Per nuove installazioni in ambienti di produzione, si consiglia di installare i
prodotti e i componenti CA Unicenter Service Catalog su almeno tre computer
distinti, come spiegato nella Implementation Guide.
Nota: per informazioni complete su tali requisiti e sui requisiti correlati,
consultare la Implementation Guide.
Considerazioni generali e requisiti (a pagina 41)
Considerazioni e requisiti di distribuzione (a pagina 43)
Considerazioni e requisiti di condivisione di rete (a pagina 43)
Considerazioni generali e requisiti
Le considerazioni e i requisiti di installazione seguenti si applicano generalmente
a tutte le implementazioni.
■
Installare Service View prima di qualsiasi altro prodotto o componente CA
Unicenter Service Catalog.
■
Verificare che tutti i computer CA Unicenter Service Catalog siano
geograficamente vicini, ossia che si trovino nello stesso edificio e nella
stessa stanza.
Il termine computer CA Unicenter Service Catalog indica principalmente il
server DBMS e qualsiasi altro computer su cui si desidera installare un
prodotto o un componente CA Unicenter Service Catalog, inclusi CA EEM,
CA Workflow e altri prodotti o componenti CA inclusi sul supporto di
installazione di CA Unicenter Service Catalog.
L'associazione geografica di tutti i computer CA Unicenter Service Catalog
consente di prevenire eventuali problemi di prestazione, causati da una
latenza di rete.
■
Verificare che il computer su cui si desidera installare un componente CA
Unicenter Service Catalog o l'MDB soddisfi i requisiti di sistema applicabili.
Capitolo 6: Considerazioni e requisiti per installazioni e aggiornamenti 41
Considerazioni generali e requisiti
■
Prima di eseguire l'aggiornamento, annotare il valore di tutte le
impostazioni dell'opzione Utilizza solo il catalogo del fornitore di servizio (a
pagina 26) per tutte le Unità di business dell'implementazione e stabilire
quali utilizzare come impostazione di sistema di CA Unicenter Service
Catalog 12.6. Dopo aver eseguito l'aggiornamento, impostare il parametro
in base alla propria scelta.
■
Prima di effettuare l'aggiornamento da una versione precedente di CA
Unicenter Service Catalog a r12.6, eseguire il backup completo del sistema.
Analogamente, dopo aver installato la versione r12,6, eseguire il backup
completo del sistema prima di eseguirne la migrazione da test a produzione.
■
Accedere al sistema utilizzando l'account Amministratore.
■
Si consiglia vivamente di non aggiungere, eliminare utenti o di modificare le
informazioni degli utenti tramite l'interfaccia utente di CA EEM. Utilizzare,
invece, le interfacce utente di Service View, le quali consentono
l'integrazione con CA EEM e l'aggiornamento corrispondente di CA EEM.
■
Se si esegue l'installazione su un computer Windows 2008 con Terminal
Server, assicurarsi di chiudere le finestre di dialogo dopo aver installato
ciascun prodotto e componente CA Unicenter Service Catalog. In caso
contrario, il successivo tentativo di installazione di un prodotto o
componente CA Unicenter Service Catalog potrebbe avere esito negativo.
■
L'Utente applicazione viene creato automaticamente al termine
dell'installazione.
L'utente del prodotto CA Unicenter Service Catalog denominato spadmin
viene automaticamente creato come un utente di prodotto. Anche la
password per questo utente è spadmin.
42 Note di rilascio
■
L'installazione di Service View richiede il riavvio prima di poter essere
completata.
■
Dopo aver completato l'aggiornamento, verificare che gli eventi, le regole e
le azioni abilitati prima dell'aggiornamento siano ancora attivi.
Considerazioni e requisiti di distribuzione
Considerazioni e requisiti di distribuzione
Quando si installano prodotti e componenti CA Unicenter Service Catalog su più
computer (implementazione distribuita), i seguenti requisiti devono essere
soddisfatti:
■
Il primo prodotto o componente CA Unicenter Service Catalog che si installa
su un computer deve essere Service View.
■
CA Service Accounting e CA Workflow possono essere installati su computer
diversi da Service View. Tuttavia, CA Unicenter Service Catalog e il
contenuto del catalogo possono essere installati solo sul primo (in
precedenza denominato primario) computer Service View.
■
Su qualsiasi computer su cui si installano Service View, CA Unicenter Service
Catalog, il contenuto del catalogo, CA Workflow o CA Service Accounting, è
necessario installare anche il server DBMS o il client DBMS. Questi requisiti
si applicano sia a SQL Server sia Oracle.
Importante Per utilizzare CA IT PAM come strumento di automazione del
processo e garantire le migliori prestazioni di sistema, non installare
l'agente di orchestrazione del dominio CA IT PAM e i componenti CA IT PAM
sullo stesso computer.
Considerazioni e requisiti di condivisione di rete
Se l'immagine dell'installazione si trova in condivisione di rete, è necessario
mappare una lettera dell'unità su questa condivisione. I file batch non sono
eseguibili da un percorso UNC.
Per ottenere i migliori risultati, copiare l'immagine di installazione in una cartella
in locale ed eseguire i programmi di installazione in locale.
Capitolo 6: Considerazioni e requisiti per installazioni e aggiornamenti 43
Capitolo 7: Considerazioni generali
Supporto internazionale (a pagina 45)
Considerazioni per prevenire la duplicazione di eventi, regole e azioni (a pagina
47)
Considerazioni sulla localizzazione (a pagina 49)
Correzioni pubblicate (a pagina 50)
Supporto internazionale
Un prodotto internazionalizzato è un prodotto in lingua inglese che viene
eseguito correttamente sulle versioni in lingua locale del sistema operativo e sui
prodotti di terze parti richiesti e che supporta i dati di input e di output in lingua
locale. I prodotti internazionalizzati consentono inoltre di specificare le
convenzioni della lingua locale per i formati di data, ora, valuta e numeri.
Un prodotto tradotto (a cui si fa riferimento anche come prodotto localizzato) è
un prodotto internazionalizzato che include il supporto in lingua locale per
l'interfaccia utente, la Guida in linea ed altra documentazione relativa al
prodotto, nonché le impostazioni predefinite in lingua locale per i formati di
data, ora, valuta e numeri.
Oltre alla versione inglese del prodotto, CA supporta solo le seguenti lingue.
Lingua
Internazionalizzato
Tradotto
Portoghese brasiliano
Sì
Sì
Cinese semplificato
No
No
Cinese tradizionale
No
No
Ceco
No
No
Finlandese
No
No
Francese
Sì
Sì
Tedesco
Sì
Sì
Greco
No
No
Ungherese
No
No
Capitolo 7: Considerazioni generali 45
Supporto internazionale
Lingua
Internazionalizzato
Tradotto
Italiano
Sì
Sì
Giapponese
Sì
No
Coreano
No
No
Norvegese
No
No
Polacco
No
No
Russo
No
No
Spagnolo
Sì
Sì
Svedese
No
No
Turco
No
No
Nota: se il prodotto viene eseguito in ambienti la cui lingua non è riportata
nell'elenco, è possibile che si verifichino problemi.
46 Note di rilascio
Considerazioni per prevenire la duplicazione di eventi, regole e azioni
Considerazioni per prevenire la duplicazione di eventi, regole e
azioni
CA Unicenter Service Catalog supporta sia CA IT PAM che CA Workflow come
strumenti di automazione dei processi. Lo strumento preferenziale è CA IT PAM,
ma è possibile utilizzare anche solo CA Workflow oppure i due strumenti
contemporaneamente. È inoltre possibile adottare un metodo misto, ossia
utilizzare CA Workflow per l'approvazione e CA IT PAM per l'esecuzione; tale
metodo può risultare particolarmente utile se si sta eseguendo l'aggiornamento
da una versione precedente di CA Unicenter Service Catalog e si desidera
passare gradualmente da CA Workflow a CA IT PAM.
In ogni caso, indipendentemente dall'approccio scelto, considerare
attentamente quanto riportato di seguito, per assicurarsi che l'implementazione
non duplichi eventi, regole e azioni durante l'elaborazione della richiesta. In
caso contrario, gli utenti potrebbero ricevere messaggi duplicati in merito ai
cambiamenti di stato delle richieste oppure richieste di approvazione o
esecuzione duplicate.
■
Verificare le regole relative ai propri strumenti di automazione dei processi.
Assicurarsi che le regole che si desidera utilizzare siano abilitate e che le
altre siano disabilitate.
■
L'esecuzione del comando dei dati codice consente di caricare le regole di
CA Unicenter Service Catalog e le azioni corrispondenti relative al contenuto
CA IT PAM, come riportato nella sezione Caricamento e configurazione del
contenuto di CA IT PAM. Se, prima di eseguire il comando, si dispone già di
regole e azioni configurate e abilitate per CA Workflow, l'esecuzione del
comando potrebbe causare la duplicazione di regole e azioni.
In tal caso, quindi, rivedere le singole regole e azioni e decidere se abilitarle
solo per CA IT PAM o per CA Workflow, ma non per entrambi.
–
Per gli aggiornamenti di CA Unicenter Service Catalog, le azioni delle
regole CA IT PAM sono disabilitate per impostazione predefinita. Per
poterle utilizzare, è necessario abilitarle manualmente.
–
Per le nuove installazioni di CA Unicenter Service Catalog, le azioni delle
regole CA IT PAM sono abilitate per impostazione predefinita, pertanto
non è necessario abilitarle manualmente. Le regole CA IT PAM per le
esecuzioni complesse, invece, sono disabilitate e sarà necessario
abilitarle manualmente per l'utilizzo.
Per informazioni dettagliate sulla configurazione, l'abilitazione e la
disabilitazione delle regole, consultare la Guida all'amministrazione.
Considerazioni per prevenire la duplicazione di eventi, regole e azioni
■
■
48 Note di rilascio
Quando CA Unicenter Service Catalog viene installato (non aggiornato) per
la prima volta e si sceglie di installare CA Workflow anziché CA IT PAM,
disabilitare le regole di notifica per non ricevere messaggi di posta
elettronica duplicati quando una richiesta passa attraverso il flusso di
approvazione. Sarà, quindi, necessario disabilitare le regole seguenti per
l'evento denominato Cambiamento elemento Richiesta/Sottoscrizione:
–
Quando lo stato è Approvato
–
Quando lo stato è Eseguito
–
Quando lo stato è Esecuzione annullata
–
Quando lo stato di trova nell'intervallo In attesa di esecuzione
–
Quando lo stato è In attesa di approvazione
–
Quando lo stato è Rifiutato
Completare tutte le attività per configurare l'integrazione di CA Unicenter
Service Catalog con CA IT PAM, CA Workflow, o entrambi, incluse le attività
di configurazione successive all'installazione. Per i dettagli, consultare la
Integration Guide.
Considerazioni sulla localizzazione
Considerazioni sulla localizzazione
Per le integrazioni di prodotti con CA Unicenter Service Catalog, inclusi altri
prodotti e componenti CA comuni, ed i prodotti di terze parti, consultare la
documentazione e le altre risorse disponibili per il prodotto o il componente per
sapere se ne esistono versioni localizzate. Ad esempio, per informazioni relative
alla localizzazione di BusinessObjects Enterprise, consultare la documentazione
e le altre risorse disponibili per BusinessObjects Enterprise.
Quando si visualizzano report di BusinessObjects Enterprise in formato
localizzato, i seguenti elementi rimangono in inglese:
■
Alcuni campi, inclusi quelli relativi allo stato della richiesta, allo stato della
fatturazione, allo stato del conto, al tipo di conto, ai pagamenti e alle
rettifiche
■
Nomi di utenti, gruppi e report
■
Alcuni prompt, opzioni di menu e altri dati richiamati dal database
■
Nomi di valute e fusi orari
Inoltre, sia nella versione inglese che in quelle localizzate, i valori di stato
personalizzati vengono visualizzati ma non le descrizioni corrispondenti.
Come rimedio provvisorio, è possibile:
■
Localizzare l'elenco dei prompt relativi a valori e dati dei report (a
pagina 49)
■
Localizzare i nomi di utenti, gruppi e report (a pagina 50)
Localizzare l'elenco dei prompt relativi a valori e dati dei report
Se l'elenco di valori (LOV) del prompt e i dati dei report non sono localizzati, è
possibile procedere alla localizzazione manuale.
Per localizzare l'elenco di valori e i dati dei report del prompt:
1. Aprire l'applicazione Universe Designer.
2. Importare l'universo SLCM.
3. Verificare di poter visualizzare tutte le classi e gli oggetti.
4. Fare doppio clic sull'oggetto che si desidera modificare.
Correzioni pubblicate
5. Fare clic sulla scheda Definizione.
6. Nell'area di selezione testo della scheda Destinazione, sostituire il testo in
inglese con il testo localizzato.
Ad esempio, per lo stato di un account, supponiamo di voler localizzare le
proprietà dell'oggetto Stato della classe Dettagli account (amministratore).
Per impostazione predefinita, l'area di selezione testo della scheda
Definizione dell'oggetto contiene il seguente testo in inglese:
case DT_Account_Details.status when 0 then 'Closed' when 1 then 'Open' when 2
then 'Suspended' when 3 then 'Closed Requested' end
Per localizzare il testo, procedere come segue:
case DT_Account_Details.status when 0 then 'stringa Closed localizzata' when
1 then 'stringa Open localizzata' when 2 then 'Stringa Suspended localizzata'
when 3 then 'stringa Closed Requested localizzata' end
Ad esempio, per tedesco, il testo potrebbe essere localizzato come segue:
case DT_Account_Details.status when 0 then 'Geschlossen' when 1 then
'Geöffnet' when 2 then 'Ausgesetzt' when 3 then 'Schliessen Angeforderten'
end
7. Fare clic su OK per salvare le modifiche.
Le modifiche verranno apportate nelle colonne, nei dati, negli elenchi di
valori e nei report relativi.
8. Esportare l'universo.
Localizzare i nomi di utenti, gruppi e report
È possibile localizzare i nomi di report, utenti e gruppi per consentire agli utenti
di BusinessObjects Enterprise di visualizzarli nella propria lingua.
Per rinominare un oggetto, selezionarlo e rinominarlo, sostituendo il nome in
inglese con il nome localizzato. Per ulteriori informazioni, consultare la
documentazione di BusinessObjects Enterprise.
Correzioni pubblicate
Tutte le correzioni pubblicate per questo prodotto si possono trovare, tramite
supporto tecnico, sul sito http://ca.com/it/support.
50 Note di rilascio
Capitolo 8: Aggiornamenti della
documentazione
Al momento della pubblicazione di GA non sono disponibili aggiornamenti della
documentazione.
Gli aggiornamenti della documentazione di CA Unicenter Service Catalog dopo
GA sono disponibili alla pagina http://ca.com/it/support.
Capitolo 8: Aggiornamenti della documentazione 51
Capitolo 9: Problemi noti
Restituzione di dati corrotti da parte di Oracle DBMS (a pagina 54)
Impedire la visualizzazione di messaggi di avviso falsi correlati al ruolo di
Gestione servizio (a pagina 54)
Riavvio del computer dopo la migrazione (a pagina 55)
Azioni disabilitate dopo l'aggiornamento (a pagina 55)
Azione CA IT PAM disattivata (a pagina 55)
Impossibile accedere a CA EEM dopo l'aggiornamento (a pagina 56)
Impossibile installare l'applicazione CA EEM (a pagina 56)
Impossibile assegnare modelli CA AMP (a pagina 57)
Integrazione con CA APM utilizzando Oracle (a pagina 58)
Impossibile creare ordini di cambiamento quando Multi-Tenancy è attivo (a
pagina 58)
Non spostare i titolari (a pagina 59)
Valori mancanti dai report (a pagina 59)
Ricreare periodi di anni fiscali dopo la migrazione (a pagina 59)
Campi numerici nei sistemi operativi localizzati (a pagina 59)
Non è possibile installare Service View e il server Oracle insieme (a pagina 60)
Stato di disponibilità delle cartelle (a pagina 60)
Campi nvarchar nei rapporti (a pagina 60)
Cartelle rimanenti al termine della disintallazione (a pagina 60)
Distinzione tra maiuscole e minuscole per CA MDB su Oracle (a pagina 61)
Impossibile generare rapporti non in linea in formato PDF (a pagina 61)
Problemi con la sospensione di un servizio sottoscritto (a pagina 61)
I collegamenti ipertestuali ai siti Web non CA potrebbero non funzionare (a
pagina 61)
Può apparire il sommario della guida al posto dell'argomento specifico della
guida. (a pagina 62)
Le richieste completate e annullate possono essere bloccate (a pagina 62)
L'aggiornamento MDB potrebbe non riuscire durante l'aggiornamento di Service
View (a pagina 62)
L'esecuzione di ulteriori tentativi per le azioni non riuscite non funziona (a
pagina 63)
Campi mancanti nell'IDE di CA Workflow con JNLP su Macintosh (a pagina 63)
Messaggi di avviso del sistema sempre in lingua inglese (a pagina 63)
La stampa batch non va a buon fine con Mozilla Firefox (a pagina 64)
Le celle appaiono di grandi dimensioni con Apple Safari (a pagina 64)
Decidere come elaborare le cifre per lo Yen (a pagina 64)
Capitolo 9: Problemi noti 53
Restituzione di dati corrotti da parte di Oracle DBMS
Restituzione di dati corrotti da parte di Oracle DBMS
Importante Se si utilizza Oracle DBMS con CA Unicenter Service Catalog, CA IT
PAM e altri prodotti CA, il database potrebbe restituire dati corrotti.
Al momento della pubblicazione, i numeri identificativi dei problemi riportati dal
supporto Oracle sono i seguenti:
■
9004101
■
9347941
■
5635254
■
8588311
■
9047803
Per una risoluzione temporanea dei problemi, attenersi ad una delle modalità
seguenti:
■
Consultare il supporto Oracle per soluzioni relative all'installazione e alla
distribuzione di CA Unicenter Service Catalog, CA IT PAM, e altri prodotti CA.
■
Utilizzare Microsoft SQL Server come DBMS per CA Unicenter Service
Catalog, CA IT PAM e altri prodotti CA
Impedire la visualizzazione di messaggi di avviso falsi correlati
al ruolo di Gestione servizio
I messaggi di avviso vengono visualizzati su un utente con un ruolo di gestione
servizio gestisce una richiesta in attesa di azione, come ad esempio
l'approvazione o il rifiuto di richieste. In questi casi, la gestione delle
approvazioni e dei rifiuti verrà eseguita correttamente anche nel caso in cui
vengano visualizzati messaggi di avviso. Per fare in modo che tali messaggi non
vengano visualizzati, gli amministratori possono eseguire le seguenti operazioni:
1. Accedere a CA Unicenter Service Catalog come amministratore di Service
Delivery o come amministratore dell'Unità di business.
2. Per modificare i diritti di accesso predefiniti del ruolo di Gestione servizio
per un'Unità di business specifica, eseguire l'accesso a tale Unità di business,
selezionare Generatore di servizi, Configurazione, quindi aggiungere
l'impostazione Access Control: Aggiungi richiesta a tale ruolo.
3. Salvare le modifiche.
54 Note di rilascio
Riavvio del computer dopo la migrazione
Riavvio del computer dopo la migrazione
Dopo aver eseguito la migrazione a CA Unicenter Service Catalog da una
versione precedente, è necessario riavviare il computer e verificare che tutti i
servizi CA Unicenter Service Catalog installati siano avviati. Tali servizi sono CA
Service View, CA Service Fulfillment e CA Service Accounting.
Nota: per maggiori dettagli relativi alla migrazione, consultare la
Implementation Guide.
Azioni disabilitate dopo l'aggiornamento
Se lo stato di un'azione di tipo JAVA, Riga di comando o HTTP Post è disabilitato
prima dell'aggiornamento di CA Unicenter Service Catalog, durante
l'aggiornamento il tipo di azione passa a Sconosciuto. Se dopo l'aggiornamento
si abilita l'azione, CA Unicenter Service Catalog richiede di specificare
nuovamente il tipo.
Per informazioni relative ad eventi, regole e azoni, consultare la Guida
all'amministrazione e la Integration Guide.
Azione CA IT PAM disattivata
Se si esegue l'integrazione di CA Unicenter Service Catalog con CA IT PAM,
consultare la presente sezione. In caso contrario, ignorarla.
Le azioni CA IT PAM per le regole CA Unicenter Service Catalog sono attivate o
disattivate per impostazione predefinita nel modo che segue:
■
Sono disattivate per impostazione predefinita per gli aggiornamenti di CA
Unicenter Service Catalog
■
Sono attivate per impostazione predefinita per le nuove installazioni di CA
Unicenter Service Catalog
Tuttavia, anche nel caso di nuove installazioni, l'azione CA IT PAM è disattivata
per impostazione predefinita per la regola denominata Quando la categoria è
Software e lo stato è In attesa di esecuzione. Di conseguenza, per utilizzare
questa azione, è necessario attivarla manualmente. Questo requisito si applica
sia agli aggiornamenti che alle nuove installazioni di CA Unicenter Service
Catalog.
Impossibile accedere a CA EEM dopo l'aggiornamento
Impossibile accedere a CA EEM dopo l'aggiornamento
Dopo aver eseguito l'aggiornamento di CA EEM, potrebbero verificarsi dei
problemi di accesso. In genere, la causa è da individuare in una o più voci
duplicate nel file spin.conf. Si tratta di un file Itechnology Igateway utilizzato da
CA EEM.
Per risolvere il problema, adottare la procedura seguente:
1. Individuare il file spin.conf in %IGW_LOC%, la directory principale di
Itechnology Igateway.
2. Eseguire il backup del file spin.conf.
3. Aprire il file spin.conf e individuare la voce seguente:
<Spindle Description="Embedded IAM Interface" Directory=""
Prefix="/eiam" Spar="eiamSpindle.spar">eiamSpindle</Spindle>
Nel file deve essere presente una sola occorrenza della voce in questione.
4. Ricercare nel file le voci duplicate ed eliminarle.
5. Salvare il file.
Impossibile installare l'applicazione CA EEM
L'installazione dell'applicazione CA EEM può non riuscire per una o più delle
seguenti ragioni:
■
La lunghezza del nome dell'applicazione è superiore ai 25 caratteri
■
Il nome dell'applicazione contiene virgolette (“), virgola (,), barra (/), barra
rovesciata (\), cancelletto (#), E commerciale (&) o segno più (+)
In questi casi, correggere l'errore e tentare nuovamente di installare
l'applicazione CA EEM.
56 Note di rilascio
Impossibile assegnare modelli CA AMP
Impossibile assegnare modelli CA AMP
Se si esegue l'integrazione di CA Unicenter Service Catalog con CA APM,
consultare la presente sezione. In caso contrario, ignorarla.
CA Unicenter Service Catalog non è in grado di assegnare modelli CA APM nella
pagina Gruppo opzioni di servizio quando l'applicazione CA APM e i server Web
risiedono su computer differenti.
Per risolvere il problema, specificare le impostazioni di configurazione di
amministrazione per i servizi Web di CA APM in CA Unicenter Service Catalog.
Questa procedura è necessaria quando l'applicazione CA APM e i server Web
risiedono su computer differenti.
1. Nella scheda Amministrazione di CA Unicenter Service Catalog, fare clic su
Configurazione e accedere alla sezione Servizi Web di CA APM.
Vengono visualizzate le opzioni di configurazione CA APM.
2. Fare clic su Modifica (icona matita) in corrispondenza di ciascuna proprietà
da aggiornare, utilizzando le seguenti informazioni.
Abilita HTTPS
Consente di specificare un protocollo Web, come indicato di seguito.
Selezionare No (impostazione predefinita) per utilizzare il protocollo
HTTP per la comunicazione con CA APM.
Selezionare Sì per utilizzare il protocollo HTTPS per la comunicazione
con CA APM.
Importante se si seleziona Sì, verificare che CA APM utilizzi il protocollo
HTTPS. Se necessario, configurarlo in modo che utilizzi HTTPS. Per
informazioni dettagliate, consultare la documentazione di CA APM.
Nome host
Specifica il nome del computer sul quale viene eseguito il server
dell'applicazione CA APM.
Numero porta
Specifica il numero porta sulla quale viene eseguito CA APM.
3. Accertarsi di aver completato l'aggiornamento delle proprietà di
configurazione.
Integrazione con CA APM utilizzando Oracle
4. Riavviare Service View.
5. Riprovare ad assegnare i modelli CA APM.
In tal modo viene eseguita la verifica della connessione tra CA Unicenter
Service Catalog e il server dell'applicazione CA APM. La connessione viene
verificata utilizzando i parametri specificati.
6. Se il tentativo di assegnare i modelli non va a buon fine, verificare che i
valori utilizzati per le opzioni di configurazione di amministrazione di CA
APM siano corretti.
I dettagli di configurazione di CA APM vengono aggiornati con i valori specificati.
Integrazione con CA APM utilizzando Oracle
Se CA Unicenter Service Catalog viene integrato con CA APM mediante un
database Oracle, l'ID utente dell'amministratore di Service Delivery [Esecutore]
deve essere in caratteri maiuscoli.
Nota:per ulteriori informazioni, consultare la Implementation Guide.
Impossibile creare ordini di cambiamento quando MultiTenancy è attivo
Se si esegue l'integrazione di CA Unicenter Service Catalog con CA Service Desk
Manager, consultare la presente sezione. In caso contrario, ignorarla.
Se CA Unicenter Service Catalog e CA Service Desk Manager sono stati
configurati per utilizzare l'amministrazione comune di titolari multipli e
l'opzione Multi-Tenancy è stata attivata in CA Service Desk Manager, potrebbe
risultare impossibile utilizzare CA Unicenter Service Catalog per creare ordini di
cambiamento in CA Service Desk Manager.
Per risolvere il problema e poter continuare ad utilizzare sia l'amministrazione
comune di titolari multipli che CA Unicenter Service Catalog per la creazione di
ordini di cambiamento di CA Service Desk Manager, attenersi alla procedura
seguente: in CA Service Desk Manager, modificare l'opzione Multi-Tenancy da
Attivo a Attivo (avviso) o Attivo (consenti).
58 Note di rilascio
Non spostare i titolari
Non spostare i titolari
Per ottenere i migliori risultati, non spostare i titolari di CA Unicenter Service
Catalog (unità di business). Questo avviso è applicabile se si gestiscono i titolari
sia direttamente in CA Unicenter Service Catalog (amministrazione dei titolari
stand-alone) che indirettamente tramite CA Service Desk Manager
(amministrazione comune dei titolari). In ogni caso, lo spostamento dei titolari
può provocare svariati problemi nella gestione delle richieste, degli utenti e di
altre funzioni.
Nota: per informazioni dettagliate sulla gestione dei titolari, consultare la Guida
Valori mancanti dai report
Questo problema noto riguarda solo l'integrazione di CA Unicenter Service
Catalog con CA Service Desk Manager e CA CMDB.
Il report BusinessObjects Enterprise predefinito, denominato Requests _Change
Orders_CI Association, non visualizza alcun valore per le colonne Nome risorsa
elemento della configurazione, Nome famiglia elemento della configurazione e
Nome classe elemento della configurazione.
Ricreare periodi di anni fiscali dopo la migrazione
Dopo aver eseguito la migrazione a CA Unicenter Service Catalog da una
versione precedente, se si utilizzano periodi fiscali annuali, è necessario ricrearli.
Non è necessario ricreare periodi fiscali mensili dopo la migrazione.
Nota: per maggiori dettagli su ulteriori problemi noti specifici della migrazione,
consultare le informazioni relative alla migrazione nella Implementation Guide.
Campi numerici nei sistemi operativi localizzati
I campi numerici nei sistemi operativi localizzati supportano solo i numeri a byte
singolo come 1, 2 e 3, utilizzati sui sistemi operativi in lingua inglese.
Non è possibile installare Service View e il server Oracle insieme
Non è possibile installare Service View e il server Oracle
insieme
Questo problema si verifica solo se si utilizza Oracle come DBMS per CA
Unicenter Service Catalog. Se il nome del database globale Oracle e il nome
dell'identificatore di sistema (SID, System Identifier) non coincidono, non si
potrà installare Service View sullo stesso computer del server Oracle.
Stato di disponibilità delle cartelle
In Generatore di servizi, dopo aver reso non disponibile una cartella o
sottocartella modificandone le date di disponibilità o non disponibilità,
selezionare Aggiorna per assicurarsi che la modifica della disponibilità sia
aggiornata nel momento in cui si visualizzano i contenuti della cartella o
sottocartella.
Campi nvarchar nei rapporti
La GUI di CA Unicenter Service Catalog consente di creare oggetti dati per i
report selezionando Amministrazione, Generatore di report, Oggetti dati.
Quando si creano rapporti, tenere a mente che gli oggetti dati di tipo ODBC non
recuperano i campi di tipo nvarchar. Per recuperare i campi nvarchar negli
oggetti presenti nei rapporti, utilizzare JDBC come tipo di connessione al
database.
Cartelle rimanenti al termine della disintallazione
Se CA Unicenter Service Catalog è stato installato su un'unità non predefinita, ad
esempio E: o F:, e CA Unicenter Service Catalog viene disinstallato in un
momento successivo, è possibile che alcuni file o cartelle potrebbero non essere
rimossi. Ad esempio, la cartella %USM_HOME%\catalog potrebbe rimanere
dopo la disinstallazione. Di solito, il motivo di tutto ciò è che i file presenti nella
cartella %USM_HOME% erano stati modificati oppure erano stati aggiunti nuovi
file. Se rimangono cartelle o file dopo la disinstallazione, eliminarli
manualmente.
60 Note di rilascio
Distinzione tra maiuscole e minuscole per CA MDB su Oracle
Distinzione tra maiuscole e minuscole per CA MDB su Oracle
Quando si utilizza CA MDB su un database Oracle, è necessario fare attenzione a
quanto indicato di seguito:
■
Non è possibile configurare la distinzione tra maiuscole e minuscole a livello
della colonna. I risultati della ricerca a livello della colonna rispettano
sempre l'uso delle lettere maiuscole e minuscole.
■
Il nome gruppo definito in CA EEM e il nome gruppo corrispondente in CA
Workflow devono corrispondere per lettere maiuscole o minuscole. In caso
contrario la richiesta non verrà assegnata al gruppo.
Impossibile generare rapporti non in linea in formato PDF
Non è possibile generare rapporti non in linea in formato PDF. È necessario
invece generarli in formato CSV o HTML.
Problemi con la sospensione di un servizio sottoscritto
Se si sospende un servizio sottoscritto, la sospensione funziona correttamente
finché la data di inizio periodo della sospensione resta impostata sul valore
predefinito. Tuttavia, la sospensione non riesce se il valore del campo Data di
inizio periodo viene cambiato in un valore non predefinito.
I collegamenti ipertestuali ai siti Web non CA potrebbero non
funzionare
Nella Guida all'amministrazione e in altri documenti, alcuni collegamenti
ipertestuali a siti Web non CA potrebbero non funzionare correttamente. Ad
esempio, dopo che la Guida all'amministrazione era stata pubblicata, si è
scoperto che la guida presenta un collegamento non aggiornato alle
informazioni sui client axis di JavaScript sul sito Web di Microsoft. In casi simili,
andare alla pagina iniziale del sito Web e utilizzare la funzione di ricerca o altre
funzionalità di navigazione per trovare le informazioni correlate. Ad esempio,
per trovare le informazioni citate in precedenza sui client axis di JavaScript,
andare sul sito Web microsoft.com ed eseguire la ricerca su tale argomento.
Può apparire il sommario della guida al posto dell'argomento specifico della guida.
Può apparire il sommario della guida al posto dell'argomento
specifico della guida.
Quando si fa clic sul collegamento della guida in linea per visualizzare la guida
contestuale relativa alla finestra attiva, è possibile che venga visualizzato il
sommario della guida e non l'argomento specifico. In questi casi, utilizzare il
sommario per cercare le informazioni necessarie.
Le richieste completate e annullate possono essere bloccate
Quando una richiesta viene annullata dopo essere stata completata, il suo stato
può essere bloccato su In attesa di annullamento e non può passare ad
Annullato come previsto. In questi casi, ignorare, sovrascrivere o ritentare la
richiesta. L'azione più giusta da intraprendere dipende dalle procedure standard
dell'azienda e dal proprio giudizio come amministratore di CA Service Catalog.
Per maggiori dettagli su come ignorare, sovrascrivere o ritentare una richiesta,
consultare la Guida all'amministrazione.
L'aggiornamento MDB potrebbe non riuscire durante
l'aggiornamento di Service View
Quando si esegue l'aggiornamento a Service View viene aggiornato anche CA
Management Database (MDB). L'aggiornamento di MDB può non riuscire in
caso di rapporti duplicati nelle tabelle in cui viene creato un solo indice. Un
esempio è la tabella usm_configuration. In tali tabelle, valutare ed eliminare i
rapporti duplicati, quindi tentare nuovamente l'installazione di MDB.
62 Note di rilascio
L'esecuzione di ulteriori tentativi per le azioni non riuscite non funziona
L'esecuzione di ulteriori tentativi per le azioni non riuscite non
funziona
Quando un'azione non riesce durante l'esecuzione di una richiesta, quest'ultima
può essere bloccata. Le richieste bloccate non possono passare allo stato
successivo del ciclo di vita della richiesta senza un'intervento manuale. Le
richieste bloccate vengono contrassegnate con uno stato di avviso. Per
impostazione predefinita, l'avviso viene rappresentato con un'icona di
avvertenza gialla nella colonna Stato di varie finestre di richiesta, inclusa la
finestra Apri richieste.
Se non si riesce ad eseguire un altro tentativo per l'azione non riuscita,
sovrascrivere (far approvare) l'avviso per far passare la richiesta allo stato
successivo. Per ulteriori informazioni su come sovrascrivere gli avvisi, consultare
la Guida all'amministrazione.
Campi mancanti nell'IDE di CA Workflow con JNLP su
Macintosh
Quando si avvia l'IDE di CA Workflow utilizzando il protocollo di avvio della rete
Java (JNP, Java Network Launch Protocol) su un computer Macintosh, è possibile
che manchino i collegamenti e le schede di azione dall'IDE. Per risolvere il
problema, utilizzare l'IDE da un computer Windows.
Messaggi di avviso del sistema sempre in lingua inglese
I messaggi di avviso del sistema vengono visualizzati sempre in lingua inglese,
anche quando CA Unicenter Service Catalog è installato su sistemi operativi in
lingua non inglese. I messaggi di avviso del sistema vengono visualizzati per le
richieste individuali quando appaiono i dettagli della richiesta; ad esempio,
quando si seleziona Pagina iniziale, Richieste. Analogamente, alcune stringhe di
testo negli elementi della GUI e nel contenuto pubblicato del Generatore
dashboard di CA Unicenter Service Catalog vengono visualizzate sempre in
lingua inglese, anche quando CA Unicenter Service Catalog è installato su
sistemi operativi in lingua non inglese.
La stampa batch non va a buon fine con Mozilla Firefox
La stampa batch non va a buon fine con Mozilla Firefox
In CA Service Accounting, la stampa batch può non andare a buon fine se si
utilizza Mozilla Firefox come browser Web. Per risolvere il problema, provare a
utilizzare Microsoft Internet Explorer per la stampa batch.
Le celle appaiono di grandi dimensioni con Apple Safari
Quando si utilizza il browser Apple Safari per accedere a CA Unicenter Service
Catalog, le celle degli elementi delle opzioni di servizio potrebbero apparire
insolitamente grandi durante le operazioni di creazione o di modifica. In ogni
caso, tale comportamento è corretto, malgrado l'aspetto insolito. Per comodità
di utilizzo, è possibile selezionare un browser differente, come Mozilla Firefox o
Microsoft Internet Explorer, per creare o modificare elementi delle opzioni di
servizio.
Decidere come elaborare le cifre per lo Yen
In CA Service Accounting, vengono visualizzate due cifre dopo il punto decimale
per tutte le unità di valuta supportate, incluso lo yen giapponese. Lo yen viene
elaborato solo in numeri interi. Di conseguenza, se l'azienda utilizza lo yen, deve
decidere in che modo elaborare le due cifre dopo il punto decimale. Ad
esempio, si può decidere di ignorarle o di arrotondarle per difetto o per eccesso
avvicinandosi il più possibile al numero intero.
64 Note di rilascio
Appendice A: Riconoscimenti delle
licenze di terze parti
CA Unicenter Service Catalog eCA Service Accounting dipendono
da prodotti software di terze parti. Prima di utilizzare CA
Unicenter Service Catalog o CA Service Accounting è necessario
accettare tutti i relativi contratti di licenza.
La presente sezione contiene i riconoscimenti delle licenze di
prodotti software di terze parti utilizzati con CA Unicenter
Service Catalog e CA Service Accounting.
In questa sezione verranno presentati i seguenti argomenti:
Dipendenze da prodotti software di terze parti (a pagina 66)
Apache License Version 2.0 (a pagina 67)
Apache License Version 1.1 (a pagina 75)
Apache CXF 2.2.8 (a pagina 79)
Apache mod_jk 1.2.30 (a pagina 123)
Apache Tomcat 5.5.29 (a pagina 132)
EclipseLink 1.1.2 (a pagina 198)
iquery 1.3.2 (a pagina 207)
Java Persistence API v.1 (a pagina 208)
Java Service Wrapper (JSW) Standard 3.3.9 (a pagina 209)
JAXB (a pagina 211)
Mozilla Rhino 1.5R4.1 (a pagina 224)
Open Message Queue 4.1 (a pagina 242)
Oracle 11G JDBC Driver (a pagina 243)
Saxon 8.53 (a pagina 243)
SourceForge Dom4j 1.6.1 (a pagina 244)
SourceForge ANT-CONTRIB v.1.0b3 (a pagina 246)
Sun JRE 1.6.0_14 (a pagina 250)
Unzip 5.42 (a pagina 263)
Appendice A: Riconoscimenti delle licenze di terze parti 65
Dipendenze da prodotti software di terze parti
Dipendenze da prodotti software di terze parti
CA Unicenter Service Catalog installa ed utilizza i seguenti
prodotti di terze parti:
66 Note di rilascio
■
Apache software (a pagina 67)
■
EclipseLink 1.1.2
■
Ext GWT 2.0
■
IBM WSDL4J 1.6.2
■
Info-Zip 5.42
■
iquery 1.3.2
■
Java Persistence API v.1
■
Jsw 3.3.1
■
Mozilla Rhino 1.5R4.1
■
OpenVizViewer 2.4.1
■
Open Message Queue version 4.1
■
Oracle 11G JDBC Driver
■
Oswego Concurrent Utilities 1.3.4
■
RSA BSAFE Crypto-J jsafejcefips 3.6
■
SourceForge,Ant-Contrib 1.0b3
■
SourceForge Dom4j 1.6.1
■
SourceForge Ehcache 1.6
■
SpringSource Spring Framework 2.5.6
■
SQL Server 2005 JDBC Driver 2.0
■
Sun Java Mail 1.3.3
■
Sun Java Persistence API 1.0
■
Sun Java Runtime Environment version 1.6.0_14
Apache License Version 2.0
The Apache License Agreement pertains to the use of the
following software:
■
Apache Ant 1.7
■
Apache Axis 1.2.1
■
Apache Commons Codec 1.3
■
Apache Commons Collection 3.2.1
■
Apache Commons Dbcp 1.2.2
■
Apache Commons Discovery 0.2
■
Apache Commons FileUpload 1.2
■
Apache FOP 0.20.5
■
Apache Common Httpclient 3.0.1
■
Apache Commons IO 1.3.1
■
Apache Commons Logging 1.1.1
■
Apache Commons Pool 1.4
■
Apache ehcache 1.6
■
Apache FOP 0.20.5
■
Apache HTTP Web Server 2.0.54
■
Apache Jakarta Tomcat version 5,5.12 or higher
■
Apache JSP Standard Tag Library (JSTL) 1.0.6
■
Apache Log4j 1.2.14
■
Apache mod_jk 2.0.58
■
Apache ORO 2.0.8
■
Apache OpenViz 2.4.1
■
Apache ORO 2.0.8
■
Apache Struts 1.2.4
■
Apache Xalan 2.7.1
■
Apache Xerces 2.9.1
Portions of this product include software developed by The
Apache Software Foundation (http://www.apache.org/). The
Apache software is distributed in accordance with the following
license agreement.
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
Terms And Conditions For Use, Reproduction, And Distribution
Definitions
"License" shall mean the terms and conditions for use,
reproduction, and distribution as defined by Sections 1 through
9 of this document.
"Licensor" shall mean the copyright owner or entity authorized
by the
copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under
common control with that entity. For the purposes of this
definition, "control" means (i) the power, direct or indirect, to
cause the direction or management of such entity, whether by
contract or otherwise, or (ii) ownership of fifty percent (50%) or
more of the outstanding shares, or (iii) beneficial ownership of
such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising
68 Note di rilascio
permissions granted by this License.
"Source" form shall mean the preferred form for making
modifications, including but not limited to software source
code, documentation source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source
or Object form, made available under the License, as indicated
by a copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or
Object form, that is based on (or derived from) the Work and
for which the editorial revisions, annotations, elaborations, or
other modifications represent, as a whole, an original work of
authorship. For the purposes of this License, Derivative Works
shall not include works that remain separable from, or merely
link (or bind by name) to the interfaces of, the Work and
Derivative Works thereof.
"Contribution" shall mean any work of authorship, including the
original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright
owner or by an individual or Legal Entity authorized to submit
on behalf of the copyright owner. For the purposes of this
definition, "submitted" means any form of electronic, verbal, or
written communication sent to the Licensor or its
representatives, including but not limited to communication on
electronic mailing lists, source code control systems, and issue
tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work,
but excluding communication that is conspicuously marked or
otherwise designated in writing by the copyright owner as "Not
a Contribution."
"Contributor" shall mean Licensor and any individual or Legal
Entity on behalf of whom a Contribution has been received by
Licensor and subsequently incorporated within the Work.
Grant of Copyright License. Subject to the terms and conditions
of this License, each Contributor hereby grants to You a
perpetual, worldwide, non-exclusive, no-charge, royalty-free,
irrevocable copyright license to reproduce, prepare Derivative
Works of, publicly display, publicly perform, sublicense, and
distribute the Work and such Derivative Works in Source or
Object form.
70 Note di rilascio
Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have
made, use, offer to sell, sell, import, and otherwise transfer the
Work, where such license applies only to those patent claims
licensable by such Contributor that are necessarily infringed by
their Contribution(s) alone or by combination of their
Contribution(s) with the Work to which such Contribution(s)
was submitted. If You institute patent litigation against any
entity (including a cross-claim or counterclaim in a lawsuit)
alleging that the Work or a Contribution incorporated within the
Work constitutes direct or contributory patent infringement,
then any patent licenses granted to You under this License for
that Work shall terminate as of the date such litigation is filed.
Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or
without modifications, and in Source or Object form, provided
that You meet the following conditions:
You must give any other recipients of the Work or Derivative
Works a copy of this License; and
You must cause any modified files to carry prominent notices
stating that you changed the files; and
You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work, excluding
those notices that do not pertain to any part of the Derivative
Works; and
If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one of
the following places: within a NOTICE text file distributed as
part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The
contents of the NOTICE file are for informational purposes only
and do not the License. You may add your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed as
modifying the License.
You may add your own copyright statement to your
modifications and may provide additional or different license
terms and conditions for use, reproduction, or distribution of
Your modifications, or for any such Derivative Works as a whole,
provided Your use, reproduction, and distribution of the Work
otherwise complies with the conditions stated in this License.
Submission of Contributions. Unless you explicitly state
otherwise, any Contribution intentionally submitted for
inclusion in the Work by you to the Licensor shall be under the
terms and conditions of this License, without any additional
terms or conditions. Notwithstanding the above, nothing herein
shall supersede or modify the terms of any separate license
agreement you may have executed with Licensor regarding such
Contributions.
Trademarks. This License does not grant permission to use the
trade names, trademarks, service marks, or product names of
the Licensor, except as required for reasonable and customary
use in describing the origin of the Work and reproducing the
content of the NOTICE file.
72 Note di rilascio
Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either
express or implied, including, without limitation, any warranties
or conditions of TITLE, NON-INFRINGEMENT,
MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE.
You are solely responsible for determining the appropriateness
of using or redistributing the Work and assume any risks
associated with your exercise of permissions under this License.
Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and
grossly negligent acts) or agreed to in writing, shall any
Contributor be liable to You for damages, including any direct,
indirect, special, incidental, or consequential damages of any
character arising as a result of this License or out of the use or
inability to use the Work (including but not limited to damages
for loss of goodwill, work stoppage, computer failure or
malfunction, or any and all other commercial damages or
losses), even if such Contributor has been advised of the
possibility of such damages.
Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, you may choose to offer,
and charge a fee for, acceptance of support, warranty,
indemnity, or other liability obligations and/or rights consistent
with this License. However, in accepting such obligations, You
may act only on Your own behalf and on Your sole
responsibility, not on behalf of any other Contributor, and only
if You agree to indemnify, defend, and hold each Contributor
harmless for any liability incurred by, or claims asserted against,
such Contributor by reason of your accepting any such warranty
or additional liability.
END OF TERMS AND CONDITIONS
How to Apply the Apache License to Your Work
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[ ]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0.
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an "AS
IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied.
See the License for the specific language governing permissions
and limitations under the License.
74 Note di rilascio
The Apache Version 1.1 license agreement pertains to the use
of the following software:: Apache ORO 2.0.8.
This product includes software developed by the Apache
Software Foundation (http://www.apache.org/). ORO 2.0.8 is
distributed in accordance with the following terms and
conditions:
/*
====================================================
================
* The Apache Software License, Version 1.1
*
* Copyright (c) 2000-2002 The Apache Software Foundation.
All rights
* reserved.
*
* Redistribution and use in source and binary forms, with or
without
* modification, are permitted provided that the following
conditions
* are met:
*
* 1. Redistributions of source code must retain the above
copyright
* notice, this list of conditions and the following disclaimer.
*
* 2. Redistributions in binary form must reproduce the above
copyright
* notice, this list of conditions and the following disclaimer in
* the documentation and/or other materials provided with
the
* distribution.
*
* 3. The end-user documentation included with the
redistribution,
* if any, must include the following acknowledgment:
*
"This product includes software developed by the
*
Apache Software Foundation (http://www.apache.org/)."
* Alternately, this acknowledgment may appear in the
software itself,
* if and wherever such third-party acknowledgments
normally appear.
*
* 4. The names "Apache" and "Apache Software Foundation",
"Jakarta-Oro"
* must not be used to endorse or promote products derived
from this
* software without prior written permission. For written
* permission, please contact apache@apache.org.
76 Note di rilascio
*
* 5. Products derived from this software may not be called
"Apache"
* or "Jakarta-Oro", nor may "Apache" or "Jakarta-Oro" appear
in their
* name, without prior written permission of the Apache
Software Foundation.
*
* THIS SOFTWARE IS PROVIDED `ÀS IS'' AND ANY EXPRESSED
OR IMPLIED
* WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES
* OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE
* DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE
FOUNDATION OR
* ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
INCIDENTAL,
* SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT
* LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
SERVICES; LOSS OF
* USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND
* ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT LIABILITY,
* OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
IN ANY WAY OUT
* OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF
* SUCH DAMAGE.
*
====================================================
================
*
* This software consists of voluntary contributions made by
many
* individuals on behalf of the Apache Software Foundation. For
more
* information on the Apache Software Foundation, please see
*.
*/
78 Note di rilascio
Apache CXF 2.2.8
Apache CXF 2.2.8
This product contains Apache CXF v.2.2.8 as well as the Apache
CXF v.2.2.8 subcomponents set forth below. Apache CXF v.2.2.8
and such subcomponents are distributed in accordance with the
following terms:
Apache License
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND
DISTRIBUTION
1. Definitions.
reproduction,
and distribution as defined by Sections 1 through 9 of this
document.
"Licensor" shall mean the copyright owner or entity
authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and
all
common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause
the
Apache CXF 2.2.8
direction or management of such entity, whether by
contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of
the
outstanding shares, or (iii) beneficial ownership of such
entity.
exercising permissions granted by this License.
modifications,
including but not limited to software source code,
documentation
source, and configuration files.
"Object" form shall mean any form resulting from
mechanical
not limited to compiled object code, generated
documentation,
"Work" shall mean the work of authorship, whether in
Source or
Object form, made available under the License, as indicated
by a
copyright notice that is included in or attached to the work
80 Note di rilascio
Apache CXF 2.2.8
"Derivative Works" shall mean any work, whether in Source
or Object
form, that is based on (or derived from) the Work and for
which the
editorial revisions, annotations, elaborations, or other
modifications
represent, as a whole, an original work of authorship. For
the purposes
of this License, Derivative Works shall not include works that
remain
separable from, or merely link (or bind by name) to the
interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or
additions
to that Work or Derivative Works thereof, that is
intentionally
submitted to Licensor for inclusion in the Work by the
copyright owner
or by an individual or Legal Entity authorized to submit on
behalf of
the copyright owner. For the purposes of this definition,
"submitted"
means any form of electronic, verbal, or written
communication sent
Apache CXF 2.2.8
to the Licensor or its representatives, including but not
limited to
communication on electronic mailing lists, source code
control systems,
and issue tracking systems that are managed by, or on
behalf of, the
Licensor for the purpose of discussing and improving the
Work, but
excluding communication that is conspicuously marked or
otherwise
designated in writing by the copyright owner as "Not a
Contribution."
Entity
on behalf of whom a Contribution has been received by
Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and
conditions of
this License, each Contributor hereby grants to You a
perpetual,
worldwide, non-exclusive, no-charge, royalty-free,
irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute
the
82 Note di rilascio
Apache CXF 2.2.8
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions
of
this License, each Contributor hereby grants to You a
perpetual,
worldwide, non-exclusive, no-charge, royalty-free,
irrevocable
(except as stated in this section) patent license to make,
have made,
use, offer to sell, sell, import, and otherwise transfer the
Work,
where such license applies only to those patent claims
licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their
Contribution(s)
with the Work to which such Contribution(s) was submitted.
If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the
Work
or a Contribution incorporated within the Work constitutes
direct
or contributory patent infringement, then any patent
licenses
Apache CXF 2.2.8
granted to You under this License for that Work shall
terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of
the
without
modifications, and in Source or Object form, provided that
You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent
notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative
Works
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute
must
84 Note di rilascio
Apache CXF 2.2.8
include a readable copy of the attribution notices
contained
within such NOTICE file, excluding those notices that do
not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file
distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative
Works; or,
contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own
attribution
notices within Derivative Works that You distribute,
alongside
or as an addendum to the NOTICE text from the Work,
provided
that such additional attribution notices cannot be
construed
as modifying the License.
You may add Your own copyright statement to Your
modifications and
Apache CXF 2.2.8
may provide additional or different license terms and
conditions
for use, reproduction, or distribution of Your modifications,
or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise
complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state
otherwise,
any Contribution intentionally submitted for inclusion in the
Work
by You to the Licensor shall be under the terms and
conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede
or modify
the terms of any separate license agreement you may have
executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use
the trade
names, trademarks, service marks, or product names of the
Licensor,
86 Note di rilascio
Apache CXF 2.2.8
except as required for reasonable and customary use in
describing the
origin of the Work and reproducing the content of the
NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law
or
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND,
either express or
implied, including, without limitation, any warranties or
conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or
FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for
determining the
appropriateness of using or redistributing the Work and
assume any
risks associated with Your exercise of permissions under this
License.
8. Limitation of Liability. In no event and under no legal
theory,
whether in tort (including negligence), contract, or
otherwise,
grossly
Apache CXF 2.2.8
negligent acts) or agreed to in writing, shall any Contributor
be
liable to You for damages, including any direct, indirect,
special,
incidental, or consequential damages of any character
arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of
goodwill,
work stoppage, computer failure or malfunction, or any and
all
other commercial damages or losses), even if such
Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While
redistributing
the Work or Derivative Works thereof, You may choose to
offer,
indemnity,
or other liability obligations and/or rights consistent with
this
License. However, in accepting such obligations, You may act
only
on Your own behalf and on Your sole responsibility, not on
behalf
88 Note di rilascio
Apache CXF 2.2.8
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by
reason
of your accepting any such warranty or additional liability.
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the
following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't
include
the brackets!) The text should be enclosed in the
appropriate
comment syntax for the file format. We also recommend
that a
file or class name and description of purpose be included on
the
Licensed under the Apache License, Version 2.0 (the
"License");
Apache CXF 2.2.8
you may not use this file except in compliance with the
License.
http://www.apache.org/licenses/LICENSE-2.0
software
distributed under the License is distributed on an "AS IS"
BASIS,
express or implied.
See the License for the specific language governing
permissions and
limitations under the License.
Apache CXF includes a number of components and libraries with
separate
copyright notices and license terms. Your use of those
components are
subject to the terms and conditions of the following licenses.
AntLR Parser Generator (http://www.antlr.org/)
antlr:antlr:jar:2.7.7
License: BSD License (http://www.antlr.org/license.html)
AOP alliance (http://aopalliance.sourceforge.net)
aopalliance:aopalliance:jar:1.0
License: Public Domain
90 Note di rilascio
Apache CXF 2.2.8
ASM (http://asm.objectweb.org/asm/asm)
asm:asm:jar:2.2.3:compile
License: BSD (http://asm.ow2.org/license.html)
Sun JAXB Reference Implementation Runtime
com.sun.xml.bind:jaxb-impl:jar:2.1.12:compile
License: COMMON DEVELOPMENT AND DISTRIBUTION
LICENSE (CDDL) Version 1.0
(http://www.sun.com/cddl/cddl.html)
Sun JAXB Reference Implementation Tools
com.sun.xml.bind:jaxb-xjc:jar:2.1.12:compile
Sun SAAJ Reference Implementation
com.sun.xml.messaging.saaj:saaj-impl:jar:1.3.2:compile
JSR 311 API (https://jsr311.dev.java.net/) javax.ws.rs:jsr311api:jar:1.0:compile
Java Architecture for XML Binding (JAXB API)
javax.xml.bind:jaxb-api:jar:2.1:compile
Apache CXF 2.2.8
Sun SAAJ API
(http://java.sun.com/webservices/saaj/index.jsp/saaj-api)
javax.xml.soap:saaj-api:jar:1.3:compile
Jaxen (http://jaxen.codehaus.org/jaxen)
jaxen:jaxen:jar:1.1:compile
License: BSD (http://jaxen.codehaus.org/license.html)
Bouncy Castle Provider
(http://www.bouncycastle.org/java.html)
org.bouncycastle:bcprov-jdk15:jar:1.43
License: Bouncy Castle Licence
(http://www.bouncycastle.org/licence.html)
Jetty Server (http://www.eclipse.org/jetty/jettyparent/project/modules/jetty) org.mortbay.jetty:jetty:jar:6.1.21
License: Apache Software License - Version 2.0
(http://www.apache.org/licenses/LICENSE-2.0)
Jetty Server (http://www.eclipse.org/jetty/jettyparent/project/modules/jetty) org.mortbay.jetty:jetty:jar:6.1.21
License: Eclipse Public License - Version 1.0
(http://www.eclipse.org/org/documents/epl-v10.php)
Jetty Utilities (http://www.eclipse.org/jetty/jettyparent/project/jetty-util) org.mortbay.jetty:jetty-util:jar:6.1.21
License: Apache Software License - Version 2.0
(http://www.apache.org/licenses/LICENSE-2.0)
92 Note di rilascio
Apache CXF 2.2.8
Jetty Utilities (http://www.eclipse.org/jetty/jettyparent/project/jetty-util) org.mortbay.jetty:jetty-util:jar:6.1.21
License: Eclipse Public License - Version 1.0
(http://www.eclipse.org/org/documents/epl-v10.php)
Simple Logging Facade for Java - API (http://www.slf4j.org/slf4japi) org.slf4j:slf4j-api:jar:1.5.8:compile
License: MIT License (http://www.slf4j.org/license.html)
Simple Logging Facade for Java - JDK Logging
(http://www.slf4j.org/slf4j-jdk14) org.slf4j:slf4jjdk14:jar:1.5.8:compile
License: MIT License (http://www.slf4j.org/license.html)
Rhino (http://www.mozilla.org/rhino/) rhino:js:jar:1.7R1
License: Mozilla Public License version 1.1
(http://www.mozilla.org/MPL/MPL-1.1.html)
WSDL4J (http://sf.net/projects/wsdl4j) wsdl4j:wsdl4j:jar:1.6.2
License: CPL
(http://www.opensource.org/licenses/cpl1.0.txt)
Sun JAXB Reference Implementation Runtime
com.sun.xml.bind:jaxb-impl:jar:2.1.12
Sun JAXB Reference Implementation Tools
com.sun.xml.bind:jaxb-xjc:jar:2.1.12
Sun SAAJ Reference Implementation
com.sun.xml.messaging.saaj:saaj-impl:jar:1.3.2
JSR 311 API (https://jsr311.dev.java.net/) javax.ws.rs:jsr311api:jar:1.0
Apache CXF 2.2.8
Java Architecture for XML Binding (JAXB API)
javax.xml.bind:jaxb-api:jar:2.1
Sun SAAJ API
(http://java.sun.com/webservices/saaj/index.jsp/saaj-api)
javax.xml.soap:saajapi:jar:1.3:
This product contains com.sun.xml.bind:jaxbimpl:jar:2.1.12,jaxb-xjc:jar:2.1.12,saaj-impl:jar:1.3.2,jsr311api:jar:1.0,jaxb-api:jar:2.1
saaj-api:jar:1.3 . The CDDL Subcomponents were was obtained
under the CDDL v.1.0 license, the
terms and conditions of which are set forth below. The CDDL
Subcomponents are distributed by
CA for use with this CA product in unmodified, object code
form, under the CA End User
License Agreement. Any provisions in the CA End User License
Agreement that differ from the
CDDL are offered by CA alone and not by any other party. CA
makes the source code for the
CDDL Subcomponents available at
http://opensrcd.ca.com/ips/06984_14/ under the terms of the
CDDL v.1.0. license:
COMMON DEVELOPMENT AND DISTRIBUTION LICENSE (CDDL)
Version 1.0
1. Definitions.
94 Note di rilascio
Apache CXF 2.2.8
1.1. “Contributor” means each individual or entity that creates
or contributes to the
creation of Modifications.
1.2. “Contributor Version” means the combination of the
Original Software, prior
Modifications used by a Contributor (if any), and the
Modifications made by that particular
Contributor.
1.3. “Covered Software” means (a) the Original Software, or (b)
Modifications, or (c) the
combination of files containing Original Software with files
containing Modifications, in
each 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 Software
available under this License.
1.6. “Larger Work” means a work which combines Covered
Software or portions thereof with
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
Apache CXF 2.2.8
at the time of the initial grant or subsequently acquired, any
and all of the rights
conveyed herein.
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 contents
of 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 this
License.
1.10. “Original Software” means the Source Code and
Executable form of computer software
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 patent Licensable by
grantor.
1.12. “Source Code” means (a) the common form of computer
software code in which
modifications are made and (b) associated documentation
included in or with such code.
96 Note di rilascio
Apache CXF 2.2.8
1.13. “You” (or “Your”) means an individual or a legal entity
exercising rights under, and
complying with all of the terms of, this License. For legal
entities, “You” includes any
entity which controls, is controlled by, or is under common
control with You. For purposes
of this definition, “control” means (a) the power, direct or
indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (b) ownership
of more than 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 party
intellectual 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 by
Initial Developer, to use, reproduce, modify, display, perform,
sublicense and distribute
Apache CXF 2.2.8
the Original Software (or portions thereof), with or without
Modifications, and/or as part
of a Larger Work; and
(b) under Patent Claims infringed by the making, using or selling
of Original Software, to
make, have made, use, practice, sell, and offer for sale, and/or
otherwise dispose of the
Original Software (or portions thereof).
(c) The licenses granted in Sections 2.1(a) and (b) are effective
on the date Initial
Developer first distributes or otherwise makes the Original
Software available to a third
party under the terms of this License.
(d) Notwithstanding Section 2.1(b) above, no patent license is
granted: (1) for code that
You delete from the Original Software, or (2) for infringements
caused by: (i) the
modification of the Original Software, or (ii) the combination of
the Original Software with
other software or devices.
2.2. Contributor Grant.
Conditioned upon Your compliance with Section 3.1 below and
subject to third party
intellectual property claims, each Contributor hereby grants You
a world-wide, royalty-free,
98 Note di rilascio
Apache CXF 2.2.8
non-exclusive license:
trademark) Licensable by
Contributor to use, reproduce, modify, display, perform,
sublicense and distribute the
Modifications created by such Contributor (or portions thereof),
either on an unmodified
basis, 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 made by
that Contributor either alone and/or in combination with its
Contributor Version (or
portions of such combination), to make, use, sell, offer for sale,
have made, and/or
otherwise dispose of: (1) Modifications made by that
Contributor (or portions thereof); and
(2) the combination of Modifications made by that Contributor
with its Contributor Version
(or portions of such combination).
(c) The licenses granted in Sections 2.2(a) and 2.2(b) are
effective on the date Contributor
first distributes or otherwise makes the Modifications available
to a third party.
granted: (1) for any code
Apache CXF 2.2.8
that Contributor has deleted from the Contributor Version; (2)
for infringements caused by:
(i) third party modifications of Contributor Version, or (ii) the
combination of
Modifications made by that Contributor with other software
(except as part of the
Contributor Version) or other devices; or (3) under Patent
Claims infringed by Covered
Software 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 Executable form must
also be made available in Source Code form and that Source
Code form must be distributed
only under the terms of this License. You must include a copy of
this License with every
copy of the Source Code form of the Covered Software You
distribute or otherwise make
available. You must inform recipients of any such Covered
Software in Executable form as to
how they can obtain such Covered Software in Source Code
form in a reasonable manner on or
through a medium customarily used for software exchange.
100 Note di rilascio
Apache CXF 2.2.8
3.2. Modifications.
The Modifications that You create or to which You contribute
are governed by the terms of
this License. You represent that You believe Your Modifications
are Your original creation
(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 the
Contributor of the Modification. You may not remove or alter
any copyright, patent or
trademark notices contained within the Covered Software, or
any notices of licensing or any
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 form that
alters or restricts the applicable version of this License or the
recipients’ rights
hereunder. 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
Apache CXF 2.2.8
only on Your own behalf, and not on behalf of the Initial
Developer 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 to
indemnify the Initial Developer
and every Contributor for any liability incurred by the Initial
Developer or such
Contributor as a result of warranty, support, indemnity or
liability terms You offer.
3.5. Distribution of Executable Versions.
You may distribute the Executable form of the Covered
Software under the terms of this
License or under the terms of a license of Your choice, which
may contain terms different
from this License, provided that You are in compliance with the
terms of this License and
that the license for the Executable form does not attempt to
limit or alter the recipient’s
rights in the Source Code form from the rights set forth in this
License. If You distribute
the Covered Software in Executable form under a different
license, You must make it
absolutely clear that any terms which differ from this License
are offered by You alone, not
Apache CXF 2.2.8
by the Initial Developer or Contributor. You hereby agree to
indemnify the Initial Developer
and every Contributor for any liability incurred by the Initial
Developer or such
Contributor 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 not governed 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 the Covered
Software.
4. Versions of the License.
4.1. New Versions.
Sun Microsystems, Inc. is the initial license steward and may
publish revised and/or new
versions of this License 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 to modify this License.
4.2. Effect of New Versions.
You may always continue to use, distribute or otherwise make
the Covered Software available
Apache CXF 2.2.8
under the terms of the version of the License under which You
originally received the
Covered Software. If the Initial Developer includes a notice in
the Original Software
prohibiting it from being distributed or otherwise made
available under any subsequent
version of the License, You must distribute and make the
Covered Software available under
the terms of the version of the License under which You
originally received the Covered
Software. Otherwise, You may also choose to use, distribute or
otherwise make the Covered
Software available under the terms of any subsequent version
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 Original
Software, You may create and use a modified version of this
License if You: (a) rename the
license and remove any references to the name of the license
steward (except to note that
the license differs from this License); and (b) otherwise make it
clear that the license
contains terms which differ from this License.
Apache CXF 2.2.8
5. DISCLAIMER OF WARRANTY.
COVERED SOFTWARE IS PROVIDED UNDER THIS LICENSE ON AN
“AS IS” BASIS, WITHOUT WARRANTY OF ANY
KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, WITHOUT
LIMITATION, WARRANTIES THAT THE
COVERED SOFTWARE IS FREE OF DEFECTS, MERCHANTABLE, FIT
FOR A PARTICULAR PURPOSE OR NONINFRINGING. THE ENTIRE RISK AS TO THE QUALITY AND
PERFORMANCE OF THE COVERED SOFTWARE IS
WITH YOU. SHOULD ANY COVERED SOFTWARE PROVE
DEFECTIVE IN ANY RESPECT, YOU (NOT THE INITIAL
DEVELOPER OR ANY OTHER CONTRIBUTOR) ASSUME THE COST
OF ANY NECESSARY SERVICING, REPAIR OR
CORRECTION. THIS DISCLAIMER OF WARRANTY CONSTITUTES
AN ESSENTIAL PART OF THIS LICENSE. NO
USE OF ANY COVERED SOFTWARE IS AUTHORIZED HEREUNDER
EXCEPT UNDER THIS DISCLAIMER.
6. TERMINATION.
6.1. This License and the rights granted hereunder will
terminate automatically if You fail
to comply with terms herein and fail to cure such breach within
30 days of becoming aware of
the breach. Provisions which, by their nature, must remain in
effect beyond the termination
of this License shall survive.
Apache CXF 2.2.8
6.2. If You assert a patent infringement claim (excluding
declaratory judgment actions)
against Initial Developer or a Contributor (the Initial Developer
or Contributor against
whom You assert such claim is referred to as “Participant”)
alleging that the Participant
Software (meaning the Contributor Version where the
Participant is a Contributor or the
Original Software where the Participant is the Initial Developer)
directly or indirectly
infringes any patent, then any and all rights granted directly or
indirectly to You by such
Participant, the Initial Developer (if the Initial Developer is not
the Participant) and all
Contributors under Sections 2.1 and/or 2.2 of this License shall,
upon 60 days notice from
Participant terminate prospectively and automatically at the
expiration of such 60 day
notice period, unless if within such 60 day period You withdraw
Your claim with respect to
the Participant Software against such Participant either
unilaterally or pursuant 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 that
Apache CXF 2.2.8
have 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 INITIAL
DEVELOPER, ANY OTHER CONTRIBUTOR, OR ANY
DISTRIBUTOR OF COVERED SOFTWARE, OR ANY SUPPLIER OF
ANY OF SUCH PARTIES, BE LIABLE TO ANY
PERSON FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR
CONSEQUENTIAL DAMAGES OF ANY CHARACTER
INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOST
PROFITS, LOSS OF GOODWILL, WORK STOPPAGE,
COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL
OTHER COMMERCIAL DAMAGES OR LOSSES, EVEN IF
SUCH PARTY SHALL HAVE BEEN INFORMED OF THE POSSIBILITY
OF SUCH DAMAGES. THIS LIMITATION OF
LIABILITY SHALL NOT APPLY TO LIABILITY FOR DEATH OR
PERSONAL INJURY RESULTING FROM SUCH
PARTY’S NEGLIGENCE TO THE EXTENT APPLICABLE LAW
PROHIBITS SUCH LIMITATION. SOME
JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION
OF INCIDENTAL OR CONSEQUENTIAL
Apache CXF 2.2.8
DAMAGES, SO THIS EXCLUSION AND LIMITATION MAY NOT
APPLY TO YOU.
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 48
C.F.R. § 252.227-7014(a)(1)) and “commercial computer
software documentation” as such terms
are used in 48 C.F.R. 12.212 (Sept. 1995). Consistent with 48
C.F.R. 12.212 and 48 C.F.R.
227.7202-1 through 227.7202-4 (June 1995), all U.S.
Government End Users acquire Covered
Software with only those rights set forth herein. This U.S.
Government Rights clause is in
lieu of, and supersedes, any other FAR, DFAR, or other clause or
provision that addresses
Government rights in computer software under this License.
9. MISCELLANEOUS.
This License represents the complete agreement concerning
subject matter hereof. If any
provision of this License is held to be unenforceable, such
provision shall be reformed only
to the extent necessary to make it enforceable. This License
shall be governed by the law of
Apache CXF 2.2.8
the jurisdiction specified in a notice contained within the
Original Software (except to the
extent applicable law, if any, provides otherwise), excluding
such jurisdiction’s conflictof-law provisions. Any litigation relating to this License shall be
subject to the
jurisdiction of the courts located in the jurisdiction and venue
specified in a notice
contained within the Original Software, with the losing party
responsible for costs,
including, without limitation, court costs and reasonable
attorneys’ fees and expenses. Il
application of the United Nations Convention on Contracts for
the International Sale of
Goods is expressly excluded. Any law or regulation which
provides that the language of a
contract shall be construed against the drafter shall not apply to
this License. You agree
that You alone are responsible for compliance with the United
States export administration
regulations (and the export control laws and regulation of any
other countries) when You
use, distribute or otherwise make available any Covered
Software.
10. RESPONSIBILITY FOR CLAIMS.
Apache CXF 2.2.8
As between Initial Developer and the Contributors, each party is
responsible for claims and
damages arising, directly or indirectly, out of its utilization of
rights under this License
and You agree to work with Initial Developer and Contributors
to distribute such
responsibility on an equitable basis. Nothing herein is intended
or shall be deemed to
constitute any admission of liability.
WSDL4J :1.6.2
This product contains WSDL4J :1.6.2. The CPL Subcomponents
were was obtained under the CPL v.1.0 license, the
terms and conditions of which are set forth below. The CPL
Subcomponents are distributed by
form, under the CA End User
License Agreement. Any provisions in the CA End User License
Agreement that differ from the
CPL are offered by CA alone and not by any other party. CA
makes the source code for the CPL
Subcomponents available at
CPL
v.1.0. license:
Common Public License Version 1.0
Apache CXF 2.2.8
THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE
TERMS OF THIS COMMON PUBLIC
LICENSE ("AGREEMENT"). ANY USE, REPRODUCTION OR
DISTRIBUTION OF THE PROGRAM
CONSTITUTES RECIPIENT'S ACCEPTANCE OF THIS AGREEMENT.
1. DEFINITIONS
"Contribution" means:
a) in the case of the initial Contributor, the initial code and
documentation distributed under this Agreement, and
b) in the case of each subsequent Contributor:
i) changes to the Program, and
ii) additions to the Program;
where such changes and/or additions to the Program originate
from and are
distributed by that particular Contributor. A Contribution
'originates' from a
Contributor if it was added to the Program by such Contributor
itself or anyone
acting on such Contributor's behalf. Contributions do not
include additions to
the Program which: (i) are separate modules of software
distributed in
conjunction with the Program under their own license
agreement, and (ii) are not
Apache CXF 2.2.8
derivative works of the Program.
"Contributor" means any person or entity that distributes the
Program.
"Licensed Patents " mean patent claims licensable by a
Contributor which are
necessarily infringed by the use or sale of its Contribution alone
or when
combined with the Program.
"Program" means the Contributions distributed in accordance
with this Agreement.
"Recipient" means anyone who receives the Program under this
Agreement,
including all Contributors.
2. GRANT OF RIGHTS
a) Subject to the terms of this Agreement, each Contributor
hereby grants
Recipient a non-exclusive, worldwide, royalty-free copyright
license to
reproduce, prepare derivative works of, publicly display,
publicly perform,
distribute and sublicense the Contribution of such Contributor,
if any, and such
derivative works, in source code and object code form.
b) Subject to the terms of this Agreement, each Contributor
hereby grants
Apache CXF 2.2.8
Recipient a non-exclusive, worldwide, royalty-free patent
license under Licensed
Patents to make, use, sell, offer to sell, import and otherwise
transfer the
Contribution of such Contributor, if any, in source code and
object code form.
This patent license shall apply to the combination of the
Contribution and the
Program if, at the time the Contribution is added by the
Contributor, such
addition of the Contribution causes such combination to be
covered by the
Licensed Patents. The patent license shall not apply to any other
combinations
which include the Contribution. No hardware per se is licensed
hereunder.
c) Recipient understands that although each Contributor grants
the licenses
to its Contributions set forth herein, no assurances are provided
by any
Contributor that the Program does not infringe the patent or
other intellectual
property rights of any other entity. Each Contributor disclaims
any liability to
Recipient for claims brought by any other entity based on
infringement of
Apache CXF 2.2.8
intellectual property rights or otherwise. As a condition to
exercising the
rights and licenses granted hereunder, each Recipient hereby
assumes sole
responsibility to secure any other intellectual property rights
needed, if any.
For example, if a third party patent license is required to allow
Recipient to
distribute the Program, it is Recipient's responsibility to acquire
that license
before distributing the Program.
d) Each Contributor represents that to its knowledge it has
sufficient
copyright rights in its Contribution, if any, to grant the copyright
license set
forth in this Agreement.
3. REQUIREMENTS
A Contributor may choose to distribute the Program in object
code form under its
own license agreement, provided that:
a) it complies with the terms and conditions of this Agreement;
and
b) its license agreement:
i) effectively disclaims on behalf of all Contributors all
warranties and
Apache CXF 2.2.8
conditions, express and implied, including warranties or
conditions of title and
non-infringement, and implied warranties or conditions of
merchantability and
fitness for a particular purpose;
ii) effectively excludes on behalf of all Contributors all liability
for
damages, including direct, indirect, special, incidental and
consequential
damages, such as lost profits;
iii) states that any provisions which differ from this Agreement
are offered
by that Contributor alone and not by any other party; and
iv) states that source code for the Program is available from
such
Contributor, and informs licensees how to obtain it in a
reasonable manner on or
through a medium customarily used for software exchange.
When the Program is made available in source code form:
a) it must be made available under this Agreement; and
b) a copy of this Agreement must be included with each copy of
the Program.
Contributors may not remove or alter any copyright notices
contained within the
Program.
Apache CXF 2.2.8
Each Contributor must identify itself as the originator of its
Contribution, if
any, in a manner that reasonably allows subsequent Recipients
to identify the
originator of the Contribution.
4. COMMERCIAL DISTRIBUTION
Commercial distributors of software may accept certain
responsibilities with
respect to end users, business partners and the like. While this
license is
intended to facilitate the commercial use of the Program, the
Contributor who
includes the Program in a commercial product offering should
do so in a manner
which does not create potential liability for other Contributors.
Therefore, if
a Contributor includes the Program in a commercial product
offering, such
Contributor ("Commercial Contributor") hereby agrees to
defend and indemnify
every other Contributor ("Indemnified Contributor") against any
losses, damages
and costs (collectively "Losses") arising from claims, lawsuits
and other legal
actions brought by a third party against the Indemnified
Contributor to the
Apache CXF 2.2.8
extent caused by the acts or omissions of such Commercial
Contributor in
connection with its distribution of the Program in a commercial
product
offering. The obligations in this section do not apply to any
claims or Losses
relating to any actual or alleged intellectual property
infringement. In order
to qualify, an Indemnified Contributor must: a) promptly notify
the Commercial
Contributor in writing of such claim, and b) allow the
Commercial Contributor to
control, and cooperate with the Commercial Contributor in, the
defense and any
related settlement negotiations. The Indemnified Contributor
may participate in
any such claim at its own expense.
For example, a Contributor might include the Program in a
commercial product
offering, Product X. That Contributor is then a Commercial
Contributor. If that
Commercial Contributor then makes performance claims, or
offers warranties
related to Product X, those performance claims and warranties
are such
Apache CXF 2.2.8
Commercial Contributor's responsibility alone. Under this
section, the
Commercial Contributor would have to defend claims against
the other
Contributors related to those performance claims and
warranties, and if a court
requires any other Contributor to pay any damages as a result,
the Commercial
Contributor must pay those damages.
5. NO WARRANTY
EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, THE
PROGRAM IS PROVIDED ON AN
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, EITHER EXPRESS OR
IMPLIED INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES
OR CONDITIONS OF TITLE,
NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE. Each
Recipient is solely responsible for determining the
appropriateness of using and
distributing the Program and assumes all risks associated with
its exercise of
rights under this Agreement, including but not limited to the
risks and costs of
program errors, compliance with applicable laws, damage to or
loss of data,
Apache CXF 2.2.8
programs or equipment, and unavailability or interruption of
operations.
6. DISCLAIMER OF LIABILITY
EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, NEITHER
RECIPIENT NOR ANY
CONTRIBUTORS SHALL HAVE ANY LIABILITY FOR ANY DIRECT,
INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING WITHOUT LIMITATION LOST
PROFITS), HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY, WHETHER IN CONTRACT,
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY
OUT OF THE USE OR DISTRIBUTION OF THE PROGRAM OR THE
EXERCISE OF ANY RIGHTS
GRANTED HEREUNDER, EVEN IF ADVISED OF THE POSSIBILITY
OF SUCH DAMAGES.
7. GENERAL
If any provision of this Agreement is invalid or unenforceable
under applicable
law, it shall not affect the validity or enforceability of the
remainder of the
terms of this Agreement, and without further action by the
parties hereto, such
provision shall be reformed to the minimum extent necessary to
make such
Apache CXF 2.2.8
provision valid and enforceable.
If Recipient institutes patent litigation against a Contributor
with respect to
a patent applicable to software (including a cross-claim or
counterclaim in a
lawsuit), then any patent licenses granted by that Contributor to
such Recipient
under this Agreement shall terminate as of the date such
litigation is filed. In
addition, if Recipient institutes patent litigation against any
entity
(including a cross-claim or counterclaim in a lawsuit) alleging
that the Program
itself (excluding combinations of the Program with other
software or hardware)
infringes such Recipient's patent(s), then such Recipient's rights
granted under
Section 2(b) shall terminate as of the date such litigation is filed.
All Recipient's rights under this Agreement shall terminate if it
fails to
comply with any of the material terms or conditions of this
Agreement and does
not cure such failure in a reasonable period of time after
becoming aware of
such noncompliance. If all Recipient's rights under this
Agreement terminate,
Apache CXF 2.2.8
Recipient agrees to cease use and distribution of the Program as
soon as
reasonably practicable. However, Recipient's obligations under
this Agreement
and any licenses granted by Recipient relating to the Program
shall continue and
survive.
Everyone is permitted to copy and distribute copies of this
Agreement, but in
order to avoid inconsistency the Agreement is copyrighted and
may only be
modified in the following manner. The Agreement Steward
reserves the right to
publish new versions (including revisions) of this Agreement
from time to time.
No one other than the Agreement Steward has the right to
modify this Agreement.
IBM is the initial Agreement Steward. IBM may assign the
responsibility to serve
as the Agreement Steward to a suitable separate entity. Each
new version of the
Agreement will be given a distinguishing version number. The
Program (including
Contributions) may always be distributed subject to the version
of the Agreement
Apache CXF 2.2.8
under which it was received. In addition, after a new version of
the Agreement
is published, Contributor may elect to distribute the Program
(including its
Contributions) under the new version. Except as expressly
stated in Sections
2(a) and 2(b) above, Recipient receives no rights or licenses to
the
intellectual property of any Contributor under this Agreement,
whether
expressly, by implication, estoppel or otherwise. All rights in the
Program not
expressly granted under this Agreement are reserved.
This Agreement is governed by the laws of the State of New
York and the
intellectual property laws of the United States of America. No
party to this
Agreement will bring a legal action under this Agreement more
than one year
after the cause of action arose. Each party waives its rights to a
jury trial in
any resulting litigation.
This product includes mod_jk 1.2.30, which is distributed in
accordance with the following license agreement:
Apache License
Definitions
9 of this document.
by the
such entity.
exercising
a Contribution."
Object form.
Works; and
Contributions.
TOMCAT CONNECTORS SUBCOMPONENTS:
The Tomcat Connectors includes a number of subcomponents
with
separate copyright notices and license terms. Your use of the
source
code for the these subcomponents is subject to the terms and
conditions of the following licenses.
From native/common/ap_snprintf.c:
*
* cvt - IEEE floating point formatting routines.
*
Inc.
Derived from UNIX V7, Copyright(C) Caldera International
*
Copyright(C) Caldera International Inc. 2001-2002. All rights
reserved.
Redistribution and use in source and binary forms, with or
without
modification, are permitted provided that the following
conditions are
met:
Redistributions of source code and documentation must retain
the above
copyright notice, this list of conditions and the following
disclaimer.
Redistributions in binary form must reproduce the above
copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the
distribution.
All advertising materials mentioning features or use of this
software
must display the following acknowledgement:
This product includes software developed or owned by
Caldera
International, Inc.
Neither the name of Caldera International, Inc. nor the names
of other
contributors may be used to endorse or promote products
derived from
this software without specific prior written permission.
USE OF THE SOFTWARE PROVIDED FOR UNDER THIS LICENSE
BY CALDERA
INTERNATIONAL, INC. AND CONTRIBUTORS `ÀS IS'' AND ANY
EXPRESS OR IMPLIED
WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
ARE DISCLAIMED. IN
NO EVENT SHALL CALDERA INTERNATIONAL, INC. BE LIABLE
FOR ANY DIRECT,
INDIRECT INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR
SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
WHETHER IN CONTRACT,
OTHERWISE) ARISING IN
ANY, WAY OUT, OF THE USE OF THIS SOFTWARE EVEN IF
ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
Apache Tomcat 5.5.29
This product contains Apache Tomcat v.5.5.29 as well as the
Apache Tomcat v.5.5.29 subcomponents set forth below.
Apache Tomcat v.5.5.29 and such subcomponents are
distributed in accordance with the following terms:
Apache License
Definitions
9 of this document.
by the
such entity.
exercising
a Contribution."
Object form.
Works; and
Contributions.
APACHE TOMCAT SUBCOMPONENTS:
Apache Tomcat includes a number of subcomponents with
separate copyright notices
and license terms. Your use of the source code for the these
subcomponents is
subject to the terms and conditions of the following licenses.
For the jmx.jar component:
/*
====================================================
================
* The MX4J License, Version 1.0
*
* Copyright (c) 2001 MX4J. All rights reserved.
*
without
conditions
* are met:
*
copyright
*
copyright
the
* distribution.
*
redistribution,
* if any, must include the following acknowledgment:
*
"This product includes software developed by the
*
MX4J project (http://mx4j.sourceforge.net)."
* Alternately, this acknowledgment may appear in the
software itself,
* if and wherever such third-party acknowledgments
normally appear.
*
* 4. The names "MX4J" and "mx4j" must not be used to
endorse or promote
* products derived from this software without prior written
* permission. For written permission, please contact
biorn_steedom@users.sourceforge.net
*
"MX4J",
* nor may "MX4J" appear in their name, without prior written
* permission of Simone Bordet.
*
* THIS SOFTWARE IS PROVIDED `ÀS IS'' AND ANY EXPRESSED
OR IMPLIED
IMPLIED WARRANTIES
PURPOSE ARE
* DISCLAIMED. IN NO EVENT SHALL CARLOS QUIROZ OR
* ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
INCIDENTAL,
(INCLUDING, BUT NOT
SERVICES; LOSS OF
HOWEVER CAUSED AND
STRICT LIABILITY,
IN ANY WAY OUT
POSSIBILITY OF
* SUCH DAMAGE.
*
====================================================
================
*
* This software consists of voluntary contributions made by
many
* individuals on behalf of MX4J. For more information on
* MX4J, please see
*.
*/
For the jasper-jdt.jar component:
Eclipse Public License - v 1.0
TERMS OF THIS ECLIPSE PUBLIC
1. DEFINITIONS
documentation
distributed under this Agreement, and
from and are
'originates' from a
itself or anyone
distributed in
Program.
"Licensed Patents" mean patent claims licensable by a
or when
Agreement,
2. GRANT OF RIGHTS
hereby grants
license to
publicly perform,
if any, and such
hereby grants
transfer the
object code form.
Contributor, such
covered by the
combinations
hereunder.
the licenses to
its Contributions set forth herein, no assurances are provided by
any
other intellectual
any liability to
infringement of
exercising the
assumes sole
needed, if any.
Recipient to
that license
sufficient copyright
rights in its Contribution, if any, to grant the copyright license
set forth in
this Agreement.
3. REQUIREMENTS
code form under its
and
warranties and
merchantability and
for
consequential
are offered by
that Contributor alone and not by any other party; and
such Contributor,
and informs licensees how to obtain it in a reasonable manner
on or through a
medium customarily used for software exchange.
the Program.
Program.
Contribution, if
to identify the
license is
Contributor who
do so in a manner
Therefore, if
offering, such
losses, damages
and other legal
Contributor to the
Contributor in
product
claims or Losses
the Commercial
Commercial Contributor
to control, and cooperate with the Commercial Contributor in,
the defense and
any related settlement negotiations. The Indemnified
Contributor may
participate in any such claim at its own expense.
commercial product
offers warranties
are such
section, the
the other
the Commercial
5. NO WARRANTY
its exercise of
rights under this Agreement , including but not limited to the
risks and costs
of program errors, compliance with applicable laws, damage to
or loss of data,
operations.
RECIPIENT NOR ANY
OF SUCH DAMAGES.
7. GENERAL
under applicable
remainder of the
make such
If Recipient institutes patent litigation against any entity
(including a
Program itself
(excluding combinations of the Program with other software or
hardware)
granted under
fails to
Agreement and does
becoming aware of
soon as
this Agreement
shall continue and
survive.
Agreement, but in
may only be
from time to time.
The Eclipse Foundation is the initial Agreement Steward. The
Eclipse Foundation
may assign the responsibility to serve as the Agreement
Steward to a suitable
separate entity. Each new version of the Agreement will be
given a
distinguishing version number. The Program (including
Contributions) may always
be distributed subject to the version of the Agreement under
which it was
received. In addition, after a new version of the Agreement is
published,
Contributor may elect to distribute the Program (including its
Contributions)
under the new version. Except as expressly stated in Sections
2(a) and 2(b)
above, Recipient receives no rights or licenses to the intellectual
property of
any Contributor under this Agreement, whether expressly, by
implication,
estoppel or otherwise. All rights in the Program not expressly
granted under
this Agreement are reserved.
York and the
party to this
than one year
jury trial in
For the Windows Installer component:
* All NSIS source code, plug-ins, documentation, examples,
header files and
graphics, with the exception of the compression modules
and where
otherwise noted, are licensed under the zlib/libpng license.
* The zlib compression module for NSIS is licensed under the
zlib/libpng
license.
* The bzip2 compression module for NSIS is licensed under
the bzip2 license.
* The lzma compression module for NSIS is licensed under the
Common Public
License version 1.0.
zlib/libpng license
This software is provided 'as-is', without any express or implied
warranty. In
no event will the authors be held liable for any damages arising
from the use of
this software.
Permission is granted to anyone to use this software for any
purpose, including
commercial applications, and to alter it and redistribute it
freely, subject to
the following restrictions:
1. The origin of this software must not be misrepresented; you
must not claim
that you wrote the original software. If you use this
software in a
product, an acknowledgment in the product documentation
would be
appreciated but is not required.
2. Altered source versions must be plainly marked as such, and
must not be
misrepresented as being the original software.
3. This notice may not be removed or altered from any source
distribution.
bzip2 license
without modification,
are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the above
copyright notice,
this list of conditions and the following disclaimer.
must not claim
software in a
would be
must not be
4. The name of the author may not be used to endorse or
promote products
derived from this software without specific prior written
permission.
THIS SOFTWARE IS PROVIDED BY THE AUTHOR `ÀS IS AND ANY
EXPRESS OR IMPLIED
WARRANTIES OF
ARE DISCLAIMED. IN NO EVENT
SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES INCLUDING BUT
NOT LIMITED TO PROCUREMENT,
OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING
IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
ADVISED OF THE POSSIBILITY
OF SUCH DAMAGE.
Julian Seward, Cambridge, UK.
jseward@acm.org
Common Public License version 1.0
1. DEFINITIONS
documentation
distributed under this Agreement, and b) in the case of each
subsequent
Contributor:
from and are
'originates' from a
itself or anyone
distributed in
Program.
or when
Agreement,
2. GRANT OF RIGHTS
hereby grants
license to
publicly perform,
if any, and such
hereby grants
transfer the
object code form.
Contributor, such
covered by the
combinations
hereunder.
the licenses to
any
other intellectual
any liability to
infringement of
exercising the
assumes sole
needed, if any.
Recipient to
that license
set forth in
this Agreement.
3. REQUIREMENTS
code form under its
and
warranties and
merchantability and
for
consequential
are offered by
such Contributor,
on or through a
the Program.
Program.
Contribution, if
to identify the
license is
Contributor who
do so in a manner
Therefore, if
offering, such
losses, damages
and other legal
Contributor to the
Contributor in
product
claims or Losses
the Commercial
defense and any
may participate in
commercial product
offers warranties
are such
section, the
the other
the Commercial
5. NO WARRANTY
its exercise of
risks and costs of
loss of data,
operations.
RECIPIENT NOR ANY
OF SUCH DAMAGES.
7. GENERAL
under applicable
remainder of the
make such
with respect to
counterclaim in a
such Recipient
entity
that the Program
granted under
fails to
Agreement and does
becoming aware of
soon as
this Agreement
shall continue and
survive.
Agreement, but in
may only be
from time to time.
new version of the
Program (including
of the Agreement
the Agreement
(including its
stated in Sections
the
whether
Program not
York and the
party to this
than one year
jury trial in
Special exception for LZMA compression module
Igor Pavlov and Amir Szekely, the authors of the LZMA
compression module for
NSIS, expressly permit you to statically or dynamically link your
code (or bind
by name) to the files from the LZMA compression module for
NSIS without
subjecting your linked code to the terms of the Common Public
license version
1.0 Any modifications or additions to files from the LZMA
compression module
for NSIS, however, are subject to the terms of the Common
Public License version
1.0
jasper-jdt.jar
This product contains jasper-jdt.jar. The ECLIPSE
Subcomponents were obtained under the ECLIPSE v.1.0
license, the terms and conditions of which are set forth below.
The ECLIPSE Subcomponents
are distributed by CA for use with this CA product in
unmodified, object code form, under
the CA End User License Agreement. Any provisions in the CA
End User License Agreement that
differ from the ECLIPSE license are offered by CA alone and not
by any other party. CA makes
the source code for the ECLIPSE Subcomponents available at
ECLIPSE v.1.0. license:
jasper-jdt.jar component:
TERMS OF THIS ECLIPSE PUBLIC
1. DEFINITIONS
documentation
distributed under this Agreement, and
from and are
'originates' from a
itself or anyone
distributed in
Program.
"Licensed Patents" mean patent claims licensable by a
or when
Agreement,
2. GRANT OF RIGHTS
hereby grants
license to
publicly perform,
if any, and such
hereby grants
transfer the
object code form.
Contributor, such
covered by the
combinations
hereunder.
the licenses to
any
other intellectual
any liability to
infringement of
exercising the
assumes sole
needed, if any.
Recipient to
that license
set forth in
this Agreement.
3. REQUIREMENTS
code form under its
and
warranties and
merchantability and
for
consequential
are offered by
such Contributor,
on or through a
the Program.
Program.
Contribution, if
to identify the
license is
Contributor who
do so in a manner
Therefore, if
offering, such
losses, damages
and other legal
Contributor to the
Contributor in
product
claims or Losses
the Commercial
Commercial Contributor
to control, and cooperate with the Commercial Contributor in,
the defense and
any related settlement negotiations. The Indemnified
Contributor may
participate in any such claim at its own expense.
commercial product
offers warranties
are such
section, the
the other
the Commercial
5. NO WARRANTY
its exercise of
rights under this Agreement , including but not limited to the
risks and costs
of program errors, compliance with applicable laws, damage to
or loss of data,
operations.
RECIPIENT NOR ANY
OF SUCH DAMAGES.
7. GENERAL
under applicable
remainder of the
make such
(including a
Program itself
(excluding combinations of the Program with other software or
hardware)
granted under
fails to
Agreement and does
becoming aware of
soon as
this Agreement
shall continue and
survive.
Agreement, but in
may only be
from time to time.
The Eclipse Foundation is the initial Agreement Steward. The
Eclipse Foundation
may assign the responsibility to serve as the Agreement
Steward to a suitable
separate entity. Each new version of the Agreement will be
given a
distinguishing version number. The Program (including
Contributions) may always
be distributed subject to the version of the Agreement under
which it was
received. In addition, after a new version of the Agreement is
published,
Contributions)
under the new version. Except as expressly stated in Sections
2(a) and 2(b)
above, Recipient receives no rights or licenses to the intellectual
property of
any Contributor under this Agreement, whether expressly, by
implication,
granted under
this Agreement are reserved.
York and the
party to this
than one year
jury trial in
For the Windows Installer component:
* All NSIS source code, plug-ins, documentation, examples,
header files and
graphics, with the exception of the compression modules
and where
otherwise noted, are licensed under the zlib/libpng license.
* The zlib compression module for NSIS is licensed under the
zlib/libpng
license.
* The bzip2 compression module for NSIS is licensed under
the bzip2 license.
* The lzma compression module for NSIS is licensed under the
Common Public
License version 1.0.
zlib/libpng license
This software is provided 'as-is', without any express or implied
warranty. In
no event will the authors be held liable for any damages arising
from the use of
this software.
purpose, including
commercial applications, and to alter it and redistribute it
freely, subject to
the following restrictions:
must not claim
software in a
would be
must not be
3. This notice may not be removed or altered from any source
distribution.
bzip2 license
without modification,
copyright notice,
this list of conditions and the following disclaimer.
must not claim
software in a
would be
must not be
4. The name of the author may not be used to endorse or
promote products
derived from this software without specific prior written
permission.
THIS SOFTWARE IS PROVIDED BY THE AUTHOR `ÀS IS AND ANY
EXPRESS OR IMPLIED
WARRANTIES OF
ARE DISCLAIMED. IN NO EVENT
SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES INCLUDING BUT
NOT LIMITED TO PROCUREMENT,
OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING
IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
ADVISED OF THE POSSIBILITY
OF SUCH DAMAGE.
Julian Seward, Cambridge, UK.
jseward@acm.org
This product contains CPL Subcomponents. The CPL
Subcomponents were was
obtained under the CPL v.1.0 license, the terms and conditions
of which are set forth below.
The CPL Subcomponents are distributed by CA for use with this
CA product in unmodified,
object code form, under the CA End User License Agreement.
Any provisions in the CA End User
License Agreement that differ from the CPL are offered by CA
alone and not by any other
party. CA makes the source code for the CPL Subcomponents
available at
CPL v.1.0. license:
Common Public License version 1.0
1. DEFINITIONS
documentation
distributed under this Agreement, and b) in the case of each
subsequent
Contributor:
from and are
'originates' from a
itself or anyone
distributed in
Program.
or when
Agreement,
2. GRANT OF RIGHTS
hereby grants
license to
publicly perform,
if any, and such
hereby grants
transfer the
object code form.
Contributor, such
covered by the
combinations
hereunder.
the licenses to
any
other intellectual
any liability to
infringement of
exercising the
assumes sole
needed, if any.
Recipient to
that license
set forth in
this Agreement.
3. REQUIREMENTS
code form under its
and
warranties and
merchantability and
for
consequential
are offered by
such Contributor,
on or through a
the Program.
Program.
Contribution, if
to identify the
license is
Contributor who
do so in a manner
Therefore, if
offering, such
losses, damages
and other legal
Contributor to the
Contributor in
product
claims or Losses
the Commercial
defense and any
may participate in
commercial product
offers warranties
are such
section, the
the other
the Commercial
5. NO WARRANTY
its exercise of
risks and costs of
loss of data,
operations.
RECIPIENT NOR ANY
OF SUCH DAMAGES.
7. GENERAL
under applicable
remainder of the
make such
with respect to
counterclaim in a
such Recipient
entity
that the Program
granted under
fails to
Agreement and does
becoming aware of
soon as
this Agreement
shall continue and
survive.
Agreement, but in
may only be
from time to time.
new version of the
Program (including
of the Agreement
the Agreement
(including its
stated in Sections
the
whether
Program not
York and the
party to this
than one year
jury trial in
Special exception for LZMA compression module
Igor Pavlov and Amir Szekely, the authors of the LZMA
compression module for
NSIS, expressly permit you to statically or dynamically link your
code (or bind
by name) to the files from the LZMA compression module for
NSIS without
subjecting your linked code to the terms of the Common Public
license version
1.0 Any modifications or additions to files from the LZMA
compression module
for NSIS, however, are subject to the terms of the Common
Public License version
1.0
EclipseLink 1.1.2
EclipseLink 1.1.2
EclipseLink 1.1.2 (the Third Party Product) is distributed by CA
for use with this CA product in unmodified, object code form.
The source code for the Third Party Product may be found at
http://opensrcd.ca.com. Your use of the Third Party Product is
subject to the following terms and conditions. Any provisions
set forth elsewhere in this Agreement that differ from the
following terms and conditions are offered by CA alone:
TERMS OF THIS ECLIPSE PUBLIC LICENSE (""AGREEMENT""). ANY
USE, REPRODUCTION OR DISTRIBUTION OF THE PROGRAM
1. DEFINITIONS
""Contribution"" means:
documentation distributed under this Agreement, and
from and are distributed by that particular Contributor. A
Contribution 'originates' from a Contributor if it was added to
the Program by such Contributor itself or anyone acting on such
Contributor's behalf. Contributions do not include additions to
distributed in conjunction with the Program under their own
license agreement, and (ii) are not derivative works of the
Program.
EclipseLink 1.1.2
""Contributor"" means any person or entity that distributes the
Program.
""Licensed Patents "" mean patent claims licensable by a
Contributor which are necessarily infringed by the use or sale of
its Contribution alone or when combined with the Program.
""Program"" means the Contributions distributed in accordance
""Recipient"" means anyone who receives the Program under
this Agreement, including all Contributors.
2. GRANT OF RIGHTS
hereby grants Recipient a non-exclusive, worldwide, royaltyfree copyright license to reproduce, prepare derivative works
of, publicly display, publicly perform, distribute and sublicense
the Contribution of such Contributor, if any, and such derivative
works, in source code and object code form.
hereby grants Recipient a non-exclusive, worldwide, royaltyfree patent license under Licensed Patents to make, use, sell,
offer to sell, import and otherwise transfer the Contribution of
such Contributor, if any, in source code and object code form.
Contribution and the Program if, at the time the Contribution is
added by the Contributor, such addition of the Contribution
causes such combination to be covered by the Licensed Patents.
The patent license shall not apply to any other combinations
hereunder.
EclipseLink 1.1.2
the licenses to its Contributions set forth herein, no assurances
are provided by any Contributor that the Program does not
infringe the patent or other intellectual property rights of any
other entity. Each Contributor disclaims any liability to Recipient
for claims brought by any other entity based on infringement of
exercising the rights and licenses granted hereunder, each
Recipient hereby assumes sole responsibility to secure any
other intellectual property rights needed, if any. For example, if
a third party patent license is required to allow Recipient to
that license before distributing the Program.
sufficient copyright rights in its Contribution, if any, to grant the
copyright license set forth in this Agreement.
3. REQUIREMENTS
code form under its own license agreement, provided that:
and
warranties and conditions, express and implied, including
warranties or conditions of title and non-infringement, and
implied warranties or conditions of merchantability and fitness
for a particular purpose;
for damages, including direct, indirect, special, incidental and
consequential damages, such as lost profits;
EclipseLink 1.1.2
are offered by that Contributor alone and not by any other
party; and
such Contributor, and informs licensees how to obtain it in a
reasonable manner on or through a medium customarily used
for software exchange.
the Program.
contained within the Program.
Contribution, if any, in a manner that reasonably allows
subsequent Recipients to identify the originator of the
Contribution.
EclipseLink 1.1.2
responsibilities with respect to end users, business partners and
the like. While this license is intended to facilitate the
commercial use of the Program, the Contributor who includes
the Program in a commercial product offering should do so in a
manner which does not create potential liability for other
Contributors. Therefore, if a Contributor includes the Program
in a commercial product offering, such Contributor
(""Commercial Contributor"") hereby agrees to defend and
indemnify every other Contributor (""Indemnified
Contributor"") against any losses, damages and costs
(collectively ""Losses"") arising from claims, lawsuits and other
legal actions brought by a third party against the Indemnified
Contributor to the extent caused by the acts or omissions of
such Commercial Contributor in connection with its distribution
of the Program in a commercial product offering. The
obligations in this section do not apply to any claims or Losses
infringement. In order to qualify, an Indemnified Contributor
must: a) promptly notify the Commercial Contributor in writing
of such claim, and b) allow the Commercial Contributor to
defense and any related settlement negotiations. The
Indemnified Contributor may participate in any such claim at its
own expense.
commercial product offering, Product X. That Contributor is
then a Commercial Contributor. If that Commercial Contributor
then makes performance claims, or offers warranties related to
Product X, those performance claims and warranties are such
section, the Commercial Contributor would have to defend
claims against the other Contributors related to those
performance claims and warranties, and if a court requires any
other Contributor to pay any damages as a result, the
Commercial Contributor must pay those damages.
EclipseLink 1.1.2
5. NO WARRANTY
PROGRAM IS PROVIDED ON AN ""AS IS"" BASIS, WITHOUT
WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS
OR IMPLIED INCLUDING, WITHOUT LIMITATION, ANY
WARRANTIES OR CONDITIONS OF TITLE, NON-INFRINGEMENT,
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Each Recipient is solely responsible for determining the
appropriateness of using and distributing the Program and
assumes all risks associated with its exercise of rights under this
Agreement , including but not limited to the risks and costs of
loss of data, programs or equipment, and unavailability or
interruption of operations.
RECIPIENT NOR ANY CONTRIBUTORS SHALL HAVE ANY LIABILITY
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY,
OR CONSEQUENTIAL DAMAGES (INCLUDING WITHOUT
LIMITATION LOST PROFITS), HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OR DISTRIBUTION OF
THE PROGRAM OR THE EXERCISE OF ANY RIGHTS GRANTED
HEREUNDER, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
DAMAGES.
7. GENERAL
under applicable law, it shall not affect the validity or
enforceability of the remainder of the terms of this Agreement,
and without further action by the parties hereto, such provision
shall be reformed to the minimum extent necessary to make
such provision valid and enforceable.
EclipseLink 1.1.2
that the Program itself (excluding combinations of the Program
with other software or hardware) infringes such Recipient's
patent(s), then such Recipient's rights granted under Section
2(b) shall terminate as of the date such litigation is filed.
fails to comply with any of the material terms or conditions of
this Agreement and does not cure such failure in a reasonable
period of time after becoming aware of such noncompliance. If
all Recipient's rights under this Agreement terminate, Recipient
agrees to cease use and distribution of the Program as soon as
this Agreement and any licenses granted by Recipient relating
to the Program shall continue and survive.
Agreement, but in order to avoid inconsistency the Agreement
is copyrighted and may only be modified in the following
manner. The Agreement Steward reserves the right to publish
new versions (including revisions) of this Agreement from time
to time. No one other than the Agreement Steward has the
right to modify this Agreement. The Eclipse Foundation is the
initial Agreement Steward. The Eclipse Foundation may assign
the responsibility to serve as the Agreement Steward to a
suitable separate entity. Each new version of the Agreement
will be given a distinguishing version number. The Program
(including Contributions) may always be distributed subject to
the version of the Agreement under which it was received. In
addition, after a new version of the Agreement is published,
stated in Sections 2(a) and 2(b) above, Recipient receives no
rights or licenses to the intellectual property of any Contributor
under this Agreement, whether expressly, by implication,
granted under this Agreement are reserved.
EclipseLink 1.1.2
York and the intellectual property laws of the United States of
America. No party to this Agreement will bring a legal action
under this Agreement more than one year after the cause of
action arose. Each party waives its rights to a jury trial in any
resulting litigation.
Eclipse Distribution License Version 1.0
Copyright (c) 2007, Eclipse Foundation, Inc. and its licensors.
All rights reserved.
without modification, are permitted provided that the following
conditions are met:
* Redistributions of source code must retain the above
disclaimer.
* Redistributions in binary form must reproduce the above
disclaimer in the documentation and/or other materials
provided with the distribution.
* Neither the name of the Eclipse Foundation, Inc. nor the
names of its contributors may be used to endorse or promote
products derived from this software without specific prior
written permission.
EclipseLink 1.1.2
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS
AND CONTRIBUTORS ""AS IS"" AND ANY EXPRESS OR IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
iquery 1.3.2
iquery 1.3.2
This product contains JQuery, which CA has elected to license
under the terms of the MIT license. JQuery is distributed in
accordance with the following license:
Copyright (c) 2009 John Resig, http://jquery.com/
Permission is hereby granted, free of charge, to any
person obtaining a copy of this software and associated
documentation files (the
&||&Software&||&), to deal in the Software without
restriction, including
without limitation the rights to use, copy, modify, merge,
publish,
distribute, sublicense, and/or sell copies of the Software, and to
permit persons to whom the Software is furnished to do so,
subject to
the following conditions:
The above copyright notice and this permission notice shall be
included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED &||&AS IS&||&, WITHOUT
WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE
WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
COPYRIGHT HOLDERS BE
LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
WHETHER IN AN ACTION
OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
OR IN CONNECTION
WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
This product contains Java Persistence API v.1 (the CDDL File)
which CA has elected to license under, and the use of which is
subject to, the Common Development and Distribution License,
Version 1.0. The source code for the CDDL File may be found
here: http://opensrcd.ca.com.
Java Service Wrapper (JSW) Standard 3.3.9
This product includes Java Service Wrapper (JSW) 3.3.9 from
Tanuki Software, Inc. which includes software and
documentation components developed in part by Silver Egg
Technology, Inc.("SET") prior to 2001 and released under the
following license.
Copyright (c) 2001 Silver Egg Technology
Permission is hereby granted, free of charge, to any person
obtaining a copy of this software and associated
documentation
files (the "Software"), to deal in the Software without
restriction, including without limitation the rights to use,
copy, modify, merge, publish, distribute, sub-license, and/or
sell copies of the Software, and to permit persons to whom
the
Software is furnished to do so, subject to the following
conditions:
The above copyright notice and this permission notice shall
be
included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY
OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE
WARRANTIES
OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE
AND
NON-INFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
COPYRIGHT
HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY,
WHETHER IN AN ACTION OF CONTRACT, TORT OR
OTHERWISE, ARISING
FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR
THE USE OR
OTHER DEALINGS IN THE SOFTWARE.
JAXB
JAXB
JAXB was obtained under the CDDL v.1.0 license, the terms and
conditions of which are set forth below. JAXB is distributed by
form, under the CA End User License Agreement. Any provisions
in the CA End User License Agreement that differ from the CDDL
are offered by CA alone and not by any other party. Source code
for JAXB is available at https://jaxb.dev.java.net/. In addition,
CA makes the source code for JAXB available at
CDDL v.1.0. license:
COMMON DEVELOPMENT AND DISTRIBUTION LICENSE (CDDL)
Version 1.0
1. Definitions.
1.1. “Contributor” means each individual or entity that
creates or contributes to the creation of Modifications.
1.2. “Contributor Version” means the combination of the
Original Software, prior Modifications used by a Contributor (if
any), and the Modifications made by that particular
Contributor.
1.3. “Covered Software” means (a) the Original Software,
or (b) Modifications, or (c) the combination of files containing
Original Software with files containing Modifications, in each
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 Software available under this License.
JAXB
1.6. “Larger Work” means a work which combines
Covered Software or portions thereof with 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 rights
conveyed herein.
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 contents of 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 this License.
1.10. “Original Software” means the Source Code and
Executable form of computer software 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 patent Licensable
by grantor.
1.12. “Source Code” means (a) the common form of
computer software code in which modifications are made and
(b) associated documentation included in or with such code.
JAXB
1.13. “You” (or “Your”) means an individual or a legal
entity exercising rights under, and complying with all of the
terms of, this License. For legal entities, “You” includes any
entity which controls, is controlled by, or is under common
control with You. For purposes of this definition, “control”
means (a) the power, direct or indirect, to cause the direction or
management of such entity, whether by contract or otherwise,
or (b) ownership of more than fifty percent (50%) of the
outstanding shares or beneficial ownership of such entity.
2. License Grants.
Conditioned upon Your compliance with Section 3.1
below and subject to third party intellectual property claims,
the Initial Developer hereby grants You a world-wide, royaltyfree, non-exclusive license:
(a) under intellectual property rights (other than
patent or trademark) Licensable by Initial Developer, to use,
reproduce, modify, display, perform, sublicense and distribute
the Original Software (or portions thereof), with or without
Modifications, and/or as part of a Larger Work; and
(b) under Patent Claims infringed by the making, using
or selling of Original Software, to make, have made, use,
practice, sell, and offer for sale, and/or otherwise dispose of the
Original Software (or portions thereof).
(c) The licenses granted in Sections 2.1(a) and (b) are
effective on the date Initial Developer first distributes or
otherwise makes the Original Software available to a third party
under the terms of this License.
JAXB
(d) Notwithstanding Section 2.1(b) above, no patent
license is granted: (1) for code that You delete from the Original
Software, or (2) for infringements caused by: (i) the
modification of the Original Software, or (ii) the combination of
the Original Software with other software or devices.
Conditioned upon Your compliance with Section 3.1
below and subject to third party intellectual 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 by Contributor to use,
reproduce, modify, display, perform, sublicense and distribute
the Modifications created by such Contributor (or portions
thereof), either on an unmodified basis, 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 made by that Contributor
either alone and/or in combination with its Contributor Version
(or portions of such combination), to make, use, sell, offer for
sale, have made, and/or otherwise dispose of: (1) Modifications
made by that Contributor (or portions thereof); and (2) the
combination of Modifications made by that Contributor with its
Contributor Version (or portions of such combination).
(c) The licenses granted in Sections 2.2(a) and 2.2(b)
are effective on the date Contributor first distributes or
otherwise makes the Modifications available to a third party.
JAXB
(d) Notwithstanding Section 2.2(b) above, no patent
license is granted: (1) for any code that Contributor has deleted
from the Contributor Version; (2) for infringements caused by:
(i) third party modifications of Contributor Version, or (ii) the
combination of Modifications made by that Contributor with
other software (except as part of the Contributor Version) or
other devices; or (3) under Patent Claims infringed by Covered
Software in the absence of Modifications made by that
Contributor.
Any Covered Software that You distribute or otherwise
make available in Executable form must also be made available
in Source Code form and that Source Code form must be
distributed only under the terms of this License. You must
include a copy of this License with every copy of the Source
Code form of the Covered Software You distribute or otherwise
make available. You must inform recipients of any such Covered
Software in Executable form as to how they can obtain such
Covered Software in Source Code form in a reasonable manner
on or through a medium customarily used for software
exchange.
3.2. Modifications.
The Modifications that You create or to which You
contribute are governed by the terms of this License. You
represent that You believe Your Modifications are Your original
creation(s) and/or You have sufficient rights to grant the rights
conveyed by this License.
JAXB
You must include a notice in each of Your Modifications
that identifies You as the Contributor of the Modification. You
may not remove or alter any copyright, patent or trademark
notices contained within the Covered Software, or any notices
of licensing or any 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 form that alters or restricts the
applicable version of this License or the recipients’ rights
hereunder. 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 Initial
Developer 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 to
indemnify the Initial Developer and every Contributor for any
liability incurred by the Initial Developer or such Contributor as
a result of warranty, support, indemnity or liability terms You
offer.
JAXB
You may distribute the Executable form of the Covered
Software under the terms of this License or under the terms of a
license of Your choice, which may contain terms different from
this License, provided that You are in compliance with the terms
of this License and that the license for the Executable form does
not attempt to limit or alter the recipient’s rights in the Source
Code form from the rights set forth in this License. If You
distribute the Covered Software in Executable form under a
different license, You must make it absolutely 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 Initial Developer and every Contributor for any
liability incurred by the Initial Developer or such Contributor 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 not governed 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 the Covered Software.
4.1. New Versions.
Sun Microsystems, Inc. is the initial license steward and
may publish revised and/or new versions of this License 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 to modify this License.
4.2 Effect of New Versions.
JAXB
You may always continue to use, distribute or otherwise
make the Covered Software available under the terms of the
version of the License under which You originally received the
Covered Software. If the Initial Developer includes a notice in
the Original Software prohibiting it from being distributed or
otherwise made available under any subsequent version of the
License, You must distribute and make the Covered Software
available under the terms of the version of the License under
which You originally received the Covered Software. Otherwise,
You may also choose to use, distribute or otherwise make the
Covered Software available under the terms of any subsequent
version 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 Original Software, You may create
and use a modified version of this License if You: (a) rename the
license and remove any references to the name of the license
steward (except to note that the license differs from this
License); and (b) otherwise make it clear that the license
contains terms which differ from this License.
JAXB
COVERED SOFTWARE IS PROVIDED UNDER THIS LICENSE ON
AN “AS IS” BASIS, WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION,
WARRANTIES THAT THE COVERED SOFTWARE IS FREE OF
DEFECTS, MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR
NON-INFRINGING. THE ENTIRE RISK AS TO THE QUALITY AND
PERFORMANCE OF THE COVERED SOFTWARE IS WITH YOU.
SHOULD ANY COVERED SOFTWARE PROVE DEFECTIVE IN ANY
RESPECT, YOU (NOT THE INITIAL DEVELOPER OR ANY OTHER
CONTRIBUTOR) ASSUME THE COST OF ANY NECESSARY
SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER OF
WARRANTY CONSTITUTES AN ESSENTIAL PART OF THIS LICENSE.
NO USE OF ANY COVERED SOFTWARE IS AUTHORIZED
HEREUNDER EXCEPT UNDER THIS DISCLAIMER.
6. TERMINATION.
terminate automatically if You fail to comply with terms herein
and fail to cure such breach within 30 days of becoming aware
of the breach. Provisions which, by their nature, must remain in
effect beyond the termination of this License shall survive.
JAXB
6.2. If You assert a patent infringement claim (excluding
declaratory judgment actions) against Initial Developer or a
Contributor (the Initial Developer or Contributor against whom
You assert such claim is referred to as “Participant”) alleging
that the Participant Software (meaning the Contributor Version
where the Participant is a Contributor or the Original Software
where the Participant is the Initial Developer) directly or
indirectly infringes any patent, then any and all rights granted
directly or indirectly to You by such Participant, the Initial
Developer (if the Initial Developer is not the Participant) and all
Contributors under Sections 2.1 and/or 2.2 of this License shall,
upon 60 days notice from Participant terminate prospectively
and automatically at the expiration of such 60 day notice
period, unless if within such 60 day period You withdraw Your
claim with respect to the Participant Software against such
Participant either unilaterally or pursuant 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 that have been validly granted by
You or any distributor hereunder prior to termination (excluding
licenses granted to You by any distributor) shall survive
termination.
JAXB
UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL
THEORY, WHETHER TORT (INCLUDING NEGLIGENCE),
CONTRACT, OR OTHERWISE, SHALL YOU, THE INITIAL
DEVELOPER, ANY OTHER CONTRIBUTOR, OR ANY DISTRIBUTOR
OF COVERED SOFTWARE, OR ANY SUPPLIER OF ANY OF SUCH
PARTIES, BE LIABLE TO ANY PERSON FOR ANY INDIRECT,
SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY
CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR
LOST PROFITS, LOSS OF GOODWILL, WORK STOPPAGE,
COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL
OTHER COMMERCIAL DAMAGES OR LOSSES, EVEN IF SUCH
PARTY SHALL HAVE BEEN INFORMED OF THE POSSIBILITY OF
SUCH DAMAGES. THIS LIMITATION OF LIABILITY SHALL NOT
APPLY TO LIABILITY FOR DEATH OR PERSONAL INJURY
RESULTING FROM SUCH PARTY’S NEGLIGENCE TO THE EXTENT
APPLICABLE LAW PROHIBITS SUCH LIMITATION. SOME
OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THIS
EXCLUSION AND LIMITATION MAY NOT APPLY TO YOU.
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 48 C.F.R. §
252.227-7014(a)(1)) and “commercial computer software
documentation” as such terms are used in 48 C.F.R. 12.212
(Sept. 1995). Consistent with 48 C.F.R. 12.212 and 48 C.F.R.
227.7202-1 through 227.7202-4 (June 1995), all U.S.
Government End Users acquire Covered Software with only
those rights set forth herein. This U.S. Government Rights clause
is in lieu of, and supersedes, any other FAR, DFAR, or other
clause or provision that addresses Government rights in
computer software under this License.
9. MISCELLANEOUS.
JAXB
subject matter hereof. If any provision of this License is held to
be unenforceable, such provision shall be reformed only to the
extent necessary to make it enforceable. This License shall be
governed by the law of the jurisdiction specified in a notice
contained within the Original Software (except to the extent
applicable law, if any, provides otherwise), excluding such
jurisdiction’s conflict-of-law provisions. Any litigation relating to
this License shall be subject to the jurisdiction of the courts
located in the jurisdiction and venue specified in a notice
contained within the Original Software, with the losing party
responsible for costs, including, without limitation, court costs
and reasonable attorneys’ fees and expenses. The application of
the United Nations Convention on Contracts for the
International Sale of Goods is expressly excluded. Any law or
regulation which provides that the language of a contract shall
be construed against the drafter shall not apply to this License.
You agree that You alone are responsible for compliance with
the United States export administration regulations (and the
export control laws and regulation of any other countries) when
You use, distribute or otherwise make available any Covered
Software.
As between Initial Developer and the Contributors, each
party is responsible for claims and damages arising, directly or
indirectly, out of its utilization of rights under this License and
You agree to work with Initial Developer and Contributors to
distribute such responsibility on an equitable basis. Nothing
herein is intended or shall be deemed to constitute any
admission of liability.
NOTICE PURSUANT TO SECTION 9 OF THE COMMON
DEVELOPMENT AND DISTRIBUTION LICENSE (CDDL)
JAXB
The code released under the CDDL shall be governed by the
laws of the State of California (excluding conflict-of-law
provisions). Any litigation relating to this License shall be subject
to the jurisdiction of the Federal Courts of the Northern District
of California and the state courts of the State of California, with
venue lying in Santa Clara County, California.
The source code version of Rhino 1.5 Release 4.1 is licensed
under the Netscape Public License Version 1.1 which can be
found at http://www.mozilla.org/NPL/ and is made available for
download from http://opensrcd.ca.com/ips/3039_8/ The
Netscape Public License Version 1.1 (""NPL"") consists of the
Mozilla Public License Version 1.1 with the following
Amendments, including Exhibit A-Netscape Public License. Files
identified with ""Exhibit A-Netscape Public License"" are
governed by the Netscape Public License Version 1.1.
Additional Terms applicable to the Netscape Public License.
I. Effect.
These additional terms described in this Netscape Public License
-- Amendments shall apply to the Mozilla Communicator client
code and to all Covered Code under this License.
II. ""Netscape's Branded Code"" means Covered Code that
Netscape distributes and/or permits others to distribute under
one or more trademark(s) which are controlled by Netscape but
which are not licensed for use under this License.
III. Netscape and logo.
This License does not grant any rights to use the trademarks
""Netscape"", the ""Netscape N and horizon"" logo or the
""Netscape lighthouse"" logo, ""Netcenter"", ""Gecko"",
""Java"" or ""JavaScript"", ""Smart Browsing"" even if such
marks are included in the Original Code or Modifications.
IV. Inability to Comply Due to Contractual Obligation.
Prior to licensing the Original Code under this License, Netscape
has licensed third party code for use in Netscape's Branded
Code. To the extent that Netscape is limited contractually from
making such third party code available under this License,
Netscape may choose to reintegrate such code into Covered
Code without being required to distribute such code in Source
Code form, even if such code would otherwise be considered
""Modifications"" under this License.
V. Use of Modifications and Covered Code by Initial Developer.
V.1. In General.
The obligations of Section 3 apply to Netscape, except to the
extent specified in this Amendment, Section V.2 and V.3.
V.2. Other Products.
Netscape may include Covered Code in products other than the
Netscape's Branded Code which are released by Netscape
during the two (2) years following the release date of the
Original Code, without such additional products becoming
subject to the terms of this License, and may license such
additional products on different terms from those contained in
this License.
V.3. Alternative Licensing.
Netscape may license the Source Code of Netscape's Branded
Code, including Modifications incorporated therein, without
such Netscape Branded Code becoming subject to the terms of
this License, and may license such Netscape Branded Code on
different terms from those contained in this License.
VI. Litigation.
Notwithstanding the limitations of Section 11 above, the
provisions regarding litigation in Section 11(a), (b) and (c) of the
License shall apply to all disputes relating to this License.
EXHIBIT A-Netscape Public License.
""The contents of this file are subject to the Netscape Public
License Version 1.1 (the ""License""); you may not use this file
except in compliance with the License. You may obtain a copy of
the License at http://www.mozilla.org/NPL/
Software distributed under the License is distributed on an ""AS
IS"" basis, WITHOUT WARRANTY OF ANY KIND, either express or
implied. See the License for the specific language governing
rights and limitations under the License.
The Original Code is Mozilla Communicator client code, released
March 31, 1998.
The Initial Developer of the Original Code is Netscape
Communications Corporation. Portions created by Netscape are
Copyright (C) 1998-1999 Netscape Communications
Corporation. All Rights Reserved.
Contributor(s): ______________________________________.
Alternatively, the contents of this file may be used under the
terms of the _____ license (the ""[___] License""), in which
case the provisions of [______] License are applicable instead
of those above. If you wish to allow use of your version of this
file only under the terms of the [____] License and not to allow
others to use your version of this file under the NPL, indicate
your decision by deleting the provisions above and replace
them with the notice and other provisions required by the [___]
License. If you do not delete the provisions above, a recipient
may use your version of this file under either the NPL or the
[___] License.""
-------------------------------------------------------------------------------MOZILLA PUBLIC LICENSE
Version 1.1
-------------------------------------------------------------------------------1. Definitions.
1.0.1. ""Commercial Use"" means distribution or otherwise
making the Covered Code available to a third party.
1.1. ""Contributor"" means each entity that creates or
contributes to the creation of Modifications.
1.2. ""Contributor Version"" means the combination of the
Original Code, prior Modifications used by a Contributor, and
the Modifications made by that particular Contributor.
1.3. ""Covered Code"" means the Original Code or Modifications
or the combination of the Original Code and Modifications, in
each case including portions thereof.
1.4. ""Electronic Distribution Mechanism"" means a mechanism
generally accepted in the software development community for
the electronic transfer of data.
1.5. ""Executable"" means Covered Code in any form other than
Source Code.
1.6. ""Initial Developer"" means the individual or entity
identified as the Initial Developer in the Source Code notice
required by Exhibit A.
1.7. ""Larger Work"" means a work which combines Covered
Code or portions thereof with code not governed by the terms
of this License.
1.8. ""License"" means this document.
1.8.1. ""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 rights
conveyed herein.
1.9. ""Modifications"" means any addition to or deletion from
the substance or structure of either the Original Code or any
previous Modifications. When Covered Code is released as a
series of files, a Modification is:
A. Any addition to or deletion from the contents of a file
containing Original Code or previous Modifications.
B. Any new file that contains any part of the Original Code or
previous Modifications.
1.10. ""Original Code"" means Source Code of computer
software code which is described in the Source Code notice
required by Exhibit A as Original Code, and which, at the time of
its release under this License is not already Covered Code
governed by this License.
1.10.1. ""Patent Claims"" means any patent claim(s), now
owned or hereafter acquired, including without limitation,
method, process, and apparatus claims, in any patent Licensable
by grantor.
1.11. ""Source Code"" means the preferred form of the Covered
Code for making modifications to it, including all modules it
contains, plus any associated interface definition files, scripts
used to control compilation and installation of an Executable, or
source code differential comparisons against either the Original
Code or another well known, available Covered Code of the
Contributor's choice. The Source Code can be in a compressed
or archival form, provided the appropriate decompression or
de-archiving software is widely available for no charge.
1.12. ""You"" (or ""Your"") means an individual or a legal entity
exercising rights under, and complying with all of the terms of,
this License or a future version of this License issued under
Section 6.1. For legal entities, ""You"" includes any entity which
controls, is controlled by, or is under common control with You.
For purposes of this definition, ""control"" means (a) the power,
direct or indirect, to cause the direction or management of such
entity, whether by contract or otherwise, or (b) ownership of
more than fifty percent (50%) of the outstanding shares or
beneficial ownership of such entity.
2. Source Code License.
The Initial Developer hereby grants You a world-wide, royaltyfree, non-exclusive license, subject to third party intellectual
property claims:
trademark) Licensable by Initial Developer to use, reproduce,
modify, display, perform, sublicense and distribute the Original
Code (or portions thereof) with or without Modifications,
and/or as part of a Larger Work; and
(b) under Patents Claims infringed by the making, using or
selling of Original Code, to make, have made, use, practice, sell,
and offer for sale, and/or otherwise dispose of the Original
Code (or portions thereof).
(c) the licenses granted in this Section 2.1(a) and (b) are
effective on the date Initial Developer first distributes Original
Code under the terms of this License.
granted: 1) for code that You delete from the Original Code; 2)
separate from the Original Code; or 3) for infringements caused
by: i) the modification of the Original Code or ii) the
combination of the Original Code with other software or
devices.
Subject to third party intellectual property claims, each
Contributor hereby grants You a world-wide, royalty-free, nonexclusive license
trademark) Licensable by Contributor, to use, reproduce,
modify, display, perform, sublicense and distribute the
Modifications created by such Contributor (or portions thereof)
either on an unmodified basis, with other Modifications, as
Covered Code and/or as part of a Larger Work; and
(b) under Patent Claims infringed by the making, using, or
selling of Modifications made by that Contributor either alone
and/or in combination with its Contributor Version (or portions
of such combination), to make, use, sell, offer for sale, have
made, and/or otherwise dispose of: 1) Modifications made by
that Contributor (or portions thereof); and 2) the combination
of Modifications made by that Contributor with its Contributor
Version (or portions of such combination).
(c) the licenses granted in Sections 2.2(a) and 2.2(b) are
effective on the date Contributor first makes Commercial Use of
the Covered Code.
granted: 1) for any code that Contributor has deleted from the
Contributor Version; 2) separate from the Contributor Version;
3) for infringements caused by: i) third party modifications of
Contributor Version or ii) the combination of Modifications
made by that Contributor with other software (except as part
of the Contributor Version) or other devices; or 4) under Patent
Claims infringed by Covered Code in the absence of
Modifications made by that Contributor.
3.1. Application of License.
The Modifications which You create or to which You contribute
are governed by the terms of this License, including without
limitation Section 2.2. The Source Code version of Covered Code
may be distributed only under the terms of this License or a
future version of this License released under Section 6.1, and
You must include a copy of this License with every copy of the
Source Code You distribute. You may not offer or impose any
terms on any Source Code version that alters or restricts the
applicable version of this License or the recipients' rights
hereunder. However, You may include an additional document
offering the additional rights described in Section 3.5.
Any Modification which You create or to which You contribute
must be made available in Source Code form under the terms of
this License either on the same media as an Executable version
or via an accepted Electronic Distribution Mechanism to anyone
to whom you made an Executable version available; and if made
available via Electronic Distribution Mechanism, must remain
available for at least twelve (12) months after the date it initially
became available, or at least six (6) months after a subsequent
version of that particular Modification has been made available
to such recipients. You are responsible for ensuring that the
Source Code version remains available even if the Electronic
Distribution Mechanism is maintained by a third party.
3.3. Description of Modifications.
You must cause all Covered Code to which You contribute to
contain a file documenting the changes You made to create that
Covered Code and the date of any change. You must include a
prominent statement that the Modification is derived, directly
or indirectly, from Original Code provided by the Initial
Developer and including the name of the Initial Developer in (a)
the Source Code, and (b) in any notice in an Executable version
or related documentation in which You describe the origin or
ownership of the Covered Code.
3.4. Intellectual Property Matters
(a) Third Party Claims.
If Contributor has knowledge that a license under a third party's
intellectual property rights is required to exercise the rights
granted by such Contributor under Sections 2.1 or 2.2,
Contributor must include a text file with the Source Code
distribution titled ""LEGAL"" which describes the claim and the
party making the claim in sufficient detail that a recipient will
know whom to contact. If Contributor obtains such knowledge
after the Modification is made available as described in Section
3.2, Contributor shall promptly modify the LEGAL file in all
copies Contributor makes available thereafter and shall take
other steps (such as notifying appropriate mailing lists or
newsgroups) reasonably calculated to inform those who
received the Covered Code that new knowledge has been
obtained.
(b) Contributor APIs.
If Contributor's Modifications include an application
programming interface and Contributor has knowledge of
patent licenses which are reasonably necessary to implement
that API, Contributor must also include this information in the
LEGAL file.
(c) Representations.
Contributor represents that, except as disclosed pursuant to
Section 3.4(a) above, Contributor believes that Contributor's
Modifications are Contributor's original creation(s) and/or
Contributor has sufficient rights to grant the rights conveyed by
this License.
You must duplicate the notice in Exhibit A in each file of the
Source Code. If it is not possible to put such notice in a
particular Source Code file due to its structure, then You must
include such notice in a location (such as a relevant directory)
where a user would be likely to look for such a notice. If You
created one or more Modification(s) You may add your name as
a Contributor to the notice described in Exhibit A. You must
also duplicate this License in any documentation for the Source
Code where You describe recipients' rights or ownership rights
relating to Covered Code. You may choose to offer, and to
charge a fee for, warranty, support, indemnity or liability
obligations to one or more recipients of Covered Code.
However, You may do so only on Your own behalf, and not on
behalf of the Initial Developer or any Contributor. You must
make it absolutely clear than any such warranty, support,
indemnity or liability obligation is offered by You alone, and You
hereby agree to indemnify the Initial Developer and every
Contributor for any liability incurred by the Initial Developer or
such Contributor as a result of warranty, support, indemnity or
liability terms You offer.
You may distribute Covered Code in Executable form only if the
requirements of Section 3.1-3.5 have been met for that Covered
Code, and if You include a notice stating that the Source Code
version of the Covered Code is available under the terms of this
License, including a description of how and where You have
fulfilled the obligations of Section 3.2. The notice must be
conspicuously included in any notice in an Executable version,
related documentation or collateral in which You describe
recipients' rights relating to the Covered Code. You may
distribute the Executable version of Covered Code or ownership
rights under a license of Your choice, which may contain terms
different from this License, provided that You are in compliance
with the terms of this License and that the license for the
Executable version does not attempt to limit or alter the
recipient's rights in the Source Code version from the rights set
forth in this License. If You distribute the Executable version
under a different license You must make it absolutely clear that
any terms which differ from this License are offered by You
alone, not by the Initial Developer or any Contributor. You
hereby agree to indemnify the Initial Developer and every
Contributor for any liability incurred by the Initial Developer or
such Contributor as a result of any such terms You offer.
3.7. Larger Works.
You may create a Larger Work by combining Covered Code with
other code not governed 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 the Covered Code.
4. Inability to Comply Due to Statute or Regulation.
If it is impossible for You to comply with any of the terms of this
License with respect to some or all of the Covered Code due to
statute, judicial order, or regulation then You must: (a) comply
with the terms of this License to the maximum extent possible;
and (b) describe the limitations and the code they affect. Such
description must be included in the LEGAL file described in
Section 3.4 and must be included with all distributions of the
Source Code. Except to the extent prohibited by statute or
regulation, such description must be sufficiently detailed for a
recipient of ordinary skill to be able to understand it.
5. Application of this License.
This License applies to code to which the Initial Developer has
attached the notice in Exhibit A and to related Covered Code.
6.1. New Versions.
Netscape Communications Corporation (""Netscape"") may
publish revised and/or new versions of the License from time to
time. Each version will be given a distinguishing version number.
6.2. Effect of New Versions.
Once Covered Code has been published under a particular
version of the License, You may always continue to use it under
the terms of that version. You may also choose to use such
Covered Code under the terms of any subsequent version of the
License published by Netscape. No one other than Netscape has
the right to modify the terms applicable to Covered Code
created under this License.
6.3. Derivative Works.
If You create or use a modified version of this License (which
you may only do in order to apply it to code which is not already
Covered Code governed by this License), You must (a) rename
Your license so that the phrases ""Mozilla"", ""MOZILLAPL"",
""MOZPL"", ""Netscape"", ""MPL"", ""NPL"" or any confusingly
similar phrase do not appear in your license (except to note that
your license differs from this License) and (b) otherwise make it
clear that Your version of the license contains terms which
differ from the Mozilla Public License and Netscape Public
License. (Filling in the name of the Initial Developer, Original
Code or Contributor in the notice described in Exhibit A shall not
of themselves be deemed to be modifications of this License.)
COVERED CODE IS PROVIDED UNDER THIS LICENSE ON AN ""AS
IS"" BASIS, WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION,
WARRANTIES THAT THE COVERED CODE IS FREE OF DEFECTS,
MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR NONINFRINGING. THE ENTIRE RISK AS TO THE QUALITY AND
PERFORMANCE OF THE COVERED CODE IS WITH YOU. SHOULD
ANY COVERED CODE PROVE DEFECTIVE IN ANY RESPECT, YOU
(NOT THE INITIAL DEVELOPER OR ANY OTHER CONTRIBUTOR)
ASSUME THE COST OF ANY NECESSARY SERVICING, REPAIR OR
CORRECTION. THIS DISCLAIMER OF WARRANTY CONSTITUTES
AN ESSENTIAL PART OF THIS LICENSE. NO USE OF ANY COVERED
CODE IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS
DISCLAIMER.
8. TERMINATION.
terminate automatically if You fail to comply with terms herein
and fail to cure such breach within 30 days of becoming aware
of the breach. All sublicenses to the Covered Code which are
properly granted shall survive any termination of this License.
Provisions which, by their nature, must remain in effect beyond
the termination of this License shall survive.
8.2. If You initiate litigation by asserting a patent infringement
claim (excluding declatory judgment actions) against Initial
Developer or a Contributor (the Initial Developer or Contributor
against whom You file such action is referred to as
""Participant"") alleging that:
(a) such Participant's Contributor Version directly or indirectly
infringes any patent, then any and all rights granted by such
Participant to You under Sections 2.1 and/or 2.2 of this License
shall, upon 60 days notice from Participant terminate
prospectively, unless if within 60 days after receipt of notice
You either: (i) agree in writing to pay Participant a mutually
agreeable reasonable royalty for Your past and future use of
Modifications made by such Participant, or (ii) withdraw Your
litigation claim with respect to the Contributor Version against
such Participant. If within 60 days of notice, a reasonable
royalty and payment arrangement are not mutually agreed
upon in writing by the parties or the litigation claim is not
withdrawn, the rights granted by Participant to You under
Sections 2.1 and/or 2.2 automatically terminate at the
expiration of the 60 day notice period specified above.
(b) any software, hardware, or device, other than such
Participant's Contributor Version, directly or indirectly infringes
any patent, then any rights granted to You by such Participant
under Sections 2.1(b) and 2.2(b) are revoked effective as of the
date You first made, used, sold, distributed, or had made,
Modifications made by that Participant.
8.3. If You assert a patent infringement claim against
Participant alleging that such Participant's Contributor Version
directly or indirectly infringes any patent where such claim is
resolved (such as by license or settlement) prior to the initiation
of patent infringement litigation, then the reasonable value of
the licenses granted by such Participant under Sections 2.1 or
2.2 shall be taken into account in determining the amount or
value of any payment or license.
8.4. In the event of termination under Sections 8.1 or 8.2
above, all end user license agreements (excluding distributors
and resellers) which have been validly granted by You or any
distributor hereunder prior to termination shall survive
termination.
UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY,
WHETHER TORT (INCLUDING NEGLIGENCE), CONTRACT, OR
OTHERWISE, SHALL YOU, THE INITIAL DEVELOPER, ANY OTHER
CONTRIBUTOR, OR ANY DISTRIBUTOR OF COVERED CODE, OR
ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO ANY
PERSON FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR
CONSEQUENTIAL DAMAGES OF ANY CHARACTER INCLUDING,
WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL,
WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR
ANY AND ALL OTHER COMMERCIAL DAMAGES OR LOSSES, EVEN
IF SUCH PARTY SHALL HAVE BEEN INFORMED OF THE
POSSIBILITY OF SUCH DAMAGES. THIS LIMITATION OF LIABILITY
SHALL NOT APPLY TO LIABILITY FOR DEATH OR PERSONAL
INJURY RESULTING FROM SUCH PARTY'S NEGLIGENCE TO THE
EXTENT APPLICABLE LAW PROHIBITS SUCH LIMITATION. SOME
OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THIS
EXCLUSION AND LIMITATION MAY NOT APPLY TO YOU.
The Covered Code is a ""commercial item,"" as that term is
defined in 48 C.F.R. 2.101 (Oct. 1995), consisting of
""commercial computer software"" and ""commercial computer
software documentation,"" as such terms are used in 48 C.F.R.
12.212 (Sept. 1995). Consistent with 48 C.F.R. 12.212 and 48
C.F.R. 227.7202-1 through 227.7202-4 (June 1995), all U.S.
Government End Users acquire Covered Code with only those
rights set forth herein.
11. MISCELLANEOUS.
subject matter hereof. If any provision of this License is held to
be unenforceable, such provision shall be reformed only to the
extent necessary to make it enforceable. This License shall be
governed by California law provisions (except to the extent
applicable law, if any, provides otherwise), excluding its conflictof-law provisions. With respect to disputes in which at least one
party is a citizen of, or an entity chartered or registered to do
business in the United States of America, any litigation relating
to this License shall be subject to the jurisdiction of the Federal
Courts of the Northern District of California, with venue lying in
Santa Clara County, California, with the losing party responsible
for costs, including without limitation, court costs and
reasonable attorneys' fees and expenses. The application of the
United Nations Convention on Contracts for the International
Sale of Goods is expressly excluded. Any law or regulation which
provides that the language of a contract shall be construed
against the drafter shall not apply to this License.
As between Initial Developer and the Contributors, each party is
responsible for claims and damages arising, directly or
indirectly, out of its utilization of rights under this License and
You agree to work with Initial Developer and Contributors to
distribute such responsibility on an equitable basis. Nothing
herein is intended or shall be deemed to constitute any
admission of liability.
13. MULTIPLE-LICENSED CODE.
Initial Developer may designate portions of the Covered Code as
""Multiple-Licensed"". ""Multiple-Licensed"" means that the
Initial Developer permits you to utilize portions of the Covered
Code under Your choice of the NPL or the alternative licenses, if
any, specified by the Initial Developer in the file described in
Exhibit A.
EXHIBIT A -Mozilla Public License.
``The contents of this file are subject to the Mozilla Public
License Version 1.1 (the ""License""); you may not use this file
except in compliance with the License. Una copia della licenza è
disponibile all'indirizzo
http://www.mozilla.org/MPL/
Software distributed under the License is distributed on an ""AS
IS"" basis, WITHOUT WARRANTY OF
ANY KIND, either express or implied. See the License for the
specific language governing rights and
limitations under the License.
The Original Code is
______________________________________.
The Initial Developer of the Original Code is
________________________. Portions created by
Open Message Queue 4.1
______________________ are Copyright (C) ______
_______________________. All Rights
Reserved.
Contributor(s): ______________________________________.
Alternatively, the contents of this file may be used under the
terms of the _____ license (the ""[___] License""), in which
case the provisions of [______] License are applicable instead
of those above. If you wish to allow use of your version of this
file only under the terms of the [____] License and not to allow
others to use your version of this file under the MPL, indicate
your decision by deleting the provisions above and replace
them with the notice and other provisions required by the [___]
License. If you do not delete the provisions above, a recipient
may use your version of this file under either the MPL or the
[___] License.""
NOTE: The text of this Exhibit A may differ slightly from the text
of the notices in the Source Code files of the Original Code. You
should use the text of this Exhibit A rather than the text found
in the Original Code Source Code for Your Modifications.]
For the above software the following terms and conditions shall
apply:
This product contains certain files (the ?CDDL Files?) which are
governed by the Common Development and Distribution
License, Version 1.0. The source code for the CDDL Files may be
found here: http://opensrcd.ca.com.
This Product is distributed with Oracle 11G JDBC Driver version
11.1.0.6.0 from Oracle USA, Inc. (&||&Oracle&||&)
The following additional terms and conditions apply to your use
of the Oracle software product (&||&Oracle Product&||&):
(1) you may only use the Oracle Product to run the CA Product;
(2) to the extent permitted by applicable law, Oracle disclaims
liability for any damages, whether direct, indirect, incidental, or
consequential, arising from your use of the Oracle Product; (3)
at the termination of this Agreement, you must discontinue use
and destroy or return to CA all copies of the Product; (4) Oracle
is not obligated to provide technical support, phone support, or
updates to the Oracle Product hereunder; (5) CA reserves the
right to audit your use of the Oracle Product and report such
use to Oracle or to assign this right to audit your use of the
Oracle Product to Oracle; (6) Oracle shall be a third party
beneficiary of this Agreement.
Saxon 8.53
Questo prodotto include Saxon 8.53. La versione del codice
sorgente di Saxon 8.6 viene fornita con una licenza pubblica
Mozilla, versione 1.1.
"The complete license (copyright notice, list of conditions, and
disclaimer) must be displayed in an Acknowledgments section in
the product user doc in accordance with the Third-Party legal
information section of CAWrite. Please precede the agreement
with |&&|Portions of this product include software developed
by the DOM4J Project (http://dom4j.org/) and is distributed in
accordance with the following license agreement.|&&|
Redistribution and use of this software and associated
documentation (""Software""), with or without modification,
Redistributions of source code must retain copyright statements
and notices. Redistributions must also contain a copy of this
document.
Redistributions in binary form must reproduce the above
disclaimer in the documentation and/or other materials
provided with the distribution.
The name ""DOM4J"" must not be used to endorse or promote
products derived from this Software without prior written
permission of MetaStuff, Ltd. For written permission, please
contact dom4j-info@metastuff.com.
Products derived from this Software may not be called
""DOM4J"" nor may ""DOM4J"" appear in their names without
prior written permission of MetaStuff, Ltd. DOM4J is a
registered trademark of MetaStuff, Ltd.
Due credit should be given to the DOM4J Project http://www.dom4j.org
THIS SOFTWARE IS PROVIDED BY METASTUFF, LTD. AND
CONTRIBUTORS ""AS IS"" AND ANY EXPRESSED OR IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
METASTUFF, LTD. OR ITS CONTRIBUTORS BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
Copyright 2001-2005 (C) MetaStuff, Ltd. All Rights Reserved.
SourceForge ANT-CONTRIB v.1.0b3
ANT-CONTRIB v.1,0b3
This product includes software developed by the Ant-Contrib
project (http://sourceforge.net/projects/ant-contrib). It was
obtained under the following terms:
/*
* The Apache Software License, Version 1.1
*
* Copyright (c) 2001-2003 Ant-Contrib project. All rights
reserved.
*
without
conditions
* are met:
*
copyright
*
copyright
the
* distribution.
*
redistribution, if
* any, must include the following acknowlegement:
*
""This product includes software developed by the
*
Ant-Contrib project (http://sourceforge.net/projects/antcontrib).""
* Alternately, this acknowlegement may appear in the
software itself,
* if and wherever such third-party acknowlegements normally
appear.
*
* 4. The name Ant-Contrib must not be used to endorse or
promote products
* derived from this software without prior written
permission. For
* written permission, please contact
* ant-contrib-developers@lists.sourceforge.net.
*
""Ant-Contrib""
* nor may ""Ant-Contrib"" appear in their names without
prior written
* permission of the Ant-Contrib project.
*
* THIS SOFTWARE IS PROVIDED `ÀS IS|&""&| AND ANY
EXPRESSED OR IMPLIED
IMPLIED WARRANTIES
PURPOSE ARE
* DISCLAIMED. IN NO EVENT SHALL THE ANT-CONTRIB
PROJECT OR ITS
* CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
INCIDENTAL,
(INCLUDING, BUT NOT
SERVICES; LOSS OF
HOWEVER CAUSED AND
STRICT LIABILITY,
IN ANY WAY OUT
POSSIBILITY OF
* SUCH DAMAGE.
*
====================================================
================
*/
Sun JRE 1.6.0_14
Sun JRE 1.6.0_14
This Product is distributed with Sun JRE 1.6.0-14-bo8 (JAVA SE
RUNTIME ENVIRONMENT (JRE), VERSION 6) (Sun JRE). The Sun
JRE is distributed in accordance with the Sun Microsystems, Inc.
(Sun) Binary Code License Agreement set forth below. As noted
in Section E of the Supplemental License Terms of this license,
Sun has provided additional copyright notices and license terms
that may be applicable to portions of the Sun JRE in the
THIRDPARTYLICENSEREADME.txt file that accompanies the Sun
JRE.
Sun Microsystems, Inc. Binary Code License Agreement
for the JAVA SE RUNTIME ENVIRONMENT (JRE) VERSION 6 and
JAVAFX RUNTIME VERSION 1
SUN MICROSYSTEMS, INC. (""SUN"") IS WILLING TO LICENSE
THE
SOFTWARE IDENTIFIED BELOW TO YOU ONLY UPON THE
CONDITION
THAT YOU ACCEPT ALL OF THE TERMS CONTAINED IN THIS
BINARY
CODE LICENSE AGREEMENT AND SUPPLEMENTAL LICENSE
TERMS
(COLLECTIVELY ""AGREEMENT""). PLEASE READ THE
AGREEMENT
CAREFULLY. BY DOWNLOADING OR INSTALLING THIS
SOFTWARE, YOU
ACCEPT THE TERMS OF THE AGREEMENT. INDICATE
ACCEPTANCE BY
Sun JRE 1.6.0_14
SELECTING THE ""ACCEPT"" BUTTON AT THE BOTTOM OF THE
AGREEMENT. IF YOU ARE NOT WILLING TO BE BOUND BY ALL
THE
TERMS, SELECT THE ""DECLINE"" BUTTON AT THE BOTTOM OF
THE
AGREEMENT AND THE DOWNLOAD OR INSTALL PROCESS WILL
NOT
CONTINUE.
1. DEFINITIONS. ""Software"" means the identified above in
binary form, any other machine readable materials
(including, but not limited to, libraries, source files,
header files, and data files), any updates or error
corrections provided by Sun, and any user manuals,
programming guides and other documentation provided to you
by Sun under this Agreement. ""General Purpose Desktop
Computers and Servers"" means computers, including desktop
and laptop computers, or servers, used for general
computing functions under end user control (such as but not
specifically limited to email, general purpose Internet
browsing, and office suite productivity tools). The use of
Software in systems and solutions that provide dedicated
functionality (other than as mentioned above) or designed
Sun JRE 1.6.0_14
for use in embedded or function-specific software
applications, for example but not limited to: Software
embedded in or bundled with industrial control systems,
wireless mobile telephones, wireless handheld devices,
netbooks, kiosks, TV/STB, Blu-ray Disc devices, telematics
and network control switching equipment, printers and
storage management systems, and other related systems are
excluded from this definition and not licensed under this
Agreement. ""Programs"" means (a) Java technology applets
and
applications intended to run on the Java Platform Standard
Edition (Java SE) platform on Java-enabled General Purpose
Desktop Computers and Servers, and (b) JavaFX technology
applications intended to run on the JavaFX Runtime on
JavaFX-enabled General Purpose Desktop Computers and
Servers.
2. LICENSE TO USE. Subject to the terms and conditions of
this Agreement, including, but not limited to the Java
Technology Restrictions of the Supplemental License Terms,
Sun grants you a non-exclusive, non-transferable, limited
license without license fees to reproduce and use internally
Sun JRE 1.6.0_14
Software complete and unmodified for the sole purpose of
running Programs. Additional licenses for developers and/or
publishers are granted in the Supplemental License Terms.
3. RESTRICTIONS. Software is confidential and copyrighted.
Title to Software and all associated intellectual property
rights is retained by Sun and/or its licensors. Unless
enforcement is prohibited by applicable law, you may not
modify, decompile, or reverse engineer Software. You
acknowledge that Licensed Software is not designed or
intended for use in the design, construction, operation or
maintenance of any nuclear facility. Sun Microsystems, Inc.
disclaims any express or implied warranty of fitness for
such uses. No right, title or interest in or to any
trademark, service mark, logo or trade name of Sun or its
licensors is granted under this Agreement. Additional
restrictions for developers and/or publishers licenses are
set forth in the Supplemental License Terms.
4. LIMITED WARRANTY. Sun warrants to you that for a period
of ninety (90) days from the date of purchase, as evidenced
by a copy of the receipt, the media on which Software is
Sun JRE 1.6.0_14
furnished (if any) will be free of defects in materials and
workmanship under normal use. Except for the foregoing,
Software is provided ""AS IS"". Your exclusive remedy and
Sun's entire liability under this limited warranty will be
at Sun's option to replace Software media or refund the fee
paid for Software. Any implied warranties on the Software
are limited to 90 days. Some states do not allow
limitations on duration of an implied warranty, so the above
may not apply to you. This limited warranty gives you
specific legal rights. You may have others, which vary from
state to state.
5. DISCLAIMER OF WARRANTY. UNLESS SPECIFIED IN THIS
AGREEMENT, ALL EXPRESS OR IMPLIED CONDITIONS,
REPRESENTATIONS AND WARRANTIES, INCLUDING ANY
IMPLIED
WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE OR NON-INFRINGEMENT ARE DISCLAIMED, EXCEPT TO
THE
EXTENT THAT THESE DISCLAIMERS ARE HELD TO BE LEGALLY
INVALID.
6. LIMITATION OF LIABILITY. TO THE EXTENT NOT PROHIBITED
Sun JRE 1.6.0_14
BY LAW, IN NO EVENT WILL SUN OR ITS LICENSORS BE LIABLE
FOR
ANY LOST REVENUE, PROFIT OR DATA, OR FOR SPECIAL,
INDIRECT,
CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES,
HOWEVER
CAUSED REGARDLESS OF THE THEORY OF LIABILITY, ARISING
OUT OF
OR RELATED TO THE USE OF OR INABILITY TO USE SOFTWARE,
EVEN
IF SUN HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
DAMAGES.
In no event will Sun's liability to you, whether in
contract, tort (including negligence), or otherwise, exceed
the amount paid by you for Software under this Agreement.
The foregoing limitations will apply even if the above
stated warranty fails of its essential purpose. Some states
do not allow the exclusion of incidental or consequential
damages, so some of the terms above may not be applicable to
you.
7. TERMINATION. This Agreement is effective until
terminated. You may terminate this Agreement at any time by
destroying all copies of Software. This Agreement will
Sun JRE 1.6.0_14
terminate immediately without notice from Sun if you fail to
comply with any provision of this Agreement. Either party
may terminate this Agreement immediately should any
Software
become, or in either party's opinion be likely to become,
the subject of a claim of infringement of any intellectual
property right. Upon Termination, you must destroy all
copies of Software.
8. EXPORT REGULATIONS. All Software and technical data
delivered under this Agreement are subject to US export
control laws and may be subject to export or import
regulations in other countries. You agree to comply
strictly with all such laws and regulations and acknowledge
that you have the responsibility to obtain such licenses to
export, re-export, or import as may be required after
delivery to you.
9. TRADEMARKS AND LOGOS. You acknowledge and agree as
between you and Sun that Sun owns the SUN, SOLARIS, JAVA,
JINI, FORTE, and iPLANET trademarks and all SUN, SOLARIS,
JAVA, JINI, FORTE, and iPLANET-related trademarks, service
marks, logos and other brand designations (""Sun Marks""), and
Sun JRE 1.6.0_14
you agree to comply with the Sun Trademark and Logo Usage
Requirements currently located at
http://www.sun.com/policies/trademarks. Any use you make
of
the Sun Marks inures to Sun's benefit.
10. U.S. GOVERNMENT RESTRICTED RIGHTS. If Software is
being acquired by or on behalf of the U.S. Government or by
a U.S. Government prime contractor or subcontractor (at any
tier), then the Government's rights in Software and
accompanying documentation will be only as set forth in this
Agreement; this is in accordance with 48 CFR 227.7201
through 227.7202-4 (for Department of Defense (DOD)
acquisitions) and with 48 CFR 2.101 and 12.212 (for non-DOD
acquisitions).
11. GOVERNING LAW. Any action related to this Agreement
will be governed by California law and controlling U.S.
federal law. No choice of law rules of any jurisdiction
will apply.
12. SEVERABILITY. If any provision of this Agreement is
held to be unenforceable, this Agreement will remain in
effect with the provision omitted, unless omission would
Sun JRE 1.6.0_14
frustrate the intent of the parties, in which case this
Agreement will immediately terminate.
13. INTEGRATION. This Agreement is the entire agreement
between you and Sun relating to its subject matter. It
supersedes all prior or contemporaneous oral or written
communications, proposals, representations and warranties
and prevails over any conflicting or additional terms of any
quote, order, acknowledgment, or other communication
between
the parties relating to its subject matter during the term
of this Agreement. No modification of this Agreement will
be binding, unless in writing and signed by an authorized
representative of each party.
SUPPLEMENTAL LICENSE TERMS
These Supplemental License Terms add to or modify the terms
of the Binary Code License Agreement. Capitalized terms not
defined in these Supplemental Terms shall have the same
meanings ascribed to them in the Binary Code License
Agreement . These Supplemental Terms shall supersede any
inconsistent or conflicting terms in the Binary Code License
Sun JRE 1.6.0_14
Agreement, or in any license contained within the Software.
A. Software Internal Use and Development License Grant.
Subject to the terms and conditions of this Agreement and
restrictions and exceptions set forth in the Software
""README"" file incorporated herein by reference, including,
but not limited to the Java Technology Restrictions of these
Supplemental Terms, Sun grants you a non-exclusive,
non-transferable, limited license without fees to reproduce
internally and use internally the Software complete and
unmodified for the purpose of designing, developing, and
testing your Programs.
B. License to Distribute Software. Subject to the terms
and conditions of this Agreement and restrictions and
exceptions set forth in the Software README file, including,
but not limited to the Java Technology Restrictions of these
Supplemental Terms, Sun grants you a non-exclusive,
non-transferable, limited license without fees to reproduce
and distribute the Software (except for the JavaFX Runtime),
provided that (i) you distribute the Software complete and
unmodified and only bundled as part of, and for the sole
Sun JRE 1.6.0_14
purpose of running, your Programs, (ii) the Programs add
significant and primary functionality to the Software, (iii)
you do not distribute additional software intended to
replace any component(s) of the Software, (iv) you do not
remove or alter any proprietary legends or notices contained
in the Software, (v) you only distribute the Software
subject to a license agreement that protects Sun's interests
consistent with the terms contained in this Agreement, and
(vi) you agree to defend and indemnify Sun and its licensors
from and against any damages, costs, liabilities, settlement
amounts and/or expenses (including attorneys' fees) incurred
in connection with any claim, lawsuit or action by any third
party that arises or results from the use or distribution of
any and all Programs and/or Software.
C. Java Technology Restrictions. You may not create,
modify, or change the behavior of, or authorize your
licensees to create, modify, or change the behavior of,
classes, interfaces, or subpackages that are in any way
identified as ""java"", ""javax"", ""sun"" or similar convention
as specified by Sun in any naming convention designation.
Sun JRE 1.6.0_14
D. Source Code. Software may contain source code that,
unless expressly licensed for other purposes, is provided
solely for reference purposes pursuant to the terms of this
Agreement. Source code may not be redistributed unless
expressly provided for in this Agreement.
E. Third Party Code. Additional copyright notices and
license terms applicable to portions of the Software are set
forth in the THIRDPARTYLICENSEREADME.txt file. In addition
to any terms and conditions of any third party
opensource/freeware license identified in the
THIRDPARTYLICENSEREADME.txt file, the disclaimer of warranty
and limitation of liability provisions in paragraphs 5 and 6
of the Binary Code License Agreement shall apply to all
Software in this distribution.
F. Termination for Infringement. Either party may
terminate this Agreement immediately should any Software
become, or in either party's opinion be likely to become,
the subject of a claim of infringement of any intellectual
property right.
G. Installation and Auto-Update. The Software's
Sun JRE 1.6.0_14
installation and auto-update processes transmit a limited
amount of data to Sun (or its service provider) about those
specific processes to help Sun understand and optimize them.
Sun does not associate the data with personally identifiable
information. You can find more information about the data
Sun collects at http://java.com/data/.
For inquiries please contact: Sun Microsystems, Inc., 4150
Network Circle, Santa Clara, California 95054, U.S.A.
Unzip 5.42
Unzip 5.42
This product includes Unzip 5.42 software distributed pursuant
to the following terms:
Copyright (c) 1990-2001 Info-ZIP. All rights reserved.
For the purposes of this copyright and license, "Info-ZIP" is
defined as
the following set of individuals:
Mark Adler, John Bush, Karl Davis, Harald Denker, Jean-Michel
Dubois,
Jean-loup Gailly, Hunter Goatley, Ian Gorman, Chris Herborth,
Dirk Haase,
Greg Hartwig, Robert Heath, Jonathan Hudson, Paul Kienitz,
David Kirschbaum,
Johnny Lee, Onno van der Linden, Igor Mandrichenko, Steve P.
Miller,
Sergio Monesi, Keith Owens, George Petrov, Greg Roelofs, Kai
Uwe Rommel,
Steve Salisbury, Dave Smith, Christian Spieler, Antoine
Verheijen,
Paul von Behren, Rich Wales, Mike White
This software is provided "as is," without warranty of any kind,
express
or implied. In no event shall Info-ZIP or its contributors be held
liable
Unzip 5.42
for any direct, indirect, incidental, special or consequential
damages
arising out of the use of or inability to use this software.
purpose,
including commercial applications, and to alter it and
redistribute it
freely, subject to the following restrictions:
copyright notice,
definition, disclaimer, and this list of conditions.
2. Redistributions in binary form must reproduce the above
copyright
notice, definition, disclaimer, and this list of conditions in
documentation and/or other materials provided with the
distribution.
3. Altered versions--including, but not limited to, ports to new
operating
systems, existing ports with new graphical interfaces, and
dynamic,
shared, or static library versions--must be plainly marked as
such
and must not be misrepresented as being the original
source. Such
Unzip 5.42
altered versions also must not be misrepresented as being
Info-ZIP
releases--including, but not limited to, labeling of the
altered
versions with the names "Info-ZIP" (or any variation thereof,
including,
but not limited to, different capitalizations), "Pocket UnZip,"
"WiZ"
or "MacZip" without the explicit permission of Info-ZIP.
Such altered
versions are further prohibited from misrepresentative use
of the
Zip-Bugs or Info-ZIP e-mail addresses or of the Info-ZIP
URL(s).
4. Info-ZIP retains the right to use the names "Info-ZIP," "Zip,"
"UnZip,"
"WiZ," "Pocket UnZip," "Pocket Zip," and "MacZip" for its
own source and
binary releases.

CA Unicenter Service Catalog - Note di rilascio

Transcription

Similar documents

Topolinux 11 - Vecchiomago

DBH1450 - The Warburg Institute

Turbo NAS hardware manual

warta kerajaan persekutuan federal government gazette

AKTA MAKANAN 1983

ZAF-2012-0014 r PDF

memorandum saling pengertian antara direktorat jenderal

Peraturan Perumahan Jentayu Residensi

PFM_Hurricane_06-2010_ita_eng 1.68 Mb

WARTA KERAJAAN PERSEKUTUAN

Catalogo generale AGV_09 copia.indd

Business Name Business Classification Code

Conveyor_Components

Basic Terms only (Giveways, SMS, MMS contests) - (Ver Nov

Diapositiva 1 - Università Bocconi

Business Name Business Classification Code

Constitution of Brunei Darussalam

DJ Song List by Artist - Southeastern Entertainment

Warta Kerajaan - Tobacco Control Laws