Oracle Retail

Rapid Installation Overview

December 2010
Note: The following is intended to outline our general
product direction. It is intended for information purposes
only, and may not be incorporated into any contract. It is not
a commitment to deliver any material, code, or functionality,
and should not be relied upon in making purchasing
decisions. The development, release, and timing of any
features or functionality described for Oracles products
remains at the sole discretion of Oracle.

i
 Contents
Contents............................................................................................................................. ii
Send Us Your Comments................................................................................................ iii
Rapid Installation .............................................................................................................. 1
Approach..................................................................................................................................1
Source ................................................................................................................................2
Target.................................................................................................................................3
Process Outline.................................................................................................................3
Known Issues and Limitations..............................................................................................4

ii
 Send Us Your Comments
Oracle welcomes customers' comments and suggestions on the quality and usefulness of
this document.
Your feedback is important and helps us to best meet your needs as a user of our
products.
For example:
Are the implementation steps correct and complete?
Did you understand the context of the information?
Did you find any errors in the information?
Does the structure of the information help you with your tasks?
Do you need different information or graphics? If so, where, and in what format?
Are the examples correct? Do you need more examples?
This document was created by the Implementation Tools team. The Implementation
Tools team is a solution unit within the Oracle Retail Research & Development
organization focused on reducing Total Cost of Ownership and Total Cost of
Implementation across the Oracle Retail Enterprise Suite. The Implementation Tools
team fosters ongoing partnership and collaboration across Oracle Retail, integration
partners, and clients to create tools/utilities/processes to improve the ease of Oracle
Retail implementations.
If you have feedback/suggestions on how to improve this document, please contact the
Implementation Tools team: RGBU-Implementation-Tools@oracle.com.

iii
 Rapid Installation
This document provides the case study details about using an existing Oracle Retail 13.1
environment enabled for Single Sign-On (SSO) to create another environment like it,
while maintaining many of the same configurations and data. This is not intended to be a
step by step guide, and is not an automated process.
The resulting target environment cannot be considered an exact replica of the source;
although the data and many of the configurations would remain the same across
environments. The process which has been documented for this effort outlines the
manual steps used to create an entire second environment, such as an Oracle database,
middle tier, and retail applications, based on an existing environment. It is specific to
Oracle Linux 5.2, and version 13.1 of a specific Oracle Retail application footprint such as
RMS, RWMS, RPM, SIM, ReIM, Allocation, and RSL.
While it is not designed to be a certified process, the intent is to show a well documented
approach that can be referenced to see how it was done in this case study. While
variations might exist on other platforms, the overall approach would likely remain the
same. Where available, the underlying Oracle infrastructure cloning functionality was
used; however some of the components dont support this functionality. Additionally,
many of the retail applications in this scenario do not readily lend themselves to be
copied and altered. In these cases, the process to install these components was
documented in order to be used as a reference to accelerate the overall installation effort
into the target environment.
Using the process described in these documents has the following benefits:
Reduce the overall time it takes to create subsequent environments based on a source
environment.
Minimize the time and effort required to set up LDAP data for subsequent
environments.
Ensure that the underlying application data is the same between environments at the
time of the copy.

Approach
The approach taken in this case study was to create a target environment, based on a
source environment, while cloning or copying as many components as feasibly possible
to shorten the time required to build the target environment. There is more than one way
to achieve the end result, and this case study outlines choices based on time and
reliability. For these reasons, the middle tier (forms and reports) has been reinstalled in
the target environment as opposed to cloning it. The target environment has a dedicated
OID in which the data is exported and imported from the source OID, eliminating the
need to recreate the LDAP data needed for the retail applications in the target
environment. The retail database is copied over and renamed, since this database already
contains the installed retail schemas from the source environment. The retail schema
names themselves are not changed from the source to target environment in order to
reduce the number of changes that need to be made in the target environment
configurations.

Rapid Installation 1
Approach

Due to complexities of changing the internal configurations of some deployed retail

applications, the easiest and safest way is to reinstall the java apps (RPM, SIM, ReIM,
Allocation, RSL) in the target instance using the Oracle Retail installers, rather than
reconfiguring them after cloning the OAS. This can be easily achieved by using the
ant.install.properties files from the source instance installations, changing the values
where appropriate, and running the app installer in the target environment. Since the
installer takes care of updating all of the properties files as well as archive files within the
instance, it is less work than updating individual files and will ensure consistent results.
The source code for forms applications (RMS, RWMS) is copied from source to target and
the URLs are created on the target server, as well as some other configuration changes to
support the forms applications. Lastly, RIB is reinstalled on the target instance using the
packaged RIB installer.

