Tuesday Jan 21, 2014

Support Implications for Your EBS Customizations

I've published this guidance in various articles before but it never hurts to consolidate it here for new readers.

You may choose to:

  • Modify or extend the E-Business Suite code that we ship
  • Add new database objects or modify existing database objects that we ship
  • Modify our standard EBS database partitioning schemes
  • Introduce various forms of third-party virtualization technologies for any of the E-Business Suite's three tiers -- the database tier, the application server tier, or the desktop tier
  • Use third-party tools to modify your database directly
  • Integrate third-party software with your EBS environment, say, for reporting purposes, or to obtain additional industry-specific functionality
  • Use third-party tools to manage or configure your EBS environment.
Oracle generally considers all of these activities to be some form of customization.  This is not a complete list. Generally speaking, if you have introduced something new into your environment that we haven't tested, we cannot take responsibility for it, so we consider it to be a customization.

Where these activities fall on a risk spectrum depends on their invasiveness.  The more invasive a customization is, the greater its potential risk.  Oracle generally recommends against invasive customizations.

Oracle's official policy on handling customizations is detailed here:

The support implications boil down to this:

  • Issues that are isolated to the E-Business Suite will be investigated by E-Business Suite Development.
  • Issues that are isolated to your customizations or third-party tools should be directed to the third-party vendor.
  • E-Business Suite Development will provide E-Business Suite Development patches for issues that can be reproduced in environments built using E-Business Suite documented procedures and tools.
  • If the third-party vendor cannot resolve issues isolated to their tools, you should restore from a backup and revert to using Oracle’s documented tools and procedures.

Related Articles

Friday Jan 17, 2014

EBS 12.2 Certified with Database 11.2.0.3 for Additional "Database Tier-only" Platforms

I am pleased to announce that Oracle E-Business Suite Release 12.2 (12.2.2 or higher) is now certified with the Oracle Database 11gR2 (11.2.0.3) for the Linux on IBM System z and Oracle Solaris on x86-64 platforms running on the database tier with the following OS versions:

For Oracle Solaris on x86-64:

  • Oracle Solaris 10 on x86-64 (64-bit)
  • Oracle Solaris 11 on x86-64 (64-bit)

For Linux on IBM System z:

  • Red Hat Enterprise Linux (RHEL) version 5 (64-bit)
  • Red Hat Enterprise Linux (RHEL) version 6 (64-bit)
  • Novell SUSE Linux Enterprise Server (SLES) version 10 (64-bit)
  • Novell SUSE Linux Enterprise Server (SLES) version 11 (64-bit)

The application tier of the E-Business Suite 12.2 is not certified with the above platforms, only the database tier; customers must run the application tier on fully certified platforms using the 12.2 software provided as part of our release (see 'Oracle E-Business Suite 12.2 Now Available').

This announcement for E-Business Suite Release 12.2 includes the following (as well as other features and options):

  • Oracle Database 11gR2 version 11.2.0.3
  • Oracle Database Real Application Clusters (RAC) 11gR2 version 11.2.0.3
  • Oracle Database Vault 11gR2 version 11.2.0.3
  • Transparent Data Encryption (TDE) Column Encryption using Oracle Database 11gR2 version 11.2.0.3
  • TDE Tablespace Encryption using Oracle Database 11gR2 version 11.2.0.3
  • Advanced Security Option (ASO)/Advanced Networking Option (ANO) with Oracle Database 11gR2 version 11.2.0.3
  • Export/Import Process for Oracle E-Business Suite Release 12 Database Instances

References

Please also review the platform-specific Oracle Database Installation Guides for operating system and other prerequisites.

Wednesday Jan 15, 2014

Java JRE 1.6.0_71 Certified with Oracle E-Business Suite

Java logo

[Jan. 16, 2014 Update:  replaced Windows versions with a generic pointer to the underlying Notes]

The latest Java Runtime Environment 1.6.0_71 (a.k.a. JRE 6u71-b12) and later updates on the JRE 6 codeline are now certified with Oracle E-Business Suite Release 11i and 12 for Windows-based desktop clients.

Effects of new support dates on Java upgrades for EBS environments

Support dates for the E-Business Suite and Java have changed.  Please review the sections below for more details:

  • What does this mean for Oracle E-Business Suite users?
  • Will EBS users be forced to upgrade to JRE 7 for Windows desktop clients?
  • Will EBS users be forced to upgrade to JDK 7 for EBS application tier servers?

