|INFORMATION INDEPTH NEWSLETTER
|Back to the main page
|Newly Simplified Installations, Patches, and Upgrades for Oracle Retail
In order to speed and simplify installations, patches, and upgrades, the Oracle Retail team has launched a new initiative that includes new content creation, more intuitive processes, and easier access to key documentation.
"Our goal is to make the installation process as simple and intuitive as possible," explains John Gray, chief technology officer and vice president, software development, Oracle Retail "We made great strides by replacing manual processes with automated installers beginning with release 12, and we continue to make significant installation improvements."
Installation improvements include
In addition, bill of materials for Oracle Retail Release 13.2, Oracle Retail Releases 13.3, and Oracle Retail Releases 13.4 Application Documentation are available in My Oracle Support. Log in and search on document ID 1393491.1 to find a snapshot of more than 200 pieces of documentation that help customers install, use, and understand Oracle Retail applications.
- Improved installation guides. Oracle Retail installation guides now feature a more unified look and feel.
- Installer enhancements. Starting with release 13.2, the Oracle Retail Warehouse Management System installation is no longer manual, and security features have been enhanced, including file permissions, password encryption, and more.
- More flexible configurations. Starting with release 13.2.3, application properties files have been moved outside of the ear/war file for Oracle Retail Invoice Matching and Oracle Retail Allocation.
To improve the patching experience, Oracle Retail has made installers both more effective and more user-friendly. New, more-standardized and more-detailed documentation offerings also help speed patching processes. Finally, Oracle Retail has more clearly defined the three methods for distributing issue resolutions to customers.
Enhanced Upgrade Assistance
- Bundled hotfixes. Scheduled for release every 6 to 12 weeks, bundled hotfixes will consist of a group of fixes (irrespective of customer or severity) completed since the last bundled release, release notes, and defect documents. All bundled hotfix releases will be regression-tested prior to release.
- Patches. Scheduled for release every 6 to 12 months, patches will consist of all bundled hotfixes released since the last patch, release notes, and defect documents. Patches may also include enhancements, technical certifications, or critical forward ports. All patches will be integration-tested prior to release.
- Ad hoc individual hotfixes. Released on an exception basis, each ad hoc individual hotfix will consist of one customer-specific bug fix resolved on the latest bundled hotfixes release, plus a defect document. All ad hoc individual hotfixes will be unit-tested prior to release.
To assist customers with upgrading their Oracle Retail applications and technology stacks, several documents have recently been made available. To access the documents, log in to My Oracle Support and search on the document IDs provided.
Bookmark these resources today—Oracle Retail documentation on OTN, the Oracle Retail documentation blog, and the RACK—and benefit from quick, easy access to the latest documentation updates.
- Oracle Retail Documentation Enhancements Summary (1393487.1)
This document captures all the major documentation changes for recent Oracle Retail releases.
- Oracle Retail Enterprise Implementation Best Practices (1189453.1)
This article offers a series of guidelines that summarize best practices for a successful enterprisewide Oracle Retail implementation. The guidelines are organized in checklist format by project phase, from implementation planning and staffing to post-rollout support. The content represents years of successful experience assisting our customers in all phases of their implementation projects.
- Approaches to RIB Integration of Oracle Retail Mixed Application Versions (1359915.1)
This document addresses the issues and possible approaches to mixed version deployments of Oracle Retail applications that are integrated by the Oracle Retail Integration Bus (RIB).
- Data Conversion Planning Guide (742229.1)
This document describes a generic approach to data conversion for Oracle Retail Merchandising System, defines the scope and purpose of the merchandising conversion toolkit, and recommends the methods and process that should be followed in a typical conversion project.
- Oracle Retail Reference Model (1145264.1)
The business process designs that make up the Oracle Retail reference model are intended to support implementations of merchandising, stores, and planning products. They explain some scenarios and factors that need to be considered for a successful implementation.
- Oracle Retail 13.2 Data Models (1296566.1)
Here you will find data models for all Oracle Retail products.
- Oracle Retail Infrastructure Compatibilities (857142.1)
Here we provide a detailed list of the infrastructure recommended for running each Oracle Retail product and the integration among Oracle Retail products. This document provides infrastructure information and integration information for the generally available 12.x and 13.x releases.
- Oracle Retail Merchandising System: Extending the Custom Flex Attribute Solution (1285660.1)
Custom Flex Attribute Solution for Oracle Retail Merchandising System is a metadata driven framework that can be used to support client-specific customizations. It is designed in such a manner that certain pre-existing form windows can be easily customized to include additional fields or attributes. Oracle Retail Merchandising System 13.2 includes a set of entities that are pre-enabled for the Custom Flex Attribute Solution. This white paper highlights how you can extend the Custom Flex Attribute Solution framework for entities that are not pre-enabled.
- Oracle Retail Merchandising System Upgrade Tools (1368413.1)
This white paper includes information about in-release technology upgrade patches, in-release upgrade tools, and application upgrade jump-points.
- Oracle Retail Reference Architecture (1313281.1 and 1330740.1)
These documents help explain how Oracle Retail products fit together and provide insight into how to optimally deploy the products on various technical platforms.
- Upgrade Guide: Oracle Retail 13.1 to Oracle Retail 13.2 (1073414.1)
As the upgrade process varies among Oracle Retail applications, the Oracle Retail upgrade guide describes the approach taken for each Oracle Retail application, as well as product-specific upgrade assumptions and considerations. Actual procedures for the upgrade may be included in corresponding installation guides.
|Back to Top
|Oracle Information InDepth newsletters bring targeted news, articles, customer stories, and special offers to business people who want to find out how to streamline enterprise information management, measure results, improve business processes, and communicate a single truth to their constituents.
Please send questions or comments to email@example.com.
For answers to questions about subscribing, unsubscribing, and managing your Oracle e-mail communications preferences, please see the Oracle E-Mail Communications page.
Copyright © 2012, Oracle Corporation and/or its affiliates. All rights reserved. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
This document is provided for information purposes only, and the contents hereof are subject to change without notice. This document is not warranted to be error-free, nor is it subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any liability with respect to this document, and no contractual obligations are formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission.