managing it complexity triole
TRANSCRIPT
Managing IT Complexity
TRIOLE
All Rights Reserved. Copyright © FUJITSU 2004
Technical White Paper on Fujitsu IT Platform for Japanese Market
Edition 2 September, 2004 Fujitsu Limited
All Rights Reserved. Copyright © FUJITSU 2004
TRIOLE Technical White Paper
Preface
This document is a white paper that contains information about TRIOLE in Japanese
market, Fujitsu’s comprehensive IT infrastructure concept and vision that aims to
significantly strengthen integration capabilities and product offerings in order to
optimize customer IT systems, reduce cost and enhance capabilities.
Fujitsu hopes that this document will enlighten customers and assist them to better
plan, develop, implement and manage their IT systems and resources for the best
returns on investment in the future.
September, 2004
Fujitsu Limited
Trademarks or registered trademarks in the document are the property of their re-
spective owners.
Future direction and product planning mentioned in the document are subject to
change without notice due to changes in business environment and technical trends.
For more information, visit us on the web at http://triole.fujitsu.com.
Fujitsu Limited; Platform Integration Solution Center; TRIOLE Promotion Group
TRIOLE Technical White Paper
All Rights Reserved. Copyright © FUJITSU 2004 i
Contents
Chapter 1 Introduction to TRIOLE ............................................................................................................................................................................... 1
1.1 Challenges due to Changes in Business and IT Environments .................................................................................................................................. 2
(1) Business Revolutions in Society and Industry
(2) Changes in IT Environments
(3) Current IT System Status and Issues
1.2 Goal of IT System by Fujitsu ........................................................................................................................................................................................ 3
(1) Business Agility (Agility)
(2) Rapid Development and Deployment of Business Applications (Efficiency)
(3) Stable and Reliable Systems and Reduced TCO (Continuity)
(4) Efforts for the Environment
1.3 TRIOLE realize a New Platform .................................................................................................................................................................................... 4
(1) Fujitsu’s Approach
(2) Efforts for TRIOLE
1.4 Enhancement of the Basic Products ............................................................................................................................................................................ 7
(1) Efforts for Enhancement of the Basic Products
(2) Application of Core Technology to Basic Products
1.5 Platform Integration Modeling ...................................................................................................................................................................................... 8
(1) Efforts for Platform Integration Modeling
(2) Templates of IT Infrastructure
Chapter 2 Toward Business Agility (Agility) .............................................................................................................................................................. 11
2.1 Aim and Concept of Service-Oriented Integration .................................................................................................................................................... 12
(1) Adapt quickly to changes in the business using the existing IT assets
(2) Concept of Service-Oriented Integration
2.2 Business Process Integration - Significantly Reduced Man-hours by XML Hub - ..................................................................................................... 15
(1) Information sharing hub - Sharing of information between various customer systems -
(2) Business process hub - Business process integration -
2.3 Information Integration - Content Management, High-speed Search and Business Intelligence - .......................................................................... 18
(1) Dynamic collection of contents
(2) High-speed search of XML contents
(3) Real-time analysis of dispersed information
2.4 People Integration - Knowledge Sharing, Know-how Accumulation and Ubiquitous Network - .............................................................................. 19
(1) Technologies Supporting People Integration
2.5 Models for System Development using Service-Oriented Integration ...................................................................................................................... 21
(1) Model for development of business application integration system
(2) Model for development of information integration system
(3) Model for development of knowledge integration system
(4) System development model ‘Route Sales’ that supports Ubiquitous Network
2.6 Collaboration with Global Servers .............................................................................................................................................................................. 24
(1) Integration with Business Process Integration
(2) Integration with Information Integration
(3) Integration with People Integration
Chapter 3 Toward Rapid Development and Deployment of Business Applications (Efficiency) .......................................................................... 27
3.1 Concepts and Effectiveness of Framework ............................................................................................................................................................... 28
(1) Extends the applicability of a framework to include the development of mission-critical systems
(2) Building Block System
(3) Rapid designing of customer system and standardization of development style
3.2 Application Framework ............................................................................................................................................................................................... 30
All Rights Reserved. Copyright © FUJITSU 2004
TRIOLE Technical White Paper
ii
Contents
3.3 Application Control Base/Operation Control Base .................................................................................................................................................... 31
(1) Application control base
(2) Operation control base
3.4 List Infrastructure ........................................................................................................................................................................................................ 32
(1) Features of List Infrastructure
(2) Speeding up development
(3) Results of introduction
Chapter 4 Toward Stable & Reliable Systems and Reduced TCO (Continuity) ...................................................................................................... 35
4.1 Toward Optimization of Customer Entire System ...................................................................................................................................................... 36
(1) Efforts for stable & reliable operation at component and system levels
(2) Efforts for stable & reliable operations at the product level
(3) Efforts for Entire System
4.2 Toward Autonomous System Infrastructure ............................................................................................................................................................... 38
(1) Structure of Autonomous System Infrastructure
(2) Grasping resource configurations and visualization of failures
(3) Approach for dynamic resource allocation
(4) Application to products from Other Companies
4.3 Servers and Middleware-based Optimization of Entire Customer System ............................................................................................................... 41
(1) Enhancing the continuation of operation
(2) Increasing the efficiency in operation
4.4 Enhancing Storage Operation Monitoring Functions ................................................................................................................................................ 44
(1) Grasping Allocation of resources and visualization of failures and impacts
(2) Expansion of the range of technology from storage SLM to IP storage
(3) Provisioning based on virtual storage pools
4.5 Network-based Optimization of Entire Customer System ......................................................................................................................................... 47
(1) Stable communication - Sharing and optimum allocation of resources -
(2) Continuous operation - Visualization of failure -
(3) Simple network operations management - Autodiscovery of configuration resources -
(4) Integration of system front functions
4.6 Integrated Management and Autonomous Protection to Ensure Security ............................................................................................................... 50
(1) Common security measures that use software products as their core
(2) Providing systems with security measures in place through Platform Integration
(3) Providing ‘automated’ and ‘integrated’ security measures
4.7 Stable and Reliable Systems through its Life Cycle .................................................................................................................................................. 52
(1) Reduction in the workload of the customer systems operation manager
(2) Enhancement of the support infrastructure
Chapter 5 Platform Integration ................................................................................................................................................................................... 55
5.1 The goal of Platform Integration ................................................................................................................................................................................. 56
5.2 Pi Templates ............................................................................................................................................................................................................... 56
(1) Pi Template features
(2) Systems requirement and Pi Templates
5.3 Contiguration of Pi Templates .................................................................................................................................................................................... 57
(1) Basic Templates
(2) Line up of Basic Templates
(3) Combination Templates
5.4 Challenge to Open System ........................................................................................................................................................................................ 60
5.5 Easy-to-use Platforms with System Lifecycle ............................................................................................................................................................ 60
TRIOLE Technical White Paper
All Rights Reserved. Copyright © FUJITSU 2004 1
Chapter 1
Introduction to TRIOLE
All Rights Reserved. Copyright © FUJITSU 2004
TRIOLE Technical White Paper
2
Chapter 1 Introduction to TRIOLE*1
The IT infrastructure should enable enterprises to quickly adapt to changes in their business,
develop and deploy business applications rapidly, and operate stable and reliable systems all
the while reducing their Total Cost of Ownership (TCO).
Fujitsu will offer server, storage, network and middleware products using the core technolo-
gies of automation, virtualization, and integration. It will also integrate those products into a
platform and provide it to customer to help them optimize their IT infrastructure and realize
the best returns on their investments in that infrastructure.
1.1 Challenges due to Changes in Business and IT Environments
The business environment and IT systems are experiencing a significant change and continuous evolution. In addition,
with the expanding investments being made in IT, the evaluation of its effects is under close scrutiny by management.
Under such an environment, an urgent IT system revolution is strongly desired to prevent missing out on any business
changes. Considered among a so-called revolution are the effective use and continuation of existing IT resources, the
shortened lead-time to system development and startup of business, the enlarging of sales chances and the stable
operation and lower costs of the system.
(1) Business Revolutions in Society and Industry
Today’s business environment continues to surprise with its increasingly influential changes. The integration and/or the
diversification of enterprises, and the reorganization of global industries are accelerating as a result. To correspond to
these dramatic changes in our business environment, resources that had been developed for specific use in divisions
and for specific uses have been expanded company-wide, and IT systems (overall company integration) for improved
business processes are notable examples. Furthermore, there are also advancements such as business integration and
mutual service sharing between enterprises and linking of basic businesses, through M&A and business alliances in an
effort to create new business.
Company-wide Integration of Customer Information, Sales Support, Finance and Accounting Process Systems
(2) Changes in IT Environments
Environments that employ IT systems are acceleratingly changing because of technical revolutions. Not only industry
activities, but also society and life in general are advancing toward even higher IT use.
Expansion of Service Selections, and One-stop Services using Web Services
Expansion of Services using Broadband Network and Ubiquitous Network*2
(3) Current IT System Status and Issues
As the multi-vendor supplied system has evolved, special purpose systems such finance, account, and HR have been
implemented on a departmental basis. As a result, IT systems within enterprises are distributed and increasingly com-
plicated. Moreover, these systems, which are now networked and today comprise a large complex enterprise system.
Accompanying that, new issues are also becoming notable. There is an urgent need for IT systems to handle these new
issues.
There is demand for systems that can flexibly support changes in business environments.
1.Continue effective use of current assets and organically integrate entire IT system
2.System that can fully utilize IT investments
*1 TRIOLE A German word meaning triplet. It is applied to conjure the image of a system wherein a variety of products, such as servers, storage, networks and middleware, and
services are in harmony.
*2 Ubiquitous Network A network that can be access from any devices, including computers or cellular telephones, anywhere and at anytime.
TRIOLE Technical White Paper
All Rights Reserved. Copyright © FUJITSU 2004 3
Customers are demanding speedier system setup times
1.Establish new methods for realizing short-term system development and high reliability
2.Early identification of causes of trouble
3.Simplified system configuretion changes (addition, expansion)
1.2 Goal of IT System by Fujitsu
The universal mission of an enterprise in deploying IT systems is to obtain the greatest possible value from the invest-
ment. As a total solution provider, Fujitsu also shares this view on IT systems.
The IT system as envisioned by Fujitsu uses the leading technologies to promote the IT revolution of industry and to
solve the issues facing the current IT systems, and Fujitsu aims to develop and deploy business applications rapidly,
provide stable and reliable systems operation and reduction in TCO while adapting customers to changes in their busi-
nesses through the life cycle of their IT systems. Fujitsu’s TRIOLE achieves that goal.
‘TRIOLE’ answers the following customer requests.
- ‘Business agility’ through a highly flexible IT infrastructure
- ‘Business efficiency’ through highly cost effective solutions
- ‘Business continuity’ through knowledge relating to mission critical that Fujitsu has cultivated
Especially in Japanese market, TRIOLE emphasizes following aspects to answer the requests of our customers for
‘business agility’, ‘business efficiency’, and ‘business continuity’.
Business Agility (Agility)
Rapid Development and Deployment of Business Applications (Efficiency)
Stable and Reliable Systems and Reduced TCO (Continuity)
(1) Business Agility (Agility)
TRIOLE enables the customer’s existing systems to quickly adapt to changes in business and transform them into an IT
system that is holistically optimized. Furthermore, by supporting Web services and ubiquitous networking, TRIOLE aims
to help customers significantly expand business and improve productivity.
(2) Rapid Development and Deployment of Business Applications (Efficiency)
TRIOLE aims to enable customers develop and deploy high quality business systems rapidly using a system develop-
ment framework. Fujitsu offers predefined control logic components as part of the framework. This enables rapid
development of highly reliable applications as well as the reuse of those applications.
(3) Stable and Reliable Systems and Reduced TCO (Continuity)
High reliability by the products will be attained through enhanced reliability at the module and device level, and applica-
tion and strengthening of autonomous control for each product. Furthermore, by providing Autonomous System Infra-
structure that encompasses a multiple of systems, the overall system will be optimized. Such an overall quality chain
realizes stable system operation and reduced operating costs.
(4) Efforts for the Environment
‘TRIOLE’ contributes to reduced consumption of resources and energy by developing with consideration to the environ-
ment at the module and product level, and providing an IT solution that is optimized for the entire system.
All Rights Reserved. Copyright © FUJITSU 2004
TRIOLE Technical White Paper
4
1.3 TRIOLE realize a New Platform
It was easy to guarantee system compatibility and uniformity for system development on main frames because of the
use of a single platform and limited products. However, that leads to the problem of not being able to exceed the single
platform range and to freely select good quality products. Open system that allow the freedom of selection (best of
breed) of good quality hardware and software products and develop systems are becoming mainstream because of their
further advancements.
However, while open system have the benefit of being able to employ the latest products, systems are developed by
collecting together different types of products which makes it difficult to guarantee the compatibility and uniformity
between products. Therefore, to enable the stable operation of a system, it is necessary to supplement links between
products according to their application. This translates into an unclear boundary between applications and platforms,
which makes it difficult to develop new business or combine new products.
In consideration of these issues, Fujitsu is providing an integrated platform that allows the freedom of product selection,
which is a hallmark of open system and that offers short-term development of the platform and stable operation. With an
integrated platform, the links between products are strengthened and by verifying the compatibility of the platform, the
same compatibility and reliability as those found in main frames can be guaranteed.
Fig. 1-1 New Platform
Compatibility
Freedom ofchoice
Tight linkage
between
products
Guaranteed stability of
entire system through
compatibility verification
ISV: Third party products (Software)
ApplicationApplicationApplication
I S V Middleware
Server
Network Storage I H V
Middleware
Server
Network Storage
Platform
integration
model
Mainframe
model
Open systems
model
Inte
gra
ted
pla
tform
Sin
gle
pla
tform
Ambiguous boundary between application and platform
Many product variations result in complicated configurations
Ensuring consistency with applications results in difficulty inachieving stable operation
I S V Middleware
Server
Network Storage
I H V
IHV: Third party products (Hardware)
(1) Fujitsu’s Approach
Business reform, relating to business management, and the advancements in IT technology are not necessarily synchro-
nized together. It is also thought to be difficult to synchronize business applications and platforms. For example,
reforms for changes in business and new developments are necessary for business application, and it is necessary to
provide enhancements for each product along with the advancements in IT technology for platforms.
For that reason, Fujitsu considers it important to optimize these after separating business applications and platforms (IT
infrastructure). This makes it possible to speedily support changes in customer business environments and innovations
in IT technology. Furthermore, standardization and modeling are keys to optimization of each.
In the application region, design process innovations will be realized through technologies that employ UML and XML.
TRIOLE Technical White Paper
All Rights Reserved. Copyright © FUJITSU 2004 5
This realizes ‘Enhancement of the Basic Products’ and ‘modeling of platform integration’ as ‘TRIOLE’ for an IT infra-
structure region.
Enhancement of the Basic Products
This will be achieved through servers, storage, networks and middleware and the optimization of the overall system
will be achieved through ‘linking and integration of business systems’, ‘short-term development by frameworks’, and
‘optimized control (automation) of resources’.
Platform Integration Modeling
Early development of highly reliable systems will be attained by assembling standardized and modeled platforms in
advance, using a building block method, like that of the prefabricated method used in the construction industry.
Also, through these measures, optimization for the IT infrastructure ‘TRIOLE’ will be realized for the entire system.
1-2 Fujitsu’s Approach
Breakthrough with standardization and modeling
Separation between business applications and IT infrastructure Optimization of all phases
Innovation of Application Design process
IT infrastructure "TRIOLE"
Enhancement of the Basic Products
Cooperation and integration of Business Systems
(Existing and new, people and information...)
Rapid development with framework
Highly reliability & autonomy of the resources
Modeling
Platform Integration
(Building block method)
Business Model
(2) Efforts for TRIOLE
Enhancement of the Basic Products
- Fujitsu applies the core technologies of ‘automation’, ‘virtualization’, and ‘integration’ to each platform product to
continue strengthening them. In addition, these realize compatibility and uniformity (overall optimization) of the
entire system by the mutual linking of the total system.
- By applying an open system architecture and standard specifications to products, it is possible to mutually connect
and link business applications and systems over a hetero-environment (an environment that combines hardware,
operating systems and middleware).
All Rights Reserved. Copyright © FUJITSU 2004
TRIOLE Technical White Paper
6
Platform Integration Modeling
- Modeling of know-how such as system development technology and operating technology that have been accumu-
lated over the years is provided. Also, the configuring elements of each are combined in blocks according to
function and role.
- By assembling each of these blocks using a building block method, the complexities of system development can be
hidden to provide highly reliable systems in short periods of time.
- The quality and performance of the entire system is guaranteed by standardized verification technology.
- This uniformly supports customer systems throughout the life-cycle of the system.
Fig. 1-3 Efforts for the IT Infrastructure ‘TRIOLE’
2. Platform integration modeling
1. S
tre
ng
th
en
ing
ba
sic
pro
du
cts
ServerStorageNetworkMiddleware
Optimization of entire customer system
Techniques for developing & deploying
and operating customer’s system
Automation, Virtualization
and Integration
Grid Computing
Grid computing for business use is now beginning. Moreover, in the past several years, its use has been accelerating.
The biggest value of grid computing for business is the tie-up of the recent advancements in IT technologies (CPU,
storage, networks) to business management, and has the potential of dramatically increasing business management
ability to correspond to changes in a variety of environments. It is the mission of Fujitsu to contribute to customer
business through IT. Grid computing is the core technology of TRIOLE and a key realize this mission.
Open system
The support of open system architecture, open source and standardized specifications, accompanying the globaliza-
tion and diversification of company activities, has an important position. Fujitsu is actively undertaking efforts to
employ open system architectures and open sources and to participate in standardizing organizations. Struts, eclipse,
SOAP, UML, Linux, IPv6, and OGSA are examples.
TRIOLE Technical White Paper
All Rights Reserved. Copyright © FUJITSU 2004 7
1.4 Enhancement of the Basic Products
With TRIOLE, the system foreseen by Fujitsu, through the application of the core technologies of ‘automation’,
‘virtualization’ and ‘integration’ to each platform product simplifies the links and integration of complex business sys-
tems, shortens development time and optimizes resource distribution.
(1) Efforts for Enhancement of the Basic Products
Simplified Links and Integration of a Multiple of Business Systems
Service-Oriented Integration seamlessly links a multiple of individual business systems and realizes optimization the
overall system. Also, by applying open system architectures, such as Web services, it is possible to connect and link
with a variety of third party systems.
Shortened System Development
System development frameworks realize improved productivity of developing business applications, ensured quality,
and early system development.
Fujitsu is embodying products and services as a B2.Sframework.
Optimized Resource Allocation
Autonomous System Infrastructure realizes stable operation throughout the life-cycle of the system and for effectively
using IT resources.
(2) Application of Core Technology to Basic Products
Fujitsu has conventionally taken steps to improve scalability and reliability and to alleviate complexities (such as opera-
tions, and settings for operation and policies) for each product to date. These efforts have been strengthened, and
embodied with the core technologies of ‘automation’, ‘virtualization’ and ‘integration’. The direction for future efforts for
each product will be clear. In the future, with a base of strengthened optimization of each product individually, links with
each product will aim for overall system optimization.
Automation
This is an optimizing technology that monitors hardware and software resources itself to continue operations through
self-recovery without affecting business, for each condition (such as hardware failures or insufficient resources).
Virtualization
By separating or concentrating either one or a multiple of resources into logical units, they can be used by the user.
This technology is for effective use of physical resources, high reliability (such as substituting devices when failures
occur), and for simplifying maintenance (expanding, changing removing).
Integration
This is a technology for integrating a multiple of system businesses and data to create new value. Also this is a
technology that batches together a multiple of devices (hardware such as servers and storage) for control to simplify
operation management.
All Rights Reserved. Copyright © FUJITSU 2004
TRIOLE Technical White Paper
8
1.5 Platform Integration Modeling
With TRIOLE, to overcome the problems associated with open system, we integrate our products (servers, storage,
networks and middleware) and superior third party products that are known in the market while ensuring uniformity and
compatibility over the entire system. This is what is known as platform integration.
(1) Efforts for Platform Integration Modeling
‘Platform integration’ as promoted by Fujitsu standardizes platform development work, and models platforms for elimi-
nation of complexities. This enables the development of high quality platforms in an open system in a short time and
strives for stable operation. The configuring elements are strictly selected. A patterned and uniform ‘platform integra-
tion’ greatly contributes to early development of an IT system, stable operation and operation monitoring.
Fujitsu will support customer business system maintenannce and expansion, by changing the system as required by
changes in business and following increased business volume.
(2) Templates of IT Infrastructure
Modeling of system development technology that has been accumulated to date and know-how eliminates the complexi-
ties developing new systems. Also, by using standardized models for customer requirements, it is possible to attain
high quality and early stable operation.
Definition of Pi (Platform Integration) Templates
The philosophy of ‘platform integration’ is not to develop and verify each system develop of each product (servers,
storage, networks, middleware), but to divide systems into function and roles and to combine pre-verified blocks to
allow for short-term system development (using a building block method). Based on this philosophy, models and
templates are defined as templates at Fujitsu.
Fig. 1-4 Integration Using TRIOLE
ServerServerServer
Customer requirements : Quick development of high-quality & robust platform
Development Means: Patterned, building blocks and fabrication
Current Process
ApplicationsMiddlewareMiddlewareMiddleware
Product-by-product
Development &
verification from
scratch plus knowledge
isolation
TRIOLE
- Total support for customer branch business management, not simply for single products -
TemplateTemplateTemplateTemplateTemplateTemplate
Applications
StorageStorageStorage
NetworkNetworkNetwork
Pre-fablicated &
pre-verified combinations
Fast development of
stable & reliable
systems via shared
knowledge base
Customer siteFujitsuCustomer siteVendor
TRIOLE Technical White Paper
All Rights Reserved. Copyright © FUJITSU 2004 9
Pi Center
Fujitsu quickly takes up the requirements in our customers’ systems toward providing our customers with the optimum
IT infrastructure, and links with our hardware and software partners. The Pi Center plans, develops and verifies Pi
templates to allow us to provide open system in shortened times, that are durable and stable, and reduced TCO.
Fig. 1-5 Verified Platform Pi Template
Flexibility to accommodate customer requirements
Operation management
Added sequentiallyMiddleware
os
Hardware
Network
DB construction
Template D
TemplateB
TemplateC
TemplateA
Example: 3-Tier Web systemProvides optimum combination in
response to customer needs
Line-up of Templates
Internet Front
Biz Apl. program
Combination of multiple templates (building blocks) allows flexibly to meet customer needs
Provides templates for each system function including development requirements (high reliability, expandability, security)
Inte
rnet F
ron
t
Bu
sin
ess A
pl. p
rog
ram
DB
Co
nstru
ctio
n
Op
era
tion
Man
ag
em
en
t
Intra
net
Backu
p
Web
Ap
l. pro
gra
m
Web
Ap
l. pro
gra
m+
Biz
Ap
l. pro
gra
m
XM
L h
ub
XM
L d
ata
base
Web
Ap
l. Pro
gra
m
All Rights Reserved. Copyright © FUJITSU 2004
TRIOLE Technical White Paper
10
memo
TRIOLE Technical White Paper
All Rights Reserved. Copyright © FUJITSU 2004 11
Chapter 2
Toward Business Agility
(Agility)
All Rights Reserved. Copyright © FUJITSU 2004
TRIOLE Technical White Paper
12
Chapter 2 Toward Business Agility (Agility)
From Individual Point to Whole Holistic Optimization---- Service-Oriented Integration Increases
Asset Value.
Service-Oriented Integration enables existing systems to adapt quickly to changes in customer’s
business and develops an optimum IT system by utilizing the existing IT assets.
It addresses the enlarging ubiquitous environment, and rapidly achieves restructuring and
consolidation of business processes.
2.1 Aim and Concept of Service-Oriented Integration
IT systems of enterprises, individual application systems have been developed considered suitable for business models
and accumulated the indispensable information. These are invaluable assets for enterprises and necessary to inherit
and utilize them from dispersed existing systems.
(1) Adapt quickly to changes in the business using the existing IT assets
Business environments are changing quickly, encouraging the brisk integration and separation of enterprises and alli-
ances between enterprises. At the same time, the integration and restructuring of many existing IT systems is required
and there is an urgent need to take flexible actions in these situations.
Enterprise is in the era of incremental development utilizing existing assets rather than scrap & build approach. Fujitsu’s
TRIOLE vision aims to achieve further efficiency of optimizations for the future as well as for the existing IT assets.
Fujitsu will realize a flexible IT environment using Service-Oriented Integration regardless of the purpose, form and work
front of the customer system. TRIOLE aims to drastically expand business and improve convenience for customers
using Web service*3 linkage and ubiquitous networking.
*3 Web service Services provided on the web.
TRIOLE Technical White Paper
All Rights Reserved. Copyright © FUJITSU 2004 13
Fig. 2-1 Integration and Development of IT Systems
Information processing
Increasing quality and availability of information
Ubiquitous networking
New types of business process
Improved information utilization
Improved computer utilization
Improved transactions, etc.
Var ious Web services
System by purpose/work front
System by purpose/work front
Enterprise portal
Providing new metrics for total optimization
CRM
SCMProcurement
Manufacturing
Distribution
Mainframe
PC
UNIX
Speedup, channelinnovation, etc.
Present
Uti
lizati
on
of
Info
rmati
on
UNIX
Grow together various business system
Improvement of operationenvironment
(2) Concept of Service-Oriented Integration
Fujitsu will realize the expansion of business through Service-Oriented Integration, which has the following three stages;
Business Processes Integration, Information Integration and People Integration.
1.Business Processes Integration for applications
2.Information Integrationfor for the dispersed data
3.People Integration for the knowledge
This integration will broaden its range of integration while advancing and expanding step by step according to various
developments such as an increasing amounts of network data and changing business requirements.
All Rights Reserved. Copyright © FUJITSU 2004
TRIOLE Technical White Paper
14
The roles of software modules used to achieve Service-Oriented Integration are shown in the figure below.
Fig. 2-3 Configuration of Service-Oriented Integration
DWHDWH*4*4
DWH*4
Location, Attribute, Location, Attribute, Access methods, etc.Access methods, etc.Location, Attribute, Access methods, etc.
GLOVIA
Adapter
Adapter
Adapter
Adapter
SAP R/3
RDB
RDB
[Business Process
Integration]
Information sharing hub
Service Integration
[Information Integration]
XMXML stor store
[People Integration]
Ap
plic
atio
n
Process hub
Communication
Presentation
User profile management
BI*5
OLAP*6
Mining*7
Interstage Shunsaku
Content Management Repository(Definition information /Location management)
XML store
Application
Fig. 2-2 Evolution of Service-Oriented Integration
Links betweenknowledge
Links betweeninformation
Links between applicationprograms
BusinessProcess Integration
People IntegrationInformation Integration
*4 DWH Abbreviation of data warehouse. This is the original database for enterprise strategy or to determine intent.
*5 BI Abbreviation of business intelligence. Software product that provides data collection, classification, analysis and accessing methods to support determination of intent to
contribute to business management by employing data accumulated throughout the enterprise.
*6 OLAP Abbreviation of online analytical processing. Online analytical processing Function for analyzing from a variety of angles by the end user, to get valuable information
from that information that has been accumulated on the DWH.
*7 Mining Function for mining raw data from that information that has been accumulated on the DWH to get valuable information (including hypotheses, knowledge and issues).
TRIOLE Technical White Paper
All Rights Reserved. Copyright © FUJITSU 2004 15
2.2 Business Process Integration - Significantly Reduced Man-hours by XML*8 Hub -
Business Process Integration involves linking business applications to create a new business operation.
Business Process Integration plays the following two roles:
1) ‘n-to-n’ information sharing between various customer systems (Information sharing hub)
2) Business Process Integration toward Improvement of automation and agility of business operations (Business pro-
cess hub)
The existing Business Process Integration has been positioned as a corporate hub to integrate information systems in
enterprises. TRIOLE’s vision Business Process Integration aims at integration including end users using two hubs as
follows.
Also, Fujitsu will expand this target to grid computing in the future.
Fig. 2-4 Development of Business Process Integration
Corporate hub Information sharing hub
Integration of information systems Third party software
Web services
Process hub
End user level
Client
Process hub
Client
Third party hardware
Gridcomputing infra.
(1) Information sharing hub - Sharing of information between various customer systems -
The information sharing hub enables rapid linkage with mainframes of each company including ERP packages and GS
series.
Conventionally, linkage between customer systems and application programs required programming. However, the
corporate hub, enables linkage with customer systems and with application programs once the customer creates a
format for the linkage. This results in cost reductions and productivity improvements. The information sharing hub
enhances the uncomputerized upper process support tools to significantly reduce consulting costs and adjustment
costs between business departments.
The information sharing hub makes a common dictionary for each business pattern such as general accounting, man-
agement accounting and production management and stores each of them into the repository. With reference to the
common dictionary, the information sharing hub finds data items (names) and matches them automatically. With the
information sharing hub, both of the creation of matched formats and the definitions of data items are unnecessary,
which enables quick linkage.
*8 XML Abbreviation of Extensible Markup Language A markup language the uses tags to describe data that is in a tree configuration as text data.
All Rights Reserved. Copyright © FUJITSU 2004
TRIOLE Technical White Paper
16
Fig. 2-5 Conversion of Data Items in Business Linkage
Individual Applications Corporate hub
EAI
Information Sharing hub(Common Dictionary)
XMLhub
Information Sharing hub(Package Connection Pattern)
RepositoryRepositoryRepository
XMLhub
SAPGLOVIA
SUMMIT
glovia
.comGLOVIA-C
Main
FrameGLOVIA
/SCP
CD
and
mapping
- AL: Application Logic, DC: Doc. Conversion, PC: Protocol Control, CD: Common Dictionary
AL
PC
DC
PC
DC
AL
PC
DC
AL
PC
DC
AL
PC
DC
AL
PC
DC
AL
DC
AL
DC
AL
DC
AL
PC
DC
AL
DC
AL
DC
AL
AL
AL
AL
AL
AL
AL
PC
DC
CD
RepositoryRepositoryRepository
PC
DC
(2) Business process hub - Business process integration -
The business process hub provides a business process runtime environment including process-flow control, modeling/
monitoring, and templates for business process development to control the business process at an end user level and
aims to optimize the entire customer system.
The business process runtime environment enables the customer to define and execute the business process and also
to redefine the business process based on the execution result.
The modeling/monitoring (analysis) tools are tools that facilitate modeling and monitoring for analysis/evaluation of the
business process.
The business template function provides templates for display (JSP*9/Servlet) and processing of intra-company opera-
tions, inter-company transactions and managerial decision-making. Combining these templates will expand the busi-
ness process from ‘in-B’ to ‘B-to-B’.
*9 JSP Abbreviation of Java server pages. A technology the uses Java script to dynamically create web pages with web servers and for transmission to clients.
TRIOLE Technical White Paper
All Rights Reserved. Copyright © FUJITSU 2004 17
Fig. 2-6 Configuration of Business Process Hub
Web servicesDevelopmentenvironment
Application server
Application server
PrivatePrivate
UDDIUDDI
Private
UDDI
UDDIregistration
toolWeb service
Web services linkage
Modeling
Monitoring
Operator/Manager Executives Workplace
Internal B
Client
Web-EDI
Rosetta Net*10
JEITA*11
Web service
Purchasedepartment
Managerialdecision-making
template
Personnel/general
affairs template
Procurement template
RFP Proposal Order Acceptance inspection etc.
Information sharing hub
Process hub
Business documentBusiness documentBusiness document
s e
Business process runtime environmentBusiness process runtime environmentBusiness process runtime environment
Integration with legacy and package apps.Integration with legacy and package apps.EDI, Rosetta Net/JEITA, etc.EDI, Rosetta Net/JEITA, etc.Integration with legacy and package apps.EDI, Rosetta Net/JEITA, etc.
*10 Rosetta Net A world-wide, non-profit consortium that sets the standard B to B framework for procurement transactions and their evaluation centering on industry related to
electronic components and information devices.
*11 JEITA Abbreviation of Japan Electronics & Information Technology Industries Association.
All Rights Reserved. Copyright © FUJITSU 2004
TRIOLE Technical White Paper
18
2.3 Information Integration - Content Management, High-speed Search and Business Intelligence -
Information Integration aims to integrate an enormous amount of data stored in various existing systems throughout the
enterprise to enable their full utilization. It provides functionalities of Content Management, High-speed XML contents
search and Business Intelligence.
Fig. 2-7 Configuration of Information Integration
Batch transferBatch transferBatch transfer
DesignDesignDesign
RepositoryRepositoryRepository
Connecting Information
Various business systems
Business Process
Integration Information Integration
Monitoring and collectionMonitoring and collectionof transaction data of transaction data Monitoring and collectionof transaction data
Content Management
Hybrid OLAP
Application
InterstageShunsaku
Query/searchapplications
Business intelligence
(information utilization/analysis)
DWHDWHDWH Data MartData MartData Mart
XMLXMLstorestoreXMLstore
DatabasesDatabasesDatabases
ManufactureManufactureManufacture
ShipmentShipmentShipment
Real-time transferReal-time transferReal-time transfer
(1) Dynamic collection of contents
Content management is the functionality to manage the location information of contents stored in each system, how to
access and relationship between them as meta-information. It also manages business applications and data linkage
definitions in the information-sharing hub and dynamically collects content to realize construction of a spiral data ware-
house.
This enables utilization of information in the current systems to quickly satisfy the needs of the end users, while reduc-
ing significantly the cost of constructing a data warehouse, which typically involves considerable expenses related to
initial investments. Step-by-step investments realize further expansion of customer systems.
(2) High-speed search of XML contents
It has been difficult with RDB to standardize formats and add/modify specifications of data. Interstage Shunsaku Data
Manager achieves a high-speed search for XML (text) data in a constant amount of time even regardless of search
parameters requested and the data amount.
(3) Real-time analysis of dispersed information
Business Intelligence (BI) functionality provides the OLAP tool, which enable to federate the various kinds of information
dispersed in systems throughout the enterprise, and analyze them in real-time. In addition to functionalities of traditional
OLAP tools(R-OLAP, M-OLAP), this new OLAP tool expands users significantly by the utilization of highly fresh informa-
tion and the detailed information as well as their summaries. For example, sales and development departments can
utilize accounting information in real time, which has been used only in the strategy departments, resulting in expanding
marketing activities. Furthermore, this functionality provides Hybrid-OLAP tools that have both the flexibility of R-OLAP
and the performance of M-OLAP to reduce drastically the cost of developing customer systems for utilization of their
information.
TRIOLE Technical White Paper
All Rights Reserved. Copyright © FUJITSU 2004 19
2.4 People Integration - Knowledge Sharing, Know-how Accumulation and Ubiquitous Network -
People Integration provides the necessary information from a wide range of information sources as needed to support
increasing individual knowledge. Although the existing system has provided personalized information simply through a
web interface accessible via a browser, Fujitsu will respond to the needs for shared intelligence and accumulated know-
how.
We are witnessing a dramatic grown communication ‘anytime’, ‘anywhere’ and from ‘any terminal’ and in ubiquitous
environments wherein computing is possible. Fujitsu is integrating basic elemental technologies with the core of ‘pres-
ence management technology’ for a real-time grasp of the status of ‘people’, ‘products’ and ‘services’ to provide high
added value as the overall system. We are linking a variety of services, networks and terminals seamlessly to realize the
free and smooth flow of information between people and services by absorbing their varieties (complexities). This is to
provide the optimum services that can be used anywhere by anyone to enable the speedy expansion to actual business.
Fig. 2-8 Configuration of People Integration
BI KM GW Training
KnowledgeKnowledgeKnowledge
UserUserprofile managementprofile management(devices/information(devices/informationprotection/trace)protection/trace)
Userprofile management(devices/informationprotection/trace)
Mobiletelephones
PDA PC
ERP
HostHostHost
CRMCRMCRM
BusinessProcess
Integration
InformationIntegration
Knowledge information link (work place)
Real-timecollaboration & communication(ubiquitous infrastructure)
Seamless communication
InformationInformationInformationAPL
Vehicle mounteddevice information
(1) Technologies Supporting People Integration
User profile management
This is positioned as the core technology of poeple integration. This is classified in organization and role in the
system. This technology manages each of these types of information.
Presentation
The presentation infrastructure provides personalized screens fitting information and services into small windows that
can display them, such as bricks of operation screens that can be used by an operator. Also, this has a trans-coding
function (for contents conversion and separation) that converts screens to mobile terminals such as such as a cellular
telephone or PDA other than a PC. Still further, back system screen data is converted to XML data and can be freely
formed with the Active scenario *12. (Back system screen integration)
*12 Active scenario Provides the information optimized for the user and reduces input work.
All Rights Reserved. Copyright © FUJITSU 2004
TRIOLE Technical White Paper
20
Communication
This provides the necessary information such as groupware or internet searches personalized, as intelligence. This
provides a communication function (mail, chat, electronic meetings) for the smooth sharing of intelligence.
Presence Management and Push Type Information Distribution
Presence management technology unifies management in real-time for the current status (presence) of ‘people’, ‘prod-
ucts’, and ‘services’ that regularly change and their changes, and selects and distributes the data and information that
is appropriate for users. Not only is presence information stored, but also if there is a change in a pre-specified
presence (notification reservation), this actively notifies of changes. By referencing presence using a Push type infor-
mation distribution function, this can automatically provide information and services optimum for the destination (such
as cellular telephones, PDA, or PCs) when required by the user. It is possible to notify immediately when there are
presence changes, if conditions such as changes of people on-site are specified, to provide timely services in a
ubiquitous environment that does not select time or place at that opportunity.
Fig. 2-9 Presence Management Technology
Reserved forReserved for
notificationnotification
Reserved for
notification
Management ofnotification destination/status of notification
Phenomena reserved for notificationPhenomena reserved for notificationPhenomena reserved for notification
Notification change phenomena
notificationnotificationnotification
Service(APL)
Service(APL)
Service(APL)
Service
Matched?
People, Products Service
Push distribution
Presence reference Presence reference Presence reference
Sta
tus c
olle
ctio
n
Med
ia G
W
PresencePresence
information information
Presence
information
StatusStatusStatus
PushPushdistributiondistributionPushdistribution
PushPushrequest request Pushrequest
UpdateUpdateUpdate
ChangeChange
notification notification
Change
notification
Knowledge Integrated Management
Fujitsu will provide the following functions to support the knowledge accumulation and practical use of integrated
knowledge.
- Application of educational contents
- Accumulation of indivisual business know-how and its application
TRIOLE Technical White Paper
All Rights Reserved. Copyright © FUJITSU 2004 21
2.5 Models for System Development using Service-Oriented Integration
The following are the typical models (basic applicable forms) for system development consolidating business applica-
tions, information and knowledge (people).
(1) Model for development of business application integration system
Fig. 2-10 Development of a New Accounting System into
which Package Applications Are Integrated
New accounting systemNew accounting system(R/3)(R/3)
New accounting system(R/3)
Current Mission-critical Systems
Business Process Integration
SAR R/3
Assortment
New Accounting System
Peripheral system
Lin
ke
xp
ress
Lin
kexp
ress
HU
LF
TH
ULF
T
ad
ap
ter
ad
ap
ter
HU
LF
T
ad
ap
ter
HU
LF
TH
ULF
Tad
ap
ter
ad
ap
ter
HU
LF
Tad
ap
ter
R/3
ad
ap
ter
HU
LF
T
HU
LF
T
HU
LF
T
accounting system
Format conversion
routing
Formatconversion
routing
Master dataMaster dataData reflection
Sales dataSales dataSales data
Master data
Business systemsother than
accounting system
Inte
rnal a
dap
ter
Data extraction
Common DB Common DB Common DB
Sales dataSales dataSales data
Sales/masterSales/masterDataData
(IDOC)(IDOC)
Sales/masterData
(IDOC)
Fig. 2-11 Integration of Current Business Systems
Associated with Business Mergers
HU
LF
T a
dap
ter
HU
LF
T a
dap
ter
HU
LF
T a
dap
ter
HU
LF
TH
ULF
Tad
ap
ter
ad
ap
ter
HU
LF
Tad
ap
ter
HU
LF
TH
ULF
Tad
ap
ter
ad
ap
ter
HU
LF
Tad
ap
ter
New Integrated System
Fleetscheduling
2. order
1. order
1. order ExistingA companyMainframe
ExistingB companyMainframe
1. order
1. order
4. Instructions forallocation of vehicles
5. Allocation
OrderOrdermastermasterOrdermaster
Business ProcessIntegration
Weborder server
Client
Absorbing
difference between
new and old systems
such as business codes
3. Dispatchschedule
ED
IE
DI
ad
ap
ter
ad
ap
ter
ED
Iad
ap
ter
System before Integration
Fo
rmat c
on
ve
rsio
nro
utin
g
ExistingExistingterminal terminal Existingterminal
ExistingExistingterminal terminal Existingterminal
New terminals (browsers)such as sales branches,trading partners
Sales distributionSales distributionserver server
Sales distributionserver
ClientClient(Current EDI)(Current EDI)
Client(Current EDI)
All Rights Reserved. Copyright © FUJITSU 2004
TRIOLE Technical White Paper
22
(2) Model for development of information integration system
Fig. 2-12 Development of Data Warehouse Using Business Process Integration
Data martData martData mart
Business Process
Integration
HU
LF
TH
ULF
Tad
ap
ter
ad
ap
ter
HU
LF
Tad
ap
ter
Fo
rmat c
on
vers
ion
rou
ting
DB
ad
ap
ter
ED
IE
DI
ad
ap
ter
ad
ap
ter
ED
Iad
ap
ter
FT
PF
TP
ad
ap
ter
ad
ap
ter
FT
Pad
ap
ter
Planning department
Data source
systems
Client
Accounting system
Sales system
Ordering system
OLAPserver
Sales department
Form creation
CentralCentralwarehouse warehouse
Centralwarehouse
Analysis report
Reference to report
DWH system
Fig. 2-13 Development of Information Infrastructure
Using Information Integration
UsedUsedapplicationapplication
group group
Usedapplication
group
Business ProcessIntegration
Fo
rmat c
on
vers
ion
rou
ting
DB
ad
ap
ter
FT
Pad
ap
ter
FT
Pad
ap
ter
Bu
sin
ess P
rocess
Inte
gra
tion
Information systemdepartment
Analysisapplication
Customerinformation
(Differences)
Customerinformation
(Differences)
Service provider system
Service provider system
Customer DBCustomer DBCustomer DB
Customer DBCustomer DBCustomer DB
Expand scope ofinformation use
Flexibleinformation use
Management of customerinformation and metainformation for each
service provider
VIEWapplications
Form creationapplication
Mart creationapplication
Planningdepartment
Salesdepartment
Integrated Informationinfrastructure System
Inte
rsta
ge
Sh
un
sa
ku
InformationInformationIntegration Integration InformationIntegration
Bu
sin
ess P
rocess
Inte
gra
tion
DevelopmentDevelopment
according toaccording to
market changes market changes
Development
according to
market changes
(3) Model for development of knowledge integration system
There is a move afoot to integrate new operating procedures and know-how with the business process, and/or to define
and share them as knowledge in association with the business contents. Human resources (HR) and e-learning also
tend to be utilized as knowledge associated with business contents.
TRIOLE Technical White Paper
All Rights Reserved. Copyright © FUJITSU 2004 23
Fig. 2-14 Scenario where knowledge is used
Realtime informationRealtime information(index change etc.)(index change etc.)
Realtime information(index change etc.)
s es e
Purpose buildserver
Core system
Business Process
Integration
People Integration
Knowledge usage scenarioKnowledge usage scenarioKnowledge usage scenario
Define knowledge asbusiness process for sharing
(1) Realization of role-based workplaces
(2) Push-type collaboration
(3) Integration of operation (process and contents manipulation), etc.
Proactive action based on observation of the effectof the pre-processes on subsequent processes
Analyse the entire process, find the bottleneck, and take measures against it
HR
e-Learning
administrative
department
/purchasing
department
etc.
Management structureSuperior
Supplier Customer
Collaborative Workplace
Related knowledge
Work place Customer
BusinessBusinessprocessprocessBusinessprocess
ActivityActivityhistoryhistoryActivityhistory
Sales, production, stock, etc.
Define Knowledge as businessprocess for sharing
Sharing content ascombined knowledge
Re-scheduling by predicting completion of operationfrom length of post-process
Identify experts and collaborate Optimize personnel and work allocation(Supplement with temporary personnel, andreallocate as needed)
InformationInformationIntegration Integration InformationIntegration
(4) System development model ‘Route Sales’ that supports Ubiquitous Network
The statuses (presence information) such as stocks of products that change regularly, and status of terminals of onsitepersonnel are managed. For example, when products are received, that delivery information is notified to the terminal in
use at that time using the optimum transmission means. In this way, services that do not miss business chances are
realized by the complete and timely notification (delivery information).
Fig. 2-15 Scene of Use of Route Sales
Stock checks/Stock checks/delivery notificationdelivery notificationrequestrequest
Stock checks/delivery notificationrequest
Product managementdepartment
Delivered productinput
Center
Existingbusinesssystem
Stockmanagement
ordersystem
InterstageRealtime Communicator
Status monitoring
PresencePresenceinformationinformationPresenceinformation
Push distribution
Notifies with optimum transmissionmeans when products are delivered
Deliverynotification
Term
inal v
irtualiz
atio
n
Sales branch
When notification received,order from that location
In transit
Product stockProduct stockTypes of terminalsTypes of terminalsPosition of salesPosition of salespersonnel personnel
Product stockTypes of terminalsPosition of salespersonnel
All Rights Reserved. Copyright © FUJITSU 2004
TRIOLE Technical White Paper
24
2.6 Collaboration with Global Servers
The global server has supported many customers’ business activities as a business information system platform. Today,
global servers have accumulated an enormous amount of customer intellectual assets (such as applications, databases,
designs, operation know-how). Global servers are being further readied for continuous operability (such as disaster
recovery) and scalability to strive for the stable system operation.
Also, the business environment surrounding business is changing from rapidly and business information systems must
grow in response to the changes. To accomplish this, instead of redeveloping the system from scratch, the utilization of
existing and abundant intellectual assets previously accumulated will most effectively enhance effectiveness in terms
both of speed and cost.
Global servers capitalize on the merits of centralized management, and ensure maintenance and uniformity through
usage and linkages (replication with open servers) from open environments (Java applications, J2EE). At the same
time, the global server will guarantee the portability and continuity of existing assets, and effort for integration of the
transaction tasks which have been managed by global servers (such as manufacturing- and distribution-associated
ordering operations and finance-associated deposit/exchange operations) with new technology realized though Ser-
vice-Oriented Integration.
Fig. 2-16 Collaboration with Global Servers
Service-Oriented IntegrationService-Oriented IntegrationService-Oriented Integration
Distribution system
<<Current system>>
Order reception system
Distribution system
Order reception systemDBDB
DBDB
DB
DB
Maximum use ofexisting assets
Company-wide infrastructuresystem
(global servers)Third partyThird partymainframesmainframesThird partymainframes
Manufacturingmanagement
system
Individual BusinessIndividual BusinessSystemsSystemsIndividual BusinessSystems
Information distribution between varioustypes of systems
Business process automation
Business Information IntegrationBusiness Process Integration
Real-time data collection and DHW
High speed information search and BI
analyses
Business People Integration Provide optimized screens for individuals, communication spots and share know-how
Internet
In-house end user Superior Client
UNIX/IAUNIX/IAserversserversUNIX/IAservers
Accounting system
Customermanagement
system
UNIX/IAUNIX/IAserversserversUNIX/IAservers
Lin
k
Lin
k
Lin
k
Lin
k
TRIOLE Technical White Paper
All Rights Reserved. Copyright © FUJITSU 2004 25
(1) Integration with Business Process Integration
Business Process Integration connects individual systems optimally arranged for each operation logically to realize a
high-value-added business information system. The transactions on the global server are indispensable to customer’s
business activities. Integrating Business Process Integration with the global server holds promise of providing highly
competitive business activities.
(2) Integration with Information Integration
Transaction information on the global server is important for customers to do business analysis. And, most of the
information are generally used on a monthly, weekly or daily basis. In various aspects from drafting of management
strategies to inventory control, the result of judgment depends largely on the degree of freshness of information. TRIOLE
will offer the results of updating transactions on the global server in real time to enhance the freshness of information.
(3) Integration with People Integration
By using the Web computing technology, most of challenges to conventional transactions (such as integration into the
IP network*13, release from complicated client software management and improvement in serviceability) can be solved
and integrating the global server with People Integration holds promise the expansion of business activities.
*13 IP network Network that uses TCP/IP protocols.
All Rights Reserved. Copyright © FUJITSU 2004
TRIOLE Technical White Paper
26
memo
TRIOLE Technical White Paper
All Rights Reserved. Copyright © FUJITSU 2004 27
Chapter 3
Toward Rapid Development and
Deployment of Business Applications
(Efficiency)
All Rights Reserved. Copyright © FUJITSU 2004
TRIOLE Technical White Paper
28
Chapter 3 Toward Rapid Development and
Deployment of Business Applications (Efficiency)
- A Framework that Extends its Applicability to Cover the Entire Customer System including
Mission-critical Systems -
With the introduction of a new development framework called B².Sframework*14, TRIOLE en-
ables rapid systems development requiring minimal programming. The framework consists of
an application framework and an application control base/operation control base, and a list
base.
3.1 Concepts and Effectiveness of Framework
At present, IT vendors are offering frameworks for application development mainly based on Web-front systems. In an
open environment, however, multi-vendors are increasing in number and as the heterogeneous environment grows popular,
resulting in the diversification of development environments for business applications. Under these environments, a
simple application framework is not enough to develop a reliable mission-critical system in a short period of time.
TRIOLE’s B².Sframework enables development ranging from Web-front systems up to mission-critical systems, and con-
centrates on designing business applications without developing any control block in infrastructure to achieve rapid
development and deployment of business applications.
(1) Extends the applicability of a framework to include the development of mission-critical systems
B².Sframework is a framework that extends applicability of development ranging from Web-front systems to mission-
critical systems, as well as the development of business applications.Consolidating the systems and business application development skills and know-how that Fujitsu has developed for
many years, TRIOLE will enable development and deployment of the entire customer system.
Fig. 3-1 Function System of B².Sframework
Application control base / operationcontrol base (For mission-critical system) List
infrastructure
Application framework
Application control base
- Synchronized online model
- Asynchronized online model
- Center cut model
- Batch model
Operation control base
- Business operation control
- Operation resource management- List creation
- Electronic lists
- External character
management- Printing
management- List transmission
B2.Sframework
Development tools Application server DB server
Basic functions
(XMLrules/data specifications descriptions,command scripting, EJB/web communication)
Mail link, mainframe link
Webframework
EJBframework
Webservices
(XMLsending/receiving)
Supports cellular terminals
Electronic forms
(Standard/Common functions)
Operation system tool
*14 B2.Sframework Abbreviation of building blocks system framework.
TRIOLE Technical White Paper
All Rights Reserved. Copyright © FUJITSU 2004 29
(2) Building Block System
The building block system framework consists of a hierarchically of two components--- platform and application pro-
gram- and customizes required functions by components.
The application program component is developed by the application framework based on the J2EE standard architec-
ture and the application control base/operation control base for development of business systems that support the life
cycle of mission-critical systems.
Fig. 3-2 Configuration of B².Sframework
Platform
Business logic
Businessapplication
Ap
plic
atio
n
[Design guidelines]
Business patternBusiness patternBusiness pattern
Package
Business solutionsDedicated to business logic
Platform
Control logicControl logicControl logicControl / operation baseControl / operation baseProvide modules as standardProvide modules as standardControl / operation baseProvide modules as standard
(3) Rapid designing of customer system and standardization of development style
Standardization of development style
The inconsistency in the quality of the system caused by individual developers can be minimized by using a pre-
defined systems design method and modularized functional blocks. By adopting development logic as well as mod-
ules enables the standardization of the development style, which will improve program readability and maintainability.
This will help homogenize the quality of development and improve the quality of the entire customer systems.
Ensuring high quality
Using software component of Fujitsu’s time-proven control logic (such as DB control) separated from business logic
describing business processing, customers can concentrate on developing business logic and develop a high-quality
system with efficiency. Combining the verified models and function blocks, developers will be able to develop a
reliable customer system.
Effort for open system
This realizes development efficiency and quality improvements through the unification and modularization/reuse of
application styles that conform to J2EE which is an open technology. This realizes use of high function component
tags and links with EJB*15 and SOAP applications by providing application import functions that use Struts, which is an
open source framework.
*15 EJB Abbreviation of enterprise java beans. One of the Java componentizing technologies; Standardizes component specifications that operate on the server side.
All Rights Reserved. Copyright © FUJITSU 2004
TRIOLE Technical White Paper
30
3.2 Application Framework
This framework standardizes a development style according to the J2EE application design guidelines and provides
logic for some of the same components as standard. Concealing the platform component of the OS and middleware,
the framework supports flexibly frequent modifications and increased variations and ensures high reusability.
Fig. 3-3 Location of Application Framework
CORBAcommunication
Item check Item check specificationsspecificationsItem check specifications
Rich systemRich systemcommunication controlcommunication controllibraries libraries
Rich systemcommunication controllibraries
Rule description Rule description in XMLin XMLRule description in XML
Process flowProcess flowProcess flow
Screen transitionScreen transitionScreen transition
Rich high-performance tag libraries,Rich high-performance tag libraries,electronic formselectronic formsRich high-performance tag libraries,electronic forms
Mobiletelephones
Screen
Electronic form functionXML business rules
XML data specifications
EJB/Webservice communication
Session management, item check, screen/business controlexception handling, other
Application framework
Interstage Application Server
XML communication
DBserver
DBDBDB
Webservice
Groupware
Legacysystem
System communicationJSP tag library
Business logic Component
MQ link
SMTP/IMAP
Business application
PDA
Browser
The framework has the following merits:
Business application development based on business logic
Load reduction in business application development and productivity improvement in business application
Asset utilization by Struts, a J2EE-based open source development framework
Development and deployment of reliable customer system with quality modules
Realization of some of the same components by standardization of development style
Improvements in program readability and maintainability of customer system
TRIOLE Technical White Paper
All Rights Reserved. Copyright © FUJITSU 2004 31
Fig. 3-4 Application Control Base
Support of various developmentlanguages
Java(EJB), COBOL, C
Support of open and standardizedtechnology(J2EE, .NET using middleware)
Providing application control proformaEJB version, COBOLversion
Support for collaboration with
Java(EJB) and COBOL Interstage Application
Framework Suit
e.Frame
Java(EJB)application control
EJB
APL
COBOLapplication control
COBOL
APL
AP/DBWWW
Interstage Application Server
(1) Application control base
The application control base provides the business processing pattern library consisting of the following four business
processing models and control modules for business application development as standard. The developers can de-
velop high-quality business applications to support large-scale and high-reliability systems just by changing the combi-
nation of the four business processing models according to applications or choosing the business processing pattern
library needed to create business logic.
Synchronous online processing model
This model provides work assignment of the control logic, transaction control, exception handling, automatic retry
control, log acquisition, and so on.
Asynchronous online processing model
In addition to the control logic of the synchronous online processing model, this model provides background process-
ing and linkage mechanisms (status inquiries and notification of the result).
Center-cut processing model
This model processes business operations, which have undergone batch processing, online and concurrently in re-
sponse to 24-hour online services. Using the same applications and resources as those for online services enables
load control without affecting response to online services.
Batch processing model
This model provides control logic that repeats the same processing for all records in the input files. It also provides
the functions for operation schedule design, automatic rerun in the event of error, and restart in order to operate
automatically batch jobs exceeding 10,000 cases per day required for the mission-critical system.
3.3 Application Control Base/Operation Control Base
This application control base/operation control base is a control base for developing business systems that support the
life cycle of mission-critical systems. Applying the application control base to the customer system enables developers
to speed up significantly the new development and/or the repeated development of business systems.
Applying the operation control base enables customers to maintain the stable operation of changing business systems.
All Rights Reserved. Copyright © FUJITSU 2004
TRIOLE Technical White Paper
32
(2) Operation control base
The operation control base provides the functions for business operation control and operational resource management
to keep the continuous stable operation of business systems. This significantly improves the operating efficiency of
large-scale mission-critical systems.
Business operation control
This provides the functions for business management, business day management and automatic operation.
Operational resource management
This provides the functions for hot-swapping, log acquisition, fault information acquisition and capacity management
required for 24-hour continuous operation. The functions for data integrity (backup/restore) and data transfer (clus-
tering, backup center) are also provided to retain business data securely.
3.4 List Infrastructure
Lists are not only indispensable in enterprise activities such as general ledgers, various type of billings and dockets.
Lists, which visualize the numbers necessary in enterprise activities and daily life, is around us 24 hours a day, 365 days
a year.
Fig. 3-5 Functions for List Infrastructure
SpoolingSpoolingSpooling
List transmission DBList transmission DBList transmission DB
Electronic listElectronic listElectronic list
List output management
Electronic forms
XML
List design/creation
XMLCSVText
ERP, business applications
Host
Onlineapplications
Externalcharacter
management
Externalcharacter
managementWeb input
printing management
Electronic list
ElectronicDB
Extraction/data forming
Extraction XMLCSVText
Electronic
List design/creationTransmission management/
printing management
Spoolingdata
printing
Network
(1) Features of List Infrastructure
‘Lists’ greatly affect enterprise activities by mistakes in system development methods which cause performance or op-
eration troubles to occur because it has a deep relationship to customer daily business. A considerable amount of
experience is needed to securely build a ‘list’ system. To develop a list system, you must have a grasp of the customer’s
requirements, but also a wide ranging knowledge from understanding the basic software specifications, to having a
grasp of printer apparatuses is required. For that reason, reformations of the development methods for lists are strongly
desired.
List infrastructure uses ‘rapid development and deployment of business applications’ in the approach to system devel-
opment, as its policy, and by providing the basic functions from data extraction to lists generation, distribution, manage-
ment and output, it is possible to development list systems without programming.
The demands on list systems, are diversifying to not only printing, but also to creating webs, electronic data and list
distribution. LIst infrastructure supports such diversified demands by preparing the industry’s top class components
TRIOLE Technical White Paper
All Rights Reserved. Copyright © FUJITSU 2004 33
and infrastructure middleware. For example, these cover the portions that have been difficult to realize with general
tools, such as external character management. By incorporating these, it is possible to speedily development list sys-
tems.
(2) Speeding up development
The philosophy of speeded up development is not simply to be used in system development, by incorporating compo-
nents and applying infrastructure middleware. For example, to design list layouts, development can be further speeded
up by automatically generating list layouts by incorporating currently used lists using scanners, or creating electronic
lists without changing applications.
Furthermore, the scope for support of list infrastructure is expanded as far as the list distribution field for which applica-
tion development was common. For example, it is possible to develop a list printing environment that does not consider
hardware type or configuration, such as printer type or configuration, or where terminals are located. That applications
can develop a list output job that links with mission critical business and online application transactions. List infrastruc-
ture uses the short-term development of systems while using existing assets as its basic concept.
List process model
List process can be classified into three models: An online list output model; a batch large-volume output model; and
list input model using an electronic form. It is developed by combining each component of the list infrastructure.
- Recently, the use webs and the internet is becoming ever more common. Online list output models support up to
areas that cannot be realized with PDF, which is the industry standard, or PDF such as photographs or immediate
printing.
- Batch large-volume output models realize high speed printing even on comparatively low-speed lines, by efficiently
transferring lists, even list distribution to center large-volume printers or branches.
- List input models using electronic forms are a new method to improve business efficiency by creating webs for lists
that are used by entering onto paper.
(3) Results of introduction
The benefits of system development (including redevelopment) are halved if information is circulated on paper, even if
business webs or ERP systems are introduced. Brought about are the benefits of ‘speed’ to pass information in real-
time, and to realize rapid publication of information, and the deeply reduced costs by using electronic/paperless data,
and the easy ‘utilization’ of data in data searches, or exporting to Excel. It is the point of creating electronic data of
enabling the dual use of operate using paper as in conventional methods, and creating electronic lists from the neces-
sary portions.
All Rights Reserved. Copyright © FUJITSU 2004
TRIOLE Technical White Paper
34
memo
TRIOLE Technical White Paper
All Rights Reserved. Copyright © FUJITSU 2004 35
Chapter 4
Toward Stable & Reliable Systems and Reduced TCO
(Continuity)
All Rights Reserved. Copyright © FUJITSU 2004
TRIOLE Technical White Paper
36
Chapter 4 Toward Stable & Reliable Systems and Reduced TCO (Continuity)
- Autonomous System Infrastructure to Overcome Challenges Associated with Scalability and
Complexity Increases –
Today’s IT systems demand 24 hour service, 365 days a year. It is unacceptable for the cus-
tomer system to go down due to temporary workload increase, for Web service to worsen due
to unbalanced operating load between customer systems, and for the customer system to
shut down due to maintenance.
In response to these needs, TRIOLE will guarantee the compatibility, consistency and quality
of the entire customer system including ISV/IHV products as well as Fujitsu products and
provide customer systems with safe and highly productive systems.
4.1 Toward Optimization of Customer Entire System
Fujitsu has developed approaches that realize high reliability and fault tolerance at the component, equipment and
products hardware and software level constituting the infrastructure of customer systems. It aims to provide mutual
linkage between the high reliability and fault tolerance of products to realize a fault-tolerant customer system through
Autonomous System Infrastructure.
Fig. 4-1 Efforts for Stable & Reliable Systems
(1) Efforts for stable & reliable operation at component and system levels
Fujitsu will enhance fault tolerance functionality at component level such as CPU and disk cache parity and CPU instruc-
tion retry. At systems level enhancement includes redundancy (hot standby, automatic retraction) and redundant con-
figurations of memory and disks, and hot swapping.
��Cluster systemsCluster systems
Product levelProduct level
�Redundancy of storage/networkRedundancy of storage/network
Product level
�Cluster systems
�Redundancy of storage/network
�Management of entire systemManagement of entire system �Optimization of system resourcesOptimization of system resources�Optimization of system resources�Management of entire system
Complete data guaranteeComplete data guaranteeComplete data guarantee
Feedback of customer system requirements
Accumulation
of reliability
System levelSystem levelSystem level
�Environmental/life testsEnvironmental/life tests
Non-stop productsNon-stop products
�Online expansionOnline expansion
Equipment levelEquipment level
�Redundancy of componentsRedundancy of components �Hot-swapHot-swap
Highly reliable equipmentHighly reliable equipment
Component levelComponent level
Non-stop businessNon-stop business
�Environmental/life tests
Non-stop products
�Online expansion
��Adoption Highly reliable design componentAdoption Highly reliable design componentAdoption Highly reliable design component
Equipment level
�Redundancy of components �Hot-swap
Highly reliable equipment
Component level
Non-stop business
TRIOLE Technical White Paper
All Rights Reserved. Copyright © FUJITSU 2004 37
Fig. 4-2 Efforts for Stable & Reliable Operation at Component and System Levels
(2) Efforts for stable & reliable operations at the product level
Fujitsu will enhance fault tolerance at the product level for example, the redundancy of fault-tolerance (FT), cluster
systems, storage and network, or the expansion of online hardware and software.
Fig. 4-3 Efforts for Stable Reliable Operation at Product Levels
Disk failover
Operating Server
SCF detects panic
Disk Recovery
Network Activation
Recovery in a Recovery in a
short timeshort time
Recovery in a
short time
DB
Hot standby
Notifies failureNotifies failure
Reconfirmation
Network failover
SCF : System Control Facility (System monitoring mechanism)
StandbyServer
Panic
Node failure
determination
Restart of operationRestart of operationRestart of operation
L1 cache
data
L2 cache
tag
L2 cache
data
Thorough protection of data (Component level) Remote monitoring by REMCS Center
(Component level)
Minimization of planned downtime for maintenance
(Equipment level)
Error detection
&
correction
Error detection
&
Retry
Parity
Parity
Parity
History
Online expansion
Hot-swap Online
upgradeRedundant configuration
Cross barCross bar
clockclock
Cross bar
clock
CPU,CPU,
memorymemory
(System(System
board)board)
CPU,
memory
(System
board)
PCI cardPCI cardPCI cardFirmwareFirmwareFirmware
Calculator
Register
Duplication
ECC
ECC
Cache retraction
(way)
SPARC64 V
Register
Computing unit
L1/L2 Cache
Log, History
Memory
CheckerChecker
PCI
SCF : System Control Facility
(System Monitoring Mechanism)
SMC : System
Management
Console
(System Console)
REMCS Center
SCF
Instruction retry
Cro
ss-b
ar
Other
L1 cache
tag
ECC
Checker
90,000 Pieces per System90,000 Pieces per System(PRIMEPOWER2500/32CPU)(PRIMEPOWER2500/32CPU)
SPARC64TMVSPARC64TMV679 pieces per processor679 pieces per processor
90,000 Pieces per System(PRIMEPOWER2500/32CPU)
Power supply,Power supply,Fan,Fan,SCF,SCF,SMC,SMC,
Disk, etc. Disk, etc.
Power supply,Fan,SCF,SMC,
Disk, etc.
SPARC64TMV679 pieces per processor
All Rights Reserved. Copyright © FUJITSU 2004
TRIOLE Technical White Paper
38
(3) Efforts for Entire System
The high reliability of individual products and mechanism of scalability (optimization mechanisms) alone can never
realize the stable and reliable operation of a customer system and reduced costs.
Fujitsu will introduce the “Autonomous System Infrastructure” to optimize the entire customer system with individual
optimization mechanisms interconnected. This is to achieve the stable and reliable operation of the entire customer
system through its life cycle. “Autonomous System Infrastructure” realize virtualization, automation and integration of
the IT infrastructure base functions provided with servers, storage, networks and middleware, and added functions.
Introduction and addition of customer system
Fujitsu guarantees the consistency of the customer system by both system and logic configurations so that customer
can introduce and add systems easily and properly.
Operations
TRIOLE will detect and pinpoint the location of faults early and predict potential faults or load spikes in advance of
their occurrence. These functions will reduce the frequency of occurrence of the fault and shorten operational recov-
ery time to realize continuous operations. It will Efforts for the total security of the customer system and also ensure
the safe operation of the customer system.
Maintenance
During software or hardware maintenance, TRIOLE can predict the impact of the maintenance and will adjust the
operations to be affected to alternative operations in advance in order to achieve system maintenance during opera-
tions. TRIOLE’s remote customer support system (REMCS) continuously monitors the customer system for stable and
reliable operation.
4.2 Toward Autonomous System Infrastructure
Fujitsu introduces a new optimization mechanism, ‘virtual and autonomous system’ infrastructure to automatically allo-
cate optimized hardware and middleware resources in response to spikes in processing requests. ‘Autonomous System
Infrastructure’ links with autonomous control mechanism of servers, storage, networks and middleware to enable opti-
mization of the resources in the overall system.
(1) Structure of Autonomous System Infrastructure
The Autonomous System Infrastructure is the optimization mechanism of the entire customer system, covering servers,
storage, networks and middleware and is composed of Systemwalker Resource Coordinator and Systemwalker Service
Quality Coordinator and so on. This is an optimization mechanism for the entire customer system, which is consoli-
dated an autonomous function embedded within individual products.
TRIOLE Technical White Paper
All Rights Reserved. Copyright © FUJITSU 2004 39
Fig. 4-4 Structure of Autonomous System Infrastructure
Middleware
Hardware
Performance &Workload management
Configuration of IT resource & fault management
Server NetworkStorage
Virtual and Autonomous System Infrastructure
SystemmanagementWeb servers
Applicationservers Database
2. Reporting low performance
3. Using capable resources for incapable hardware
1. Monitoring hardware errors
(2) Grasping resource configurations and visualization of failures
The Autonomous System Infrastructure virtualizes a variety of hardware resource configurations (both physical and
logical) to integrate management (virtualization of IT resources). It monitors each operating status to detect failures or
shut-downs (resource configuration and failure management). The influence and causes of failure is visualized to con-
tinue the business over the entire system with cooperation of the sensor functions of each product in the case of the
device failure, bottlenecks and so on.
For example, this grasps and visualizes the locations of connections between server and storage and configuration of
the entire network. IT makes possible to minimize its affects on business.
Also, this provides preemptive maintenance through prediction monitoring and preempts trouble by automatically switch-
ing to substitute servers and substitute communication paths. (Automation of failure processing) Also, this supports
operator work by automating configurations changes and introduction, expansion and maintenance based on resource
configuration information.
All Rights Reserved. Copyright © FUJITSU 2004
TRIOLE Technical White Paper
40
Fig. 4-5 Visualization of Causes and Effects of Trouble
!
The service affected by a failure can be determined
The cause of a problem is quickly determined
ServiceManagement
Integrated management ofIT resources
Individual resource
management
To furtherdetails
Storagemanagement
Detailed drill down
Systemwalker Resource Coordinator
Notifies the services affected by the failure
Business A
Business B
Node A Node B Node C Node D
Node E Node F
StoragemanagementTo further
details
To furtherdetails
(3) Approach for dynamic resource allocation
The Autonomous System Infrastructure uses autonomous adjustments of loads to avoid degradation of functions caused
by heavy loads. For that reason, this strengthens detection of performance errors in each product and bottlenecks, with
regard to performance problems, and supports each working phase of operators (grasping of configuring resources
and visualization of failures).
In the future, this will also link with each product to enable detection of performance errors and bottlenecks through
prediction monitoring to reallocate resources according to policy settings (performance/workload management).
For examples, these functions permit monitoring in details the operational status such as the usage rate of middleware,
CPU and memory running on the server in order to allocate servers with sufficient processing capabilities to middleware
degraded in performance. The reallocation is performed according to the policies with existing load balancer. (sharing
of resources and optimized allocation of resources).
Also, this realizes continued business on the network and simplified operation management by guaranteeing avoiding
errors and automation of recovery by linking between nodes, and an accurate grasp of and compatibility of physical and
logical layers. This automatically realizes selection of the optimum communication path and ensures communication
bandwidth.
The Autonomous System Infrastructure constantly grasps and manages service levels over the entire system. This
conserves and automates customer work (visualization of service status). This realizes an autonomous system for
which service levels can be guaranteed.
TRIOLE Technical White Paper
All Rights Reserved. Copyright © FUJITSU 2004 41
Fig. 4-6 Visualization of Service Status
End-userEnd-userresponseresponse
Visualization ofVisualization ofservice levelsservice levels
Visualization ofservice levels
End-userresponse
Systemwalker Service Quality Coordinator notifies Systemwalker Centric Manager of the response status
Systemwalker Service Quality Coordinator visualizes and analyzes the overall performance of resources that configure the service
Systemwalker Centric Manager (monitoring)
Systemwalker Service Quality Coordinator
End userStorageStorageStorage
Network
Webservers
AP
servers
DB
servers
(4) Application to products from Other Companies
Publishing the API of the relationship management, resource demands and completion notification of SystemwalkerResource Coordinator allows it to control products from other companies. To strengthen the Autonomous System Infra-
structure and links with third party products, Fujitsu is making efforts for the publishing of API.
4.3 Servers and Middleware-based Optimization of Entire Customer System
To achieve non-stop operation, it is necessary to prevent customer system failure caused by hardware errors or hang-
ups caused by overload. This must be accomplished according to the service-level management of the entire customer
system as well as on a fixed number of servers.
Fujitsu expands service-level management from a single server to multiple servers and three-layered system models in
stages and ensures detailed management of performance and workload. This evolves in stages to conservation, auto-
mation and autonomy, in view of lightening the load in customer work.
(1) Enhancing the continuation of operation
Fujitsu believes that the base of workload management in three-layered system models is to control the application
program (AP) server. We provide the following solutions to CPU or memory contention among multiple application pro-
grams in the AP server:
Prevention of performance degradation as online processing and batch processing coexist
When two or more business applications are in the same server, the load of applications with low-priority such as
batch processing affect the processing capabilities of applications with high-priority such as online processing, caus-
ing degradation in the response time and the throughput of online applications.
The Autonomous System Infrastructure and middleware (such as Interstage) jointly allocate CPU resources preferen-
tially in order not to allow crowded transactions to exceed the allowable range resources, and also coordinate the
multiplicity of application programs to prevent degradation in their performance.
All Rights Reserved. Copyright © FUJITSU 2004
TRIOLE Technical White Paper
42
Batch job priority decisions
The Autonomous System Infrastructure and Systemwalker OperationMGR jointly allocate CPU resources and decide
the priorities for batch jobs according to the batch priority.
Dynamic coordination of load fluctuations caused by mixed applications
Online applications and B2B applications may cause imbalanced load fluctuations in a weekly or monthly cycle such
as on settlement day (claim/payment) and the patterns of the load fluctuations cannot be duplicated and are compli-
cated. Usually, only the fixed allocation of CPU resources cannot respond to these complicated applications.
The Autonomous System Infrastructure can analyze the patterns of load fluctuations and make recommendations
based on the analytical data, which the operator can use to decide how to coordinate dynamically the allocation of
CPU resources.
Optimization of AP server scalability in SMP*16 system
The AP server may not provide performance suitable for large-scale SMP. The Autonomous System Infrastructure can
optimize CPU scheduling in the SMP system with middleware resources to improve the scalability of the AP server.
Fig. 4-7 Example of Preferential resource allocation when Online and
Batch applications are mixed
- Load monitoring- Prioritized resource allocation
to online processing
Application server Application server
Online business : 70%
(high-priority)
Batch : 30%
(low-priority)
OverloadOverloadOverloadBusinessApplication
Job
Online business : 90%
Batch :10%
Minimum resources
BusinessApplication
Job
(2) Increasing the efficiency in operation
If there are still crowded transactions and the lack of resources are predicted after coordinating the server resources in
each node, the Autonomous System Infrastructure will warn the operator to perform the following processing. In this
case, the Resource Coordinator presents performance information on applications across two or more AP servers to the
operator to assist in the operator’s decision.
Workload Adjustment by Provisioning*17
The Autonomous System Infrastructure will generate software configurations necessary for the AP servers and Web
servers as nodes in the shared server pool and dynamically incorporate them into the AP servers and Web servers as
needed.
*16 SMP Abbreviation of Symmetric Multi Processor. Multi-processing method that enables a multiple of CPU to behave as basically the same one.*17 Provisioning Function for allocating resources that have been pooled in advance, quickly to users.
TRIOLE Technical White Paper
All Rights Reserved. Copyright © FUJITSU 2004 43
Fig. 4-8 Workload Adjustment through Provisioning
Netw
ork
Adjustment between nodes
Web server AP server server
Server pool
Interstage Interstage
Applications
Added server nodes(Install Interstage and add
to AP server group)
Symfoware
Perfo
rman
ce
data
Mu
ltiplic
ityad
justm
en
t R
eso
urc
es
Reso
urc
es
Reso
urc
es
Perfo
rman
ce
satu
ratio
n
Performance /Workload management
Performance /
Workload management
IT resource configuration /
Fault management
WarningManual control Node addition
Pro
vis
ion
ing
Virtual and AutonomousSystem Infrastructure
Changes of partition and coordination of resources by changing partition
The Autonomous System Infrastructure changes the partition boundaries to allocate resources preferentially to higher-priority applications that have insufficient resources.
Fig. 4-9 Coordination of Resource Allocation by Changing Partitions
LSB : Logical System Board
Business
application
Replacement at
the appropriate
time
Addition of backup LSB
Addition o
f back
up LSB
Job
Batch
Business
application
Online B
Physical node
Memory
CPU
CPU
LSB0
Memory
CPU
CPU
LSB1
Memory
CPU
CPU
LSB2
Memory
CPU
CPU
LSB3
Memory
CPU
CPU
LSB4
Memory
CPU
CPU
LSB5
Physical node
Partitio
n-P
oo
l
Memory
CPU
CPU
LSB0
Memory
CPU
CPU
LSB1
Memory
CPU
CPU
LSB4
Memory
CPU
CPU
LSB2
Memory
CPU
CPU
LSB3
Memory
CPU
CPU
LSB5
Application A
Application B Overload
1
2
Partitio
n-B
Partitio
n-B
Partitio
n-A
Partitio
n-A
All Rights Reserved. Copyright © FUJITSU 2004
TRIOLE Technical White Paper
44
Operation management of blade servers
The Autonomous System Infrastructure pools servers by IT resource virtualization, and distributes loads by dynami-
cally adding servers according to use (Virtual Server Pool). Also, this unifies configuration information that changes
from introduction to maintenance, for management, to combine introduction and design work. The locations of fail-
ures and range of affects are visualized so it is possible to quickly handle, by allocating spare servers, etc., and to
recover.
Fig. 4-10 Integration of Operation Management Through Resource Virtualization
Failure detectionBatch installation / Batch installation /
setting setting
Batch installation /
setting
Visualizing
Instruction
ConfigurationManagement
Resource management
VLAN
OS
Software
Policy
Re-development
Introduction Operation Maintenance
Switch
VLAN 1 VLAN 2
Web 1
Web 2
Web
1
Web
2
Web
2
Web
1
Web
2
Web
1
Web
2
Web
1
Web
2
Web
1
Web
2
Web
1
Web
2
Switch
VLAN 1 VLAN 2
Sp
are
reso
urc
e
Switch
VLAN 1 VLAN 2
Sp
are
reso
urc
e
Server pool in data center
The Autonomous System Infrastructure pools backup resources in the data center and allocates them according to
load. To keep the service level, the Autonomous System Infrastructure monitors the load status of each server to
control autonomically the load balance and resources to be supplied to applications on the entire customer system.
4.4 Enhancing Storage Operation Monitoring Functions
As storage networking advances, storage can be integrated independent of the servers, enabling a reduction in the cost
of operations management and data sharing. On the other hand, problems associated with operations management
and fault measurement arise.
Fujitsu promises to realize stable & reliable systems and reduced TCO using a storage management mechanism that
manages storage-related resources comprehensively using the Autonomous System Infrastructure from entired system
of view.
(1) Grasping Allocation of resources and visualization of failures and impacts
Problems associated with complicated storage networks
With the complexity of the storage networks, considerable skills and effort are required to design and develop hard-
ware configurations, and design and operate backups. Furthermore, the prediction of the correspondence between
data used in application programs and the storage disk required is getting more difficult, taking more time and efforts
to identify the cause and impact in the event of trouble.
TRIOLE Technical White Paper
All Rights Reserved. Copyright © FUJITSU 2004 45
Solution by integrated storage management mechanism
Fujitsu will integrate and control storage-related resources to solve these problems (storage SLM*18 mechanism).
The storage SLM mechanism enables nonstop operation, sever independence and autonomous backup/recovery which
are preconditions for the stable and reliable operation of the customer system.
Access path display function
The access path and connection relationship between the database used in application programs and the physical
disk can be listed on a screen. Customer can understand which data and applications on the server are to be affected
instantly when a failure occurs. Thus during system maintenance, system replacement, and performance tuning, they
can minimize the impact on applications.
Fig. 4-11 Access Path Display Function
Server
Switch
Storage
Database
File system
Cluster
Volume Manager
HBA
Channel Port
Logical Volume
RAID Group
Disk
Switch
Switch Port
Range of failure effects
Precise failure detection
Automatic configuration design/development function
In existing customer systems, storage SLM reads definition and connection information on each component to choose
the most suitable sample configuration out of the multiple sample configurations to design a new configuration. Based
on the information, this mechanism generates definition information on each component automatically to design the
most suitable configuration in terms of reliability and performance according to the policy setting.
*18 SLM Abbreviation of service level management. Manages network quality with details numerical values, such as latency, throughput and usability.
All Rights Reserved. Copyright © FUJITSU 2004
TRIOLE Technical White Paper
46
Fig. 4-12 Automatic Configuration Design/Mechanism Function
3. Save3. Saveconfigurationconfigurationinformationinformation
2. Compatibility2. Compatibility
checkschecks
2. Compatibility
checks
3. Saveconfigurationinformation
1. System1. Systemconfigurationconfigurationdesigndesign
1. Systemconfigurationdesign
Storage
Switch
File system
driver
HBA
Edit screen
New introduction
Expansion
SettingSetting To siteTo siteTo siteSetting
Space
Reliability
Performance
Sample configuration Policy input
Load sampleLoad sampleLoad sampleAutomatic configurationAutomatic configuration
based on policybased on policy
Automatic configuration
based on policyNG!NG!
Correct problem locationCorrect problem location
NG!
Correct problem location
Load currentLoad currentconfigurationconfigurationLoad currentconfiguration
Realize storage system design with single view
Easy design using sample configuration and resource policies
Accurate configuration check screen of a GUI base
Suppress design mistakes with integrated check mechanism
Environment
Configuration information
(2) Expansion of the range of technology from storage SLM to IP storage
Fujitsu will expand the technology of storage SLM from FC-SAN to IP storage (NAS or iSCSI) to further extend to thebroadband storage network between the data centers. It aims to guarantee the security of storage access and quality of
services QoS in order to ensure safety and stability.
(3) Provisioning based on virtual storage pools
Fujitsu will realize provisioning that optimally supplies resources that meet predetermined service levels and policies to
applications with virtual storage pools that integrate storage.
For example, Fujitsu will provide on demand storage space that is based on requirements of data volumes, performance
and reliability. Furthermore, this will support the optimized arrangement of server resources by linking with provisioning
and on demand systems for servers and networks.
TRIOLE Technical White Paper
All Rights Reserved. Copyright © FUJITSU 2004 47
Fig. 4-13 Future Expansion of Storage
Storage network
IIP-SANP-SANFC-SC-SAN
Storage pool
Storage
Managementserver
Virtualizationand autonomousbackup control
SpaceSpace
IP-SANFC-SAN
Space
Data
man
ag
em
en
t an
du
se re
qu
irem
en
t
4.5 Network-based Optimization of Entire Customer System
Our customers face many difficult issues that accompany the move to large scale and complex IT systems and networks.
Fujitsu will realize high reliability of the entire network by applying autonomous and virtualization technologies to serv-
ers and network devices that compose the network, to overcome customer issues.
Fujitsu also is working on achieving stable communications, continuous applications, and simple network operation
management to provide high-reliability IT systems. This consists of various servers and network products including
those from other companies with different capabilities and functions.
(1) Stable communication - Sharing and optimum allocation of resources -
For load concentration and sudden load fluctuations, a server load balancer virtualizes the server and regulated the
communication load according to the operational status of the server to ensure business application response.
For sudden load fluctuations and increases, a server pool is provided in conjunction with the Autonomous System
Infrastructure.
Fujitsu will incorporate routing path management and congestion control technology into the shaping (band control)
function to automatically adjust communication load, such as wide-area load distribution and error recovery on a wide
range of networks.
(2) Continuous operation - Visualization of failure -
Fujitsu duplicates the system and communication path to achieve continuous operation for failures in network equip-
ment.
In the future, Fujitsu enhances the monitoring function in the network to grasp the status of the entire network to visual-
ize where the error occurs, by linking with the Autonomous System Infrastructure for performance error, intermittent
failure, and failure on one side of communication path caused by insufficient processing capabilities and overload. To
do so, grasping the configuration information of network devices in the center, Fujitsu unify this with server and storage
configuration information.
All Rights Reserved. Copyright © FUJITSU 2004
TRIOLE Technical White Paper
48
Fig. 4-14 Monitoring Network Errors
1. Node monitoring;
monitoring its own by creating a redundant; configuration
2. Link monitoring;
monitoring connecting ports and cables between switches
3. Other node monitoring;
Failure analysis and automatic recovery
Node
SW
SW
Node
Node
Node
Node NodeSW SWLowfunction mode
Node NodeSW SWLow
function mode
The combination of 2 and 3 can support recovery of networkdevices with low detection capability (see below).
Change over of node at both ends
1
SW : Switch
1 3
2
Fujitsu will provide criteria information required when the operator intervenes in the event of a failure. This is to shorten
the time taken from detection of an error until identification of the location of the error and minimize the operator’s
intervention and allowing support for a 24 hours a day 356 days a year continuous operation.
Fig. 4-15 Minimization of Operator’s Intervention in the Event of Failure
Operator and
operation manager
verify the error
5. Operator NotificationVirtual and AutonomousVirtual and AutonomousSystem InfrastructureSystem InfrastructureVirtual and AutonomousSystem Infrastructure
4. Information collection4. Information collection4. Information Collection
3. Resource management
2. Notification
1. Error
Detection
FW Firewall
SLB Server load balancer
Router
Switch Switch SwitchFWFW
SLB Web
Router
Switch Switch SwitchFWFW
FW
FWSLB Web
6. Assessment of the
Information
[Action]
1. Detecting a failure
2. Notifying of the failure
3. Determining a failed device based on the failure information4. Collecting troubleshooting information such as device, traffic, packet loss, etc.5. Notifying an operator6. The operator takes corrective action - network switchover
Internet
TRIOLE Technical White Paper
All Rights Reserved. Copyright © FUJITSU 2004 49
(3) Simple network operations management - Autodiscovery of configuration resources -
TRIOLE accurately autodiscovers the physical configuration (equipment, server physical connection) and logical topog-
raphy information (IP address, VLAN, sub-net) of the network and the compatibility between those configurations. This
helps to ensure the connectivity of the entire customer systems and the compatibility between communication param-
eters and network design toward the business SLA*19.
Fujitsu will also make efforts on automation to avoid the effects of network errors on applications and the recovery from
the error. This also includes automation of design/compatibility tests at the time of introduction and configuration change.
Fig. 4-16 From Network Monitoring to Autonomous Control
IP-VPNIP-VPNIP-VPN
Wide-range EtherWide-range EtherWide-range Ether
Monitoring and MeasurementAnalysis
Visualization of Failures
Based on Network Topology
Operation
Configuration
Change Control
Network operation monitoring
(Operating status/traffic)
Network device error
monitoring
In-server network monitoring
(Layer 4 monitoring)
Branch Router
Targeted network
Router FW SLB
Web servers AP servers
DB
servers
SW
FW SLB
SW SW
SW
SW
SW
SW
SW
SW
SW
SW
SW
SW
SW
(4) Integration of system front functions
Networks for enterprise IT systems are growing from being dedicated line networks to becoming high speed, wide
bandwidth broadband networks. All-IP enables the flexible support of business changes by integrating a variety of
services that existed as individual networks.
However, to fully utilize broadband networks, a variety of functions, such as support for load variations, ensuring secu-
rity, and high reliability including the network, are in demand. Also, there is a limit to system development, by combin-
ing single function servers, such as routers, switches, firewalls and load balancers, individual functions of appliance
products, and devices.
Fujitsu integrate the functions required in IT system fronts (system fronts) into one device, with fusion the server and
network technologies that have been cultivated from the past.
This realizes a simple and highly reliable IP network environment through devices from the combination of apparatuses.
*19 SLA Abbreviation of service level agreement. Shows network quality with detailed values, such as latency and throughput. Philosophy for development maintenance
management of networks with agreements at the side providing the network and the user side.
All Rights Reserved. Copyright © FUJITSU 2004
TRIOLE Technical White Paper
50
4.6 Integrated Management and Autonomous Protection to Ensure Security
Fujitsu is making attempts for IT system security and reduced operation management costs, in view of the following
three points.
(1) Common security measures that use software products as their core
Fujitsu is taking practical measures for security at the software product development level. To ensure security, the
division developing software products has set a ‘product development guideline for security’ that conforms to ISO15408
to analyze threats to security products and to take the appropriate measures. This supports improvement of the weak-
nesses at the programming level. Furthermore, security is strengthened at the testing stage by using security weakness
inspection tools and feeding back those results to the product design/development groups.
By equipping each of the products that compose the IT infrastructure ‘TRIOLE’ with security functions based on the core
technologies for protection control using ‘automation’ and operation management using ‘integration’, we can strengthen
the security of the overall system.
(2) Providing systems with security measures in place through Platform Integration
This provides standard security settings already applied to the basic software (OS) and middleware, and standardly
incorporates security products in Pi templates. This realizes complete security measures as an IT infrastructure.
Furthermore, security measures for the entire system are possible by applying Fujitsu security solutions from applica-
tion layers, infrastructure layers and organizational regulation layers.
(3) Providing ‘automated’ and ‘integrated’ security measures
Protecting the customer system from atacks requires some measures (periodical audit and update) including Web appli-
cation operation as well as the use of a firewall and products for detecting illegal intrusion and virus attacks.
Also, for the operations management of security, some measures against the ever-changing threat of security are always
required, which becomes a burden to customer in terms of cost. For this reason, integrated and autonomous security
management is necessary, and it aims reduction of the operation load. It is especially important to protect illegal access
at the system front-end and realize the following functions.
Integration of access security function
This integrates system front-end security functions to monitor for illegal access. When illegal access are detected,
these are handled based on security policy and setting of security functions are changed autonomously.
Because illegal accesses detection and firewalls cannot completely prevent illegal accesses that maliciously use se-
curity holes, this analyzes the web access before damage occurs to automatically shut it down.
TRIOLE Technical White Paper
All Rights Reserved. Copyright © FUJITSU 2004 51
Fig. 4-17 Integrated Security Management at the System Front-end
for Illegal Access Measures
Viruscheck- SV
Appl. GW Web-SV
Internet
Router
Firewall Firewall
DMZ*20
Operation management - SV
4. Setting
4. Setting 4. Setting
2. Notification
3. Integrating system front-end security functions
can determine how to take action against illegal
access according to the policy settings.
4. Setting1. Virus check 1. Illegal access detection
Intra
net
2. Notification
IDS
1. Intrusiondetection IDS
AuthenticationAuthentication
- SV- SV
AuthenticationAuthentication
- SV- SV
Authentication
- SV
Autonomous Protection Against Viruses
This integrates management of security patches for each device and application information for virus protection pat-
tern files. This links with network authentication and does not allow devices that do not have enough security mea-
sures to connect to networks to automatically protect against virus infections.
Information leak measures
DRM*21 technology is very important for information leaks caused by human error and those that are malicious in
intent. Access control is strongly executed on users and groups to prevent information leaks from internal personnel.
Also, data is constantly encrypted. Decrypting is possible only when conditions for consent are met. By applying
these kinds of technologies to middleware, it is possible to prevent malicious information leaks.
*20 DMZ Region separated from both external networks and internal networks by a firewall, on a network connected to the Internet.
*21 DRM Digital Rights Technology.
All Rights Reserved. Copyright © FUJITSU 2004
TRIOLE Technical White Paper
52
Fig. 4-18 Information Leak Measures
Measures against deliberate information leaks from outside Measures against deliberate information leaks from outside Measures against deliberate information leaks from outside
Measure againstinadvertent information
leaks from inside
Measures against deliberate information leaks from inside
Zoning *22
Room entry management system
DRM
VPN
PC use limitsMail filter *23
Hard disk encryption
Integrated validation/authentication management
The protection of personal information and the security technology of the authentication system which users can use
with confidence are indispensable in a ubiquitous network society.
In the customer system using the Web server as a core, for example, validation/authentication is needed for each Web
server and application, which becomes a large burden to customers and operators. For example, to reduce the load
on users, a simplified log-in operation using a single sign-on is in demand. Also, to ensure security, it is necessary to
limit the clients (PCs, etc.) that can connect to the network.
Fujitsu is striving for integrated management of authentication/validation information including current systems by
applying security policies. To ensure security when handy terminals (such as laptop computers) connect to a network,
this integrates with wireless LAN, including cable LAN, based on authentication when connecting to a network, using
IEEE802.1x.
4.7 Stable and Reliable Systems through its Life Cycle
For the stable and reliable operation of the customer system and reduced TCO, support is indispensable after starting
operations. Fujitsu provides REMCS (see Section 1.2 TRIOLE) to realize the stable and reliable operation of the cus-
tomer system throughout its entire life cycle.
(1) Reduction in the workload of the customer systems operation manager
Fujitsu REMCS is a support system that always monitors, analyzes and predicts the status of the customer system after
starting operations from the remote center. It provides high-quality support services. Preventive maintenance with REMCS
promises stable operations and quick troubleshooting to reduce workload for the customer system operations manager.
*22 Zoning Leak measures according to equipment level, such as server arrangements.*23 Mail filter Function for causing sometime of action if conditions are met, when the contents of mail are read by a predetermined defined setting.
TRIOLE Technical White Paper
All Rights Reserved. Copyright © FUJITSU 2004 53
Fig. 4-19 Basic Functions of REMCS
OperationOperationInformationInformationOperation
Information
Customer Site
REMCS CenterField Department
Servicedepartment
Development Department
Database
CorrectionCorrection
informationinformation
FailureFailureInformationInformation
Correction
information
FailureInformation
Internet
Registration
Remote Monitoring
Remote Monitoring
InformationCollection
REMCSAgent
Autonomous control
mechanismProvidedCorrections
Security/communicationmanagement
REMCS-Web
REMCS-Web
REMCS-Web
Link
Link
REMCS
MS
Analysis
/
display
Platform
CustomerCustomerinformationinformationCustomer
information
SystemSystem
SystemInformationInformationInformation
(2) Enhancement of the support infrastructure
Toward the stable and reliable operation of the customer system and reduced TCO, Fujitsu will provide high qualitysupport by linking with the autonomous control mechanism of each product and with the Autonomous System Infra-
structure.
All Rights Reserved. Copyright © FUJITSU 2004
TRIOLE Technical White Paper
54
memo
TRIOLE Technical White Paper
All Rights Reserved. Copyright © FUJITSU 2004 55
Chapter 5
Platform Integration
All Rights Reserved. Copyright © FUJITSU 2004
TRIOLE Technical White Paper
56
Chapter 5 Platform Integration
- ‘Platform Integration’ ,which realizes highly reliable systems and reduces time and cost: -
Platform integration systematizes pattern of the high reliability system by analyzing and veri-
fying variety of case studies in the past, and provide it as ‘Pi template’. By using the Pi tem-
plate which guarantees quality and reliability of its model, you will be able to build up highly
consistent platforms.
5.1 The goal of Platform Integration
As IT environment changes quicly today, the market is more focused on how to build up new system quickly and
improve system reliability. On the other hand, although using open system have the benefit of having the latest tech-
nologies, the problem is that IT engineers have to gather and combine different types of products,which is painful for
system engineers to guarantee the compatibility and consistency of those products.
Fujitsu’s Platform integration eliminates such system complexities by using an approach of system modeling, and thereby
enabes development, update, and expansion of the system in a short term.
Also, Fujitsu defines variety of high reliable system platform which includes both Fujitsu and carefully-selected other
vender’s product, and provides it as pre-tested, quality-guaranteed model.
5.2 Pi Templates
(1) Pi Template features
Fujitsu’s TRIOLE defines integrated platform as ‘Pi template’, leveraging flexibility of selecting open technology based
products.
Pi templates consists of servers, storage, networks and middleware products which have the leading technologies and
are carefully selected by Fujitsu. Those open products are well-known and have variety of case studies. Also Fujitsu
provides documents and tools used for the system design and in development phase in order to be able to build up
system easily and in a shortterm. Thus Fujitsu’s Pi template enables to build up new IT systems quickly to allow cus-
tomer to catch up the latest market trend.
Reliability, expandability, performance and security technology, designed and pre-tested by experts for realizing stable
system, are embedded in the Pi template.
TRIOLE Technical White Paper
All Rights Reserved. Copyright © FUJITSU 2004 57
Fig. 5-1 Features of Pi Templates
Leading TechnologyComposed of products that have the leading technologiesand selected for server, storage, networks and middle-ware
SpeedSpeeding up of each phase from proposal to system development.
Stable OperationIncorporate reliability, expandability, performanceand security everywhere for the stability of system operation
(2) Systems requirement and Pi Templates
Fujitsu defines Pi template as pre-designed and pre-tested model of availability, fault-tolerance, reliability, scalability
and performance, and provide it accordingly to your requirement.
Platform integration consists of carefully selected, formalized, and equalized elements in the Pi template and thus Fujitsu
believe it will enable to build up new stable system in a short term.
5.3 Contiguration of Pi Templates
(1) Basic Templates
Current typical IT systems consists of three tiers: ‘web servers’, ‘application servers’, and ‘database servers’. The IT
system can be additionally divided into the segment of function and role such as the ‘system front’ block including
router, switch or load balancer, ‘operation management’ which manages the entire system, ‘XML hub’ which converts
business systems into XML format data, and ‘backup’ for saving data.
In a concept of the Pi templates, those segments are independently defined as “basic templates”. The basic templates
are easily deployed into existing systems independently. This is called ‘building block method’ and it enables the devel-
opment of high quality systems in a short-term.
All Rights Reserved. Copyright © FUJITSU 2004
TRIOLE Technical White Paper
58
Fig. 5-2 Pi Templates
Router F/W IPCOM SW SW DB-SV Monitor-SV
Web-SV Ls-Trd AP-SV
Other Systems
SW HUB-SV Backup-SV Tape Library
Mutual testing and load testing combining all blocks
Building Block Development for Short-term Development of High Quality Systems
Ex.: Add-in to Existing System Sta
nd
ard
ized
Syste
m
Co
nfig
ura
tion
/
Test D
ocu
men
t
Internet Front
Existing System
Existing SystemExisting System
Internet Front Web Application Business Application Database Operation Management
XML Hub Backup
Basic Pi template: Separation and verification of the IT Infrastructure in its basic function blocks
Internet
(2) Line up of Basic Templates
Pi templates defines basic templates for the following functions and roles individually. Furthermore, the basic templates
for each segment has some variations accordingly for the purpose and use. These templates consist of servers
(PRIMEPOWER/Solaris, PRIMERGY/Linux and Windows) which are a backdrop to TRIOLE’s automation, virtualization
and integration, storage units (ETERNUS), networks (GeoStream and IPCOM) and middleware (Interstage, Systemwalker,
Symfoware, Oracle).
System front
System front template provides high reliability and availability at boundary between IP networks (Internet and Intranet)
and server groups by three functions: robust security to protect them from illegal access from outside, load balancing
that supports sudden load variations, and redundancy of devices.
Web Application
Web Application template provides an environment that enables users the use of business applications over the
Internet via their browser. The Web application template also provides functions that manage user authentication over
multiple web servers with single authentication server for additional web server in the future.
Business application
Business Application template handles business processes accordingly the request from the web applications. Also,
the business application template provides functions for requesting database processing to the database server and
for send ing back the processing results to the web server.
Database
Database template defines high reliability and high performance database processing to data access requests from
application servers.
Operation management
Operation management template provides an operation management function for monitoring operations of all servers
and devices in the system, and for managing operating log.
TRIOLE Technical White Paper
All Rights Reserved. Copyright © FUJITSU 2004 59
XML Hub
XML Hub template defines a hub environment for converting individual data of a business system into XML format data
for integration.
Backup
Backup template defines centralization of controlling backup operations and unified management functions for backup
targets and backup media, to backup entire system data.
(3) Combination Templates
According to analyzes of pilot examples, ‘combination templates’ combines some basic templates that are frequently
used.
Web transaction system (Internet type)
This is a template that defines a typical three-tiered (Web sever, AP server, and DB server) model.
Web transaction system (Intranet type)
This is a template that defines the Intranet system to realizes a two-tiered (Web/AP servers, and DB server) model.
XML Real-time information application
This template integrates data on each business system using an XML data format. It also uses web applications to
realize high speed searches of integrated XLM data.
Customer requirements are expanding more to handle changes in business environments, and IT systems are con-
stantly evolving.
Pi templates will be gradually amplified by separating them for system formats, purpose and usage that meet customer
needs in the future.
Fig. 5-3 Expansion of Pi TemplatesIn
tern
et fro
nt
Bu
siness
Ap
plic
atio
n
data
base
Op
era
tion
man
ag
em
en
t
Intra
net
Backu
p
Web
ap
plic
atio
ns
XML
XML
hu
b
d
ata
base
Operation managementOperation management
databasedatabase
Internet frontInternet front
BusinessBusinessApplicationApplication
Internet frontInternet front
BusinessBusinessApplicationApplication
Strengthen optimum template product lineup from analysis of customer needsFurther enhance for combination templates
Sequentially expand
templates for
system format,
for purpose,
and for use
Web 3-tiered (Basic full configuration)
Intra
net
Intra
net
Multi-dimension
analyses
Server consolidation
etcXMLhubXMLhub
Basic templates (Solaris/Linux/Windows)
Combination templates
XMLdatabaseXMLdatabase
Intra
net
XMLhub
XMLdatabase
XML Real-time information application
Operation management
database
Internet front
BusinessApplication
Web
Web
ap
plic
atio
ns
ap
plic
atio
ns
Web
ap
plic
atio
ns
Internet front
BusinessApplication
Web
Web
ap
plic
atio
ns
ap
plic
atio
ns
Web
ap
plic
atio
ns
Web
ap
plic
atio
ns +
bu
siness a
pp
licatio
ns
All Rights Reserved. Copyright © FUJITSU 2004
TRIOLE Technical White Paper
60
5.4 Challenge to Open System
Fujitsu is providing a variety of products based on open system architectures, such as servers, storage, networks and
middleware. Pi templates consists of open system products, and include leading third party products in the market as
well as Fujitsu products. Fujitsu will continue providing system model templates by combining variety of products from
our many hardware and software partners, in Pi templates and thoroughly combine open architectures and open sources,
to satisfy our customers' requests.
Fig. 5-4 Expansion of Pi Templates
Open architecture/Contribution to application and
strengthening open sources J2EE, eclipse, SOAP,
XML, UDDI, ebXML,
Struts, Linux, IPv6 etc.
Accumulation of technologyAccumulation of technology / know-how / know-how
Accumulation of technology / know-how
Server
Storage
Network
Middle-ware
Cooperation with hardware
partners
Cooperation with software
partners
5.5 Easy-to-use Platforms with System Lifecycle
Fujitsu’s mission is to provide platforms systems that customers can easily use and confidence over the entire system
lifecycle of development, operation and expansion.
In order for our customers to be able to use their systems with ease and stability , Fujitsu provides a one-stop shop for
an IT infrastructure that realizes ‘shortened development’, ‘reliability and stability’ and ‘reduced TCO’ to enable power-
ful support to customer ‘speed business’ through platform integration.
Fujitsu continues and strengthens its platform integration to quickly solve customer business issues that are in need of
immediate adaptation to business changes.
TRIOLE Technical White Paper
All Rights Reserved. Copyright © FUJITSU 2004 61