All JRE 6 and 7 releases are certified with EBS upon release

Our standard policy is that all E-Business Suite customers can apply all JRE updates to end-user desktops from JRE 1.6.0_03 and later updates on the 1.6 codeline, and from JRE 7u10 and later updates on the JRE 7 codeline.  We test all new JRE 1.6 and JRE 7 releases in parallel with the JRE development process, so all new JRE 1.6 and 7 releases are considered certified with the E-Business Suite on the same day that they're released by our Java team. 

You do not need to wait for a certification announcement before applying new JRE 1.6 or JRE 7 releases to your EBS users' desktops.

What's new in in this Java release?

Java 6 is now available only via My Oracle Support for E-Business Suite users.  You can find links to this release, including Release Notes, documentation, and the actual Java downloads here:

Both JDK and JRE packages are contained in a single combined download after 6u45.  Download the "JDK" package for both the desktop client JRE and the server-side JDK package.

32-bit and 64-bit versions certified

This certification includes both the 32-bit and 64-bit JRE versions for various Windows operating systems. See the respective Deploying JRE documentation for your EBS release for details.

Worried about the 'mismanaged session cookie' issue?

No need to worry -- it's fixed.  To recap: JRE releases 1.6.0_18 through 1.6.0_22 had issues with mismanaging session cookies that affected some users in some circumstances.

The fix for those issues was first included in JRE 1.6.0_23. These fixes will carry forward and continue to be fixed in all future JRE releases.  In other words, if you wish to avoid the mismanaged session cookie issue, you should apply any release after JRE 1.6.0_22.

Implications of Java 6 End of Public Updates for EBS Users

The Support Roadmap for Oracle Java is published here:

The latest updates to that page (as of Sept. 19, 2012) state (emphasis added):

Java SE 6 End of Public Updates Notice

After February 2013, Oracle will no longer post updates of Java SE 6 to its public download sites. Existing Java SE 6 downloads already posted as of February 2013 will remain accessible in the Java Archive on Oracle Technology Network. Developers and end-users are encouraged to update to more recent Java SE versions that remain available for public download. For enterprise customers, who need continued access to critical bug fixes and security fixes as well as general maintenance for Java SE 6 or older versions, long term support is available through Oracle Java SE Support .

What does this mean for Oracle E-Business Suite users?

EBS users fall under the category of "enterprise users" above.  Java is an integral part of the Oracle E-Business Suite technology stack, so EBS users will continue to receive Java SE 6 updates from February 2013 to the end of Java SE 6 Extended Support in June 2017.

In other words, nothing changes for EBS users after February 2013. 

EBS users will continue to receive critical bug fixes and security fixes as well as general maintenance for Java SE 6 until the end of Java SE 6 Extended Support in June 2017. 

How can EBS customers obtain Java 6 updates after the public end-of-life?

EBS customers can download Java 6 patches from My Oracle Support.  For a complete list of all Java SE patch numbers, see:

Will EBS users be forced to upgrade to JRE 7 for Windows desktop clients?

This upgrade is highly recommended but remains optional while Java 6 is covered by Extended Support. Updates will be delivered via My Oracle Support, where you can continue to receive critical bug fixes and security fixes as well as general maintenance for JRE 6 desktop clients. 

Java 6 is covered by Extended Support until June 2017.  All E-Business Suite customers must upgrade to JRE 7 by June 2017.

Coexistence of JRE 6 and JRE 7 on Windows desktops

The upgrade to JRE 7 is highly recommended for EBS users, but some users may need to run both JRE 6 and 7 on their Windows desktops for reasons unrelated to the E-Business Suite.

Most EBS configurations with IE and Firefox use non-static versioning by default. JRE 7 will be invoked instead of JRE 6 if both are installed on a Windows desktop. For more details, see "Appendix B: Static vs. Non-static Versioning and Set Up Options" in Notes 290807.1 and 393931.1.

Applying Updates to JRE 6 and JRE 7 to Windows desktops

Auto-update will keep JRE 7 up-to-date for Windows users with JRE 7 installed.

Auto-update will only keep JRE 7 up-to-date for Windows users with both JRE 6 and 7 installed. 

