Tuesday, September 13, 2011

Apex 4.1




After several months, new Apex release is here. In this release there are several new features (and fixes) and here they are in comprehensive list:
  • Error Handling
    Release 4.1 includes improved error handling and user-defined exception processing. You can now easily capture error messages generated by the Oracle database and replace the message text with user friendly text. For example, instead of an error message such as "ORA-00001 unique constraint (EMP_UK) violated" the developer can define a message such as "Employee Name must be unique".
    This means that beautiful Patric Wolf solution is somehow directly supported.
  • Use of ROWID
    Application Express now supports the use of ROWID for updates, inserts and deletes as an alternative to specifying primary keys. Previously you could only specific two primary key columns. Therefore, if your table had more than two key columns then you could not use the default DML processes and had to manually write your own processes. Use of ROWID is now the default method for any new DML processes generated.
    Finally for those who had "older" non surogate PK database designs!
  • Data Upload
    Developers can now easily add the capability for end-users to load spreadsheet data into existing tables within an application. The developer can utilize a wizard to create a collection of pages that allow the end user to upload a file or cut and paste data into a table. Additionally the developer can define lookup columns and data transformations. End users are then led through a runtime wizard which allows them to load the data, map the columns, see whether the data will be inserted or updated, and review the results.
    Very handy new feature which really lead to WEB 5.0
  • Calendar
    The calendar wizards have been enhanced to include the ability to create an Edit page as part of creating the calendar. Further calendars can now include drag and drop functionality which allows the end user to change the date and or time of a record by simply dragging it on the calendar itself.
    Another WEB 5.0 like feature
  • Websheets
    Building on their initial introduction in Release 4.0, the look and feel of Websheets in Release 4.1 has been substantially improved and the controls redesigned to make it more intuitive for users. There are also new page section types, and enhanced data grid integration
  • Tabular Forms
    Tabular Forms now support all validation types. Depending on the validation type you can use bind variable syntax, substitution syntax, or just specify the tabular form column name. These enhancements allow developers to declaratively define complex validations instead of having to perform extensive manual PL/SQL coding.
  • Plug-Ins
    Plug-ins enable developers to enhance the existing built-in functionality by writing PL/SQL components for various components. This release expands the plug-in functionality and introduces the ability to create plug-ins for authentication and authorization schemes.
  • Dynamic Actions
    Dynamic Actions allow developers to declaritively define client-side functionality, without needing to master JavaScript and AJAX. With this release, a number of enhancements were added including the ability to define dynamic actions for buttons and also use dynamic actions to set multiple item values.
  • Accessibility
    Release 4.1 includes dramatic improvement in the HTML generated by the Application Express engine, together with accessibility improvements in existing themes and HTML templates.
  • Mobile Applications
    Release 4.1 includes a number of key improvements to improve support for mobile frameworks, including form rendering without HTML tables.

ORA-24344 when upgrade from Release: 4 and later

When upgrading Apex from 4.0.2 to 4.1 results in the following errors /warnings in the log file
Warning: Websheet schema EBUS upgrade_ws_to_040100 
ORA-24344: success with compilation error

Solution

Customers do not use Websheets in 4.0.2 but would like to use it in 4.1. If a customer is not using Websheet, the error with trigger will NOT be an issue. This will be an issue only if customer starts to use Websheets. In the future if customer decides to use Websheets, they can use workspace administration interface to validate Websheet objects to correct invalid or missing Websheet objects.
  1. Log into APEX
  2. Administration -> Tasks->WebSheet Database Objects -> Validate Websheet Objects

The End

For all of you who want to see Apex in "live", here is link where you can find that.

Until next Apex version, which would be, IMHO, more oriented in mobile apps ... Cheers!

Sunday, September 11, 2011

Application Express Preferences for an APEX Instance

Application Express Preferences is set of vital parameters that describe how Apex Instance beehive. Usually they are set through Apex Administrator GUI interface, but it also may be handy to set them from SQLPlus as well.

How can you determine the APEX preference settings for an APEX instance?

SYS@egis>select name||'=<'||value||'>' from APEX_040000.wwv_flow_platform_prefs order by name;

