A Better Install

© 2011 IBM CorporationOctober 4, 2010

A Better Install

Scott Pickett – WW Informix Technical SalesFor questions about this presentation contact: [email protected]

© 2010 IBM Corporation2

What's New for Informix 11.70 Installation

New integrated software bundle for Server, CSDK, Iconnect, JDBC.

Unified look and feel for all platforms (Unix/Linux, Windows, MacOS).

Multiple installation modes:– Silent (with response file).– Console (for non-graphic environments).– GUI

Inclusion of Spatial and TimeSeries extensions on most platforms.

Instance configuration wizard that offers tuned instance. Reduced click count for most typical installations. More autonomic features: user/group creation, server

discovery, port conflict detection.


Spatial Data Extension

Installs as part of the server when “Database extensions” is chosen in the feature tree.

When user attempts to use one of the types or functions associated with it (like create a table with a ST_Point), the extension will be registered automatically in that database.

Available on most Unix/Linux and Windows platforms:– Linux (32/64 Intel/AMD – not PowerPC or Z platforms)– HP (PA-RISC and IA64)– AIX– Solaris (Intel and Sparc)– Windows– MacOS


TimeSeries Data Extension

Installs as part of the server when “Database extensions” is chosen in the feature tree.

When user attempts to use one of the types or functions associated with it (like create a table with a timeseries), the extension will be registered automatically in that database.

Available on most Unix/Linux platforms:– Linux (32/64 Intel/AMD)– Z-series– HP (PA-RISC and IA64)– AIX– Solaris (Sparc)– Windows (32bit)


Getting Started with Informix 11.70


Types of Installation

Typical– Installs all server features, ClientSDK, JDBC.– By default, creates a server instance based on standard configuration

file (onconfig.std):• Server instance creation can be suppressed by unchecking the Create

Server Instance box on the Installation Type screen.– Minimum number of “clicks” to begin the installation.

Custom– Feature tree presented for customization of desired server features for

all products (Server, ClientSDK/IConnect, JDBC).– Server instance creation optional by default.– Widest variety of installation/configuration options.


Installation Type


Typical Installation Panel flow

OverviewOverviewInstallation

Type

Installation

Type

License

Accept

License

Accept

Password

(Windows)

Password

(Windows)

Installation

Summary

Installation

Summary

Install

Location

Install

Location


Feature Tree


Custom Installation Features User authentication (Windows)

– Local SYSTEM account / user informix.– Domain installation options.

Role Separation– Configure users and groups for various tasks (Windows).– Configure groups (Unix/Linux).

Instance Creation– Default instance based on onconfig.std

• Abbreviated set of screens for basic information and connectivity options.– Custom instance with configuration wizard:

• Configure number of processors, workload, memory, disk utilization, connectivity.


Server Instance Creation Create a simple instance – default parameters.

Create a “tuned” instance - customize parameters:– Single or multiple processors, custom memory footprint.– 6 different dbspaces are created on initialization

• Root (based on tuning parameters).• Physical Log (based on tuning parameters).• Logical Log (based on tuning parameters).• Data (user configured).• Smart Large Object (32MB) – (user configured).• Temporary (user configured).

• Opportunity is presented to adjust the sizes and locations of the dbspaces during “Space Review”.


Server Instance Creation

Factors that go into tuning:– Processor speed.– Number of processors.– Total memory allocated to Informix by user.– I/O speed on selected volume(s).– Type of instance (DSS/OLTP).– Concurrent user counts (transactional and decision support).– Transaction support by application.– Recovery time objective for OLTP applications.

Can initialize the default or custom instance created as part of the install process.


Server Instance Creation Notes Parameter specification:

– CPU, Memory, Disk can be allocated either by absolute value (1 cpu or 256MB of memory/disk), or by percentages of those resources. These can be used in combination with each other, i.e. absolute number of cpu combined with percentage of memory/disk.

– Disk speed matters when sizing root, physical log and logical logs. Both logical and physical logs are created in the root space initially and then moved to separate spaces in a later step, so you will see a larger root space created.

Recovery Time Objective(RTO) can greatly influence the logical and physical log size.


Default Server Instance Creation


Customized Instance Configuration Wizard


Custom Instance - Disk Configuration


Custom Instance - Systems Resources Usage (Processor/Memory)


Custom Instance - Connectivity


Custom Instance - Disk Space Allocation Summary


Installation Summary


Install Future Roadmap Installer Translation into 17 languages. Instance Manager replacement. Integration with Native Install Technologies (RPM, Solaris

Package, HPUX Depots, etc):– Instead of installation, output would be as one of these native

installation package types for easier deployment.

Publication of Installation/Deployment API. Enhancement of Configuration Wizard:

– Flexible GRID.– Integration with Storage Provisioning.


Questions?


Private Instance/Install

Scott Pickett – WW IDS Technical SalesFor questions about this presentation contact: [email protected]


Private Instance/Server (non-root install) – Intro

Also known as the non-root install. Allows to install and create an Informix instance without needing

