Professional Documents
Culture Documents
---------------------------------------
1.Cloud computing
1.1 Breif of cloud computing
1.2 what u did in cloud computing
2.DB2
2.1 how DB2 will be different in Cloud
2.2 biref of what you did in DB2
2.3 Breif of the Security
2.4 Breif of Physical desgin
2.5 Breif of GSK plugin
2.6 Breif of WLM
2.7 Breif of LBAC
2.8 Breif of Autoninc involved
2.9 HADR
2.10 difference between Db2 z/Os and LUW
3.SOA
3.1 breif of SOA
3.2 breif of what modules we have
3.3 steps involved in the modules
3.4 what and how???
4.Rexx command etc
5.Virtualisation
6.Fuzzy logic
7.System Z
-------------------------------------------------------------------------
cloud defination :
Common, Location-independent,Online Utility on Demand where Common implies mult
i-tenancy, not single or isolated tenancy; Utility implies pay-for-use pricing ;
on Demand implies ~infinite, ~immediate, ~invisible scalability
Alternatively, a Zero-One-Infinity definition
0 On-premise infrastructure, acquisition cost, adoption cost,support cost
1 Coherent and resilient environment not a brittle software stack
? Scalability in response to changing need,Integratability/ Interoperability wit
h legacy assets and other services
Customizability/Programmability from data, through logic, up into the us
er interface without compromising robust
multi-tenancy
------------------------------------------------------------------------
Multitenancy refers to a principle in software architecture where a single insta
nce of the software runs on a server, serving multiple client organizations (ten
ants).
------------------------------------------------------------------------
Cloud Software as a Service (SaaS)
Use provider s applications over a network
Cloud Platform as a Service (PaaS)
Deploy customer-created applications to a cloud
Cloud Infrastructure as a Service (IaaS)
Rent processing, storage, network capacity, and other fundamental computing reso
urces
-------------------------------------------------------------------------
Certificate Management System:-CMS
-------------------------
LBAC:
A security label is composed of one or more security label components. There are
three types of security label components that you can use to build your security
labels:
Sets. A set is a collection of elements where the order in which those
elements appear is not important. All elements are deemed equal.
Arrays. An array is an ordered set that can be used to represent a simple
hierarchy. In an array, the order in which the elements appear is
important. For example, the first element ranks higher than the second
element and the second higher than the third.
Trees. A tree represents a more complex hierarchy that can have multiple
nodes and branches. For example, trees can be used to represent
organizational charts. You use a security policy to define the security label
components that make up a particular security label.