JRE 6 users are strongly encouraged to apply the latest Critical Patch Updates as soon as possible after each release. The Jave SE CPUs will be available via My Oracle Support.  EBS users can find more information about JRE 6 and 7 updates here:

The dates for future Java SE CPUs can be found on the Critical Patch Updates, Security Alerts and Third Party Bulletin.  An RSS feed is available on that site for those who would like to be kept up-to-date.

What do Mac users need?

Mac users running Mac OS X 10.9 can run JRE 7 plug-ins.  See this article:

Will EBS users be forced to upgrade to JDK 7 for EBS application tier servers?

JRE is used for desktop clients.  JDK is used for application tier servers

JDK upgrades for E-Business Suite application tier servers are highly recommended but currently remain optional while Java 6 is covered by Extended Support. Updates will be delivered via My Oracle Support, where you can continue to receive critical bug fixes and security fixes as well as general maintenance for JDK 6 for application tier servers. 

Java SE 6 is covered by Extended Support until June 2017.  All EBS customers with application tier servers on Windows, Solaris, and Linux must upgrade to JDK 7 by June 2017. EBS customers running their application tier servers on other operating systems should check with their respective vendors for the support dates for those platforms.

JDK 7 is certified with E-Business Suite 12.  See:

References

    Related Articles

    Java JRE 1.7.0_51 Certified with Oracle E-Business Suite

    Java logoJava Runtime Environment 7u51 (a.k.a. JRE 7u51-b13) and later updates on the JRE 7 codeline are now certified with Oracle E-Business Suite Release 11i and 12.0, 12.1, and 12.2 for Windows-based desktop clients.

    Effects of new support dates on Java upgrades for EBS environments

    Support dates for the E-Business Suite and Java have changed.  Please review the sections below for more details:

    • What does this mean for Oracle E-Business Suite users?
    • Will EBS users be forced to upgrade to JRE 7 for Windows desktop clients?
    • Will EBS users be forced to upgrade to JDK 7 for EBS application tier servers?

    All JRE 6 and 7 releases are certified with EBS upon release

    Our standard policy is that all E-Business Suite customers can apply all JRE updates to end-user desktops from JRE 1.6.0_03 and later updates on the 1.6 codeline, and from JRE 7u10 and later updates on the JRE 7 codeline.  We test all new JRE 1.6 and JRE 7 releases in parallel with the JRE development process, so all new JRE 1.6 and 7 releases are considered certified with the E-Business Suite on the same day that they're released by our Java team. 

    You do not need to wait for a certification announcement before applying new JRE 1.6 or JRE 7 releases to your EBS users' desktops.

    New Features in JRE 1.7.0_51

    For a full list of new features included in this JRE release, see the JRE 1.7.0_51 Update Release Notes. Amongst other changes and features this includes:

    Changes to Security Slider
    • Self-Signed and Unsigned applets are now blocked on the default 'High' Security Setting. This setting also requires the inclusion of the 'permission' attribute.
    • For information on signing jar files with a 'Trusted Certificate', see Enhanced Jar Signing for Oracle E-Business Suite (Note 1591073.1)

    Exception Site List

    • The 'Exception Site List'  allows end users to control  their own application whitelist to by-pass a number of security rules. For example this would allow applications and sites to run even though they are using using self-signed certificates for example. For further information on this feature see the  Java SE Exception Site List document.

    32-bit and 64-bit versions certified

    This certification includes both the 32-bit and 64-bit JRE versions for various Windows operating systems. See the respective Recommended Browser documentation for your EBS release for details.

    Where are the official patch requirements documented?

    All patches required for ensuring full compatibility of the E-Business Suite with JRE 7 are documented in these Notes:

    For EBS 11i:

    For EBS 12.0, 12.1, 12.2
    EBS + Discoverer 11g Users

    JRE 1.7.0_51 is certified for Discoverer 11g in E-Business Suite environments with the following minimum requirements:

    Worried about the 'mismanaged session cookie' issue?

    No need to worry -- it's fixed.  To recap: JRE releases 1.6.0_18 through 1.6.0_22 had issues with mismanaging session cookies that affected some users in some circumstances.

    The fix for those issues was first included in JRE 1.6.0_23. These fixes will carry forward and continue to be fixed in all future JRE releases on the JRE 6 and 7 codelines.  In other words, if you wish to avoid the mismanaged session cookie issue, you should apply any release after JRE 1.6.0_22 on the JRE 6 codeline, and JRE 7u10 and later JRE 7 codeline updates.

    Implications of Java 6 End of Public Updates for EBS Users

    The Support Roadmap for Oracle Java is published here:

    The latest updates to that page (as of Sept. 19, 2012) state (emphasis added):

    Java SE 6 End of Public Updates Notice

    After February 2013, Oracle will no longer post updates of Java SE 6 to its public download sites. Existing Java SE 6 downloads already posted as of February 2013 will remain accessible in the Java Archive on Oracle Technology Network. Developers and end-users are encouraged to update to more recent Java SE versions that remain available for public download. For enterprise customers, who need continued access to critical bug fixes and security fixes as well as general maintenance for Java SE 6 or older versions, long term support is available through Oracle Java SE Support .

    What does this mean for Oracle E-Business Suite users?

    EBS users fall under the category of "enterprise users" above.  Java is an integral part of the Oracle E-Business Suite technology stack, so EBS users will continue to receive Java SE 6 updates from February 2013 to the end of Java SE 6 Extended Support in June 2017.

    In other words, nothing changes for EBS users after February 2013. 

    EBS users will continue to receive critical bug fixes and security fixes as well as general maintenance for Java SE 6 until the end of Java SE 6 Extended Support in June 2017.

    How can EBS customers obtain Java 6 updates after the public end-of-life?

    EBS customers can download Java 6 patches from My Oracle Support.  For a complete list of all Java SE patch numbers, see:

    Both JDK and JRE packages are contained in a single combined download after 6u45.  Download the "JDK" package for both the desktop client JRE and the server-side JDK package. 

    Will EBS users be forced to upgrade to JRE 7 for Windows desktop clients?

    This upgrade is highly recommended but remains optional while Java 6 is covered by Extended Support. Updates will be delivered via My Oracle Support, where you can continue to receive critical bug fixes and security fixes as well as general maintenance for JRE 6 desktop clients. 

    Java 6 is covered by Extended Support until June 2017.  All E-Business Suite customers must upgrade to JRE 7 by June 2017.

    Coexistence of JRE 6 and JRE 7 on Windows desktops

    The upgrade to JRE 7 is highly recommended for EBS users, but some users may need to run both JRE 6 and 7 on their Windows desktops for reasons unrelated to the E-Business Suite.

    Most EBS configurations with IE and Firefox use non-static versioning by default. JRE 7 will be invoked instead of JRE 6 if both are installed on a Windows desktop. For more details, see "Appendix B: Static vs. Non-static Versioning and Set Up Options" in Notes 290807.1 and 393931.1.

    Applying Updates to JRE 6 and JRE 7 to Windows desktops

    Auto-update will keep JRE 7 up-to-date for Windows users with JRE 7 installed.

    Auto-update will only keep JRE 7 up-to-date for Windows users with both JRE 6 and 7 installed. 

    JRE 6 users are strongly encouraged to apply the latest Critical Patch Updates as soon as possible after each release. The Jave SE CPUs will be available via My Oracle Support.  EBS users can find more information about JRE 6 and 7 updates here:

    The dates for future Java SE CPUs can be found on the Critical Patch Updates, Security Alerts and Third Party Bulletin.  An RSS feed is available on that site for those who would like to be kept up-to-date.

    What do Mac users need?

    Mac users running Mac OS X 10.9 can run JRE 7 plug-ins.  See this article:

    Will EBS users be forced to upgrade to JDK 7 for EBS application tier servers?

    JRE is used for desktop clients.  JDK is used for application tier servers

    JDK upgrades for E-Business Suite application tier servers are highly recommended but currently remain optional while Java 6 is covered by Extended Support. Updates will be delivered via My Oracle Support, where you can continue to receive critical bug fixes and security fixes as well as general maintenance for JDK 6 for application tier servers. 

    Java SE 6 is covered by Extended Support until June 2017.  All EBS customers with application tier servers on Windows, Solaris, and Linux must upgrade to JDK 7 by June 2017. EBS customers running their application tier servers on other operating systems should check with their respective vendors for the support dates for those platforms.

    JDK 7 is certified with E-Business Suite 12.  See:

    References

    Related Articles

    Tuesday Jan 14, 2014

    Critical Patch Update for January 2014 Now Available

    The  Critical Patch Update (CPU) for January 2014 was released on January 14, 2014.  Oracle strongly recommends applying the patches as soon as possible.

    The Critical Patch Update Advisory is the starting point for relevant information. It includes a list of products affected, pointers to obtain the patches, a summary of the security vulnerabilities, and links to other important documents.

    Supported products that are not listed in the "Supported Products and Components Affected" Section of the advisory do not require new patches to be applied.

    Also, it is essential to review the Critical Patch Update supporting documentation referenced in the Advisory before applying patches, as this is where you can find important pertinent information.

    The Critical Patch Update Advisory is available at the following location:

    The next four Critical Patch Update release dates are:

    • April 15, 2014
    • July 15, 2014
    • October 14, 2014
    • January 13, 2015
    E-Business Suite Releases 11i and 12 Reference

    Monday Jan 13, 2014

    EBS Release 12 Certified with Mac OS X 10.9 with Safari 7 and JRE 7

    Apple logoOracle E-Business Suite Release 12 (12.1.1 or higher) is now certified with the Safari 7 browser and the JRE 7 plugin on the following Apple Mac OS X desktop configuration:

    • Mac OS X 10.9 ("Mavericks" version 10.9.1 or higher)
    • Safari version 7 (7.0.1 or higher)
    • Oracle JRE 7 plugin (1.7.0_45 or higher)

    Users should review all relevant information along with other specific patching requirements and known limitations posted in the Notes listed below.

    References

     Related Articles

    Wednesday Jan 08, 2014

    Java (JDK) 7 Certified with E-Business Suite 12.2 Servers

    Java logoOracle E-Business Suite 12.2 shipped with Java SE (JDK) 6 as part of its Rapid Install technology stack. 

    Java (JDK) 7 is now certified for EBS 12.2 application and database tier servers.  See:

    You can apply the Java 7 update on all tier nodes:

    • Java 6.0 either Oracle JRockit (JRockit) or Java SE Development Kit (JDK), on the application tier
    • 32-bit or 64-bit Java 6 for use by Oracle WebLogic Server 11.1.1.6.0 only
    • Non-WebLogic middle tier nodes using 32-bit Java version 6.0 only
    • Java SE Development Kit (JDK) version 6.0 on the OracleAS 10g 10.1.2 application tier hosting Oracle Forms and Reports services
    • Java SE Runtime Environment (JRE) version 6.0 on the database tier

    End-users can use either JRE 6 or 7 on their Windows desktop clients to run Forms-based products in EBS 12.2.

    Implications of Java 6 End of Public Updates for EBS Users

    The Support Roadmap for Oracle Java is published here:

    The latest updates to that page (as of Sept. 19, 2012) state:

    Java SE 6 End of Public Updates Notice

    After February 2013, Oracle will no longer post updates of Java SE 6 to its public download sites. Existing Java SE 6 downloads already posted as of February 2013 will remain accessible in the Java Archive on Oracle Technology Network. Developers and end-users are encouraged to update to more recent Java SE versions that remain available for public download. For enterprise customers, who need continued access to critical bug fixes and security fixes as well as general maintenance for Java SE 6 or older versions, long term support is available through Oracle Java SE Support .

    What does this mean for Oracle E-Business Suite users?

    EBS users fall under the category of "enterprise users" above.  Java is an integral part of the Oracle E-Business Suite technology stack, so EBS users will continue to receive Java SE 6 updates from February 2013 to the end of Java SE 6 Extended Support in June 2017.

    In other words, nothing changed for EBS users after February 2013. 

    EBS users will continue to receive critical bug fixes and security fixes as well as general maintenance for Java SE 6. These Java SE 6 updates will be made available to EBS users for the Extended Support periods documented in the Oracle Lifetime Support policy document for Oracle Applications (PDF).

    How can EBS customers obtain Java 6 updates after the public end-of-life?

    EBS customers can download Java 6 patches from My Oracle Support.  For a complete list of all Java SE patch numbers, see:

    Will EBS users be forced to upgrade to JDK 7 for EBS Servers?

    No. This upgrade will be highly recommended but will be optional for EBS application tier servers running on Windows, Linux, and Solaris.  You can choose to remain on JDK 6 for the duration of your respective EBS Extended Support period.  If you remain on JDK 6, you will continue to receive critical bug fixes and security fixes as well as general maintenance for JDK 6.

    Will EBS users be forced to upgrade to JRE 7 for Windows desktop clients?

    No. This upgrade will be highly recommended but currently remains optional. JRE 6 desktop clients can connect to EBS 12.2 environments running JDK 7.

    JRE 6 will be available to Windows users to run with EBS to the end of Java SE 6 Extended Support in June 2017.  Updates will be delivered via My Oracle Support, where you can continue to receive critical bug fixes and security fixes as well as general maintenance for JRE 6 desktop clients. 

    Coexistence of JRE 6 and JRE 7 on Windows desktops

    The upgrade to JRE 7 is highly recommended for EBS users, but some users may need to run both JRE 6 and 7 on their Windows desktops for reasons unrelated to the E-Business Suite.

    Most EBS configurations with IE and Firefox use non-static versioning by default. JRE 7 will be invoked instead of JRE 6 if both are installed on a Windows desktop. For more details, see "Appendix B: Static vs. Non-static Versioning and Set Up Options" in Notes 290801.1 and 393931.1.

    Applying Updates to JRE 6 and JRE 7 to Windows desktops

    Auto-update will keep JRE 7 up-to-date for Windows users with JRE 7 installed.

    Auto-update will only keep JRE 7 up-to-date for Windows users with both JRE 6 and 7 installed. 

    JRE 6 users are strongly encouraged to apply the latest Critical Patch Updates as soon as possible after each release. The Jave SE CPUs will be available via My Oracle Support.  EBS users can find more information about JRE 6 and 7 updates here:

    The dates for future Java SE CPUs can be found on the Critical Patch Updates, Security Alerts and Third Party Bulletin.  An RSS feed is available on that site for those who would like to be kept up-to-date.

    Will EBS users be forced to upgrade to JDK 7 for EBS application tier servers?

    No. This upgrade will be highly recommended but will be optional for EBS application tier servers running on Windows, Linux, and Solaris.  You can choose to remain on JDK 6 to the end of Java SE 6 Extended Support in June 2017.  If you remain on JDK 6, you will continue to receive critical bug fixes and security fixes as well as general maintenance for JDK 6 to the end of June 2017.

    Summary of EBS Certifications

    There is a one-page summary of all of the latest E-Business Suite techstack certifications here:

    • http://blogs.oracle.com/stevenChan/resource/certifications.html

    This listing summarizes the official CERTIFY database on My Oracle Support.  The CERTIFY database is the official and authoritative reference for all E-Business Suite certifications.

    Related Articles


    Monday Jan 06, 2014

    ATG Live Webcast Jan. 8th: Advanced EBS Management using Enterprise Manager

    I'm pleased to announce our first webcast of the year:

    • Oracle Enterprise Manager: Advanced Management of Oracle E-Business Suite
      Wednesday, January 8, 2014
      10:00 AM Pacific Standard Time

    You will receive links to the live webcast after you register here:

    Angelo Rosado and Vasu Rao, EBS Product Management, will provide an update on the latest Application Management Pack features for managing E-Business Suite environments with Oracle Enterprise Manager 12c.  They will cover AMP features such as:

    • Online Patching with E-Business Suite 12.2
    • Customization management 
    • Cloning
    • System monitoring
    • Configuration and compliance management 

    They will also provide a glimpse of the product roadmap, and you will have the opportunity to ask questions during the live webcast.

    EM12c AMP 12.1.0.2 screenshot

    Related Articles


    Friday Jan 03, 2014

    Which JDeveloper Version Works With Your EBS Release?

    JDeveloper logoWhen you create extensions to Oracle E-Business Suite OA Framework pages, you must use the version of Oracle JDeveloper shipped by the Oracle E-Business Suite product team.

    The version of Oracle JDeveloper is specific to the Oracle E-Business Suite Applications Technology patch level, so there is a new version of Oracle JDeveloper with each new release of the Oracle E-Business Suite Applications Technology patchset.

    This Note lists the JDeveloper with OA Extension updates for EBS 11i, 12.0, 12.1, and 12.2:

    Related Articles

    About

    Search

    Categories
    Archives
    « January 2014 »
    SunMonTueWedThuFriSat
       
    1
    2
    4
    5
    7
    9
    10
    11
    12
    16
    18
    19
    20
    22
    23
    24
    25
    26
    27
    28
    29
    30
    31
     
           
    Today