Table of contents (Corrected on May 31. 2016) In the Overview section updated the last sentence of the first paragraph. In the Product positioning section under the heading for DB2 Direct Standard Edition changed DB2 Advanced Workgroup Server Edition to DB2 Workgroup Server Edition.
In the Program technical support section replaced the second paragraph with updated text.
Includes the functionality and tools needed for large, complex enterprise environments, and is ideal for both transactional and data warehouse workloads. Is available on a PVU, per Authorized User Single Install (AUSI), or per Terabyte charge metric. Under the AUSI charge metric, you must acquire a minimum of 25 AUSI licenses per 100 PVUs. Under the per Terabyte charge metric, you must 1) Use the database for a data warehouse and run a data warehouse workload. A data warehouse is a subject-oriented, integrated, time-variant collection of data that integrates data from multiple data sources for historical ad hoc data reporting and querying.
A data warehouse workload is a workload that typically scans thousands or millions of rows in a single query in order to support the analysis of data in a data warehouse; 2) Have user data from a single database spread across two or more active data partitions or at least 75% of the user data residing in BLU Acceleration column-organized tables with a majority of the workload accessing the BLU Acceleration column-organized tables; 3) Not use DB2 for Linux, UNIX, and Windows built-in high availability disaster recovery (HADR) or pureScale capabilities. Is designed to meet the data server needs of midsize to large-size businesses and is ideal for transactional and mixed workloads. It can be deployed on Linux, UNIX, or Windows servers of any size, from one processor to hundreds of processors, and on both physical and virtual servers.
The edition includes IBM Data Studio, Label Based Access Control, Row and Column Access Control, Multi-Temperature Data Management, Time Travel Query, Table Partitioning, High Availability Disaster Recovery, Online Reorganization, Materialized Query Tables (MQTs), Multidimensional Clustering (MDC), Query Parallelism, Scan Sharing, Connection Concentrator, pureXML, backup compression, and Tivoli System Automation for Multiplatforms for use with high availability. The product also includes DB2 Homogeneous Federation and Homogeneous SQL Replication allowing federated data access and replication between DB2 for Linux, UNIX and Windows servers as well as web services federation. Includes the capabilities needed for medium-sized business environments, and is ideal for both transactional and data warehouse workloads.
The edition includes largely the same functionality and tools as DB2 Advanced Enterprise Server Edition. The main difference is that DB2 Advanced Workgroup Server Edition has processor core, socket, memory, and terabyte restrictions described below. In addition, DB2 Advanced Workgroup Server Edition supports federation only with DB2 for Linux, UNIX and Windows and Informix data sources. Is available on a PVU, per Authorized User Single Install (AUSI), or per Terabyte charge metric. Under the AUSI charge metric, you must acquire a minimum of 25 AUSI licenses per 100 PVUs. Under the PVU and AUSI charge metrics, you are restricted to 16 processor cores and 128 GB of instance memory while under the per Terabyte charge metric, you are restricted to 4 processor sockets. These restrictions are per physical or, where partitioned, virtual server except in a pureScale or DPF cluster where the restrictions apply to the entire cluster.
Under all charge metrics, you are restricted to 15 terabytes of user data per database. Under the Terabyte charge metric, you must also 1) use the database for a data warehouse and run a data warehouse workload. A data warehouse is a subject-oriented, integrated, time-variant collection of data that integrates data from multiple data sources for historical ad hoc data reporting and querying. A data warehouse workload is a workload that typically scans thousands or millions of rows in a single query in order to support the analysis of data in a data warehouse; 2) Have user data from a single database spread across two or more active data partitions or at least 75% of the user data residing in BLU Acceleration column-organized tables with a majority of the workload accessing the BLU Acceleration column-organized tables; 3) Not use DB2 for Linux, UNIX, and pureScale capabilities. Is suitable for transactional database workloads in a departmental, workgroup, or medium-sized business environment.
The edition shares significant functionality with DB2 Enterprise Server Edition but has processor core and memory restrictions described below. DB2 Workgroup Server Edition can be deployed in Linux, UNIX, and Windows server environments. If using multiple virtual servers on a physical server, there is no limit on the cores or memory available to the physical server providing the processor and memory restrictions are observed by the virtual servers running DB2. This makes DB2 Workgroup Server Edition ideal for consolidating multiple workloads onto a large physical server running DB2 Workgroup Server Edition in multiple virtual servers. Is a full-function transactional data server, which provides very attractive entry-level pricing for the small and medium business (SMB) market. It comes with simplified packaging and is easy to transparently install within an application. With DB2 Express Server Edition, it is easy to subsequently upgrade to the other editions of DB2 10.5 since DB2 Express Server Edition includes most of the same features, including security and HADR, as the more scalable editions.
DB2 Express Server Edition can be deployed in x64 server environments and is restricted to 8 processor cores and 64 GB of memory per physical or, where partitioned, virtual server. If using multiple virtual servers on a physical server, there is no limit on the cores or memory available to the physical server providing the processor and memory restrictions are observed by the virtual servers running DB2. This makes DB2 Express Server Edition ideal for consolidating multiple workloads onto a large physical server running DB2 Express Server Edition in multiple virtual servers. DB2 Advanced Recovery feature is a bundle of advanced database backup, recovery, and data extraction tools that can help enterprises improve data availability, mitigate risk, and accelerate crucial administrative tasks when time is of the essence.
The feature bundle contains the following tools: IBM DB2 Merge Backup for Linux, UNIX, and Windows V2.1 IBM DB2 Recovery Expert for Linux, UNIX, and Windows V4.1 IBM Optim High Performance Unload for DB2 for Linux, UNIX, and Windows V5.1 Program charges: DB2 10.5 Advanced Recovery feature is available under Authorized User Single Install, PVU, and per Terabyte charge metrics. You must acquire the same Metric and number of entitlements as you have acquired for the DB2 for Linux, UNIX, and Windows server that you will be running this feature against.
Buy the D0A1LLL IBM DB2 Workgroup Server Edition with 1 Year Software Subscription and Support for your technical service repair or maintenance IT part networking systems. The D0A1LLL IBM DB2 Workgroup Server Edition with 1 Year Software Subscription and Support is part of our discounted, computer systems IT parts liquidation inventory. We supply the D0A1LLL IBM DB2 Workgroup Server Edition with 1 Year Software Subscription and Support and everything else you need for all of your IT parts systems hardware, upgrades and maintenance at discounted liquidation prices.
1.3 DB2 UDB Editions DB2 UDB for Linux, UNIX, and Windows (sometimes referred to as LUW) is developed using the C/C language; more than ninety percent of the code is common among these platforms. The remaining code is unique to take full advantage of the underlying platform architecture; however, the database functionality on all of these platforms is the same. Like any other C/C application, DB2 is written in separate modules&8212.c/.C source files&8212;that have been separately compiled to obtain object files (.o files). These object files are later linked to obtain an executable file. Shows a simplified view of how each edition is built.
How DB2 editions build on top of each other As you can see in, each edition (other than DB2 UDB Everyplace, which is not shown in the figure) builds on top of the other by linking modules or object files that contain additional functionality. The core of the DB2 UDB code is common across all editions, which greatly benefits application development. For example, if you are developing an application for the DB2 UDB Personal Edition, this application will also work on the DB2 UDB Workgroup Server Edition, the DB2 UDB Express Edition, and the DB2 UDB Enterprise Server Edition on any of the supported platforms. From the above explanation, it should be clear that the DB2 LUW editions are mainly packaging and licensing distinctions that let you choose the appropriate features or functions you need for the right price. The underlying technology is always DB2, so choose the appropriate edition based on the features and functions you need and which server(s) DB2 will be running.
Refer to Appendix C, IBM Servers, for a description of the xSeries, eSeries, pSeries, iSeries, and zSeries servers. Illustrates the different editions and the types of servers they typically run on. DB2 takes advantage of all the processing power it is given, and the figure also shows that DB2 is a scalable product.
With the exception of DB2 UDB Everyplace, the functions, features, and benefits of an edition shown on the bottom of the figure are included in each subsequent edition as you move up the figure. The following sections provide more detail on the functionality of each edition. DB2 UDB editions 1.3.1 Everyplace Edition As its name implies, the DB2 UDB Everyplace edition can run anywhere, anytime, in all kinds of small devices like personal digital assistants (PDAs), handheld computers, embedded devices, and laptops. DB2 UDB Everyplace, though only about 200K in size, is a true RDBMS that uses a subset of the DB2 UDB server SQL functionality. While database maintenance operations and some specific features like triggers are not supported, DB2 UDB Everyplace does include the DB2 UDB Everyplace Mobile Application Builder tool to develop, deploy, and support e-business applications. If you know how to code an application for a DB2 UDB server edition, you know how to code for DB2 UDB Everyplace.
Applications can be developed using ODBC, CLI, JDBC, and.NET. Typically, users of DB2 UDB Everyplace store information in the mobile database and later replicate it to a back-end database server using the DB2 UDB Everyplace Sync Server installed on another machine. This edition supports operating systems that run on mobile devices.
Embedded Linux. Java 2 Micro Edition (J2ME) devices. Microsoft Windows CE/PocketPC. Palm OS. QNX Neutrino. Symbian. Windows 32-bit operating systems DB2 UDB Everyplace can be licensed as a fully synchronized environment or as a standalone embedded database.
1.3.2 Personal Edition The DB2 UDB Personal Edition (PE) is a complete product for a single user. It has all the functionality of a database server, including the administration graphical tools, as well as audio, image, spatial, and video extenders. While this edition can also be used as a client to connect to other DB2 servers, it does not support database connections from other computers. Only Windows and Linux operating systems, which are the most commonly used platforms in personal computers, support the DB2 UDB Personal Edition.
Shows the DB2 UDB PE installed on Machine 2. The local DB2 client (the client component of Machine 2) can connect to the DB2 UDB PE server on Machine 2, but the remote DB2 client in Machine 1 cannot connect to the server on Machine 2 because DB2 UDB PE does not accept remote (inbound) connections. The figure also shows the DB2 UDB PE on Machine 2 as the remote client to other DB2 UDB server editions installed on machines 3, 4, and 5. A DB2 UDB database is considered a server when it can accept inbound client connections for data retrieval purposes.
Hence, DB2 UDB Personal Edition is not considered a DB2 UDB server. 1.3.3 Workgroup Server Edition The DB2 UDB Workgroup Server Edition ( WSE) is a full-function database server designed for deployment in a department or small business environment. Linux, UNIX, and Windows platforms support the DB2 UDB WSE running on at most four CPU servers with a 32-bit operating system. It comes under two licensing models. Licensing per user (ideal for applications with just a few users). Licensing per processor (ideal for applications with many users, like a Web application) This edition is referred to as Workgroup Server Unlimited Edition ( WSUE) when using the per-processor licensing model because an unlimited number of users are allowed. 1.3.4 Express Edition The DB2 UDB Express Edition, a low-cost, full-function database server, is ideal for a business that requires a database, but has minimal in-house database skills.
This edition provides the same support as DB2 UDB WSE, but it also features one-click installation, enhanced self-management, and other ease-of-use features. Businesses developing applications that require a database can embed DB2 UDB Express Edition as part of their solution. The supported operating systems for this edition are Windows and Linux (on Intel and AMD), running at most on two CPU 32-bit SMP hardware computers. 1.3.5 Enterprise Server Edition The Enterprise Server Edition ( ESE) is the most complete database server offering.
It provides unparalleled scalability, accessibility, and extensibility features, as well as full 64-bit support, and is the edition of choice for most enterprises. It provides the same functionality as DB2 UDB WSE, but also includes DB2 Connect functionality, which provides licensed access for a single user to connect to host systems like DB2 UDB for iSeries or DB2 UDB for OS/390 and z/OS (zSeries).
DB2 UDB ESE includes the database partitioning feature ( DPF), which allows you to partition your data within a single server or across multiple servers running the same operating system. This means that your databases can grow to sizes that are limited only by the number of servers available. DPF can be used when you buy the corresponding DPF license. You can use DB2 UDB ESE in SMP systems, and DB2 UDB ESE with DPF can be used in either SMP or clustered server systems. The supported operating system platforms are Linux, UNIX, and Windows. Summarizes all the DB2 editions and features.
IBM Blue Gene-P This Quick Guide is available in PDF format – Simply subscribe to our free newsletter to receive a free copy instantly. Introduction IBM is one of the largest software vendors in the world – some rankings even list it as the largest software vendor. However, IBM licensing rules and policies are not as well-known as that of some other software vendors. One reason for this is that IBM has a broad portfolio of software which is continually expanding, and each product has different licensing rules and methods of measuring deployment. This guide aims at providing a quick overview of licensing topics which apply to most IBM software products. IBM brands IBM groups its software offerings in five general “brands”:. DB2 and Information Management: This brand is mostly known for its DB2 database products such as DB2 Enterprise Edition.
Other products in this brand focus on areas such as data warehousing, data analysis, data mining, media asset management, enterprise content management and information integration. Acquisitions which have been added to this brand include Informix (2001), Ascential (2005), FileNet (2006), and Cognos (2008). Lotus: Besides the well-known Lotus Notes/Domino email software, this brand covers products which are aimed at providing a unified environment for messaging, calendaring, application development, real-time and team collaboration, content management, mobile and wireless devices, and social networking. Lotus Software was acquired by IBM in 1995. Tivoli: The products in this brand focus on infrastructure management. Examples of commonly used products are Tivoli Storage Manager (for data backup and restore) and Tivoli Monitoring (for monitoring performance and availability of servers and applications). Tivoli Systems was acquired by IBM in 1997.
Recent acquisitions which were added to this brand are Candle (2004), Micromuse (2006), and MRO (2006). Rational: This brand groups most IBM software relating to software development and delivery. Rational itself was acquired by IBM in 2003 and expanded through the acquisition of Telelogic in 2008. WebSphere: Product families within this brand are application servers, business integration, commerce, development tools, and portals. Commonly used products are WebSphere Application Server and WebSphere MQ (middleware).
IBM frequently expands its portfolio through product development and acquisitions of software companies. 2015-2017 games ps2 games torrent. An overview of the most common IBM products within each brand can be found.
In some cases, IBM changes the licensing rules of the acquired company to align with the existing IBM rules. In other cases, IBM chooses to maintain some of the license metrics of the acquired company (Maximo and Cognos are examples).
Passport Advantage The programs through which IBM offers its software licenses are called Passport Advantage (for larger organizations) and Passport Advantage Express (from small to midsized organizations). Passport Advantage Express has no minimum purchase requirement and its offerings are priced per transaction – no discount applies for volume licensing. Passport Advantage, on the other hand, applies a points-based system to calculate volume discount. Based on the number of purchases a customer makes each year, a Relationship Suggested Volume Price (RVSP)-Level is assigned, with a corresponding discount level. Large organizations are wise to consolidate their IBM license contracts as much as possible to benefit from these volume discounts. In most cases, IBM software licenses allow the customer to use the software indefinitely, although fixed-term licenses are also available.
Once a license has been purchased, the customer is required to buy software subscription and support annually in order to benefit from software updates and technical support. The initial purchase of a software license generally includes subscription and support for the first year. Using your Passport Advantage user ID and password, it is possible to obtain an overview of your software entitlements through the IBM website. Capacity based license metrics The Processor Value Unit (PVU) license metric is the most common license type for IBM server products. The advent of multi-core processors and increasingly powerful hardware technologies lead IBM to introduce this license metric in 2006. Previously, licenses were calculated “per processor”. As performance of processor technologies began to differentiate, IBM adapted their licensing policy accordingly.
The PVU license metric is meant to align license requirements with hardware performance. For example, a dual-core POWER5 chip requires double the amount of PVUs as a dual-core AMD Opteron chip (200 PVUs vs. Note that single-core chips almost always require 100 PVUs (with the exception of Cell processors). The latest PVU conversion table can be found.
IBM continually updates this table to reflect new developments in processor technologies. Currently, PVU calculations are based on Processor Vendor, Brand, Type and Model Number. Be aware that the use of the word “processor” may sometimes lead to confusion. IBM uses the word processor to indicate a “core”, as opposed to a “chip” (or “socket”), which may contain multiple cores. Some hardware vendors however define “processor” as being a “chip”. Make sure that these distinctions are understood when using software asset management (SAM)-tools or a CMDB to determine the deployed quantity of PVUs. Many Tivoli products (such as Tivoli Storage Manager and Tivoli Monitoring) are licensed based on the environment being managed by the Tivoli product.
For example, when Tivoli Monitoring is used to monitor 500 servers in the environment, PVU entitlements must be purchased to cover all 500 servers. Customers who deploy these products in a large environment need to consider how to efficiently collect server hardware details in order to calculate PVU deployment. Besides the PVU license metric, some server products are still licensed based on the install or the server license metric. Deployment for such products can be calculated by determining the number of installed copies (install) or physical servers hosting the software (server). User based license metrics The authorized user metric is the most common license type for user-based products.
In some cases server-based products can also be licensed per user. Users are defined as people who access the software in any manner. Once a user is assigned as an “authorized user”, the license may not be reassigned to another user, unless the original user is being replaced on a long-term or permanent basis. In some environments, it may not be straightforward to identify the end users of a certain product. For example, a database product may only be accessed by some third-party applications and a few administrators. In this case, all users of the third-party applications would also need to be licensed. When multiplexing technology is used, the same applies – all the end users need to be licensed.
Edition Limited Art
A useful thought experiment can be to ask the following question: “What would happen if I deactivate this product today, who would be affected?” Those people are usually the ones that would need to be licensed. Also note that for some server products, a minimum purchase quantity of authorized users applies. For example, the licensing terms and conditions of DB2 Workgroup Server Edition indicate that a minimum of 5 authorized users must be purchased per server on which it is installed. Other common user-based license metrics include Concurrent User, Floating User and User Value Unit. Concurrent User licenses allow a certain number of users to access a program simultaneously. The number of licenses required is the maximum peak of concurrent users which have accessed the program at any time. Depending on the IT environment, it may be beneficial to deploy software which limits or measures concurrent usage to prevent usage to exceed the number of licenses.
Floating Users, which are common for Rational software, are similar to Concurrent Users. Floating User products usually require license keys to be installed on a central server. Each user then needs to “borrow” a license key to start using the program – in case no license keys are available, access is denied. Rather than measuring actual usage, the deployment quantity is determined by counting the number of installed license keys.
User Value Units (UVU), which is used for some Tivoli products, are similar to authorized users. Usually this metric is used to allow for tier-based volume licensing. For example, 5,000 users of Tivoli Identity Manager would require 5,000 UVUs, but 10,000 users would only require 7,500 UVUs. For each product the tier levels are different. Within the Lotus brand, a special type of user license is the Lotus Domino Complete Enterprise Option (CEO) bundle. Normally, Lotus products require separate entitlements to be purchased for server products (such as Domino Enterprise) and client products (such as Lotus Notes). CEO bundles however are licensed based on the number of end users only – the supporting server software is “included” in the license.
For some organizations this may provide a cost-effective alternative to the client-server license model. However, keep in mind that certain rules apply when using CEO bundles. One of the requirements when using CEO bundles is that each employee in the organization with desktop or laptop access needs to be licensed. Other license metrics There are many more license metrics than the ones mentioned above, some common ones are:.
Resource Value Unit (RVU): This license metric is used for some Tivoli products (in particular Tivoli Netcool). Rather than licensing the capacity of the servers being managed (in PVUs), other “types” of resources or devices (such as switches, printers, etc.) also need to be licensed. The specific rules for calculating the required RVUs differ for each product to which this license metric is applied. Determining the deployment quantity for products with this license metric is usually quite complex as it requires a deep understanding of the environment being managed. Millions of Service Units (MSU): This license metric is used solely for IBM software which is installed on the IBM mainframe, or zSeries. Products need to be licensed based on the total MSU capacity of each zSeries machine where the product is installed.
Concurrent Session: This license metric is used for some Informix products. It requires that the maximum number of concurrent sessions connecting with the product at any time be licensed. An important difference between the Concurrent User and the Concurrent Session metric is that a single user can start multiple sessions. That is, a single user creating 10 concurrent connections to the Informix product would count as one Concurrent User, but ten Concurrent Sessions.
Again, software which limits or measures concurrent usage can help to prevent peaks that exceed license entitlements. Virtualization/Partitioning In current IT environments organizations are increasingly using virtualization (such as VMWare) and partitioning (such as LPARs) to optimize the use of system resources and allow for flexible sharing of hardware capacity. However, this development has also introduced new complexities in the area of software licensing.
The IBM licensing term for virtualization/partitioning is sub-capacity licensing, and it applies to PVU-based products. In previous years, many IBM products were not eligible for sub-capacity licensing. This means that even if certain software was only installed on a single partition, the full capacity of the underlying hardware needed to be licensed (so-called full-capacity licensing). Since April 2009, IBM has expanded the list of products which are eligible for sub-capacity licensing to almost all IBM products.
However, a customer may only apply sub-capacity licensing when certain conditions are met. First of all, a sub-capacity agreement must be signed with IBM. Customer must then deploy the free IBM License Metric Tool to monitor sub-capacity usage. Lastly, sub-capacity licensing is limited to certain listed eligible processor technologies and virtualization technologies. It is important to remember that in case sub-capacity conditions are not met, the full-capacity rules apply. Customers who do not take sub-capacity counting rules into account therefore risk considerable underlicensing. Creating an overview of IBM software deployment Now that we know how the most common license metrics work, what is the best method of creating an overview of deployed IBM software?
Unfortunately, there is no common approach which applies for all IBM products. Unlike some other software vendors, most IBM product installations are not linked to a specific license key. This means that there are usually no technical limitations to deploying more IBM software than is licensed. This allows for flexibility and scalability, but may create some headaches when trying to match licenses with deployment. In some cases, using software discovery tools on desktops and servers can help to create an initial overview of installed IBM software. IBM products often also include a product console through which software deployment can be managed.
Depending on the product and license metric, it is often possible to extract useful information from these product consoles for licensing purposes. In order to calculate PVUs, it is essential that the correct hardware details are captured through scanning tools or a central CMDB (in small environments it may be feasible to collect this information manually). Technologies such as hyperthreading, virtualization, clustering etc.
Sometimes lead to the hardware details being captured inadequately. Make sure to double-check any hardware details which are used to calculate license quantities. Wrap up As discussed in this guide, there are many aspects to consider when dealing with IBM software licenses. IBM has a wide array of products with different licensing rules and metrics. The topics discussed in this article can help to get acquainted with the general rules and common issues. When dealing with IBM software licenses in your organization, it is best to collect further information specific to your IBM products and IT environment. In case you have detailed questions concerning IBM software licensing, don’t hesitate to ask help from software licensing expert.
This Quick Guide to IBM Licensing has been provided by of. Koen is an entrepreneur in the area of Software License Management and Software Asset Management. From 2006 to 2009, he performed more than 60 onsite software license compliance inspections throughout Europe, on behalf of international software vendors.
He currently performs software license optimization projects at end-user organizations. This Quick Guide is available in PDF format – Simply subscribe to our free newsletter to receive a free copy instantly. About Martin Thompson Martin is owner and founder of The ITAM Review, an online resource and community for worldwide ITAM professionals. Martin is also author of the book, a book that describes how to get started and make a difference in the field of IT Asset Management. On a voluntary basis Martin is the Chief Agitator at the Campaign for Clear Licensing, a contributor to ISO WG21 which develops the SAM International Standard ISO/IEC 19770 and board member of Free ICT Europe which supports the ICT secondary market. Learn more about him and connect with him on.
The Employee User Value Unit (EUVU) license metric is available for a select group of IBM products, including some which formerly belonged to FileNet. The main difference with the Authorized User Value Unit (AUVU) is that with the EUVU license metric, you are required to buy licenses for all employees (including agents/contractors), whether or not they are able to use the product. The advantage of EUVU is that it is generally less expensive than the AUVU license. When faced with a choice between EUVU and AUVU licenses, consider the following: – Do all or almost all employees (and agents/contractors) use the IBM product concerned? If so, the EUVU metric is probably a better choice for your organization.
– Is the total employee headcount of your organization considerably higher than the number of users of the IBM product? Then the AUVU metric may be a better choice. – Make sure to consider any parent or subsidiary companies, as these may need to be included in your employee count. – It is not permitted to mix AUVU and EUVU licenses for the same product.
It is best to review the licensing terms and conditions of the IBM product concerned for more information on this subject. The licensing terms and conditions will also include a Value Unit license conversion table, which indicates the amount of EUVUs required per Employee User. The more EUVUs you buy, the fewer EUVUs you need to buy per user (the same applies for the AUVU license metric). Good explanation. Be extremely careful in dealing with IBM, however.
If you have ND IBM will charge for the units on the Administration Console, even if that server is running no applications. Versions prior to 7 had different licensing terms, but IBM may not honor these. There is no redundancy for the Admin Console under ND, so if it is lost, so is your ability to effectively administer the sites. IBM says the software is so improved that redundancy is not needed (paraphrasing IBM documentation and support). The solution for a lost admin console is to start the application servers with “nanny processes.” Nice. And virtual may not save you on this one.
Ibm Db2 Work Group Server Edition
ND is extremely overpriced software and licensing is handled through sales agents who may not understand the product. Bottom line, do not consider WAS ND, or better yet, build on something with consistent and reasonable licensing terms.