root privileges on Unix/Linux. Makes it even easier for Informix to be exploited as the

enterprise-class embedded database it is:– To go embedded or integrated into ISV/OEM software and

appliances.– Allows Informix to be deployed and configured in Unix/Linux

systems where there is limited access to root privileges. When Informix is installed this way, by an unprivileged user, the

installation is known as a Private server/instance.– Compared to the known or traditional Standard software installation

and server deployment, which is performed by a privileged user (root).


Private Instance/Server – Installation (1)

Informix will allow:– To be installed by a user other than root.– To run the database server without informix user or group defined.

Internally, the name ‘informix’ continues to be used as the owner of the system catalog:– But informix will not have special privileges on a private server

Install of a Private server exists in interactive and silent modes. The install program automatically recognizes whether the user

running the installer is a privileged user (root) or not– For anyone other than root, Informix installer will ask for

confirmation from the user and proceed with a private installation.


Private Instance/Server – Installation (2)

In silent installations, you can use the following option to ids_install command to perform a private install:

./ids_install -i silent ... -DUNIX_INSTALLTYPE_SELECT=PRIVATE

The install program needs the target Informix install directory:– Not all users have privilege to create/use the default Informix target

installation directory, /opt/IBM/informix, so a target install directory is needed.

– Needs to be a directory the user has full access to create and use.

The owner of the private instance and its files will be the user’s id of the user who installed Informix:– This user is the DBSA (Database Server Administrator) of the

server.


Private Instance/Server – Operation (1)

When a private server accesses files…– it will do so as the owner of the private instance, not as

root/informix.

The database server executables…– will not be owned by root or informix, but by the user who installed

the private server.

A private Informix server will run with lower privileges and in a more restricted environment than a standard install.

Informix functionality currently not supported in Private server deployments: – MACH clusters (on HDR, RSS, SDS), Enterprise Replication (ER),

I-Star (distributed connections and queries), ON-BAR, Role separation, and administration via OAT.


Private Instance/Server – Operation (2)

Not guaranteed to be able to authenticate through the O/S. Therefore:– A new Informix internal users authentication mechanism.– Users and their passwords are defined and maintained in Informix’s

sysuser database.– Internal authentication is done by Informix, verifying the passwords.

Internal users authentication via SYSUSER database– sysintauthusers and other tables in sysuser are populated using

new SQL commands– The DBSA can invoke:

• CREATE USER to add the individual users that will be internally authenticated in Informix.

• GRANT ACCESS to allow users to access a private server with connect, resource or DBA access.

• REVOKE ACCESS to revoke access or privilege from an Internal user.• RENAME USER allows to rename an internal user in Informix.• ALTER USER command with ACCOUNT LOCK/UNLOCK clause to

lock/unlock an Internal user.• DROP USER to remove an internally defined user in Informix.


Questions?


RPM for Linux



RPM image deployment for Linux - Intro

Prior to Informix 11.70.xC2…– Ability to “output” an Informix installation as a functional install

• Response file generated out of a “recorded” template installation.• Ability to replicate same or similar install across multiple computers.• Simplifies large deployments.

Now, on Linux:– Informix allows to “output” an on-going installation as an RPM

image, rather than as a functional installation.– The new RPM image feature simplifies the redistribution of an

Informix installation across multiple Linux machines.– Offers additional options to remove products, embed the database

server or customize multiple deployments on Linux in an easier way.


RPM image deployment for Linux – Generate image

Informix install’s first screen will change if the installer detects Linux and rpmbuild, to display the third RPM install option.

If proper prerequisites are not present, the third option (RPM image for redistribution) will not appear:– Still the choice of doing a standard installation or a “legacy” installation

(-DLEGACY), which extracts the files and leaves in a separate file the permissions settings needed to be done by a privileged user.



Feature integrated with the private (non-root) installation:– RPM images could be generated out from a “private” installation.

Installer will ask for location to “install” the product, and present the product selection screen with all the options to select / deselect in an Informix custom installation:– You can reduce the size of the distributable RPM image.

Finally, a summary screen presents all the bundled products and functionality, and the output directory:



After “install” is clicked, the installation program will start to generate the RPM image, displaying a “Creating RPM image”

And the rpm image file is generated in the output location:– Example: informix-11.70.FC2-0.x86_64.rpm

An output RPM image has the following name format: informix_version-release.architecture.rpm Where:– version – Indicates the full version of the package. (e.g. 11.70.FC2)– architecture – x86 (for 32bit Linux x86) or x86_64 (for 64bit AMD)– release – Normally will be 0


Deploying an Informix RPM image on a machine

To install the RPM image produced before (as root):

rpm -i informix-11.70.FC2-0.x86_64.rpm –prefix <your installation location>

– If –prefix is not provided, the default is /opt/IBM/informix

Silent mode installation is supported through the parameter UNIX_INSTALLTYPE_SELECT, passed to the install program:– “RPM” for standard root-based installation/RPM distribution– “RPM_PRIVATE” for private installation


Questions?


Logo

A Better Install

Documents

Transcript of A Better Install