Installation of BODS 4.0
Prerequisites:
Ø Database
(MY SQL)
Ø Web
Application Server(WAS) Ex: Tomcat,Jboss
Supported
Platform:
Hardware
·
64 bit
·
RAM Minimum(8GB-16GB)
·
Hard Disk(40 GB)
Operating System(OS)
·
64 bit server(OS)
·
64/32 bit client os
PAM(Product Availability Matrix), SMP(Service Market
Place) for BODS 4.0 in windows/unix
BODS Tools
CMC/IPS Tools
|
BODS Server Tools
|
BODS Client Tools
|
CCM->CMS
|
Repository Manager
|
BODS Designer
|
CMC
|
Server Manager
|
Local Selector
|
LCM
|
BODS Management Console
|
Documentation
|
UMT
|
Meta Data Integrator
|
|
WDT
|
License Manager
|
|
CMC/IPS Tools:
1.
Central Configuration
Manager(CCM):
·
Type: Desktop Tool/Server
Tool/Administrator Tool
·
Function: BO Server Management (which we
can manage platform services & servers)
·
Add additional BO server (SIA)
·
SIA -Clustering/Backup CMS DB/Restoring
of CMS DB
·
Management of BO Services/server
w.r.to
BODS
CCM
has CMS and EIM
Ø CMS
(Central Management Server) will create interface b/w BO application &
repository.
Ø EIM
Adaptive Processing Server use when we connect in between RFC and BODS. If EIM
Services is nt working /down then we can’t create RFC communication for SAP
extraction.
Note: Input/ Output file repository services: we can’t
save to repository and we can’t access doc's from repository
2.
CMC (Central Management
Console)
·
Type: webapp/administration tool/server
tool
·
URL:http://<IPS/CMC
Server>:<WAS Port>/BOE/CMC
·
Ex: http://localhost:8080/BOE/CMC
·
Function : BODS Repository Management,
User management, security management(content/user), license management
3.
LCM(Life Cycle Mnagement
Console)
·
Type: web/server/administrator
·
Function: Deployeement of BOE Content
(CMS content)/ version managemnt tool
·
URL:
http://<IPS/cmcserver>:<WAS port>/BOE/LCM
·
SP05 onwards LCM integrated with cMC as
Promotion management, sub version management
·
CMS DB content only we can move using
LCM
4.
UMT(Upgrade Management Tool)
·
Two types- Full upgrade/ increment
upgrade
·
Type:Desktop/administration tool/server
tool
·
Function:upgrading/migrating BOE content
& application from lower 4.0 version to higher 4.1 version
Ø Import wizard
·
IW(Import wizard 3.x)=LCM(4.0)+UMT(4.1)
·
Source and destination system will be
same version
·
Import wizard doesn’t support Rollback
·
No version management
·
No scheduling deployment
·
No log maintenance
5.
Web Deployment Tool
·
Type: Desktop/server/administrator tool
·
Function: web application deployment
tool. .WAR files deploy into Web Application Server(WAS) ie. Tomcats, IIS, Web
logic..etc. The .war files are located in BOE installation directory/BOE/War
files folder.
·
BODS4.0upgrademgr.exe in bin folder, we
will get this along with BODS 4.0 installation
BODS Server Tools:
1.
Repository Manager
·
It is a tool to create repositories
·
DB->Repository Manager->Repository
·
Types: 3 types of repositories at DB
level
·
Local: Store the metadata of designer
·
Central: to enable version management
& multi user working environment
·
Profile: to perform data assessment.. measuring
& analyzing the data
·
4th type of repository at OS level not
DB level
·
Directories is also one kind of
repositories which stores cleansing packages (<LINK_DIR>/Admin/Repo)
·
all script files are version dependent
on version (4.1, 4.0)
·
all script files which will create metadata
tables in repositories
·
5 types of script files which will allows
to create repository in DB(Oracle, MS SQL, HANA, DB2..etc)
·
If BODS version was upgraded, then only
we will upgrade the repository 3.x->4.0
·
Repository Manager will also helps you
to check the version of a repository
·
It is a administrator /Desktop / Server
tool
·
Repository manager is a tool to create
repositories, upgrade repositories, check the version of a repositories
·
Cleansing packages (under reference
directory folder)
2.
Server Manager:
·
It is a server tool/ administrator tool/
desktop tool
·
It is a tool to create job server,
access server
·
It is a tool where we can define pegable
memory path settings(RJ10, RJ20..)
·
It is a tool where we can do email
configurations
·
It is a tool where we can do realtime
job configuration at receiver side
·
Run/ Restart services either manually
(services.msc) or automatic method(at server manager)
·
Assignment of repository to job server
·
If you do any activity you need to
restart a service in BODS called server manager
·
Repositories are project specific..
·
Job server, access server services are
landscape specific(Dev, QLT, Prod)
3.
Management Console
·
Type: web application/administration
application/web server
·
URL:http://local host:28080/Data
Services
4.
Metadata Integrator: (MDI)
·
It is a tool which will integrate BODS
& BOBI
·
It is Desktop/Server/Administrator tool
·
We can schedule the MDI to get the data
from CMS DB to BODS Repo with regular intervals
·
here in BODS we will get all metadata of
(universes, reports..)do the impact & leanage analysis
·
It is a tool to integrate BODS & BOE
to enable impact & leanage analysis till reports
·
BODS 4.0 onwards, system should already
contain(installed) BOE Client tools. then only we can able to install metadata
integrator(BODS Client tools)
·
Ex: If we delete these 2 tables in
source we estimate how many reports are affected in BOE
5.
License Manager:
·
we can add, delete, modify license
·
It is desktop/administrator/ server tool
·
we have to login to server to access
this ool
BODS Client Tool
1.
Designer
·
It is desktop/client tool
·
we hav eto install bods client tools
2.
Locale selector:
·
Language selector
·
It is developer/client/Desktop tool
·
It will help you to select a default
language of a designer tool
3.
Documentation:
·
Technical manual of the tool
Nice post...
ReplyDeleteWe are providing the best master data services around the world....visit our website for more information....
data cleansing tools
Master Data Governance
Data Cleansing Services
data classification tools
Master Data Management Solutions
data transformation service
Material Master Data Management