Five Stages to Fast Advancement with TierDeveloper 4.0
Stage 1: HAVE YOUR DATABASE Prepared
1. Make your database in Microsoft SQL Server, Prophet, or DB2. You can structure and make your very own database. Or then again, you can utilize the example database furnished with TierDeveloper. Or on the other hand, you can utilize one of the databases/constructions previously furnished with your database. They are:
a.Microsoft SQL Server: Northwind database. Simply make another TierDeveloper venture against this database.
b.Oracle: DEMO construction with EMP, DEPT, Reward, SALGRADE, and different tables. Simply make another TierDeveloper venture against this pattern.
c.DB2: Test mapping gave DB2. Simply make another TierDeveloper venture against this diagram.
2. Populate database with information. This would guarantee that you have a completely working database prepared to be utilized by a web application.
Stage 2: KNOW YOUR APPLICATION'S DATABASE Connection
1. Identify table-sections your application will access: Before you do anything, you should realize which tables and which segments in these tables is your application going to get to.
2. Identify value-based activities: Distinguish where in your application you have to do embed, update, erase, or single-push select tasks.
3. Identify questions: Most applications need to recover accumulation of columns from at least one tables in the database. Distinguish all spots where you have to issue inquiries. These could be single-table inquiries or could include complex joins or settled questions.
4. Identify put away techniques to call: If there are any put away methods that as of now exist in the database which you have to call, recognize them here. These put away methodology ought to be those that contains complex business rules or other information control rationale. Don't physically make put away techniques in the database for value-based tasks or for questions that are generally taken care of by TierDeveloper. TierDeveloper can create put away technique DDL for you in that circumstance.
5. Identify mass updates or erases: Most applications don't require mass updates or erases however some do. In the event that you have any, recognize them.
The most ideal approach to comprehend your applications database communication needs is to comprehend its conduct from the client's point of view and spotlight on every one of the information that should be shown to the client or changed by the client.
Stage 3: Make TIERDEVELOPER Undertaking
1. Connect TierDeveloper to your database: TierDeveloper utilizes OLEDB to interface with your database and peruses its pattern so it can give you a chance to characterize the mappings of center level items with tables in the database (in view of what you have decided about your application's collaboration with your database). It would be ideal if you note that regardless of whether you will create Java/J2EE application that will utilize JDBC to associate with the database, TierDeveloper (the item) will utilize OLEDB to interface with your database.
2. Define information object mappings to your tables: Wherever you had distinguished table-segments that your application needs, characterize information objects mapped to these tables with the proper segments chose as information object properties. You can delineate information article to single table or various tables. You'll require multi-table information objects for circumstances where you're attempting to issue a multi-table join question that profits information from numerous tables.
3. Specify value-based strategies in information objects: In view of what you distinguished as your application's value-based needs prior, you should now characterize those addition, update, erase, and single-push select as techniques for your information objects. TierDeveloper gives you a chance to do that with point-and-snap.
4. Define inquiries as information object techniques: For each question that you recognized before, characterize an inquiry strategy in the proper information objects. Keep in mind, an inquiry restores a resultset which get converted into a gathering of information questions by TierDeveloper created code.
5. Define put away technique calls as information object strategies: Wherever you expected to call put away systems, you have to characterize information object techniques for them. Keep in mind, these put away systems contain refined business rules. Any put away methods for value-based activities or inquiries can be produced by TierDeveloper so you don't need to physically think of them in the database.
6. Define mass update/erase activities as information object techniques: Wherever you have to complete a mass update or mass erase, you'll have to characterize information object strategies for them.
Stage 4: Create AND RUN half OF YOUR APPLICATION In a flash
1. Generate information objects: After you have characterized every one of your information objects, you are prepared to create code for them. You can create information object code in the accompanying configuration:
a. .NET parts
2. Build and send information objects created code: In the event that you machine has the fitting form condition for your stage, TierDeveloper asks you whether you need to manufacture the produced information objects code. In the event that you state "yes", it makes the accompanying. It likewise then sends them to your proper condition.
a. .NET congregations for .NET segments. They are conveyed through segment administrations.
3. Generate web application: After you have produced and fabricate the information objects, you can create a completely working web application. The reason for this web application is to give you a chance to test every one of the elements of information objects. This additionally fills in as a decent example/precedent code for you to duplicate into your very own web application advancement. TierDeveloper creates the accompanying kinds of web applications:
a. ASP.NET pages in C# or VB.NET and with or without XML/XSLT.
4. Build and send web application: TierDeveloper can likewise assemble the website pages for you. It does the accompanying for every stage:
a. Build a .NET gathering for ASP.NET pages. They are sent to IIS
5. Run sent web application with information objects: Since you have effectively conveyed the information objects and the web application, you can run the web application. The extremely decent thing is that this produced code is currently neutralizing your very own database and in your own condition. You can see all the conduct of the information protests through this web application and furthermore use it as a guide in your very own web improvement. Attempt this and you'll be persuaded about TierDeveloper being a genuine Fast Improvement apparatus.
Stage 5: Create Staying half OF YOUR APPLICATION
In the wake of running and confirming that all the created code contains your ideal usefulness and runs effectively against your database, you are presently prepared to build up the remainder of the application. The zones you are probably going to need to create in your application are:
1. Presentation Layer (Site pages): Use TierDeveloper produced web application as an example/case for rapidly building up your own. You can even duplicate/glue a great deal of the code from the created web application into yours, accordingly accelerating your advancement work much further.
2. Business Items: In spite of the fact that TierDeveloper produced code contains every one of your information control rationale and a portion of your business runs too (as information approval or put away methodology calls), you will in all probability need to build up extra business objects. In case you're not a specialist in your objective stage (.NET, J2EE, or J2SE), you can gain from the produced information protests as your business objects are likely going to be in a similar situation and would pursue comparable structure approach.