This document provides instructions for getting started with JBoss ESB, including downloading and installing JBoss ESB, deploying it to the JBoss Application Server or JBoss ESB Server, and running a "Hello World" quickstart example to validate the installation. Key steps include downloading JBoss ESB and either the JBoss Application Server or JBoss ESB Server, configuring deployment properties, deploying JBoss ESB archives using Ant, and running the quickstart to test the integration.
MySQL Workbench is a visual tool for database design, creation, modeling, and administration. It allows users to design and create databases visually using EER diagrams or through a schema navigator. The tool also supports importing and exporting SQL scripts, creating tables and foreign key relationships, and documenting databases through generated diagrams and reports. MySQL Workbench is available in both open source and commercial editions.
This document provides a step-by-step guide for deploying IBM Tivoli Monitoring 6.1 in small to large environments. It discusses planning the installation, defining the architecture, creating deployment plans, installing the various Tivoli Monitoring components, and configuring the system. The guide also covers demonstrations of a single machine proof of concept installation and a small installation using DB2 Workgroup Edition.
eRoom 7 Installation,Upgrade, and Configuration Guidemaddinapudi
This document is an installation, upgrade, and configuration guide for eRoom 7. It contains information about installing and upgrading eRoom 7, system requirements, default permissions, security guidelines, and troubleshooting. The guide has multiple chapters that cover topics such as pre-installation requirements, the installation process, integrating eRoom with other applications like mail servers and content servers, and setting up eRoom in clustered environments.
Suse service virtualization_image_set up_guide_140214Darrel Rader
This document provides instructions for using a sample virtual environment for testing IBM Rational Service Testing and Virtualization products. The environment includes:
- SUSE Linux operating system
- IBM WebSphere MQ, WebSphere Application Server, and DB2
- Apache Tomcat
- Rational Integration Tester and Test Control Panel
It describes how to start and stop the included services like Tomcat and WebSphere Application Server. It also explains that the user needs to install libstatgrab and a SQLite JDBC driver for full functionality. The environment models a vacation booking system with flows for flight search, hotel booking, and flight confirmation that involve the various components.
This document provides best practices for upgrading VMware vSphere and ESXi hypervisor components to version 5.0. It covers upgrading vCenter Server from versions 4.0 and 4.1 to 5.0, including scenarios for local and remote databases. It also covers upgrading ESXi hosts from earlier versions to 5.0, either using VMware Update Manager for a non-disruptive upgrade or the ESXi installer. Requirements, recommendations, and step-by-step instructions are provided for each upgrade scenario.
This document provides best practices for upgrading VMware vSphere and ESXi hypervisor components to version 5.0. It covers upgrading vCenter Server from versions 4.0 and 4.1 to 5.0, including scenarios for local and remote databases. It also covers upgrading ESXi hosts from earlier versions to 5.0, either using VMware Update Manager for a non-disruptive upgrade or the ESXi installer. Requirements, recommendations, and step-by-step instructions are provided for each upgrade scenario.
This document provides step-by-step instructions for setting up and configuring IBM Tivoli Access Manager for Enterprise Single Sign-On 8.1 on both a single Windows server and in a clustered environment. It covers installing and configuring required components like the database, WebSphere Application Server, IBM HTTP Server, and the IMS Server. The document also discusses applying fix packs, configuring the IMS Server, and installing additional components like AccessAgent and AccessStudio.
This document provides instructions for installing Plesk on Linux, FreeBSD, and Mac OS systems. The key steps are:
1. Download the Auto-installer utility for the desired OS from the Plesk website.
2. Run the Auto-installer, specifying whether to install from a local file, official update server, or other site.
3. The Auto-installer will then guide the user through the remainder of the installation process.
Prior to installing Plesk on FreeBSD, the 'kern_securelevel_enable="NO"' entry must be added to /etc/rc.conf and the server restarted. Instructions are provided for a single server installation; multi-server
MySQL Workbench is a visual tool for database design, creation, modeling, and administration. It allows users to design and create databases visually using EER diagrams or through a schema navigator. The tool also supports importing and exporting SQL scripts, creating tables and foreign key relationships, and documenting databases through generated diagrams and reports. MySQL Workbench is available in both open source and commercial editions.
This document provides a step-by-step guide for deploying IBM Tivoli Monitoring 6.1 in small to large environments. It discusses planning the installation, defining the architecture, creating deployment plans, installing the various Tivoli Monitoring components, and configuring the system. The guide also covers demonstrations of a single machine proof of concept installation and a small installation using DB2 Workgroup Edition.
eRoom 7 Installation,Upgrade, and Configuration Guidemaddinapudi
This document is an installation, upgrade, and configuration guide for eRoom 7. It contains information about installing and upgrading eRoom 7, system requirements, default permissions, security guidelines, and troubleshooting. The guide has multiple chapters that cover topics such as pre-installation requirements, the installation process, integrating eRoom with other applications like mail servers and content servers, and setting up eRoom in clustered environments.
Suse service virtualization_image_set up_guide_140214Darrel Rader
This document provides instructions for using a sample virtual environment for testing IBM Rational Service Testing and Virtualization products. The environment includes:
- SUSE Linux operating system
- IBM WebSphere MQ, WebSphere Application Server, and DB2
- Apache Tomcat
- Rational Integration Tester and Test Control Panel
It describes how to start and stop the included services like Tomcat and WebSphere Application Server. It also explains that the user needs to install libstatgrab and a SQLite JDBC driver for full functionality. The environment models a vacation booking system with flows for flight search, hotel booking, and flight confirmation that involve the various components.
This document provides best practices for upgrading VMware vSphere and ESXi hypervisor components to version 5.0. It covers upgrading vCenter Server from versions 4.0 and 4.1 to 5.0, including scenarios for local and remote databases. It also covers upgrading ESXi hosts from earlier versions to 5.0, either using VMware Update Manager for a non-disruptive upgrade or the ESXi installer. Requirements, recommendations, and step-by-step instructions are provided for each upgrade scenario.
This document provides best practices for upgrading VMware vSphere and ESXi hypervisor components to version 5.0. It covers upgrading vCenter Server from versions 4.0 and 4.1 to 5.0, including scenarios for local and remote databases. It also covers upgrading ESXi hosts from earlier versions to 5.0, either using VMware Update Manager for a non-disruptive upgrade or the ESXi installer. Requirements, recommendations, and step-by-step instructions are provided for each upgrade scenario.
This document provides step-by-step instructions for setting up and configuring IBM Tivoli Access Manager for Enterprise Single Sign-On 8.1 on both a single Windows server and in a clustered environment. It covers installing and configuring required components like the database, WebSphere Application Server, IBM HTTP Server, and the IMS Server. The document also discusses applying fix packs, configuring the IMS Server, and installing additional components like AccessAgent and AccessStudio.
This document provides instructions for installing Plesk on Linux, FreeBSD, and Mac OS systems. The key steps are:
1. Download the Auto-installer utility for the desired OS from the Plesk website.
2. Run the Auto-installer, specifying whether to install from a local file, official update server, or other site.
3. The Auto-installer will then guide the user through the remainder of the installation process.
Prior to installing Plesk on FreeBSD, the 'kern_securelevel_enable="NO"' entry must be added to /etc/rc.conf and the server restarted. Instructions are provided for a single server installation; multi-server
This document is the user manual for sqlmap, an open source tool for detecting and exploiting SQL injection vulnerabilities. It details sqlmap's requirements, typical usage scenario, and supported features for fingerprinting databases, enumerating data, reading/writing files, executing commands, and establishing connections. The tool can detect SQL injections, fingerprint database systems, retrieve user information, dump database tables, run custom SQL statements, access the file system and operating system, and more.
This document provides an overview of performance best practices for VMware vSphere 5.0. It covers selecting hardware, configuring ESXi, optimizing guest operating systems, and managing virtual infrastructure. Specific topics include validating hardware compatibility, using CPUs with hardware virtualization features, selecting storage and networking hardware, configuring ESXi settings for power management and memory, and tips for VMware vCenter, vMotion, and other management tools.
This document discusses memory management in VMware ESX Server. It provides an overview of ESX memory management concepts including terminology, memory virtualization basics, and memory management in ESX. It then describes techniques for memory reclamation in ESX such as transparent page sharing, ballooning, and hypervisor swapping. It evaluates the performance of these techniques and provides best practices for host and guest memory usage.
This document provides an overview and guide for implementing and tuning open source applications on IBM PowerLinux systems using virtualization. It introduces common open source applications for web, mail, file, print and network serving. It then describes considerations for installing the Virtual I/O Server (VIOS), creating virtual servers, installing Linux and applications. The guide also covers monitoring with Ganglia and performance tuning. It is intended to help professionals plan and deploy open source solutions on IBM PowerLinux infrastructure.
JBoss AS 7 : Déployer sur terre et dans les nuagesAlexis Hassler
This document discusses the deployment of JBoss Application Server on both physical and cloud infrastructures. It provides an overview of the history and major versions of JBoss AS. It describes improvements in startup time, configuration, modularization, and deployment between versions 4.0 through 7.1. It also covers administration using the CLI and console, as well as deployment in PaaS environments like OpenShift and CloudBees.
Plesk 8.2 for Windows Domain Administrator's Guidewebhostingguy
To log in to Plesk, open the URL provided by your provider in a web browser and enter your login credentials. The standard view interface has a navigation pane on the left and main screen on the right, while the desktop view consolidates tools, statistics, and favorites. Familiarize yourself with search, sorting, and customization options to efficiently manage your website and email through Plesk.
The document provides instructions for installing Ubuntu Server Edition. It discusses preparing for installation by checking system requirements and backing up data. It then describes the installation process, which involves booting from the installation media, selecting options like keyboard layout and network configuration, partitioning disks, setting up users, and optionally installing package tasks like a mail server, web server, or database. The installation process is menu-driven and console-based for the server edition.
This document provides an overview and instructions for integrating IBM DB2 databases with the IBM System Storage N series. It discusses requirements, configuration, creating new databases, and migrating existing databases to the N series storage system. The document is intended to help users optimize DB2 database performance, backup and recovery, high availability, reliability, and storage requirements when using IBM N series storage.
The Ubuntu Server Guide provides step-by-step instructions for installing and configuring server applications on Ubuntu, covering topics like installation, package management, networking, security, monitoring, web servers, databases, file servers, email services, and more; it is intended as a task-oriented guide for system administrators to customize their Ubuntu server setup.
VM Explorer® is a simple but powerful software to back up, replicate and restore your VMware ESX, ESXi and Microsoft Hyper-V Virtual Machines (VM).
The following documentation explains the main tasks required for configuration and daily use of VM Explorer®. All services hereinafter are brought to you by HPE.
The HPE services and materials presented for VM Explorer® hereinafter are protected by copyright, trademark, trade dress, unfair competition, and other intellectual property rights. The trademarks, logos and marks of HPE and VM Explorer® displayed on the services and products are the property of HPE or third parties. You are not permitted to use the Marks without the prior consent of HPE or the third party that may own the Marks.
This document provides a proof of concept guide for evaluating VMware's Virtual SAN (VSAN) storage technology. It outlines the requirements, setup instructions, and test workflows to complete a full evaluation. The guide walks through configuring a VSAN cluster, creating VM storage policies, deploying VMs, testing availability and troubleshooting tools. Completing the steps will give customers hands-on experience with VSAN's full capabilities.
The document provides information about using the Symantec Backup Exec Command Line Applet, including:
- Required command line switches to perform Backup Exec functions like running backup jobs.
- Supported operations like backup, restore, managing media, and getting job status.
- Creating job scripts to automate backup jobs using command line switches.
- Targeting remote Backup Exec servers and logging in with credentials.
This document provides an overview of FreeNAS 8.3.0, including its core features, ZFS and RAID concepts, hardware considerations, and what's new in version 8.3.0. It covers topics such as installing FreeNAS, using the graphical interface, upgrading, configuring volumes and shares, managing ZFS features like snapshots and replication, installing plugins using the Plugins Jail, and installing additional software. The document contains information to help users perform essential FreeNAS system administration tasks.
This document provides instructions for installing Ubuntu Server Edition, including:
- Recommended system requirements for a server installation
- Differences between the server and desktop editions
- Backing up data before installation
- Running the installation from a CD which uses a console-based process to set up networking, configure the system hostname and time zone, partition the disk, set up a new user, and choose automatic update options
- Optional tasks like DNS, LAMP, mail, and file servers that can be selected to install additional related packages
This document provides instructions for advanced configuration of Autodesk data management server 2009/2010, including:
1. Customizing the installation location and SQL credentials.
2. Installing with other web applications that require a different .NET version by configuring a separate application pool.
3. Configuring the server for a remote SQL database, backups, vault connections, logging, and replication between servers.
Anoop Singh introduces himself and his background. He currently lives and works in India. Previously he worked for two other companies and has strengths in taking initiative, multitasking, and using technology for productivity. He provides his email address and LinkedIn profile for contact and expresses interest in working together with organizations to help achieve goals and objectives.
O.I.M. (Only Indy Music) is a proposed retail store that will give independent artists a place to sell their CDs and merchandise directly to fans. It will be the first major store specifically targeting independent artists. The store aims to provide artists opportunities for in-store distribution and performances to help them gain more control over their music careers.
This document provides instructions for getting started with JBoss ESB, including downloading and installing JBoss ESB, deploying it to the JBoss Application Server or JBoss ESB Server, and running a "Hello World" quickstart example to validate the installation. Key steps include downloading JBoss ESB and either the JBoss Application Server or JBoss ESB Server, configuring deployment properties, deploying JBoss ESB archives using Ant, and starting the server.
This document outlines the steps taken to create a double page spread for an A3 background. It lists adding the artist's name, stand first, images, a pull quote, columns of text, and page numbers as the key elements included in the production of the double page spread.
DHall Events is an Arkansas-based events company that offers services in central and northwest Arkansas. The company name comes from the owner's name to distinguish it from competitors. While others offer similar services, the owner aims to provide consistently high quality. The logo incorporates the owner's signature to represent something unique that cannot be replicated. It aims to attract accomplished young urban professionals seeking quality entertainment. The tagline "Signature Upscale Events" communicates the type of high-end events and signature touch provided.
Ringkasan dokumen tersebut adalah:
1) Dokumen tersebut membahas profil SMK Negeri 1 Rawajitu Selatan sebagai sekolah pangkal dalam kegiatan on the job learning calon pengawas sekolah.
2) SMK tersebut memiliki 5 program keahlian dan 19 rombel dengan total siswa 485 orang yang diampu 39 orang guru.
3) Calon pengawas melakukan supervisi manajerial dan akademik di sekolah tersebut sebagai bagian dari
Retailing Dictionary A To Z Retail BusinessAnoopsinghMba
This document provides definitions for over 100 common retail business terms starting with A through G. Some of the key terms defined include:
- Anchor store: A major store used to drive customers to smaller retailers in a shopping center.
- Brand: A name, symbol or mark associated with a seller's goods/services that distinguishes them from competitors.
- Brick and mortar: Refers to physical retail stores located in a building rather than online.
- Category killer store: A large specialty store with an enormous selection in its product category and low prices that draws customers from a wide area.
- Department store: A large retail unit organized into departments selling a wide variety of goods and services
This document is the user manual for sqlmap, an open source tool for detecting and exploiting SQL injection vulnerabilities. It details sqlmap's requirements, typical usage scenario, and supported features for fingerprinting databases, enumerating data, reading/writing files, executing commands, and establishing connections. The tool can detect SQL injections, fingerprint database systems, retrieve user information, dump database tables, run custom SQL statements, access the file system and operating system, and more.
This document provides an overview of performance best practices for VMware vSphere 5.0. It covers selecting hardware, configuring ESXi, optimizing guest operating systems, and managing virtual infrastructure. Specific topics include validating hardware compatibility, using CPUs with hardware virtualization features, selecting storage and networking hardware, configuring ESXi settings for power management and memory, and tips for VMware vCenter, vMotion, and other management tools.
This document discusses memory management in VMware ESX Server. It provides an overview of ESX memory management concepts including terminology, memory virtualization basics, and memory management in ESX. It then describes techniques for memory reclamation in ESX such as transparent page sharing, ballooning, and hypervisor swapping. It evaluates the performance of these techniques and provides best practices for host and guest memory usage.
This document provides an overview and guide for implementing and tuning open source applications on IBM PowerLinux systems using virtualization. It introduces common open source applications for web, mail, file, print and network serving. It then describes considerations for installing the Virtual I/O Server (VIOS), creating virtual servers, installing Linux and applications. The guide also covers monitoring with Ganglia and performance tuning. It is intended to help professionals plan and deploy open source solutions on IBM PowerLinux infrastructure.
JBoss AS 7 : Déployer sur terre et dans les nuagesAlexis Hassler
This document discusses the deployment of JBoss Application Server on both physical and cloud infrastructures. It provides an overview of the history and major versions of JBoss AS. It describes improvements in startup time, configuration, modularization, and deployment between versions 4.0 through 7.1. It also covers administration using the CLI and console, as well as deployment in PaaS environments like OpenShift and CloudBees.
Plesk 8.2 for Windows Domain Administrator's Guidewebhostingguy
To log in to Plesk, open the URL provided by your provider in a web browser and enter your login credentials. The standard view interface has a navigation pane on the left and main screen on the right, while the desktop view consolidates tools, statistics, and favorites. Familiarize yourself with search, sorting, and customization options to efficiently manage your website and email through Plesk.
The document provides instructions for installing Ubuntu Server Edition. It discusses preparing for installation by checking system requirements and backing up data. It then describes the installation process, which involves booting from the installation media, selecting options like keyboard layout and network configuration, partitioning disks, setting up users, and optionally installing package tasks like a mail server, web server, or database. The installation process is menu-driven and console-based for the server edition.
This document provides an overview and instructions for integrating IBM DB2 databases with the IBM System Storage N series. It discusses requirements, configuration, creating new databases, and migrating existing databases to the N series storage system. The document is intended to help users optimize DB2 database performance, backup and recovery, high availability, reliability, and storage requirements when using IBM N series storage.
The Ubuntu Server Guide provides step-by-step instructions for installing and configuring server applications on Ubuntu, covering topics like installation, package management, networking, security, monitoring, web servers, databases, file servers, email services, and more; it is intended as a task-oriented guide for system administrators to customize their Ubuntu server setup.
VM Explorer® is a simple but powerful software to back up, replicate and restore your VMware ESX, ESXi and Microsoft Hyper-V Virtual Machines (VM).
The following documentation explains the main tasks required for configuration and daily use of VM Explorer®. All services hereinafter are brought to you by HPE.
The HPE services and materials presented for VM Explorer® hereinafter are protected by copyright, trademark, trade dress, unfair competition, and other intellectual property rights. The trademarks, logos and marks of HPE and VM Explorer® displayed on the services and products are the property of HPE or third parties. You are not permitted to use the Marks without the prior consent of HPE or the third party that may own the Marks.
This document provides a proof of concept guide for evaluating VMware's Virtual SAN (VSAN) storage technology. It outlines the requirements, setup instructions, and test workflows to complete a full evaluation. The guide walks through configuring a VSAN cluster, creating VM storage policies, deploying VMs, testing availability and troubleshooting tools. Completing the steps will give customers hands-on experience with VSAN's full capabilities.
The document provides information about using the Symantec Backup Exec Command Line Applet, including:
- Required command line switches to perform Backup Exec functions like running backup jobs.
- Supported operations like backup, restore, managing media, and getting job status.
- Creating job scripts to automate backup jobs using command line switches.
- Targeting remote Backup Exec servers and logging in with credentials.
This document provides an overview of FreeNAS 8.3.0, including its core features, ZFS and RAID concepts, hardware considerations, and what's new in version 8.3.0. It covers topics such as installing FreeNAS, using the graphical interface, upgrading, configuring volumes and shares, managing ZFS features like snapshots and replication, installing plugins using the Plugins Jail, and installing additional software. The document contains information to help users perform essential FreeNAS system administration tasks.
This document provides instructions for installing Ubuntu Server Edition, including:
- Recommended system requirements for a server installation
- Differences between the server and desktop editions
- Backing up data before installation
- Running the installation from a CD which uses a console-based process to set up networking, configure the system hostname and time zone, partition the disk, set up a new user, and choose automatic update options
- Optional tasks like DNS, LAMP, mail, and file servers that can be selected to install additional related packages
This document provides instructions for advanced configuration of Autodesk data management server 2009/2010, including:
1. Customizing the installation location and SQL credentials.
2. Installing with other web applications that require a different .NET version by configuring a separate application pool.
3. Configuring the server for a remote SQL database, backups, vault connections, logging, and replication between servers.
Anoop Singh introduces himself and his background. He currently lives and works in India. Previously he worked for two other companies and has strengths in taking initiative, multitasking, and using technology for productivity. He provides his email address and LinkedIn profile for contact and expresses interest in working together with organizations to help achieve goals and objectives.
O.I.M. (Only Indy Music) is a proposed retail store that will give independent artists a place to sell their CDs and merchandise directly to fans. It will be the first major store specifically targeting independent artists. The store aims to provide artists opportunities for in-store distribution and performances to help them gain more control over their music careers.
This document provides instructions for getting started with JBoss ESB, including downloading and installing JBoss ESB, deploying it to the JBoss Application Server or JBoss ESB Server, and running a "Hello World" quickstart example to validate the installation. Key steps include downloading JBoss ESB and either the JBoss Application Server or JBoss ESB Server, configuring deployment properties, deploying JBoss ESB archives using Ant, and starting the server.
This document outlines the steps taken to create a double page spread for an A3 background. It lists adding the artist's name, stand first, images, a pull quote, columns of text, and page numbers as the key elements included in the production of the double page spread.
DHall Events is an Arkansas-based events company that offers services in central and northwest Arkansas. The company name comes from the owner's name to distinguish it from competitors. While others offer similar services, the owner aims to provide consistently high quality. The logo incorporates the owner's signature to represent something unique that cannot be replicated. It aims to attract accomplished young urban professionals seeking quality entertainment. The tagline "Signature Upscale Events" communicates the type of high-end events and signature touch provided.
Ringkasan dokumen tersebut adalah:
1) Dokumen tersebut membahas profil SMK Negeri 1 Rawajitu Selatan sebagai sekolah pangkal dalam kegiatan on the job learning calon pengawas sekolah.
2) SMK tersebut memiliki 5 program keahlian dan 19 rombel dengan total siswa 485 orang yang diampu 39 orang guru.
3) Calon pengawas melakukan supervisi manajerial dan akademik di sekolah tersebut sebagai bagian dari
Retailing Dictionary A To Z Retail BusinessAnoopsinghMba
This document provides definitions for over 100 common retail business terms starting with A through G. Some of the key terms defined include:
- Anchor store: A major store used to drive customers to smaller retailers in a shopping center.
- Brand: A name, symbol or mark associated with a seller's goods/services that distinguishes them from competitors.
- Brick and mortar: Refers to physical retail stores located in a building rather than online.
- Category killer store: A large specialty store with an enormous selection in its product category and low prices that draws customers from a wide area.
- Department store: A large retail unit organized into departments selling a wide variety of goods and services
The document provides an overview of JBoss Application Server, including its definition, architecture, advantages, installation, configuration, deployment, running applications, and undeployment. It discusses that JBoss is a widely used open source Java application server that allows deployment of Java applications and provides services like transaction processing and security. The document also provides details on installing JBoss, using the management console, deploying applications as WAR files using Ant build scripts, and modifying or removing deployed applications.
The document provides an introduction to JBoss Application Server, including its history, architecture, components, installation process, directory structure, and how to start and stop the server. It also discusses the JBoss Administration Console and JMX Console for managing and monitoring the application server.
The document provides an overview of getting started with JBoss Application Server 7, including downloading, installing, exploring the directory structure, starting the server, and managing it. Key points covered include downloading the distribution, a tour of the directory structure and configuration files, how to start the server in standalone and domain modes, and how to authenticate and use the administration console and CLI to manage the running server.
This document describes how to hack a default JBoss installation using the JMX console by deploying a web application that executes system commands. It explains how to create a WAR file with a JSP that allows command execution, deploy it to JBoss by adding the URL to the DeploymentScanner, and then use the application to execute commands with the privileges of the JBoss server. It concludes by providing information on securing the JMX console to prevent this type of attack.
This document provides an overview of installing and administering the JBoss Application Server. It discusses topics such as installing JBoss AS, understanding its directory structure, deploying applications, configuring web and enterprise services, database integration, security, performance tuning, and clustering for high availability and scalability. The document is intended as a guide for working with the popular open source JBoss Application Server.
This document discusses how to configure JBoss Application Server within Eclipse to develop Java EE applications. It describes how to download and set up Eclipse and JBoss AS, create a dynamic web project in Eclipse, write a simple servlet class, and define the servlet in a web deployment descriptor. The next steps of compiling, deploying to JBoss AS, and accessing the servlet via its defined URL are also outlined.
Medooze MCU Video Multiconference Server Installation and configuration guide...sreeharsha43
This document provides instructions for installing and configuring a Medooze MCU videoconferencing system on Ubuntu 12.04 LTS. It describes how to install various software tools like Wireshark, Java JDK, and NetBeans IDE. It then explains how to install the Medooze Media Mixer Server and mcuWeb application. Finally, it outlines the steps to deploy mcuWeb in application servers like GlassFish, JBoss and Tomcat, and configure media mixers, video profiles, conferences and other features of the videoconferencing system.
Composer 6.7 includes changes such as renaming executable files, adding support for distributed storage, and including data dictionaries for aspect types. It also streamlines the user interface and includes cheat sheets for importing applications from TaskSpace into Composer. Known issues are documented along with workarounds and limitations.
BISP is committed to provide BEST learning material to the beginners and advance learners.
In the same series, we have prepared a complete end-to end Hands-on Guide for WebLogic
Administration. The document focuses on how to install, configure and post configuration steps.
Join our professional training program and learn from experts.
This document provides instructions for setting up and configuring IBM Tivoli Access Manager for Enterprise Single Sign-On 8.1 in both single-server and clustered environments. It discusses installing and configuring the necessary software components like DB2, WebSphere Application Server, IBM HTTP Server, and the IMS server. It also covers steps for configuration of these components as well as the IMS server for single sign-on functionality. The document is intended as a guide for carrying out an end-to-end installation and configuration of the IBM Tivoli Access Manager single sign-on solution.
This document provides instructions for setting up a virtual machine environment for use in IBM UrbanCode Deploy labs. It includes downloading required software packages like Apache Tomcat, IBM UrbanCode Deploy, and a sample JPetStore application. It also guides setting up a Tomcat instance for a Systems Integration Test (SIT) environment on the virtual machine. Specifically, it covers expanding the Tomcat distribution, configuring user roles, and changing ports to avoid conflicts. This prepares the virtual machine for installing and configuring the IBM UrbanCode Deploy server and agents in the next lab.
You're on another typical JavaEE-based project, and you find yourself writing the same old infrastructure code - again. Are you wondering if there's a easier way to incorporate the basics such as configuration, logging, HTTP, and email into your application? If so, then this presentation is for you. By using a number of Java-based utilities from Apache and similar projects, you can learn how to stop re-inventing the wheel.
We'll start with a simple Java application and add the ability to use:
Apache Commons Lang for String handling
Apache Commons Configuration to configure an application
Apache Velocity Templates and Apache Commons Email to format and send email messages
Apache Commons IOUtils to simplify File and Stream I/O
Apache POI to generate Excel spreadsheets
Joda Time to simplify Date/Time handling
SLF4J and Logback to log messages
Jasypt to encrypt sensitive data
By learning to leverage these utilities, attendees can simplify their applications by reducing/eliminating infrastructure code.
This document provides instructions for installing an Oracle 11gR2 RAC database using raw devices on an AIX system. It discusses hardware and network requirements including configuring shared storage using HACMP. It provides details on installing Oracle Clusterware and database software, and creating the database. Key steps include preparing the system, installing Grid Infrastructure, installing the database software, and using DBCA or manual methods to create the database.
This document provides instructions for installing SwiftConfigurator software. It outlines requirements for the operating system, database, application server, and browser. It describes how to configure the Oracle 11g database and Application Server 10g. Steps are provided for deploying the SwiftConfigurator application and configuring datasources. Additional setup information is also included for language settings and known issues.
The document provides an overview of the Java Server Faces (JSF) framework and its architecture. It describes the six phases of the JSF lifecycle: restore view, apply request values, process validations, update model values, invoke application, and render response. It also discusses setting up the development environment for JSF, including installing Java, Eclipse, Maven, and Tomcat.
The document provides deployment guidance for EMC Documentum Content Management Interoperability Services (CMIS) version 7.2. It describes configuration settings for the Java virtual machine, Linux environment, Documentum CMIS configuration files, and supported application servers. Post-deployment validation steps are also outlined.
This document provides instructions for installing Zenoss Core Beta release 5.0.0b2, which introduces Zenoss Control Center. It describes installing Zenoss Control Center on a master host with certain requirements and preparing additional resource pool hosts. The steps include installing Docker, adding Zenoss repositories, and configuring the serviced daemon. Optional configuration allows multi-host deployment across resource pools.
The document provides instructions for setting up a development environment for JBoss, including installing Java JDK, EasyEclipse IDE, JBoss Application Server, and configuring directories. It also demonstrates how to create a basic J2EE web application with a Servlet, with code examples and build instructions. Key directories and files like the application.xml, web.xml, and packaging-build.xml are configured to deploy the Servlet war file to the JBoss Application Server.
Sharepoint 2007 Install Best Practice Phase 1LiquidHub
This document provides instructions for installing Microsoft Office SharePoint Server 2007 in a server farm. It outlines hardware and software requirements and describes installing SharePoint on front-end, application, and database servers. The two-phase process involves installing SharePoint using a domain administrator account, then running the configuration wizard to configure authentication, databases, and other settings. Additional post-installation steps include configuring Internet Explorer security settings and designating SharePoint administrators.
This document introduces Subversion (SVN) as a version control system that improves upon CVS. It discusses downloading and using SVN clients like TortoiseSVN, describes how to set up a SVN repository for a project with multiple developers, and provides examples of common SVN commands like checking out files, committing changes, and updating a working copy.
2. Getting Started Guide
A.2. TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND
MODIFICATION ....................................................................................................... 11
A.2.1. Section 0 ............................................................................................... 11
A.2.2. Section 1 ............................................................................................... 11
A.2.3. Section 2 ............................................................................................... 12
A.2.4. Section 3 ............................................................................................... 12
A.2.5. Section 4 ............................................................................................... 13
A.2.6. Section 5 ............................................................................................... 13
A.2.7. Section 6 ............................................................................................... 13
A.2.8. Section 7 ............................................................................................... 14
A.2.9. Section 8 ............................................................................................... 14
A.2.10. Section 9 ............................................................................................. 14
A.2.11. Section 10 ........................................................................................... 15
A.2.12. NO WARRANTY Section 11 ................................................................. 15
A.2.13. Section 12 ........................................................................................... 15
A.3. How to Apply These Terms to Your New Programs ............................................ 15
B. Revision History .......................................................................................................... 16
The quickest way to get started using JBoss ESB is by running one of the quickstarts in the
samples/quickstarts folder. This will also perform a basic validation of your system. Before doing
this however, be sure to check that your system meets the following minimum requirements:
1. JDK 5 (v1.5.0_06 recommended)
2. Ant (v1.6.5 recommended)
3. JBoss Application Server 4.2.x.GA or JBoss ESB Server 4.8
There are two ways to run JBossESB. You can deploy it to JBossAS / JBossESB Server,
or run standalone. This guide will concentrate on the JBoss Application Server / JBoss ESB
Server scenario because these scenarios are the most common and provide the largest range of
functionality to users. We suggest using the JBoss ESB Server for this guide.
The ESB components can also be deployed directly to the JBoss Application Server. If you
require .EAR deployment or if you require EJB3, then you will want to use the JBoss Application
Server. Below are the steps needed to install JBoss ESB to the JBoss Application server. If you
plan to use the JBoss ESB Server, no additional installation is required.
The JBoss ESB Server is an application server that serves as a convenient and lightweight
container to deploy to. It is a stripped down version of the JBoss application server that will deploy
all of your WAR, SAR, but does not contain EJB3 libraries or deployers. The main advantage of
using the ESB Server over using the JBoss ESB 4.8 Server is that it has a much quicker boot time
than the JBoss Application Server, which is helpful during development.
1. Downloading
This document assumes you have Ant (1.6.5 or higher) and Java5 installed on your machine,
and that you have a fresh copy of JBossAS. So now go and download the JBoss ESB 4.8
2
3. Installation to the JBoss Application Server (not required for ESB Server)
distribution from http://labs.jboss.com/portal/jbossesb/downloads. There are three corresponding
distribution versions, jbossesb-server-{version}, jbossesb-{version} and jbossesb-{version}-src.
The standalone JBossESB Server execution requires the jbossesb-server-{version} distribution
while deployed execution requires the jbossesb-{version} distribution.
If you wish to use the JBoss Application Server, download the JBoss ESB 4.8 distribution from
the above URL. Then download JBoss AS 4.2.3.GA from http://labs.jboss.com/portal/jbossesb/
downloads. JBoss AS 5 is supported starting from version 5.1.0.GA and can be downloaded from
the same location.
2. Installation to the JBoss Application Server (not
required for ESB Server)
1. Use jbossesb-{version}/install/deployment.properties.example as a template to create
install.deployment.properites.
2. Edit your version of install/deployment.properties. Open this file and edit the following lines if
needed to represent the directory where you have installed the JBoss application server and
the server configuration you wish. Most users choose “default” for their configuration setting:
# application server root directory
org.jboss.esb.server.home=/jboss-4.2.3.GA
# the instance of jboss you are running(default)
org.jboss.esb.server.config=default
3. Run 'ant' (default target) from the install directory. This will deploy JBossESB to your JBossAS
instance. It copies several .sar and .esb archives files and directories (jbossesb.esb, jbpm.esb,
jbrules.esb, smooks.esb, spring.esb, soap.esb) into the application server's deploy directory.
4. Start your server. There is a bin directory within the JBoss Application Server or the JBoss ESB
Server (whichever you have chosen to use). Execute the run script (run.sh on Linux/Mac OS
X/Unix, run.bat on Windows).
5. Verify the server you have chosen is running by visiting http://localhost:8080 with your web
browser.
3. Installation to the JBoss Application Server 5.1.0.GA
1. Download JBoss AS 5.1.0.GA from http://www.jboss.org/jbossas/downloads/ and unzip it.
2. Follow the same steps as listed above for “Installation to the JBoss Application Server (not
required for ESB Server)”
# application server root directory
3
4. Getting Started Guide
org.jboss.esb.server.home=/jboss-4.2.3.GA
# the instance of jboss you are running(default)
org.jboss.esb.server.config=default
Note
Depending on whether you access certain application (like the jopr console)
you might need to increase the memory settings when starting the server (in
run.conf):
-Xms128m -Xmx512m -XX:PermSize=200m -XX:MaxPermSize=500m
3.1. Windows script update for JBoss AS 5
The run.bat script contains an error which prevents wise from compiling the webservice proxies.
In order to fix the type you must edit the run.bat script and locate the following lines
if "x%JAVAC_JAR%" == "x" (
set "RUNJAR=%JAVAC_JAR%;%JBOSS_HOME%binrun.jar"
) else (
set "RUNJAR=%JBOSS_HOME%binrun.jar"
)
The fix involves switching the set statements so that they read as follows
if "x%JAVAC_JAR%" == "x" (
set "RUNJAR=%JBOSS_HOME%binrun.jar"
) else (
set "RUNJAR=%JAVAC_JAR%;%JBOSS_HOME%binrun.jar"
)
3.2. Scoped Deployments in JBoss AS 5
In ESB 4.x you can specify that a deployment be scoped by configuring this in deployment.xml:
<jbossesb-deployment>
<depends>jboss.esb:test=server</depends>
<depends>
4
5. Java 6
jboss.esb.qa.junit.destination:service=Queue,name=esb_gateway_channel_versioned
</depends>
<depends>
jboss.esb.qa.junit.destination:service=Queue,name=esb_channel_versioned
</depends>
<loader-repository>
org.jboss.soa.esb:loader=simple-scoped
<loader-repository-config>java2ParentDelegaton=false</loader-repository-config>
</loader-repository>
</jbossesb-deployment>
The AS5 deployers ignore this section of deployment.xml. Instead for a ESB 4.x scoped
deployment, users will be required to create a META-INF/jboss-classloading.xml:
<classloading xmlns="urn:jboss:classloading:1.0" domain="simple-scoped"
parent-first="false" />
3.3. Java 6
When using Java 6 the following jars are required to be available in <server_home>/lib/endorsed
• jaxb-api.jar
• jbossws-native-jaxrpc.jar
• jbossws-native-jaxws-.jar
• jbossws-native-jaxws-ext.jar
• jbossws-native-saaj.jar
4. ESB archive deployment strategies
JBossESB is packaged and shipped with base services. A service should be deployed in an ESB
archive consisting of an action code + configuration. The idea behind an ESB archive is that it
is a deployable service unit. An ESB archive is simply a zip file with an .esb extension. You can
deploy as many ESB archives as you please. You can influence the deployment order of archives
using the deployment.xml, which specifies start-order dependencies.
Typically you would deploy an ESB archive to the 'deploy' directory. ESB archives should enable
you to move services between servers simply by moving the corresponding ESB archive. An ESB
archive file has the following structure:
5
6. Getting Started Guide
####META-INF
# ####jboss-esb.xml
# ####deployment.xml
# ####MANIFEST.MF
####<java classes>
####<jars>
####<queue-service.xml>
• <jboss-esb.xml>: contains the service configuration (listener and actions), as well as provider
configuration.
• <deployment.xml>: is optional, but can be used for 2 reasons:
1. make this .esb archive depend on other archives, to specify classloading order.
2. make the deployment of this .esb archive scoped.
• <java classes>: your custom action classes in standard package hierarchy.
• <jars>: additional jar archives your actions depend on.
• <queue-service.xml>: if the 'providers' section of the jboss-esb.xml references queues or topics,
you can deploy their configuration in the ESB archive. Note that this is strictly a convenience and
any other way to deploy these queues is fine too. We recommend this approach to keep your
deployments as self-contained as possible therefore keeping dependency management simple.
JBossESB ships with a number of standard service archives:
jbossesb.esb
• http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/services/jbossesb/
• Contains internal services like the DeadLetterService, http://wiki.jboss.org/wiki/Wiki.jsp?
page=JBossESBDeadLetterService.
jbrules.esb
• http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/services/jbrules/
• Needed for rules evaluation using Drools, http://wiki.jboss.org/wiki/Wiki.jsp?
page=JBossRules
• Need for services like the Content-Based Router, http://wiki.jboss.org/wiki/Wiki.jsp?
page=JBossESBContentBasedRouting.
jbpm.esb
• http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/services/jbpm/
6
7. The Hello World Quickstart
• Needed for default provider of Business Process Management jBPM, http://
community.jboss.org/wiki/jbpm.
smooks.esb
• The default message transformation engine Smooks, http://docs.codehaus.org/display/
MILYN/Smooks+In+JBoss+ESB.
These services are deployed by default, but you should be able to remove them if you don't need
these service deployments.
5. The Hello World Quickstart
This QuickStart allows you get up and running with JBossESB, out of the box. It is located in the
distribution under samples/quickstarts/helloworld/.
To run this QuickStart following Running the Helloworld QuickStart.
Procedure 1. Running the Helloworld QuickStart
1. Start your Server in a way that allows you to view the output console. If you are on Windows,
it is preferable not to run JBoss as a Windows Service for the purposes of this guide.
2. From a command terminal window, change directory into the samples/quickstarts/
helloworld directory.
3. Make sure that install/deployment.properties has the correct configuration and home
directory settings for your server.
4. Type "ant deploy" to deploy the helloworld .esb package archive to your application server.
5. Type "ant runtest".
6. Switch back to your application server's console. You should soon see a "Hello World"
message appear in your application server's console.
7. That's it! The QuickStart ran successfully. Your environment is properly configured for
JBossESB.
You can find more detailed directions on how to setup the quickstart examples by running "ant
help-quickstarts" under any of the specific quickstart directories. To get information on how to
run a particular quickstart under different deployment scenarios, change directory to the specific
quickstart and type "ant help".
5.1. Components of the QuickStart
The following diagram illustrates the sequence of events that take place in this QuickStart. It
touches on a number of the key concepts within JBossESB.
7
8. Getting Started Guide
Figure 1. HelloWorld QuickStart Sequence of Events
Window1 shows each of the main "ESB" components used in this sample:
1. Service Registry: This is a JAXR Registry implementation. In this QuickStart, the registry
uses RMI based communication. See docs/services/RegistryConfiguration.pdf for more
details on the Registry Service.
2. JMS Gateway Listener: A "Gateway Listener" is one of the key architectural components within
JBossESB. This listener type is, as its name would suggest, the gateway to the ESB from
endpoints outside the domain of the ESB. In this case, we're using a JMS Gateway.
3. The ESB Aware Service Listener: The "FirstServiceESB:SimpleListener" ESB Aware Service
Listener listens for "ESB Aware" messages on "queue/quickstart_helloworld_Request_esb".
This introduces you further to the concept of ESB "Aware" and "Unaware" messages. We will
touch on these next.
5.2. ESB Aware and Unaware Messages
JBossESB has a well defined concept of what a message is. This is defined fully in xml/
message.xsd. This construct makes it possible to pass decorated messages payloads between
components of the ESB. The message payload is typically stored in the message "Body" (see
the Programmers Guide).
8
9. QuickStart Sequence of Events
This makes a lot of sense from the point of services within the ESB domain being able to
collaborate effectively. However, it is not practical to expect endpoints outside the domain of a
JBossESB deployment to be "aware" of these internal ESB constructs. For this reason, JBossESB
has the concept of ESB Aware and Unaware Messages and Endpoints, with the Gateway acting
as the bridge (adapter) between the two worlds.
5.3. QuickStart Sequence of Events
After starting the ESB in Window1 and before any "Hello World" messages are put on the bus,
the "FirstServiceESB:SimpleListener" Service is registered with the Registry Service.
The sequence of events in the Hello World QuickStart are as follows:
• ESB Unaware JMS Client endpoint puts an ESB Unaware "Hello World" Message (plain String
Object) into JMS Queue "queue/quickstart_helloworld_Request_gw".
• The JMS Gateway Listener receives the ESB Unaware message. The Gateways Job is to adapt
this message by making it an ESB Aware Message for consumption by an ESB Aware Endpoint.
• The JMS Gateway Listener uses the registry to lookup the Endpoint Reference (EPR)
for "FirstServiceESB:SimpleListener" Service. This works out to be JMS Queue "queue/
quickstart_helloworld_Request_esb".
• The JMS Gateway Listener "adapts" the message into an ESB Aware message and places it
into JMS Queue "queue/quickstart_helloworld_Request_esb".
• "FirstServiceESB:SimpleListener" Service receives the message.
• "FirstServiceESB:SimpleListener" Service extracts the payload from the message and prints it
to the console.
6. Running other QuickStarts
Once you have successfully run the Helloworld QuickStart and understand the concepts
involved, there are many other Quickstarts to try. Please note that the Quickstarts have different
requirements which are documented in their respective readme.txt, and that not all of the
Quickstarts will run in every deployment. Below is a suggested map of Quickstarts to follow in
order.
Quickstarts Trailmap
1. helloworld
2. helloworld_action
3. custom_action
4. helloworld_file_action
9
10. Getting Started Guide
5. helloworld_ftp_action
6. simple_cbr
7. fun_cbr
8. business_service
9. business_rules_service
10.scripting_groovy
11.transform_CSV2XML
12.transform_XML2POJO
13.transform_XML2XML_simple
14.transform_XML2XML_date_manipulation
15.aggregator
16.bpm_orchestration1
17.bpm_orchestration2
18.webservice_consumer1
19.webservice_producer
A. GNU General Public License
A.1. Preamble
The licenses for most software are designed to take away your freedom to share and change
it. By contrast, the GNU General Public License is intended to guarantee your freedom to share
and change free software - to make sure the software is free for all its users. This General Public
License applies to most of the Free Software Foundation's software and to any other program
whose authors commit to using it. (Some other Free Software Foundation software is covered by
the GNU Library General Public License instead.) You can apply it to your programs, too.
When we speak of free software, we are referring to freedom, not price. Our General Public
Licenses are designed to make sure that you have the freedom to distribute copies of free software
(and charge for this service if you wish), that you receive source code or can get it if you want
it, that you can change the software or use pieces of it in new free programs; and that you know
you can do these things.
To protect your rights, we need to make restrictions that forbid anyone to deny you these rights
or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you
if you distribute copies of the software, or if you modify it.
10
11. TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
For example, if you distribute copies of such a program, whether gratis or for a fee, you must give
the recipients all the rights that you have. You must make sure that they, too, receive or can get
the source code. And you must show them these terms so they know their rights.
We protect your rights with two steps:
1. copyright the software, and
2. offer you this license which gives you legal permission to copy, distribute and/or modify the
software.
Also, for each author's protection and ours, we want to make certain that everyone understands
that there is no warranty for this free software. If the software is modified by someone else and
passed on, we want its recipients to know that what they have is not the original, so that any
problems introduced by others will not reflect on the original authors' reputations.
Finally, any free program is threatened constantly by software patents. We wish to avoid the
danger that redistributors of a free program will individually obtain patent licenses, in effect making
the program proprietary. To prevent this, we have made it clear that any patent must be licensed
for everyone's free use or not licensed at all.
The precise terms and conditions for copying, distribution and modification follow.
A.2. TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION
AND MODIFICATION
A.2.1. Section 0
This License applies to any program or other work which contains a notice placed by the copyright
holder saying it may be distributed under the terms of this General Public License. The “Program”,
below, refers to any such program or work, and a “work based on the Program” means either the
Program or any derivative work under copyright law: that is to say, a work containing the Program
or a portion of it, either verbatim or with modifications and/or translated into another language.
(Hereinafter, translation is included without limitation in the term “modification”.) Each licensee is
addressed as “you”.
Activities other than copying, distribution and modification are not covered by this License; they
are outside its scope. The act of running the Program is not restricted, and the output from the
Program is covered only if its contents constitute a work based on the Program (independent of
having been made by running the Program). Whether that is true depends on what the Program
does.
A.2.2. Section 1
You may copy and distribute verbatim copies of the Program's source code as you receive it, in any
medium, provided that you conspicuously and appropriately publish on each copy an appropriate
copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License
11
12. Getting Started Guide
and to the absence of any warranty; and give any other recipients of the Program a copy of this
License along with the Program.
You may charge a fee for the physical act of transferring a copy, and you may at your option offer
warranty protection in exchange for a fee.
A.2.3. Section 2
You may modify your copy or copies of the Program or any portion of it, thus forming a work based
on the Program, and copy and distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:
a. You must cause the modified files to carry prominent notices stating that you changed the files
and the date of any change.
b. You must cause any work that you distribute or publish, that in whole or in part contains or is
derived from the Program or any part thereof, to be licensed as a whole at no charge to all third
parties under the terms of this License.
c. If the modified program normally reads commands interactively when run, you must cause it,
when started running for such interactive use in the most ordinary way, to print or display an
announcement including an appropriate copyright notice and a notice that there is no warranty
(or else, saying that you provide a warranty) and that users may redistribute the program under
these conditions, and telling the user how to view a copy of this License. (Exception: If the
Program itself is interactive but does not normally print such an announcement, your work
based on the Program is not required to print an announcement.)
These requirements apply to the modified work as a whole. If identifiable sections of that work
are not derived from the Program, and can be reasonably considered independent and separate
works in themselves, then this License, and its terms, do not apply to those sections when you
distribute them as separate works. But when you distribute the same sections as part of a whole
which is a work based on the Program, the distribution of the whole must be on the terms of this
License, whose permissions for other licensees extend to the entire whole, and thus to each and
every part regardless of who wrote it.
Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely
by you; rather, the intent is to exercise the right to control the distribution of derivative or collective
works based on the Program.
In addition, mere aggregation of another work not based on the Program with the Program (or with
a work based on the Program) on a volume of a storage or distribution medium does not bring
the other work under the scope of this License.
A.2.4. Section 3
You may copy and distribute the Program (or a work based on it, under Section 2 in object code
or executable form under the terms of Sections 1 and 2 above provided that you also do one of
the following:
12
13. TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
a. Accompany it with the complete corresponding machine-readable source code, which must
be distributed under the terms of Sections 1 and 2 above on a medium customarily used for
software interchange; or,
b. Accompany it with a written offer, valid for at least three years, to give any third party, for
a charge no more than your cost of physically performing source distribution, a complete
machine-readable copy of the corresponding source code, to be distributed under the terms of
Sections 1 and 2 above on a medium customarily used for software interchange; or,
c. Accompany it with the information you received as to the offer to distribute corresponding
source code. (This alternative is allowed only for noncommercial distribution and only if you
received the program in object code or executable form with such an offer, in accord with
Subsection b above.)
The source code for a work means the preferred form of the work for making modifications to
it. For an executable work, complete source code means all the source code for all modules it
contains, plus any associated interface definition files, plus the scripts used to control compilation
and installation of the executable. However, as a special exception, the source code distributed
need not include anything that is normally distributed (in either source or binary form) with the
major components (compiler, kernel, and so on) of the operating system on which the executable
runs, unless that component itself accompanies the executable.
If distribution of executable or object code is made by offering access to copy from a designated
place, then offering equivalent access to copy the source code from the same place counts as
distribution of the source code, even though third parties are not compelled to copy the source
along with the object code.
A.2.5. Section 4
You may not copy, modify, sublicense, or distribute the Program except as expressly provided
under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is
void, and will automatically terminate your rights under this License. However, parties who have
received copies, or rights, from you under this License will not have their licenses terminated so
long as such parties remain in full compliance.
A.2.6. Section 5
You are not required to accept this License, since you have not signed it. However, nothing else
grants you permission to modify or distribute the Program or its derivative works. These actions
are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the
Program (or any work based on the Program), you indicate your acceptance of this License to do
so, and all its terms and conditions for copying, distributing or modifying the Program or works
based on it.
A.2.7. Section 6
Each time you redistribute the Program (or any work based on the Program), the recipient
automatically receives a license from the original licensor to copy, distribute or modify the Program
13
14. Getting Started Guide
subject to these terms and conditions. You may not impose any further restrictions on the
recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance
by third parties to this License.
A.2.8. Section 7
If, as a consequence of a court judgment or allegation of patent infringement or for any other
reason (not limited to patent issues), conditions are imposed on you (whether by court order,
agreement or otherwise) that contradict the conditions of this License, they do not excuse you
from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your
obligations under this License and any other pertinent obligations, then as a consequence you
may not distribute the Program at all. For example, if a patent license would not permit royalty-
free redistribution of the Program by all those who receive copies directly or indirectly through
you, then the only way you could satisfy both it and this License would be to refrain entirely from
distribution of the Program.
If any portion of this section is held invalid or unenforceable under any particular circumstance,
the balance of the section is intended to apply and the section as a whole is intended to apply
in other circumstances.
It is not the purpose of this section to induce you to infringe any patents or other property right
claims or to contest validity of any such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system, which is implemented by public license practices.
Many people have made generous contributions to the wide range of software distributed through
that system in reliance on consistent application of that system; it is up to the author/donor to
decide if he or she is willing to distribute software through any other system and a licensee cannot
impose that choice.
This section is intended to make thoroughly clear what is believed to be a consequence of the
rest of this License.
A.2.9. Section 8
If the distribution and/or use of the Program is restricted in certain countries either by patents
or by copyrighted interfaces, the original copyright holder who places the Program under this
License may add an explicit geographical distribution limitation excluding those countries, so that
distribution is permitted only in or among countries not thus excluded. In such case, this License
incorporates the limitation as if written in the body of this License.
A.2.10. Section 9
The Free Software Foundation may publish revised and/or new versions of the General Public
License from time to time. Such new versions will be similar in spirit to the present version, but
may differ in detail to address new problems or concerns.
Each version is given a distinguishing version number. If the Program specifies a version number
of this License which applies to it and “any later version”, you have the option of following the
14
15. How to Apply These Terms to Your New Programs
terms and conditions either of that version or of any later version published by the Free Software
Foundation. If the Program does not specify a version number of this License, you may choose
any version ever published by the Free Software Foundation.
A.2.11. Section 10
If you wish to incorporate parts of the Program into other free programs whose distribution
conditions are different, write to the author to ask for permission. For software which is copyrighted
by the Free Software Foundation, write to the Free Software Foundation; we sometimes make
exceptions for this. Our decision will be guided by the two goals of preserving the free status of
all derivatives of our free software and of promoting the sharing and reuse of software generally.
A.2.12. NO WARRANTY Section 11
BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT
WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER
PARTIES PROVIDE THE PROGRAM “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK
AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD
THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY
SERVICING, REPAIR OR CORRECTION.
A.2.13. Section 12
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/
OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR
DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL
DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING
BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR
LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO
OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY
HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
END OF TERMS AND CONDITIONS
A.3. How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest possible use to the public, the
best way to achieve this is to make it free software which everyone can redistribute and change
under these terms.
To do so, attach the following notices to the program. It is safest to attach them to the start of each
source file to most effectively convey the exclusion of warranty; and each file should have at least
the “copyright” line and a pointer to where the full notice is found.
15
16. Getting Started Guide
<one line to give the program's name and a brief idea of what it does.> Copyright (C) <year>
<name of author>
This program is free software; you can redistribute it and/or modify it under the terms of the GNU
General Public License as published by the Free Software Foundation; either version 2 of the
License, or (at your option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY;
without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR
PURPOSE. See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with this program;
if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA
02110-1301 USA
Also add information on how to contact you by electronic and paper mail.
If the program is interactive, make it output a short notice like this when it starts in an interactive
mode:
Gnomovision version 69, Copyright (C) year name of author Gnomovision comes with
ABSOLUTELY NO WARRANTY; for details type “show w”. This is free software, and you are
welcome to redistribute it under certain conditions; type “show c” for details.
The hypothetical commands “show w” and “show c” should show the appropriate parts of the
General Public License. Of course, the commands you use may be called something other than
“show w” and “show c”; they could even be mouse-clicks or menu items--whatever suits your
program.
You should also get your employer (if you work as a programmer) or your school, if any, to sign a
“copyright disclaimer” for the program, if necessary. Here is a sample; alter the names:
Yoyodyne, Inc., hereby disclaims all copyright interest in the program “Gnomovision” (which
makes passes at compilers) written by James Hacker.
<signature of Ty Coon>, 1 April 1989 Ty Coon, President of Vice
This General Public License does not permit incorporating your program into proprietary programs.
If your program is a subroutine library, you may consider it more useful to permit linking proprietary
applications with the library. If this is what you want to do, use the GNU Library General Public
License instead of this License.
B. Revision History
Revision History
Revision 1 Fri Jul 16 2010 DavidLe
Sage<dlesage@redhat.com>,
DarrinMison<dmison@redhat.com>
16