NAME||'=<'||VALUE||'>'
----------------------------------------------------------------------------------------------------
ACCOUNT_LIFETIME_DAYS=<9999>
ALLOW_DB_MONITOR=<N>
ALLOW_PUBLIC_FILE_UPLOAD=<N>
ALLOW_REST=<N>
AUTOEXTEND_TABLESPACES=<Y>
DISABLE_ADMIN_LOGIN=<N>
DISABLE_WORKSPACE_LOGIN=<N>
DISABLE_WS_PROV=<N>
ENABLE_TRANSACTIONAL_SQL=<Y>
EXPIRE_FND_USER_ACCOUNTS=<N>
MAX_LOGIN_FAILURES=<9999>
MAX_SCRIPT_SIZE=<500000>
MAX_SESSION_IDLE_SEC=<360000>
MAX_SESSION_LENGTH_SEC=<288000>
NOTIFICATION_EMAIL=<damir.vadas@teb-informatika.hr>
PASSWORD_ALPHA_CHARACTERS=<abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ>
PASSWORD_MIN_LENGTH=<0>
PASSWORD_NEW_DIFFERS_BY=<0>
PASSWORD_NOT_LIKE_USERNAME=<N>
PASSWORD_NOT_LIKE_WORDS=<oracle:hello:welcome:guest:user:database>
PASSWORD_NOT_LIKE_WS_NAME=<N>
PASSWORD_ONE_ALPHA=<N>
PASSWORD_ONE_LOWER_CASE=<N>
PASSWORD_ONE_NUMERIC=<N>
PASSWORD_ONE_PUNCTUATION=<N>
PASSWORD_ONE_UPPER_CASE=<N>
PASSWORD_PUNCTUATION_CHARACTERS=<!"#$%&()``*+,-/:;<=>?_>
PLSQL_EDITING=<Y>
PRINT_BIB_LICENSED=<ADVANCED>
PRINT_SVR_HOST=<192.168.168.102>
PRINT_SVR_PORT=<9704>
PRINT_SVR_PROTOCOL=<http>
PRINT_SVR_SCRIPT=</xmlpserver/convert>
REQ_NEW_SCHEMA=<N>
REQUIRE_HTTPS=<N>
SERVICE_REQUEST_FLOW=<MANUAL>
SMTP_FROM=<damir.vadas@teb-informatika.hr>
SMTP_HOST_ADDRESS=<mail.iskon.hr>
SMTP_HOST_PORT=<25>
SQL_SCRIPT_MAX_OUTPUT_SIZE=<200000>
STRONG_SITE_ADMIN_PASSWORD=<N>
WEBSHEET_SQL_ACCESS=<Y>
WORKSPACE_MAX_OUTPUT_SIZE=<2000000>
WORKSPACE_NAME_USER_COOKIE=<Y>
WORKSPACE_PROVISION_DEMO_OBJECTS=<Y>
WORKSPACE_WEBSHEET_OBJECTS=<Y>

46 rows selected.

How to set/reset preferences in a runtime installation?

APEX_INSTANCE_ADMIN.SET_PARAMETER can be used to reset values programatically, if the Administrator GUI interface is not available.
Example.

To reenable the Disable Admin Login preference in APEX 4.0:
  1. Login to SQLPLUS as the SYS user.
  2. Change users to the APEX schema:
    ALTER SESSION SET CURRENT_SCHEMA = APEX_040000;
    
  3. Use the APEX_INSTANCE_ADMIN API to reset the preference value for Disable Workspace Login:
    BEGIN
       APEX_INSTANCE_ADMIN.SET_PARAMETER('DISABLE_ADMIN_LOGIN', 'N');  
       commit;
    END;
    /
    
The values available for use with APEX_INSTANCE_ADMIN.SET_PARAMETER can be found in the Oracle Application Express API Reference "Available Parameter Values" in the APEX_INSTANCE_ADMIN section.

The End

This post is made more like handy manual but to pretend be be some new and curious Oracle theme.

Cheers!

Monday, September 5, 2011

Oracle Database Express Edition 11g Release 2


Finally, while I was on vacation, on 2nd Sptembre 2011, Oracle Database Express Edition 11g Release 2, AKA "Oracle XE", is become a full release for 11g version.

For those who haven't met Oracle XE before, it is the only free edition of Oracle and best way to find what Oracle database is in a way of Microsoft instillation and maintenance.

Beside many other restrictions, this version allows for up to 11Gb of data (4Gb was in previous version-10gR2) and will use only 1 CPU and 1 GB of RAM (server can have more power, but it won't get used by the database).

It comes with Apex 4.0 pre-installed.

You don't get some of the snazzy Enterprise Edition features. No FLASHBACK DATABASE or FLASHBACK TABLE. No PL/SQL Function Result Cache. No Diagnostic or Tuning packs. Or table compression ... etc. .

Remember, you can always upgrade your database to Standard or Enterprise Edition if you outgrow the resource constraints of Express Edition.

Cheers!

Zagreb u srcu!

Copyright © 2009-2018 Damir Vadas

All rights reserved.


Sign by Danasoft - Get Your Sign