Skip to main content

ITIL Refresh Project / ITIL Version 3 - Middleware News

A six month project was launched by the 'owners of ITIL', Office of Government Commerce (OGC) based in the UK, on the 8th November 2004, to define the scope of and development plans for a refreshed version of ITIL best practice guidance. The OGC from January through to March 2005 consulted and collected opinions from ITIL users, educationalists and vendors from around the world. Having analysed the feedback the subsequent scope of the ITIL Refresh project was founded based upon areas where high degrees of consensus were found.

The development stages started in August 2005 and are planned to be completed in December 2006, with the publication of the 'core' intended for February 2007.

The 'core' represents the generic principles of ITIL guidance, but has been expanded to incorporate the life-cycle stages of Service Management. In addition to the 'core' publications will be 'complementary guidance' and 'value added products to assist organizations in the context of:

* Business environments
* Economic conditions
* Organizational strategies

Five volumes will comprise of the 'core' publications:

* Service Strategy (SS)
* Service Design (SD)
* Service Transition (ST)
* Service Operation (SO)
* Continual Service Improvement (CSI)

The January to March 2005 consultation identified the following finding, which have moulded and shaped ITIL Version 3:

* Consistent structure and navigation
* Preserve key concepts - no radical changes to Service Support and Service Delivery
* Reflect the service life cycle - strategic to operational as a Service Management framework
* Organizational structures and models for Service Management
* Dealing with cultural issues
* Refer to other best practices
* Business case examples, case studies, templates, implementation work packages
* ITIL in multi-sourced environments
* Alignment to other frameworks
* Scalability
* Remain non prescriptive
* Return on investment
* Quality of authoring
* Improved standard terms and definitions
* Address IT governance
* Executive-level awareness and marketing
* Evaluation guidance for tools
* Key performance metrics
* Improved self-assessment
* Reduce the core and increase ancillary guidance
* Integrated process model
* Quick wins in each process


ITIL Version 2
Service Support
Service Desk
Incident Management
Problem Management
Change Management
Release Management
Configuration Management
Service Delivery
Service Level Management
Availability Management
Capacity Management
Financial Management
IT Service Continuity Management
ITIL Version 3
Core Publications

Service Strategy (SS)
Financial Management
Service Design (SD)
Service Level Management
Capacity Management
Availability Management
IT Service Continuity Management
Service Transition (ST)
Change Management
Configuration Management
Release Management
Incident Management
Problem Management
Service Operation (SO)
Change Management
Configuration Management
Release Management
Service Desk
Incident Management
Problem Management
Capacity Management
Availaibility Management
Financial Management
IT Service Continuity Management
Continual Service Improvement (CSI)

Comments

  1. ITIL has recently undergone a major and important refresh project. The upgrade of ITIL from version 2 (2000) to version 3 (2007) included some intensive changes.One of the most visible changes was the subtle change of name: from "The IT Infrastructure Library" to "ITIL Service Management Practices". This itself reflected ITIL’s evolution, implying a broader scope. Indeed, the whole approach to version 3 is more holistic, value based and business focused.ITIL V3 is a new version of the IT Infrastructure Library has many new subjects closely related to business operations. ITIL V3

    ReplyDelete

Post a Comment

adsrerrapop

Popular posts from this blog

IBM Websphere MQ interview Questions Part 5

MQ Series: - It is an IBM web sphere product which is evolved in 1990’s. MQ series does transportation from one point to other. It is an EAI tool (Middle ware) VERSIONS:-5.0, 5.1, 5.3, 6.0, 7.0(new version). The currently using version is 6.2 Note: – MQ series supports more than 35+ operating systems. It is platform Independent. For every OS we have different MQ series software’s. But the functionality of MQ series Default path for installing MQ series is:- C: programfiles\BM\clipse\SDK30 C: programfiles\IBM\WebsphereMQ After installation it will create a group and user. Some middleware technologies are Tibco, SAP XI. MQ series deals with two things, they are OBJECTS, SERVICES. In OBJECTS we have • QUEUES • CHANNELS • PROCESS • AUTHENTICATION • QUERY MANAGER. In SERVICES we have LISTENERS. Objects: – objects are used to handle the transactions with the help of services. QUEUE MANAGER maintains all the objects and services. QUEUE: – it is a database structure

IBM Websphere MQ Reason code list / mq reason codes / websphere mq error codes / mq error messages

Reason code list ================= The following is a list of reason codes, in numeric order, providing detailed information to help you understand them, including: * An explanation of the circumstances that have caused the code to be raised * The associated completion code * Suggested programmer actions in response to the code * 0 (0000) (RC0): MQRC_NONE * 900 (0384) (RC900): MQRC_APPL_FIRST * 999 (03E7) (RC999): MQRC_APPL_LAST * 2001 (07D1) (RC2001): MQRC_ALIAS_BASE_Q_TYPE_ERROR * 2002 (07D2) (RC2002): MQRC_ALREADY_CONNECTED * 2003 (07D3) (RC2003): MQRC_BACKED_OUT * 2004 (07D4) (RC2004): MQRC_BUFFER_ERROR * 2005 (07D5) (RC2005): MQRC_BUFFER_LENGTH_ERROR * 2006 (07D6) (RC2006): MQRC_CHAR_ATTR_LENGTH_ERROR * 2007 (07D7) (RC2007): MQRC_CHAR_ATTRS_ERROR * 2008 (07D8) (RC2008): MQRC_CHAR_ATTRS_TOO_SHORT * 2009 (07D9) (RC2009): MQRC_CONNECTION_BROKEN * 2010 (07DA) (RC2010): MQRC_DATA_LENGTH_ERROR * 2011 (07DB) (RC2011): MQRC_DYNAMIC_Q_NAME_ERROR * 2012 (07DC) (RC201

IBM WebSphere MQ – Common install/uninstall issues for MQ Version on Windows - Middleware News

Creating a log file when you install or uninstall WebSphere MQ WebSphere MQ for Windows is installed using the Microsoft Installer (MSI). If you install the MQ server or client through launchpad , MQPARMS or setup.exe , then a log file is automatically generated in %temp% during installation. Alternatively you can supply parameters on the installation MSI command msiexec to generate a log file, or enable MSI logging system-wide (which generates MSI logs for all install and uninstall operations). If you uninstall through the Windows Add/Remove programs option, no log file is generated. You should either uninstall from the MSI command line and supply parameters to generate a log file, or enable MSI logging system-wide (which generates MSI logs for all install and uninstall operations). For details on how to enable MSI logging, see the following article in the WebSphere MQ product documentation: Advanced installation using msiexec For details on how to enable system-w