Source
The diagram below outlines the source environment used in the case study. The source
environment consists of 4 Oracle Linux 5.2 Oracle VM images. The source environment
does contain infrastructure and retail apps not listed below; however the scope of this
effort only includes those which are listed below.

ordbsrv orappsrv01
RDBMS 11.1.0.7 Infra/Midtier 10.1.2.3
RMS 13.1 schema RDBMS 10.1.0.5 w/ metadata repository
RWMS 13.1 schema Identity management services
SIM 13.1 schema Forms server
RMS 13.1
RWMS 13.1
SOA Suite 10.1.3.4
RPM 13.1
SIM 13.1

orappsrv02 orribsrv
OAS 10.1.3.4 OAS 10.1.3.4
Alloc 13.1 RIB 13.1
ReIM 13.1
RSL 13.1

2 Oracle Retail
 Approach

Target
The diagram below outlines the target environment. The target environment consists of
three Oracle Linux 5.2 servers.

mspdv356 mspdv357
RDBMS 11.1.0.7 Infra/Midtier 10.1.2.3
RMS 13.1 schema Identity management services
RWMS 13.1 schema Forms server
SIM 13.1 schema RMS 13.1
RDBMS 10.2.0.4 RWMS 13.1
OID metadata repository SOA Suite 10.1.3.4
RPM 13.1
SIM 13.1

mspdv358
OAS 10.1.3.4
Alloc 13.1
ReIM 13.1
RSL 13.1
OAS 10.1.3.4
RIB 13.1

Process Outline
Below is a general outline of the rapid installation process. The outline includes
references to the My Oracle Support articles that you should consult for each step. All of
these documents can be found on My Oracle Support (https://support.oracle.com)
under Article ID 1196607.1.

Step 1: Exporting OID

Rapid Installation Step 1: Exporting OID
Export source LDAP data from OID (source)

Step 2: Installing Oracle Database 10.2.0.4

Rapid Installation Step 2: Installing RDBMS 10.2.0.4
Install 10.2.0.4 Oracle Database software (target)
Create metadata repository using repca (target)

Step 3: Installing Oracle Application Server Infrastructure/Midtier

Rapid Installation Step 3: Installing Oracle Application Server Infrastructure/Midtier
Install and patch the infrastructure and midtier (target)
Upgrade metadata repository (target)

Step 4: Importing OID

Rapid Installation Step 4: Importing OID
Import LDAP data into target OID (target)

Rapid Installation 3
Known Issues and Limitations

Step 5: Cloning 11g RDBMS and Copying Retail Database

Rapid Installation Step 5: Cloning 11g RDBMS and Copying Retail Database
Clone RDBMS 11.1.0.7 software and copy retail database (source to target)
Step 6: Copying and Configuring RMS and RWMS
Rapid Installation Step 6: Copying and Configuring RMS and RWMS
Copy RMS batch and forms and reconfigure (source to target)
Copy RWMS forms and reports and reconfigure (source to target)

Step 7: Cloning Oracle Application Server 10.1.3 and Reinstalling Java

Applications
Rapid Installation Step 7: Cloning Oracle Application Server 10.1.3 and Reinstalling Java
Applications
Clone OracleAS Suite 10.1.3.4 (source to target)
Reregister cloned OracleAS Suite to target OID (target)
Reinstall RPM and SIM (target)
Clone OracleAS 10.1.3.4 (source to target)
Reregister cloned OracleAS to target OID (target)
Reinstall Allocation, ReIM, and RSL applications (target)
Clone OracleAS 10.1.3.4 (source to target)
Install RIB (target)
Refer to the Oracle Retail Integration Bus Installation Guide for this task.

Known Issues and Limitations

1. The Oracle Identity Management and OracleAS Metadata Repository used as part of
this case study cannot be cloned. (Cloning is not supported.) It must be reinstalled on
the target instance.
2. The approach taken in this case study was to reinstall the middle tier (forms and
reports) in the target instance as opposed to cloning it from the source instance.
Cloning of the middle tier is supported; however that approach is out of scope for
this case study.
3. Based on feedback from internal and external resources, RIB cannot be successfully
cloned. Previous attempts at this have failed, and the installation is straightforward
so cloning would not necessarily save time.
4. At the time of this case study, the internal configurations for the retail java
applications (RPM, SIM, Allocation, ReIM, RSL) in the cloned OAS do not lend
themselves to be readily updated after cloning. Additional work needs to be done in
order to define all of the necessary changes that need to be made, which is out of
scope for this effort.

4 Oracle Retail
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores, CA 94065
U.S.A.

Worldwide Inquiries:
Phone: +1.650.506.7000
Fax: +1.650.506.7200
oracle.com

Copyright 2010, Oracle. All rights reserved.

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 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.
Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle
Corporation and/or its affiliates. Other names may be trademarks
of their respective owners.