This document summarizes tools and objects in BODS Server. It describes five main tools: Repository Manager, Server Manager, BODS management console, Metadata integrator, and License manager. It also describes two client tools: Designer and Locale Selector. Finally, it outlines two types of BODS objects - reusable objects like data flows and jobs, and single-use objects like scripts. It provides examples of projects, jobs, dataflows, and datastores as key reusable objects in BODS.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0 ratings0% found this document useful (0 votes)
52 views2 pages
Reusable Objects
This document summarizes tools and objects in BODS Server. It describes five main tools: Repository Manager, Server Manager, BODS management console, Metadata integrator, and License manager. It also describes two client tools: Designer and Locale Selector. Finally, it outlines two types of BODS objects - reusable objects like data flows and jobs, and single-use objects like scripts. It provides examples of projects, jobs, dataflows, and datastores as key reusable objects in BODS.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2
1.
BODS Server tools
I. Repository Manager:It s a tool to create repositories; It helps to check the version of the repository; upgrade repository. If BODS version gets upgraded we will upgrade the repository. It is administrator tool; desktop tool; server tool. II. Server Manager: It is a tool to create Job server, Access server; Assignment of repository to job server is done here; It is server tool ; administrator tool; desktop tool; we can do email configurations; we can define pageble memory path settings; we can do email configurations; we can do real time job configuration at receiver side. III. BODS mgmt console: IV. Metadata integrator: It is a tool which will integrate BODS and BO BI; here in BODS we will get all metadata of (universes, reports etc.) and so the impact and linage analysis; It is desktop tool; Server tool; administrator tool; we can schedule the metadata integrator to get the data from cmsdb to BODS repo with regular intervals. V. License manager: We can add, delete, modify licenses; It is a desktop tool; Administrator tool; server tool. 2. BODS Client tools I. Designer: It is a desktop application and client tool; it is a developer tool to develop BODS jobs; it supports batch job and real time jobs; it is only aapplication , it does not store data. II. Locale Selector :It will help you to select a default language of designer; Developer tool; it is client tool; it is desktop tool. III. Documentation: Technical manual of the tool. BODS Objects BODS objects are two types I. Reusable objects: A reusable object has a single definition; all calls to the object refer to that definition. Accessreusable objects through the local object library. A data flow, work flow, datastore, function etc are example of reusable objects. II. Single-use objects: Some objects are defined only within the context of a single job or data flow, for example scripts, project, loop, try-catch, conditionsetc are single use objects. Projects: A project is a reusable object that allows you to group jobs;A project is the highest level of organization offered by the software; You can use a project to group jobs that have schedules that depend on one another or that you want to monitor together. Jobs: A job is the only object you can execute. You can manually execute and test jobs in development. Dataflow: It is an object to define a ETL definition in BODS (what to extract, how to extract and where to load). Workflow: It is an object which helps in grouping of data flows (or) grouping of set of ETL operations Datastores: Datastores represent connection configurations between the software and databases or applications: There are three kinds of Datastores: I. Database Datastores:provide a simple way to import metadata directly froma RDBMS. II. Application Datastores:let users easily import metadata from mostEnterprise Resource Planning (ERP) systems. III. Adapter Datastores:can provide access to an application’s data and metadataor just metadata. For example, if the data source is SQL-compatible, theadapter might be designed to access metadata, while Data Services extractsdata from or loads data directly to the application.