Академический Документы
Профессиональный Документы
Культура Документы
Version 11.1
Oracle ATG
One Main Street
Cambridge, MA 02142
USA
Commerce Reference Store Installation and Configuration Guide
Product version: 11.1
Release date: 06-27-14
Document identifier: CrsInstallationAndConfigurationGuide1502251324
Copyright 1997, 2014 Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are
protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy,
reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any
means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please
report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government,
the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the
hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable
Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and
adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or
documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S.
Government.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended
for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or
hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures
to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in
dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are
trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or
registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information on content, products, and services from third parties.
Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party
content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to
your access to or use of third-party content, products, or services.
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/
topic/lookup?ctx=acc&id=docacc.
Access to Oracle Support: Oracle customers have access to electronic support through My Oracle Support. For information, visit http://
www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing
impaired.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Commerce Reference Store for Mobile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
2. Installation Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Commerce Reference Store Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Installation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Before Installing Oracle Commerce Platform Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Identifying Your Environment and Add-on Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Setting Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Installing the Oracle Commerce Platform and Commerce Reference Store Software . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Installing on Linux with GCJ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Installing the Oracle Commerce Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Installing Commerce Reference Store . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Starting the Application Server (WebLogic and WebSphere Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Creating a Shared Archive Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Configuring the Oracle Commerce Platform Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Starting CIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Setting the Administrator Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Configuring Oracle Commerce Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Selecting an Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Configuring Your Database Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Configuring a Security Credential for User Segment Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Configuring Your Oracle Commerce Platform Server Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Creating the EAC Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Assembling and Deploying Your Oracle Commerce Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Reducing Logging Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Additional Oracle Commerce Platform Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Additional Application Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
WebLogic Configuration (WebLogic Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Additional WebSphere Configuration (WebSphere Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Starting the Publishing and Production Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
WebLogic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
JBoss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
WebSphere . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Browsing the Publishing and Production Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Browsing the Publishing Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Browsing the Production Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Configuring and Running a Full Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Configuring the Deployment Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Checking the Baseline Index Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Promoting the Commerce Reference Store Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Accessing the Storefront . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Adding the User Segment Credential to the Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Configuring Incremental Change Tracking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
3. Uninstalling Commerce Reference Store . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Stopping the Publishing and Production Servers and Removing Their Artifacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Stopping the Servers and Removing Artifacts on WebLogic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Stopping the Servers on JBoss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Stopping the Servers and Removing Their Artifacts on WebSphere . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Dropping the Oracle Commerce Schemas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
This document describes how to install and configure Oracle Commerce Reference Store on the WebLogic,
JBoss, and WebSphere application servers. Developers who are interested in modifying and extending
Commerce Reference Store should follow these instructions provided in this guide. This chapter covers the
following topics:
Document Conventions
This guide uses <ATG11dir> to represent the Oracle Commerce Platform installation directory (C:\ATG
\ATG11.1, for example).
1 Introduction 1
2 1 Introduction
2 Installation Instructions
This section describes the Commerce Reference Store architecture and provides detailed information on how to
install and configure it.
Has two Oracle Commerce Platform instances, one for publishing and one for production, which run under
separate servers within a single application server distribution.
Each Oracle Commerce Platform server instance (EAR file) running in your application server includes
the appropriate configuration and modules for its designated tasks. The publishing server runs Content
Administration, Site Administration, Oracle Commerce Merchandising, and, to make it available for editing in
the Business Control Center, an instance of Commerce Reference Store. The publishing server also runs the
components that allow the Oracle Commerce Platform to integrate with Oracle Commerce Guided Search. These
integration components trigger the loading of catalog data into the Oracle Commerce Content Acquisition
System. This loading step must happen before the data can be indexed in an Oracle Commerce MDEX Engine
and searched by Oracle Commerce Guided Search.
The production server runs the Content Administration publishing agent as well as the instance of Commerce
Reference Store that is served to customers. To allow it to query the MDEX via the Assembler API, the production
server also runs the Guided Search integration components.
The Commerce Reference Store EAR files are assembled in development mode, where only classes, libraries,
and J2EE modules are imported to the EAR file, and Nucleus configuration and other resources are used directly
from the Oracle Commerce Platform install directory. The two Oracle Commerce Platform servers communicate
with each other through the Java Remote Method Invocation (RMI) API, for example, when the publishing server
deploys content to the production server.
Commerce Reference Store includes three storefront sites: CRS Store US, CRS Store Germany, and CRS Home.
These sites are related in the following ways:
CRS Store US and CRS Home share a shopping cart, product comparisons, and gift and wish lists. Some
catalog items are available on both sites, but each site also has items not available on the other site.
CRS Store US and CRS Store Germany have identical catalogs but use different price lists, because CRS Store
US prices are in US dollars and CRS Store Germany prices are in Euros. These sites do not share a shopping
cart, product comparisons, or gift and wish lists.
2 Installation Instructions 3
Additionally, the three sites include support for the languages shown in the following table:
Commerce Reference Store uses a switching database configuration that allows you to deploy changes to an
offline copy of your data, rather than making changes directly to the data your live site depends on. After the
data is deployed to the offline copy, a switch is made so that the offline copy becomes the online copy and vice
versa. In this way, you avoid deploying to your live site, which can cause errors, inconsistencies, or poor site
performance. After the switch is made, the offline copy is also updated, so that both copies are current after each
deployment.
When you deploy from the publishing server to the production server, data that is ready to go live is copied from
a versioned database, implemented as part of Content Administration, to the production database. Not all data
benefits from versioning, so the production database contains several schemas:
The Production schema holds data that does not benefit from switching, such as user account data.
The SwitchingA and SwitchingB schemas hold data that does benefit from switching, such as catalog
and pricing data. Only one switching schema is active on the live site at any given time. Data is copied to the
offline schema, and then the switch is made.
The versioned database only has one schema, Publishing, that contains all the data required for your sites,
plus additional fields that manage asset versioning.
4 2 Installation Instructions
Installation Requirements
Before beginning an installation, make sure:
A supported JDK exists on the system, and the JVM is in the systems PATH.
A supported application server is installed. WebLogic environments must also have a user domain configured.
A supported version of Oracle Commerce Guided Search with Experience Manager is installed and running.
2 Installation Instructions 5
Note: Oracle Commerce Guided Search with Experience Manager runs on Linux, Solaris, and Windows only.
If you are installing the Oracle Commerce Platform on an AIX machine, then Guided Search with Experience
Manager must be installed on a separate machine.
You have usernames and passwords for four database accounts, along with the following connection details
for a supported database:
Host
Port
Database name
Database URL
Driver type and path to driver file. Environments that use a DB2 database also require a path to the DB2
license file.
For more information on supported operating systems, application server versions, JDK versions, and Oracle
Commerce Guided Search with Experience Manager versions, refer to the Oracle Commerce Supported
Environments document in the My Oracle Support knowledge base (https://support.oracle.com/).
As you progress through this guide, take care to follow the instructions that match your configuration.
Also, note that the Commerce Reference Store and this Installation and Configuration Guide have been tested on
the following configurations:
Solaris/WebLogic/Oracle/Sun JDK
AIX/WebSphere/DB2/IBM JDK
6 2 Installation Instructions
Note: Refer to the Oracle Commerce Supported Environments document in the My Oracle Support knowledge
base (https://support.oracle.com/) for detailed information on the supported versions of the operating sytems,
application servers, databases, and JDKs in the list above.
Set JAVA_HOME:
For Linux and Solaris, set JAVA_HOME to include the Sun JDK home directory (for example, /usr/local/
jdk1.7.0_55).
For AIX, set JAVA_HOME to include the home directory of the IBM JDK found in the WebSphere distribution
(for example, /usr/local/IBM/WebSphere/AppServer/java_1.7_64).
For Windows, set JAVA_HOME to include the Sun JDK home directory (for example, C:\Program Files
\Java\jdk1.7.0_55).
Set PATH:
For Linux, set PATH to include the Sun JDK /bin directory (for example, /usr/local/jdk1.7.0_55/bin).
For Solaris, set PATH to include the Sun JDK /bin/sparcv9 directory (for example, /usr/local/
jdk1.7.0_55/bin/sparcv9)
For AIX, set PATH to include the IBM JDK /bin directory included in the WebSphere distribution (for
example, /usr/local/IBM/Websphere/AppServer/java_1.7_64/bin).
For Windows, set PATH to include the Sun JDK /bin directory (for example, C:\Program Files\Java
\jdk1.7.0_55\bin.
(WebLogic only) If WebLogic is your application server, consider setting the following environment variables.
Note that your environment may require alternate values for these settings.
JAVA_OPTIONS='-d64 -XX:ParallelGCThreads=8
-Dsun.rmi.dgc.client.gcInterval=3600000
-Dsun.rmi.dgc.server.gcInterval=3600000'
Notes:
For WebSphere environments, Oracle recommends setting your JAVA_HOME and PATH variables to point to
the JDK installed in the WebSphere distribution to ensure that the JDK functionality that WebSphere relies on
is available and updated properly.
If you are running multiple versions of Oracle Commerce Platform on your machine, you should not set
DYNAMO_HOME globally, as this will change the variable for all Oracle Commerce Platform versions. Instead, set
DYNAMO_HOME locally for each shell or command prompt you open for the remainder of this guide.
2 Installation Instructions 7
Installing the Oracle Commerce Platform and Commerce
Reference Store Software
All of the installers are available as self-extracting Windows executables or UNIX binary files, which you can
download from the Oracle web site. On UNIX platforms, you must unjar the downloaded file to access the
installer .bin file, and then set permissions so that you can run the installers. To set installer permissions, run the
following command on the directory where the .bin files reside:
chmod 777 *
For example:
5. Specify the installation folder for the Oracle Commerce Platform software (for example, /usr/local/ATG/
ATG11.1 or C:\ATG\ATG11.1).
6. If you have specified an installation directory that differs from the default, confirm your entry.
8. Select your application server. For WebSphere environments, choose the second option, 2- IBM WebSphere,
for WebSphere without clustering.
8 2 Installation Instructions
The full path to the Oracle_Home directory, for example, /usr/local/Oracle/Middleware/
Oracle_Home
The full path to the WebLogic home directory, for example, /usr/local/Oracle/Middleware/
Oracle_Home/wlserver
The full path to the WebLogic domain directory, for example, /usr/local/Oracle/Middleware/
Oracle_Home/user_projects/domains/base_domain
The full path to the WebSphere install directory, for example, /usr/local/IBM/WebSphere/AppServer
(All Environments) Enter the listen port that your application server uses to listen for incoming
connections. Defaults are:
(All Environments) Enter the ATG RMI port your Nucleus-based applications will use (defaults to 8860).
10.Review the installation summary. On UNIX, press Enter to continue. On Windows, click Install.
The Oracle Commerce Platform installer copies the software distribution to the location you specified.
11.On UNIX, press Enter to exit the installer. On Windows, click Done to exit the installer.
5. Specify the installation folder for the Commerce Reference Store software (the default is the <ATG11dir>
directory). The installer creates a CommerceReferenceStore directory that contains the Commerce
Reference Store software in the location you provide.
2 Installation Instructions 9
6. If you have specified an installation directory that differs from the default, confirm your entry.
8. Review the installation summary. On UNIX, press Enter to continue. On Windows, click Install.
The Oracle Commerce Platform installer copies the Commerce Reference Store distribution to the location
you specified.
9. On UNIX, press Enter to exit the installer. On Windows, click Done to exit the installer.
Starting WebLogic
To start WebLogic:
1. In a UNIX shell, change directories to your user domains bin directory, for example, /usr/local/Oracle/
Middleware/Oracle_Home/user_projects/domains/base_domain/bin.
./startWebLogic.sh
3. After you see the notification <The server started in RUNNING mode>, open a browser and navigate to
http://hostname:7001/console to start the WebLogic Server Administration Console.
4. Enter your WebLogic username and password and click Log In.
Starting WebSphere
To start WebSphere:
In a UNIX shell, change directories to your deployment managers bin directory, for example, /usr/
local/IBM/WebSphere/AppServer/profiles/Dmgr01/bin
./startManager.sh
You see a status report similar to the following when the deployment manager has started:
10 2 Installation Instructions
Enter your user ID and, if necessary, password and click Login.
In a UNIX shell, change directories to your application servers bin directory, for example, /usr/local/
IBM/WebSphere/AppServer/profiles/AppSrv01/bin.
./startNode.sh
You see a status report similar to the following when the default application server has started:
Note that Guided Search with Experience Manager does not support the AIX operating system; therefore, if you
are installing the Oracle Commerce Platform on AIX, you must install Guided Search with Experience Manager
on a separate Linux, Windows, or Solaris machine and set up the shared directory.
As you progress through this guide, you will be notified when you need to point to this shared directory during
configuration process. Be careful to use the shared directorys path instead of the default path that is provided.
1. On the machine where Guided Search with Experience Manager is installed, create a directory, for example, /
usr/local/application_export_archive or C:\application_export_archive, and share it.
2. On the machine where the Oracle Commerce Platform is installed, mount the shared
application_export_archive directory.
2 Installation Instructions 11
Configuring your Oracle Commerce Platform server instances (production and publishing instances)
Assembling and deploying your Oracle Commerce Platform applications to the application server
Creating the EAC application that runs under Oracle Commerce Guided Search with Experience Manager
Starting CIM
CIM is a text-based application that simplifies configuration for the Oracle Commerce Platform products. CIM
dynamically generates menus for each part of the configuration process, so that you are presented with relevant
options for your installed products. For each step, CIM identifies a default option with an asterisk (*) and/or a
default note. In the main menu, this default identifies the next step to perform; in other menus, it shows the
standard selection for configuration choices.
To start CIM:
UNIX:
./cim.sh
Windows:
cim.bat
CIM starts, showing you the CIM MAIN MENU. For general instructions on using CIM, enter h at any time. The
following are some key notes that will help you as you use CIM:
To select an option, type its number or letter, then press Enter. Selected options are marked with an
asterisk. To deselect an option, type its number or letter and press enter. To select multiple options, type a
space-delimited list of option numbers or letters, then press Enter.
CIM maintains your selections, so you can start a configuration, quit CIM, and then return to CIM later
where you left off.
If you make a mistake, type m to return to the main menu and redo your selections.
Continue with the next section, Setting the Administrator Password (page 12).
1. In the CIM MAIN MENU, select [R] Set the Administrator Password.
2. In the RESET ADMINISTRATOR PASSWORD STEP, enter the administrator password, for example, Admin123.
4. Continue with the next section, Configuring Oracle Commerce Products (page 13).
12 2 Installation Instructions
Configuring Oracle Commerce Products
The next step to configuring a development environment is selecting the Oracle Commerce products and
add-ons you want to install. If your configuration does not include Internationalization, skip the steps marked
(International Only).
2. In the PRODUCT SELECTION menu, select [9] Oracle Commerce Reference Store - Includes the Oracle
Commerce Platform, Oracle Commerce Platform-Guided Search Integration, Content Administration, Site
Administration, Core Commerce, and Merchandising. Optional: data warehouse components and Preview.
3. Select D to indicate you are done and ready to move to the next menu.
4. In the CHOOSE ADDONS menu, select D to indicate you are done and ready to move to the next menu.
5. In the INCLUDE DEMO APPLICATION menu, select D to indicate you are done and ready to move to the next
menu.
6. In the CHOOSE SWITCHING OR NON-SWITCHING DATASOURCE menu, select [2] Switching Datasource.
7. In the COMMERCE INDEX TYPE SELECTION menu, select [1] Index by SKU.
8. In the EXPERIENCE MANAGER PREVIEW OPTIONS SELECTION FOR PRODUCTION, select [D] Done.
IMPORTANT: To properly configure Experience Manager Preview, your environment must include a staging
server. Experience Manager Preview will not be configured with the instructions in this guide.
9. Select [D] Done to indicate you are done and ready to move to the next menu.
10.In the CHOOSE COMMERCE REFERENCE STORE ADDONS menu, select the following:
[3] Fulfillment
To select multiple options, type them as a space-delimited list (1 3 4 5 6), then press Enter.
11.(International Only) If you want internationalization functionality, select [2] International: Enables multi-
country and multi-language functionality.
12.Select [D] Done to indicate you are done and ready to move to the next menu.
13.In the CHOOSE STOREFRONT ADDONS menu, select [2] Inspect Application.
14.Select [D] Done to indicate you are done and ready to move to the next menu.
15.In the CHOOSE STOREFRONT SAMPLE DATA CONFIGURATION menu, select [1] Full: Populated product
catalog, users, orders, promotions, etc.
16.In the CHOOSE ORACLE RECOMMENDATIONS ON DEMAND ACCOUNT menu, select [1] Use
Recommendations demonstration account.
2 Installation Instructions 13
17.In the CHOOSE CLICKTOCALL ACCOUNT menu, select [1] Use Click To Call demonstration account.
WebLogic
2. In the APPLICATION SERVER SELECTION menu, select [2] Oracle Weblogic Online (Either Production or
Developer Mode).
3. In the ENTER WEBLOGIC HOME PATH menu, enter the path to your WebLogic home, for example, /user/
local/Oracle/Middleware/Oracle_Home/wlserver.
4. In the ENTER DOMAIN PATH menu, enter the path to the WebLogic domain directory you created, for
example, /usr/local/Oracle/Middleware/Oracle_Home/user_projects/domains/base_domain.
5. In the ENTER URL TO ADMIN SERVER menu, enter the URL used to communicate with the WebLogic Admin
Server. The default is t3://localhost:7001.
6. In the ENTER USERNAME TO ADMIN SERVER menu, enter your WebLogic administrator username (default is
weblogic).
7. In the ENTER PASSWORD TO ADMIN SERVER menu, enter your WebLogic administrator password (default is
weblogic1).
9. In the VALIDATE WEBLOGIC ONLINE STATUS menu, select [P] Perform Validation.
Note: Depending on your environment, the confirmation message can take several minutes to appear.
10.Continue with the section Configuring Your Database Connections (page 15).
JBoss
1. In the CIM MAIN MENU menu, select [A] Select Application Server.
2. In the APPLICATION SERVER SELECTION menu, select [1] JBoss Application Server.
3. In the ENTER JBOSS HOME PATH menu, enter your JBoss home path, for example, /usr/local/jboss-
eap-6.1.0/jboss-eap-6.1 or C:\jboss-eap-6.1.0\jboss-eap-6.1.
4. Continue with the section Configuring Your Database Connections (page 15).
WebSphere
Note: The instructions below assume you have WebSphere security disabled.
14 2 Installation Instructions
2. In the APPLICATION SERVER SELECTION menu, select [3] IBM WebSphere Application Server.
3. In the ENTER WEBSPHERE HOME PATH menu, enter the full path to you WebSphere home directory, for
example, /usr/local/IBM/WebSphere/AppServer.
4. In the ENTER HOSTNAME TO ADMIN SERVER menu, enter the name of the machine that hosts your
WebSphere deployment manager.
Note: CIM refers to the WebSphere deployment manager as the admin server.
5. In the ENTER SOAP CONNECTOR PORT ON ADMIN SERVER menu, enter the SOAP port for your deployment
manager (default is 8879).
7. In the VALIDATE WEBSPHERE ONLINE STATUS menu, select [P] Perform Validation.
8. Continue with the section Configuring Your Database Connections (page 15).
5. Enter the following information for the database account you want to use for the Publishing schema:
User name
Password
Re-enter password
Host name
Port number
Database name
Database URL
Note: CIM will provide a Database URL for you, based on the information that you have already entered.
Driver path
JNDI name
Note: CIM provides a default JNDI name of ATGPublishingDS for the Publishing schema.
2 Installation Instructions 15
6. In the CONFIGURE DATASOURCE PUBLISHING menu, select [T] Test Connection.
9. In the CONFIGURE DATASOURCE PUBLISHING menu, select [I] Import Initial Data.
13.Enter a password for the publishing admin user, for example, Admin123.
Data importing begins for the publishing schema. Note that this process can take time, depending on your
environment.
15.In the CONFIGURE DATASOURCE PUBLISHING menu, select [O] Configure Another Datasource.
16.In the SELECT A DATASOURCE TO CONFIGURE menu, select [C] Production Core.
17.In the CONFIGURE DATASOURCE PRODUCTION CORE menu, select [C] Connection Details.
18.In the RE-USE VALUES FROM PREVIOUS DATASOURCE menu, select [2] None/Use Existing.
19.In the ENTER CONNECTION DETAILS menu, select your database type.
20.Enter the connections details for the database account you want to use for the Production Core schema. The
default JNDI name that CIM provides for the Production Core schema is ATGProductionDS.
21.In the CONFIGURE DATASOURCE PRODUCTION CORE menu, select [T] Test Connection.
22.In the CONFIGURE DATASOURCE PRODUCTION CORE menu, select [S] Create Schema.
24.In the CONFIGURE DATASOURCE PRODUCTION CORE menu, select [I] Import Initial Data.
26.Repeat steps 15 to 25 for the remaining two datasources. Be sure to configure the datasources in this order:
[S] Switching A
[B] Switching B
27.In the CONFIGURE DATASOURCE SWITCHING B menu, select [O] Configure Another Datasource.
29.Continue with the section Configuring a Security Credential for User Segment Requests (page 17).
16 2 Installation Instructions
Configuring a Security Credential for User Segment Requests
The user segment sharing feature allows a content administrator to choose a user segment that has been
defined in the Business Control Center as a trigger for a cartridge in Experience Manager. To enable this feature,
you must configure a security credential that is used in the user segment requests, as described below.
2. In the SECURITY DEPLOYMENT MENU, choose [1] Enter the location to deploy OPSS files.
4. In the SECURITY DEPLOYMENT MENU, choose [2] Enter the security credential for REST Services.
5. Enter the new credential at the prompt. The credential can be any text, similar to a password, however it
should correspond to your organizations OPSS security platform requirements.
8. In the COPY CREDENTIALS TO SHARED DIRECTORY menu, choose [D] Deploy to /<ATG11dir>/home/../
home/security.
9. In the VERIFY WHETHER TO OVERWRITE CURRENT DIRECTORY CONTENTS menu, choose [D] Deploy OPSS
configuration files.
11.Continue with the section Configuring Your Oracle Commerce Platform Server Instances (page 17).
2. In the SERVER INSTANCE TYPE SELECTION menu, select [P] Publishing Server - 0 Instances Configured.
3. In the SERVER INSTANCE TYPE CONFIGURATION menu, select [P] Publishing Server General Configuration -
REQUIRED.
4. Enter the following information for your publishing server instance. In most cases, you can accept the
defaults, which are provided in brackets below. The exception is the EAC base application name. Change this
setting from ATG to CRS.
2 Installation Instructions 17
EAC host name [localhost]
Application configuration archive path. This is the location where content promoted using the
file-based method is stored, for example, /usr/local/endeca/Apps/CRS/data/workbench/
application_export_archive/CRS or C:/Endeca/Apps/CRS/data/workbench/
application_export_archive/CRS. IMPORTANT: If you have a split install, where Oracle Commerce
Guided Search with Experience Manager and the Oracle Commerce Platform are installed on different
machines, you must specify a CRS directory in the shared directory you created in the Creating a Shared
Archive Directory (page 11) section, for example, /usr/local/application_export_archive/CRS
or C:\application_export_archive/CRS.
5. In the SERVER INSTANCE TYPE CONFIGURATION menu, select [I] Instance Management REQUIRED.
7. In the Select Type of Server Instance To Create menu, select [1] Publishing with a Server Lock Manager:
Minimum 1 Required.
8. In the NAME FOR NEW SERVER INSTANCE menu, enter ATGPublishing for the Server Instance Name.
In the WEBLOGIC ONLINE PORT BINDING menu, select [C] Choose Custom Port Binding.
In the CHOOSE CUSTOM WEBLOGIC ONLINE PORT BINDING menu, select [2] ports-01: http port is 7103.
In the JBOSS PORT BINDING menu, select [C] Choose Custom Port Binding.
In the CHOOSE CUSTOM JBOSS PORT BINDING menu, select [2] ports-01: http port is 8180.
In the WEBSPHERE PORT BINDING menu, select [C] Choose Custom Port Binding.
In the CHOOSE CUSTOM WEBSPHERE PORT BINDING menu, select [2] ports-01: http port is 9181.
12.Enter the following ports. The defaults CIM provides for each application server are listed in the table below.
You can leave the defaults as is unless they cause port conflicts on your machine.
18 2 Installation Instructions
Port Type WebLogic Default JBoss Default WebSphere Default
Note: By default the Sun T1000 and T2000 systems run a server that uses port 9010. ATGs lock management
components also use this port. If you are using lock management on one of these systems, you must either
disable the Sun server or use a different lock server port while configuring your server instance. See the Sun
T1000 and T2000 Requirements in the Platform Installation and Configuration Guide for detailed instructions.
14.In the SERVER INSTANCE TYPE CONFIGURATION menu, select [O] Configure Another Server Instance Type.
15.In the SERVER INSTANCE TYPE SELECTION menu, select [S] Production Server - 0 Instances Configured.
16.In the SERVER INSTANCE TYPE CONFIGURATION menu, select [P] Production Server General Configuration -
REQUIRED.
17.Enter the following information for your production server instance. Note that the defaults have been
updated based on the information you provided for the publishing server so, for most settings, you should be
able to accept the default values.
Application configuration archive path. This is the location where content promoted using the
file-based method is stored, for example, /usr/local/endeca/Apps/CRS/data/workbench/
application_export_archive/CRS or C:/Endeca/Apps/CRS/data/workbench/
2 Installation Instructions 19
application_export_archive/CRS. IMPORTANT: If you have a split install, where Oracle Commerce
Guided Search with Experience Manager and the Oracle Commerce Platform are installed on different
machines, you must specify a CRS directory in the shared directory you created in the Creating a Shared
Archive Directory (page 11) section, for example, /usr/local/application_export_archive/CRS
or C:\application_export_archive/CRS.
18.In the SERVER INSTANCE TYPE CONFIGURATION menu, select [I] Instance Management REQUIRED.
19.In the INSTANCE MANAGEMENT menu, select [A] Add Server Instance.
20.In the Select Type of Server Instance To Create menu, select [1] Production with a Server Lock Manager:
Minimum 1 Required.
21.In the NAME FOR NEW SERVER INSTANCE menu, enter ATGProduction for the Server Instance Name.
22.In the <Application_Server> ONLINE PORT BINDING menu, select [U] Use Default Port Binding.
23.Enter the following ports. The defaults CIM provides for each application server are listed in the table below.
You can leave the defaults as is unless they cause port conflicts on your machine.
25.In the SERVER INSTANCE TYPE CONFIGURATION menu, select [O] Configure Another Server Instance Type.
26.In the SERVER INSTANCE TYPE SELECTION menu, select [D] Done.
27.Continue with the section Creating the EAC Application (page 20).
If the Oracle Commerce Platform and Oracle Commerce Guided Search with Experience Manager are installed
on different machines, you must create the EAC application via a script. Note that Guided Search with
Experience Manager does not support the AIX operating system; therefore, if you are installing the Oracle
Commerce Platform on AIX, you must install Guided Search with Experience Manager on a separate Linux,
20 2 Installation Instructions
Windows, or Solaris machine and use a script to create the EAC application. See Appendix A: Creating the EAC
Application via Scripts (page 47) for detailed instructions. After creating the EAC application, continue with
the Assembling and Deploying Your Oracle Commerce Applications (page 22) in this guide.
1. In a new UNIX shell or command prompt, create the directory where the EAC applications are deployed, for
example, /usr/local/endeca/Apps or C:\Endeca\Apps.
3. In the SERVER INSTANCE TYPE SELECTION menu, select [S] Production Server - 1 Instance Configured DONE.
4. In the SERVER INSTANCE TYPE CONFIGURATION menu, select [D] Deploy CRS EAC Application OPTIONAL.
CAS Path including the version number. Enter the CAS Path using UNIX-style forward slashes, even if on
Windows, for example, /usr/local/endeca/CAS/11.1.0 or C:/Endeca/CAS/11.1.0.
Production application server HTTP port number. IMPORTANT: If you are following the instructions in this
guide, these values are 7003 for WebLogic, 8080 for JBoss and Tomcat, and 9081 for WebSphere.
Preview host name [localhost]. For this installation, use the ATGProduction servers host name.
Preview port number. For this installation, use the ATGProduction servers HTTP port. IMPORTANT: If you
are following the instructions in this guide, these values are 7003 for WebLogic, 8080 for JBoss and Tomcat,
and 9081 for WebSphere.
IMPORTANT: The proper way to configure Experience Manager preview is to have it reference a staging
server. Because the configuration documented in this guide does not include a staging server, you
should use the ATGProduction servers host and port instead. However, please note that, with this
2 Installation Instructions 21
configuration, Experience Manager Preview will be referencing the live production server and changes
made in Experience Manager will not be reflected until after they are promoted to the live production
server using the promote_content.sh|bat script.
Host name of the user segment server. This is the server that will respond to Workbench requests for
Busines Control Center user segment data. Oracle recommends using the Content Adminstration server
(also called the Publishing server in this guide). [localhost]
HTTP port of the user segment server. IMPORTANT: If you are following the instructions in this guide, these
values are 7103 for WebLogic, 8180 for JBoss and Tomcat, and 9181 for WebSphere.
Path for the Oracle Wallet jps-config.xml file, for example, /usr/local/endeca/
ToolsAndFrameworks/11.1.0/server/workspace/credential_store/jps-config.xml or C:
\Endeca\ToolsAndFrameworks\11.1.0\server\workspace\credential_store\jps-config.xml
Application configuration archive path. This is the location where content promoted using
the file-based method is stored, for example, /usr/local/endeca/Apps/CRS/data/
workbench/application_export_archive or C:/Endeca/Apps/CRS/data/workbench/
application_export_archive.
Note that, unlike the server instance configuration, this path does not include /CRS at the end.
Path to the MDEX directory including the version number, for example, /usr/local/endeca/
MDEX/6.5.1 or C:\Endeca\MDEX\6.5.1
Path to the Platform Services directory including the version number, for example, /usr/local/endeca/
PlatformServices/11.1.0 or C:\Endeca\PlatformServices\11.1.0
8. In the INITIALIZE CRS EAC APP menu, choose [I] Initialize. After the initializing is done, you are returned to the
SERVER INSTANCE TYPE CONFIGURATION menu.
9. In the SERVER INSTANCE TYPE CONFIGURATION menu, choose [O] Configure Another Server Instance Type.
10.In the SERVER INSTANCE TYPE SELECTION menu, choose [D] Done.
11.Continue with the section Assembling and Deploying Your Oracle Commerce Applications (page 22).
WebLogic
To assemble and deploy your Oracle Commerce applications on WebLogic:
1. In the CIM MAIN MENU, select [4] Application Assembly & Deployment.
2. In the DEPLOYMENT SERVER INSTANCE SELECTION menu, select [A] ATGProduction - Production with a Server
Lock Manager.
22 2 Installation Instructions
3. In the ENTER EAR FILE NAME(S) menu, enter the name ATGProduction.ear.
4. In the WEBLOGIC ONLINE DEPLOYMENT MENU, select [D] Deploy Production with a Server Lock Manager
ATGProduction.ear to Weblogic Online.
5. In the WEBLOGIC ONLINE DEPLOYMENT MENU, select [R] Register Datasources on WebLogic Online.
6. In the WEBLOGIC ONLINE DEPLOYMENT MENU, select [A] Add database driver to app server classpath.
7. In the WEBLOGIC CLASSPATH MODIFICATION menu, select [U] Update the WebLogic_user_domain/bin/
setDomainEnv.sh file.
8. In the WEBLOGIC ONLINE DEPLOYMENT MENU, select [P] Post Deployment Actions on WebLogic Online.
9. In the POST DEPLOYMENT OPTIONS menu, select [W] Weblogic JVM Optimization.
10.In the WEBLOGIC JVM OPTIMIZATION menu, select [U] Update startup script.
11.In the POST DEPLOYMENT OPTIONS menu, select [C] Copy protocol.jar.
12.In the WEBLOGIC POST DEPLOYMENT OPTIONS menu, select [C] Copy protocol.jar to Production with a Server
Lock Manager ATGProduction.ear to Weblogic Online.
14.In the WEBLOGIC ONLINE DEPLOYMENT MENU, select [O] Configure Another Server Instance.
15.In the DEPLOYMENT SERVER INSTANCE SELECTION menu, select [P] ATGPublishing - Publishing with a Server
Lock Manager.
16.In the ENTER EAR FILE NAME(S) menu, enter the name ATGPublishing.ear for the ATG Commerce Store
Production with Server Lock Manager.
17.In the WEBLOGIC ONLINE DEPLOYMENT MENU, select [D] Deploy Publishing with a Server Lock Manager
ATGPublishing.ear to Weblogic Online.
18.In the WEBLOGIC ONLINE DEPLOYMENT MENU, select [R] Register Datasources on WebLogic Online.
19.In the WEBLOGIC ONLINE DEPLOYMENT MENU, select [A] Add database driver to app server classpath.
20.In the WEBLOGIC CLASSPATH MODIFICATION menu, select [U] Update the WebLogic_domain/bin/
setDomainEnv.sh file.
21.In the WEBLOGIC ONLINE DEPLOYMENT MENU, select [P] Post Deployment Actions on WebLogic Online.
22.In the POST DEPLOYMENT OPTIONS menu, select [C] Copy protocol.jar.
23.In the WEBLOGIC POST DEPLOYMENT OPTIONS menu, select [C] Copy protocol.jar to Publishing with a Server
Lock Manager ATGPublishing.ear to Weblogic Online.
25.In the WEBLOGIC ONLINE DEPLOYMENT MENU, select [O] Configure Another Server Instance.
26.In the DEPLOYMENT SERVER INSTANCE SELECTION menu, select [D] Done.
JBoss
To assemble and deploy your Oracle Commerce applications on JBoss:
2 Installation Instructions 23
1. In the CIM MAIN MENU, select [4] Application Assembly & Deployment.
2. In the DEPLOYMENT SERVER INSTANCE SELECTION menu, select [A] ATGProduction - Production with a Server
Lock Manager.
3. In the ENTER EAR FILE NAME(S) menu, enter the name ATGProduction.ear.
4. In the SELECT JBOSS SERVER TO USE menu, select [C] CIM should create a new server for me.
5. In the SELECT JBOSS SERVER TEMPLATE TO USE menu, select [S] standalone.xml.
7. In the JBOSS DEPLOYMENT MENU, select [D] Deploy Production with a Server Lock Manager
ATGProduction.ear to JBoss.
9. In the JBOSS DEPLOYMENT MENU, select [A] Add database driver to app server classpath.
10.In the JBOSS JDBC DRIVER JAR COPY menu, select [C] Copy file.
11.In the JBOSS DEPLOYMENT MENU, select [P] Post Deployment Actions on JBoss.
12.In the POST DEPLOYMENT OPTIONS menu, select [J] JBoss JVM Optimization.
13.In the JBOSS JVM OPTIMIZATION menu, select [U] Update JBoss standalone.conf.bat file.
15.In the JBOSS DEPLOYMENT MENU, select [O] Configure Another Server Instance.
16.In the DEPLOYMENT SERVER INSTANCE SELECTION menu, select [P] ATGPublishing - Publishing with a Server
Lock Manager.
17.In the ENTER EAR FILE NAME(S) menu, enter the name ATGPublishing.ear.
18.In the SELECT JBOSS SERVER TO USE menu, select [C] CIM should create a new server for me.
19.In the SELECT JBOSS SERVER TEMPLATE TO USE menu, select [S] standalone.xml.
21.In the JBOSS DEPLOYMENT MENU, select [D] Deploy Publishing with a Server Lock Manager
ATGPublishing.ear to JBoss.
22.In the JBOSS DEPLOYMENT MENU, select [R] Register Datasources on JBoss.
23.In the JBOSS DEPLOYMENT MENU, select [A] Add database driver to app server classpath.
24.In the JBOSS JDBC DRIVER JAR COPY menu, select [C] Copy file.
25.In the JBOSS DEPLOYMENT MENU, select [P] Post Deployment Actions on JBoss.
27.In the JBOSS DEPLOYMENT MENU, select [O] Configure Another Server Instance.
28.In the DEPLOYMENT SERVER INSTANCE SELECTION menu, select [D] Done.
24 2 Installation Instructions
29.In the CIM MAIN MENU, enter q to exit CIM.
WebSphere
1. In the CIM MAIN MENU, select [4] Application Assembly & Deployment.
2. In the DEPLOYMENT SERVER INSTANCE SELECTION menu, select [A] ATGProduction - Production with a Server
Lock Manager.
3. In the ENTER EAR FILE NAME(S) menu, enter the name ATGProduction.ear for the Production with a Server
Lock Manager ear file.
5. In the SELECT WEBSPHERE SERVER TO USE menu, select [C] CIM should create a new server for me.
7. In the WEBSPHERE DEPLOYMENT MENU, select [D] Deploy Production with a Server Lock Manager
ATGProduction.ear to WebSphere.
9. In the WEBSPHERE DEPLOYMENT MENU, select [A] Add database driver to app server classpath.
10.In the WEBSPHERE APP SERVER CLASSPATH menu, select [C] Continue.
11.In the WEBSPHERE DEPLOYMENT MENU, select [O] Configure Another Server Instance.
12.In the DEPLOYMENT SERVER INSTANCE SELECTION menu, select [P] ATGPublishing - Publishing with a Lock
Server.
13.In the ENTER EAR FILE NAME(S) menu, enter the name ATGPublishing.ear for the Publishing with a Server
Lock Manager ear file.
15.In the SELECT WEBSPHERE SERVER TO USE menu, select [C] CIM should create a new server for me.
17.In the WEBSPHERE DEPLOYMENT MENU, select [D] Deploy Publishing with a Server Lock Manager
ATGPublishing.ear to WebSphere.
18.In the WEBSPHERE DEPLOYMENT MENU, select [R] Register Datasources on WebSphere.
19.In the WEBSPHERE DEPLOYMENT MENU, select [A] Add database driver to app server classpath.
20.In the WEBSPHERE APP SERVER CLASSPATH menu, select [C] Continue.
21.In the WEBSPHERE DEPLOYMENT MENU, select [O] Configure Another Server Instance.
22.In the DEPLOYMENT SERVER INSTANCE SELECTION menu, select [D] Done.
2 Installation Instructions 25
Reducing Logging Messages
In order to write records to the CAS record stores, the Oracle Commerce Guided Search document
submitters import classes from the com.endeca.itl.record and com.endeca.itl.recordstore
packages. These classes make use of the Apache CXF framework. Using the default CXF configuration
results in a large number of informational logging messages. The volume of the messages can result in
problems. In particular, environments that use MSSQL and index by SKU will have issues because the
logging seizes up the MSSQL server and indexing fails. Therefore, you should reduce the number of logging
messages by setting the logging level of the org.apache.cxf.interceptor.LoggingInInterceptor
and org.apache.cxf.interceptor.LoggingOutInterceptor loggers to WARNING for both the
ATGPublishing and the ATGProduction server instances. The way to set these logging levels differs
depending on your application server. See the documentation for your application server for information.
In DB2 environments, you must modify the DeploymentManager components properties for the Publishing
server in order for deployments to succeed. DB2 deadlocks occur during deployments over multiple Content
Administration threads. This problem is due to IBMs locking strategy (see PMR #42831,756,000), which
constrains Oracle Commerce Platform deployments to a single thread. Use the workaround provided below to
avoid this problem.
To enable the ATGPublishing server to trigger the data loading process to run on the ATGProduction server:
<ATG11dir>/home/servers/ATGPublishing/localconfig/atg/search
host=production-server-host-name
port=production-server-rmi-port
maxThreads=1
26 2 Installation Instructions
useDistributedDeployment=false
1. If the WebLogic Server Administration Console is not already open, open a browser, navigate to
http://hostname:7001/console , enter your WebLogic username and password, and click Log In.
7. Repeat steps 3 through 6 for each of the other datasources: ATGPublishingDS, ATGSwitchingDS_A, and
ATGSwitchingDS_B.
1. If the WebSphere Integrated Solutions Console is not already open, open a browser, navigate to the consoles
URL, for example http://hostname:9060/admin, enter your user ID, and click Log In.
5. Under Container Settings, expand Container Services, then click Transaction Service.
6. Set both the Total transaction lifetime timeout and the Maximum transaction timeout to 500.
2 Installation Instructions 27
7. Click OK.
11.Set both the Initial heap size and the Maximum heap size to 1024.
-Djava.net.preferIPv4Stack=true
13.Click OK.
16.Click New.
19.Click OK.
23.Under Container Settings, expand Container Services, then click Transaction Service.
24.Set both the Total transaction lifetime timeout and the Maximum transaction timeout to 500.
25.Click OK.
29.Set both the Initial heap size and the Maximum heap size to 1024.
-Djava.net.preferIPv4Stack=true
31.Click OK, then click Save to apply your changes to the master configuration.
28 2 Installation Instructions
WebLogic
Starting a server instance on WebLogic is a two-step process. First, you must start the WebLogic server that the
server instance runs under, and then you start the server instance itself in the WebLogic Server Administration
Console.
./startManagedWebLogic.sh ATGPublishing
Note: Depending on how you configured WebLogic, you may or may not need to enter a username and
password when starting a server.
When you see the message Server started in RUNNING mode continue with the next step.
When the ATGPublishing server is ready to service requests, its state changes to Active and its health
changes to OK.
./startManagedWebLogic.sh ATGProduction
Note: Depending on how you configured WebLogic, you may or may not need to enter a username and
password when starting a server.
When you see the message Server started in RUNNING mode continue with the next step.
Note: This step assumes you are still on the Summary of Deployments page in the WebLogic Server
Administration Console. If not, under Domain Structure, click Deployments for your user domain to see this
page.
2 Installation Instructions 29
7. Click Start and choose Servicing All Requests.
When the ATGProduction server is ready to service requests, its state changes to Active and its health
changes to OK.
8. Continue with the section Browsing the Publishing and Production Servers (page 31).
JBoss
To start the ATGPublishing server:
1. In a UNIX shell or command prompt, navigate to the JBoss bin directory, for example, /usr/local/jboss-
eap-6.1.0/jboss-eap-6.1/bin or C:\jboss-eap-6.1.0\jboss-eap-6.1\bin.
UNIX:
Windows:
Note: You can find the output log for the ATGPublishing server instance running under JBoss in jboss-
eap-6.1.0/jboss-eap-6.1/standalone/log/ATGPublishing.log.
UNIX:
Windows:
Note: You can find the output log for the ATGProduction server instance running under JBoss in jboss-
eap-6.1.0/jboss-eap-6.1/standalone/log/ATGProduction.log.
4. Continue with the section Browsing the Publishing and Production Servers (page 31).
WebSphere
To start the ATGPublishing and ATGProduction servers and applications:
1. In the WebSphere Integrated Solutions Console, if necessary, expand Servers, and then expand Server Types.
3. Select the ATGPublishing server and click Start. This process starts the ATGPublishing server and also
automatically starts the ATGPublishing.ear application.
30 2 Installation Instructions
4. Select the ATGProduction server and click Start. This process starts the ATGProduction server and also
automatically starts the ATGProduction.ear application.
5. Continue with the section Browsing the Publishing and Production Servers (page 31).
http://<hostname>:<HTTP_port>/atg/bcc
http://localhost:7103/atg/bcc
On JBoss:
http://localhost:8180/atg/bcc
On WebSphere:
http://localhost:9181/atg/bcc
2. Enter admin for the username and Admin123 for the password, and then click Log In.
http://<hostname>:<HTTP_port>/dyn/admin
http://localhost:7103/dyn/admin
On JBoss:
http://localhost:8180/dyn/admin
On WebSphere:
http://localhost:9181/dyn/admin
2 Installation Instructions 31
2. In the authentication dialog box, enter admin for the username and Admin123 password and click OK.
3. (WebLogic only) Depending on how you configured your environment, WebLogic may require an additional
login for the WebLogic server. If necessary, enter your WebLogic username and password, and then click OK.
http://<hostname>:<HTTP_port>/dyn/admin
http://localhost:7003/dyn/admin
On JBoss, use:
http://localhost:8080/dyn/admin
On WebSphere, use:
http://localhost:9081/dyn/admin
1. If necessary, log onto the Business Control Center. For instructions, see Browsing the Publishing Server (page
31).
32 2 Installation Instructions
Site Initialization Options: Do a full deployment
5. Add the following repository mappings. To add a repository mapping, select a Source Repository and
Destination Repository, then click Add.
/atg/commerce/catalog/ /atg/commerce/catalog/
SecureProductCatalog ProductCatalog_production
/atg/commerce/claimable/ /atg/commerce/claimable/
SecureClaimableRepository ClaimableRepository_production
/atg/commerce/locations/ /atg/commerce/locations/
SecureLocationRepository LocationRepository_production
/atg/commerce/pricing/priceLists/ /atg/commerce/pricing/priceLists/
SecurePriceLists PriceLists_production
/atg/content/ /atg/content/
SecureContentManagementRepository ContentManagementRepository_production
/atg/multisite/SecureSiteRepository /atg/multisite/
SiteRepository_production
/atg/seo/SecureSEORepository /atg/seo/SEORepository_production
/atg/store/stores/ /atg/store/stores/
SecureStoreContentRepository StoreContentRepository_production
/atg/userprofiling/ /atg/userprofiling/
PersonalizationRepository PersonalizationRepository_production
Note: Your browser must have Javascript enabled to create these mappings.
6. Click Save Changes to save your changes and enable the Agents tab.
7. Click the Agents tab, and then click Add Agent to Site.
For example:
rmi://localhost:8860/atg/epub/AgentTransport
Note: The RMI port you enter here should be the same RMI port you specified in Installing the Oracle
Commerce Platform (page 8).
2 Installation Instructions 33
9. Click the button with the double-right arrow to include both the /atg/epub/file/WWWFileSystem and /
atg/epub/file/ConfigFileSystem file systems in the configuration.
13.Accept the default, Do a full deployment (data NOT imported), then click Make changes live.
14.To view your deployments progress, under Deployment Administration, click Overview, then click Production
to see the percent complete.
15.After the deployment has finished, proceed to the next section, Checking the Baseline Index Status (page
34), to verify that the baseline index initiated after the deployment completes successfully.
Note: If your deployment is not successful, it may be related to the transaction timeout setting in your
application server. All supported application servers time out long running transactions by marking the active
transaction as rolled back (essentially, by calling setRollbackOnly on the transaction), which could result in
problems with Oracle Commerce Platform applications. If your deployment fails, try increasing the transaction
timeout setting and resuming the deployment in the Business Control Center. For details on changing your
transaction timeout, see Setting the Transaction Timeout on WebLogic, Setting the Transaction Timeout on JBoss, or
Setting the Transaction Timeout on WebSphere in the Platform Installation and Configuration Guide.
1. In a browser, return to the Dynamo Server Admin on the ATGProduction server. See Browsing the
Production Server (page 32) for details.
2. Click the Component Browser link, and then use the subsequent links to navigate to the /atg/commerce/
endeca/index/ProductCatalogSimpleIndexingAdmin component.
3. Ensure that the Auto Refresh option is selected so that the status information is refreshed.
4. When the Status for all phases is COMPLETE (Succeeded), proceed to the next section, Promoting the
Commerce Reference Store Content (page 34).
34 2 Installation Instructions
To promote the Commerce Reference Store content:
1. Open a UNIX shell or command prompt on the server that is running Guided Search with Experience
Manager.
2. Change directories to the CRS Endeca applications control directory, for example:
cd /usr/local/endeca/Apps/CRS/control
or
cd C:\Endeca\Apps\CRS\control
UNIX:
./promote_content.sh
Windows:
promote_content.bat
http://<hostname>:<HTTP_port>/crs
http://localhost:7003/crs
On JBoss use:
http://localhost:8080/crs
On WebSphere use:
http://localhost:9081/crs
1. In a UNIX shell or command prompt on the server that is running Guided Search with Experience
Manager, navigate to the ENDECA_TOOLS_ROOT/credential_store/bin directory, for example, /
2 Installation Instructions 35
usr/local/endeca/ToolsAndFrameworks/version/credential_store/bin or C:\Endeca
\ToolsAndFrameworks\version\credential_store\bin.
On UNIX, enter:
For example:
On Windows, enter:
For example:
3. At the prompt, enter the same credential you specified during the OPSS configuraiton in CIM.
./shutdown.sh
./startup.sh
1. From the Start menu, choose Administrative Tools > Services to open the Services control panel.
To confirm that the Business Control Center user segments are appearing in Experience Manager:
2. Enter your Workbench username and password (default is admin for both values) and click Log In.
36 2 Installation Instructions
4. Under Content, expand Shared, then click Auto-Suggest Panels.
6. Click Select User Segments. The Business Control Center user segments (Fashionista, MenOnly,
ThirtySomethings, WomenOnly, and Young) should appear in the Add/Modify User Segments dialog box.
1. In a UNIX shell or command prompt on the machine that is running the Oracle Commerce Platform, locate
the /atg/commerce/search/ProductCatalogOutputConfig.properties file in the <ATG11dir>/
home/servers/ATGPublishing/localconfig/ directory.
2. Remove the # from the #targetName=production line to set the targetName property and save the file.
3. Repeat the preceding step with the following files located in the <ATG11dir>/home/servers/
ATGPublishing/localconfig/ directory:
/atg/commerce/search/StoreLocationOutputConfig
/atg/commerce/endeca/index/CategoryToDimensionOutputConfig
/atg/content/search/ArticleOutputConfig
/atg/content/search/MediaContentOutputConfig
4. Stop and restart the ATGPublishing server. For details on stopping the server, see Stopping the Publishing
and Production Servers and Removing Their Artifacts (page 39). For details on starting the server, see
Starting the Publishing and Production Servers (page 28).
2 Installation Instructions 37
38 2 Installation Instructions
3 Uninstalling Commerce Reference
Store
The instructions in this section tell you how to remove an existing Commerce Reference Store installation
so that you have a clean environment and can start again. In the procedure below, you are only removing
Oracle Commerce Platform and Commerce Reference Store artifacts. Your application server, the JDK, and your
environment variables remain intact and usable for your next installation. The basic process involves these steps:
(WebLogic and WebSphere Only) Remove the Commerce Reference Store artifacts through the application
server console.
Use CIM to drop the Production, Switching B, Switching A, and Publishing schemas from your database, in that
order.
(Windows Only) Remove the Oracle Commerce Platform and Oracle Commerce Reference Store software
through the Add or Remove Programs control panel.
1. Go to the shell where you started the WebLogic server that supports the ATGProduction server instance and
enter Ctrl-C to stop the WebLogic server.
2. Go to the shell where you started the WebLogic server that supports the ATGPublishing server instance and
enter Ctrl-C to stop the WebLogic server.
http://<hostname>:7001/console
6. Select the ATGPublishing.ear and the ATGProduction.ear, and then click Delete.
7. Under Domain Structure, expand Environment for your user domain, and then click Servers.
8. Select the ATGPublishing and the ATGProduction servers, and then click Delete.
9. Under Domain Structure, expand Services for your user domain, and then click Data Sources.
cd /usr/local/Oracle/Middleware/Oracle_Home/user_projects/domains/
base_domain/bin
./stopWebLogic.sh
On UNIX
To stop the ATGProduction and ATGPublishing servers on UNIX:
ps ef
2. Identify the process ID numbers for the ATGProduction and ATGPublishing servers and their related Java
processes.
3. Enter the following command to kill the processes, replacing <processIDs> with a space delimited list of the
IDs you identified in the previous step:
kill -9 <processIDs>
Note: It is best to use this method of killing the Oracle Commerce Platform servers, instead of Control-C, in
order to make sure that all related processes are stopped and the ports are available for future use.
Delete all XML files whose names start with either ATGProduction or ATGPublishing.
On Windows
To stop the ATGProduction and ATGPublishing servers on Windows:
1. In the command prompt where you are running the ATGProduction server, type Ctrl-C.
3. Repeat these steps in the command prompt where you are running the ATGPublishing server.
4. In a command prompt or using Windows Explorer, delete the ATGProduction and ATGPublishing
directories:
Delete all XML files whose names start with either ATGProduction or ATGPublishing.
http://localhost:9060/ibm/console
6. Click OK to confirm, and then click OK again in the Server Status Feedback page after the servers are stopped.
13.Click OK to confirm, and then click Save to save the change to the master configuration.
16.Click OK to confirm, and then click Save to save the changes to the master configuration.
In a UNIX shell, change directories to your application servers bin directory, for example, /usr/local/
IBM/WebSphere/AppServer/profiles/AppSrv01/bin.
./stopNode.sh
You see a status report similar to the following when the default application server has stopped:
In a UNIX shell, change directories to your deployment managers bin directory, for example, /usr/
local/IBM/WebSphere/AppServer/profiles/Dmgr01/bin
./stopManager.sh
You see a status report similar to the following when the deployment manager has stopped:
23.In a shell window, delete the ATGProduction and ATGPublishing log directories:
1. In a UNIX shell or command prompt, run CIM. For detailed instructions, see Starting CIM (page 12).
6. In the CONFIGURE DATASOURCE SWITCHING B menu, select [O] Configure Another Datasource.
10.In the CONFIGURE DATASOURCE SWITCHING A menu, select [O] Configure Another Datasource.
11.In the SELECT A DATASOURCE TO CONFIGURE menu, select [C] Production Core Done.
12.In the CONFIGURE DATASOURCE PRODUCTION CORE menu, select [D] Drop Schema.
14.In the CONFIGURE DATASOURCE PRODUCTION CORE menu, select [O] Configure Another Datasource.
15.In the SELECT A DATASOURCE TO CONFIGURE menu, select [P] Publishing Done.
16.In the CONFIGURE DATASOURCE PUBLISHING menu, select [D] Drop Schema.
5. Click Done.
6. In the control panel, select Oracle Commerce Platform [version] and click Uninstall/Change.
8. Click Done.
2. Change directories to the CRS EAC applications control directory, for example:
cd /usr/local/endeca/Apps/CRS/control
or
cd C:\Endeca\Apps\CRS\control
On UNIX, enter:
./runcommand.sh --remove-app
On Windows, enter:
runcommand.bat -remove-app
1. In a UNIX shell or command prompt, change directories to the CAS bin directory, for example:
cd /usr/local/endeca/CAS/11.1.0/bin
or
cd C:\Endeca\CAS\11.1.0\bin
2. Enter one of the following commands to delete the CRS-data record store.
On UNIX, enter:
On Windows, enter:
3. To delete the other two record stores, repeat the command in the previous step two more times, substituting
CRS-dimvals and CRS-dimension-value-id-manager for CRS-data.
4. To verify that your record stores are deleted, you can optionally use this command:
On UNIX, enter:
./component-manager-cmd.sh list-components
On Windows, enter:
component-manager-cmd.bat list-components
You should see the following message, indicating that all three record stores are deleted:
On UNIX, enter:
On Windows, enter:
At this point, you are ready for a clean Commerce Reference Store installation. To do a clean install, begin with
the Installing the Oracle Commerce Platform and Commerce Reference Store Software (page 8) section in this
guide.
This appendix provides instructions for creating the EAC application that supports Commerce Reference Store
using scripts instead of CIM. If the Oracle Commerce Platform and Oracle Commerce Guided Search with
Experience Manager are installed on different servers, you must create and provision the EAC application using
the scripts described below. After creating the EAC application, return to the Assembling and Deploying Your
Oracle Commerce Applications (page 22) section earlier in this guide to finish configuring your environment.
1. On the machine where Oracle Commerce Guided Search with Experience Manager is installed, create the
directory where the EAC application will reside, for example, /usr/local/endeca/Apps or C:\Endeca
\Apps.
3. On the machine where Oracle Commerce Guided Search with Experience Manager is installed, open a UNIX
shell or command prompt and browse to the ToolsAndFrameworks /deployment_template/bin directory,
for example, /usr/local/endeca/ToolsAndFrameworks/11.1.0/deployment_template/bin or C:
\Endeca\ToolsAndFrameworks\11.1.0\deployment_template\bin.
On Windows, enter:
5. After the note about the Platform Services version, press Enter to continue with the install.
Enter the full path to the Apps directory, for example: /usr/local/endeca/Apps or C:\Endeca\Apps.
Note: The EAC port is used for all Endeca applications that have been deployed, so if you deploy more than
one application, continue to use the same port number for all of them.
Enter the CAS install directory using UNIX-style forward slashes, even if on Windows. For example, /usr/
local/endeca/CAS/11.1.0 or C:/Endeca/CAS/11.1.0.
Production application server host name. This is the host where the ATGProduction server will be
running. [localhost]
Production application server HTTP port number. IMPORTANT: If you are following the instructions in this
guide, these values are 7003 for WebLogic, 8080 for JBoss and Tomcat, and 9081 for WebSphere.
Preview host name [localhost]. For this installation, use the ATGProduction servers host name.
Preview port number. For this installation, use the ATGProduction servers HTTP port. IMPORTANT: If you
are following the instructions in this guide, these values are 7003 for WebLogic, 8080 for JBoss and Tomcat,
and 9081 for WebSphere.
IMPORTANT: The proper way to configure Experience Manager preview is to have it reference a staging
server. Because the configuration documented in this guide does not include a staging server, you
should use the ATGProduction servers host and port instead. However, please note that, with this
configuration, Experience Manager Preview will be referencing the live production server and changes
made in Experience Manager will not be reflected in Preview until after they are promoted to the live
production server using the promote_content.sh|bat script.
Host name of the user segment server. This is the server that will respond to Experience Manager requests
for Business Control Center user segment data. Oracle recommends using the Content Adminstration
server (also called the ATGPublishing server in this guide). [localhost]
HTTP port of the user segment server. IMPORTANT: If you are following the instructions in this guide, these
values are 7103 for WebLogic, 8180 for JBoss and Tomcat, and 9181 for WebSphere.
Path for the Oracle Wallet jps-config.xml file, for example, /usr/local/endeca/
ToolsAndFrameworks/11.1.0/server/workspace/credential_store/jps-config.xml or C:
\Endeca\ToolsAndFrameworks\11.1.0\server\workspace\credential_store\jps-config.xml
Application configuration archive path. This is the location where content promoted using
the file-based method is stored, for example, /usr/local/endeca/Apps/CRS/data/
workbench/application_export_archive or C:/Endeca/Apps/CRS/data/workbench/
application_export_archive. IMPORTANT: If you have a split install, where Oracle Commerce
You see a message that says Application successfully deployed when the deployment is finished.
7. In a UNIX shell or command prompt, change directories to the EAC applications directory, for example, /usr/
local/endeca/Apps or C:\endeca\Apps. The CRS application directory is added as child of the /Apps
directory.
Commerce Reference Store only requires one EAC application, so at this point you can move onto provisioning
the application, described below. Other environments may require additional EAC applications (see the
Platform-Guided Search Integration Guide for guidance). If so, you should create additional EAC applications for
any other Oracle Commerce Platform server instances which you intend to index against, for example, Staging
and Publishing servers. Be sure to enter unique ports for Live Dgraph, Authoring Dgraph, and LogServer for each
additional application.
1. In a UNIX shell or command prompt, change directories to your EAC applications /control directory, for
example, /usr/local/endeca/Apps/CRS/control or C:\Endeca\Apps\CRS\control.
./initialize_services.sh
On Windows, enter:
initialize_services.bat
3. Return to the Assembling and Deploying Your Oracle Commerce Applications (page 22) section earlier in
this guide to finish configuring your environment. (Note: If your environment has multiple EAC applications,
repeat these steps for any other EAC applications you created.)
D U
DB2 uninstalling
additional configuration required for, 26 dropping ATG schemas, 43
deployment removing ATG artifacts, 39
configuring and running, 32 removing ATG software, 44
troubleshooting, 34 removing the Endeca application, 44
Dynamo Server Admin, 31, 32, 34 stopping the ATG servers, 39
DYNAMO_HOME, 7
W
E WebLogic
Endeca application starting, 10
creating via scripts, 47 WebSphere, starting, 10
environment variables, 7
F
file locations, 1
I
installing
assembling and deploying ATG applications, 22
Index 51
52 Index