Check out ImageMagick to programmatically or from the command prompt manipulate images. It supports a ton of formats. It has support from .NET and Java, etc.
A very good tool to have in your toolbox.
Showing posts with label Tools. Show all posts
Showing posts with label Tools. Show all posts
Friday, February 23, 2018
Wednesday, August 30, 2017
Data Generation of test data
Writing your own test data generator
There are cases where it makes sense to generate data in your SQL Server database. If you are dealing with one table this can be a pretty straight forward task and you may consider writing it yourself as a simple app or code that runs before your tests run.The hard part to rolling your own generator for a single table is the generation of data. There are some nuget packages that will help with this.
NBuilder - this is great for creating object graphs. It should be able to play with Entity Framework and be saved to database. In theory in situ updates could be done.
Bogus - you can save changes using Entity Framework to the database. The relationships would be handled by entity framework automatically. If the data is loaded from the data and then updated using Bogus generated data the data could be anonymized in situ. It does have really nice options for rules the data must follow.
REX - a command line tool to generate data that follows a regular expression. Very cool.
Free-ish products for generating data for single table
If you don't want to roll your own there are other options as well for simple one table type options. Below are some you may want to check out:
Yan DATA - It is a web based tool that requires you to enter your table definition into a web form and then generate the data from there. This one is nice in that it support many formats as output like SQL, JSON, Excel, XML, CSV, and HTML. It does up to 10,000 rows and is free / donation.
Mockaroo - It is similar to Yan DATA, but is limited to 1000 rows or $50 or $500 / year and its focus is on realistic data types. It even has datatypes for specific industries. It has some additional options for outputting the data including some that are database specific, etc. Interestingly they do have a REST url you can use to get data and use in your automation. It does also allow you to define your tables based on table create SQL statements or Excel column headers. It also lets you specify a formula for a column and specify how many empty values should be used.
Products for generating data for multiple related tables (they have a price)
DevArt dbForge Data Generator - appears to be a very similar tool.
Friday, September 23, 2016
Take aways from Agile on the Beach 2016
I attended Agile on the Beach in Falmouth (England). It was really great to hear so many people with different experiences. The videos and slides can be found here. Below are some of the highlights of what I found particularly interesting.
Keynote by Dr. Linda Rising
Continuous Delivery
Keynote by Dr. Linda Rising
- Surprisingly, people are moved to action by stories NOT facts (or evidence). In fact when someone is shown evidence as to why they are wrong they only stand firmer in their belief (as a defense mechanism).
- A placebo can be just as useful as the "real thing" because what we BELIEVE can make us fail or succeed. The placebo allows us to believe in something.
Continuous Delivery
- Tools: NCrunch, CruiseControl.Net, R#, NANT
- Policy: Develop to one trunk (no long standing branches). Because of this, GIT may not be the best choice.
- Goal: Want SMALL commits frequently. For example, about once an hour and ideally 2 files.
- Break refactoring out in a separate commit.
- Policy: Can't commit when build is broken
- Policy: Run all tests before commit (on local machine)
- Policy: Don't go home until a broken build is fixed. This doesn't mean late hours necessarily. It could just mean backing out the offending commit, and addressing it the next day, then recommit.
- Goal: a pipeline should be about 4 minutes for quick feedback.
- Goal: it is ideal for it to be faster to redeploy a change using the pipeline than manually backing out a release.
- Goal: 75% code coverage. Most will be between 50% and 80%
- Use Feature Toggles when required, but avoid if can.
- Warm up an app after deploy
- Measure commit to live time.
- Broken Windows Effect - one broken window (bug, issue, technical debt, not tested unit, etc) begets more broken windows.
- As developers we spend 70% of our time reading code (ours or someone else's) and the rest of the time copy and pasting. Consider poorly written code to be a broken window and copy and pasting that implementation pattern the creation of more broken windows.
- Anti-patterns: Fat controllers, large models, functionality grouped into services or managers (not sure I understand the last one...).
- Enforce standards on each commit and fail the build. Could be formatting rules, naming conventions, etc. This will make code diffs be much easier because we only have to read meaningful changes, not changes to code formats.
- Code that is easy to change (opposite of code smell) has: High Cohesion, Loosely coupled, little duplication, low cyclomatic complexity.
- Tools: ESLint (for JavaScript checking), Resharper, Visual Studio, NDepend, NCover
- Shorten Feedback loop: Idea -> Test -> Measure -> Learn -> (loop back)
- Gall's Law: Solving complex problems (or systems) from scratch in one go does NOT work, but starting with simple case that works and iterating works (summarized from quote from John Gall).
- Testing Pyramid (GUI testing, Acceptance testing, unit testing)
- Interestingly, only 20%-25% of the audience in the Testing in CD talk at AOTB used TDD. Maybe it isn't so surprising because people that already know it and use it may not attend a talk on it when there are new topics to be heard.
- Interestingly, only 10%-15% of same group used BDD.
- Hypothesis Driven Development - Can be written as statements in the following format: We believe <this capability>, Will result in <this outcome>, We will have confidence to proceed when <we see measurable signal>.
Pen Testing (Penetration Testing)
- Expect 20-30 minutes scan time depending on application size
- Run on UI and API.
- Use BDD to describe security tests (see BDD Security) to have human readable tests for security.
- Tools can find 70-80% of vulnerabilities, but the rest needs to be manually done.
Pen Testing Tools
- Static code review using tools like Veracode.
- BDD_Security - Define security tests using BDD style scenarios.
- Mittn - define a hardening target using human-readable language
- Arachni-Scanner - free with source and runs on Windows, Mac, and Linux
- Gauntlt - may be useful as well to coordinate security tools.
- ZAP - free security tools / scanner.
- SSLyze - checks for mis-configurations affecting SSL Servers.
- Nessus - a paid PCI vulnerability scanner.
Business Agility
- Process: Test Hypothesis -> Quick delivery and release -> measurement -> repeat
- Big Bang never works or at least very scary.
- Use The Strangler Pattern to avoid big bang.
- Postel's Law - Architect for testability, develop for evolve-ability.
- Last Response Moment - wait as long as you can (so you have more information), but no longer.
- Beware of the silver bullet
- Continuous Delivery - automate as much as you can. Note, you can still have approvals in your process, but the action once approved is still automatic.
- Conway's Law - organizations which design systems ... are constrained to produce designs which are copies of the communication structures of these organizations
- Keep systems poised for change.
- Don't think yes, no to ideas, but instead think what are the risks and benefits. Then the other person get's to decide if it is worth it.
- Do the simplest possible thing that might work because the complexity may never be needed.
Understanding the problem
- Empathy Maps
- A3 - Root cause analysis
- PDSA
Keeping up
Thursday, December 24, 2015
Must have Graphics Tools
Below is a short list of some really great tools for editing or creating graphics, editing photos, etc.
The Gimp - It is the cross platform FREE and Open Source alternative to Photoshop.
Paint.NET - This is my long time favorite because it is easier to install and use than Gimp, opens faster, and has most the features I need.
Pixlr - Has most of the important functionality of The Gimp, but runs in any browser that supports flash.
Please suggest any other graphics apps that should be included here.
The Gimp - It is the cross platform FREE and Open Source alternative to Photoshop.
Paint.NET - This is my long time favorite because it is easier to install and use than Gimp, opens faster, and has most the features I need.
Pixlr - Has most of the important functionality of The Gimp, but runs in any browser that supports flash.
Please suggest any other graphics apps that should be included here.
Tuesday, December 1, 2015
Review of some products for working with MS Word documents using .NET / C#
I didn't want to use MS Automation because it is slow and not server friendly, so I am not covering that here. The solutions below do NOT require MS Word to be installed and they are server friendly.
Open XML Word Processing SDK
This is my first choice for completely free solutions because is relatively easy for basic things and it will likely always be supported by Microsoft. This is the Microsoft SDK (released as Open Source as of version 2.5) for creating and editing MS Word documents in DOCX format. It takes a bit to get used since it mirrors the internal DOCX format. The advantage is that pretty much everything you need to be done here. The disadvantage is that it may take more code than using other packages. The link above has sample code on how to do many common tasks. Here is a good place to start to familiarize yourself with the file formats, what resources are available, etc. To understand the DOCX file format, check this out. The DOCX format is much simpler than the XLSX format. I recommend giving it a try. The learning curve is pretty small for the DOCX file format and there is a lot of examples available. In the end it isn't so different than NPOI (see section below) for DOCX. Here is a list of how to do's.
It is unofficially distributed on NuGet as DocumentFormat.OpenXml, but it is unofficially distributed by someone other than Microsoft (even though it shows the author as Microsoft). If you want the official binaries they can be downloaded here. If you want the source code you can get it on GitHub. This video shows how to build the source code if you want to go that route. If you want to use 2.6 it has been released on NuGet as OpenXMLSDK-MOT. This is the same as official binaries and source code in GitHub (from what I can tell). All options install an assembly called DocumentFormat.OpenXml and if done through NuGet it is added a reference to your project.
If you want to validate that the document you create is valid, check out this code example.
Here is an example of how to do a search and replace in a DOCX file.
Here is the link to the Open Xml Developer website.
There are also tons of example on the Open Xml Power Tools project on GitHub and from NuGet.
Open-Xml-Power-Tools - DocumentAssembler
This is an Open Source module in Open Xml Power Tools that allows you to create templates using .DOCX files as templates, a xml data source, and generating a well formatted DOCX file with the data merged in to the template. The template allows such things as tables, conditions, etc using XPATH-like syntax. Here is a video on how it works, but not a step by step tutorial. Here is a getting started video / tutorial that walks you through using the product. It is important to watch the ending where he talks using <# #> instead of Content Controls in Word as the placeholders. It works similar to most reporting tools, but using MS Word as report definition (template) file and the output being a MS Word document as well. You can download the entire Open-Xml-Power-Tools suite that includes DocumentAssembler from here. It is not meant to be used to create DOCX documents from scratch. It always uses a template file to generate new DOCX files. However, Open-Xml-Power-Tools suite does have the ability to help work with DOCX files. NOTE: It is built on top of (requires it) the Open XML Word Processing SDK (above).
DOCX
If you really don't want to learn anything about the DOCX format and want a more inuitive way to interact with the DOCX files then this may be a good option if you are okay with alpha software. A simple Open Source project available from codeplex.com or NuGet. It let's you interact with the Word document in an intuitive manor without understanding how Word documents internally work. The examples on his blog are good and good examples in source code. It is easy to use. It is still alpha, but has been around since 2009. It has growing popularity.
Free Spire.Doc
This is a free version with limitations for a professional package called Spire.Doc. It is quite powerful and also does conversions to PDF and many other formats. It does mail merges, etc. Is is nice for small projects that are below the limitations. The API is well thought out and works nicely.
NPOI
This is the .NET implementation of the popular POI Java Project. It is Open Source and totally free and also does MS Excel. The API is a bit low level at time, but works well. I recommend downloaded from github to work with examples. Also, you can install binaries via NuGet. The documentation and examples for XDOC are not really there yet though. Look for XWPF if you want to use DOCX file format. The problem is that it is not the exact same API as the POI Java Project, but it is similar. It is also not as mature and is thus missing some features. It is a bit more abstract that just using the Microsoft packages, but still quite a bit of DOCX format knowledge is needed. In general I found the experience a bit frustrating because of how the project is organized and the poor documentation and very few DOCX examples.
Open XML Word Processing SDK
This is my first choice for completely free solutions because is relatively easy for basic things and it will likely always be supported by Microsoft. This is the Microsoft SDK (released as Open Source as of version 2.5) for creating and editing MS Word documents in DOCX format. It takes a bit to get used since it mirrors the internal DOCX format. The advantage is that pretty much everything you need to be done here. The disadvantage is that it may take more code than using other packages. The link above has sample code on how to do many common tasks. Here is a good place to start to familiarize yourself with the file formats, what resources are available, etc. To understand the DOCX file format, check this out. The DOCX format is much simpler than the XLSX format. I recommend giving it a try. The learning curve is pretty small for the DOCX file format and there is a lot of examples available. In the end it isn't so different than NPOI (see section below) for DOCX. Here is a list of how to do's.
It is unofficially distributed on NuGet as DocumentFormat.OpenXml, but it is unofficially distributed by someone other than Microsoft (even though it shows the author as Microsoft). If you want the official binaries they can be downloaded here. If you want the source code you can get it on GitHub. This video shows how to build the source code if you want to go that route. If you want to use 2.6 it has been released on NuGet as OpenXMLSDK-MOT. This is the same as official binaries and source code in GitHub (from what I can tell). All options install an assembly called DocumentFormat.OpenXml and if done through NuGet it is added a reference to your project.
If you want to validate that the document you create is valid, check out this code example.
Here is an example of how to do a search and replace in a DOCX file.
Here is the link to the Open Xml Developer website.
There are also tons of example on the Open Xml Power Tools project on GitHub and from NuGet.
Open-Xml-Power-Tools - DocumentAssembler
This is an Open Source module in Open Xml Power Tools that allows you to create templates using .DOCX files as templates, a xml data source, and generating a well formatted DOCX file with the data merged in to the template. The template allows such things as tables, conditions, etc using XPATH-like syntax. Here is a video on how it works, but not a step by step tutorial. Here is a getting started video / tutorial that walks you through using the product. It is important to watch the ending where he talks using <# #> instead of Content Controls in Word as the placeholders. It works similar to most reporting tools, but using MS Word as report definition (template) file and the output being a MS Word document as well. You can download the entire Open-Xml-Power-Tools suite that includes DocumentAssembler from here. It is not meant to be used to create DOCX documents from scratch. It always uses a template file to generate new DOCX files. However, Open-Xml-Power-Tools suite does have the ability to help work with DOCX files. NOTE: It is built on top of (requires it) the Open XML Word Processing SDK (above).
DOCX
If you really don't want to learn anything about the DOCX format and want a more inuitive way to interact with the DOCX files then this may be a good option if you are okay with alpha software. A simple Open Source project available from codeplex.com or NuGet. It let's you interact with the Word document in an intuitive manor without understanding how Word documents internally work. The examples on his blog are good and good examples in source code. It is easy to use. It is still alpha, but has been around since 2009. It has growing popularity.
Free Spire.Doc
This is a free version with limitations for a professional package called Spire.Doc. It is quite powerful and also does conversions to PDF and many other formats. It does mail merges, etc. Is is nice for small projects that are below the limitations. The API is well thought out and works nicely.
NPOI
This is the .NET implementation of the popular POI Java Project. It is Open Source and totally free and also does MS Excel. The API is a bit low level at time, but works well. I recommend downloaded from github to work with examples. Also, you can install binaries via NuGet. The documentation and examples for XDOC are not really there yet though. Look for XWPF if you want to use DOCX file format. The problem is that it is not the exact same API as the POI Java Project, but it is similar. It is also not as mature and is thus missing some features. It is a bit more abstract that just using the Microsoft packages, but still quite a bit of DOCX format knowledge is needed. In general I found the experience a bit frustrating because of how the project is organized and the poor documentation and very few DOCX examples.
Thursday, November 26, 2015
Essential MVC Tools
Below is a list of tools, plug-ins, packages, etc that you should really consider using if you are doing development for ASP.NET MVC.
Sidewaffle - custom templates. Can consume them from library or create own
Glimpse - amazing view into all things. particularly performance. Scott Hanselman has a good review of it.
ZenCoding - very cool html coding that greatly reduces typing of html tags
Web Essentials - extends Visual Studio, including design time edit from browser
Less - gives variables, etc to CSS like files that we can generate css files from automatically
WURFL - on nuget for reliable device detection (mobile, table, google glasses, etc)
Automapper - Copying data automatically from object to another similar object
d
dd
Sidewaffle - custom templates. Can consume them from library or create own
Glimpse - amazing view into all things. particularly performance. Scott Hanselman has a good review of it.
ZenCoding - very cool html coding that greatly reduces typing of html tags
Web Essentials - extends Visual Studio, including design time edit from browser
Less - gives variables, etc to CSS like files that we can generate css files from automatically
WURFL - on nuget for reliable device detection (mobile, table, google glasses, etc)
Automapper - Copying data automatically from object to another similar object
d
dd
Friday, April 10, 2015
Sysinternals is back!
If you were a fan of the Sysinternals tools by Mark Russinovich, then you will be happy to know that they are back. Thankfully they moved to Microsoft (a bit later) with Mark.
Here is the link to the new Sysinternals Suite.
Here are links to the individual utilities:
Thank you Mark!
Here is the link to the new Sysinternals Suite.
Here are links to the individual utilities:
Thank you Mark!
Wednesday, April 16, 2014
FREE or Open Source or Inexpensive options to compare data (in tables) in SQL Server
Intro
Visual Studio 2012 (an some earlier editions) include Schema comparison for SQL Server. This is NOT what I am writing about here today. Assuming you have used this tool to make tables, etc the same you may have a need like I do when moving data from dev to production databases or the reverse. There are several ways to go about this.FREE - SQL Server Data Tools
Probably the best place to start is SQL Server Data Tools which is available from Microsoft. It includes among other things the ability to compare data in SQL Server tables.It is available for Visual Studio 2010 and newer. There was an option in some editions of Visual Studio 2010, but not in Visual Studio 2012. To get the functionality in Visual Studio 2012 you need the SQL Server Data Tools to be installed. Once you have it installed you will have functionality very similar to what was available in VS 2010 or the RedGate product. Here is a direct link for the download of the English ISO. One of the nice things about this option is that it is well integrated into Visual Studio 2012 and uses the same source and destination configurations as the SQL Schema Comparison that is built into VS 2012.You can also select what tables you want to compare, what columns in the tables, if you want source or destination records, etc. It will just to the update for you or you can have it generate the SQL Script that you can manually. It gives you a nice visual representation of the differences and let's you select the rows you want to change. It seems to be pretty fast. The generated SQL script even disables constraints as needed. It also seems to handle nulls properly. This is a very nice option for free!
It appears it can be called from the command line as well, but I have not tried it.
Here is the blog for the SSDT team.
FREE - tablediff.exe
IMHO, this may be the best choice for scripted options. Believe it or not tablediff.exe is a utility that comes with SQL Sever 2005 or greater. I believe this is the tool that SQL Server uses when replicating tables, though that is just what I read from someone else. It will tell you on a row by row and column by column basis what is different. It will even generate the SQL scripts needed to make the destination table look like the source table. As far as I know you cannot download it separately. However, it is installed when you install SQL Sever 2005 or newer and you choose SQL Server Replication feature. In SQL Server 2008 R2 it is included by default, but I'm not sure about the other versions. On my machine it was located at C:\Program Files\Microsoft SQL Server\100\COM\tablediff.exe. Once you find it you can type tablediff.exe -? for the options or refer here to the documentation. The parameters are pretty well documented and easy to follow to I won't go into all the options, but here is an example of how you would generate a change script (SQL) and see what the differences are.
C:\Program Files\Microsoft SQL Server\100\COM>tablediff.exe -sourceserver MySrcServer-sourcedatabase MyDevDB -sourceschema dbo -sourcetable Person -sourceuser User1 -sourcepassword User1Pwd -destinationserver MyDestServer -destinationdatabase MyProdDB -destinat
ionschema dbo -destinationtable Person -destinationuser User1 -destinationpassword User1Pwd -c -o c:\temp\diff.txt -f c:\temp\diffgen.sql
This will generate two files. diff.txt which will have the differences, and diffgen.sql which will be the SQL script you can execute to make the destination table the same as the source table.
WARNING:
Be careful, the SQL will also generate delete statements for your destination table. This may or may not be what you want so just be aware. I recommend backing up your destination table before doing this operation.
Also, it doesn't appear to generate correct scripts for null. It put null in single-quotes. This can be changed easily with a search and replace though.
Keep in mind this is per table. If you have lots of tables and you want them all to be updated it could be a done also, but it a bit tedious. However, the nice thing about this tool is since it is command line once you have it setup you can run it again and again with little to no effort.
If you want you can even download a GUI for the command line tool. NOTE: You still need the command line tool. I was not able to get it to work with SQL Server 2008 R2, but you can decompile it and fix it I'm sure. Does it work for anyone else? All it does is exactly what you do on the command line so I'm not sure I really see the benefit if you are going to want to run it more than once.
Inexpensive - SQLDBTools
If I have a little money to spend on the solution. SQLDBTools costs $60 at seems to do pretty much what the RedGate products do, but for a fraction of the cost. It does do schema and data comparisons which is nice to have it all in one tool. I does visually let you see the differences and it also generates the change script. I have not tried this product, but it looks like the best product for the money (if you are going to pay for a solution). Given that SQL Server Data Tools now exists I don't really see the advantage or reason to pay for this tool.
FREE - Linked Server
This is a less desirable option because it doesn't do anything automatically for you. After you have a linked server you can do queries to see the differences between tables. This does nothing for automatically generating the update scripts. This solution is good for analysis only.
Inexpensive - Beyond Compare
Beyond Compare does a nice job of visually showing the differences in two files. It doesn't know anything about SQL or databases, but as long as you use SSMS to export the data to CSV, Excel, or tabular data Beyond Compare will show you the differences in an Excel like manner. Again, this does nothing for generating the change script and could be slow for very large tables.This is best for comparing two adhoc queries in my opinion.
Additional Info
I found this site that has a pretty exhaustive list of tools for SQL Server that may be useful.
Wednesday, March 5, 2014
Oracle APEX Review
Overview
Oracle APEX = Oracle Application Express
Been around since 2004 under various names
Browser Based development and deployment
Think of it as a replacement for MS Access, but on the web and multi-user with an Oracle backend.
RAD tool for the Oracle Database; think Forms over data
Declaratively build web 2.0 applications
Leverage SQL and PL/SQL skills.
Multi-tenant Hosting
Departmental Solutions is focus
The Oracle store is built with APEX
Lots of options for Authentication or even custom
Built-in support to prevent URL tampering
20 canned themes or can create your own, including one for starting mobile.
Wizards to create forms including master detail, etc, but has basic layout, functionality, etc.
Create web services with wizard. A web service can be created from a region also.
Can add regions to a page and add most anything to the region including forms, etc.
Cost
Fully supported by Oracle
Free with Oracle Database (include Oracle XE)
Skill Set Required
PL/SQL
SQL
Skill Set Required for Customization
HTML
JavaScript
CSS
Advantages
Robust migration path for Oracle Forms application to APEX.
Very easy to generate data-driven CRUD data entry style applications that include simple reporting.
Migrating MS Access, or Excel files to a multi-user web environment
Similar to SharePoint lists such that you can create tables, and UI based on an Excel spreadsheet.
Free with Oracle database license
RAD or demo or POC
Built-in themes
Customization done using standards such as JavaScript, HTML, and CSS.
Disadvantages
Debugging can be painful. No breakpoints,
Business Logic written in PL/SQL. No layers such as a business layer and data access layer. SQL or stored procedures are referenced directly.
Web based development environment feels a bit clumsy and slow.
Tightly bound to PL/SQL and Oracle.
You must work within the paradigm that is defined by APEX. If the application doesn't fit the paradigm the effort drastically increases. For instance javascript and html/css become the way of working. This is a much different skillset. Alternatively, plug-ins can be created to extend APEX.
Migration path from MS Access to APEX is limited and works on with simple
The time you save in development time can be quickly lost in debugging, support, and customization.
No version control
Architecture
- Web Browser
- Apache with mod_plsql/EPG web listener
- Application Express
- Meta Data
KEY FEATURES according to a Oracle APEX Specialist
FRAMEWORK
The APEX framework uses SQL and PL/SQL on the back-end, and HTML, CSS, and JavaScript for the user interface. SQL and PL/SQL are solid and proven languages and they allow APEX developers to leverage the features of the Oracle database. HTML, CSS, and JavaScript are industry standard components for building web applications.
SUPPORT FOR MULTIPLE AUTHENTICATION SCHEMES
APEX supports various authentication schemes such as LDAP, database, Single Sign on, Oracle Access Manager, custom, etc. This makes it convenient to integrate with any existing applications and authentication systems.
DECLARATIVE MOBILE APPLICATION DEVELOPMENT
APEX is bundled with the popular jQuery mobile libraries and provides declarative support for building mobile applications. A special mobile theme provides APEX mobile applications with typical mobile features such as page transitions and gestures including swipe, pinch, and tap. Custom mobile themes can easily be created with the jQuery mobile theme roller.
RESPONSIVE DESIGN FOR OPTIMAL VIEWING ON DESKTOP, TABLET AND SMARTPHONES
APEX applications can be rendered on desktops, tablets, and smartphones by choosing a theme based on a responsive design. APEX includes a set of modern themes that are based on CSS3 and HTML5, and supports HTML5 charts, and HTML5 item types such as sliders and toggles.
PACKAGED APPLICATIONS – A FULL DEVELOPMENT SUITE
APEX is bundled with a suite of business productivity applications that can be freely used to assist with the management and control of projects. The suite contains applications for bug tracking, issue logs, checklist management, meeting minutes, group calendar, decision management, document management, and project management.
RESTFUL WEB SERVICES
APEX has built-in support for RESTful web services and allows applications to access data and services over the internet or intranet using standard web APIs. Database web services that implement SQL or PL/SQL can also be created. RESTful web services in APEX requires the APEX Listener, a J2EE based alternative for the Oracle HTTP server and mod_plsql.
DATABASE INTEGRATION
APEX is a component of the Oracle database and applications build with APEX can utilize or benefit from any feature of the database such as advanced security, RAC, Spatial, Analytics, Multimedia, XML DB, Job Scheduler, utility packages, etc. APEX uses SQL and PLSQL to interact with the Oracle host database.
GLOBALIZATION SUPPORT
Applications build in APEX can run concurrently in different languages. Applications are developed in a primary language and can be mapped to a supported target language. Strings in the primary application are exported to a XML Localization Interchange File (XLIFF) where they are translated and imported and automatically used by the translated application.
TEAM DEVELOPMENT
Team development is a built-in feature that allows a group of developers, working on a single application, manage new features, to dos, bugs, and milestones. Users of an application can provide instant feedback which can then be classified as feature, to do, or bug.
EXTENSIBLE
The APEX development framework supports plugins that allow developers to extend the functionality of their applications with reusable custom or third-party extensions. APEX applications can also be extended with custom HTML, CSS, or JavaScript.
OTHER FEATURES
APEX is also stacked with other utilities and features that greatly improve developer productivity throughout the life of a project.
Version Control Support – Applications can be automatically exported into SQL script files where they can be included in a version control system. APEX provides an application exporter utility as well as an application splitter utility for splitting application into individual page scripts.
Error Handling – Developers can create a single error handling function that handles exception consistently across all pages in an application.
Oracle Forms Migration Tool – If Java/ADF is not for you, APEX is a viable option for converting Oracle Forms applications. APEX includes a forms migration tool to assist with the migration of Oracle Forms applications.
Accessibility – APEX applications have automatic built-in accessibility support. Applications can be rendered in high contrast mode or screen reader mode in order to meet accessibility requirements.
Utility Reports – APEX has a comprehensive list of reports that provide real-time information on applications. Some of the more useful reports are:
- Change History – List of changes made by developers
- Advisor – Quality control review of an application
- Database Object Dependencies – List of database objects used by an application
- Debug Messages – List of debug messages generated by an application
- Recently Updated Pages – List of pages that were recently updated
Features
Reports
Forms
Charts
Calendar
Templates
Navigation
Validations
Processes
Computations
Branches
Web Services
Email Services
Translation Services
Conditional Processing
Authentication
Authorization
Session State Management
Logging & Monitoring
Interactive Reports
Integrating with Other Tools / Services
SQL
PL/SQL
RAC
Spatial
OLAP
Flashback
Web Services
Text
Multimedia
Analytic Functions
Globalization
XML DB
eBusiness Suite
Migration to APEX
Direct Excel Conversion
MS Access Conversion Support
Oracle Forms Conversion Support
Security
Popular authentication supported as well as custom
Can hide columns based on user access level
Screenshots of the development environment
Built-in User Management
List of applications in the workspace
List of all pages in an application
Design a page
Options for creating a new application
Add a page
Create a Form
Sample User Interface
of the application created from a Spreadsheet
This is an interactive report. We can add charts, group by, add aggregate columns, filter, highlight, export to CSV, re-order columns, hide columns, save report, etc.
Conclusion
Oracle APEX may be a good choice depending on your needs. Here are some key criteria for this to be a good choice:
- Oracle database is your database of choice
- You know SQL and even better you know PL/SQL
- Your application is essentially a CRUD or forms over data applications or data-centric application
- You want to do RAD
- You don't want to write lots of code
- For customization you will need JavaScript and HTML/CSS knowledge
- For writing Business logic and customizing the application you will need PL/SQL knowledge
- To get the largest savings in time you will want to use the predefined forms and wizards, but this is not required.
It also means you are willing to give up some of the more common development practices
- Having separate tiers for business logic and data access. Instead you must want your business logic to be in the database in packages.
- IDE that runs on your pc
- Robust debugger
- Unit tests
- Version control (Yes you can export files and them to version control, but it isn't quite the same thing in my opinion)
- If you want to do OOP or MVC this is
- Drag n drop files from your desktop into the IDE
- Less control over files in your project
If the above criteria is okay with you then Oracle APEX is worth looking at. You get a lot of functionality. Similar to what you would get with SharePoint, MS Access, or meta-data tools, but with different strengths and weaknesses as noted above.
References:
Subscribe to:
Posts (Atom)












