Bfc Presentation

  • 602 views
Uploaded on

Short presentation of BFC framework

Short presentation of BFC framework

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
602
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
2
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Base/1 Foundation Application Presentation Godina Filip
  • 2. What is BFC ?
    • RAD toolkit
    • Allows building of secure database applications with C# and ASP.NET
    • “ Database-centric” architecture
    • Supports major databases: Microsoft, Oracle, IBM, Sybase, MySQL
  • 3. Features
    • Supports and extends leading databases
      • Data Dictionary: component used throughout BFC which provides a description of records layout and indexes
    • Integration into Windows development (with Visual Studio)
    • Single, consistent API
      • Database access is wrapped with an easy-to-learn API accessible with .NET, COM or MFC
  • 4. Features
    • Rich client applications
    • Distributed processing
    • Enhanced security
      • for checking/changing passwords, grouping users and granting/revoking database privileges
      • setting per-application access privileges on the basis of user groups
      • security groups
      • specifying prohibited actions
      • database session monitoring
  • 5. Architecture
    • Grid computing: uses a “virtual supercomputer”, comprised of loosely coupled “batch job servers”
    • Three parts:
      • Rich client core components
      • Distributed batch processing services
      • Grid computing middleware
  • 6. Rich client core components
  • 7. Distributed batch processing services
    • Large jobs are broken down into smaller pieces that can be run individually
      • fault-tolerant
      • supports a high degree of database concurrency
      • automatically balances workload across a dynamic pool of available PCs
  • 8. Grid computing middleware
    • the layer that ties together all the distributed components into a virtual supercomputer for large database applications
  • 9. Base/1 Foundation Application Advantages Cracaoanu Sergiu
  • 10. BFC advantages – General Benefits
    • Lower cost of development and operations , in some cases cost has been reduced as much as 85%
    • Faster implementation and deployment, Customers can quickly prototype a distributed solution by using the BFC , which includes a large selection of programming tools and sample templates.
  • 11. BFC advantages – General Benefits
    • Secure, industrial-strength applications : Deutsche Bank's Securities Custody System is one of the earliest successful examples of commercial grid computing. This large-scale financial application demonstrates the substantially lower costs and higher return on investment possible with Base One's distributed processing software, as compared to traditional architectures.
  • 12. BFC advantages – Technical Benefits
    • Faster development through .NET and COM : C#, VB, VB.NET, ASP, ASP.NET (for web sites), VC++, and any other language that supports the popular COM or .NET  interfaces can use BFC components to do database access and security control
  • 13. BFC advantages – Technical Benefits
    • Base One is integrated with commercial database environments, Base One operates through ODBC drivers and high-efficiency, direct connections to Microsoft SQL Server and Access, Oracle, IBM DB2, Sybase, and MySQL. (ADO.NET data providers are not required.) Databases can reside on Windows, Unix/Linux, and IBM midrange (AS400) and mainframe servers
  • 14. BFC advantages – Technical Benefits
    • With Base One distributed computing technology, large-scale business and scientific applications are significantly less expensive to build, maintain, and administer and they are faster to implement.
  • 15. BFC advantages – Technical Benefits
    • The benefits of Base One's approach derive not from specialization, but just the opposite: employing ordinary, under-utilized computer resources and using well established software technologies for database management and rapid application development.
  • 16. BFC advantages – Technical Benefits
    • This dramatically reduces the total cost of ownership (TCO), with savings on the cost of new equipment and accompanying system software, as well as lower cost of programming. The net result is faster development and deployment of maintainable, production applications.
  • 17. BFC disadvantages and Limitations
    • One of the disadvantages involved by using this product is that it is not free
    • The main limitations for BFC are that it runs only on Windows OS and the only IDE accepted is Microsoft Visual Studio .NET 2008 SP1. So Microsoft dependence is the main limitation.
  • 18. Base/1 Foundation Application Tutorial Herea Adrian
  • 19. Log On
  • 20. Autocorrect if the previous session failed
  • 21. USER TYPES AND DATABASE LOGONS
    • Full User
    • A "regular" user with a real database logon, e.g. "OWNER"
    • Lite User
    • Lightweight user. NOT a real database logon, e.g. "LITE01”
    • Full Batch User
    • For grid, cluster, distributed computing; real Db logon
    • Lite Batch User
    • Same features as Full Batch User but NOT a real Db logon
    • Super User
    • Does database access for Lite and Lite Batch Users
    • Database Setup User
    • For connecting to an "empty" database
  • 22. .INI file
    • All of the Base/1 Foundation Application's database connection settings come from its .INI file, B1_App.ini.
    • the default search order is to look for the .INI file first in the current directory and then in the windows directory
  • 23. Database settings in the .ini file
    • DbNam (Database Name), always required
    • DbTyp (Database Type), always required
    • Back end database system (DBMS) to be used, e.g. MSSQLSERVER
    • DbQualifierStr (Database Qualifier String), required for most database types e.g. schema, owner or database name
    • DbServId (Database Server ID), required for most database types e.g. server name or (local)
    • DbConnTyp (Database Connection Type), optional ODBC, except for Oracle (DirectAPI); can be left blank
    • DbSetupUsrId (Database Setup User ID), required but only for certain activities The Login ID used for initial creation of the BFC built-in record types
    • InetServHostAddr (Internet Server Host Address), optional Remote location (I.P. address, URL) of a database accessed via BIS
    • InetServPortNum (Internet Server Port Number), only required if HostAddr used Port number to use on an Internet Server (BIS) for doing database access
    • SuperUsrId (Super User ID), optional Real database login used by Lite Users for data access
    • SuperUsrPassw (Super User Password), only required if SuperUsrId is supplied Password for Super User. (This model assumes a secure room for computers)
  • 24. Run batch jobs - summary
    • Build the necessary solutions
    • Submit a batch job
    • Start the batch job manager, which finds and does the work
  • 25. Run Distributed Batch Processing Services
    • Administrators and other interactive users can submit work to be picked up asynchronously by any batch machines that are available
    • MS Access is NOT suitable for multiple batch machines running together:
  • 26. Run the Foundation App with a Remote Internet Server
    • Install BFC on a second PC to run the Internet Server
    • Obtain the IP Address of the PC running the Internet Server.
    • Set the Internet Server TCP/IP Information for the Foundation Application
    • Optionally, set the Internet Server Internet Report Path.
    • Launch the Internet Server and the Foundation Application
    • For production systems, use BIS only on Win2000 or Win2003.
    • Client applications that are installed on XP connect to BIS on Win2000 or Win20003 without any problem
  • 27. 'XML Parsing Error ' If the source code is correct Possible Solution: Reinstall the ASP.NET Possible Problem: ASP.NET installed after IIS.
  • 28. Other problems
    • The Directory where Access database is should be a virtual directory shared in network
    • The .ini file should be well configured
  • 29. The End